yashsingh1/xdaforums huggingface dataset:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
EDIT - Forget everything I've said (well, maybe except for the last part, I'm still unsure as to what caused, and what fixed the problem)

After wiping my phone again, and restoring my backup (using latest, 20170502 nano GApps), "Okay Google" works again, so does "call <sb>"

-1: Backed up current ROM with TWRP

0: Copied over "BeansGapps-Mini-7.1.x-20170415.zip", "lineage-14.1-20170426-UNOFFICIAL-mad-murdock-EXP-oneplus3t.zip", "oxygenos-ob5-firmware.zip" from OT/@mad-murdock's post (#5 I think)

1: Unplugged phone, rebooted into recovery (TWRP 3.0.4-1)

2: Wipe -> Advanced Wipe -> Ticked "Dalvik / ART Cache", "System", "Data", "Cache" -> Swipe to Wipe

3: Recovery home page -> Install -> "oxygenos-ob5-firmware.zip", "lineage-14.1-20170426-UNOFFICIAL-mad-murdock-EXP-oneplus3t.zip", "BeansGapps-Mini-7.1.x-20170415.zip" (in this order)

4: "Reboot System"

5: Entered pin, unlocked screen, tapped on next, selected language (EN US)

6: Start as new (This isn't what I usually tap, because AFAIK it only downloads my apps I had installed from Play Store, if this ACTUALLY makes a difference, please correct me)

7: Connected to WiFI network, logged in to Google

8: Skipped FP setup for the sake of quickness

9: Had everything as default (Automatically back up device data, Use Google's location service to help apps, Improve location accuracy, and Help improve Android experience)

10: At Google Assistant setup added my voice and viola:

"OK Google" detection works, so does "Call sb".

Now, as you might have figured, I'm not very smart myself, but could this be a GApps bug?

I remember using nano OpenGApps on both your LOS build, and on apascual89's RR, (I gave RR a try after doing a full wipe (so like 2-3 days ago, can't remember, isn't that important anyways)), and on neither did "OK Google" detection, nor Google Assistant settings work.

There's a menu in GA settings (long press home button, press on 3 dots, and settings) called ""Ok Google" detection", so I suppose that because I wasn't able to get to the settings (always got an error saying "No connection, please try again later" (or something similar)), it didn't even attempt to look for the hotword.

I've seen many people report "OK Google" *not* working for them either in the RR forum post, where the guide doesn't specifically ask us to flash Beans Gapps.

Since I do not want to stay on this freshly installed LOS, and set everything up again, (and if OpenGApps really is the cause of the problem), is there any way to get rid of the currently installed OpenGApps on the backup I made, and install BeansGapps Mini? Could I just flash BeansGapps, and would it get rid of the currently installed Gapps?

Again, thank you so much for your help, appreciate you taking time to deal with my crap!

PS: I suppose you can use "clairvoyant" like that, but "visionary" would fit it better imo. Yet again, I'm not a native, so don't take my word for granted.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] reddevil08:
No problem, thanks again for taking a look even though you were low on time.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] technotravel:
Yay!

Flashed the latest microg, together with a clean flash - and now it works! The notifications, that is :)

Still have to do some more testing, but it looks really good. Whether this is the new microg version, or me finally understanding what clean flash really means (unmounting system ... noob me) I don't know. But I want to encourage all the people out there trying to live a life without google services: it IS possible. Might take some time and fiddling, but in the end it pays off. And this ROM does a lot to support it - thanks again!

But maybe I was too fast, as a new version is arriving - will I be able to update it OTA, or do I have to go through the whole clean flashing process again? Hesitating to already put my fingerprints and to proceed to personalisation ... these tasks take longer than the actual flashing! :D

Greetings from a happy Chris
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] wistlo:
Instead of “clairvoyant”, perhaps “omniscient” is a closer matching English word? It means “all seeing” rather than “future seeing”.

Looks like it should be pronounced “omni-sigh-ent“ but true to quirky English, it's “oh-mish-cee-unt”.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
[MENTION=7264930]Lada333[/MENTION]:

I don't know. Most propable reasons may be one or more of: artifacts of settings (i.e. persistent properties - should be gone after clean flash, but who knows...), missbehaving third party app, settings, permissions, bug in gapps themself, bug in gapps package...

For completeness: gapps suckz!

[MENTION=5702613]technotravel[/MENTION]:

Now, as you mention the microg update, I remember having read about some api changes in the gservices messaging stuff. Propably microG has caught up. I don't know, since I havn't tested, so I'm guessing (but I'm quite good in guessing... ;) ): go ahead with microG OTA update, no need to clean flash again (as stated: take this with a grain of salt).

I'm really happy if people use microG and write on their expirience here. Sadly, I have not the time to dive into all this gservices stuff and use microG myself. Untill November I relay on in time whatsapp notifications. I would like to use microG myself and doing much better support for running microG on this rom.

Feel invited to close this gap: perhaps you want to write a step-by-step HOWTO. I would link that in OP.

Anyway: thanx for reporting.

[MENTION=5825970]reddevil08[/MENTION]:

You're welcome.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Oh, yes, that makes semanticaly sense to me.

And propably the the ponounciation differs from a Cambridge graduated BBC documantary speaker to someone from Australia or the United States...

Thanx, man. Enough OT - I have to unpack a roms zip. Download will finish anytime now...
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
Is there a way for me to uninstall GApps, and install BeansGApps instead (without having to do a clean flash, obviously)?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
Neither seems quite right. Might wanna use perceptive/psychic/mind-reader.

Also, being a "native" speaker doesn't necessarily mean that you have a mastery of the language that a non-native speaker cannot achieve.

Edit: omniscient is the perfect word.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
UPDATE (regular stable again - no test or EXPerimental)

Build 20170503

This build requires firmware OpenBeta 6 (aka ob6). This build ships with this firmware.

Currently Beans Dynamic Mini Gapps are confirmed to work for clean flashes. (I highly recommend to stay with installed gapps on dirty flashes!)

If you have used the EXPerimental builds, some of the following may be well-kwon to one or the other, but I strongly recommend reading again!

This update is a BIG step: OMS patches added, MagiskManager is no longer shiped, network traffic monitor added to status bar, lockscreen shows "Dash charging", updated firmware & blobs to name the most important changes. A clean flash is recommended!

If you decide to dirty flash remember to accomblish this:

Disable AND deinstall all overlays, sounds, fonts, boot-animations andmbackgrounds.

delete persist.camera.* from /data/property .

Wipe dalvik, system and cache - check if system is unmounted (it's really important, please belive me).

Flash rom and the exact gapps zip, you used to setup your current installation.

If have booted back to system go to playstore and uninstall MagiskManager. Then install it again. You do not need to leave plqystore in between.

Check settings of MagiskManager

Changelog (relative to the last REGULAR build):

Security patch level bumped to 5th of May.

Update all blobs to OxygenOS OpenBeta6. — nvertigo (see: https://https://github.com/nvertigo...mmit/cbdaed3b744ad78038a429ebbf131167080f4a70 for details)

microg: rebase our patches. — Nvertigo

magisk: delete magisk.zip after flashing. (This is only cosmetics, but left over install files are ugly and bad programming style.)— Nvertigo

magisk: rebase our patch. — Nvertigo

op3: Add missing & remove unused blobs — dianlujitao

op3: Update to OB14 blobs — dianlujitao (This is just to keep our source base konsistant with laos - our blobs are from ob4)

op3: Sort blob list — dianlujitao

init: set build description to OpenBeta5. — nvertigo

blobs: use aptX binaries from OxygenOS. — nvertigo

overlay: add some missing overlays. — nvertigo

Magisk: don't ship Magiskmanager. — nvertigo

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

add traffic-monitor to statusbar.

lockscreen has learned about Dash charge.

ROM: lineage-14.1-20170503-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip

MD5: 975dac1e47712540a24369ecec2f9e2c

Happy Flashing!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] horqai:
Thanks nvertigo for all your work. Just one little remark... Link send me to 404

There are some paragraphs added at the end. This should be the correct one

https://drive.google.com/file/d/0B_f72wz8rwc6UGVmWFVmUFpWTzA/view
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] spida_singh:
Same here
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
gDrive (win google drive client) puts a linefeed at the end of the URL when copying to clipboard... I forget that regulary... ;) Thanx for the headsup!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] xpissio:
Just flashed the new build. Only one thing, on OOS camera, there is no HDR for photos, and no 1080p60fps for videos.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
Might be related to the hal1/hal3 thing. https://xdaforums.com/oneplus-3/one...official-lineageos-14-1-t3588696/post72110191
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
...but you can save raw images... ;) If we use forced HAL1, oos cam has hdr, but no raw image and vice versa for HAL3.

Using forced HAL1 (to be accurate: system wide force HAL3 disabled) mode breaks some third party cameras apps. If we don't force HAL3 disabled, ww can use both HAL versions at the same time.

Drawback: the app has to decide which HAL should be used.

I configured Snap (our laos standard cam app) to use HAL1lmand it works like before. For OOS cam I have no source (closed source app - of course), so fixing this is not that easy. If I find the time, I'll look into that.

For now I've decided, that an app (oos cam) which is no native part of laos (hey, we all here have decided to have laos on our devices, and not OOS) is not so important like not castrating the complete system for ever from HAL3.

BTW: gcam is no longer crashing, and with opencamera you can switch between HAL1 and HAL3...

The strange point: oos cam can only do hdr, when used with HAL1, but saving raw images is only available with HAL3. I'm really curious about what oneplus is doing in oos to have both...

If you don't want to use multi-HAL just disable it i.e. via cli (as root) with the command and reboot:

setprop persist.camera.HAL3.enabled 0

To enable multi-HAL again delete /data/property/persist.camera.HAL3.enabled and reboot. Or you can use the HAL3 disabler zip from the ported oos cam thread.

When fideling with this property always remember as long as this prop exists, the HAL is forced either to 1 or to 3 - to have both HALs the same time active this prop has to be entirely abscent!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mumapizza:
Rom works great, oms support is great, beans gapps work great. Thank you
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] spida_singh:
Dirty flashed latest build, all OK so far, using open gapps nano
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] PerryRhodan:
The rom works really great. Thank you!

I did it, too. But had battery draining. Nearly 30% at night.

My fault. After clean flash with beans gapps it is perfect.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] xpissio:
I noticed one thing. When battery is around and/or under 15%, I have some little lags and fingerprint is slower than normal.

(Maybe it's a normal thing, never noticed this)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
https://xdaforums.com/oneplus-3t/development/rom-lineageos-14-1-t3547024/post71207930#post71207930
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] 186Y:
Have you been dirty flashing with this specific gapps "open_gapps-arm64-7.1-nano-20170120.zip" or any other? I have been dirty flashing the past 5 builds with that and haven't had any crazy battery drain like yours.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] PerryRhodan:
I flashed clean with latest open gapps. Should be around 04/27.

Phone was getting really hot and battery was draining.

I'm not a pro in battery analytics, so GSAM or the regular battery info didn't show me anything that makes it easy to find out if the gapps really was the bad component in this game. But after reading the first post again I saw that I missed one thing...the right gapps.

And now it just works :)

After a clean install I just need to reboot once more, because some Apps in store are showing, that they are not compatible with my phone. After reboot every App can be installed.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] smarvel:
Thank you for this awesome Rom!

Can anyone help me how to get HDR and 60 FPS/1080P in OOS Camera working? Can't find it.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Last three paragraphs: https://xdaforums.com/oneplus-3t/development/rom-lineageos-14-1-t3547024/post72143714#post72143714
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] smarvel:
Thank you for reply!

Doesn't work for me. I can only save RAW images either way.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] cmattern:
At least in my region it's pronounced

om nish int
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Have you tried to delete apps data? Reboot after setprop and deleting data?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] smarvel:
Deleting app data fixed it! Thanks man, really appreciate it!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] ArchGalileu:
Browser crashes in some addresses

It is very annoying.

Any solution or advice?

I'm with the last version of the ROM

Best regards

ArchGalileu
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
Yeah, use Chrome.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] cmattern:
Hey [MENTION=4405529]nvertigo67[/MENTION] and [MENTION=3044422]mad-murdock[/MENTION], I ran into a mount that I don't think we should be referencing in my-pick, here is the output that makes me think so

......
Applying: BatteryService: add dash charging support
~/android/cm14
Press ENTER...
my_tmp/local_manifest/my_pick.sh: line 59: /mnt/export/data/src/cm14/my_tmp/merge_oms/lineage_oms_merge.sh: No such file or directory

or should I be pulling something else in that I missed?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mhoppi:
Nice trick with the oos camera. The camera app is part of the oneplus 3t that I don't want to miss. 60fps video is just awesome.

Any chance we can still use hal 3 and hal1 in oos camera?

For now I will stay with hal1

Thx op for the great rom!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Tried that:

ingo@adler /usr/local/src/cm14/device/oneplus/oneplus3t $ git show 1d039ed
commit 1d039ed92c7ce3137db56f5c30a752a7ed44d54d
Author: nvertigo <nvertigo67@gmail.com>
Date: Fri May 5 16:11:08 2017 +0200

camera: add Snap and OOS to camera.hal1.packagelist.

Change-Id: I1756ccf77db89c49e69306e913818ed68c572727

diff --git a/system.prop b/system.prop
index d509178..73f1945 100644
--- a/system.prop
+++ b/system.prop
@@ -37,6 +37,7 @@ qcom.bluetooth.soc=rome
persist.camera.imglib.fddsp=1
persist.camera.llc=1
persist.camera.llnoise=1
+camera.hal1.packagelist=com.oneplus.camera,org.cyanogenmod.snap

# Display power reduction (FOSS)
ro.qcom.dpps.sensortype=3
lines 1-20/20 (END)

While this works for Snap, OOS Cam is though connecting to api2 (since it's there).

Since Snap is working with hal1 with the above property, and GoogleCam and OpenCamera are working great with our HAL3 (which is fully working and not broken, as many people claimed the last months), I tend to leave it this way. Who ever wants to disable HAL3 for using OOS Cam, can do so.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] cmattern:
Understood, thanks for the time, effort and patience.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I just switched back from my oms merge git to the original from LineageOMS.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
[MENTION=535343]all[/MENTION]: what do you think? Do you think I move in the right direction for the future of this rom? Without feedback and discussion I can't know what you are thinking.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
I'd still prefer to have OOS cam built in, and prioritized over Snap.

(Also, I still can't install Google Camera, it crashes after it launches, you recommended me to delete some files in order to get it working, but it didn't solve my issue ;_;

Any other tips?)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
May I ask what quoting my complete posting is good for? In regards to information it's just redudant noise. Why just tap the thanx button? I think it was invented to prevent such long postings, just to say "understood". Help me keeping the thread readable. Thanx.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
In which direction we decide, we have OOS cam onboard anyway.

I don't priorize Snap over OnePlusCamera, but a active HAL1 and HAL3 over a completly disabled HAL3.

Please remember, that OnePlusCamera is even with disabling HAL3, doesn't make it work issue free: raw sensor data can't be saved (of course, this feature of our sensors and socs is only available to apps in HAL3) and it's crashing on first ffc shot).

The question is: shall I ship with HAL3 enabled (people, who want to use only HAL1 can do so by issuing one short command and reboot), or with HAL3 disabled (people, who want to use the device as a semi professionell Camera with third party apps like OpenCamera or some paid apps or want to be able to save raw images, has to do so by unpacking boot.img, extrcating ramdisk, edit ramdisk, repack ramdisk, repack bootimage and flash the edited bootimage again)?

Google Camera from Playstore? Data and cache of gcam deleted? What files EXACTLY did you remove?

Get root in a shell on your device (terminal had to be activatetd in dev-ops). Give me the complete and exact output of "getprop | grep -i camera" and "ls -la /data/property/".
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] xpissio:
I prefer OOS camera, over Snap. :)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Egor Gunko:
[MENTION=4405529]nvertigo67[/MENTION]

Thanks, awesome ROM :3

But I in my opinion OOS's Gallery and Camera apps are working pretty good, so why you keep stock LOS's apps alongside them? Why don't you remove them? As for me, they are just bothering me...

Thank you for attention, and for your work ^^
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
As someone who works with photos and videos, I think you should keep shipping as it is. People who actually know what manual mode and RAW is, should be able to do some research and enable the correct HAL for their needs.

Uninstalled Google Camera completely, deleted the above mentioned files, and it still doesn't want to boot up

This is what I got:

---------- Post added at 06:41 PM ---------- Previous post was at 06:38 PM ----------

Tap & hold apps you don't want to use -> App info -> disable.

You won't see them in the app drawer for as long as you don't re-enable them.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
My personal policy for this rom:

I build LineageOS. There will be only additions, that don't break native LineageOS rom features.

Again: the question is not Snap or OOS Cam, nor is it about to priorize Snap over OOS cam or vice versa: Both are working as before. The question is if we want HAL1 _AND_ HAL3 shipped as default, or if we want HAL3 disabled by default. As allready stated: both solutions will work the same for Snap - so my policy is in place. The difference is only HAL3.

Get OpenCamera. Here you can select if api1 (HAL1) or api2 (HAL3) is used (of course only if HAL3 is not disabled). Check both for quality, performance (on focus, on taking pictures, especially with HDR and Expo).

At the moment I'm working on a solution to have a flashable zip to enable HAL3 again, which can be used directly while flashing the rom, for people not accepting dismissing HAL3 completly, for an single app. That would mean: nothing changes for those, who want HAL3 disabled.

Before I make a decission, what to ship as default (the opposite users will be provided with a flashable zip), I want to hear some more voices!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
I'd prefer it if HAL3 were not crippled.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
You did NOT! See below.

As you can see: persist.camera.HAL3.enabled is still there and preveting google camera to work.

Why can't you stick to directions you were given?

Accessing /data/property requires root previlgs!!! Perhaps this also happend on the attempt to delete /data/property/persist.camera.*. Don't ignore error messages and continue, but read and understand them and react accordingly. If a command fails, but you constantly claim you've done that, you cut off the solution...
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
I thought uninstalling the camera app was enough. Guess not.

Yet again, I can't code, but doesn't "persist.camera.hal3.enable=0" mean HAL3 is disabled?

Yeah, it gave me an error message in the terminal, but I have deleted those files multiple times, either via recovery, or via Solid Explorer (with root access granted obviously, else I wouldn't have been able to see the files either), and they were deleted successfully.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Yes. And once again just for you: Google Camera only supports HAL3. That means: if you have HAL3 disabled, Google Camera will not run.

As a matter of fact: the persistent property is still there. And as long as it's there you will NOT!!! be able to run Google Camera.

Can you clearly state what you wish to do? Run Google Camera or having HAL3 disabled to have hdr on OOS Cam - both at the same time IS NOT POSSIBLE at the moment.

Or do I completly missunderstand your wishes and give answers, that aren't matching your demands? Sometimes it feels for me like my answers are not understood - perhaps because I got the questions wrong.

EDIT: do we talk about the build from 20170503? Or have you setprop from the commandline? Or have you flashed the HAL1 enabler zip?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
Don't worry, it's most likely me misunderstanding quite a few things, I apologize for that.

Using siankatabg's HAL3 enabler got the camera working.

Sorry for bothering again >.<