yashsingh1/xdaforums huggingface dataset:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Update 20170214

Changelog:

init: import input_boost config from OxygenOS-4.0.3. — mad-murdock

op3: Move org.ifaa.android.manager to OSS — dianlujitao

update vendor/qcom/binaries from OxygenOS 4.0.3 — nvertigo

ship without firmware, but with TZ check — nvertigo

update build fingerprint

Revert "op3: Correct the name of the frp partition" — nvertigo

Revert "op3: Disable FRP" — nvertigo

init: we are 3T. — nvertigo

op3: Refactor init extension — dianlujitao

ROM: https://drive.google.com/open?id=0B_f72wz8rwc6MHVnczl2ZnRlUVk

MD5: c60d72934c2665a4ffcec673428da4b9

Mirror: posting #2

I would be interested in feedback on batterie life, espacially on sot. Since [MENTION=3044422]mad-murdock[/MENTION] figured out, that oxygen is using a slightly lower freq on input boost, we hope this change increases sot, without feeling laggy.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] lapapunk:
[MENTION=4405529]nvertigo67[/MENTION]

Make a dirty flash and It's seems to be good.

Don't know if it was must to survive, but SuperSU didn't survive, so I was flash it again. So anyway, it's good and work as should.

Thanks, for new build. Tomorrow I will show my sot.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
SuperSU can't survive since this rom is prerooted with laos superuser. Ifmyou need SuperSU instead of superuser you need to flash it every time. I remember SuperSU has an option to install a script for survive flashes, but it's not tested.

For batt: give it one loading cycle to settle. That'a why I have no numbers myself: I'm just flashing test builds to often to get real numbers.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] freepenguin84:
[MENTION=4405529]nvertigo67[/MENTION] Are you fully on par with current LAOS sources everytime you release a new update (despite your own changes of course)?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I'm syncing every time prior to build clean with emptied ccache. Build-Date minus 10 minutes is roughly the date of last repo sync.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I'm not happy with the place innsettings, too. But laos has decided to do it that way, because of upstream (aosp). But honestly: putting this part of configuration to additional buttons is the wrong placemas well: since all other configuration for on/off button is locatwd at buttons. But this is only of theoretically important because of sentence #2.

This rom is optimized for 3t hardware, but should give the user the plain laos expirience.

For the white screen while the preview surface of snap is initialized, configured and fired up: I would preferma blackscren, but I don't prefer it enough to put my time in.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] endursa:
fair enough :) both issues are no real issues anyways at the moment :)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] ram4ufriends:
This thread seems to be very interactive and discusses the low level technical details as well...I LIKE IT!!!!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] endursa:
So far it does not feel laggy at all, i will comment on battery life in the next days!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Sadly I'm limited to 8 thanks per day. :(

I liked it that way, too. It's about learning, exchanging knowledge and enpowerment to do something yourself. If this ends up having a nice rom as daily driver... ;)

That doesn't mean I don't appriciate "normal" users - and I really hope we don't leave anybody behind. This thread should be a good mixture. With some (knowledge-)candy for everyone...
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
I honestly gave up on it. Those terms are used in different meanings over and over again, that I probably also dont use them always exact. I make sure though to add content to it, so the meaning becomes clear in the context.

One thing I like to use though is talking about "crypto" - leaving the actual use case blank.

I _think_ the explanation is how those additional options are integrated into LaOS. You find them at device/oppo/common/configpanel/ - that's how they are tied into LaOS - not being part either of settings, CMParts or cmsdk. It's easier this way than include them in the main settings part and only include those changes into OnePlus builds.

Not an opinion though, just trying to explain the why. Sure "additional buttons" doesnt fit under an entry "buttons" - no discussion here.

Edit: In the same directory there also is a KeyHandler replacement - obviously to handle alert slider. It looks - on first glance - a lot different from LaOS keyhandler. But well, it seems to work.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] ram4ufriends:
Has there been any progress on fingerprint scanner not working sometimes? I think that's the only "bug" I would say left...
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] USHAM2:
Has anyone tried pixel launcher and if it's buggy? I had a lot of intermittent glitches a few builds back using pixel launcher and dialer but haven't tried with latest build. Stock Trebuchet works great!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
That's why I defined it, before asking my question...m;)

We don't need to speculate here. The reason is given here:

https://review.lineageos.org/#/c/157516/

this IS part of settings.

Additional buttons is a completly other topic, since most android devices doesn't have those. But additional buttons isn't the right place for configuring power button anyway. So the question is, why is this a gestures config and not a button config. This is answered in the above mentiojed commit.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Never expirienced fps not working - sure you expirienced this on this rom? fps qas working from the beginning of this rom. The only situations I have issues is when comming just out of the sauna and my fingers skin is ... (don't know the word - but I think you got it), and when the device is in my car holder: it's hard to place my thumb in the same angle as when I registered it's print.

If you really have issues with fps, try registering the fingerprints in as many angles as possible. This solved the latter issue for me.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] herwarth:
The camera is too buggy I decided to go to stock ROM again... Google duo camera crashing.... Slow mo video not working....OOS photo app seems to make better quality photos.... But that is maybe in my mind...
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
I use pixel launcher from the beginning of this rom. never had issues. installed as system app though for google now integration.

---------- Post added at 11:17 PM ---------- Previous post was at 11:15 PM ----------

lol. i replied to this - on the wrong thread (twrp) - roflcopter!

Quoting myself:

working flawlessly here. when i originally switched to this rom (first version) from another laos rom, i noticed the fingerprint worked way better than on the other rom. didnt see any change to this so far.

did you try this rom already or asking in preparation?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] ram4ufriends:
Asking in preparation..thanks for the reply....

How do we use substratum themes? Any flashable to make it substratum usable?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
The new Laos gestures aren't working for me. I tried toggling them on and off, but to no avail. Are they a work in progress or something?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Can you give a little bit of information? What is not working?

Just tried to set one finger swipe up to messages: message app is started, but screen is NOT unlocked, nor messages is put on top of locked screen, like camera i.e. This may be a bug - but if so, I like it. Imagine if anybody swiping up with one finger gets access to your messages. The same goes for browser or email.

This was geussing what you could have ment. If I take your bug report literal: we have no option to switch laos gestures on and off, we can only set gesture to action or no action for each gesture.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
It works in legacy mode.

[IRONIC]What do you suggest where to put it in OP? To the section IMPORTANT?[/IRONIC] ;) ;) ;)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] endursa:
Hi

I discovered yesterday that it might be possible to include open mobile api into this rom.

references:

https://xdaforums.com/oneplus-3/themes/mod-mobile-api-installer-t3547842

https://xdaforums.com/oneplus-3/how-to/openmobile-api-maybe-devs-to-include-t3414801

https://github.com/johnzweng/platfo...ardService/releases/jz_android_6.0_OMAPI-2.05

This is of interesst for me, since this api enables mobile payment via nfc based sim card (uicc) in austria!

first simply tried to flash the omapi from recovery but my banking app stil reported incompatibility.

second i tried all sorts of stuff within /system/etc/libnfc_bcmp.conf to try to find a cause of improper uicc offhost routing from the nfc controller to the sim card.

but i am still not sure if the omapi is properly loaded, is there a way to check if maybe selinux or anything else permission related could block it?

secondly does anybody have a clue if the oneplus 3t has proper SWP wireing between the nfc controller and the simcard slot(s) ? and if so, are both slots working, or just one? there is really no documentation anywhere regarding this!

so far I did not even manage to determine which nfc controller is used in the OPO3t to try to find a datasheet.

could you guys help me out here with anything? I would really like to get this working, or at least try to! but atm I am stuck
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Since I can't test this in germany, you are on your own here. Fot the git link: I doubt this will work without modification on N roms, because it's for M. Anyway: logcat is your friend, not only for checking if omapi is loaded.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
I mean literally none of the offscreen gestures are working. Only double tap to wake works, but even it doesn't produce any haptic feedback. You say it works for you so something is wrong on my side. You should know I am using your ROM with MultiROM, but I don't think that could cause this, could it?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] lapapunk:
Yep. It's on your side. One minute ago(because I don't use them in daily life), I checked my gestures. And all works as should. I have haptic feedback, and all gestures that I can to switch on. But if I use fingerprint (and its logical for me) I can't for example open the messaging, until my finger "open" the phone. So if I want to have a faster gestures that will be opening some apps, I must to delete my pattern and fingerprint.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] fireguy0306:
I had the same issue, I believe its related to the gapps package I flashed overwriting something and thus I got the aosp config wizard and not Laos. Anyway put this into terminal emulator.

su -c 'settings --cm put secure cm_setup_wizard_completed 1'

All my gestures and the physical switch/slider worked.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
Huh that's weird, I flashed nano Gapps. And I'm fairly certain I got the Laos config wizard, and not AOSP. Thanks! I will try that and see if it works.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] fireguy0306:
My theory was just that, however I found the command to work. I saw the official 1.4 guys complaining about the same issue about no gestures and that command was suggested.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
It worked! Gestures and haptic feedback are working now. DT2W still has no haptic feedback and the gestures respond kinda late compared to OOS.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] lapapunk:
So it definitely gapps. Because when I was install last build, I do it apart with gapps. And like result I had pass trough the laos wizard. That is why, all fine on my side.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
What do you suggest to write in OP and "google apps known issues", to stop you from using incompatible gapps? If you have any suggestions to improve this, I'm happy to change it.

This is not about issueing one command, it's about side-effects: what's with your next issue? Is it an other side-effect from wrong gapps, or is it something else?

For haptic feedback on dt2w, check the lineage os changelog (I think it's in op just above the devicespecific changlog) this is removed by purpose: https://review.lineageos.org/#/c/159794/
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
If you flash working gapps (or non working as well for that matter) you see both setups laos and google. Justba few pages back: https://xdaforums.com/showpost.php?p=71024116&postcount=394
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
My theory IS: stick to the gapps version known to have the least trouble.

If one command fixes this side-effect, who tells you that ther are no others?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] freepenguin84:
I read [MENTION=3044422]mad-murdock[/MENTION] s post about encryption (https://xdaforums.com/showpost.php?p=70960320&postcount=322). Some questions, though: Assuming that I'm encrypted on OOS 4.0.3, do I need to remove my screen lock pin or password before flashing this ROM? Or what will be the password for decryption in TWRP otherwise? Does it even ask for a password if I wipe data? I'm a bit confused here.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] endursa:
Thanks, I will try to get this working by myself then :)

btw OMAPI is designed for apilvl21 so should be compatible from android 5.0 on upwards! unless google removed something with nougat of course :D
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Stick to op. twrp and laos will ask you for encryption passphrase. When you clean flash this rom oos lockscreen password is gone, anyway. lockscreen and encryption passphrases are bundled in oos, but not in laos (can be set to different passphrases).

Removing encryption passwd is recommended for nandroids.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] binopech:
Can i install viper4android on this rom?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
Ah I see. I'd make it clear you meant a particular date of Gapps build. I thought you meant a particular variant, like nano. Or maybe it's just me who misunderstood. But yeah I usually flash the latest Gapps available using the logic that they'd have fixed older issues.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] babs232:
I am currently on Open Beta 2. To Flash this ROM, do I need to be in OOS 4.0.3?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] lapapunk:
hi. you will have 3 ways:

1. You will flash OOS 4.0.3, after this wipe all except internal storage. And flash Feb 14 2017 build

2. Flash previous build of this rom from Feb 10 2017, and after this latest build (dirty flash) Feb 14 2017

3. Flash firmware from 4.0.3 and then this build Feb 14 2017

and i propose you will needed in newest twrp - 3.0.4.-1
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] m0d hipp¥:
You need to flash the rom with the 4.0.3 firmware and then update to the 2-14 rom.

OR you can flash the 4.0.3 firmware first and then flash the 2-14 rom.

[MENTION=4405529]nvertigo67[/MENTION]

Not sure if anyone else is running into this, but I noticed on the 2-14 rom a few things.

1. I am no longer able to run adb commands. They were working perfectly prior to flashing this rom. I was on the stock 4.0.3 rom before.

2. When I enable sRGB in developer options, after I close out and go back into it, that option is turned off again.

3. I can't enable OEM Unlock bootloader option in developer options for some reason. It just slides from enable to disable automatically whenever I try to toggle it.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] lapapunk:
1. didn't check.

2. its truth but if you want to see the sRGB mode, you should go to set-display-color profile and set Natural. its exactly the same as srgb.

3. checked, its truth
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] lapapunk:
[MENTION=4405529]nvertigo67[/MENTION]

here is my a small report about battery life.

- with latest build i get 6h of SOT, and about 5% of night drain. (60% using with 3g, and 40%wifi + maybe 45m was gaming)

- by the previous i get 7.30h of SOT! with the similar using..
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] nitinvaid:
SUBSTRATUM support??
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] lapapunk:
just read this answer of the dev.

https://xdaforums.com/showpost.php?p=70901193&postcount=251

and this one

https://xdaforums.com/showpost.php?p=71038186&postcount=426
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Use twrp-3.0.4-1; flash oxygenos-4.0.3-firmware from Download section. Then just follow Installation in OP. No need to flash a second rom.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
1. enable adb in devops.

2. sRGB display mode is in livedisplay - I don't know what sRGB photo mode is, but it's broken; but it's NOT sRGB display mode.

3. fixed one second ago - will be in next build.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] m0d hipp¥:
1. It was enabled in the dev section, but for some reason the driver didn't work with this rom. I posted what I did to fix the ADB issue a few posts above.

2. ok

3. thanks
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Really?? Two pages back...:rolleyes:

https://xdaforums.com/showpost.php?p=71038186&postcount=426
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Just checked with win10: no problem here - works like charme. But I don't remember what package I used for adb (using linux most of the time for adb). Drivers are just the drivers win10 has loaded, when I first connected the 3t...

But thank you very much for fideling with win drivers!!! I'm totally noob on win.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] m0d hipp¥:
Windows is def my strong point, I'm having a pain in the butt configuring Linux on my new machine for some reason, and I have never run into this trouble before. I have a PCIE SSD drive that is technically 4 drives in a raid0 and Ubuntu sees them but isn't allowing me to create a ext4 partition and a swap partition on it and I have to figure out how to get it working because that drive is completely blank so I'd like to setup the git on there for this project.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
Its a slightly confusing topic if you didnt test all the options.

If you are encrypted on OOS, everything is fine. Just install your custom ROM and on boot it will ask for your password. Enter it, done.

About wiping, there are many options in TWRP.

- If you just wipe data, it will only remove all the files except /data/media, which represents your sdcard.

- If you format the data partition via advanced wipe, it will fully format the data partition and also remove the encryption key.

- If you change the file system - i.e. from f2fs to ext4, it will fully format the data partition, but not remove the encryption key.

Every scenario works splendid with this ROM. Encrypted, unencrypted, f2fs, ext4, whatever you like will work. The only thing tested late January not to work - and in the process destroying your data - is encrypting an unencrypted device. But before doing such a thing a user should backup all his data anyways.

Hope that answers your questions.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] cmattern:
I can help on the Linux side if you'd like, please PM me as it's not really 3t specific.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] freepenguin84:
Thank you so much, [MENTION=3044422]mad-murdock[/MENTION] and [MENTION=4405529]nvertigo67[/MENTION] for patiently answering my questions. I tried out a unified build of Lineage OS some time ago but there were some rough edges (with ROM, TWRP, ecryption, f2fs ...) so I went back to OOS for the moment. I miss some CM/Lineage features badly, though. Since then I follow development, especially in this thread. Time has come to give Lineage another try. I'm a professional Java software developer with little experience on Android. The friendly atmosphere here even makes me want to contribute :)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] themcfly:
Hey nvertigo,

Flashed your rom after having problems with the official that wakelocked my phone for 20-25% of sleep time, even trying to disable Google Now/Location reporting, BBS and Wackelock detector were not of any help (just showed empty bars under partial wakelocks). I flashed gapps on the official AFTER first lineage boot to avoid the slider alert and related issues, but after reading your post maybe that caused the deeper issues. When do you think this issue will be solved so one can flash any Gapps package without first setup issues? Is that on Lineage part or Gapps?

By the way, now I'm on your rom flashing as instructed. With google now/location reporting active and everything I get 4% wake time compared to before (is this alright?), something less on longer sleep stints, like at night. Buttery smooth performance even with the new input_boost. Color profiles works compared to the official build (when you boot first time you have the standard color profile, but once you select sRGB you are unable to go back since it's the only entry in the menu).

Love the fact that you keep as close to LOS as possible, correcting bugs and optimizing performance without adding lots of features like other roms. Thanks for the great work! :good:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] m0d hipp¥:
I flashed the newest rom with 4.0.3 and then within the same twrp session after flashing lineageos I flashed opengapps nano from the first post and it worked fine for me. No issues with the slider, so you should be fine.