yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I googled "gboard space" and there are some interesting links from last year. Including one form the OnePlus community forums https://forums.oneplus.com/threads/gboard-space-below.1185914/

One of the replies said that the space is by design in Android 10!

I tried the suggested fix in that post, but ended up with even a bigger space (after trying different values) under the keyboard when I reset the values to all 0.

So I restored a 2-day old backup and the space was still present. Then I rotated my phone by accident into landscape whilst using the keyboard and noticed that it had no space. And when I rotated the phone back to portrait mode and ...

Voila, no space!

I normally have my phone locked in portrait mode. And even if it isn't, I would never use the keyboard in landscape mode. So I was lucky to stumble across this "fix".

Tl;dr: rotate the keyboard into landscape and back to portrait and the space disappears.
[OnePlus 3 & 3T Cross Device Development] felixchris:
I always kinda didn't like Gboard. If you want a nice keyboard and don't mind the potential data protection issues you can always take SwiftKey and log in with Google. Voila, no space + additional customization unlocked :D
[OnePlus 3 & 3T Cross Device Development] punio4:
Tested, the gboard issue doesn't happen on stock OxygenOS 9.0.6 or stock LOS16, only on NLOS.
[OnePlus 3 & 3T Cross Device Development] Hazbelll:
Fun fact: The Spell Checker in GBoard (Not auto-correct, I mean if you turn that off and use the old fashioned red underline) has been broken for years now. A red line appears (Might be blue), but tapping it shows no suggestions. A workaround I discovered was to use the "AOSP Keyboard" spell checker instead in Settings, then it works. For that reason I'd be wary about Google ever fixing the space issue you're all on about.

Honestly, if the AOSP Keyboard had a proper dark theme (Its only dark theme is Holo theme from centuries ago), then it would be the perfect keyboard in my eyes.

Edit: Almost forgot to say also, thank you [MENTION=4405529]nvertigo67[/MENTION] for all the amazing work (Such as this ROM) and support you provide to us all for our old, but still gold OnePlus 3(T)'s! :)
[OnePlus 3 & 3T Cross Device Development] :
Not only gapps suckz - FYI:

https://fossbytes.com/zoom-app-sends-your-data-to-facebook-because-why-not/
[OnePlus 3 & 3T Cross Device Development] pijas82:
Can't wait nlos 17.1 ?
[OnePlus 3 & 3T Cross Device Development] knpk13:
Can't wait NLOS 18 Developer Preview 2
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Does this mean you aren't planning to build nlos 17.1 or that you'll have two versions supported or something else?
[OnePlus 3 & 3T Cross Device Development] :
I've really enjoyed the last months: using a build for 10 or 14 days without reboot, just working and no major issues left. With the covid-19 lockdown I was thinking about using the time to put nlos to 17.1.

Then 17.1 went nightly. As you know, I'm using the official los threads as well as the nlos threads to fix, enhance and support both flavors. Let me note at this point, that I really look up to your patience! But after the postings in the los-17 thread - especially the last 72 h - all my motivation droped to zero.

It looks like Murphy is not only hiding Ockham's razor, but has an unlimized pool of lazy and demanding ignorants, he has send to the op3/t official los-17 thread.

I don't want to explain how to pull logs, why logs are important to fix something, what pstore is, what "the very next reboot" means, that a missing (not yet implemented as well as droped because of aosp changes) callrecorder is no issue. Sadly, I can't fix or improve things, without the help and feedback of users.

The following might be arrogant, but it's the way I feel - and since I'm doing all this dev stuff voluntary in my spare time I allow myself to feel like that:

When reading your wonderfull and patient response to explain what magisk's purpose is, my frustration was shouting from deep inside me: you bloody, lazy, demanding ignorant, if you arn't able to check within 60 seconds what magisk is, return to stock, relock your bl and don't bother with custom roms! Which is not acceptable, of course.

For now I think I'll stay with 16 and take a break from 17. I don't know how long the lockdown will be, I don't know what's the summer and autum will bring - what I know is: like for 14 to15 and 15 to 16, if I put los to >16, I'll provide 16 builds untill all thread-active users feel safe to switch.

EDIT:

Before one asks: I'm planning to use my op3t for another year - if nothing breaks.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Lol! I loved your post. And I totally empathize with the frustration caused by new users.

But I was one of them too, one upon a time, and others helped me. And I've watched you be so, so patient with annoying users at times.

I totally understand wanting to avoid dealing with all the silly questions.

I'm hoping that my op3t will last another 2 years - I'm not liking the prices or size of current phones (too expensive, too big). Maybe in a couple of years they'll be cheaper and a sensible size (~6' max).

So I'm looking forward to using 10 for at least another year and hopefully 11.
[OnePlus 3 & 3T Cross Device Development] knpk13:
I noticed that too and thought about replying but the people kept coming lol. How to relock bootloader, where is privacy guard, why magisk, all basic questions asked a dozen different times on the same page although it's already been answered and documented (I sometimes miss the mark with more complicated stuff myself, but this is basic stuff that even a new user can understand by reading a blog post). I've been using custom ROMs since Jelly bean, and this influx of posts happens every time a new version of CM/LOS goes official lol, so I try to save my sanity by not replying immediately to some of them, although I try to reply if no one else does and the question is reasonable enough, as I've been a new user myself and had so many questions before modding my phone. I imagine that's also why a lot of devs don't interact as much as you in threads, or can be really snarky when they do (especially on telegram lol), since they deal with this stuff so much.

Edit: Oh btw [MENTION=2911853]BillGoss[/MENTION] when I read your magisk post my insides were saying, oh no he forgot to mention magisk modules, should I reply xD. I figured they'd learn that if they googled it and went to magisk's XDA forum or GitHub so I didn't reply. That's kind of how I decide to reply [MENTION=4405529]nvertigo67[/MENTION] ; if I google the question and find the answer within the first page easily, I don't reply. I sometimes PM them if I notice they're making posts in multiple threads and really having trouble getting started and I have some free time.
[OnePlus 3 & 3T Cross Device Development] SenseSei:
I can only say to ignore the trolls and ignorant users and focus on the stuff and reports which matter and are constructive. For your own sanity (and our favorite Rom) ;)

I look forward to the Pixel 4a release and also keep a look on the Sony Xperia 10 II personally, I won't pay more than 400€ for a phone ever... These two look promising but my OP3T is still working fine and I'm in no hurry.

I have only a minor issue but I was wondering how to properly report it:

Sometimes the fingerprint-scanner/home button isn't working at all and I have to manual lock and unlock it again for it to function normally. It feels random and I can't reproduce it...
[OnePlus 3 & 3T Cross Device Development] 64ashg:
I have it too. Its maybe because i use naptime's doze.

It also happens in my k20pro running lineageos. So if there is an issue, its not device specific.

Ps k20pro or mi9t pro aka Raphael was also a good option. Bought it three weeks ago, around 300$
[OnePlus 3 & 3T Cross Device Development] SenseSei:
I don't use any hibernation apps like naptime or Greenify, as they are not needed since Android Pie. I guess it's a Lineage issue but idk what causes it
[OnePlus 3 & 3T Cross Device Development] :
It's hw fault for being too sensitive on such minor dirt

It happens on all roms under certain conditions, you just doesn't test it thoroughly if you feel x is better

Tapping too frequently on a dirty fp/fingers usually the cause
[OnePlus 3 & 3T Cross Device Development] Hazbelll:
Don't be disheartened by the uneducated noise. Unfortunately it's the norm wherever you go in life (For a serious example: Here in the UK, many are still ignoring the COVID-19 Lockdown initiative, despite the rapidly rising death toll nationwide as they're totally unaware of how easy/rapidly it can spread from close contact!).

Rest assured your hard work and efforts are appreciated by many, more than you might think. People might be lurking these threads, searching for answers and then applying thought themselves. Until very recently, that's what I was doing myself, until I needed to ask some questions to get more thorough answers, and I appreciate any and all the help received.

As far as I'm concerned, you're the "official co-maintainer" of our phone as you're always engaging with its community, helping others and fixing bugs. Honestly, it's so nice to see and I respect you're doing this out of your own time and efforts. Keep up the excellent work [MENTION=4405529]nvertigo67[/MENTION] and thank you for everything!
[OnePlus 3 & 3T Cross Device Development] mk_1996:
do not get disheartened brother. i love your work and i can only laud the perfection in your work. we know how the so called "Junior Members" are here. you don't have to reply to each one of them. I've tried your builds since los 15 days and i can only thank you for your work. we all know how a developer puts their time and effort into this. I also have no plans to upgrade right now. everything works fine. just updated to los 17.1 and will switch back to NLOS 17.1 once its out.

P.S- i guess we should all have a thank you thread dedicated to the developers of our device. that's the least we can do to thank them for their work. idk just an idea lol.
[OnePlus 3 & 3T Cross Device Development] stevenkyk:
I had a similar issue a while back, whereby the home button will suddenly lose functionality, but spam pressing will sometimes bring it back while the phone is on. Sometimes the fingerprint reader will also not work and a manual unlock is needed. I thought that it was a hardware issue when one day after another episode of the home button not working, I rebooted the phone to find it working reliably again but without fingerprint functionality at all.

My investigation led me to clear all fingerprint data by manually removing /data/system/users/0/settings_fingerprint.xml and /data/system/users/0/fpdata/user.db

After a reboot everything works well again and I was able to register my fingerprints once again. Hope this helps.
[OnePlus 3 & 3T Cross Device Development] punio4:
I fixed it by disabling pocket detection.
[OnePlus 3 & 3T Cross Device Development] hellcat50:
Your ROM is very stable and has very good performance, and is secure (thanks to your speedy security updates!). That's what I love about this ROM :good:

And if you keep updating the ROM, I don't see any reason to upgrade to Android 10 (LOS 17.1)
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (April Security Patches; WireGuard 1.0.20200401; webview 80.0.3987.1 )

You're welcome! :) Here we go:

Build 20200407

Releasenotes:

ATTENTION!

From build 20200312 on there are two invasive changes:

Night mode is changed from aosp implementation back to LiveDisplay implementation. If you want to dirty flash (aka update) reset night display before rebooting to recovery for updating. This is mandatory!

Alipay, WeChatPay, ifaa and soter has been removed to protect your privacy. Some alipay and soter files needed to authenticate with fingerprint for Alipay and WeChatPay reside in the modem firmware. To get rid of these, I higly recommend to use no-alipay firmware packages (links below are adjusted to the new packages). This is not mandatory but highly recommended.

If you decide to use Alipay with fingerprint authentication with nlos see posting #6.

This build relies on OxygenOS firmware. OxygenOS 9.0.6 firmware is required. At this point you have two options:

You don't care about loosing data on an unlocked bootloader and clean flash including format userdata according to the first time installation instructions in OP (recommended):

Oneplus 3T: OxygenOS 9.0.6 firmware without alipay and soter files

Oneplus 3: OxygenOS 9.0.6 firmware without alipay and soter files

You want to keep your current setup and like to dirty flash on top of beta builds:

I've created a firmware package from OxygenOS 9.0.6. To avoid issues due to an unlocked bootloader and/or encrypted userdata partition, I've kept the bootloader and and keymaster partition to OxygenOS 5.0.8. This allows to run the pie-blobs builds with native Oneplus OxygenOS 9.0.6 firmware, but you don't need to reformat the userdata partition (for details see: https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164 ).

Oneplus 3T: OxygenOS 9.0.6 firmware with 5.0.8 bootloader and keymaster and without alipay and soter files

Oneplus 3: OxygenOS 9.0.6 firmware with 5.0.8 bootloader and keymaster and without alipay and soter files

If you need to pass safetynet api flash sec-patch-2019-08-01_v02.zip from https://xdaforums.com/oneplus-3/one...-nlos-16-0-t3879405/post78433987#post78433987 .

Before you ask: though I've updated the blobs used in the rom to OOS 9.0.6, I've decided to stick with OOS 9.0.5 build fimgerprint, because 9.0.5 is the only version with identical fingerprint strings for op3 and op3t.

If you want to use Alipay with fingerprint authentication, follow [MENTION=9998549]Galiis[/MENTION]' directions in posting #6.

For a complete list of additional cherry picks see: current.pick.sh.

Changelog (Last repo sync: 7 Apr 2020, 15:00:26 CEST / 7 Apr 2020, 13:00:26 UTC):

Patch up: P_asb_2020-04. — Nvertigo

current.pick.sh: force pickicking abandoned topic "app-perf-profiles". — Nvertigo

current.pick.sh: "webview_80.0.3987.162". — Nvertigo

WG: squash WireGuard-linux-compat-1.0.20200401. — Nvertigo

NLOS-Bootlogo

nlos_bootlogo-v0.1.zip

back_in_black_bootlogo-v1.0.zip(pre ob16 OxygenOS Bootlogo)

[SIZE="+2"]DOWNLOAD[/SIZE]​

Happy flashing!
[OnePlus 3 & 3T Cross Device Development] hellcat50:
[MENTION=4405529]nvertigo67[/MENTION] Thanks for the privacy friendly firmware. Yes, I'm a privacy freak and I of course immediately flashed your firmware.

I would like to link this firmware in my own firmware thread (https://xdaforums.com/oneplus-3/how-to/op3-flashable-firmware-modem-zips-t3816066), is this ok for you? (I would give you all the credits for this of course)
[OnePlus 3 & 3T Cross Device Development] :
Absolutly. Feel free to go ahead.

Sadly, the blobs in the firmware are the property of OnePlus, of course. Otherwise I would have put a gpl copyleft somewhere.
[OnePlus 3 & 3T Cross Device Development] pijas82:
Well I'm back to my favourite rom,.thanks , perfect always ??
[OnePlus 3 & 3T Cross Device Development] defi231:
can i dirty flash this from latest LineageOS 16.0?
[OnePlus 3 & 3T Cross Device Development] knpk13:
As always, you can try and see if it works. If not, then clean flash. Still not recommended to dirty flash between official and unofficial versions.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Is there any way to tell if you're using the no alipay/soter firmware? I just flashed it and was wondering if there's a different baseband version or something.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
You can browse the modem (/vendor/firmware_mnt/image) for ali* and sot* files. If there aren't any, you're using the modified firmware.
[OnePlus 3 & 3T Cross Device Development] :
You need root previlegs to read the mounted firmware partition:

adb shell find /system/vendor/firmware_mnt/image -name \*ali\* -o -name \*soter\*
find: /system/vendor/firmware_mnt/image: Permission denied

For magisk su:

adb shell su -c "find /system/vendor/firmware_mnt/image -name \*ali\* -o -name \*soter\*"

If you don't use any su package, enable root for adb:

adb shell su "find /system/vendor/firmware_mnt/image -name \*ali\* -o -name \*soter\*"

Or use the twrp terminal, mount system, mount /dev/block/sde11 to /system/vendor/firmware_mnt and use just the find command from the above examples directly without adb.

If you are rooted, you can also use a root enabled file manager to search for any files containing ali or soter in their names from within the rom.

Note: the above is for non-sar roms. You may need to adjust paths if using a sar rom.
[OnePlus 3 & 3T Cross Device Development] :
Before reporting issues do a clean flash.

Remeber the nightdiplay setting as mentioned in the last two announcements!
[OnePlus 3 & 3T Cross Device Development] ArchGalileu:
Hello [MENTION=4405529]nvertigo67[/MENTION]

I now have problem with Aliexpress...

Payment doesn't finish on mobile... And nasty error appears on my account.

Do you think it is related to the alipay cleanup?

Any advice?

As always best regards and congratulations for this great ROM ;)

ArchGalileu
[OnePlus 3 & 3T Cross Device Development] pijas82:
Try flash magisk 20.4 and in magisk manager put ✓ on hide
[OnePlus 3 & 3T Cross Device Development] :
Hard to say based on this information. I'm not using alipay, which doesn't really qualify me to have a solution at hand. From what I've been told only fingerprint auth doesn't work, but paymemt is still working. I don't know if alipay and aliexpress is the same, or if alipay is workimg but ali express is not... Sorry.

The first what I would try, is the guide from [MENTION=9998549]Galiis[/MENTION] in posting #6, if that fails, try an earlier build with ifaa/ali/soter stuff in place together with an ali/soter containing fw.

Another good place to get assistance on this may be: https://xdaforums.com/oneplus-3/how-to/guide-deblob-alipay-ifaa-tencent-soter-t4064893
[OnePlus 3 & 3T Cross Device Development] skothiya:
Can i use this rom using f2fs file system?
[OnePlus 3 & 3T Cross Device Development] :
Yes. As mentioned in OP ext4 is recommended. Current twrp should be able to format f2fs with encryption footer. Since twrp had many regressions regarding f2fs, following the OP recommended manual formating method is always safe.

I'm using encrypted f2fs myself to catch errors first - there's NO performance benefit, in deed ext4 is faster if the userdata partition is used 70% and more. The cache partition should be ext4: f2fs on cache is not only slower, but can lead to trouble with xattr!

EDIT:

One of the best non-religous write ups on filesystems: https://www.xda-developers.com/f2fs-why-file-systems-matter-interview-stan-dmitriev-tuxera/
[OnePlus 3 & 3T Cross Device Development] :
OP - update

I've changed the OP installation instructions slightly.

From:

Optional (mandatory, if you have issues with encryption): Format data: in twrp tap on wipe and then tap on format data. This will delete all data, remove encryption and leave you with ext4, which is highly recommended. If you are insisting to use f2fs see: https://xdaforums.com/one...9#post75688089 - NOT recommended!

To:

Optional (mandatory, if you have issues with encryption): Format data: in twrp tap on wipe and then tap on format data. This will delete all data, remove encryption and leave you with ext4, which is highly recommended. If you want to use f2fs you need to change the fs back to f2fs - it's possible but not recommended (at least if you don't have basic knowledge of fs implementations). Many twrp versions have serious regressions regarding f2fs with encryption footer. Though this should be fixed by now, you can always manually format f2fs with footer. See: https://xdaforums.com/one...9#post75688089.
[OnePlus 3 & 3T Cross Device Development] :
I've tried gaming lately because of covid things, and reading users experiences they said OOS Nougat (4.x.x) is the best version for it.

I've tried to compare it with nlos 16, both on clean install with only gapps, magisk (no modules) and the game installed, it's indeed better in terms of FPS.

How can i help to determine if it's the game or the rom/kernel issues?
[OnePlus 3 & 3T Cross Device Development] :
I don't think it's an issue.

General thoughts:

Higher version->more features->more background services->less performamce for foreground processes (possible user actions: disable as much bg activity as possible)

Higher version->more bat saver features->less performance (laws of thermodynamics) (possible user actions: change performance profile - general or per app)

most performance limiting factor on "normal" flagships is thermal throttling - I don't want to fiddle with it, because it does not only compromise the first two priorities to increase the third priority, but also degrades the life time of the device. That's why all gaming devices have heat sinks (possible user action: get a gaming device like https://www.asus.com/Phone/ROG-Phone-II/ ;) if you get me one, I'll try to port nlos ;) ;) ;) )
[OnePlus 3 & 3T Cross Device Development] :
I'm actually modding this phone, i used to play a lot when this phone was new and then lost interest with it, so heat isn't my issue :laugh:

Replace the CPU cover with this, join/solder the top of it with this, do the same to the alumunium backcover. The heat transfer now become evenly on all side

No need to buy "branded gaming" phone :D

=====

You might be right, android version might be the culprit...
[OnePlus 3 & 3T Cross Device Development] :
Hardcore gaming is always a hardware battle - though the specs and features of the ROG II are really impressive, it's just a matter of time till it's an outdated paperweight...

A friend of mine is a hardcore pc gamer, as far as I know of he buys once a year a new cpu with mb and ram and twice a year a new graphics card (or should I say an new graphics computer cluster)... (I use his 7 years old AMD FX-8150 Eight-Core Processor on an sabertooth 990FX board for building roms, vdr and samba server and call it "my server"; he calls it "my oldtimer"; but he also claims everything you can't connect at least 3 4k displays to is not good for gaming)

op3t is an over three years old device. Apart from mods and tweaks I think it's ok to lag on highend games.
[OnePlus 3 & 3T Cross Device Development] :
Just to keep you busy [MENTION=4405529]nvertigo67[/MENTION] lol

Could this be ported here too?

I have a feeling you're not a fan of this, but i can assure you the last time I played with nano gapps+xposed instant face unlock, you'll be grateful for not having to press your dirty fingerprint reader or type a passwords while your screen is wet :D

Just make sure it's secure though, like google or none of my apps or anyone (really) doesn't have my pretty photos :p
[OnePlus 3 & 3T Cross Device Development] hellcat50:
[MENTION=4405529]nvertigo67[/MENTION] by any chance do you know why my dad's oneplus 3t randomly crashes to white led and then gets very hot with your rom? I mean, he had this issue too with Havoc OS (Android 10) but it was very rare.

I read somewhere that this could be a cpu issue and that underclocking the cpu can help with that. I will try this for now. But maybe you know more.

btw I've never had this issue with my oneplus 3.
[OnePlus 3 & 3T Cross Device Development] pedritopl:
It could be: https://www.reddit.com/r/Android/comments/5j2jk5/sultanxda_found_that_if_the_oneplus_3t_sd_821/