yashsingh1/xdaforums huggingface dataset:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
[MENTION=6795212]soseono[/MENTION]:

Would you please try this:

https://xdaforums.com/android/software-hacking/fix-fix-crashing-setup-wizard-t3586177

So I doubt it's the same issue: if this is working, I can try to add the button [MENTION=3172940]goosebickel[/MENTION] mentioned.

Would you please also try to setup without gapps?

And would you be so kind to get a log from the failed installation via adb (addonsu needs to be flashed) with beans mini flashed. Perhaps it's just a sepolicy denial... ...or something as trivial.

Some random idea: sometimes it takes really long to switch on wifi. Have you tried to wait after the language selection for 180 s?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] soseono:
I'll try tonight and let you know how it went.

Would you please show me which adb commands to run? I've never gotten a log over adb... Also, I was flashing Magisk for root. Do you recommend addonsu over Magisk?

No, but I'll try this as well.

As for trying without GApps... I need GApps for my daily driver, so I'm hesitant to try that.

Thank you for being so attentive to my problem. Really appreciate it!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/

Or just search XDA for logcat to get a few threads related to it.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] soseono:
[MENTION=4405529]nvertigo67[/MENTION]:

I've searched for adb logcat on XDA and they say that USB Debugging should be turned on. Will it be turned on by default at the time of setup??

ps. I'm at the setup screen right now, and adb doesn't recognize the device. "adb devices" pulls up nothing. I can't run any adb commands since device isn't found. Here's the error message when I click the SKIP button on Insert SIM Cards screen:

Setup Wizard has stopped -> dialog box title

Open app again -> upon clicking this, I'm back to the language selection screen.

ps2. Inserted the SIM and went through the initial setup just fine. So I'm all set now.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] magoo5289:
I think I used this method successfully before.

Clean flash without gapps, boot up, connect to your wifi, reboot to recovery, flash gapps, boot up, setup your google accounts. This may get you past the loop you are stuck in.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] soseono:
I'm setting up the rom and just encountered this: Is anyone able to install Amazon Shopping app on this rom? It says incompatible on Play store. ("Your device isn't compatible with this version." is the exact language there.) I was able to install it on OOS 4.5.0 just this afternoon... I googled for possible OS incompatibility issues, but couldn't find any answer. Weird.

ps. YouTube Music is incompatible and cannot be installed from the Play store as well...
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] sandeep_kumar:
Dear Sir,

When to flash "back_in_black_bootlogo-v1.0.zip" at the time of installation. Is it after Oxygen OS OB15 and before full ROM zip

or after BeansGappsmini at the end before booting? I am confused. Please guide.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
If I can't solve a problem (any problem - not only sim-less installs) on the first glance, I try to aproach this systematically:

Quite helpdesk standard: how to reproduce, what has changed recently, what has changed longer ago, what is the exact error-message, -symptom, or whatever. Being as exact as possible and searching for as much information as possible in all this, makes my mind understanding the problem enough to come to a solution for most problems. For the still unsolved problems this exactness and info collection prepares me for comunicating my problem: maybe for an bug report, a hotline call or an argument with an significant other...

If the context of the problem or the problem itself is too complicated for me, I try to reduce the complexity (what works quite well on most technical problems, but seldom in social engeneering...). If the problem does not occure in the reduced complexity, I add it back - step by step.

In the end it's just it's just KISS combined with occam's blade for complexity afraid humans. ;)

Anyway, you would need a special build to get logs, so you did not need to try to pull them.

I would have tried (and I did exactly that, when I had hands on twp bacons) if installing the rom is possible at all: therefore just clean flash the fw and rom, run through SetupWizard (cm's of course, no gapps installed) to start screen. Next I started over: clean flash with gapps, run through SetupWizard (gapps this time), setup personal prefs and reboot to recovery and flash addonsu (this is just the original lineageos su solution and not a complete mod - why make things so complecated?!?!).
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Havn't tested music, but shopping installs just fine:

EDIT: don't know, why the IMG tags abovemaren't working. Anyway, these are the screenshots from installing shopping.

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

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

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

EDIT2: funny, the gdrive l8nks doesn't work, perhaps the same, that some people can't find latest uploads in gdrive. I leave the IMGs and links, perhaps this posting looks like intended in a few hours... ;) I asditionally attach the images.

why quoting a complete long posting? The text you quoted is not related to your question. Such quoting makes the thread much more difficult to read... :( If somethingg in the quoting IS related to your question, it would be much better to quote only that.

This is NLOS. You do NOT need to deal with an official OnePlus OxygenOS - neither ob nor stable. Just flash the ob15 fw from the Download section of #1. Flash NLOS, back-in-black and beans. In other words: stick to OP just flash additionally back-in-black right after NLOS.

Since this is the NLOS thread, the phrase "the rom" always refers to NLOS.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] sandeep_kumar:
Dear Sir,

How is the camera quality in this ROM as compared to oxygen OS especially in low light. I am very much concerned about the camera because most of the custom ROM deprive of the quality unlike stock oxygen OS.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] kinghaloman:
1: what is the difference between this and official lineage OS for the 3T

2: Does this come with the updated privacy guard and the new color engine?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] crian:
1. read the op

2. It supports substratum
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] soseono:
None of your links worked, but I was able to see the images you attached to the post. It's really weird :( Let me attach my screenshot from Google Playstore. I can't even find the Amazon Shopping app on my phone (it's hidden probably due to the incompatibility), so had to do it on the computer. As you see there's that X mark right next to the 3T.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I ask you not to flood this thread with unneccessary and complete quotes. That you do the very same on the very next posting is no longer bad manner, but offensive!

For your question: why not use thread search?

Dude, you need to read. In the first place I recommend forum rules.

I was trying this with the next test build, where I moved the build fingerprint in the appropriate make variable, so the build fingerprint is uswd throughout the build process, and not much later on boot time. Maybe this makes a difference. Maybe it's some mod or even country/carrier can make a difference.

I found it in playstore app. I can't find ymusic, and play store still shows in settings: uncertified device. Is it shown on los nightlies (on both devices - op3t and op3)?

I'm working on for more then 8 weeks - and I'm clueless atm.

EDIT: I'm on a A3003, perhaps that can make a difference, too. I doubt that, but on the other hand: it's google - who knows... ;) Try the next build.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
What are you talking about?

https://www.google.de/search?q=upda...e..69i57j0.12554j0j4&sourceid=chrome&ie=UTF-8

Can't find anything recent.

Search before posting.

[MENTION=535343]all[/MENTION]: I promise it's not hurting to use thread search!!!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I had a bad cut'n'paste derp in in init - fixed. Some apps (including ps) doesn't like, if the build fingerprint prop is only in ram, but not in system.prop - fixed. The third issue is due to my renaming: los build system forces the obsolete ro.build.target to TARGET_DEVICE - but gservice expect this to be OnePlus3 (not oneplus3t) - fixed.

Now gservices accepts NLOS on op3t as certified device.

This should fix the issue with Amazone Shopping.

For Youtube Music: After the above changes, I get on the gp web page: "Dieser Artikel kann im Land deines Geräts nicht installiert werden." (This product can not be instlled in the country of your device.) I can't do anything about this restriction.

Next build will fix Amazone, but on ym you are alone, til ym is free for germany.

Sadly, apk mirror has only a version from 2015.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mcdachpappe:
maybe hes pointing to the updated privacy guard within lineageos which received between august and september some changes

https://review.lineageos.org/#/q/status:merged+privacy+guard (the first 5)

[MENTION=8463535]kinghaloman[/MENTION] : but since this rom is based on lineageos, these changes are included in this rom (if you meant them).

sidenote: if you are meaning with "the new color engine" the color engine which was introduced with paranoid android, its not as good as OMS in my opinion. ive merged their commits some time ago into this rom - its not as powerfull as oms is.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
...and I always wundered why there is a link to LineageOS just before the current announcement... Great finding! *lol*

I know the commits, but havn't considered them "the updated" privguard... (and I feel guilty, if I catch the sec updates later then 24h...)

That's as true as redundant:

https://xdaforums.com/search/thread/3547024?query=color engine

If you cut the postings added by this already answered question, you get devs oppinion including an detailed explenation...

Anyway, thank you for answering - as you can see, when ever I deal with such postings, I just wonder if this is thoughtless or reckless - what makes me really frustrated.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mcdachpappe:
a quick review:

i flashed a test build including your latest commits in the device tree about the little cluster freq thing. the little core is still set to 1.5ghz, problem not solved yet.

i wish i had an idea to fix this
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Yeah, I know. Something's strange with cpufreq: scaling_min_freq is setable (echo returns successfull), and unsetable (the value always is 1GHz) at the same time, but it IS scaled down to a scaling_current_freq 307 MHz... sadly scaling_max_freq is really limitting the freqs. For the moment I'm clueless.

On the other hand: nobody complained about eas performance.

The build I have just announced is without the vp changes (in deed my voxpopuli repo is for testing - I build against the origin).
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
UPDATE

Build 20170929

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.

I had to change the lcd density back to 420 dp. All values other then 360, 420 and 480 introduce some funny side efects. Sorry, but I'm quite sure it is the last time. Just flash the update and after first boot switch once away from your prefered setting and immediatly switch back - that's it. Thanx for your patience and understanding.

Anybody having issues with finding some (known to be working) apks on play store, should check with this build. If play store settings still show device is uncertified, or you can still not find the apk, close all google play using apps (i.e.: chrome) or log off from google, delete your google account, go to https://myaccount.google.com/device-activity and delete your device (of course: don't do this with chrome, because this would let chrome logging in again) and DELETE the device (backups will be lost, but read on). Now create a new google account. Don't forget to sync - and the backups are filled with the current state of your device - which is the exact state of your device, as before dwleting the device on google. (This is propably not neccessary, but doesn't harm neither.)

Changelog:

Use 420 dp asmsmallest width. (rebase)

Add [added for changelog: German] translation for Dash Charging — crian

buildinfo: make ro.product.device and ro.build.product overrideble. — nvertigo

init, props: move props from init to lineage.mk; overrride ro.build.device and ro.target.device. — nvertigo

op3t: init: set max_freq of LITTLE cluster to 2.2 GHz and big cluster to 2.3 GHz. — nvertigo

op3t: init: remove op3 models; move build fingerprint in the appropriate make variables. — nvertigo

op3t: overlay: enable burnIn protection support — Joey Rizzoli

back_in_black_bootlogo-v1.0.zip

Camera- and Gallery-Download (If you havn't done so, update com.oneplus.camera and com.oneplus.gallery.)

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

Happy flashing!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
You need an insecure bootimage with adb enabled - I thought I mentioned that, sorry.

Congrats! I hope besides this annoying installation you are enjoying NLOS!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Mr.LOVER:
hi, it's a very noob question, but can anyone please tell me what are these terms? and what are there advantages / disadvantages ?

1. [EAS]

2. [OMS]

3. [UBERTC;SDCLANG]

4. [microG-ready]
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] nan0s7:
1. Energy aware scheduling. It's basically just another way of managing CPU frequencies and such. Have a look here for more information.

2. Overlay manager service. Made by Sony, used by Substratum.

3. Uber tool chains and sdclang I assume are just developer stuff to enhance whatever you compile. Not 100% sure though.

4. microG is a FOSS (open-source) version of the Google Services. Still in beta but it's good if you want more privacy but still want the Google Play stuff. More info here.

Hope that helps!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I've added this to the very beginning of OP just 18 h before your posting.

Added a link to xda forum rules, now.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] soseono:
I just did a dirty flash, and went to the Google Playstore app settings and deleted its data and cache. Started the app, re-registered my Google account, and now Amazon Shopping as well as YouTube Music are both compatible and downloadable!!!!! Yay!!!!! (Checked both the Playstore app and the website and found the device compatible in both places.)

In Playstore settings, the "Device certification" is still "Uncertified", though. So I wonder if the fix had to do with the screen density. I actually read something about the screen density setting causing issues with Play store while googling before. But I was using the default setting in the Display - Display Size settings, and didn't know that you had changed it, so didn't know what to do about it.

Anyway, I'm happy that I can download the apps now. Amazon Shopping app gives me delivery notifications, which is quite indispensable to me. Thank you!!!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Mr.LOVER:
my bad
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
No, it's a combimation 9f three errors in my prop config - not related to screen density.

I procceded like described in the announcement for 15 or 20 times (to not miss the build that fixes this).

Do not only delete pstore date, but remove your gaccount from the device and from the device mamager (on g's webpage). Then restart pstore and add your account again.

EDIT: I wipe system, too, from time to time and have root disabled if starting pstore for the forst time after deleting the device from g's device manager.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mcdachpappe:
my device is certified in play store settings.. im on the latest build
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] UnbracedTundra:
When flashing the ROM, if you do not flash Magisk, and complete the setup/open Play Store, your device will be uncertified. But if you flash ROM, Magisk at the start and then complete the setup, it will be certified.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mcdachpappe:
i can confirm that.. im flashing magisk right after the rom (reverted the commits back to the old days were magisk was flashed within the initial flashing process).
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] soseono:
I followed the steps in your build post (delete Google account, remove device on the webpage list, then add the Google account again) and even removed the app data of Google Playstore. The device is still uncertified, though. :( Would it have to do with the root package? I’m using addonsu for LOS, not Magisk.

Ps. Googled and found this: https://jira.lineageos.org/browse/BUGBASH-809

So I deleted data from both Google Play Services and Playstore, and now in Playstore settings the Device Certification has disappeared! I’m baffled...
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] RaEsAcademy:
It is just because you are using the lineagesu other than Magisk...
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] soseono:
So I removed addonsu (flashed the remove package) and flashed Magisk 14. Deleted app data for Play Services and Play Store. The device certification entry still wasn’t there. Then I found this post https://forums.oneplus.net/threads/magisk-module-fix-google-play-certification-status.535634/ so I enabled Magisk Hide on Google Play Store and deleted the data for the app. Now it’s showing as certified! So it did have to do with what root I had. Interesting.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Interesting? I don't know, but it's absolutly expectable. That gservice's checks of the device had become more restrictive was the reason, why I removed it again.

That's a very good example (and it is really only an example - it's by far not only you!) for missing exactness: if I would have known, you are using magisk, I would had have the chance to point you to this... But I can't consider something I don't know of.

I want to recommend my posting on systematically hunting down issues and reducing complexity to everybody. Following those strategies would have naturally lead you magisk.

Anyway, I'm happy it's working for you, now. Especially that ymusic is working, because I can't check this due to country limitations.

I'll remove flashing su from installation instructions later - I'm very busy atm and the next days.

Thanx to everybody helping here!

BTW: I use addonsu. If I'm testing safetynet before I push a build, I just disable root completly and close all apps, that are acually using root - when the last root using app is closed, the asterix indicating root will void. This does not only work for sn, but also for playstorenand root checking apps like some banking apps. When magisk was compiled in, I always needed to make two builds, if I suspected magisk for an issue...
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
UPDATE (Oct. sec path)

Build 20171004

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.

Changelog:

Update sec patch level.

back_in_black_bootlogo-v1.0.zip

Camera- and Gallery-Download (If you havn't done so, update com.oneplus.camera and com.oneplus.gallery.)

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

Happy flashing!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Camera implementation

I'm trying to get the los camera implementation running since the patched hal should fix the first ffc shots issue. You'll find the latest of my attempts in the branch "nlos-cam" for device and vendor (kernel is nlos-14.1).

This renders the ffc for all HAL1 using apps unusable, because it crashes every single time!

If I use the old libmmcamera_interface.so it's back to normal - including the well known crash of one of the first shots.

I have no clue at all why this is the way it is...

ingo@adler /usr/local/src/cm14/device/oneplus/oneplus3t $ git diff los-cam laos/cm-14.1 -- camera/
lines ?-?/? (END)

I also found these camera blobs differ from ob15 (op3t) to ob24 (op3):

colordiff -ur oneplus3/proprietary/vendor/lib oneplus3t/proprietary/vendor/lib
Binärdateien oneplus3/proprietary/vendor/lib/libmmcamera2_iface_modules.so und oneplus3t/proprietary/vendor/lib/libmmcamera2_iface_modules.so sind verschieden.
Binärdateien oneplus3/proprietary/vendor/lib/libmmcamera2_imglib_modules.so und oneplus3t/proprietary/vendor/lib/libmmcamera2_imglib_modules.so sind verschieden.
Binärdateien oneplus3/proprietary/vendor/lib/libmmcamera2_mct.so und oneplus3t/proprietary/vendor/lib/libmmcamera2_mct.so sind verschieden.
Binärdateien oneplus3/proprietary/vendor/lib/libmmcamera2_sensor_modules.so und oneplus3t/proprietary/vendor/lib/libmmcamera2_sensor_modules.so sind verschieden.
Binärdateien oneplus3/proprietary/vendor/lib/libmmcamera2_stats_modules.so und oneplus3t/proprietary/vendor/lib/libmmcamera2_stats_modules.so sind verschieden.
Binärdateien oneplus3/proprietary/vendor/lib/libqti-iop-client.so und oneplus3t/proprietary/vendor/lib/libqti-iop-client.so sind verschieden.
Binärdateien oneplus3/proprietary/vendor/lib/libqti-iop.so und oneplus3t/proprietary/vendor/lib/libqti-iop.so sind verschieden.
Nur in oneplus3t/proprietary/vendor/lib: libqti_performance.so.

(sorry, forgot to set LANG to C: "Binärdateien" ~ binary files; "sind verschieden" ~ differ)

The qti differences are ok, because I changed them while setting up eas, but the cam-blobs seem to differ in the beta roms.

Of course I've tested with op3 blobs, but withnthe same results as described above: always crashing ffc since I change back to old interface lib, then the first ffc shots issue is back.

If anybody (especially the homebuilders) see the inconsistancy in my code base, please help me out. I've run out of ideas for now.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mcdachpappe:
thank you for your latest build and your how-to-build nlos "guide" - much appreciated.

while we are talking about your repos i want to ask you 1 question:

why are you using CyanogenMod/android_frameworks_base instead of LineageOS/android_frameworks_base ? same goes for android_frameworks_av. pretty much everything else (excluding vendor and device-tree) are forked from LineageOS. is there a special reason for this? im just curious..
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mcdachpappe:
i saw this on your github (https://github.com/nvertigo?tab=repositories).

there it says:

android_frameworks_base

Forked from CyanogenMod/android_frameworks_base

same for anddroid_frameworks_av

everything else is like:

android_packages_apps_Settings

Forked from LineageOS/android_packages_apps_Settings

this is what github tells me. i know they are up-to-date with the lineageos repos - but i dont understand why its telling me that it was forked from CyanogenMod :confused:

its no big deal nor a problem at all. i dont want to steal/waste your time for this. i thought there would be a simple explanation.