yashsingh1/xdaforums huggingface dataset:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
Having OMS7 in the ROM enables you to download and install the substratum app to apply themes - or more correct: to apply overlays.

How and where to put - for example - the battery percentage is in the hands of the themer. He can put it to every location or disable it. Hell, he can make it blink in pink if he wants to.

Be aware though, most themes cost a dollar or two. Having a glimpse about how much work it requires I can understand this, on the other hand it hurts me a bit, that there are no good free themes around.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
[MENTION=4405529]nvertigo67[/MENTION]

only error i could find is this:

05-24 09:57:29.136 9212 9212 W System : ClassLoader referenced unknown path: /data/app/projekt.substratum-2/lib/arm64

I fixed it. I made a log from booting and adb becoming available to the PC side until boot was done and I started substratum - it's attached to this post.

Also logcat'in only for Error, Fatal or Warning while starting substratum didnt show anything suspicious to me.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
UPDATE

Build 20170524

Releasenotes:

This build requires firmware OpenBeta 7 (aka ob7). Camera implementation has changed slightly, though I don't expect any problems, if you expirience any unexpected behavior of camera apps: wipe data of all theses apps.

Changelog:

change cam implementation according upstream:

overlay: Snap: don't force open_legacy to false. — nvertigo

op3: Don't disable HAL3 mode — Sultanxda

op3: Set camera package name to OnePlus Camera — dianlujitao

op3: Add specific camera parameter library — dianlujitao

op3: Remove camera shim library — dianlujitao

init.qcom.rc : Add time_daemon in init.qcom.rc — Mao Jinlong

op3: rootdir: Update fs tune from marlin — Luca Stefani

op3: Update to OB16 blobs — dianlujitao

Revert "Enable Tethering" — nvertigo

op3: Disable tethering provisioning for all carriers — Sultanxda

my_pick.sh: add "fw: Don't consume home key press when long-press to sleep is used."

ROM: lineage-14.1-20170524-UNOFFICIAL-nvertigo-oneplus3t.zip

MD5: cfda6c6c45457221e58c632be5dea40e

Happy Flashing!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Fixed in 0524. Thanx!

I think we need to have an eye on the home button, since this patch https://review.lineageos.org/#/c/168903/ (patch set 2) is more current - the same issue is present on double-tap on home button. Sadly, I found this just 5 minutes ago. The patch you pointed my to (thanx) is patch set 1 of the gerrit change. Next build will be even better then this one... *lol*
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] serious96:
in the new build, built in browser. there is no tab indicator, and no swipe gesture adress bar to change tab too. so i can't change to another opened tab.

edit: turn out we can change tab using recent apps button, all tab are listed there
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I removed Gello on user request three or four builds ago - shortly after that lineage declared Gello dead. SincemI don't know if and when Jello will be introduced. For now we have to use aosp browser - no other choice atm.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
I believe Lineage has replaced gello with jelly.

https://www.lineageos.org/Changelog-9/
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
This conclusion is not true:

ingo@adler /usr/local/src/cm14 $ repolastsync
Last repo sync: 24 Mai 2017, 18:01:14 CEST / 24 Mai 2017, 16:01:14 UTC
ingo@adler /usr/local/src/cm14 $ grep -r Jelly .repo/manifest.xml
ingo@adler /usr/local/src/cm14 $

After reading this article I'm not even sure, if Jello is planed to ship on our device, or if it is only "made for devices that couldn’t handle a heavier browser such as Gello and/or Chrome". Anyway, atm it's not shipped on any device.

(I know how to include Jelly, but I don't want it atm.)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] m0d hipp¥:
Can I suggest looking at Pyrope? That's what I use and I really like it.

https://play.google.com/store/apps/details?id=com.ninnix96.pyrope.browser&hl=en
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
That's not true. Jelly is shipped on official LOS builds for 2 of my other devices: OnePlus 2 and Moto G 2015 (osprey)

But I don't like jelly. I use chrome dev.

---------- Post added at 10:36 PM ---------- Previous post was at 10:35 PM ----------

Doesn't inspire confidence. Hasn't been updated since last year.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] wistlo:
EDIT: I also wanted to ask, does anyone use the built-in browser (whatever version) on the 3T? How about an older device, such as HTC M8? I presume most people install CHrome or Dolphin. The built-in is essential if only to access download sites for more advanced tools. </EDIT>

Jelly is the default browser in 20170524.

I tried it, looks like a lightweight Chrome.

Given the beastly power and 6 Gb of Ram on the 3T, I use Chrome Beta as my default browser.

In principle, Android or at least Lineageos should ship with a light as possible browser that can run on slower, more memory limited devices, and then let the user decide whether a more fully-featured browser is needed.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Both of you are right. I was confused, since Jelly is not included on per device basis (like Gellomor Snap), but it's build by default from vendor/cm. I have to check, how to build aosp browser instead. Thanx for heads up!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
UPDATE (ob8)

Build 20170602

Releasenotes:

This build requires firmware OpenBeta 8 (aka ob8). The firmware update is included in this build.

Changelog:

Update all blobs to OxygenOS OpenBeta 8. — nvertigo

UPSTREAM: lz4: fix wrong compress buffer size for 64-bits — Bongkyu Kim

UPSTREAM: zram/zcomp: do not zero out zcomp private pages — Sergey Senozhatsky

UPSTREAM: zram: pass gfp from zcomp frontend to backend — Minchan Kim

proc: Remove additional SafetyNet flags from /proc/cmdline — Sultanxda

op3: rootdir: Enable ZRAM for msm8996 targets — Diogo Ferreira (HEAD -> swap

op3t: init: update to OxygenOS OpenBeta 8 build fingerprint. — nvertigo

sepolicy: Substratum: allow plattform_app to getattr on system_app_data_file:dir. — nvertigo

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

MD5: 308a58a8453c834d2ee3f2661b35ee5f

Happy Flashing!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] serious96:
i know we can flash renderkernel build (and i already tried it. it works), but without rom side support we don't have a Vox / PowerHAL function. [MENTION=4405529]nvertigo67[/MENTION] considering that this rom already stable, will you add EAS support?

https://github.com/EAS-Project/android_device_voxpopuli
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
That's right.

If this is a feature request: do you have a pointer to an working patch, that doesn't break current power hal implementation, I'll look at it.

As mentioned before: I'm very low on time till November.

Extremely low on my priority list. Bad effort-advantage balance: why should I spend a complete weekend (that I don't have till November, anyway) to increase batt life by <5% (if at all in real life UX)?

BTW: if I implement this voxpopuly stuff in the device tree, my rom wouldn't run on a non-EAS kernel. You are suggesting to break my rom for all non-EAS kernels - including laos stock kernel. As you can easily guess: never ever! This link also doesn't cover kernel patches.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] technotravel:
Uhm, I am hit by the recent nasty removal of Magisk Manager from the playstore. I cleanflashed the latest build ... should have gone for dirty, I guess :-S

What is the best way to proceed here, to get Magisk running?

Cheers

Chris
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
Ya but hopefully OnePlus officially switches to EAS soon since everyone is claiming it's the future. Don't know how true that is though.

---------- Post added at 10:04 AM ---------- Previous post was at 10:03 AM ----------

Get the magisk​ manager apk from the magisk thread or XDA labs
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] technotravel:
Thanks!

Anybody else looking for the apk - here is the link to XDA labs

Cheers

Chris
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] endursa:
I just came in to say, that I switched to your rom again today because I had troubles with my front facing camera on sultan's lineageos release.

Now the bank card app works flawlessly! Also the front facing camera works. But the OoS camera does not have her support. Is this on purpose? I guess I has something to do with all the hal1/3 shananigans?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Do you mind to elaborate? It's working exactly like before the cam changes. (Including the ffc first shot crash... ;) )
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] endursa:
God damn autocorrection :)

I ment to say OOS camera does not have hdr support, besides that it works great!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
This is working on current build. Did you clear data of all installed camera apps?

Clean flash? You do not need to flash any HAL switcher zip - in deed this would break the current camera implementation for many apps.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] endursa:
I did a clean flash of the latest build 20170602 with minimal gapps. Also I did not flash any hal changer what so ever.

I have OOS camera as well as snap camera installed. Snap camera has the hdr option.

OOS cam only shows hq mode, but no hdr. I tried clearing cam app cache and storage, did not change anything.

I also tried installing Google camera, which works perfectly, even slow motions is available. But also no hdr option.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Finally somebody understands me: of course I thankfully take the additional whatever % of bat life - without the need to spend time on it... ;)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Hotfix for OnePlusCamera

Google camera didn't had hdr before the switch. But I never relly looked into that. I'm occupied with looking into Snap and OnePlusCam... ;) I guess, that's one of the reasons, why google does support its cam on a limited number of devices.

OnePlusCamera Hotfix

I forgot to include the modded camera again, after updating blobs... Just copy the attached file to /system/priv-app/OnePlusCamera/OnePlusCamera.apk (either with a root enabled fs browser or via twrp with /system mounted), check for fs access rights (-rw-r--r-- or 0644) of the copied file and discard com.oneplus.camera's data.

Will be fixed in next build.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Hasn't been asked before. Most people understand, that I mention only additions that are actually added in OP, but no additions you will NOT find on my rom.

No and no. I have to take this as two seperate questions, since "or" doesn't make any sense at all to me.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
It's basically a stock LOS, but more optimized, but no extra customizability features, all additions are listed in OP, or like the first 3 posts.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] endursa:
Thanks, works like a charm!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
Haha I understand your position. Regardless, maybe you'll find reading about EAS interesting.

https://xdaforums.com/oneplus-3/one...nt/kernel-render-kernel-t3505956/post72557100
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I don't think we have "no extra customizability". We have a customizable root solution. We have the choice to use microG or google gms. What is OMS/Substratum about, if not customizability? That's some of the reasons, why the "or" in the other guys posting makes no sense.

Reading the first postings is always a good idea, but to know, what is added over plain laos, you need to read only the first paragraph of OP.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] 1337iceskater:
Question on VoLTE

Hi team,

I was very happy to find a ROM, which is considered stable and has that much customizing options and tweaks for OP3T.

I will do a flash of this, but I am still having a question:

1. I have currently an issue with OOS, where my Voice over LTE option is missing - just as many other users as well.

As VoLTE is mainly a software issue - and as other users have this option visible - I am thinking of a bug in OOS.

Could someone please check, if LOS with the current build allows Voice over LTE to be enabled?

Thanks for your help!

Regards
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
UPDATE: security patch level

Build 20170606

Releasenotes:

This build requires firmware OpenBeta 8 (aka ob8). If you does NOT come from last build, you need to flash this firmware first.

Changelog:

Update security patch level to June 5, 2017

OnePlusCamera: add modded Camera. — Kevin Mckee (indeed: readd ;) )

Merge tag 'LA.UM.5.5.r1-04700-8x96.0' of https://source.codeaurora.org/quic/la/kernel/msm-3.18 into HEAD — dianlujitao

Revert "op3: rootdir: Update fs tune from marlin" — nvertigo

ROM: lineage-14.1-20170606-UNOFFICIAL-nvertigo-oneplus3t.zip

MD5: be22572f7040dcefee70c194a8b2f181

Happy Flashing!

[MENTION=313982]home[/MENTION]builders: you need to use branch swap for device and kernel, and 141-work for vendor to build the current version (no branch for that in local_manifest - just use 141-work and checkout swap on device and kernel manually).
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
OnePlusCamera: modded versions

I unpacked the oxygen version and @kxzxxx's version. Put it in a git. Finally I redid the changes on the oxygen version without adding the libs (we have them in /system - no reason to add it twice.

The version we have in the last build is kxzxxx's version. It's in the branch "kevins-mod". From the next build on we'll use the libs-less version from the branch no-callbacks (no changes in functionality, just smaller because of not including the redundant libs).

If you want to look at the changes to the modded versions:

https://github.com/nvertigo/OnePlusCamera

If you want to use the libs-less version just copy this OnPlusCamera.apk to /system/priv-app/OnePlusCamera/OnePlusCamera.apk, check fs access rights (-rw-r--r-- or 0644) and delete the app data.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] endursa:
[MENTION=4405529]nvertigo67[/MENTION] quick question regarding gps, sultanxda had an entry in changelog regarding gps fix and I really had the fastest gps fixes on his rom. Can you implement them as well?

Unfortunately I do not know where to look for that
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Time, time and time... :( The changes in [MENTION=4800121]Sultanxda[/MENTION]'s device tree aren't trivial - at least to me. Also I don't know if kernel changes are needed. To check this, I would need time. Or a teammate, who collects the needed commits. Also: honestly I had to admit, that I have a deep understanding of how gps works in aviation, but I never digged in gps sensor programming. ATM: Sorry, no.

In my trailer (build from aluminium) it takes 3 - 6s (the same on OOS) to get a gps fix. In my car's phone mount under the front window it takes 2 - 4s (the same on OOS). I don't say it can't be faster, but it isn't a show stopper, neither. (For the record: last time I tested OOS it was 3.5.4 - may be it's faster on 4.x.x.)

I'm always willing to improve this rom. I'm always willing to incorporate user requests. I'm always willing to accept help.

Sadly this rom is a one man show at the moment.

My complete spare time is consumed by keeping the rom up to date (merging, rebasing, building and creating changelogs) and doing support here. The latter is very important to me, since just pushing the build without support and reacting to user feedback is NOT what I consider supporting a rom...
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Which build from [MENTION=4800121]Sultanxda[/MENTION] are you talking about? I'm asking because of these:

https://github.com/sultanxda/propri...mmit/09899a5becf1843772c9197f479a8f5e79a68d35

and

https://github.com/sultanxda/androi...mmit/52d31f9044250dd8105bed449683a080752117fe

At this very moment these are the only differences:

9043443

b197d2e

10909fc

5800c6e

78179ca

I'll try to cherry-pick these five commits and doing a test build. But I'm afraid you want the implementation [MENTION=4800121]Sultanxda[/MENTION] has reverted?!?!

Who wants to try: use device's branch sultan-gps.

EDIT: sultan-gps is merged on top of swap. You need kernel's branch swap and vendor's branch 141-work.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] endursa:
the changlelog for the gps fix was for the rom from may 19th! so this should be the commits sultan was refering to in his changelog.

Btw you are extremely awesome, my op3t would not be as awesome without you investing all this time into the rom as it is! so please do not feel obliged to fix everything :D i was just asking if you could!

unfortunately i do not have the environment to build a kernel by myself but i am willing to try any testbuilds if you can share them somehow

also gps is not broken, but it is wonky to describe it best, sometimes the fix is really fast, as you describe and sometimes it takes forever to find gps even though gps status (app) shows that enough satellites are in view! with qualcomm location stack commits i always had a fix really fast!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
I love your work :victory:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
TESTBUILD: sultan-gps

No kernel changes. Just the 5 changes I mentioned (and the new modded cam app). Funny: most times it's VERY fast (2s aluminium shielded) - but while testing perhaps 6 or 8 times, I had one of 51s... Perhaps a one time incident. Needs testing.

Here, we go:

BUILD 20160606-nvertigo-gps-test

Releasenotes:

Requires ob8 firmware.

Changelog:

OnePlusCamera: change to modded apk without libs included. — nvertigo

Show "gps-test" in the build name. — nvertigo

op3: Don't override GPS settings set on a per-carrier basis — Sultanxda

Revert "oneplus3: Disable premium location services" — Sultanxda

gps: Update to CAF LA.UM.5.5.r1-04000-8x96.0 — Sultanxda

oneplus3: Disable premium location services — Sultanxda

oneplus3: Use SUPL version 2.0 — Sultanxda

ROM: lineage-14.1-20170606-UNOFFICIAL-nvertigo-gps-test-oneplus3t.zip

MD5: bcd16672baa72b5ba6648e03db0c3597

Happy testing!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] endursa:
thanks for the rom! i tested gps today morning on my way to work, and it worked flawless, first fix was 12 seconds, fastest fix afterwards 2 seconds, and so far really consistent!

i will keep testing and report back
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Thanx for the feedback. Please keep testing! (see below on why)

For me it works the same as before. The "over 50s fix" never ever occured again. The fixes are as fast (or slow) as with the laos stack (depending more on weather conditions then on the difference of the two implementations).

I would like to ask everybody to use the gps-test build: since it makes no difference for me and it's working better for [MENTION=1444259]endursa[/MENTION], I'll considering putting this changes to the rom, if nobody complains on any regressions with gps. Now is the time for checking out gps changes. You don't risc anything when trying gps-test: it's the very same build as 0606, but the gps stack - you can savely dirty flash between them (nandroid always strongly recommended).

Thanx in advance for your feedback.

I'm also interested in feedback on volte. 8 weeks ago I was in a region, where the connection was said to be lte+ (icon in statusbar) and I had speeds of 102 MBit/s with vodafone.de. I'm pretty sure volte was working (connection was still signaled as lte+, when a call was active). Now I'm in a region where I can get only lte (without the "+" sign). Max download speed is only about 36 MBit/s. And volte is NOT working: falling back to 3G when calling. I can't be sure, if vodfone.de is just not supporting 150MBit/s connections and volte where I'm now, or if volte got broken sometime during the last 8 weeks.

I may be wrong, but to me it seems that hsupa (the download speed would match) is used here on the country side, which is sgnaled as lte, but doesn't support volte... Anyway: testing of volte (don't forget to enable Settings->SIM Cards->Mobile network settings/SIM ? settings->Enhanced 4G LTE Mode: enabled) is needed. Thanx in advance.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] endursa:
regarding VoLTE unfortunately my provider has not actived it yet, i regularly have LTE+ reception, but always 3g/2g fallback for calls :(

Gps working fine so far, played some pokemon go on my bike and very fast fixes, i did force a few gps "reconnects" with reopening the app. All worked great.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Great news - the part on gps fixes. Scary new - the part on playing pokemon while cycling... ;) Take care, dude.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] buzzqw:
Hi

great Rom!

would be possible to add customizable date in panel ?

thanks

BHH
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] AhmadAlmousa:
I've done a quick test yesterday and gotta swift lock. However, my problem with the GPS used to be that it disconnects intermittently. For that, I'll have to get back to you tomorrow since I'll be conducting multiple trips at different conditions.

Thank you so much for the effort and support ?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
Should I stick with ob8 firmware or update to 4.1.5 firmware?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Since the TZ has not changed it could be possible. Both current builds relay on ob8 - as stated in the Releasenotes. I recommend using the firmware, the build is based on (and I only support this configuration!).

On OxygenOS 4.1.5 update: atm I have not decided, if I go from ob8 blobs to the ones from 4.1.5. I want to check first, which blobs are the latest, regarding features and bugfixes of the blobs we are using. As far as I can see from OnePlus so called changelog i.e. aptx is still missing in !OpenBeta. To make a n educated decission I need to unpack the full rom, and put it in my local oxygenos git and see, what exactly has changed. Sadly, http://downloads.oneplus.net/ is still recommending 4.1.3. I'm waiting for their download page to be updated.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
https://xdaforums.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074/post72592024

That's the download link from their official servers linked in the post.

I think you should stick to ob8. Because apparently 4.1.5 still lacks the touchscreen fw fix among other things.

Can you tell me more about what these "blobs" are supposed to be? And where I can learn more about them? (Different from firmware right?)

And yup I almost always read most of what you post, even if I don't understand all of it, so I know the last 2 builds use ob8
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mcdachpappe:
i havent noticed any negative effects since you decided to implement sultan's gps related commits. i wouldn't even say that gps fixing is faster than before.. for me it was always quite fast.

it seems that it doesn't hurt to keep these changes.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] wistlo:
I had to clear GPS data to get a fix, but after that it's been solid. Fixes with marginal sky visibility (in house, inside a streetcar) seem faster.