yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] counterfeit187:
Are you saying that one of those adb commands will fix date/time in twrp? My time is always hours off even with correct time zone set and checking daylight savings options. I'm on fix 3. I think I also end up with bad dates in filenames.
[OnePlus 3 & 3T Cross Device Development] :
/vendor is just a symlink pointing to /system/vendor - both arn't related to this. We talk of /data/vendor/time. You need to check ownership, group, unix perms (I think group system needs x) on each of the recursed dirs (/data, /data/vendor) and r and x on /data/vendor/time.

Since ownership amd group are missing from the listing, it's hard to tell.

adb shell su -c "ls -laZd /data/ /data/vendor/ /data/vendor/time"
drwxrwx--x 47 system system u:object_r:system_data_file:s0 4096 2019-02-23 12:37 /data/
drwxrwx--x 37 root root u:object_r:vendor_data_file:s0 3488 1971-12-27 06:37 /data/vendor/
drwx------ 2 system system u:object_r:vendor_time_data_file:s0 3488 2019-01-03 12:08 /data/vendor/time
[OnePlus 3 & 3T Cross Device Development] :
Tried with changing permissions with chmodding /data /data/vendor /data/vendor/time and /data/vendor/time/* to 771 and 777 in twrp.

Then I changed date with date -s "2019-02-25 20:23" (current time) in twrp.

After reboot same issue.

Strange part of it; after reboot rights are changed back to what it was.

Results after reboot, using adb:

adb shell
OnePlus3T:/ $ su
OnePlus3T:/ # ls -laZd /data/ /data/vendor/ /data/vendor/time
drwxrwx--x 41 system system u:object_r:system_data_file:s0 4096 2019-02-25 17:52 /data/
drwxrwx--x 38 root root u:object_r:vendor_data_file:s0 4096 1970-09-14 16:42 /data/vendor/
drwx------ 2 system system u:object_r:vendor_time_data_file:s0 4096 2019-02-19 18:48 /data/vendor/time
OnePlus3T:/ # ls -laZd /data/ /data/vendor/ /data/vendor/time /data/vendor/time/*
drwxrwx--x 41 system system u:object_r:system_data_file:s0 4096 2019-02-25 17:52 /data/
drwxrwx--x 38 root root u:object_r:vendor_data_file:s0 4096 1970-09-14 16:42 /data/vendor/
drwx------ 2 system system u:object_r:vendor_time_data_file:s0 4096 2019-02-19 18:48 /data/vendor/time
-rwxrwxrwx 1 system net_raw u:object_r:vendor_time_data_file:s0 8 2019-02-25 20:15 /data/vendor/time/ats_1
-rwxrwxrwx 1 system net_raw u:object_r:vendor_time_data_file:s0 8 2019-02-24 12:05 /data/vendor/time/ats_12
-rwxrwxrwx 1 system net_raw u:object_r:vendor_time_data_file:s0 8 2019-02-24 12:05 /data/vendor/time/ats_13
-rwxrwxrwx 1 system net_raw u:object_r:vendor_time_data_file:s0 8 2019-02-24 12:05 /data/vendor/time/ats_15
-rwxrwxrwx 1 system net_raw u:object_r:vendor_time_data_file:s0 8 2019-02-25 20:15 /data/vendor/time/ats_16
-rwxrwxrwx 1 system net_raw u:object_r:vendor_time_data_file:s0 8 2019-02-25 20:15 /data/vendor/time/ats_2

But not important; everything is working, so may be I will find it out some day.... ;)

Again, thanks for your support!
[OnePlus 3 & 3T Cross Device Development] DoN LoUhI:
twrp-fix-3 not responsive to touch won't let me swipe..please help
[OnePlus 3 & 3T Cross Device Development] :
Redownload and reflash (fastboot). If that doesn't help flash older twrp versions until it's working again. Flash oreo firmware after you've foumd a working twrp version. After flashing oreo firmware switch to fix3 again.
[OnePlus 3 & 3T Cross Device Development] laupuy:
And/or delete .twrps (twrp settings).

Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk
[OnePlus 3 & 3T Cross Device Development] :
These are the sizes of the userdata partition and the encrypted volume for a 3t with 64 GB:

adler ~ # adb shell su -c "blockdev --getsz /dev/block/sda15"
112477144
adler ~ # adb shell su -c "blockdev --getsz /dev/block/dm-0"
112477112
adler ~ # adb shell su -c "cat /proc/partitions"|grep -e sda15 -e dm-0
8 15 56238572 sda15
253 0 56238556 dm-0
adler ~ #

---------- Post added at 20:14 ---------- Previous post was at 19:33 ----------

@dianljitao:

I've always thought this isn't necessary, because the fix3 changes would be merged straight away and the the problems with a broken "latest official build" would void, but since https://gerrit.omnirom.org/#/c/android_bootable_recovery/+/33021/ is still not merged, and the vast majority of users just use "the latest official twrp", without reading the complete fix3 story, it may be time to consider pulling 3.2.3-1 from the download page and linking fix3 in the OP. Thanx in advance.
[OnePlus 3 & 3T Cross Device Development] blade_:
hello just installed this rom,thanks

how can i go back to white stock theme?thanks in advance
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Wrong thread. This is for TWRP, not a rom.
[OnePlus 3 & 3T Cross Device Development] Chickenbreadlp:
The more I read about Versions, the more I get confused. What's the problem with 3.2.3-0? Is 3.2.3-1 / 3.2.3-1-fix3 really required for Android 9?
[OnePlus 3 & 3T Cross Device Development] DarkSJ1998:
There's no problem with v3.2.3-0, but there's a problem jn 3.2.3-1 (which is still there on TWRP official page).

If you format the /data partition using the 3.2.3-1 to decrypt, you won't be able to encrypt EVER again.

To fix this, [MENTION=4405529]nvertigo67[/MENTION] released a special version of v3.2.3-1-fix3 which is fine AFAIK.
[OnePlus 3 & 3T Cross Device Development] Chickenbreadlp:
I know of the Issues with 3.2.3-1. But there seems to be the misconception, that encryption can't be restored ever again. I've accedently ran into this issue and soft-bricked my phone (couldn't format the encrypted partitions without having the encryption footer). When I used the OnePlus 3T Unbrick Tool, I've somehow restored the encryption footer. Don't ask me how...
[OnePlus 3 & 3T Cross Device Development] :
Nobody stated that that! To restore the footer it's sufficient format via fastboot. I've said: if you use 3.2.3-1 and format data you have permanently removed the encryption footer. This is true for 3.2.3-1. If you use an other way of formatting (manually, other recovery, adb etc.) you can put the space required back - but if you use 3.2.3-1 the encryption footer is gone permanently (no matter how often you format, if you use format data or change fs for data), until you fix it.

Many people in different rom's threads have complained about not being able to encrypt their devices - the standard answer is "format data". This advice works untill you've installed 3.2.3-1 (obviously). So using 3.2.3-1 breaks encryption permanently. At this point additional steps are needed to fix the situation.

The unbrick tool - of course - restores (among many other things) the factory format, which includes - again: of course! - the encryption footer.
[OnePlus 3 & 3T Cross Device Development] cowgaR:
So why not just use official 3.2.3-0

Just withdraw bad version and link previous one. So much noise everywhere about it (Los thread on 5 pages), and requires one minute fix (link old one).

So much for OP3 maintainer, with all respect. If I would screw up my phone encryption I would not be happy indeed.
[OnePlus 3 & 3T Cross Device Development] DarkSJ1998:
Yep that's correct. I've been using the 3.2.3-0 since it's release & have switched back and forth between many ROMs. 3.2.3-0 is completely fine. :)
[OnePlus 3 & 3T Cross Device Development] :
With all due respect, the fix is provided. Why it hasn't been pushed to the official is a different story than you think.

If you get into trouble, i would blame yourself for not reading properly... I would agree to blame him if he doesn't provide a fix.

This whole modification isn't a child plays, from the moment you're unlocking the bootloader means you're asking for trouble.

And the word "never" used by some member is exaggerated, i know it's a language barriers, but the word never is close to impossible/screwed/no turning back, while the fact it's possible to fix the broken encryption

Below me will be another repeated question, and possibly another angry mob... [MENTION=5091734]dianlujitao[/MENTION] seems to enjoy it by just watching it in the shadow :laugh:
[OnePlus 3 & 3T Cross Device Development] knpk13:
As much as I agree with you, I think it's a reasonable request to ask [MENTION=5091734]dianlujitao[/MENTION] to just put a link/note to the fix3 build in the OP so that new people aren't confused and it's easier for everyone. Or people are just going to have OT conversation like this and be mad.
[OnePlus 3 & 3T Cross Device Development] :
I believe It's been asked by others couple of times to put the fix 3 link in the first page though.. i've been following this thread since the whole fiasco with f2fs.

Seems.. he just doesn't want it.

He might say.. -" Just let it burn " :laugh:
[OnePlus 3 & 3T Cross Device Development] knpk13:
I know. And lol he's just busy. He wouldn't do that haha. Editing OP is grunt work compared working on LOS commits (like him fixing DCI-P3 a few days ago) so devs often don't pay as much attention to it. Which is fine, but can clutter up thread with people asking the same question lol.
[OnePlus 3 & 3T Cross Device Development] Anghirrim:
I just realized that I've done the mistake of formatting data under 3.2.3-1 as well (can't encrypt).

So to fix this I am doing the following:

- Flashed OOS 5.0.8 using the fixed TWRP version.

- Flashed the patched boot.img to avoid the dm-verity message.

- Rebooted right away into fastboot

- Formatted with " fastboot format userdata"

- Rebooted with "fastboot reboot"

It has now been 20mn that I am on the OOS boot animation.

Let's cross fingers

Edit: It worked! 25mn to reboot and now phone status is encrypted.
[OnePlus 3 & 3T Cross Device Development] Scorpion70:
is this newer than twrp fix 3 ?? https://androidfilehost.com/?fid=1395089523397907195

which one is the best?
[OnePlus 3 & 3T Cross Device Development] counterfeit187:
well, the one you linked to is uploaded this morning, so yeah that's the newest, but I don't know anything about it so can't recommend switching yet I'm still on fix 3. It could be a buggy test build I don't know how you found it or whatever but I would wait for the developer to say okay
[OnePlus 3 & 3T Cross Device Development] P1nGu1n_:
This is the recommended build by the developer, see this change. This build is now mentioned on the OnePlus 3 LineageOS wiki page.
[OnePlus 3 & 3T Cross Device Development] Scorpion70:
ok, thanks... i found it on lineage os 16 thread by dianlujitao and he mentioned it hightly recommended!
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
For information:

- New highly recommended TWRP on the OnePlus 3 LineageOS wiki page (https://wiki.lineageos.org/devices/oneplus3/install).

==> TWRP link : https://androidfilehost.com/?fid=1395089523397907195

Advertise custom TWRP for oneplus3/jason :

* To reserve crypto footer across format data
[OnePlus 3 & 3T Cross Device Development] BillGoss:
[MENTION=5091734]dianlujitao[/MENTION], there's a bug in the latest TWRP 3.2.3-10 from https://androidfilehost.com/?fid=1395089523397907195 . The wipe command no longer accepts 'system' as an option. It works fine with 'data'.

TWRP log:

I:command is: 'wipe'
I:value is: 'data'
Formatting Cache using make_ext4fs...
...
Wiping data without wiping /data/media ...
I:skipped '/data/lost+found'
I:skipped '/data/media'
I:skipped '/data/misc/vold'
I:skipped '/data/system/storage.xml'
I:skipped '/data/.layout_version'
Done
I:command is: 'wipe'
I:value is: 'system'
E:Error with wipe command value: 'system'

I've been using the "wipe data|system" for quite a while in my scripts.
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
Probably a regression after upstream patch https://github.com/omnirom/android_bootable_recovery/commit/9d6feb53115e2dcc49a644400da4d62a16c1c3c6 , as I rebased my format fix on top of latest twrp source and that one didn't exist before

wipe system from gui works well
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Thanks for that. I hope they fix it or at least explain what values they expect because it's broken my installation scripts.

Yes, the GUI works, but I'm guessing that doesn't use the TWRP built-in wipe command (in terminal: twrp wipe system).
[OnePlus 3 & 3T Cross Device Development] faboz84:
nandroid restore

Hi folks,

have you ever had problems restoring a nandroid backup with pin (and fingerprint) encryption?

Is it the safest procedure or i should disable the pin encryption before making a nandoid backup?

Thanks in advantage
[OnePlus 3 & 3T Cross Device Development] :
No problems on my side doing/restoring a nandroid backup of the encrypted (with pin) data partition.

My data is on ext4
[OnePlus 3 & 3T Cross Device Development] faboz84:
Thanks for your feedback; i'm asking this because once i couldn't boot the OS. Now i've flashed the latest TWRP version and hope this has been fixed.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Define "latest". Latest Official from TWRP website? You don't want to use that. 3.2.1-0 works perfectly for me but the latest is 3.2.3-10.
[OnePlus 3 & 3T Cross Device Development] pedritopl:
If You mean that PIN is not accepted after restore then that's normal. You have to manually remove a few files on the FS from inside TWRP after restoring the backup. Just Google it and You'll find the details.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
My config: full wipe + clean install / last current build / Open Gapp nano / official LOS addon SU / FW 5.0.8 / TWRP 3.2.3-10 / encrypted data

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

Nandroid Backup in every case and no problem.
[OnePlus 3 & 3T Cross Device Development] :
If you use 3.2.3-1 for formatting data the encryption footer is removed. If you try to boot a rom with forced encryption (like oos) it can't complete the first boot, because i can't encrypt data any more.
[OnePlus 3 & 3T Cross Device Development] faboz84:
damn.. i'm on twrp-3.2.3-1-oneplus3.img - I'm gonna upgrading it with the link provided few posts before. thx again

---------- Post added at 05:10 PM ---------- Previous post was at 05:08 PM ----------

no...worse. the rom didn't boot. i never had problems before with other smartphones in several years

---------- Post added at 05:14 PM ---------- Previous post was at 05:10 PM ----------

i'm moving to 3.2.3-10 - in this specific case i would like to make a nandoid backup to restore for any inconvenience.

By the way what do you mean? i shouldn't format /data via TWRP? i did this when i switched to NitrogenOS
[OnePlus 3 & 3T Cross Device Development] :
If you have used 3.2.3-1 for fprmatting userdata the encryption footer is removed. oos is forced encrypted (this means, that oos tries to encrypt an unenfrypted userdata partition on boot). If there is no space on userdata reserved for encryption footer that doesn't work and the rom can't boot.

3.2.3-0 will format userdata with encryption footer. 3.2.3-10 will only preserve the space for encrypton footer, if it's present - if no encryption foozer is present, 3.2.3-10 will not create a new one.

To get the encryption footer back, use 3.2.3-0 or format with fastboot.

Once you have the encryption footer back, 3.2.3-10 is highly recommended..
[OnePlus 3 & 3T Cross Device Development] faboz84:
In the past i used the twrp-3.2.1-0-oneplus3.img to format /data ...i've been lucky or not?!
[OnePlus 3 & 3T Cross Device Development] :
Magenta says: "You are lucky. He is lucky. I'm lucky. We're all are lucky." [1975, Jim Sharman, Richard O'Brian]

nvertigo67 says: "Go directly to 3.2.3-10 - by any means skip 3.2.3-1, and you'll stay lucky, no matter if you decide to format useradata." [2019, nvertigo67]

:)

SCNR
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
It depends on several parameters: encrypted data or not, ext4 or f2fs formatting, ROM ... and so on.

A word of advice: read this thread and this one (https://xdaforums.com/oneplus-3/one...ment/rom-lineageos-16-0-oneplus-3-3t-t3866517). You'll see that [MENTION=4405529]nvertigo67[/MENTION] gives very good explanations and advice.

And if you want to save time:

- Backup your personal data and your app (e.g. Migrate - https://xdaforums.com/and...-tool-t3862763)

- Perform a clean installation (full wipe in ext4 or f2fs format of cache/data – install your ROM, Gapp and SU) then re-install your app and personal data

==> It is not time-consuming ... between 15 and 30 min max.
[OnePlus 3 & 3T Cross Device Development] Dirk:
3.2.1-0 has always worked perfectly for me. I used it for all my Oreo needs and yesterday, to clean install with format data (Ext4), with Pie.
[OnePlus 3 & 3T Cross Device Development] Dheeraj Menon:
I am on an locked bootloader OnePlus 3 running on OOS 5.0.8 and I wish to flash a custom ROM

Can someone give me links and steps I need to follow to ensure that I don't have any problems while I am at it
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Installation instructions:

==> https://wiki.lineageos.org/devices/oneplus3/install

and

a suggested custom ROM (official LOS 16.0) :

==> https://download.lineageos.org/oneplus3

XDA Thread: https://xdaforums.com/oneplus-3/one...ment/rom-lineageos-16-0-oneplus-3-3t-t3866517

Good flash!
[OnePlus 3 & 3T Cross Device Development] Dheeraj Menon:
Thanks a lot for the help
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Do not forget to perform a full wipe in recovery mode before installing ROM, gapp and SU (if you wish it).

Reminder: TWRP 3.2.3-10 supports Decrypt /data and f2fs

So, you can choice to format cache and data in f2fs via "Avanced Wipe" .. if you want.

Some good reads .....

https://www.xda-developers.com/clea...-and-op3t-storage-speed-differences-and-f2fs/

https://www.xda-developers.com/oneplus-3t-xda-review-what-has-changed-and-by-how-much/
[OnePlus 3 & 3T Cross Device Development] Sylverfalcon:
Hey guys, it's been a while i haven't updated my phone and i wanted to do it again this weekend, but i'm kinda a bit lost. I've been reading the last few pages and saw the new twrp version (the 3.2.3-10).

So i just wanna check before doing any mistake: Will i be able to follow the guide "[GUIDE] OnePlus 3T: How to Unlock Bootloader | Flash TWRP | Root | Nandroid & EFS Backup and More !!" on Oneplus forum (can't post links, sorry :( ) without any issue using this twrp version? I mean, with the dm-verity and forced encryption disabler specified in the guide especially, or do i need another one.
[OnePlus 3 & 3T Cross Device Development] Paschfire:
Nope, you should be good to go. :good:

May I also note that guide is very outdated.

The information provided within is still relevant, just make sure to search out for newer version of zips/files shared within it.

You should check out the main DM-Verity thread for further information on that subject.

https://xdaforums.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748/page73
[OnePlus 3 & 3T Cross Device Development] Sylverfalcon:
Thanks !

I'm gonna follow this post then, with the one you provided and the last twrp :)

Edit: Worked perfectly with the post you provided and the one i linked. Wow, feels like a new phone ahah Thanks !
[OnePlus 3 & 3T Cross Device Development] zoneofSAM:
Which version should i flash for OOS 4.5.1 (currently on bluspark 8.61 twrp 3T). I read the last 3 pages, and i got more confused, also i am having older 7.1 firmware..

I plan to stick to nougat (yet) until stable OOS PIE comes out.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Flash the latest firmware: OxygenOS 5.0.8

Oneplus 3T: OxygenOS 5.0.8 firmware (https://github.com/nvertigo/firmware-3t/raw/master/archive/oxygenos-5.0.8-firmware.zip)

Oneplus 3: OxygenOS 5.0.8 firmware (https://www.celsoazevedo.com/files/android/oneplus3-modem-firmware/)

Credit: [MENTION=4405529]nvertigo67[/MENTION]

and then the latest TWRP: 3.2.3-10

[MENTION=5091734]dianlujitao[/MENTION]'s TWRP is highly recommended: https://androidfilehost.com/?fid=1395089523397907195
[OnePlus 3 & 3T Cross Device Development] zoneofSAM:
I still intend to stay on OOS 4.5.1 nougat.

Won't flashing latest firmware means oos 4.5.1 will likely result in bootloop?

i just want to update twrp AND still be on old OOS.
[OnePlus 3 & 3T Cross Device Development] Dirk:
What's the point in updating Recovery right now? You're clearly not updating anything. Just wait until OOS Pie is released, flash this TWRP (3.2.3-10), Format and Wipe everything, and Install the full OOS Pie zip.
[OnePlus 3 & 3T Cross Device Development] abhibnl:
There will no point or benefit of upgrading to a latest TWRP if you are planning to stick to Nougat for now. I think it can create some issues with data handling but I could be wrong. I would also suggest to only update TWRP and firmware once Official Pie is available.

BTW, out of curiosity, why exactly are you still on Nougat when we are waiting for Pie now?
[OnePlus 3 & 3T Cross Device Development] MJPollard:
I can't answer for him, but in my case, it's stability. "If it ain't broke, don't fix it" is still good advice, and yeah, Nougat is a few years behind the state of the art, but if it's working for him and he needs his phone to be rock-solid and reliable, there's no sense in hopping on the upgrade carousel until the latest and greatest is proven to be stable. I'm on Oreo right now (my own customized Lineage 15.1), and I'm in no hurry to get a slice of Pie, at least not until my own custom Lineage 16.0 is ready and steady.

My $0.02, anyway. :D
[OnePlus 3 & 3T Cross Device Development] zoneofSAM:
wanted to update my stock kernel to dorimanx kernel updated recently on 31st march 2019 (v3.4). and the op instructed the twrp to twrp-3.1.1-2-oneplus3T.img

I am still on nougat ONLY cause of better gaming performance and battery life than OOS oreo. maybe OOS PIE will be better :fingers-crossed:
[OnePlus 3 & 3T Cross Device Development] abhibnl:
I am on stable OOS 5.0.8 and i would say it's really stable and works for me. I have tried almost all popular custom ROMs and Pie ain't ready to be called fully stable yet. I might be interested in testing now. If only I could find last released nougat build for OP3.
[OnePlus 3 & 3T Cross Device Development] fresholli:
Is the twrp version 3.2.3.10 stabil for beta. I'm asking because i don't see this on the homepage
[OnePlus 3 & 3T Cross Device Development] Dirk:
3.2.3-10 is stable and the recommended build. The Official website never seems to get updated any more. Don't worry about it.
[OnePlus 3 & 3T Cross Device Development] aboodyaiman:
Anyone flashed the new update?
[OnePlus 3 & 3T Cross Device Development] Paschfire:
Flashed what new update? Details?
[OnePlus 3 & 3T Cross Device Development] Dirk:
There is a new build. twrp-3.3.0-0-oneplus3.img

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

Nothing mentioned in Changelog so your guess is as good as mine. Until we know more people should stick to 3.2.3-10.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
I just flashed the new recovery (twrp-3.3.0-0-oneplus3.img) ... and no sweat on LOS 16.0 (encrypted ext4)... !
[OnePlus 3 & 3T Cross Device Development] Paschfire:
Interesting. Seems the list hasn't updated for my neck of the woods yet, as the newest build listed for me is still the previous 3.2.3-1 build. Or it's been pulled.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
==> https://dl.twrp.me/oneplus3/twrp-3.3.0-0-oneplus3.img.html
[OnePlus 3 & 3T Cross Device Development] Dirk:
Try Formatting with it. If Encryption still works afterwards we'll know it's not just an updated 3.2.3-1. (Seeing as how they never took down that broken version we may end up with a long line of TWRP builds that still include the broken code and still break the Encryption Footer).
[OnePlus 3 & 3T Cross Device Development] phil_greg2001:
New TWRP 3.3.0 with OOS 5.0.8 and data encrypted ext4, everything works well :svetius:
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Not tonight... :D

NB: Prudent I am... not crazy yet...
[OnePlus 3 & 3T Cross Device Development] Paschfire:
Strange, now 3.3.0-0 showing within the list.

Anyhow thank for sharing the DL link.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Crossing the Atlantic Ocean is time consuming ... :)
[OnePlus 3 & 3T Cross Device Development] Dirk:
Normal. :good:

Can't wait for someone to Format using this build. Will it break all the things? Watch this space...