yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Oops ... Migrate was written with M in capital letter. So I thought it was the Play Store app.... Sorry [MENTION=6911010]Calum 2[/MENTION] !

About your question: I don't know. I wasn't using secure start-up on f2fs.
[OnePlus 3 & 3T Cross Device Development] :
Then it's really offtopic. I didn't know of a Migrate app, I've thought the recommended method is migration build or migration script (like described here: https://wiki.lineageos.org/signing_builds.html). Sorry.
[OnePlus 3 & 3T Cross Device Development] Calum 2:
I was asking about using the Migrate app with LOS SU, which is off topic in this thread. You were right to call me on. I didn't acknowledge further because I didn't want to add even more clutter to the thread. Instead I thanked your post and dropped the conversation.

[MENTION=4405529]nvertigo67[/MENTION] I appreciate it, but if I see the need to, I can defend myself just fine. I should have asked my question either in a PM if I was looking for Eric's opinion in particular, or in the Migrate thread where I likely would have been told, appropriately so, to read the OP.

:good:
[OnePlus 3 & 3T Cross Device Development] lutherkingmartin:
03/22 break my wifi, mobile phone, data and fingerprint. Go back to 03/14 and no problem.
[OnePlus 3 & 3T Cross Device Development] simmeone:
Has anyone else this issues?
[OnePlus 3 & 3T Cross Device Development] Dirk:
Firmware version?
[OnePlus 3 & 3T Cross Device Development] :
https://xdaforums.com/oneplus-3/one...eplus-3-3t-t3866517/post79148947#post79148947
[OnePlus 3 & 3T Cross Device Development] lutherkingmartin:
5.0.8
[OnePlus 3 & 3T Cross Device Development] :
Missed that - I'm glad you are back.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Mods?

Back to lvl 1 tech support. Keeps me grounded! :)
[OnePlus 3 & 3T Cross Device Development] Calum 2:
DATA f2fs

FW 5.0.8

TWRP 3.2.3.1

LOS 190322

LOS SU installed

No issues here.
[OnePlus 3 & 3T Cross Device Development] Dirk:
That jogged something in my memory. The Aptx codec module was reported by a user on Havoc OS to have killed all of his Radios.

https://xdaforums.com/showpost.php?p=79147363&postcount=6752

Not yet, but if you ever decide to Format using that version of TWRP you most certainly will! :D
[OnePlus 3 & 3T Cross Device Development] Calum 2:
****. I figured the official build would be safest. Thanks for the heads up.
[OnePlus 3 & 3T Cross Device Development] Dirk:
All of the other Official Builds are safe. Just not that one. :)

3.2.3-10 is the latest if you can find a link.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
[MENTION=1763460]Dirk[/MENTION]:

About a customization issue of SIM card:

A color change of SIM card disables the PIN code input screen at restart and the mobile network is not working!

See these posts:

https://xdaforums.com/showpost.php?p=79159967&postcount=1342

https://xdaforums.com/showpost.php?p=79162280&postcount=1347

https://xdaforums.com/showpost.php?p=79167138&postcount=1360

https://xdaforums.com/showpost.php?p=79167814&postcount=1370

Can you help us? Thank you in advance ... :)
[OnePlus 3 & 3T Cross Device Development] Calum 2:
I... I hate having to say this, but I'm not seeing it anywhere. *sigh * Can you share a link? Or better yet, [MENTION=5091734]dianlujitao[/MENTION] would you mind adding it to your OP?

Sorry for being that guy.

Edit: https://androidfilehost.com/?fid=1395089523397907195

I was looking on XDA, google to the rescue.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Installation:

First time flashing LineageOS 16.0 on your device, or coming from another ROM?

Download the zip(s)

Install a compatible Recovery (My unofficial TWRP is highly recommended: https://androidfilehost.com/?fid=1395089523397907195)

Perform a nandroid backup of your current ROM (Optional)

Wipe data/factory reset

Flash LineageOS

Optional: Install the Google Apps addon package

Reboot

Credit : [MENTION=5091734]dianlujitao[/MENTION]
[OnePlus 3 & 3T Cross Device Development] :
It IS in OP!!!
[OnePlus 3 & 3T Cross Device Development] lutherkingmartin:
Thank, I have this magisk module. I will try without it.

---------- Post added at 07:59 PM ---------- Previous post was at 07:57 PM ----------

Thank, I have this module, I will try without it.
[OnePlus 3 & 3T Cross Device Development] Calum 2:
[MENTION=4405529]nvertigo67[/MENTION] [MENTION=9708417]Eric_Lev[/MENTION]

LMAO

I've been searching for 3.2.3-10, of course I should have just read the OP in it's entirety instead of just skipping to the rom download link and heading to the TWRP homepage for that.

Thank you.
[OnePlus 3 & 3T Cross Device Development] Dirk:
I can tell you that it definitely sounds like a problem. :p

Is it when either one or both slots are occupied? Did you try without the SU Addon? Has anyone else had the issue?

Have you tried a full format rather than just wiping? A PITA i know, but could be just the thing. Anything to do with Boot PIN hints at an Encryption problem and the only way to know for sure would be to remove it entirely by formatting and starting again. Just a thought from a lvl 1 (lvl 2 on a good day) tech support.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Only one ...

Of course

See this post: https://xdaforums.com/showpost.php?p=79167831&postcount=1371 ... But [MENTION=1966251]Uqbar[/MENTION] (two slots occupied) comes from 15.1 (unless I'm mistaken).

Yes ... clean install (full wipe + install only build) from a scratch.

Tested on f2fs and ext4 (cache/data)

perhaps lvl 2 ... ;)
[OnePlus 3 & 3T Cross Device Development] Dirk:
Have you tried a SIM card other than your regular one? Perhaps you could borrow another one to try?
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
I'll try asap... Thanx.
[OnePlus 3 & 3T Cross Device Development] cowgaR:
Any recommended kernel that follows LOS commits and has wireguard baked in?
[OnePlus 3 & 3T Cross Device Development] b.roid:
made the switch from havoc to this. nice to be back on official LOS :)

nice to see protected apps back! :good: seems to only work with default launcher though.

very smooth so far. battery doesn't seem to be as good as the other ROMs does anyone use a customs kernel with this?

also how do you get rid of sim 1 in status bar?

anyway to get dark notifications?
[OnePlus 3 & 3T Cross Device Development] Dirk:
When you said previously that you have trouble with the PIN at boot, do you mean that when you set up your security measures during initial setup, i.e Fingerprint+PIN, you said 'yes' to 'protect my phone at boot' when you were prompted? In other words you have on-boot Encryption security....

..or...

..that you have set an actual SIM PIN? i.e under Settings/Security & Location/SIM card lock? Because that sounds like something that could easily be the root cause of your problems. If your actual SIM were locked out because you weren't entering the code it was asking for, it would then disable your Radio, would it not?

Even to my ears that sounds like one of my more crackpot suggestions. Maybe i'm just tired. Still very interested to here if things change with another SIM card in the phone though. Something is nagging my brain that all these things are connected and the common factor is the card itself.
[OnePlus 3 & 3T Cross Device Development] pitrus-:
You have to wait a day or two until the system settles, the battery consumption goes down. It's just like with new cars, while the engines burnes in it uses more gasoline/diesel but goes down after x miles. [emoji16]

Skickat från min ONEPLUS A3003 via Tapatalk
[OnePlus 3 & 3T Cross Device Development] b.roid:
I've already been on it a few weeks now. drains pretty quick and I don't even have gapps installed.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Option 2 : radio disabled because PIN code input screen disabled.

News:

- Tested with one SIM card: PIN code input screen disabled after restarting system ... same issue with the SIM card of one of my sons.

- Tested with two SIM cards: it works ... :) ... Now I know why no such issue for [MENTION=1966251]Uqbar[/MENTION] (two slots occupied).

==> I can also tell you that it definitely sounds like a problem ... Isn't it ? .... [MENTION=4405529]nvertigo67[/MENTION] and [MENTION=1966251]Uqbar[/MENTION]

May I ask someone to confirm this issue?

First, perform a Nandroid backup before testing.

Second:

- Go to Settings … Networks & Internet … SIM cards

- Select SIM slot 1 or 2 ... but use only one SIM card ... not two.

- Change the colour of SIM card … Confirm by OK

- Go back to home page of Settings

- Restart

Question: is the PIN code input screen enabled at restart?

Logs here: https://xdaforums.com/showpost.php?p=79167814&postcount=1370
[OnePlus 3 & 3T Cross Device Development] Dirk:
I think most people change to Pixel Blue or something else otherwise it's the default Teal Green in the Dialer, incall UI screen. I don't use a boot PIN so i'm no help with that part.

When you change color, is that change reflected in your incall UI screen?
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
I don't use a PIN boot, too.

I wasn't clear, I think...

For me, the PIN code input screen is the screen to unlock my SIM card.
[OnePlus 3 & 3T Cross Device Development] :
As already said, the only difference on sim setting's source code from los to nlos (working with one sim) is the topic https://review.lineageos.org/q/branch:%5E.*lineage-16.0.*+pie-msim-ringtones. First I thought ringtone is not related to your issue, but considering your above posting (msim working), it gets much more probable from my point of view.
[OnePlus 3 & 3T Cross Device Development] Dirk:
I'm not sure everybody understood that distinction. It has probably been assumed that it was the regular boot PIN that you've been having issues with, as i don't think it's very common for people to use a SIM PIN any more. I may be wrong, but i've never used one ever!

From a security standpoint you would be much better off setting a boot PIN for decryption even if it means not using a SIM PIN at all. What's the worst that can happen? Someone takes your Phone/SIM and you alert your carrier and they cut it off?

However you cut it, it's definitely bug-of-the-month! (Beats my 'Phone is Starting' bug)
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
To avoid misunderstanding,, a PIN code input screen for me is ...
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
[MENTION=4405529]nvertigo67[/MENTION] and [MENTION=1763460]Dirk[/MENTION] ... Many thanks !
[OnePlus 3 & 3T Cross Device Development] Dirk:
Apparently your phone is a HTC something, circa 2008. That might explain some of the issues you're having! :p
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
My first phone was a HTC HD2 on CM7 (Feb 2009) ... :p

==> https://xdaforums.com/showthread.php?t=1497520

Bye!

E.
[OnePlus 3 & 3T Cross Device Development] unimke:
Just a little thing. We still have the Oreo notification when you plug in the phone, not the pie one.
[OnePlus 3 & 3T Cross Device Development] ciarpame:
In the last days I had an increasing feeling that battery was draining a little too fast, mostly during SOT. I looked at the running tasks and I found an heavy CPU usage by the system Audioserver process, while I was doing nothing audio related. The issue was still there right after a reboot (and I always remove the "start at boot" permission from most apps, including music, video, and podcasts apps)

Before reporting the issue here (and going down the clean flash road), I looked at the log via ADB and I was lucky (I usually look at the log like the average guy looks at the faulty car engine after opening the hood, I just hope it's something obvious) to find a few rows like this:

E HotwordDetector: Invalid or incompatible speaker models. Silent enrollment required.

"Hotword" reminded me that I was having troubles with the Google Assistant, it was ignoring my "Ok Google" requests and I overlooked the issue, since I barely use the Assistant. So I checked again and I realized that the Assistant default language was Italian (my mother tongue, I probably messed with Google Assistant settings in the past), I changed it to English as primary language and Italian as secondary language. This change solved the "Ok Google" detection issue and fixed the Audioserver cpu usage too.

I'm reporting here because may be useful to someone else, it's a niche issue that can only affect people who use languages other than English with Google Assistant (even if the device language is English) and somehow messed with Google Assistant languages and it's not so easy even to realize you have the problem, the battery usage statistics and warnings do not report about a system process draining battery since they are obviously designed to focus on user apps battery usage.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
I had the same problem some time ago and uninstalled Google Assistant.

The default language of my assistant was French and I didn't have the idea of using English as my primary language.

I will test your solution as soon as possible.

Many thanks [MENTION=3986617]ciarpame[/MENTION]
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
OP3/3T on official LOS 16.0 (0319 build) : f2fs vs. ext4

It is now accepted that, EXT4, the current standard filesystem for Android, isn’t as optimized for flash storage as F2FS is, which results in the slower read/write speeds.

Some articles conclude that if you’re looking for a file system that works just fine, EXT4 it is. However, if you prefer speed over stability and being cutting edge, F2FS it is.

So I quickly tested the impact of both formats on LOS 16 using AnTuTu... and I didn't notice any relevant differences.

See below (in French... sorry): ext4 (left) and f2fs (right).
[OnePlus 3 & 3T Cross Device Development] Dirk:
None of the four things i can see is a storage related test. Your heart is in the right place but your benchmarking software is not!

Good real world storage read/write testing might include system restart times, app loading, batch file editing, pure read/write disk tests including sequential and random.

I'd suggest Androbench for one, if you want to try for some more tests, i'd be interested in the result. There is this too:

https://xdaforums.com/showthread.php?t=2697069

Personally after running f2fs for almost two years and then switching to EXT4, i didn't notice any significant difference in daily operation but i did feel there was a slight deterioration in general fluidity.

Edit: While synthetic benchmarks might have their place, most are no better than random number generators. The best tests of this kind are surely those that can be conducted with a stopwatch.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Fully agree with you about the first part of your post... :good:... but I wanted to use the most popular benchmark these days.

The most important thing is the end user's feeling and your feeling as mine is that there is no relevant/significant difference.

I will try for some more tests with Androbench.... If I have time.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Let loose the stopwatch. The difficult part that might take some thought is coming up with good tests. Phone restart times averaged over several runs, time to open and load every app in your Drawer, app install time, .... those tests that expose real world performance.
[OnePlus 3 & 3T Cross Device Development] :
Though I don't give anything on antutu values (speed happens on your fingertips ;) ), to get reliable and comparable results, you need to do at least 5 (more is better, much more is much better) runs in a row for each setup and take the average.

Did you notice that gpu is also increased? This can't be related to userdata's fs. The difference is most probably due to background activities and/or thermal differences. This can always impact your benchmarking: gpu as well as mem(*).

I love antutu for stability testing, and I get regulary values between 166k and 178k.

Keep in mind that f2fs is optimized for small benchmarks. You can trick antutu mem speed with playing around with read ahead pretty good.

Don't overestimate those one time values. And avoid makimg conclusions from them...

EDIT:

(*) bg tasks effect mem much more then graphics... ;)
[OnePlus 3 & 3T Cross Device Development] Dirk:
The thing that really makes me shake my head in disbelief is when a Youtube video describes itself as a Graphics test, and then proceeds to time how long it takes to open and load a game or two. A test that has nothing to do with Graphics and everything to do with nand read speeds. :D
[OnePlus 3 & 3T Cross Device Development] :
Dirk, don't try to watch youtube completely... There are quite some technical videos not tainted by technical knowledge. This "cleaness" doesn't make them better... ;)
[OnePlus 3 & 3T Cross Device Development] Dirk:
Leo was a magnificent beast! I held one and it was both beautiful and scarily large.

On the issue at hand. If you disable your SIM Lock, change SIM color and then re-enable the SIM Lock, does the issue go away? What about disable, change color, reboot, re-enable?
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
[MENTION=3456089]nvertigo[/MENTION]

Also fully agree and, for reminder, I wrote "I quickly tested the impact of both formats on LOS 16 using AnTuTu" ... So very far from an in-depth test.

I performed several runs. Here, RSD of AnTuTu rankings reaches 10 %: a value in agreement with your results.

If I had the time, I would perform more in-depth tests with tables, graphics, etc ... But the ideal would be to have 2 OP3T... :)

[MENTION=4405529]nvertigo67[/MENTION] and [MENTION=1763460]Dirk[/MENTION]

Please, donate me ... :D

[MENTION=1763460]Dirk[/MENTION]

On the issue at hand, I will try asap ...
[OnePlus 3 & 3T Cross Device Development] Dirk:
Can someone tell me if this ROM still displays the 'SIM is HD capable' notification, or was that taken care of?

Thanks.
[OnePlus 3 & 3T Cross Device Development] melasuda:
Is Tesla Unread working for anyone with Nova Launcher? It always crashes for me.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Leo was a magnificent beast ... It's still alive but in a drawer...

If I disable my SIM Lock, change SIM color and then re-enable the SIM Lock, the issue doesn't go away.

Likewise with the procedure "disable, change color, reboot, re-enable".
[OnePlus 3 & 3T Cross Device Development] b.roid:
still there
[OnePlus 3 & 3T Cross Device Development] :
OTA automatic flashing issue

Since the question, why some ussers suffer from this and others not is answered (f2fs fails with the sepolicy denials), as well as why only op3/t suffers from it (other devices show the same issue), it's time to go ahead.

I've made this change:

commit 4c8a55b538dbf51a484b68637e129f00ea185048 (HEAD -> lineage-16.0)
Author: Nvertigo <nvertigo67@gmail.com>
Date: Sat Mar 23 15:54:21 2019 +0100

common: fix OTA auto-flashing with encrypted f2fs.

If userdata is on f2fs and encrypted (OOS stock config for userdata),
neither /cache/recovery/block.map, nor /cache/recovery/uncrypt_file
are created due to theses denials:

03-12 11:14:40.568 1290 1290 W Thread-26: type=1400 audit(0.0:176): avc: denied { getattr } for path="/data/lineageos_updates" dev="dm-0" ino=25753 scontext=u:r:system_server:s0 tcontext=u:object_r:ota_package_file:s0 tclass=dir permissive=0
03-12 11:14:41.575 6803 6803 W uncrypt : type=1400 audit(0.0:178): avc: denied { fowner } for capability=3 scontext=u:r:uncrypt:s0 tcontext=u:r:uncrypt:s0 tclass=capability permissive=0

Without block.map and uncrypt_file the automatic flashing of the OTA
without user interaction fails, and the user needs to manually mount
data, and flash the OTA manually.

Change-Id: I6ecb84e8b730d4c641a8bd8769043dfbfb817b83

diff --git a/common/private/system_server.te b/common/private/system_server.te
index 05f75fa..209b123 100644
--- a/common/private/system_server.te
+++ b/common/private/system_server.te
@@ -7,3 +7,6 @@ allow system_server sysfs_livedisplay_tuneable:file rw_file_perms;
hal_client_domain(system_server, hal_lineage_livedisplay)
hal_client_domain(system_server, hal_lineage_touch)
hal_client_domain(system_server, hal_lineage_trust)
+
+# OTA with encrypted f2fs
+allow system_server ota_package_file:dir getattr;
diff --git a/common/private/uncrypt.te b/common/private/uncrypt.te
new file mode 100644
index 0000000..3ad9604
--- /dev/null
+++ b/common/private/uncrypt.te
@@ -0,0 +1,2 @@
+# OTA with encrypted f2fs
+allow uncrypt self:capability fowner;

Attached you'll find a zip containing a boot image (plain los kernel) with this patch applied.

Can someone with encrypted f2fs do this test, please:

unzip ota_fix_boot.zip and place the contained boot.img on the device

boot to twrp

take a nandroid, dirty flash yesterday's (or older, but NOT today's build)

flash boot.img and wipe caches

reboot to system

Try to update via OTA

report back, please
[OnePlus 3 & 3T Cross Device Development] melasuda:
Also the Gallery app is heavily bugged. When opening it and going to the "albums" tab and "timeline", no images appear.

Any fix for this?
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Gallery app is not bugged! ... It works very fine.
[OnePlus 3 & 3T Cross Device Development] Milka78:
No problems here...

Last official LOS

Nova prime
[OnePlus 3 & 3T Cross Device Development] :
Storage permissions granted?
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Please, could you test the zip of [MENTION=4405529]nvertigo67[/MENTION] ?

==> https://xdaforums.com/showpost.php?p=79181764&postcount=1443

Thank you in advance.

---------- Post added at 17:38 ---------- Previous post was at 17:33 ----------

Please, could you test the zip of [MENTION=4405529]nvertigo67[/MENTION] ?

==> https://xdaforums.com/showpost.php?p=79181764&postcount=1443

Thank you in advance.

PS: you can use Disk Info (Play store app) to check the file system of cache & data.

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

Please, could you test the zip of [MENTION=4405529]nvertigo67[/MENTION] ?

==> https://xdaforums.com/showpost.php?p=79181764&postcount=1443

Thank you in advance.
[OnePlus 3 & 3T Cross Device Development] Calum 2:
I'm about to leave to pick up my wife and kids from the air port. My spare time is about to reduce drastically, back to normal. Sorry man. I don't like testing new things unless I have a couple of hours to repair my phone if things go wrong. Like yesterday when I tried to flash TWRP 3.2.3-10 via the TWRP app and ended up loading drivers onto my computer and flashing via fastboot. A ten minute process if you're familiar with it. A two hour process if you have to good every instruction to figure out what it's actually saying.

I do appreciate what you guys are trying to do, and that's it's directly helping me. If you'd asked yesterday I'd be all over it. As it is I updated from Sultans unofficial LOS14 straight to LOS16 because this was the first time that I felt comfortable taking the risk due to time constraints.

Sorry, man.
[OnePlus 3 & 3T Cross Device Development] Syssx:
I've tried this.

I was already on one of the older builds, so I've just went ahead, backupped my system and boot and flashed it.

OTA worked like a charm. I just pressed "install" and everything went smooth automatically.
[OnePlus 3 & 3T Cross Device Development] :
Thanx!

https://review.lineageos.org/c/LineageOS/android_device_lineage_sepolicy/+/244801
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Many thanks [MENTION=4405529]nvertigo67[/MENTION] (IP) for this great job ... :good:

---------- Post added at 23:02 ---------- Previous post was at 22:59 ----------

Many thanks [MENTION=5396529]Syssx[/MENTION] !
[OnePlus 3 & 3T Cross Device Development] GTRanushka:
Dark Notifications

+1 Dark/black notifications would be awesome
[OnePlus 3 & 3T Cross Device Development] OTAx1:
Flashed boot.img confirmed working. Had to reinstall Magisk before OTA update was successful. :)