yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] DarkSJ1998:
Ohh yeah, my bad :)

How could I forget the legendary CM Theme Engine? Maybe because it's been a while since I last saw it. Used to use it on my old device. Thanks for correcting me! :) Post edited :victory:
[OnePlus 3 & 3T Cross Device Development] ceanth:
This is going to sound crazy but my device appears to be playing a song all the time :confused:

It seems to trigger when I plug the device into charge and then it just keeps playing. I closed all my apps but it still plays.

No idea what I have done but I can't seem to turn it off unless I put the device in silent mode or vibrate mode
[OnePlus 3 & 3T Cross Device Development] DarkSJ1998:
It seems to me as if you set a song on the charging sound in Settings. Can you check it?
[OnePlus 3 & 3T Cross Device Development] slipenbois:
Hello guys,

i have this weird bug i try to fix since i flashed lineageos 16.0

Home and recents button stop working after some time on oneplus3:

https://gitlab.com/LineageOS/issues/android/issues/358#note_157147932

What i have try

factory reset + wipe data/cache/dalvik

Format everything and reflash with twrp

Change opengapps to pico.

the bug always come back.

The buttons rework after some time (5/10mn) since the last update. (20190405)

I want to try this, but maybe there is a different command for 16.0

https://xdaforums.com/oneplus-x/help/lineage-os-14-1-home-recents-button-t3611964

Thx for your help i'm starting to be a little desesperate...

I provided a logcat in the issue report and can post a bug report if necessary
[OnePlus 3 & 3T Cross Device Development] FlakeCannon:
Negative. The latest build still does not pass SafetyNet unrooted which is needed for GooglePay. Any chance this might be fixed soon?

Thanks!
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I doubt it:

"Our official stance is that we will not intentionally circumvent an integrity check that Google has put in place for app developers."

https://lineageos.org/Safetynet/
[OnePlus 3 & 3T Cross Device Development] Dirk:
As Bill said, the fact that the ROM used to pass Safetynet out of the box meant, by LOS standards anyway, that it was broken. So you could say that they have fixed it now!

So if people could stop asking when it will be fixed, that would be great. You should of course be asking if it could be broken again, as that would benefit a lot of people. :p
[OnePlus 3 & 3T Cross Device Development] FlakeCannon:
I read the previous replies but I think my misunderstanding was that this is intended functionality. It sucks, but it is what it is. Thank you for clarifying.
[OnePlus 3 & 3T Cross Device Development] Dirk:
I think they intentionally fixed what was previously, accidentally broken. It's got a lot of people through the period where most of the other ROMs were running Selinux Permissive, making Safetynet out of the box impossible. Now it's swung the other way, leaving LOS as one of the only ROMs that doesn't do it. Yeah, it sucks. Maybe they'll accidentally un-break it again. Or un-fix it. Hell, even i'm getting confused with the terminology now! :D

No reason not to try the last Caesium Kernel though. I know development stopped but it will still be fine. Or any of the others.
[OnePlus 3 & 3T Cross Device Development] :
Another drama :good::good::good:

I'll just put this before some angry guy coming (which i predict it will happen regardless)...
[OnePlus 3 & 3T Cross Device Development] ceanth:
Thanks, I figured it out in the end. It was to do with the notification sounds, the default sound is Argon (or something like that) but the actual sound was linked to another sound which was the music which I mentioned.

So even though it was displayed as one, the notification sounds were something else. I fixed it by reselecting the default sound.

---------- Post added at 08:25 AM ---------- Previous post was at 08:24 AM ----------

I am using Caesium and Google pay works fine for me, used it this morning on the tube.
[OnePlus 3 & 3T Cross Device Development] cgirerd:
Just wanted to deliver a huge thank you to the devs. Was looking for a nice phone that could have a chance to have a long term support, and looks like this one is still very active :)
[OnePlus 3 & 3T Cross Device Development] unimke:
I discovered an issue. If I have the mobile data set on sim 2 and I reboot my device, it goes back to sim 1. Anyone else notice this?

Mobile data sim preference does not stick after a reboot.
[OnePlus 3 & 3T Cross Device Development] Oyorf:
Sorry for not knowing, but does this mean that there is no way to pass safetynet with newest builds of LOS16? Or does this only mean that you need to have Magisk Manager installed to be able to pass safetynet?

I have OP3 and LOS16 nightly from 15.3 and it is working fine. But just wondering that should I just stay on this or if I update it will broke safetynet completely and even magisk is not going to help me?
[OnePlus 3 & 3T Cross Device Development] Dirk:
Custom Kernel or Magisk.

The Kernel alone will do it 100%, easy peasy. If you are going to use Magisk i'd advise using both as Magisk alone isn't always 100%.
[OnePlus 3 & 3T Cross Device Development] Pablo.x:
I'm running stock kernel with lastest magisk canary and I've used GPay succesfuly a few days ago...
[OnePlus 3 & 3T Cross Device Development] Dirk:
Edit: Sorry, that didn't come out the way i meant it to. Let me try again:

There are builds of Magisk that are better than others, and there are people who are more experienced with configuring Magisk than others. Because of this, passing Safetynet with Magisk alone can be hit and miss. It seems like the newest builds of Magisk have got on top of the situation again, but this can of course change.

Using a Custom Kernel is 100%, but if someone needs Magisk for other things, i'd recommend using both. One thing that nobody in their right minds should ever consider is using Magisk just to pass Safetynet. That would be like jumping onto a Tiger in the hope that it will save you from the Wasps. :)
[OnePlus 3 & 3T Cross Device Development] DarkSJ1998:
It sets to SIM 1 only after the 1st reboot. After the 1st reboot, the setting would stick. This happens to me on almost every ROM that I've tried till date. Happened on LOS16.0, happened on OOS 5.0.8 too.
[OnePlus 3 & 3T Cross Device Development] ceanth:
Are there periodic stable builds of LOS 16 or is it just nightly? Does everybody install every nightly build?

Also where can I find release notes for our device?
[OnePlus 3 & 3T Cross Device Development] DarkSJ1998:
1. Nope, no periodic 'stable' builds, only 'Nightly' builds.

2. Nope, it's your personal choice to install the Nightly builds. Some flash them daily, some weekly, some monthly & some even don't [emoji14]

3. Official Changelog Page :-

https://download.lineageos.org/oneplus3/changes/

You can track the changes here & then decide if the newer build is worth upgrading to or not :cowboy:
[OnePlus 3 & 3T Cross Device Development] ceanth:
Cool thanks. I remember the old Cyanogenmod days you had a periodic stable build.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
You can also get to the list of changes from the download page.
[OnePlus 3 & 3T Cross Device Development] qhsusb_bulk:
Yep you remember right. There were snapshot builds which got updated montlyish.
[OnePlus 3 & 3T Cross Device Development] gruntyoldbag:
Photos attached to SMS (MMS) messages was fussy on the last 3 major versions of CyanogenMod and has been fussy on all versions of LineageOS.

No one seems to care about SMS messaging anymore - or not enough to fix it.

I hate it when I send MMS messages to other people.

They don't understand why my messages looks so bad - when I have told them that I am running the latest and the greatest version of Android.
[OnePlus 3 & 3T Cross Device Development] Calum 2:
I can't say for certain, but I'd imagine that the app you're using, or you carrier, is responsible for the compression. Not your rom.
[OnePlus 3 & 3T Cross Device Development] gruntyoldbag:
I can not believe that.

I have had several carriers through out the years and photos has been fussy on all of them.

I just tried sending a 1,3 MB photo to myself.

It get compressed to 43 KB - no wonder it is fussy.

And a 2.13 MB photo gets compressed to 114 KB.

As far as I know, the limit lies within the (standard) SMS app.
[OnePlus 3 & 3T Cross Device Development] Calum 2:
Try a different app then.
[OnePlus 3 & 3T Cross Device Development] wojtek007pl:
Hello, how is sot on this rom, and how it is compared to stock oreo? Can you use oxygenos camera with this rom with full functionality?
[OnePlus 3 & 3T Cross Device Development] Shreeram02:
Is this normal

Single core seems to be normal but multicore...
[OnePlus 3 & 3T Cross Device Development] Calum 2:
SOT is fine. A little less than I was getting with Sultans LOS14 but that could be caused by a plethora of things.

No idea on the OOS camera. Down load it and try.
[OnePlus 3 & 3T Cross Device Development] questionquince:
Very satisfying. On April 12 build, i got great SOT just for text messaging, browsing and social media (no gaming).
[OnePlus 3 & 3T Cross Device Development] thetoolmaker:
Flash HavocOS OOS Camera and Gallery:

OOS Camera and Gallery
[OnePlus 3 & 3T Cross Device Development] bian_ki:
Bluetooth

With current 16.0 build I can't use Bluetooth on 3T.

I don't see my audio devices when searching for them and previously added ones have disappeared.

Upd: forget this, seems Bluetooth is working somehow.
[OnePlus 3 & 3T Cross Device Development] :
Can I assume that autoflashing ota on a setup on encrypted f2fs with secured boot (aka boot passphrase) is working for everybody, now? Or does it only work with "default_password" (aka no boot passphrase set in rom when setting lockscreen passphrase)?
[OnePlus 3 & 3T Cross Device Development] sandeep_kumar:
I generally do not set boot password but I use the PIN on lock screen. In that case OTA worked fine for me with encryption and F2FS data partition.
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
No, for me it does not. :(

TWRP does not ask for the lockscreen passphrase so it can't access the filesystem.

When I powercycle the device, TWRP does ask for lockscreen passphrase, but I (of course) manually have to start the update procedure.
[OnePlus 3 & 3T Cross Device Development] :
May I ask you to try with boot passphrase set, please? Is autoflashing still working? Thanx in advance.

May I ask you to remove your boot passphrase, please? Is autoflashing starting to work? Thanx in advance.
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
Yes of course.

I tried it right now and there's still the same error: Error installing zip file '@/cache/recovery/block.map
[OnePlus 3 & 3T Cross Device Development] Doc Sniper:
[MENTION=4405529]nvertigo67[/MENTION]: I can confirm that this OTA bug still exists. I have a pattern encrypted f2fs /data partition and OTA updates are not working like expected.
[OnePlus 3 & 3T Cross Device Development] vinoxflame:
just tested and OTA works for me. I'm encrypted with ext4 filesystem but I don't have any security code or passphrase
[OnePlus 3 & 3T Cross Device Development] ParadiseCity1986:
Camera keeps stopping

Hello,

i have a strange 'Google Fotos Bug'

When i open Google Fotos (to view my photos - and backup my fotos to google fotos) it says 'Camera keeps stopping' after a few seconds. And Google Fotos is closing.

When i take photos with my google camera there is no problem, and no errormessage.

Only as soon as i open Google Fotos i´ll get this errormessage again and again. i can´t really use google fotos.

I think as if it had worked fine from beginning of LineageOS 16 on my OnePlus 3T and that this problem came with an update but it has not gone since.

I´ve already cleared the caches (in the system and the cache in TWRP) but the problem still exists.

Do you have an idea, what i can do to fix this problem?

(btw: by flashing LineageOS16 to my OP3T i´ve also flashed the opengapps: open_gapps-arm64-9.0-aroma-20190316.zip
[OnePlus 3 & 3T Cross Device Development] Imnoa:
Same here, using opengapps pico
[OnePlus 3 & 3T Cross Device Development] :
Please read the thread. We allready know that the autoflashing issue only occurs on encrypted f2fs.

Anyway: I highly doubt, that the fix https://review.lineageos.org/c/LineageOS/android_device_lineage_sepolicy/+/244801 will be merged some day.

Frankly, I don't care anymore. I've found the reason. I've pushed a patch. But since some people claim it's working with encrypted f2fs, los bosses will not accept the fix. The next step would be, to compare working f2fs encrypted working setups with f2fs non-working setups en detail. This would imply to start again asking for detailed setup information. I'm so tired about begging for information over and over again, that I'm out of solving this.

I'd suggest making a small magisk module injecting these two sepolicy rules. The people, who are suffering from auto-flashing failure can use it, all other users on encrypted f2fs with working autoflashing don't need it. Since I'm not even using OTA updates, someone else can jump in here and make the magisk module.

Try installing no gcam and fotos as user app. If fotos is working then, install a gcam port as user app. If you try different gcam ports, don't forget to delete fotos' data and cache on each gcam switch.

BTW: I'd recommend to use nano or pico, and install all other needed gapps as user apps from playstore.

EDIT: if all of the above fails, increase log buffer to 4 Mio, reboot, reproduce the fotos' crash and get a complete logcat.
[OnePlus 3 & 3T Cross Device Development] ParadiseCity1986:
Thanks for your fast reply!

For that i probably have to wipe all and to reinstall everything new, right?

Or is deleting gcam and fotos and reinstall as user app (from playstore?) also possible?
[OnePlus 3 & 3T Cross Device Development] Doc Sniper:
Too bad to read this, because my system definitely has this problem, even though it has been newly setup.

I formatted my system to f2fs with "twrp-3.2.3-10-oneplus3.img" and after that installed "lineage-16.0-201904XX-nightly-oneplus3-signed.zip" and enabled encryption (with pattern lock).

So with a recent installation OTA on f2fs is failing.
[OnePlus 3 & 3T Cross Device Development] :
If you know what you are doing, and how aroma settings translate to addon.d scripts, and how to remove the apps now installed as user apps from g settings db, there's probably a way by formatting system and reflash pico or nano - I don't know enough of gapps and gservices and aroma addon.d scripts to find that way. I'd recommend a clean flash.

You don't need to convince ME - I am. This fix hasn't been merged - or even commented, for that matter - by the los bosses when our line of argument was clear. After this posting we have no line of argument any longer. Though I belive that's a false positive, the effort to find either the reason for the false positive, or - otherwise - the reason for the different expirience, is too much. Even if I would be willing to beg for information many hours again, it may not be merged anyway. Please understand, that - for me - it's not worth the effort.

Making a magisk module injecting two sepolicy rules can't be too hard - even for somebody learning magisk modules with this task it takes less time, then the above (which is worthless, anyway, if the fix won't be merged).
[OnePlus 3 & 3T Cross Device Development] :
Just point them to your build, i'm sure you're already merged it and it's working fine :good:

So it's not there for nothing. Official always be official on fixing things. We cared about our device, while they cared about the whole device they supported. Both in different prospective.

The people who got the problem then must choose to go dirty on unofficial or stay official for whatever reason we don't cared :p
[OnePlus 3 & 3T Cross Device Development] Dirk:
That's not a false positive though. ersandeepkr previously stated not having On-Boot Security, whereas sniperle specifically stated that he did. (The latter was failing OTA). It seems the only difference between working OTA and non-working OTA on Encrypted f2fs is the presense, or not, of on-boot security. I've searched the thread and this seems to be a consistent factor.

Anyway, i understand your frustration with the issue. There's only so much you can do.

---------- Post added at 17:58 ---------- Previous post was at 17:40 ----------

Another thing to learn from this. Anyone whose OTA is failing have at least secured their phone properly. The rest of us are idiots! :p

At best you could say we like living dangerously. Though, being Encrypted without on-boot security is like putting a padlock on a door but never actually closing it.
[OnePlus 3 & 3T Cross Device Development] :
Hoped that, too! Sadly, it happens for some usrers without secured boot: https://xdaforums.com/showpost.php?p=79335114&postcount=1726 fff.

Getting logs, comparing them line by line and comparing each and every single detail from bothe setups (working vs. non-working) is the only chance to get to the ground.

Most proberly it's just a little misunderstanding and/or misread question (like the user telling me that auto flashing works for ext4) resulting in a report that's most probable false positive (most probable, because from the logs I've examined so far, sepolicy is preventing the generation of the needed files on f2fs encrypted; and we have no confirmation of a working autoflash on f2fs encrypted without secured boot: see link above). But I maybe wrong... who knows...

[MENTION=9350973]All[/MENTION]:

The debugging process is well documentated within this thread, including how to generate the logs just before the rebbot, as well as the log lines to look for. Theoretically everybody can start collecting the needed information - it doesn't need to be me...

EDIT: [MENTION=1763460]Dirk[/MENTION]: the rom youmare refering to doesn't offer ota of any kind: https://github.com/nvertigo/android_vendor_nlos/commit/6b8409936e7f648e68a892bece360158e94b8b33

---------- Post added at 19:07 ---------- Previous post was at 19:00 ----------

Wise words! Perhaps people think the hardware accelerated encryption/decyption is like a muscle and shrivels if not used... ;)
[OnePlus 3 & 3T Cross Device Development] Dirk:
Perhaps [MENTION=8530490]Not-Aus[/MENTION] could confirm specifically what file system he uses? Also, after removing boot security, was the device rebooted once or was the OTA tried immediately?

If someone is clean installing soon and wants to run the definitive test, it would be very easy.

(f2fs for file system).

1) Download an older LOS build.

2) Clean Install.

3) Set Boot security during initial setup.

4) Try OTA.

Compare to:

1) Clean Install same older build.

2) Do not set Boot security during setup.

3) Try OTA.

Run test as many times as you like. If on-boot security is the factor it should become readily apparent.

Edit: Ultimately this issue can be added to the list of reasons why people should just format in EXT4 like the rest of us normal people! :D
[OnePlus 3 & 3T Cross Device Development] :
As far as I remeber, he has already. But I'm too lazy to search. That's the problem with collecting the necessary information... ...after some time you feel lile a search engine robot...

That's a good point.

Oh, my friend, I thank you for that testing plan!!! I havn't had the balls to ask for a clean flash just for testing purpose... Let's see how many users report back on that.

May I add: getting each time a complete logcat from starting the update to the reboot, would be great!

Absolutly! I wonder if f2fs should be removed from fstab and only support ext4 rom wise. But as l9ng as the rom is shipped with f2fs support it should be fully supported. Shipping with f2fs possibility, but not supporting it completely (technically as well as here in the thread) is somehow lame... ...especially when considering that encrypted f2fs is what most users get, if changing from oos to los... Just some thoughts, I really don't know if droping f2fs is the solution.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
In my previous tests, with or without boot passphrase, OTA updater had failed on encrypted f2fs.

==> dropping f2fs for ext4 has been the solution... at least for me. ... like the rest of us normal people ... :)
[OnePlus 3 & 3T Cross Device Development] Dirk:
:highfive:

There is a new TWRP build, (3.3.0-0), on the Official Website.

https://dl.twrp.me/oneplus3/

Nothing in Changelog though. :rolleyes:
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
I just flashed the new recovery (twrp-3.3.0-0-oneplus3.img) ... and no sweat (encrypted ext4) ... !

==> https://dl.twrp.me/oneplus3/twrp-3.3.0-0-oneplus3.img.html

NB: OTA updater works fine on TWRP 3.3.0-0 and encrypted ext4 ... :D
[OnePlus 3 & 3T Cross Device Development] Dirk:
:D

You were off the blocks faster than Linford Christie! Well, we won't know if they did something stupid like adding new stuff to 3.2.3-1 until someone tries to Format using it. Ideally this is just 3.2.3-10 with a new name, but seeing as how the new build has rolled out to several devices i'm guessing this is one of those times where they wanted to add something new to all builds. I think i'll stick to the downstream builds personally until finding out what 3.3.0-0 actually is!
[OnePlus 3 & 3T Cross Device Development] Calum 2:
Just fuel for the fire. I haven't updated in a couple of weeks but the last time I did the OTA failed.

F2fs, twrp linked in OP, Los root, encrypted but no boot security / only the login security.

I really should just reformat to ext4, as suggested...

Same. Without a change log I'm not touching that with a ten foot pole.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Do not update TWRP .... read this post : https://xdaforums.com/showpost.php?p=79343413&postcount=547

I just downgraded...
[OnePlus 3 & 3T Cross Device Development] Calum 2:
My schedule is about to open up enough that I'll have time to fix things if something goes wrong. I'm on f2fs presently, what do you guys want me to try? I'm not as well versed in this stuff as most of you, but I made it this far and I'm willing to learn.

If you want a logcat of the process failing I'll need instructions on how to make that happen. Is there anything special to do to make the log continue through the boot to recovery process?

---------- Post added at 09:41 PM ---------- Previous post was at 09:41 PM ----------

Thanks!!
[OnePlus 3 & 3T Cross Device Development] Dirk:
Your OTA failed even without on-boot security, so there's no point running the test i suggested earlier. Honestly, if it were me i'd spend that time re-formatting to EXT4 and having an easier life in future! :p

Nice of you to offer though. :good:
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I apologize if my post confused things. There's nothing wrong with using the wipe menus in the latest (3.3.0.0) TWRP. There's no reason not to use it unless you run scripts.

I'm only talking about the Open Recovery Script command wipe system or its equivalent terminal command twrp wipe system.

I've edited my post to make it clear.
[OnePlus 3 & 3T Cross Device Development] :
I'm bored.. NOS hasn't give me any problem... I'll help you guys with OTA problems, hold my beer.

EXT4 Encrypted = Success

EXT4 Encrypted POB = Success

EXT4 /data Decrypted = Success

F2FS /data Encrypted = Fail

F2FS /data Encrypted POB = Fail

No logs from the success results since i'm so lazy to flash root.. no way i know to pull last recovery log without SU, but basically it results in script succeed.

Only the ROM is flashed. If it's matter, i use TWRP-fix3 (not the newest one from dianlujitao), 14apr to 15apr build update.

And because i forget to remove POB when changing FS, i'm forced to format data and starting F2FS with /data decrypted since it messed up TWRP and LOS... (details below)

Logs below is from unsuccessfull OTA flash