yashsingh1/xdaforums huggingface dataset:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Second patagraph of OP:

Don't mean to offend you, but if you missed the second paragraph of the OP, microg might not be for you at the moment. Sadly ease of installation and configuration is no part of microg, right now.

How to use Android without Google Apps is quite some times larger then OP and you need to read and understand the whole guide before starting out with installing microg. It takes some time (and even more time to acquire the nesseccary knowledge) and some enthusiasm to have a non-frustrating microg expirience.

If you decide to start your microg adventure and accept the limitations of microg - this can be the beginning of something great - the more people use microg and the more people involve in its open source development, the better microg will be in future. MicroG and FOSS in general are clearly needed in the very near future (this very near future we call "NOW") to maintain at least a minimum of privacy.

Free, community developed open source software is a matter of Freedom, Human Rights and Democracy. My data should be mine. Therefore we need easy to install/use FOSS.

I'm dreaming for more then three years of a project, consisting of not only a microg preinstalled rom, but also an ready to use sdcard image for a raspberry, banana or similar with owncloud to sync calendars and contacts and share data. The third and absolut elemental part of this project had to be easy to understand and 'fail safe' end user documentation, which contains not more then 4 Kb of text and max. 8 screenshots... ...the last part is surely not for me... ;):p:angel::p:p

If you - or anybody else for that matter - decides to move to microg (did I say, that microg is an important and awesome piece of software? It is!), take notes, take notes and take notes. Later make a howto. If I would take my time to do so (and it's on my agenda to change to microg on the long run), my howtonwould have great and a real lot of information - but it would be unreadable for a user flashing the first time a custom aosp based rom just looking for a gapps/gservices replacement, without beeing ask to read a 20 pages documentation...

This posting seems to be slightly OT on the first view - on the second: I would love, to link a step-by-step howto by posting # (you are welcome to place this posting here in our thread, but an own thread is also fine for me!) to answer this quoted posting. There is nothing wrong with wishing just 7 (or 13, or so...) easy steps, and google, apple, microsoft are not longer commander in chief of our data. But I have no such documentation! Get involved! Help me (and all others here interested in privacy)! Help!?!

Happy Helping! Happy FOSS! Happy privacy! Happy Happy!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] 186Y:
Thanks [MENTION=4405529]nvertigo67[/MENTION] for adding OMS! Just got back from dirty flashing over the 20170418 build with open_gapps-arm64-7.1-nano-20170120.zip and everything's all good. I had to uninstall/reinstall substratum to get 7.1 OMS to work with Swift Dark but other than that following the instructions worked flawlessly.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mcdachpappe:
an addition to this:

remember me (and some other users) asking you for some more notification-/alert-slider settings? got it working now with a little research.

these are simple commits to device_oppo_common and the kernel. have a look at my repos if you are interested in (im still a beginner, excuse me several messy things there)

another question:

do you want me to report some stuff i found out? you said you are curious about my future commits. or shall i do a pull request to your repos instead? i dont want to spam your thread with possible changes
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Welcome.

What I like about the aproach of this script, is that all the OMS stuff is applied ON TOP of whatever you have synced or edited. The main problem for me as a freetime dev is: whenever reaching out on code which is not part of our device, kernel or vendor git, I have to constantly keep this additional git in line with upstream. With repo-/cherry-picked changes on top of that, I have no longer to bother with.

That's why I have i.e. an own andriod_build git, but fetch and cherry pick the changes from there without using the git in local_manifest. After repo sync I fetch/apply the changes,mand everything is up to date. From time to time (not on every ****ing sync) I rebase the changes needed, and adjust the URLs of the rebased commits. It's for me more time efficient, then keeping my own forks of such high freq changed gits like frameworks/base up to date on my own. It also keeps the commit history and status of the additional applied commits more readable for a non-genius like you (I think you have meant something like this "unreadabilty", when writing "i was dealing with nearly hundreds of different commits in different files and locations.") and me. ;)

Hey, today is experimental day - OT allowed... ;) and this is definetly "O"n "T"opic: Feature request motivated by a not fixed long time issue of this rom is NOT "O"ff "T"opic.

I remeber not exactly, but I have seen the comments on this commit... it's just one commit to rebase frequently more... ;) No promise, but if there is no systematically conflict I will consider putting it in.

Noob question of a dev using is device not often enough, because he's always flashing some testbuilds: doesn't coffeine, laos's custom tile implementation, offer an option for LiveDisplay night mode?

Or: if you build yourself anyway, flash each day a new build - the broken auto mode will never cross your way again (I know what I'm talking of!)... ROFL

Exactly. That's the theme-engine-user's part - I'm not too surprised to find you in that group. ;)

And you are welcome to share your Substratum expirience here. I have no such expirience. I want to give you the choice and put OMS in the experimental, but I'm totally new to substratum: if the to be found/tested/chosen reference theme is a dark one, I would pay for it.

There is a equally important (if not more important) part of feedback I need: users, that leave substratum uninstalled and use the rom like before. Stabillity, safety/security and batt life impacts are not exeptable at all. Performance impacts may be acceptable, depending on how serve and often they occur.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Either is ok for me. Don't be irritated if I cherry-pick, instead of accepting pull requests. Accepted pull requests result in merge instead of cherry-pick or apply-patch, what in consequence gives an ugly and difficult to read (for us - github guru preferences may differ, but I use git lg1 to watch my history) git history, with empty pull request merge commits. (OK, I got really not enough sleep recently: whoever read the last paragraph and is still with me with that explenation, should consider consulting his doctor... ;) If I take some rom-rest the next days, just read this paragraph... *lol*

And now the short version: I'll have a look at your gits in the next days. If you think something is considerable important to add it to our rom, just drop the link here, so others can read, learn, comment and discuss.

Just for the record: I'll look in the slider commits - of course. But I still LOVE the slider the way lineage implemented it. If the commits break this in any way they will not be merged (talked much about freedom of choice, but my loved slider-functionality is not discussable, sorry).
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] MATRIKS:
Exp build work without issue using swift black theme

Thanks
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
Slider commits won't affect anything. They just add two options in the drop down menu for slider, ring and vibrate. I've used it on other rooms for the op3t and op2.

And it's experimental day indeed. This ROM is getting everything I've always wanted in a ROM. Though I'd prefer to flash additional stuff manually, like magisk. I think the choice of root solution should be up to the user though I use magisk myself.

Maybe this ROM will get EAS one day at this rate. :P

https://xdaforums.com/oneplus-3/one...nt/kernel-render-kernel-t3505956/post71981907
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] technotravel:
nvertigo67 - you da man! I want to thank you for your your efforts to this marvellous ROM!

I share your enthusiasm for microg and FOSS - in fact, it is the reason for me to do the flashing. I hope it will be working soon as planned - and spread further and further.

I am still new to this activity, but I will try to contribute as best as I can.

Wishing you all the best for the continuation - and take a necessary rest, too!

Thanks again

Chris
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
Wow, I am very impressed by substratum. First time I take a look at it.

Much more to say, already started writing a post, but I need more testing and using this thing. At first glance, it might look as old CM Theme Engine in a bit better, but it is much more. And it has issues. But: VERY impressed. More tomorrow.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
Yup their goal is to get it merged into AOSP. So all devices should be able to use it, without root and other mods.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
I doubt in its current state it will either be merged into AOSP or into LaOS. LaOS always has the "a ROM for your mom" philosophy. This surely isn't for your mom. Only playing with a couple of themes I already had a total breakdown, requiring me to reinstall substratum and one theme to be able to apply themes again. And it didnt fully reset the system. Script errors still occured. I am not sure whats the reason, because in most cases, the error dialog is only visible for a few seconds before GUI is restarted due to new theme installed and error dialog is gone. This is just one example - there is much more what shouldnt be.

If your theme selection is running, its flawless (at least until now it seems like it), but getting there can be a nightmare. Possibilities are also amazing. But without a LOT of work on stability i doubt it will get popular. Hell, I myself would vote not to include it into LaOS.

Our ROM though is another matter. MicroG is optional. Substratum is optional. Our ROM surely is NOT for your mother. Depending on more feedback - especially from users not using themes - I think it might fit. Not my call though.

Should I go into more detail about my findings?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
Of course not. I said it's their eventual goal. Both projects have high standards of code quality and you need to comply to Google's rules like no root, etc.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mcdachpappe:
clean fash:

did a clean flash now (beans gapps - no more microg), no issues so far. everything is up and running smooth and fast (oms support via lineage_oms_merge.sh did its job successfully for my build).

im currently testing the swiftdark theme (current version 6.8) and didnt noticed any problems yet. its just a simple dark themed theme with blue accent color - its good for testing.

i dont really understand your question. as far as i know coffeine keeps the display awake as long the qs tile(coffeine) is enabled - shouldnt something to do with livedisplay night mode

haha yes, didnt noticed the broken auto mode the past days during recently flashing new builds. but i know its still there, thats way i added nightdisplay.

about the slider modes:

the kernel and additional-button-settings commits i applied do not break any do-not-disturb behaviors from stock lineageos settings. these are just additions and no replacements - you got my word on this.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] SourPower:
I agree
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Just to avoid future misunderstandings:

OMS is patched into the rom - that's a service provider (like location provider, i.e.). This service is utilized by an user app, called "Substratum". There is NO Substratum in this rom. There is OMS in the rom. Since I only know of substratum using this service, I hope it doesn't have any impact on the system, if no app which utilizes the OM Service is ever installed. Let's get the phrases and words straight, when talking of technical aspects.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] yannmrt:
:crying: didn't find it :crying: :crying:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] horqai:
Tested the experimental build and somehow I'm losing root after a reboot. Direct after installation the phone is rooted.

I did the installation the dirty way but followed the OPs instructions.

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] technotravel:
read here how to overcome this - worked perfectly for me (and I was in the same situation).

Good luck!

Chris
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] horqai:
Hey great hint, activated busybox in Magisk was the problem. [emoji106] thank you

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mcdachpappe:
yes ill try to lern git in the future. the github interface is indeed not quite good. im still a beginner and didnt know most of the time what i was doing - thats why my commits look like they are at the moment.

after getting some further knowledge about git ill delete my repo's and fork some new ones with the correct and clean commits with the original authors - excuse me please. it was not my intention to kang anything, i tried to insert the original authors names and changeid's to the commits a apllied. i know its not a good manner.

most of the last time i was "working" via the github overlay as i dindt find the time to add the commits on my local machine. i know i have to change that, thanks for the heads up.

i had to deal with some merging conflicts with some commits on my machine and i didnt know how to solve them, so i applied them one by one in my repos via github interface by hand - this will explain the missing authorship.

i sadly dont understand this enough but i will try my best in the future.

thank you for your explainations about the nightdisplay and the ambient display. about the nightdisplay: sorry i didnt know that it has such a big impact.

sorry for any inconvienences.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
You are welcome. As you can guess from the amount of EDITs, I havn't know this, either.... Had to read and to learn. The reason, why this commit was canceled that fast: NightDisplay is not just another hook to LiveDisplays night mode (that's what we both thought in the beginning), but a complete different subsystem, which does nearly the same as LiveDisplaya night mode.

You can get an idea what NightDisplay will do, when looking at: frameworks/base/core/res/res/values/config.xml (lines 799 to 810, it's quite well documented)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Added uniblobs and firmware for OpenBeta 5 to OP

Firmware

OxygenOS OpenBeta5: https://drive.google.com/open?id=0B_f72wz8rwc6QjVZMkxVd1JSSVE

OxygenOS OpenBeta4: https://drive.google.com/open?id=0B_f72wz8rwc6cUctQjZzT1ZPN0E

OxygenOS 4.1.0: https://drive.google.com/open?id=0B_f72wz8rwc6S1NiNGZmUDZfcjA

OxygenOS OpenBeta3: https://drive.google.com/open?id=0B_f72wz8rwc6TGZYVENiejhMQ0E

OxygenOS 4.0.3: https://drive.google.com/open?id=0B_f72wz8rwc6OUw4eE5IVlNzZU0

Renamed blobs (for use with custom kernels build for unifie roms)

OxygenOS OpenBeta5: https://drive.google.com/open?id=0B_f72wz8rwc6ZG5veVVQYkV4TUk

OxygenOS OpenBeta4: https://drive.google.com/open?id=0B_f72wz8rwc6NVFfZVlSaUdjOW8

OxygenOS 4.1.0: https://drive.google.com/open?id=0B_f72wz8rwc6a0lMeU5PekE3Q0U

OxygenOS OpenBeta3: https://drive.google.com/open?id=0B_f72wz8rwc6NVFfZVlSaUdjOW8

OxygenOS 4.0.3: https://drive.google.com/open?id=0B_f72wz8rwc6VXZVQVY5QWZORVE
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] technotravel:
Some feedback on microg with build 20170422:

- the fakestore (coming with microg) does not seem to work. I could not get whatsapp running correctly - it complained about the missing playstore while restoring the chats. Even after overcoming that and got it restored (don't remember exactly how I did), it never registered in the microg cloud messaging. Only after having flashed the playstore it eventually started working. Had this in the previous build already, though.

- I have quite some delays in the notifications while in standby, ranging from 10 minutes to 2 hours. For whatsapp, telegram and email. Couldn't find a pattern why it is sometimes shorter and sometimes longer.

Any hope that this will improve with future builds? Or hints how to get whatsapp working without having to flash the playstore? Would love to keep the phone free of google completely, but I need reliable notifications. Mail, fileshare, contacts and calendar all working to satisfaction through self-hosting and Nextcloud, so I don't need any of the google services, really. Just the notifications ...

Cheers

Chris
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
Experimental Build 20170426

Disclaimer: Since [MENTION=4405529]nvertigo67[/MENTION] is busy for the time being, he asked me to build and upload new ROM versions every few days.

This is an updated experimental build with OMS.

Some advice on Theme/OMS/Substratum users. You can ignore this, if you don't use themes:

Make sure you disable all overlays in substratum BEFORE dirty flashing.

If you ignore this, you get a force close of system-ui on boot.

To fix such errors, flash /sdcard/substratum/SubstratumRecovery.zip in TWRP. This will remove any OMS overlays and allow you to boot again.

To enable your Theme again, you must BUILD it, not only enable. Enabling it without building will make system-ui force-close again and requires you to flash the recovery zip in TWRP.

Changelog

I don't have changes. Shame on me. Rebooted Windows for gaming.

Of course updated to latest LaOS and OMS sources.

Note on firmware: This build requires OOS beta 5 firmware. If you get an TZ error while flashing, make sure to flash OOS beta 5 firmware first. It was included for users having flashed lineage-14.1-20170422-UNOFFICIAL-nvertigo-EXP-firmware-oneplus3t.zip.

ROM: lineage-14.1-20170426-UNOFFICIAL-mad-murdock-EXP-oneplus3t.zip

MD5: 8aa8df7ed35999ec47c8ea23d659f78e

Mirror: posting #2

Happy flashing!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
Hey, this might sound like a stupid question, but I don't want to flash the experimental builds as of now (I don't have enough free time to be able to recover my device if I screw up something), so I'm on 20170418, can I still flash the latest firmware?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
No. Firmware should always matched to ROM and included blobs (kind of drivers). That was OB4 for the 18 ROM, right?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
Yup.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Changelog:

Switch to our own version of merge script to keep the LineageOS reposmand just patch them for OMS - current version of Nathan's script would change the upsream path.

Updated these camera changes:

camera: hotfix for not forcing HAL1 and vanished hdr. — nvertigo

op3: Don't disable HAL3 mode — Sultanxda

op3: Use open_legacy — Sultanxda

op3: Bump camera wrapper hal3 device api version to 3.4 — dianlujitao

op3: Bump camera wrapper module api version to 2.4 — dianlujitao

op3: Set camera package name to OnePlus Camera — dianlujitao

op3: Add camera wrapper — codeworkx

Revert "audio: enable high_perf_mode." — nvertigo

added network traffic mointor to settings->statusbar

Note on the cam changes: with this changes nothing changed for Snap (same functionality; same issues [i.e. ffc crash on first shot]). OOS cam lost hdr, but can save raw images. Third party cam apps, like Google Camera or OpenCamera are working again - the latter with raw images and hdr, if you enable api2 in OC's settings.

You'll find the ob5 firmware (and uniblobs) in the OP or in this posting.

Test builds are not mirrored on a regular basis.

Firmware should match the one, the rom is build on: if you don't use a ob5 rom, you shouldn't use ob5 Firmware.

I completely understand your caution about EXP roms. On the other hand it's atm the only rom with ob5 firmware and if I would have put some serve derps in, we would have known from the first experimental. Remember: no new is good news. I consider the EXP as stable and if we won't receive any reports on issues and/or drawbacks likemstability problems or decreased batt life, I'll put OMS commits in the next regular build. I would say: if you have a nandroid the advantages (updated firmware, working HAL3) outweight the risks.

Note to the homebuilders: If you would like to build the current rom: there is a branch "cam-test" in local_manifest. Read the comments in my_pick.sh carefully and follow the directions:

ingo@adler /usr/local/src/cm14/my_tmp/local_manifest $ git show HEAD
commit 6247214aef79d1cc3871d273866843601ad798af
Author: Nvertigo <nvertigo67@gmail.com>
Date: Wed Apr 26 11:44:29 2017 +0200

merge OMS: don't touch manifests - we include ThemeInterfacer in local_manifests.

You need to clone LineageOMS/merge_script, i.e.:
git clone https://github.com/nvertigo/merge_script.git

You also need to adjust LAOSROOT and LOMSDIR accordingly.

Happy flashing! Happy building! Happy Happy!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Thanx for the feedback.

To my unserstanding fakestore only pretends to be playstore - not more, not less. If you need to use Playstore for authentication, you need to flash the microg+playstore zip. I needed playstaore as well for whatsapp as for navigon (payed app).

But I belive you get more competent answers on this in the microG thread.

That was the reason I switched back to gapps. You can disable batt optimization for those apps - at least wa is a batt drainer without this.

You are mixing up things: I do NO active development on the microG patches, apps and zips. I add the most current patches. If you are looking for current microG development information, updated microG zips or a mission statement of microG, please get in touch with microG developers i.e. in the xda thread: https://xdaforums.com/android/apps-games/app-microg-gmscore-floss-play-services-t3217616

Keep in mind: since microG is based on the documented api of playservices and quite some reverse enginiering, it has to be always one step behind all the proprietary **** in googles playstore.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] endursa:
[MENTION=4405529]nvertigo67[/MENTION]

I am currently using sultans unified rom, because I was having trouble getting NFC payment to work with your rom (using Open mobile api which was compiled for use in any rom from 6.x upwards https://github.com/johnzweng/platform_packages_apps_SmartCardService/releases/jz_android_6.0_OMAPI-2.05)

After debugging the NFC SWP connection to my sim card (which is nfc enabled and worked previously with my moto x 2014) I knew it has to be a software problem.

Since I could not get it to work with your rom, the next try was to use stock oxygen rom. I injected the OMAPI, got the nfc connection correct (slight changes to libnfc brcm and nxp) but my payment app did not work.

Next try Sultans unified lineage rom. same changes (smartcardservice apk, permission and framework file copied to system/... changes to the two libnfc files) and here we go, the payment app works like a charm! first try it recognized my sim card and everything is ok

I have a bunch of logs taken while using your rom which are attached here to maybe help and debug this!

MY guess is that is has something to do with the kernel, since that is basically the only difference between the two roms!

Alternative could be something regarding selinux ?