yashsingh1/xdaforums huggingface dataset:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I don't understand the logs. https://github.com/johnzweng/platform_packages_apps_SmartCardService/releases/jz_android_6.0_OMAPI-2.05, does not mention any rom or kernel related dependencies. In https://github.com/sultanxda/android_kernel_oneplus_msm8996/search?utf8=✓&q=omapi&type= there is nothing omapi related.

I'm a bit clueless with you logs. There is no single selinux denial and the only errors (from BOTH files) are:

03-31 17:37:07.768 8895 8895 E ßöå : buildtype: PROD
03-31 17:37:07.772 8895 8895 E ßöå : LOAD RELEASE BACKEND
03-31 17:37:07.927 450 1508 E ANDR-PERF-OPTSHANDLER: Failed to read /proc/sys/vm/swap_ratio
03-31 17:37:07.927 450 1508 E ANDR-PERF-RESOURCEQS: Failed to apply optimization [11, 3]

I'd be happy to add a kernel patch allowing your payment to work, if you would be so kind to drop me a pointer. I'd be happy to avoid your app running into selinux denials by adding such rules, but then I need logs containing the denials. Sorry, but I'm still clueless on this.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] endursa:
Ok thanks for looking into this, I will try to get you the logs you need.

The problem is that the payment app is obfuscated and thus this is the only entries i get in logcat :(

I will setup an installation tomorrow and try to replicate everything that is possible.

I also did try to contact the app developer but so far to no avail.

Trying to find the differences between your kernel and sultans is to much i would guess since he is using a caf based kernel and you are on oxygen base ?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
LAST CALL

If nobody expirienced any impacts from the OMS patches on stability, performance and/or batt life, I'll add OMS permenently to this rom.

You can consider [MENTION=3044422]mad-murdock[/MENTION]s (thanx, dude) build from yesterday as release candidate.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I have serched the [MENTION=4800121]Sultanxda[/MENTION]' repo. I FOUND NOTHING related. If the logs have dinials you can send me them. AGAIN: I would like to add keenel patches or sepolicy rules - I do NOT have ANY knowledge of omapi, and therfore CAN NOT (I'M NOT ABLE TO!!!) debug the proprietary app.

Even if I would diff our kernel against sultans, and go through that line by line - I have no idea what to look for...

If you have denials in your logs (grep avc: logfile) or if you have a patch, please send them, otherwise you are on your own, sorry.

EDIT: if I recall correctly sultan's rom is unrooted. Have you tried to unroot in twrp just before boot the rom the first time and before installing the app?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
Does ANYONE use one of the experimental builds without themes? If so, were there any problems flashing the second (my) experimental build over the first? (I dont think there is, but written proof would be fine)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Chaz9999:
Excellent ROM! Stock OOS (+ Beta 5) couldn't get Android Auto working so I had to explore custom ROMs, but stock Lineage, Experience, RR all had higher temps than what I experienced from OOS.

Finally found one that works with AA, conveniently builds in Magisk (for Pokemon Go), and gives great battery life with low phone temps.

Thanks again! Donate ahoy!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] goosebickel:
Have flashed both experimental builds, not had any problems with lag or battery drain.

Not using any themes.

Dirty flashed both times.

Still on recommended gapps from op.

Great ROM, been using it from day one.

Thanks for all the hard work and time you put in.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
[MENTION=4405529]nvertigo67[/MENTION] no clue if the following are (known) LOS bugs, or only happen in your build, but:

After recording the screen with the default app, and stopping the recording, after a random amount of time the floating record widget re-appears, only way to get rid of it is by starting and stopping recording. Usually this gets rid of it until I actually re-open the record app, in rare cases only a reboot fixes it.

By going to Dialer -> Settings -> Calling Accounts -> *sim* -> IMS Settings, the app just crashes. I've reported something similar a few months ago, which you have fixed, this one isn't a major issue at all (I have no idea what IMS settings should be), just curious if this is known at all?

When asking Google Assistant to call someone for the first time (eg. "Call Mom"), she asks "Who is your mom", but doesn't give you the dropdown menu under contacts. If you tap on contacts however, you can select a contact, but Google Assistant hangs afterwards.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] wistlo:
I am not using themes at all with these builds.

Sequence:

20170418 > 20170422 with firmware, dirty flash followed by Magisk uninstall/reinstall as recommended > 20170426 dirty flash

In each update, I also flash a small second .zip with some additional ringtones (just copies .ogg files into system media directories).

No problems observed.

In all cases, using Kernel Adiutor to switch to Conservative governor at boot. I control night use with inside-the-app dark theme options, and CF.lumen Pro, with root and daytime/sunset/night modes.

Good battery life, accumulated run-time about 30 min so far on 20170426
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] PerryRhodan:
Dirty flashed the latest 3 builds and no problems.

I'm not using themes.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
First of all: thank you to all giving feedback, since it's very important information to decide on OMS!

[MENTION=7264930]Lada333[/MENTION]: Can I assume, that you don't answer [MENTION=3044422]mad-murdock[/MENTION]s and my requests? You are speaking genarally, and not about the differences after bringing up OMS? Or have these issues shown up, after OMS waa merged?

I just checked this (with and w/o theme applied): working like charme here. After starting the recording, the widget disappears and never shows again after stoping the recording.

Yeah, this is known. When they tried to fix it upstream complete sim settings were crashing. Since we have ims package installed, I have no clue, why it is crashing (obviously I'm not the only one failing to understand.

I don't use online speech processing for privacy matters. If I should guess: assistant doesn't like laos (aosp) dialer - and/or vice versa. Perhaps some other using onlne speech proccessing wants to jump in here?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
Maybe installing (oh I hate to say it, I will be haunted) GOOGLE dialer from play store and setting it as default dialer might fix this. I do this and get nagged about it by [MENTION=4405529]nvertigo67[/MENTION] all the time :P Of course, I also dont talk with my phone and have not idea, if it fixes the problem.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] yannmrt:
I didn't install yet the last experience ROM still with 0422. So far all Good with everything, I don't use theme and only gapps.

Thanks for your work and time
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
I don't use it often either, I just noticed it a few days ago, and what I find weird is that it used to work before. I remember it working perfectly with Google Assistant a few builds prior, oh well, it's not that big a deal for me to do a clean install.

Thanks for your answers!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
Okay, just finished upgrading to the latest exp. build (by mad-murdock), oddly enough, when tapping on Magisk manager, I didn't get taken to the play store, it just worked fine (maybe because I haven't installed the first experimental build?)

substratum works just fine, installed quite a few themes (mostly for the sake of testing), no slowdowns or bugs at all, I'll post here though if I find any bugs

God bless [MENTION=4405529]nvertigo67[/MENTION] [MENTION=3044422]mad-murdock[/MENTION] <3
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] reddevil08:
Clean flashed the exp-build by nvertigo and then dirty-flashed mad-murdock's exp-build over it.

Absolutely no issues here. Have been using a mixture of themes like compound and swift black. The rom performs smoothly with and without substratum.

If you accept feature requests, then can you maybe add the option to turn on volte symbol in the statusbar. It helps a lot as volte sometimes drops out and without that symbol you don't know about it until you call someone.

Thanks for the awesome rom!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Removing OMS again!?!?!

Not using this feature, doesn't mean I don't care. If "call xxx" stoped working due to OMS patches, it's a showstopper and I'll drop OMS again. To be sure you are right, we need some more information:

What was EXACTLY the last version "call xxx" was working?

What was the EXACT setup (gapps version, dialer version, substartum installed at all, theme applied, etc)?

Does it work with google dialer?

Is this reproducable on a clean install with only beans gapps mini installed (system has never seen substratum, nor any other apps)?

This is very important, especially the fourth point on the list. Since I'm low on time, I need your help here. Otherwise I'll remove OMS again, even if OMS is only suspect to breal "call xxx". I'm meaning "@all", when writing you.

If anyone missed the beginning of this conversation: if you want "OK, Google" to dial contact "xxx" by saying "call xxx" it won't happen.

[MENTION=7264930]Lada333[/MENTION]: Have you tried what I implicitly and [MENTION=3044422]mad-murdock[/MENTION] explecitly suggested: check if google dialer works better with ok google? (And I really need to know the exact version and setup, which worked last!)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Do you have any pointer to an existing implementation?

I looked in the source. To my understanding I can check if the device has volte enabled when no voice call is active, but I can only check if volte is currently used if a voice call is active. Maybe I'm missing something here.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
Uh, unfortunately I don't remember what the last version it worked on was, I'm pretty sure it was before upgrading to 7.1.2.

The last time I clean flashed was about when I started posting in this thread, so about 2 months ago, since then I've been dirty flashing both your and mad-murdock's builds, with nano GApps. Dialer is whatever comes pre-packaged, I also tried setting Google Dialer as default app, didn't make a difference (see attached screenshots).

substratum is acting up again, does the same things I had to restore a backup a few months ago. I have had Google Pixel UI pack and N Navbar pack installed (since Pixel UI failed to apply the navbar correctly). Now, after disabling all installed packs, removing them, uninstalling substratum, and rebooting the device, I still have the Pixel boot animation, and the Pixel navbar (from N Navbar), no clue how I could get rid of them.

I'm pretty sure I haven't applied any substratum themes to dialer/GA., so it's probably not thanks to the theme engine.

EDIT:

I made a profile backup with substratum before disabling and uninstalling everything, now that I restored my profile (which had all the mentioned themes enabled), it got rid of the Pixel Navbar completely.

EDIT2: I totally didn't forget to attach the screenshots:

https://dl2.pushbulletusercontent.c...jojyq19csLxpQd/Screenshot_20170430-103935.png

https://dl2.pushbulletusercontent.c...ft29wAk5giezwE/Screenshot_20170430-103942.png
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] reddevil08:
The other ROMs I tried were VertexOS and Phoenix AEX. Both had the option to turn the volte symbol on/off. It was in the systemui tuner in Vertex. It's usually in the list that shows which icons are shown in the Statusbar.

In LOS, it should be in the list under Settings>Statusbar>System Icons

I hope that helps. Thanks for looking into it.

---------- Post added at 10:36 AM ---------- Previous post was at 10:14 AM ----------

I'm using mad-murdock's exp build with beans gapps. I dirty flashed that build over nvertigo's exp build(which I clean flashed)

I'm using Swift Black(and sometimes compound) to theme the dialer and I'm not using Google dialer.

When I ask Google assistant to call a relative e.g. "call my brother", it asks me to select who my brother is. It gives the option to select my brother from contacts or I can simply say the name and it gets selected through voice. I've tried doing it both ways and it was successful, no crashes on my end.

So OMS is definitely not the cause of "call xxx" not working.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
I suppose I could just clean flash to solve the issue then.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] xpissio:
Hi all! Is it too late for reporting my experience with the experimental build of mad-murdock? (2017-04-26) :)

First of all, I flashed the build coming from FreedomOS. (So OpenBeta 5 firmware was necessary)

I'm using the ROM with a Substratum theme (Pixel UI), and I can confirm that Google Camera works. (I'm using 4.3.016)

All running fine, no problems.

Thanks for your hard work and for this amazing ROM! ;)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
Yo, where did you get Google Camera from?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] xpissio:
Can I mention APK Mirror? :D
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
Oh okay, that's what I thought. It was available for a while in the Play Store, guess they removed it again :|

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

(Feel free to remove this comment if the linking is inappropriate)

Okay, I've downloaded this, installed it, and it crashes just as I open it.

Downloading older versions, while they start up, I get an error saying "can't connect to camera" after a few seconds.

I should do a full wipe and start from scratch, shouldn't I [MENTION=4405529]nvertigo67[/MENTION] ?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] reddevil08:
Hey [MENTION=4405529]nvertigo67[/MENTION], I tried looking for the volte implementation in vertexos and found these 2 links

https://github.com/VertexOS/android_frameworks_base/commit/27923b34d9ff73698293ddde5f9cbcd5a6e7ec5e

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

I don't know much about this stuff but I'm sure you can make more sense of it.

Hope it helps.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
That's quite some config chaos, isn't it?

What do you think?

Let me wonder about this [sarcasm]non-trivial[/sarcasm] question... Yes, of course, what else???

May I be allowed to remember as polite as possible:

If you dirty flash without issues you are fine - if issues occur: clean flash and reproduce before reporting an issue.

Use common sense to solve/report/test an issue.

This discussion about "call xxx" and my code searching took all of my yesterdays and todays spare time. [MENTION=3044422]mad-murdock[/MENTION] and me wanted to know, if we can use the OMS patches and move on with making this rom better. Mayby it was just the wrong time for your posting after [MENTION=3044422]mad-murdock[/MENTION]s and my feedback request, but you really swnd me down the debugging road for something, which isn't a problem of the rom, but you local installation. I belive with a little bit of brainwork you could have found a better time and context. I try to care for the matters of users of our rom. But to do so without hunting for phantom issues,mI depend on the users common sense and a bit of empathy. Most of the time this works in this thread - thank you all for this!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Don't know, why gcamera is not searchable in playstore any more. Just follow this link: Google Camera in Playstore

[MENTION=535343]all[/MENTION]: please stick to xda rules - not only - regarding external URLs (I know, nobody has done this, so far). Thanx
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Will check them out. Again: I'm afraid it only shows on what device and carrier negotiated on their last handshake, and not "what would actually be used, if a call would be active, now". We will see...

These links are exactly what I was looking for. I'm not lazy (ok, on activities like home- or paperwork I am lazy - but not on emerging and supporting this rom), but I use my spare time atm for OMS, rebasing and maintaining additions and cam debugging - ah, and for doing support here - so you can consider your findings as extremly helpful: thanx.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] reddevil08:
You are welcome. Glad I could be of help.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
If present, delete "/data/property/persist.camera*" and reboot. Even if gcam is working then, do a clean flash with recommended beans mini gapps.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
My apologies for asking of solving an issue/any issue instead of doing a clean flash every time I face one.

Yeah, sure, since nobody else confirmed having the same issues (especially today, when multiple users have reported *not* having the same issues as me), I indeed could have just done a clean flash.

Don't blame me though, I have never commented saying "Your rom is bad because this and that doesn't work, fix it", so I suppose you guys wouldn't have had to start debugging, just test it on both of your devices, if it works for you, just tell me that I've ****ed something up, and do a clean install.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] coalee:
Hi

I have no problem using "OK Google" to call someone. It just works. I am using latest experiments version (dirty flash from previous version) with OMS theme applied.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] lapapunk:
[MENTION=4405529]nvertigo67[/MENTION]

Hi. Man, thank you so much, for your work, and for the oms ( now it's so beautiful). I was absent for a while time (about one month), becouase my display was crashed and I was waiting for new one. And after all, when I already replaced new lcd, I was so glad to see, that you continues create builds.

Thanks.

Latest exp build is fine, with recommended gapps (BeansGapps-Mini-7.1.x-20170415 ). All cameras is working now. Oms too, without any kind of issues. So there is no reason for deleting oms.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
[MENTION=4405529]nvertigo67[/MENTION] [MENTION=3044422]mad-murdock[/MENTION]

Hey, oddly enough, not another bug report, just something I noticed this morning.

TLDR: I wiped everything from my phone last night (inc. internal storage), went in for a clean install, this time I installed a different ROM, and even there, Google Assistant refuses to call people.. Well.. Sort of..

Remember the screenshots I attached in my original report? Well, that still happens, I still do not get a dropdown menu, but after closing GA, and telling it again to call someone, the dialog sort-of continues.

After the re-launch, it asked me to remember <contact name> as <nickname>, I said yes, and from now on, I can call them.

Since it's not working as intended for me on two different roms (before anyone thinks that, no, I'm not at all blaming the roms, I'm pretty sure I ruined my phone somehow lmao), and it's probably not a GApps bugs (I'm sure I had this malfunction on your rom without upgrading my GApps), does anyone have any clue what I've done wrong?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] ngradt:
Love this rom!

Did a clean install with gapps and was experiencing steady battery drain making it a poor daily driver... did a dirty flash of the rom after a few days and it fixed the only problem I had in an instant!

Keep up the good work, love the features and stability so far :) :)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Switch off your device. Take a notepad and note EVERY SINGLE step you take from here. Every step. Do a clean flash (rememmber to umount system after wiping!) and only(!) flash beans gapps mini. Continue noting every single step (or tap - for that matter)! Boot up the device and set it up. Set up "ok google" and assistant. (while writing down every tap). Now do your tests. Post your notes here.

Please give the exact versions of packages, you are using.

Nobody here is clairvoyant (to the native speakers: I looked up the german word "hellsichtig"; and hope this phrase is correctly used - feel free to help me to learn, if there is a better phrase), therefor it is important to know, what exactly you are doing. You won't belive how many different actions are done, when people claim i.e. they've done a "clean flash".
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I was on the right track: you can ask for what is negotiated, but not whats going on right now. To do the latter we need some more logic. At the moment there is some work in progress for volte:

https://review.lineageos.org/#/q/topic:ims-notify

As you can see, there are some serve merge conflicts. Since I'm low on time and the conflicts on frameworks/base are quite complicated (and having microg, dash charging shown on lock-screen [comes within the next regular build later today or tomorrow] and OMS patched in here, doesn't make it better), I decided to wait to put it in till the gerrit topic is rebased (let do it the dev, who wrote the patches... ;) ).

I know: waiting suckz, but - at least - you know now, I have not forgotten about the volte icon.

EDIT: more waiting: just finished a clean build, when I found OpenBeta6 ready for download. I'll update blobs to ob6 and rebuild... stay tuned... I'll try to upload today.