yashsingh1/xdaforums huggingface dataset:
[Huawei P9 Lite Questions & Answers] 3boge:
da

My problem is i can't get in settings to enable usb debugging, my phone say my gmail acount is incorect
[Huawei P9 Lite Questions & Answers] Coolyou:
You just need the unlocked bootloader and gmail have nothing to do with it.
[OnePlus 3T Questions & Answers] dreinulldrei:
Hi,

Have been using Viper4Android on MM a lot. Now that I have upgraded to Nougat (Open Beta 2), all I get is a valid installation but for some reason it does not process my audio. Please see screenshot.
[OnePlus 3T Questions & Answers] cultofluna:
Uninstall the viper apk..And flash viper4arise zip on twrp..
[OnePlus 3T Questions & Answers] dreinulldrei:
Thanks, but I am looking for a systemless install.

This has been working and others report it's working (on other devices though).

I wonder if anyone has tried it on a 3T with Nougat.
[OnePlus 3T Questions & Answers] cha0zine:
So is it possible to get it working systemless? Thanks!
[OnePlus 3T Questions & Answers] x12prem:
You can use viper4rarise with magisk. Safetynet not triggered. But the problem is selinux status. Its always enforcing for some reason. But yi can change it from terminals using setenforce 0 command. Then it works. You need to do it every time after reboot. I tried to make selinux permissive. Bug it triggers safetynet. So im swt with running everytime post reboot
[OnePlus 3T Questions & Answers] SpasilliumNexus:
Systemless user here. If you're interested, I've created a Magisk module of ViPER4Android 2.3.4.0, which in my opinion is the best version as it had drivers of different quality you could choose. My Magisk module runs on Super High Quality.

And yes, I'm running it on Nougat/OOS 4.0.2. If you want it on Open Beta, send me the following files:

And I'll make it for you.
[OnePlus 3T Questions & Answers] cha0zine:
Where can I download your module? Thanks!
[OnePlus 3T Questions & Answers] dreinulldrei:
Thanks! Much appreciated. Config attached.
[OnePlus 3T Questions & Answers] SpasilliumNexus:
Attached to this post.

Not a problem. Let me know how it goes.
[OnePlus 3T Questions & Answers] cha0zine:
I installed your module. How do I know if it's working properly? I tried changing settings while using google play music but didn't hear any changes. Driver status is enabled but processing shows "no".

Edit: tried listening a podcast and viperfx seems to be working. I can hear changes in sound. How can I get google play music also working?
[OnePlus 3T Questions & Answers] SpasilliumNexus:
I forgot about that. At the moment I cannot get streaming via Play Music working with ViPER's FX Compatible Mode set as normal. Only locally stored music played in Play Music will make ViPER work with it.

However, setting ViPER's FX Compatible Mode to Compatible will make it work with both local and streaming music in Google Play Music, along with other audio apps.

Hopefully that makes sense.
[OnePlus 3T Questions & Answers] Sykojoe:
I had this issue too, I had to go into system/etc/audio_policy.conf and # out deep_buffer
[OnePlus 3T Questions & Answers] damiensturdy:
Viper works here for everything but Google play music. The files you're modifying don't include the XML files, from experience in Nougat just modifying the conf files didn't make any difference, but I may be wrong (Certainly sounds so). What changes did you make may I ask? Removing deep buffer and raw only makes any difference for me if I modify the XML files in Nougat.
[OnePlus 3T Questions & Answers] SpasilliumNexus:
Check out my post here in the LG V20 thread for what I did. It's the exact same process, minus making backups and moving scripts to /su.d.

EDIT: I'm an idiot. I forgot the link. Time for bed. Here it is: https://xdaforums.com/showpost.php?p=70797723&postcount=530
[OnePlus 3T Questions & Answers] damiensturdy:
It appears we are on the same page. Just noticed your post above about Google play music. Gah. I'm going to keep fiddling :)
[OnePlus 3T Questions & Answers] dreinulldrei:
[MENTION=5083335]Spasticdroid[/MENTION]: Magisk 11.0 breaks this module... :(
[OnePlus 3T Questions & Answers] SpasilliumNexus:
Fixed! ;)

Attachments below are for Magisk v11.0+ only!
[OnePlus 3T Questions & Answers] Regionella:
How could i install this? with magisk flash, or twrp flash?

And how can i uninstall it again?
[OnePlus 3T Questions & Answers] Mersine:
install the magisk app in the play store and use it to install magisk. Install the above zip in magisk. Uninstall with magisk if needed.
[XDA Assist] kalpesh137:
Make custom recovery for my Lava a72. It has spreadtrum chip sc 9830a. Android version is 6.0 and my stock recovery is here. http://cloud.tapatalk.com/s/588db95e6e13a/recovery.img.zip
[XDA Assist] xanthrax:
Hi !

Your device has no support on twrp website for your device as off now

You can try to search on Google for more info

Good luck !
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Deleted member 4405529:
3T only - why that?

Since the latest changes in init and overlay, I don't think this posting is true any longer.

I don't like to publish a rom for a device I have not my hands on. So this is still 3t-only.

I completely understand all devs doing unified builds. I completely understand it was so annoying, that oneplus launched 3T half a year after 3, and devs wanted to preserve their work, or don't want to buy just another device. So if you think unified builds are your way, I understand and appriciate that!

For me, on the other hand, it looks like this: I've come from bacon to 3t, I have no 3 and my personal policy is building only for devices I have my hands on. I like OOS - indeed for me it's one of the best stock roms I've ever seen - but it lacks some features I learned to love in cm times, like privacy, app-ops, automatic do not disturb rules and much more.

I lurked some time around in the threads, build OSS from source and tried to dig in the sources. I tried hard to understand the differences of 3 and 3t. What I found in most of the sources was [MENTION=4800121]Sultanxda[/MENTION]'s and [MENTION=4443334]Grarak[/MENTION]s patches to load different adreno firmware.

Then I pulled blobs from OOS-4 for 3t and ran diff against the onplus3 blobs from themuppets. I don't say they were completely different, but they differed in about 4/5th of the files (as you can see in this commit: https://github.com/nvertigo/proprie...mmit/17c7609f79167c02041736306b18f52bca5b9ac6). Then I compared the specs of 3 and 3t - surprise: they are different... ;)

Let me give you an example: the battery is different. That means power_profile.xml has to be different for 3 and 3t, too. If you got traped by the hoax, that the 3t comes with a 3000 mAh battery read this.

So I decided to build a rom with all blobs beeing native and configuration optimized for 3t. To my surprise my first attempt ended in a build so smooth with all features I missed, that I fell in love instantly. So I spent even more time on this, added busybox (not as toybox' replacement, but just as binary in /system/xbin/busybox) and used native qcom SnapDragon llvm for CLANG and UBERTC/linaro for kernel.

At this point [MENTION=3044422]mad-murdock[/MENTION] tested the build. I wasn't sure about my own perception, because it was my own rom. He ensured me though, it was stable and smooth. So I was happy with the build.

I don't say it's not possible to achieve all this with an unified build. But I'm absolutely sure, that 3 and 3t differ in more aspects then graphic blobs. These differences need to be addressed in unified builds (RR seems to be a step ahead compared to laos). This is far behind my scope (and to stick to my personal policy to build only for devices I have hands on, I would need to get a 3 and a second sim), so here we are: LineageOS for 3t only.

I surely don't want to start a religous debate on "the right way" of building roms for 3 and 3t - there are always many ways to build awesome roms - this is just my way for the moment.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Deleted member 4405529:
UPDATED: Camera Mods

To give the user more freedom of choice, OnePlusCamera and onePlus Gallery are removed from the rom. In this posting I provide additionally installable apks, to allow the user to install them as any other apk.

@kxzxx's mod (use to get the same cam setup we use for four months - callbacks removed):

https://drive.google.com/open?id=0B_f72wz8rwc6SV9VTXRXMVdfeFk

This should work on all laos based roms. Recommended, if you want the very same setup as before.

Update Version 1.5.0 (ob14): https://drive.google.com/file/d/0B_f72wz8rwc6dEpHUGVlQ2hYY28/view?usp=drivesdk

Plain stock OOS gallery - op3/t (dng support):

https://drive.google.com/file/d/0B_f72wz8rwc6QWNWUDhpQWhJa3M/view?usp=drivesdk

This should work on any rom without OnePlusGallery not installed.

Update Version 1.8.4 (ob14): https://drive.google.com/file/d/0B_f72wz8rwc6S2VkV1VsaHNNYzA/view?usp=drivesdk

Some candy:

Plain stock OOS 4.5.x cam - op5 (sometimes glitchy, flash not working reliable - raw working [set iso and shutter manually in pro-mode]):

https://drive.google.com/file/d/0B_f72wz8rwc6UzBoUlNhT0NabWs/view?usp=drivesdk

Outdated and obsoleted - just for reference: If you want to check this out on our current rom, needs to remove OnePlusCamera&Gallery first. Flash this in recovery:

https://drive.google.com/file/d/0B_f72wz8rwc6b2xUSUZQMXNuck0/view?usp=drivesdk

[MENTION=313982]home[/MENTION]builders and all interessted people:

This is neither a HOWTO, nor a script (op3t/op5 is hardcoded, because I havn't parsed arguments), but gives at least an impression on what is needed to make a other roms system app an user installable app. As you can see, I sign the apk with laos test keys. The key does not really matter, as long as the apk is signed at all.

cat build.sh
#!/bin/bash

S1="-decompiled"
S2="-unaligned-unsigend.apk"
S3="-unaligned.apk"
S4="-v1.4.0-op3-nvertigo.apk"

for i in $*; do
apktool d -f -v -t oxy -o $i$S1 $i.apk
cp -av lib $i$S1
apktool b -f -o $i$S2 $i$S1
../.signing/sign.sh $i$S2 $i$S3
zipalign -f -v 8 $i$S3 $i$S4
done

cat sign.sh
#!/bin/bash

java -Xmx2048m -Djava.library.path=/mnt/export/data/src/cm14/out/host/linux-x86/lib64 -jar /mnt/export/data/src/cm14/out/host/linux-x86/framework/signapk.jar -w /mnt/export/data/src/cm14/build/target/product/security/testkey.x509.pem /mnt/export/data/src/cm14/build/target/product/security/testkey.pk8 $1 $2

@kxzxxx: if you still read here and if you have plenty of (spare-)time, would you be so awesome to look into op5 cam for callbacks on flash? I tried based on op3 cam, but failed. No need to hurry. Thanx in advance.

You should also checkout these:

MI5 camera mods (by [MENTION=4860033]Arnova8G2[/MENTION]): https://xdaforums.com/mi-5/themes/app-collection-camera-modded-t3591177

OxygenOS Camera Mod (by [MENTION=4837394]siankatabg[/MENTION]): https://xdaforums.com/oneplus-3/themes/port-oxygenos-stock-camera-cm-t3451721

Pixel Google Camera: https://www.xda-developers.com/google-camera-hdr-ported/
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] ryshd296:
Thanks!!

your rom is best!!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] dago:
Thanks guy ! Great
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] TheFrozen4:
Great to see you started your own thread afterall. :) Going to flash this today, also because [MENTION=3044422]mad-murdock[/MENTION] approves this rom so much :). Can't wait!

edit: found a small typo in the instructions. Check the year [MENTION=4405529]nvertigo67[/MENTION] :

"Install the Google Apps addon package (Optional. Use opengapps nano package from 20160120)"
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
Update: Wipe before you install.

You might want to know that I flashed this ROM dirty over koenkk's ROM.

I have no problems doing so. Be advised though, that this isn't recommended and can result in stuff not working. You can try a dirty flash, if it works, fine. If not, just wipe as in official instructions.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] pamposmouskos:
Just flashed your Rom. Fluent and feels natural! Thanks Developer
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] t-shock:
Glad to see you posting a thread on XDA

;)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Deleted member 4405529:
I like experimenting, I like dirty flashing, I like custom kernels (indeed I'd love to see Boeffla cm/laos-14.1 kernel) and I want to encourage everybody to home-build, experiment, dirty flash, try mods, kernels or what ever: he, who never bricked an android device, has not flashed hard enough.

The only problem with that is support: I can't test any combination, reproduce issues and so on. Also if everybody reports on his very own combination, the thread becomes unreadable/unundestandeble.

So I kindly ask you to try whatever you want; but if reporting an issue, stick to OP rules, please.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Deleted member 4405529:
HOWTO: build this rom yourself

The "homegrow"-howto is here in the file named README.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] TheFrozen4:
Well deserved. Take care.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] DeadPicsel:
Has anyone installed this ROM after formatting system and cache to F2FS?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
System and cache as f2fs is rare. No idea which Roms support this. I would say, just try, if it won't work, format system and cache. It's no extra effort.

Just make sure not to reboot recovery while system is blank, since TWRP pulls crypto lib from system
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] lapapunk:
Hi. I like the way, that you chose. Hope you will doing it in future. Like and you, I came from oneplus one.

Btw. What about sRGB mode? Is it here ? I'm hate oversaturated colors. After opo it's looks so ****ty..
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] hassan_1000:
sorry to be a pain but how long does it take for first boot? I've been waiting for 15 mins so I'm not sure if I've done something wrong...
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
it depends on how many apps you had installed. still, 15 minutes sounds pretty long. did you dirty flash without wiping? if so, you should probably go and wipe now.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] psdl:
No problem. But the problem with the opengapps are the updates the google play store was installing because automatic update was checked.

I now have opengapps aroma with nearly everything running smoothly. But webview rendering was switched from system to chrome rendering. And the version from the google play store does use the system rendering engine and the opengapps the chrome engine which is more efficient. Also the different versions from chrome to webview might also be a problem.

So, use opengapps what you like but don't install google play store updates for the apps from opengapps.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] d3xtr0:
Edit: wrong thread. Sorry.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] TheFrozen4:
[MENTION=4405529]nvertigo67[/MENTION] Can't do a complete clean flash now. TWRP complains and aborts with an error 7:

Comparing TZ version TZ.BF.4.0.1-76917 to TZ.BF.4.0.1-83199

Assert failed: oppo.verify_trustzone("TZ.BF.4.0.1-76917") == "1"

I lack full understanding of why TZ version is important, but it seems I'm on a newer version than the script allows for ... ??

My old OS before the wipe was the latest Oxygen.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] cmattern:
Hey [MENTION=3044422]mad-murdock[/MENTION],

I have a good build env here now and am ready to hunt this tethering bug. I've verified with AT&T that I do have tethering so I'm not doing anything sketchy. You mentioned this was enable recently but I've not yet found a reference, can you help guy out? Having a place to start is ever so much more fun that just starting a find|grep from the top of the tree.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] m0d hipp¥:
Updated mirror to newest link:

http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170203-UNOFFICIAL-nvertigo-oneplus3t.zip
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
May you name exactly, what the "My old OS before the wipe was the latest Oxygen." was? I'm using the trust zone of the firmware shiped OxygenOS-4.0.2 - I guess, you was on openbeta?

The first two versions of this rom (see History in OP) was shipped with firmware (OxygenOS-4.0.2), so just flash one of them, reboot to recovery and flash current version of this zip.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
No. The problem is, that if you use stock, the systems webview is REPLACED (if not, the auto update would only harm additional webviews, but not the system webview).

If you install nano and get chrome from playstore, chrome's webview is installed as user app ADDITIONALLY. Then you can switch between systems webview and (propably broken by autoupdate) chromes webview from dev-ops. Also: if you use stock, Gello gets replaced - if using nano, you get chrome added without Gello deleted.

BTW: Gello is a chromium fork, and should be mostly compatible with chrome.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] TheFrozen4:
I will name exactly: open beta 2. See screenshot for the details.

I will do as you said. Coming from Nexus 6P I do not understand what in the 3T context 'firmware' refers to. Is it like the vendor (-specific blobs) or the modem/radio partition or perhaps something else?

Oh, does this actually mean your zip is supposed to be flashed as an upgrade to an earlier version? Or how is one supposed to get the correct base firmware?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
No it's not supposed to be an update: when I ship the rom with firmware, I don't need to check which TZ is installwd, because I know it: it's the one flashed together with the rom. If I don't ship the firmware, I have to check the the TZ, to ensure a compatible firmware version is installed. This ia to avoid that a user renders his installation unuseble.

firmware: content of these partitions

/aboot	emmc	/dev/block/bootdevice/by-name/aboot	flags=backup=1;display="Bootloader"
/cmnlib64	emmc	/dev/block/bootdevice/by-name/cmnlib64	flags=backup=1;subpartitionof=/aboot
/cmnlib	emmc	/dev/block/bootdevice/by-name/cmnlib	flags=backup=1;subpartitionof=/aboot
/hyp	emmc	/dev/block/bootdevice/by-name/hyp	flags=backup=1;subpartitionof=/aboot
/pmic	emmc	/dev/block/bootdevice/by-name/pmic	flags=backup=1;subpartitionof=/aboot
/tz	emmc	/dev/block/bootdevice/by-name/tz	flags=backup=1;subpartitionof=/aboot
/rpm	emmc	/dev/block/bootdevice/by-name/rpm	flags=backup=1;subpartitionof=/aboot
/keymaster	emmc	/dev/block/bootdevice/by-name/keymaster	flags=backup=1;subpartitionof=/aboot
/devcfg	emmc	/dev/block/bootdevice/by-name/devcfg	flags=backup=1;subpartitionof=/aboot
/xbl	emmc	/dev/block/bootdevice/by-name/xbl	flags=backup=1;subpartitionof=/aboot
/modem	emmc	/dev/block/bootdevice/by-name/modem	flags=backup=1;display="Modem"
/bluetooth	emmc	/dev/block/bootdevice/by-name/bluetooth	flags=backup=1;subpartitionof=/modem
/dsp	emmc	/dev/block/bootdevice/by-name/dsp	flags=backup=1;subpartitionof=/modem

(taken from recovery.fstab from [MENTION=5672995]jcadduono[/MENTION])
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
If you have sourced build/envupdate.sh take a look at that file: it contains some sweet bash functions for grepping recursively.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] wistlo:
tethering on 3T with Lineage OS

I am on AT&T using a 3T with lineage-14.1-20170203-UNOFFICIAL-nvertigo-oneplus3t. When installed, tethering was grayed out and disabled. When I use this procedure (posted in a Nexus thread but works fine for me on the 3T), tethering works. I did not need to flash SuperSU but the phone does need to be rooted.

I'm on AT&T standard 16 Gb plan with the ATT GoPhone APN (the default choice, unchanged from installation). Note that I am *not* a DirectTV subscriber with unlimited data and tethering prohibited. On plans with limits, tethering is allowed.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Great finding, dude.

[MENTION=5226211]cmattern[/MENTION]: I think, the second step from the original posting is obsolete, if you just add the property to system.prop in device-tree. Since tether_dun_required is null, when not set otherwise.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] cmattern:
This is great! But we still should not need to make this change. I can now make my t3 my daily driver and sell my 6p but I'm going to keep on looking for the root problem too.

---------- Post added at 09:54 ---------- Previous post was at 09:53 ----------

Many thanks!

This was the last step I needed to make my 3t my daily driver.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] psdl:
Ah, thanks for the info.

I have another app that is causing problems. I am using enpass as my password safe. The application uses the android autofill option that is enabled by the application under (don't know the English term in Android) "Bedienungshilfe". It is tracking constantly the screen if any field is visible for username / password etc. This addon is also "generating" stutter all over the place.

*sigh*

The great from aroma or stock is i have the pixel launcher available.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Hmm, I don't know enpass, but if I google "enpass lagging" or "enpass stutter" there are a lot of people having issues with enpasa and nougat roms. I lurked at some threads in their own forum, and it seems to me, they are working on it for months on this without final solution - but they are still working on it (what is great). Perhaps you can ask them. If they suggest special patches to the nougat sources, I'd be happy to check if they apply to this rom. At the moment most users suggest to disable autofill.

Install pixel launcher from playstore as userapp - then you can even backup it, to maintain screen layouts:

https://play.google.com/store/apps/details?id=com.google.android.apps.nexuslauncher

[MENTION=535343]all[/MENTION]: if you install nano, you can install all missing apps from playstore without messing with system files, and therfore without messing your system!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] TheFrozen4:
Clean flash 20170203 version, alert slider is not working. Workaround doesn't work either. Logcat makes no mention of anything happening.

Can somebody confirm this, or is it just me. ?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
UPDATE: Finally Nov. Sec. Patch has arrived on NLOS!

Build 20171117

Releasenotes:

This build requires firmware OpenBeta 15 (aka ob15). As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images. NLOS and 'old'-style bootlogos can be found down in this posting.

Changelog:

Manually merged November Android Security Bulletin.

Bootlogo choices

nlos_bootlogo-v0.1.zip

back_in_black_bootlogo-v1.0.zip

[SIZE=+2]DOWNLOAD[/SIZE]​

Happy flashing!

P.S.: chagallwifi build was updated with Nov. Sec. Patch as well. Downloadlink can be found in my signature.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] phoenixg36:
I love this rom and it looks like every thing is working smothly.

I'm not sure if this is a rom problem, or is hardware related. I use my phone every day as navi with android car and it works ok. But with oxigenos i got nearly evrey day no gps fix. After a reboot it works normal. Now one time it happen also with this rom. An the only thing I did diffrent on this time was to charge the phone during driving.

And a nother quation I have, I use the tool fing and normal it is able to ping ip adresses. But on this rom it say it´s not posible to use the tool ping or tracert. What do I need to do too give apps the right to use ping? I rooted with Magisk 14.0.

Thank for the gread work to this rom.

Sorry for my bad english :(
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] FloGatt:
New build is working flawlessly, as expected. I'm dirty flashing since ten builds or so :D And never experienced any problems :good: