yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] :
Does anybody know, what's considered "system" in the settings ui's caculation? My settings say 7.7 GB, but:

oneplus3 / # df -h /system
Filesystem Size Used Avail Use% Mounted on
/dev/block/sde20 2.8G 1.4G 1.3G 52% /system
oneplus3 / #

Without knowing exactly which directories are added (7.7 GB - 1.4 GB = 6.3 GB) , and therefore belong to settings ui numbers, comparing these numbers are just that: meaningless numbers...

On the other hand: if we know, which directories/files are counted as system, we can easily get to the reason, why we have all different numbers in settings.
[OnePlus 3 & 3T Cross Device Development] morphvale:
Do you have any backups taken in TWRP?

I've noticed before that I had backups in /data/media/TWRP instead of /data/media/0/TWRP

This caused System to show up as aprox 16Gb instead of 8 or so. Deleteing (or moving) the TWRP folder to /data/media/0 should fix the issue if this is the case.
[OnePlus 3 & 3T Cross Device Development] :
livedisplay color profile issue

To all users suffering from this issue:

Can you confirm you have the device encrypted and passphrase secured?

If so: unset the secure boot option (reset your lockscreen passphrase and answer no, if asked if the boot up should be secured) and try if modes are sticking.

For me it's reproduceble:

Passphrase on: issue present; passphrase off: color profile work as expected.

[MENTION=1763460]DirkGently[/MENTION]: you are right, it's one of those... ...everthing is connected to everything - or at least to encryption... ;) ;) ;)
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I've often set a password without also setting the secure boot password and I've never found it to unset the existing boot password.

I've just tested it again by setting a new password (different to the on boot password) and the on boot password remains.

In fact I've not found a way to remove the on boot password (other than reformatting /data).
[OnePlus 3 & 3T Cross Device Development] Nassi:
[MENTION=5091734]dianlujitao[/MENTION]: Would you mind to add MCC 262 and MNC 001 to the VoLTE list (its FCBMobil as Brand of Telekom.de).?Thanks!
[OnePlus 3 & 3T Cross Device Development] Dirk:
Interesting find! I don't use a Boot Pin/Password, just Lockscreen Security, and LiveDisplay sticks.

So it would be the Boot Pin/Password that's causing the issue? If everyone else affected by this can try without it and see if they can get their Presets to stick? :good:
[OnePlus 3 & 3T Cross Device Development] :
I have changed and removed the secure boot password on encrypted /data many times since this was merged: https://review.lineageos.org/#/c/LineageOS/android_frameworks_base/+/217505/

Others have found the bug you are describing fixed, too:

https://xdaforums.com/showpost.php?p=76857617&postcount=2874

Are you really sure, you have checked this on the latest build???

[MENTION=5091734]dianlujitao[/MENTION]: https://jira.lineageos.org/browse/BUGBASH-1587 can be closed. Since the above commit changing and deleteing the secure boot passphrase is fixed. Tested to work with pin, pattern and password on ext4 as well as on f2fs.

[MENTION=535343]all[/MENTION]: That being said, may I kindly ask all users with devices effected by "livedisplay's color profile not sticking"-issue to update to the latest build, and check if this issue persists, if the secure boot passphrase is unset? This is really important to narrow down the issue!
[OnePlus 3 & 3T Cross Device Development] Dirk:
Further to this.. Bugs like this one would usually effect RR and other LOS based ROMs too. The only mention of this in the RR thread was way back in April, suggesting the problem doesn't exist there now. Could Caesium Kernel be making the difference? Someone with the issue could try it and see if it helps.
[OnePlus 3 & 3T Cross Device Development] Doc Sniper:
We should have all Germany MNCs added, especially: 01, 02 and 03

See: https://en.wikipedia.org/wiki/List_of_mobile_network_operators_of_Europe#Germany
[OnePlus 3 & 3T Cross Device Development] S4turno:
Can confirm. Works without boot pin/password.
[OnePlus 3 & 3T Cross Device Development] helderfp:
heavy battery drain on android system, made a clean flash but still the same on latest release.
[OnePlus 3 & 3T Cross Device Development] :
The check I asked for works vice versa, too: you just need to encrypt your phone (non-dedault secure boot passphrase is set then) and the bug will be present, disable password and it's gone again.

It's not kernel related: https://xdaforums.com/oneplus-3/one...eplus-3-3t-t3739169/post76868230#post76868230

I'll check with caesium later today. (Or can I convience you an other way? ;) ) I doubt it's possible to address this issue in the keenel, see my analysis below.

I belive many roms and (livedisplay-enabled-)devices are effected. I'm afraid most people run custom roms unencrypted at all or with default_password for comfortability or scared from some encryption incompatibilities when updating... Or they are just not interested in sortimg out bugs (https://xdaforums.com/showpost.php?p=76885184&postcount=526 ). When discussing security people often tell me: I've gifted my soul to facebook, google and amazon, why should I care about encryption. One might get the impression it's only on one device and only in one rom for very few installations.

I gueess the cause for this is some very sensitive timing in the boot process:

livedisplay stores its settings for color profile in /data/vendor/display/. This is encrypted. If the secure boot passphrase is set to default_password (aka unset) the decryption of data (and therefor /data/vendor/display) is earlier availeble, then with the additional time for interactivly giving a password/pin/pattern.

This would also explain, why the mode is set on the panel: the mpde is changed, after the boot is completed and the sim pin dialog is fired up to the screen. At this time data is sucessfully decrypted, no matter if the secure passphrase is set or not.

[MENTION=5091734]dianlujitao[/MENTION]: I don't know where the livedisplay service is started. Though service livedisplay-hal-1-0 is defined in system/vendor/etc/init/vendor.lineage.livedisplay@1.0-service-sdm.rc, but there's no start livedisplay-hal-1-0 anywhere. I ask because killing vendor.lineage.livedisplay@1.0-service-sdm and com.android.settings after an reboot before opening settings make settings showing the correct profile.

---------- Post added at 15:48 ---------- Previous post was at 15:33 ----------

I can't see the pics (broken, if I click on) and have no info on wakelocks. If timerfd is on top of all(*), a kernel with boeffla_wl_blocker merged will help.

Even if all the wakelocks doesn't sum up to the time of device awake while screen off; if timerfd is wl champion, boeffla_wl_blocker is your friend.

i.e.:

- boeffla

- caesium

- franco

- ...

---------- Post added at 16:45 ---------- Previous post was at 15:48 ----------

Does not work either, if sbppp (secure boot password/pin/pattern) is set.

But I love the naming scheme... puzzling pumpkin (and [MENTION=6552280]MSF Jarvis[/MENTION] explanation) still laughing... Honestly you should admit, you insisted on trying caesium to give me that laugh, not for fixing color profiles... ;) revolting radish...
[OnePlus 3 & 3T Cross Device Development] Dirk:
The naming convention is bonkers! :)

Shame it didn't help, but worth a gamble. So this and the flash photography problem are the big outstanding issues right now. Any others?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Yes, I tested first on 180619 before posting.

I booted up with a boot password but without a lock screen password.

Then I set an on boot password. And rebooted and was prompted for the boot password.

Then I changed my password without setting a boot password. And rebooted and was prompted for both the boot and lock screen password.

I'm on f2fs and I've never decrypted by phone.

I guess this makes my phone "special" :laugh:

PS: I'm just surprised that others can remove the on boot password. But it's not an issue for me as I always set a boot password as it prevents anybody else accessing the data on my phone.
[OnePlus 3 & 3T Cross Device Development] :
:good::good::good: Very true! One should always have a boot password - but if the bootloader is unlocked and a custom recovery is installed, it's absolutly mandatory! If you read my response some postings back, most people give a**** on their privacy....

For your issue: it's not possible to have no paasphrase on encrypted devices. "Unsetting" a password on encrypted devices is in deed impossible. To give the user a way to boot without entering a sbppp, someone had the idea to "fake" a unset password: therefore answering no to the secure boot question when changing lock screen passphrase makes android to set the sbppp to "default_pasaword". This is completely independent from the fs: it's the very same for ext4 and f2fs.

I have checked initial encryption, changing sbppp and "unsetting" sbppp on ext4 asmwell as on f2fs. I'm currently on f2fs with "unset" sbppp (checked that "unsetting" password works from all previous states - I had checked "unsetting" only from pin and pattern, but not directly from password. I wanted to be sure before writing this). (I'll set my sbppp immidiatly after finishing this posting... ;) )

It makes no sense to me, that changing the passphrase to an arbritrary password works, but setting it to "default_password" fails.

Considering all this, I wouldn't say your installation is "special" - I would call this "broken". Keeping in mind you are security and privacy aware (I guess 1 out of 100... ;) ), I would recommend fixing your installation, because if one aspect of a security feature is broken, who can guaranty that all other aspects are operational?

Sidenote on f2fs: compared to ext4 I condider f2fs experimental. At least it's heavy work in progress. Though the f2fs devs try to keep the evolving transparent and forward compatible (i.e. features like xattr are extended in a way, that it can be applied to an existing f2fs filesystem without breakage), but not backward compatible (i.e. if an additional feature of xattr is added once, it can't be removed again). On vendor roms the vendor guaranties (or should guarantee) that the direction is always only forward (for the german speakers: vorwärts immer, rückwärts nimmer). If you look around in custom roms, you'll find many different f2fs backport levels. If using different custom roms on the same f2fs, you can't guarentee the direction for f2fs is always forward. This may or may not have an effect on the running f2fs. In terms of security, reliebility and stability it's mandatory to reformat data if some unexplainable aspects occur.

Sidenote on ext4: regarding proofed security, reliability and stability ext4 is ages ahead (ok, it's only two decades ;) ) of f2fs. In real lifes expirience ext4 is not slower then f2fs (an empty fs is always faster then a filled fs, that's why you hear over and over how fast the device became after switching from ext4 to f2fs).

Bottom line: changing and "unsetting" sbppp is working perfectly fine with ext4 and f2fs since this weeks build.
[OnePlus 3 & 3T Cross Device Development] Doc Sniper:
I have LOS 2018-06-18 and standard partition formats:

/dev/block/sda3 on /cache type ext4

/dev/block/sde20 on /system type ext4

/dev/block/dm-0 on /data type f2fs (encrypted)

Have just tested it again on 2 phones, I can "delete" my pattern then the phone boots only with lock screen pattern. If I set it again, I will be asked at boot to unlock the data partition and later to unlock the lock screen. This works for me since LOS 2018-06-18.
[OnePlus 3 & 3T Cross Device Development] 9Lukas5:
Off topic: I'm running Ubuntu on my main system where I have a ssd as system storage.

I have switched my partitions on the ssd all to f2fs and it made a visible speedup for my system.

Never had any problems with my system, as you normally don't change that often between kernels, it could be considered guaranteed, that you don't get one day a kernel that removed some f2fs features active on the system^^.

I'm just sad that Ubuntu doesn't support f2fs out of the box as filesystem for the installation :/

L
[OnePlus 3 & 3T Cross Device Development] Doc Sniper:
Well, it depends on the Linux distribution, I have F2fs support out-of-the-box, but i prefer BTRFS on my machines ;)

/usr/lib/modules/4.17.2-1-ARCH/kernel/fs/f2fs/f2fs.ko.xz
[OnePlus 3 & 3T Cross Device Development] PlayFriik:
Is there a way to make apps like AudioFX won't be installed automatically?
[OnePlus 3 & 3T Cross Device Development] SpasilliumNexus:
Plenty of ways...

- Build LineageOS from source without it.

- Use a kitchen to extract and rebuild the ROM without it.

- Make an addon.d script which automatically removes it after every ROM upgrade.

- Delete it while in recovery.

- Disable it in App Info.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Is anyone else here on Three UK? I'm trying to figure out whether i could be using VOLTE or not. Currently i don't have the Enhanced 4G option in settings. I know Three support it but officially it's only only on devices bought from them, via software update.
[OnePlus 3 & 3T Cross Device Development] :
Still OT:

Gentoo, about 1600 0ackages; /var/tmp on ssd; distfiles on md-raid-5: rebuild the complete system with ext4 (quotas enabled, xattr enabled, scheduled fstrim once a day - no inline fstrim): ~24h.

With f2fs (no quote, xattr enabled) on /var/tmp: don't know, stoped the test after 40h with about 80% build.

Iozone with 100GB: f2fs is about 30% faster then ext4 on reading and about 20% faster on writing.

iozone with 100GB via nfs on the ssd: ext4 is nearly 10% faster on reads and writes.

This all is bull**** - of course! - f2fs is not designed as server/build-host fs, but the iozones result made me trying it. (Caught in the benchmark trap... ;) )

Let's get back on topic. One of the best writings on mobile fses: https://www.xda-developers.com/f2fs-why-file-systems-matter-interview-stan-dmitriev-tuxera/

BTW: if anyone has a source from oneplus, why they went back to ext4 for their newer models, drop me a link please.
[OnePlus 3 & 3T Cross Device Development] Doc Sniper:
Most people say ISSUES, but nobody really knows: https://www.reddit.com/r/Android/comments/6txvqx/why_arent_android_manufacturers_adopting_the_f2fs/

And I really like this Twitter post:

And because I'm not a grandma, I prefer f2fs ;)
[OnePlus 3 & 3T Cross Device Development] Dirk:
^^ Now, that's how you do a bug report! :good:

Welcome to the forum [MENTION=9259017]h1ghKL[/MENTION]
[OnePlus 3 & 3T Cross Device Development] mk_1996:
[MENTION=9259017]h1ghKL[/MENTION] mention dinalujitao too. It would be easier for him to see. Good bug report mate.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Did you ever get this figured out?

Anybody can answer this... Is the ROM supposed to have the Enhanced 4G and WiFi Calling options in Settings? Are there specific circumstances where they show up or not?

I've read that the following should be in the build.prop:

#ifdef VENDOR_EDIT

persist.dbg.ims_volte_enable=1

persist.dbg.volte_avail_ovr=1

persist.dbg.vt_avail_ovr=1

persist.data.iwlan.enable=true

persist.dbg.wfc_avail_ovr=1

#endif

Can anyone shed some light on this?
[OnePlus 3 & 3T Cross Device Development] Doc Sniper:
According to this thread https://xdaforums.com/apps/magisk/module-v4-volte-enabler-t3649613 the following should be set:

# Debug Options
persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=1
persist.dbg.wfc_avail_ovr=1
# Radio Options
persist.radio.rat_on=combine
persist.radio.data_ltd_sys_ind=1
persist.radio.data_con_rprt=1
persist.radio.calls.on.ims=1

I would love to see VoLTE activated for Germanys MCCs 01, 02 and 03 because all mobile operators in Germany have already enabled it for all users.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Shouldn't the ROM have the Settings already, regardless of Carrier support or not? That's what i can't understand. I know i've seen those settings when setting up a new ROM not long ago, but i can't remember which ROM.
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=9259017]h1ghKL[/MENTION]

I've tried to reproduce on an installation clean flashed 4 or 5 days ago: no freeze, no crash, just everything working flawlessly. Freezing doesn't occur with trebuchet, nor with nova. Can you pull a complete log, when display is frozen?

BTW: I've tried just returning to the allready running instance (I think that's what you descripe in your report), as well as force closing brave and restarting it. Both works out fine.
[OnePlus 3 & 3T Cross Device Development] Doc Sniper:
Yes, I think that would be the way to go.

Copied the above settings (8 lines) to the build.prop and rebooted and now I have new options (see pictures).

But I don't know if VoWiFi is working, because didn't test it and

I don't know why VoLTE is still disabled.
[OnePlus 3 & 3T Cross Device Development] :
Why should they be set? The author of the posting you mentioned clearly states his changes do not work:

I may miss something here, but I can't understand why you suggest to use changes that are proofed not to work.

Sidenote:

if anybody has tried this magisk module or edited build.prop, remember these all are persistent props!!! They will only be removed on clean flashes or if deleted manually.
[OnePlus 3 & 3T Cross Device Development] Dirk:
So nobody on this ROM is using VoLTE? Nobody has the 'Enhanced 4G' option in Settings, right? It's not in the ROM and the build.prop edits don't work?
[OnePlus 3 & 3T Cross Device Development] laupuy:
You can try jamal2367 magisk module OnePlus_3-3T_OOS-OB_VoLTE-VoWiFi_Enabler_v1.0-signed.zip 7.28KB here https://jamal2367.com/downloads/?dir=Magisk Modules

I have a problem with my carrier (because my phone is not sold by sfr, while the option is available in my phone package...). But I have at least the option in Settings :)
[OnePlus 3 & 3T Cross Device Development] laupuy:
One more
[OnePlus 3 & 3T Cross Device Development] Dirk:
I don't use Magisk. Regardless, did you have the setting by default or did you add it with the module?

Do you have the option in Settings? By default, or via Magisk module?
[OnePlus 3 & 3T Cross Device Development] laupuy:
Options are added by the module
[OnePlus 3 & 3T Cross Device Development] :
I could swear I've seen the "Enhanced 4G" in settings - currently it's gone. Others must have seen this as well:

https://xdaforums.com/showpost.php?p=76886969&postcount=528
[OnePlus 3 & 3T Cross Device Development] Dirk:
Good grief, there are layers to this nonsense. From what i'm learning having the option in Settings is purely cosmetic anyway if the carrier doesn't support VoLTE. I don't know if the ROM is detecting lack of support automatically somehow and therefore leaving that option out in those cases. Perhaps the option only appears when full support is known to exist?

Here's what i know about my specific case. I'm on Three UK. The APN Settings i'm using are correct. Three have only activated VoLTE on phones they've sold, with or without contract. Phones like this one that they never sold aren't officially supported. From what i gather it's because they have to load specific software, whether firmware or otherwise i don't know. It could just be configuration files but maybe it's more.

What's more VoLTE only works on 800Mhz which is a band they specifically paid a lot of money for. The phone does 1800 and 800Mhz. For 4G it defaults to 1800Mhz and drops to 3G if that isn't available. There must be something in the software they add that enables the phone to use 800Mhz for VoLTE.

Whatever it is they do to enable VoLTE on their 'officially supported' devices, it must be possible to do the same on a custom ROM, right?

[MENTION=5091734]dianlujitao[/MENTION] Any ideas?
[OnePlus 3 & 3T Cross Device Development] xpissio:
Just for information, OP3 builds have been moved to Tuesday. (https://review.lineageos.org/#/c/LineageOS/hudson/+/218032/)
[OnePlus 3 & 3T Cross Device Development] Doc Sniper:
One more with switches.

With the settings from "OnePlus_3-3T_OOS-OB_VoLTE-VoWiFi_Enabler_v1.0-signed.zip" I was able to activate the switches and settings for VoLTE and VoWiFi.

But I suspect this will not be enough to make it work.

I have also created an APN "ims" as recommended in another thread.

Where should we continue?
[OnePlus 3 & 3T Cross Device Development] Dirk:
How did you activate the switches? build.prop edits?
[OnePlus 3 & 3T Cross Device Development] Doc Sniper:
Yes, I edited the build.prop directly and added the lines that I found in the ZIP (but be aware, one line has two transposed letters).

So far no success, but I keep testing.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Does your carrier support it on all devices or like mine, only on specific devices with their 'special sauce' alterations? Have you found any ROMs where VoLTE worked for you out of the box? There seems to be at least three things needed to successfully get it working:

1) Options in ROM Settings.

2) Full Carrier support.

3) ?

(Where ? is some weird unknown factor. Some magical config, or maybe luck of the draw.)
[OnePlus 3 & 3T Cross Device Development] Doc Sniper:
No, I have not tested any other ROMs, at least OOS would be worth a try.

According to many press releases, Telefonica (O2 Germany) has activated LTE for all devices.

See: https://translate.google.com/translate?sl=auto&tl=en&js=y&prev=_t&hl=en&ie=UTF-8&u=https%3A%2F%2Fblog.telefonica.de%2F2018%2F02%2Fverbesserte-sprachqualitaet-und-erweiterte-netzabdeckung-telefonica-deutschland-schaltet-volte-und-vowifi-fuer-alle-kunden-frei%2F&edit-text=

Edit: Perhaps the last sentence of the quote means that O2 Germany will activate the device for VoLTE only after the manufacturer integrates the necessary VoLTE configuration for O2?
[OnePlus 3 & 3T Cross Device Development] Dirk:
It really seems like you should have it working. I'm almost certain it would work for you on OOS, and maybe in other custom ROMs. For the latter you might have to ask around in the ROM threads or check out some YT videos. What i still don't understand is why you're having to do build.prop edits to make the options appear in Settings. Those options should be there by default, regardless of Carrier support. :confused:

My case is further complicated by the restrictions inflicted by Three on devices bought outside of their control. :mad:
[OnePlus 3 & 3T Cross Device Development] :
I havn't checked the code, but I think it's similar to the ims settings in the phone app: it's only shown, if ims is supported with the current carrier. YMMV, but for me this makes sense. The phone app i.e. has shown ims settings for all on 14.1, but a lot of people were complaining on crashes of the phone app, if they enter imsmsettings. Only show options available on the current setup is a good idea.
[OnePlus 3 & 3T Cross Device Development] Doc Sniper:
Because it is not enabled by default in LOS, only networks that are known to work with VoLTE are enabled. View the file:

https://github.com/LineageOS/android_device_oneplus_oneplus3/blob/lineage-15.1/overlay/packages/apps/CarrierConfig/res/xml/vendor.xml

Can you see your providers MCC and MNC there?

Mine is not there, I need 262/03 to be activated.
[OnePlus 3 & 3T Cross Device Development] :
Me2
[OnePlus 3 & 3T Cross Device Development] Dirk:
You're probably right. I have seen those options when setting up a ROM on my device though. Can't remember which ROM though. What i need to figure out is what specific changes Three UK are making to their 'officially supported' devices to have VoLTE working. I can't see any reason why the same changes couldn't be made to any device to get it working.

---------- Post added at 17:06 ---------- Previous post was at 16:51 ----------

That's weird. I'm not seeing mine either (MCC: 234 MNC: 20)

I do have the preset for Three in the ROM though which has the correct APN settings. :confused:
[OnePlus 3 & 3T Cross Device Development] :
https://review.lineageos.org/#/c/LineageOS/android_device_oneplus_oneplus3/+/218626/