yashsingh1/xdaforums huggingface dataset:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Vipeout:
Dear Mr. [MENTION=4405529]nvertigo67[/MENTION]

I have to make a confession. During this weekend, I have cheated on your Rom. On Friday evening I installed sultanxda's LAOS rom because I was curious about the custom kernel and other changes. To cut the story short, on Saturday afternoon I have already flashed back to your Rom from 22. June :D

I had some stability issue with the other rom (random freezes or spontaneous reboots for no apparent reason). The most hilarious bug I had was that my unlock swipe pattern sometimes wouldn't be recognized on the first try, so I had to do it twice and on the second attempt it would miraculously be recognized :rolleyes:

Anyhow, I'm happy to be back after less than 24h :D Haven't tested extensively, but the new GPS seems to be near-instant with position locking, gj :good: Last time I had a phone with truly fast and precise GPS and navigation was the HTC Sensation. Unfortunately, that was about the only good thing about it...

However, one problem I have been having for a while with your rom is that "OK google" is not working for me. I realised that I was using a super old gapps package from January which was recommended here back then. I just kept using that and updated via play store.

I have now installed the latest Beans mini GApps package and wiped cache + dalvik. First stime i said ok google it actually launched the setup wizard which I have compelted and registred my voice. But after the setup search/assistant is still not activated when I say ok google :confused:

Ideas?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I would say it's time for a clean flash.

If - and only if, in the current state of your installation this comes to late!!! - you have an backup of data, go to twrp-3.0.4-1 and wipe dalvik, system(!), data and cache. umount system. reboot to recovery. restore data from your backup from before your attempt to dirty update gapp. Make sure you are on ob9 fw. Flash latest rom. Flash Beans Mini. For feeding the paranoia clear dalvik and cache once more. This may work or not - even if it is working now, you may encounter issues after some days originating from this messy state of the installation... (Perhaps you want to read my longer posting from yesterday, to learn how to dirty flash without issues.)

I always (really many times, dude!) recommend reflashing only the package, the installation was created with.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Vipeout:
Goddamn I just clean flashed and setup my phone twice over the weekend, I was really hoping to avoid having to do it again :(

Thanks for your input, but I guess I'm gonna go the safe route and clean flash, again >.<

Oh well, here we go,will report back...
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] MickyFoley:
[MENTION=4405529]nvertigo67[/MENTION]: I've tried to find any clue, if you managed to get the Camera2 API correct working on your ROM. Searching the thread didn't get me a hint.

Could anyone using this ROM download Open Camera, switch to Camera2, cover the back of the phone and look, what ISO-level is the maximum? If nothing got hacked together, it should state max. 799 1/16,7s and the bug isn't fixed.

I know, it's a thing for OnePlus & requesting a working HAL from any dev here is really selfish - but I had to ask: Any way to get this working? Sultan once managed to do a custom HAL.

For the bug itself from the Open Camera dev: https://forums.oneplus.net/threads/camera2-api-bugs-for-3rd-party-camera-apps.506100/

Thanks in advance.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] TheGatorade:
799 1/16.7s yeah. Lastest version of this rom and open camera.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
The point is wiping system: factory reset does not wipe system. Icould have said: do factory reset and wipe system, which is the same as "wipe dalvik, system, data and cache". Again: most issues on clean flashing is not wiping system. So you are right, but missed the point, that factory reset does NOT wipe system!

In other words: read OP and stick to that procedure for new installs. The directions are there for a reson: they work... ;)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
???

You were debating wiping data in advanced wipe or via factory reset... If I misunderstood you, I'm sorry, I don't meant my general thoughts for you, and when you replied it was about data. I did NOT mean to offend you in any way.

If you need any help let me know by giving exact information what you exactly did and a log. I would be happy to assist. This would help me to understand you and avoid further misunderstandings, too.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] fireguy0306:
Viper4Arise

So when i install Viper4Arise and the Magisk Compatibility module i'm having issues getting to work.

When i install the module i get SafteyNet to fail. I also can't get Viper4Arise to install successfully. I get the "abnormal" status no matter what i try.

Anybody get it to work?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
"Inter-module-compatibility" is definetly behind my scope. Perhaps the best and fastest way to get this one sorted out, is to provide both devs (or is the dev tge same for both modules?) with logs.

BTW: Magisk will not be inclided in this rom anymore. I'll change the OP asap.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] playenball:
I just wanted to take a minute to say thank you to nvertigo67 for the incredible rom that he has put together. I had put off installing anything other than the Official Beta roms until now and I must say your rom has exceeded my expectations for a daily driver. I've been almost 3 days now on the 6/22 build without any issues. Keep up the good work.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] endursa:
I just got told today that while on speakerphone I sound really silent as in I am far away from the phone, does anxious else experience this? Also I have no comparison to stock ROMs since I do not use speakerphone too often. Would be nice to get some feedback from others on this.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Note on GPS

Good news: our location stack is working better then the logs suggest.

When doing a last test build last night, I suddenly (ok, not a split second, but the time I need to reboot to recovery wipe dalvik, cache and system and reflash rom, gapps and su and boot to system again) got no fixes on any gps sat, but only on glonass and baidu. Elevation and azimut were missing an everymsingle gps-sat and time to first fix was 70 to 100 seconds.

After wiping aiding data (you need a user apk that supports clearing aiding data; I recommend: https://play.google.com/store/apps/details?id=com.android.gpstest&rdid=com.android.gpstest ; watch out, there are many apps with this name!), the first fix takes 20 s and gps was back to normal.

(Disclaimer: this is no direct response to anybody. This is not ment to offend anybody. This is just a ux report.)

Back to the good news: this means, even though logcat is still reporting injecting xtra-data failed, at least some ephemeris and almanac data gets effectively injected.

[lamenting dev]

This is the very, very least I would expect, after reducing my nights sleep to 3h.

[/lamenting dev]

Honestly I'm happy about this finding!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] endursa:
thanks for the suggestion, i already knew about mixer path xml, but not where to look exactly! i will try to find the correct device and play with increasing values!

i did not, by any means, try to get you to fix something, that is maybe only on a few devices/my problem :D i am not offended the least :)

this rom is working better for me, than any oxygen os release ever did! keep up the good work BUT also your sleep schedule ;)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Update delayed

Hello Folks,

I've not forgotten to update this rom to the new blobs (ob10). As soon as the Juli safety patch level is merged upstream, I'll build a new update.

Meanwhile I'm still trying to get izat running... ...out of desperation I'll flash oxy this night, to see how it's working... I'm not sure, but I think it's a similar issue, we have regarding ims settings. It seems to me we miss something fundamental with oneplus/qualcomm proprietary settings - or just a simple socket access somewhere.

If someone knows of a rom with fully working qualcomm location stack (including izat fully working and funtional injecting, please let me now.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] yannmrt:
I personally like the respect their is on this treat. 5 days without any news, and no one is crying. :svetius: to every one!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] DazzelRiderx19:
Going to flash this today, also because [MENTION=3044422]mad-murdock[/MENTION] approves this rom so much . Can't wait!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
This is so true and can never stated often enough!

New sec patch level was pushed last night. I'm syncing at the moment. If nothing goes wrong there should be an update later this evening (UTC +2).
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
UPDATE (ob10 blobs & Security Patch Level 5th of July)

Build 20170706

Releasenotes:

This build requires firmware OpenBeta 10 (aka ob10). It's included in this build. A flashable zip for ob10 firmware is below in the firmware section of Downloads.

(This section is redone and links for firmware and uniblobs to my gits.)

I have removed Magisk again - you find the reasons in the thread. As long as you do not flash any root package (or use the los addon completely disabled in dev-settings) this rom is compatible with g's SafetyNet API.

Changelog:

Update to Juli's Security Patch Level.

Update to OpenBeta 10.

init: toybox's chmod doesn't know about "-h". — nvertigo

Magisk: remove package. — nvertigo

update power_profile.xml from ob9. — nvertigo

op3: Light up buttons only when pressed — dianlujitao

sepolicy: allow netd to use sockets to communicate. — nvertigo

sepolicy: allow time_daemon to setprop on diag_prop. — nvertigo

sepolicy: allow phone to getattr on system_app_data_file. — nvertigo

sensors: allow sensors access to /persis/sensors settings and calibration files. — nvertigo

sensors: allow system_server to access /persist. — nvertigo

qcacld-2.0: Update to LA.UM.5.5.r1-05100-8x96.0 — dianlujitao

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

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

MD5: 0738b4027fe67c692c92d31d8a9bc626

Happy Flashing!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] goosebickel:
Just so people know, this ROM will not flash with the latest twrp from the team win website (twrp-3.1.1-2-oneplus3t.img), you will get an error 7 message, incompatible device/model.

Stick with the recommended twrp 3.0.4-1 from op.

Latest ROM seems great so far, thanks again for all the hard work and lack of sleep nights.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mumapizza:
blu-spark twrp v38 working dirty flashed over last build no problem
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] endursa:
did a dirty flash over the last version, I will report how it fairs after 1-2 ´days

regarding my speaker issue, i did not really get any improvements from fiddling with the mixer path values, maybe i was to cautious but i will continue trying to improve it, at least for my needs :)! as always, great dev and really great rom
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mcdachpappe:
thats odd.. nobody else seems to have this issue - me neither. try to increase <ctl name="RX0 Digital Volume" value="84" /> (found in audio/mixer_paths_tasha.xml; line 54) to 87 or something similar. this should increase your in-call volume issue.

b2t:

thanks for the update sir, great work as always.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] arifnasirshaikh:
Clean installed... Lags everywhere can't open apps force closes. Can it be because of substratum? Applied swift black theme.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] horqai:
Everything perfect here

Dirty flashed with the latest bluespark twrp.

Thank you
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
How should we tell?

Include the following information:

Detailed description of installation.

Exact versions of software used (gapps, twrp).

Description of how to reproduce the issie.

MOST IMPORTANT: logcat.

From the los changelog you can see, that the implementation of additional tiles has been completely chamged. I know oms needs some adjustment - this has been done in the loms patches I use. I did NOT know, if the themes needs work, too (theme dev should know, if he cares about los).

Have you tried uninstalling all themes, uninstalling substratum app, wiping cache and dalvik.

An other common reason for lagging on clean flashes is restoring system near packages incliding it's old data.

Without sufficient information this all is guessing.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
It's difficult for me to test twrp: for all other rom related tests I relay on a working twrp. I know 3.0.4.1 has some itches (like the need to manual umount system after wiping system), but it is absolute reliable regarding backup/restore (use image for system, to catch posix xattr).

If anybody would create (and maintain!) a list of working/not-working twrps, I'll be happy to link it!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
On GPS

smali is my friend... I have decompiled all boot jars and the complete framework from OOS4 and OOS3 to get known to whats hapening with the gps stack and location services. What I found out so far:

com.qualcomm.location.XT has been removed from OOS3 to OOS4. It was in xtra_t_app.apk. After decompiling I found this I think it's mainly to accept qc's eula and claiming XT class is in place.

The real configuration of the location stack is in OPLocation (yes, after com.android.location, com.qualcomm.location and com.qti.location (what seems to be the real location service and provider code, "proxied" into com.qualcomm.location), OPLocation (com.oneplus.location) is the forth part of 1+'s location implementation.

The config from gps.conf and izat.conf are NOT really used on OOS: i.e. injection of izat data (including xtra data is done from within com.oneplus.location and not via native caf gps hal (gps.msm8996.so, libloc_* and friends).

We are missing this "location-configuration-layer" (no matter if implemented in com.oneplus... or com.qualcomm.loc...). I think, we need to configure our gps hal and libloc manually. Sadly I can't do this on a global basis: depending on the features the carrier is delivering and personal privacy preferences, the configuration needs to be adjusted.

At the moment we are still lacking the capability to write (inject) data to the izat hardware. I hope, we can get this working, once we find a config for izat feature mask in izat.conf.

I belive to take any advantage of izat you need to enable intermidiate position in izat.conf. Thismworks great: I get immidiate fix (1 - 2 s), starting with a caculated inaccuracy of 21 km... ;)

Next config I'll check is nmea provider set to modem.

If you want to play with that options, backup gps.conf and izat.conf and set logging in both files to 5.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] TheGatorade:
YouTube at 60fps drops frames if the phone is set to Balanced profile or lower. (even with profile auto switch on)

I've seen this in Lineage for other devices, but in some it doesn't happen so it must be fixable.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Havn't expririenced that, so no need to fix something. I run my device balanced with accu optimized for all apps but gms, so I think a general lagging in yt should have cought my attention.

Detailed info (clean flash? gapps version and package? Which settings exactly? (There is no profile "auto" - perhaps you mixed some up?) Link to vodeo to reproduce? Do you use substratum? If so: have you tried to cleanflash without installing substartum in the first place? How about charging (one of the "auto" options controles when the bat saving kicks in)? ) is needed if you want me to fix something.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
This sentence is misleading: this rom lacks the capability to manual inject xtra data. Neither to the chip (by design - what is a good idea!), nor to the location api.

After checking with oos this night again, I'm pretty sure even if the latter is not intended, I have no chance to change this without the qc proprietary sources for QMI.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] wistlo:
For Magisk users, I dirty flashed 20170706 and added latest Magisk beta (c4377ed) as second file, no issues. Magisk Manager version 5.0.2 [edit: now 5.0.3, thanks mcdachepappe]

Also: Caffiene tile fixed in 20170706!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mcdachpappe:
an Addition to the magisk topic:

rom passes saftynet check with latest v13 beta c4377ed and magiskmanager 5.0.3.. just for the record
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] ArchGalileu:
How to flash, and can you post link to the files?

Best regards

ArchGalileu
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] wistlo:
Magisk BETA Link

You must use 13.0 or higher with this ROM, which is currently in beta. Do not use the older Magisk version on the main page.

Manager is bundled in the .zip file. I ran the .apk manually.

To flash, in TRWP select Install and choose the Magisk .zip file. If you update the ROM, you will need to add the file as second after the ROM file.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] ArchGalileu:
Perfect ;)

Done and running ;)

Best regards

ArchGalileu
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] ArchGalileu:
Any advice how to install Viper4android?

I can't manage... it installs but doesn't work...

Best regards

ArchGalileu
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Please respect my dessiccion to support only unmmodded installations. It's not possible for me, to support additional mods. Please remember this complete project is a one-man-show.

From OP:

This is a question, the dev of the mod may like to answer. I strongly recommend to get logs, before posting in his thread.

(This doesn't mean it's not appriciated to answer, if anybody can help with this mod - I'm just saying I won't dig into this, and the appropriate support is to be found in the devs thread. And: don't let the devs beg for logs...)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mcdachpappe:
since you are using magisk there is a module to get viper4android working. ill attach that zip to this post but please remember that im only sharing this zip - i did not create it. credits to the owner.. i dont remember where ive got it from sorry.

installation steps:

1. flash viper 2.5.0.5 in recovery.

2. flash the attached magisk module in recovery

3. check in magisk if the Installation was successfull

4. run viper and grant storage permissions

5. done

remember:

the attached zip file is only the module to get viper running! you still need the main zip file of viper!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] venomus001:
quick question can we use other kernels giving the fact that radio and wifi would stop working because ur kernel is based on stock OOS ?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
You can, but no support is provided from that point, and no guarantee that it won't break functions.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
You need to flash the uniblob-ob10 before booting a custom kernel: all custom kernels I know of expect the display's firmware files in the location of unified roms. Otherwise your display will remain black.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] venomus001:
I tested with franko's kernel everything is working except for the wifi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
TWRP and GPS

TWRP:

After investigating the issues (error 7; mismatch: this is oneplus3) with current official twrp, I found out

there is a incompatibility between official lineageos and official twrp: ro.build.product holds the value of "oneplus3" in current twrp and as well on stock images. In lineage this prop is set to "oneplus3t". The lineage build system does not know of ro.display.series. For stock and twrp this is set to "OnePlus 3T" and stock uses this prop to tell if it's a 3 or 3t.

As long as the (unified) roms are checking ro.build.device are checking for oneplus3t AND oneplus3, this will work though the disagreement on ro.build.device. My 3t-only builds (the builds with firmware) will hardbrick a 3. So I can't add oneplus3...

I would need to hack the build system of laos, to check for ro.display.series - sadly, I have not the time to do so.

FOR NOW: this rom is known to be working with unofficial twrp-3.0.4-1. Other versions may work, but are not supported within this thread.

(As stated before: if anybody is willing to compile and maintain a list of working recoveries, I'll be happy to link.)

GPS:

I was so focused on the technical side of getting izat working, that I completely forgot to think about the privacy part of this.

I.e. if SUPL including Emergency SUPL is configured correctly, my carrier (a british company) would be able to give my complete motion profile to GCHQ and NSA - without ANY need to comply to german law. Or: with extra data enabled and configuered correctly, you can reasonably guess about your private network infrastructure.

Of course this is not only true for vodafone, GCHQ and NSA.

For this reason I'll reverted to laos configuration (not the source code updates from [MENTION=4800121]Sultanxda[/MENTION] and me, but only the configuration) this breaks emergency SUPL and xtra data. This is by purpose - see above.

Sadly, you can't easily switch izat on and off (this possibility is removed on stock oxygen, too - what's the purpose of not allowing the user to disable izat?).

From my point of view privacy is part of human rights. Nobody will ensure your privacy... ...but you!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
Wow... Such detail and transparency [MENTION=4405529]nvertigo67[/MENTION]

Impressed as always. Don't understand half of it but I'm happy that you're sharing whatever you do. Thanks!

Do you have a donation link or something?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] FloGatt:
[MENTION=4405529]nvertigo67[/MENTION] FYI: I can confirm that eng.stk's latest TWRPv39 is also working flawlessly with the latest build of your rom.

Thank you for your work. This is clearly one of the best ROMs for the OP3T out there. And i really appreciate your concerns about the privacy of the users of your ROM.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I don't know if this is related: if I use my latest build, my wifi 5GHz a/c connectivity is halfed, while transfering large files in my local network. I checked the latest kernel changes and revertes them for testing to no advance... Finally I found out: if I use ob9 firmware I get the normal throughtput (about 5 Mbyte/s - it's only 66% of what I get on oxygen), if I flash ob10 firmware throughput drops to 2.5 Mbyte/s.

Can anyone confirm issues, slower speeds or any other problems with wifi on tge last build?

(Don't try to flash between the firmware versions without knowing how to return to a working system: just downgrading the fw breaks fp for me. If I'm not the only one with reduced wifi throughput, I'll provide a flashable solition with the next build.)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Do you have a link to the thread, please? Or even better: would you like to volunteer on the recovery list? (If you feel this is highly manipulating - you are right... ;) )

Propably not related to my wifi issues.

Does franco provide a lineage kernel? If I remember correctly franco is building for oxygen roms. All custom kernel threads I know of, state in the OP (if not in the title) which roms are supported. Unified or not: this is LINEAGEOS.