yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] dingsaller:
[MENTION=2380313]VVMM[/MENTION] true, HDR button is crossed out, don't know too what HQ exactly means/does.

Tried also 2.10 (night shot option but slow motion doesn't work in 2.10).

Quick research

https://m.gsmarena.com/oneplus_3t-review-1531p8.php

there's the HQ mode explained

Better canera suggestion welcome ....
[OnePlus 3 & 3T Cross Device Development] tfae:
GCam from Tolyan009 aka TlnNeun.

I'm using MGC_6.1.013_B-S-G-based_v.0.4_TlnNeun.apk with no issues apart of the well known: no SlowMotion and black viewfinder on Night mode.
[OnePlus 3 & 3T Cross Device Development] uttam.ace:
I am using GCam MGC_6.1.013_B-S-G-based_v.0.4_TlnNeun.apk on LOS 16, pretty satisfied with performance.
[OnePlus 3 & 3T Cross Device Development] VVMM:
I gave it myself a try, it seems that it works. So far so good. I haven't tried slow motion & night mode, but at least it didn't lag/crash for me since installation.

What I noticed is that the "black images when using flash with no HDR" issue is persistent also on OnePlus camera from apk mirror and not only Google Camera. Is this a driver issue that needs to be fixed in this ROM? I would have thought that the drivers/blobs present in LinageOS contain all the requisite libraries from the official OxygenOS build.
[OnePlus 3 & 3T Cross Device Development] Dirk:
This is a GREAT read and may help people understand the difficulties involved:

https://www.xda-developers.com/came...opers-make-hardware-work-without-source-code/
[OnePlus 3 & 3T Cross Device Development] :
In a perfect world every vendor woukd use api2/HAL3 in the complete stack from the apk over camera- and mediaserver over the closed source blobs down to the kernel driver. In the real world OnePlus uses api1/HAL1 for op3/t and implements some api2/HAL3 functions via callbacks on top of api1/HAL1. Additionally the blobs work in different ways according to the name of the camera package.

There were different attempts to reverse engineer the proprietary callbacks and iplement them in custom roms. Sadly, that's much more complicated then it sounds, and you would need to put different sources for i.e. cameraserver in the custom rom's source tree for op3/t and all other devices - which is practically impossible for source tree's serving more then only op3/t devices.

Considering this [MENTION=5091734]dianlujitao[/MENTION] and [MENTION=4800121]Sultanxda[/MENTION] are real coding jedi's getting snap to work at all on our devices.

EDIT:

Funny enough: even in oss all issues due to the proprietary callbacks are present. In deed the los implementation is much better then oss...
[OnePlus 3 & 3T Cross Device Development] tfae:
Did OnePlus fix this on 6/6T?

I somewhat predict a "no" as your response, but…
[OnePlus 3 & 3T Cross Device Development] :
I don't know about op6/t.

It's important to understand that there is nothing to "fix" from OnePlus' point of view: in oos the proprietary solution is working properly, and for oss the cam is considered as "working good enough"... :(

https://github.com/OnePlusOSS/android_hardware_qcom_camera/issues/1 (OnePlus' NULL answer to the last request in the comments is speaking for itself... :( )
[OnePlus 3 & 3T Cross Device Development] tfae:
Well, they call themselves a "community driven company" and they encourage custom ROMs, so they need to release fixed blobs if they want to support the community.

Wouldn't OOS benefit with a proper HAL3 implementation? Maybe they need to redo a lot of code to make it work on full HAL3 implementation, but once it's done I only see benefits for them.

One of the reasons many keep with OnePlus devices is because of the community support!
[OnePlus 3 & 3T Cross Device Development] :
OnePlus is the only company that offers an oss source tree: the open source community support from OnePlus is better then from most other companies. Unlocking the bootloader voids the warranty of most devices - not so for OnePlus devices!!! That's why I prefer OnePlus devices.

Nonetheless, companies are driven by money - that's the definition of a company. Everybody saying a company is driven by community is a liar. Sales departments - of course - never ever lie... ;)

EDIT:

Carl Pei: "Going forward, we actually want to be known as having one of the best cameras" from: https://www.xda-developers.com/interview-with-carl-pei-from-oneplus-pt3/
[OnePlus 3 & 3T Cross Device Development] tfae:
Exactly! Having an unlockable bootloader that doesn't void the warranty is what makes OnePlus devices so special for the developers and the community.

And again, OnePlus highly benefits from this symbiosis with the community. If I didn't like OOS (it's not the case) I would still buy a OnePlus device knowing I could freely unlock the bootloader and flash a great ROM.

But knowing that they don't correctly support developers and the community the best way they could, it's becoming a turn off for me… This bad camera implementation is a big bummer to me.
[OnePlus 3 & 3T Cross Device Development] :
You don't need to convince me! I love foss!

I've only tried to show you, why it is so hard to get an acceptable camera. The same goes fpr OnePlus' attitude: I havn't meant I like it, I've meant to show you what it currently IS.

If you want to start a petition, I'll sign it. If you want to write an open letter to OnePlus, I'll sign it.

I completely agree with you: if OnePlus would make OOS open development with a gerrit instance, I'm pretty sure most devs here on xda would contribute, so that not only custom roms would profit, but also OOS (I don't know if any legal issues would be violated - i.e. non disclosure agreements to qcom and google). But if I read the conversation on the github I've quoted earlier, I'm afraid all petitions, open letters or what ever won't change OnePlus' state of mind.

Bottom line: though OnePlus' as a company is surely not community driven, and quite some proprietary parts of soirce is holded back, it's by far the best support for the open source community we can get today.
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
Every other company is doing the same thing - not releasing anything to the devs...

So I think OP is a step ahead of the other companies.

At least they are releasing anything of their sources to the community - and also allowing to unlock the bootloader.

On other phones, you aren't even able to unlock the bootloader (without using a major security breach) and as a result using any custom rom...

The only difference to the other companies is that OP is says that they are community friendly.

And up to a certain extent - they are!
[OnePlus 3 & 3T Cross Device Development] tfae:
We don't need them to open their sources, because there are indeed some legal issues involved. That's why they release blobs — and we gotta love them for doing it!

But they just need to do a better work for themselves. As a developer, knowing that part of my code is not the best implementation possible bugs me. That's why I can't understand their options related to the HAL3 implementation.

But, we are already going way too long on the off-topic :p
[OnePlus 3 & 3T Cross Device Development] Dirk:
Speaking of which:

Why did it travel from the Status Bar to the Quick Settings? Did it change energy level and Quantum Leap? You can't explain that!

Here you are Google. Fixed that for you:

While i'm busy making improvements, why not an upgrade to the Google Phone In-call UI?
[OnePlus 3 & 3T Cross Device Development] mk_1996:
I won't mind if you share her number Dirk. Asking for a friend ofcourse?
[OnePlus 3 & 3T Cross Device Development] highdiver_2000:
I need to test this too!:)
[OnePlus 3 & 3T Cross Device Development] dferreira:
No problems here. Camera, Google apps, Magisk all ok. Battery life is very good too. Waiting for the official rollout. Running experimental one.
[OnePlus 3 & 3T Cross Device Development] P4M30:
Are you using LOS camera? I was thinking about ditching Oxygen OS for this ROM and was wondering how good it is compared to Oxygen OS camera.

I've heard good things about Google camera, but I really don't want crashes in my camera app, so I'm a bit wary of using it.
[OnePlus 3 & 3T Cross Device Development] Diaze:
For me the latest 15.1 has setup wizard fc. I tried with sever gapps
[OnePlus 3 & 3T Cross Device Development] drmcatchr:
Try in this order: Official Build > Unofficial OpenGapps > MindtheGapps ..
[OnePlus 3 & 3T Cross Device Development] Diaze:
Flash gapps 2 times or ?
[OnePlus 3 & 3T Cross Device Development] UTI0:
[MENTION=5091734]dianlujitao[/MENTION] I have seen on multiple post's that LOS has been "optimized" for Treble does that mean that LOS team is experimenting with repartitioning of supported devices including OnePlus 3/3T or I'm bad at English so I got it wrong.
[OnePlus 3 & 3T Cross Device Development] redhand:
I have the same problem with FC.

Do I need to flash build, then flash unoffical gapps, then flash mindthegapps and after that start the phone?
[OnePlus 3 & 3T Cross Device Development] drmcatchr:
MindtheGapps doesn't have much (any) Google Apps in it, But you need to flash it to rectify the Setup Force close.

---------- Post added at 02:13 PM ---------- Previous post was at 02:06 PM ----------

Flashing the Unofficial Gapps is upto you. You can flash just the MindtheGapps package and then install the Google Apps later from the Playstore. I prefer to have it all installed in one go. But to prevent the Setup FC, you need to flash the MindtheGapps package which contains the SetupWizard.apk that rectifies the setup from force closing.
[OnePlus 3 & 3T Cross Device Development] redhand:
So maybe I had bad MindtheGapps. I flashed LOS and then MindtheGapps and I had FC.
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
I don't have Android Wear devices, can't reproduce your issue so can't fix it.
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
I don't take care of any app level features
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
LineageOS has been optimized for Treble doesn't mean OnePlus devices have been optimized for Treble. At least their proprietary camera driver doesn't meet Treble requirements. You should know that any OSS Android distributions heavily rely on proprietary drivers from device manufacturers. Even though it's 100% possible to use the 1.5G last_parti partition as /vendor so that it "looks like" a Treble device, there's 0 possibility to bypass Google VTS and end up getting a "fake" Treble device. We can build OSS camera HAL from CAF source which matches Treble requirements, but comparing with proprietary camera HAL there's a huge picture quality regression. From my point of view there's zero benifits and endless trouble from the trick and I have zero interest with such games.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Just going to mention this in case anybody runs into the same situation:

Plugging my newly Oreo laden OP3T into my PC to transfer some files, there is no prompt in Notification area to switch from Charging to MTP, so PC doesn't see phone at all. There is however, an option in Developer Settings to choose what mode to be in. Default is 'Charging'. Change to MTP and PC can see phone and transfer files.

People running Oreo/LOS 15 before now might have encountered this already, i don't know. Useful to know for those who haven't.
[OnePlus 3 & 3T Cross Device Development] megatomic:
My most recent attempt to fix the Google app stopping messages was to dirty flash the experimental build and wipe cache/dalvik. It's been 30 minutes so far and no Google stopping messages, hopefully this did the trick.

---------- Post added at 09:29 AM ---------- Previous post was at 09:18 AM ----------

I think I'd like to mention that EVERYTHING else in my OP3T is working flawlessy. I'm running the official Google camera and phone apps and both are perfect. I'm not a huge camera buff but the results from the Google camera are good for me and my family. I tested it on my granddaughter and my puppy and I see no difference between the pics from the OP camera and the Google camera. Phone calls are what you expect, no one has complained about my end and I am hearing the other party just fine. Audio output via Pocket Casts and Blackplayer EX are great. WiFi and cellular speed tests using Ookla Speedtest are identical to what I had on OOS 5.0.1. Battery life remains to be seen but so far it's not been an issue.

And even though I am(was) getting the Google has stopped messages none of my Google services were impacted. Aside from the message box needing to be confirmed to make it go away I noticed no ill effects.

So that's my mini review. YMMV but I am super pleased with LOS15.1.
[OnePlus 3 & 3T Cross Device Development] goodoldie1996:
Will there be a official build coming today? Or should i flash the experimental build?
[OnePlus 3 & 3T Cross Device Development] xpissio:
https://jenkins.lineageos.org/job/android/10362/
[OnePlus 3 & 3T Cross Device Development] IAMSPINI:
They said that today is the day....
[OnePlus 3 & 3T Cross Device Development] qhsusb_bulk:
Official nightly is coming in few minutes. Exciting. Take your backups ;).

EDIT:Finished succesfully, mirror: http://ftp.acc.umu.se/mirror/lineag...age-15.1-20180226-nightly-oneplus3-signed.zip
[OnePlus 3 & 3T Cross Device Development] BRDigung:
When is the nightly is out, what are the right steps?

When do I update my firmware and modem? In step 5? Which firme ware and modem.are recommended?

1. Download everything you need, of course.

2. Boot into recovery

3. Format system partition

4. Install lineage 15.1 build without reboot

5. Gapps, su or magisk
[OnePlus 3 & 3T Cross Device Development] nasbdh9:
https://ftp.acc.umu.se/mirror/linea...age-15.1-20180226-nightly-oneplus3-signed.zip
[OnePlus 3 & 3T Cross Device Development] Vency77:
Hello,

After a fiasco with the Beta to Stable OOS transition and the

stupid

stock recovery, I got fed up and finally installed LineageOS on my 3T. Back to custom development and XDA feels good, wont lie :cowboy:

After a day or two of usage, I am suspecting a problem with my battery life. SOT is one thing, but what bugs me the most is the fact that last night I lost more than 10%. I think I got used to losing 1-2-5% overnight with OOS (they do some things right I guess..). So the question, is this normal or am I missing something? I will surely leave it some more days to settle (or do we "never settle" here too? :D ) and collect more detailed battery usage data, but wanted to be sure that I'm not missing something obvious. Applications are the same, 27.11 nightly, the most usage is for "Android system, Screen, Phone Idle and Android OS".

Thank you in advance!

P.S. Been a while since I've used AOSP and this 'Do not disturb' thing is kind of confusing. Is there a way to make the slider switch to "Vibration only" and leave my notifications intact?
[OnePlus 3 & 3T Cross Device Development] cukierkas:
Install bbs app from XDA or gplay market. It will show you the culprit. Another thing, first couple cycles after fresh install are always power hungry, just because all apps are building itself comfortable situation. Relax.
[OnePlus 3 & 3T Cross Device Development] SuperEvil:
I am getting poor network and call reception in 15.1

whereas OOS 5.0.7 works fine.

The signals kept on flickering
[OnePlus 3 & 3T Cross Device Development] andrew2511:
That's because OOS has boosted signal indicator and AOSP ROM don't. You'll notice that the the dbi you get are the same but the indicator is "higher" on OOS. No joke. However I don't remember who discovered this
[OnePlus 3 & 3T Cross Device Development] SuperEvil:
Okay.

Then by any means i can get good cellular reception?

Improve dbi?

The only problem i am facing.

other than It's Better than OOS.

Battery Backup is the best part.
[OnePlus 3 & 3T Cross Device Development] Dirk:
What you're seeing is a different interpretation and representation of signal strength between ROMs. OOS is designed to show an inaccurate and optimistic version of the true signal strength in it's status bar. LOS displays a truer image that responds more quickly to the varying conditions.

Instead of relying upon the iconography in the status bar, what you should be reading is a report of the actual signal strength at any given time, as in the screenshot below:

Compare to this table:

---------- Post added at 12:29 ---------- Previous post was at 11:41 ----------

i) Move closer to a cell tower

ii) Improve line-of-sight to cell tower

iii) Install a femtocell

iv) Hold phone above head and wave arms about

v) That's it. I'm out of ideas

Bear in mind that there's nothing you can do about contention. If your provider is over-subscribed and doesn't have the necessary capacity to deliver a good service, the only recourse is to switch provider. (Assuming a better one is available).

I myself am struggling to get any service at work today on either 3G or 4G, despite the fact that i'm practically sitting on an antenna! Some providers simply suck.

More info:

https://www.reddit.com/r/oneplus/comments/9ww8fm/misleading_signal_bars_on_op6/

This build.prop business is crying out for further investigation, if anyone wants to tackle that? Specifically, does it exist on all OOS builds and what effect if any setting it to '0' has.
[OnePlus 3 & 3T Cross Device Development] pharandeamit:
Same with me on every custom Rom Oreo or Pie. I'm on Jio VoLTE network & BSNL network in India... But BSNL sim gets better Signal other side Jio VoLTE gets poor signal with flickering... But on Havoc OS i get better Signal for Jio VoLTE on their Oreo 8.1 or Pie based Rom.... I don't know how :confused::silly:
[OnePlus 3 & 3T Cross Device Development] :
Do you really get different dbm values in different roms? I highly doubt that, since all roms - no matter if source build or closed source - use the very same hardware, kernel driver and ril blobs. Since we have no pie blobs, yet, this is also true for oreo and pie roms.

What exactly do you mean by flickering?
[OnePlus 3 & 3T Cross Device Development] Dirk:
No ROM can affect the signal. Only how it is displayed.

The signal is affected by your physical proximity to the Tower, line of sight, how far inside a building you are, what the building is constructed of, how you hold your (i)phone, if you have your phone wrapped in tinfoil, live in an anechoic chamber, contention, weather and some other factors that i'm probably forgetting.

Edit: Interference.
[OnePlus 3 & 3T Cross Device Development] pharandeamit:
The new update showing in OTA 02-12-2018 but why not it's updated here on thread or in download page here- https://download.lineageos.org/oneplus3
[OnePlus 3 & 3T Cross Device Development] Dirk:
ROM is on daily builds so the thread doesn't need a daily announcement. Download page does show the 12/02 build now.

This page is more useful imo:

https://www.lineageoslog.com/15.1/oneplus3
[OnePlus 3 & 3T Cross Device Development] Narren:
Wondering about vibration settings for the notification slider myself. Would be nice to have some control over vibration in do-not-disturb mode. Or maybe to be able to assign different profiles to slider positions would do it.
[OnePlus 3 & 3T Cross Device Development] pharandeamit:
+1
[OnePlus 3 & 3T Cross Device Development] Vency77:
Not natively supported I'm afraid. I also doubt that it could be implemented in any variation, too custom and too device specific.

The good thing is that the settings allow us to set each position to 'none' so we can completely override the behaviour. A tasker profile for example will be fairly easy to implement (with root and maybe selinux change).
[OnePlus 3 & 3T Cross Device Development] :
Adding something device specific is not the problem:

https://review.lineageos.org/q/topic:tristate-vibration

The kernel patch for msm8996, would look like this: https://github.com/nvertigo/android...mmit/ba5f0b44d6601f8695643119a53a209ca2de89bc

The problem is the last comment in this one: https://review.lineageos.org/c/LineageOS/android_device_oppo_common/+/215212

Since most devs are working on 16.0 now, I'm afraid the "other approach" will never come - but I may be wrong.

For now you have three options:

take it as is.

use an unofficial los build or a los based rom with the above patches applied.

wait for the "other approach".
[OnePlus 3 & 3T Cross Device Development] Narren:
"Do not disturb" mode generally could use some vibration settings IMHO. It just happens that on 1+ devices it is bound to slider.

I think I will wait for this "other approach". In a mean time, I'll probably use profiles instead and ignore slider. Thanks for clarifying.
[OnePlus 3 & 3T Cross Device Development] DarkSJ1998:
Same thing happened to me too a few weeks back. Decided to go old school & install LOS on my 3T after I got bored of using OOS for an year. But couldn't find the vibrate only mode for Alert Slider setting. Hence, moved to other ROM.

Then I got some recommendations from peeps here on XDA & they told me that NLOS by [MENTION=4405529]nvertigo67[/MENTION] has that option. You might want to try that. It's really a great option. ;)

What a coincidence, I use the same providers as you do. BSNL @ 2G in SIM 1 & Jio @ VoLTE 4G in SIM 2.

I got a really bad network connectivity in Jio while I was on NLOS recently (don't mean to point NLOS specifically). While, I do get decent connectivity on OOS. Didn't know about that boosted "false" notification indicator. But in practical usage, I've noticed data connectivity improvement on OOS, atleast in SIM slot 2.

And, IMO, the 3/3T Support 4G VoLTE equally in both the slots, not like those devices in the market that do in only SIM 1 slot [emoji14]
[OnePlus 3 & 3T Cross Device Development] :
Is playstore certified and safetynet passing?
[OnePlus 3 & 3T Cross Device Development] xuser_:
How LOS's built in profiles (under battery section) affects the profile we set through Kernel apps?
[OnePlus 3 & 3T Cross Device Development] dimon2242:
Yes.

After reflash ROM with wipe data problem solved!:p
[OnePlus 3 & 3T Cross Device Development] :
Wrong place to ask. The dev of the kernel app should now.

The profiles in los utilize qcom's perfd to adjust kernel settings (this is not limited to writing values to files, but also by writing op codes directly to the kernel). This is done dynamically (meaning some values are adjusted i.e. depending on cpu load - not only once when the profile is activated.

This rom doesn't know of any kernel apps, so it's the task of the kernel app to take care of perfd profiles and avoid races - disabling perfd profiles alltogether would be one way to deal with. Only the kernel app dev can tell you.
[OnePlus 3 & 3T Cross Device Development] 洛城天使:
Vibrate on connect/disconnect not work for me? anyone the same?
[OnePlus 3 & 3T Cross Device Development] Gotolei:
I've since upgraded to an OP6, but personally I ended up just working around it with Tasker. In system-level settings, the top and bottom slider positions are set to do nothing, and the middle to "complete silence." The middle position is important because that means the ringer state changes any time the slider is moved. In Tasker, a profile of "Variable Set %SILENT" is triggered, which runs a task that checks the position the slider is in (root shell command: cat /sys/devices/virtual/switch/tri-state-key/state) and stores it to a variable (%Slidernew in the screenshot's case). From there it's just whatever logic you want it to be, just make sure to check that the slider position has actually changed since last the task was run because the profile ends up triggering itself infinitely otherwise. The limitation is that the middle position has to be set to something that Tasker can pick up on, and if you move the slider too fast it doesn't catch it, but the method does leave the top and bottom positions free for whatever you want.

(For a while I also had a really hacky way of doing it that ran a shell script every ten seconds which updated a file in /sdcard and triggered a profile that way, but it's safe to say this way is much more sane)

It would indeed be nice if there was some proper built-in customization for it, though. Or at least a vibration option.