yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] knpk13:
Additional exposures? Ooh it installs a magisk module. Guess I need to reboot every time to apply themes. Unfortunate. Well at least it's all black now haha. Funny thing is in P, I find the spacing of notifications to be quite large. The P-ify module on O was more compact and nice, better than original P lol. Maybe there's way to change it, or I'll just get used to it. Everything else seems great.

This sounds app in the screenshot. I tried to change my ringtone and it asked me to pick between media storage and sounds. Media storage works, sounds crashes.

I don't have any audio files in the alarms or notifications folders. Only the inbuilt LOS sounds. Here's one example of a duplicate, Platinum.

So I shouldn't be worried about the setup wizard FC's? I had only one FC.
[OnePlus 3 & 3T Cross Device Development] dyc3:
yes !! hope it gets stable as 15.1 or even better.. any screens ??
[OnePlus 3 & 3T Cross Device Development] cukierkas:
Last question before update from nlos 15. Does call recording feature works out of the box?
[OnePlus 3 & 3T Cross Device Development] 64ashg:
I have the network speed indicator at a slight offset. Is anybody else having this problem?

The first screenshot is of the default settings, and the next one is of me having the display size small and font large.

I dirty flashed over nlos 15.1 so anyone with the same experience. Or clean flashers, having this issue. I remember someone having this problem in the los16 beta thread.

Thanks in advance :)
[OnePlus 3 & 3T Cross Device Development] knpk13:
All the reports in the LOS 16 thread say it doesn't work at all. The feature seems to work for me on NLOS 16 (I don't use it, just downloaded an app to check if the monitor showed any info) and this is the position I get on a clean flash.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Not true lol. The people who read the message will flash the firmware so you won't get posts from them on XDA and you won't know they read it. The people who don't read it will post on XDA so you'll only see them making the posts. Sampling bias :P So LOS should merge the commit lol.
[OnePlus 3 & 3T Cross Device Development] abhibnl:
Thanks for explaining. And i totally understand your decision.
[OnePlus 3 & 3T Cross Device Development] Halamadrid:
Yes. I agree that i didn't see the error properly. After seeing the error i saw the name of the file. It was named '3t' . I thought the error was because of that, so i immediately went back to my previous rom.

Sorry for the inconvenience. Will try next time by flashing the firmware first.

Thanks
[OnePlus 3 & 3T Cross Device Development] knpk13:
If you're using a recent ROM, you should probably update your firmware regardless of what ROM you're using.
[OnePlus 3 & 3T Cross Device Development] Charles::
Quick Q, I clean flashed/wiped data first. Loaded OOS 5.0.8 firmware > NLOS 16 ROM > GApps pico 9.0 64 bit. Phone boots but I get stuck where the "Checking for updates" screen is right after I connect to a wifi network for the first time during initial set up. When I try to skip that part and update Google Play Services, it just stays on "Download pending". Did I perhaps flash the wrong GApps package?
[OnePlus 3 & 3T Cross Device Development] :
Arrgh, I feared this day.

Background: opengapps are auto build on a nearly daily basis. Generally without any regression testing. Newer is not always better - newer can mean: has regressions.

If using opengapps (MindTheGapps seems to have some issues, if you read a few pages back) I've made it a pattern of habbit to stick to a version, once I found a working one. This doesn't matter, since older versions of the apps are updated via playstore - play and play seevices are autoupdated, no matter of your settings.

I'm currently using https://github.com/opengapps/arm64/releases/download/20181209/open_gapps-arm64-9.0-nano-20181209.zip. On my last clean flash I've got one or two fcs, but the setup went through.

You can also give MindTheGapps another shot: https://www.cyanogenmods.org/forums/topic/google-apps-download-lineage-os-16-mindthegapps-zip-file/

Feedback on this is highly appriciated!

gapps suckz...

Good luck!
[OnePlus 3 & 3T Cross Device Development] cukierkas:
Had the same situation while ago, when freshly installed and flashed open gapps pico . Had same hanging, but used another wifi and after 15mins of waiting - it updated itself. Take your time.

Edit 2: don't forget to factory reset after fresh install. Only this way my dnd switch started to gave the vibrating feedback. Guessing and other stuff might work better.
[OnePlus 3 & 3T Cross Device Development] Charles::
Thanks for the insight. I'll give it a shot!

I waited for over 30 minutes, both wifi and LTE....nothing.
[OnePlus 3 & 3T Cross Device Development] cukierkas:
Hold power button for hard restart, might help. If that won't work, please reflash with gapps package, [MENTION=4405529]nvertigo67[/MENTION] just posted. In my case waiting helped.
[OnePlus 3 & 3T Cross Device Development] mesziman:
Hello [MENTION=4405529]nvertigo67[/MENTION] I just picked your changes to build a ROM just to try out this SDCLANG thing.

I got the error and nfc and solved all good. What I am wondering how the build system decides if it wants to compile with SDCLANG or google clang.

I saw that external/skia was built with google one but system/nfc was with sdclang obviously. I was wondering why it dont get builded all with the snapdragon one.

Do you know ?

maybe this line in nfc/src/android.bp ?:

Anyways I think you may need to pick changes for build/soong to fully utilize the compiler:

look:

https://source.codeaurora.org/quic/...0&id=a3bc430031f316e26064d7f12d9c839f3fde3d9c

https://source.codeaurora.org/quic/...4000-8x96.0&qt=author&q=pzheng@codeaurora.org
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=7637791]mesziman[/MENTION]:

I don't completely understand soong, yet. So I leave my fingers away from the soong patch. By leaving this out we miss eventaully one package or another, but most packages still come with Android.mk. (And no one wants a build the builder doesn't understand... ;) )

Have you tried building with the soong patch? Would you be able to help me out with soong and it's bp files? And most important: would you like to help?

To exclude a package from being build with sdclang (or better with sdllvm - clang is just the c frontend to llvm), just use "LOCAL_CLANG := false" in the packageas Makefile-section.
[OnePlus 3 & 3T Cross Device Development] Halamadrid:
Tbh i flashed the 5.0.8 firmware before installing my previous rom (that time 5.0.8 firmware just came out) . That's why i didn't flashed the firmware this time while installing the recent nlos.

My bad.
[OnePlus 3 & 3T Cross Device Development] deepak jr:
hey [MENTION=4405529]nvertigo67[/MENTION] . can you please create a telegram group where you can announce the upcoming updates and/or have a updater app in the rom please ?
[OnePlus 3 & 3T Cross Device Development] :
Already answered:

https://xdaforums.com/showpost.php?p=78486462&postcount=89

Help keeping the thread readable by searching before posting, please. Thanx in advance.
[OnePlus 3 & 3T Cross Device Development] mesziman:
Yes I am now compiling AOSPExtended and I pulled the soong patches from CAF I will share my notes. when it completes There were a few errors here and there.

it is in 63% so I am waiting when finishes and try it.
[OnePlus 3 & 3T Cross Device Development] mesziman:
HI [MENTION=4405529]nvertigo67[/MENTION]

AEX is finished and it boots so here is what I did for soong:

Cherry-picked from CAF these commits: https://source.codeaurora.org/quic/...4000-8x96.0&qt=author&q=pzheng@codeaurora.org

also this fix: https://source.codeaurora.org/quic/...0&id=8afb4bbc07d6e353c8ddaa97e77b6d7cf3ce3238

art had an error here is the fix: https://source.codeaurora.org/quic/...0&id=d15ee88ee443ad19df19059eff11d27238e49fcb

And for CLANG export the SDCLANG_COMMON_FLAGS here to build https://github.com/syberia-project/platform_vendor_syberia/blob/9.0/sdclang/vendorsetup.sh

You can just put

in your envsetup.sh

I also added -mcpu=kryo there maybe it helps I dont know, I also used the newest sdllvm-lto-defs.mk from CAF.

That's all. Everything built with sdclang except art . :)
[OnePlus 3 & 3T Cross Device Development] mesziman:
[MENTION=4405529]nvertigo67[/MENTION]

I manually deleted the AE stuff from soong because it is empty anyways. Yes I forgot about sdclang.json it cries for it sorry.

EDIT 3+4 : Yes those flags are to prevent those errors like in edit.
[OnePlus 3 & 3T Cross Device Development] pedritopl:
Hi! I finally managed to switch from NLOS 15.1 to 16.0 (clean flash) :) [MENTION=4405529]nvertigo67[/MENTION] - you rule! Thanks :)

I have two questions:

1)

I can't find a way to switch off one of the SIM cards temporarily. In 15.1 it was possible with on/off switches in Settings -> Network & Internet -> SIM cards, but it's seems not possible (yet?) in 16.0.

I just want to make sure if that's one of the not yet ported options or I'm missing something here.

2)

I also can't seem to be able to switch the network operator (in roaming) manually. Whenever I switch off the "Automatically select network" switch and get the list of available networks - selecting one just gets me one menu level back. Is that a known issue?

Also the list of available networks differs from 15.1. In 15.1 the list contained the same operator names listed 2-3 times (separate entries for GSM, WCDMA, LTE maybe?), but in 16.0 the list contains each operator listed only once.

Logcat attached.

260 01 (Poland Plus) is my SIMs home network.

334 50 (Mexico AT&T) is the one I'm selecting manually.

Logcat: https://drive.google.com/file/d/1-SkszNEImVJNCHfg5OVHxs7MmaRe-D3s/view?usp=drivesdk
[OnePlus 3 & 3T Cross Device Development] :
First of all: last night I managed to build booting and running rom with the sdclang-soong patches. You encouraged me to look in soong again. I'll zeroed out ccache stats before building:

ccache -s|grep -e "cache hit " -e "cache miss"
cache hit (direct) 11383
cache hit (preprocessed) 9361
cache miss 28230
cache hit rate 42.36 %

The misses are quite accurate all files compiled with sdllvm because I wasn't using -O3 before. Prior to the soong patches I had about 9000 files compiled with sdllvm. I was completely wrong, when thinking the majority of packages is still using Android.mk.

I really like the "use env only" patch for two reasons: first because it's more common to me, second because it's always an systhematical error if the very same information is stored in more then one location.

The build itself feels more snappy - can't tell bat life, but it looks promising in deep sleep.

I'll push all needed commits today, after that I'll make e freshly synced build.
[OnePlus 3 & 3T Cross Device Development] :
I use only one sim, but I have no reason to doubt your observation. I guess it will come sooner or later - patches for multi sim ringtones are in the queue, other multi sim additions will probably added, too: https://review.lineageos.org/q/topic:"pie-msim-ringtones"+(status:open OR status:merged)

2)

I'm happy you ask: came across that last night, and womdered if that's a regression due to the soong patches. You saved me from flashing an old build for testing. I'm looking into.
[OnePlus 3 & 3T Cross Device Development] Syssx:
Regarding SIM cards, thing is, in Beta LOS build from Dian which I'm using pretty much from 3 builds ago, the switches are there. On your build, the switches are missing. This is the only reason I'm not using your build, because I'm disabling second SIM for weekends and day off from work (because I don't want anyone to call me on my free days :))

Attaching screenshot from 1.1. build from Dian

View attachment 4680353
[OnePlus 3 & 3T Cross Device Development] Syssx:
I can confirm this, happens on beta LOS build from Dian too.
[OnePlus 3 & 3T Cross Device Development] Sytis:
Has anyone already tried this ROM with MicroG? So far I've been using NLOS 15.1 for a very long time but I'll go for the Upgrade soon and while I'm at it also go for MicroG to reduce the Google footprint on my device a little. Oh and another small, slightly Off-Topic question: I know you will only support devices that you own, therefore could you maybe inform us as soon as you plan on getting a new device which it is so in case we want to switch as well we can still enjoy NLOS? :)
[OnePlus 3 & 3T Cross Device Development] :
Just tell me which commit to cherry-pick additionally, and I'll add it - I've only found the ringtone topic regarding multi sim.

EDIT: https://review.lineageos.org/c/LineageOS/android_packages_apps_Settings/+/231590 is merged upstream will be in the next build together with msim-ringtones.

I havn't had any time slice to play with microg on pie. Sadly, I won't have the time to do so in the near future.

I've answered that a few pagws back: I think I'll use my op3t for another 10 - 12 months.
[OnePlus 3 & 3T Cross Device Development] Zaphod_B_1:
Yup. I'm using the ROM on my 3T since about two weeks with NanoDroid microG Version as Magisk Module.

Can confirm it works, even FCM with Threema and SafetyNet Check green. :good:
[OnePlus 3 & 3T Cross Device Development] Syssx:
You were faster, I just wanted to reply with this commit.

Also I find NLOS bootanimation a littlebit dull, so I tried to revive my old after effects "skills" and came up with this: https://streamable.com/e0013. It's just a basic idea (it transitions from the stock OP bootlogo), I have some improvements already in my head which I'd like to make but I have no time atm.

Should I continue working on it, or are you statisfied with your current boot animation?
[OnePlus 3 & 3T Cross Device Development] :
Looks great. I love the slight movement on the lettering at the end. Go ahead.

(BTW: our current bootanimation needs back_in_black boot logo for a smooth first transition. Basing the bootanimation on the current bootlogo seems a good idea to me.)
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (kernel: vdso; soong: use SDCLANG)

Build 20190105

Releasenotes:

NLOS-16.0 relays on OxygenOS firmware. OxygenOS 5.0.8 firmware or later is required:

Oneplus 3T: OxygenOS 5.0.8 firmware

Oneplus 3: OxygenOS 5.0.8 firmware

For a complete list of additional cherry picks see: current.pick.sh.

Changelog (Last repo sync: 5 Jan 2019, 11:51:24 CET / 5 Jan 2019, 10:51:24 UTC):

current.pick.sh: pie-msim-ringtones. — Nvertigo

current.pick.sh: remove pie-privacy-guard; merged upstream. — Nvertigo

current.pick.sh: remove pie-su; merged upstream. — Nvertigo

current.pick.sh: remove pie-legacy-hw-fde; merged upstream. — Nvertigo

NLOS: track our own art. — Nvertigo

Turn off sdclang for art — Pengxuan Zheng

NLOS: track our own build/soong. — Nvertigo

cc: Only use env variables for sdclang — Joe Maples

Fix build error — Jiyong Park

Allow linking against sanitizer libraries from SDLLVM — Pengxuan Zheng

Run header-abi-diff in advisory mode for SDLLVM — Pengxuan Zheng

Rework handling of aarch64_elf64_le_vec for SDLLVM — Pengxuan Zheng

Use QCLD for LTO if SDLLVM is the default compiler — Pengxuan Zheng

Add support for building with proprietary compiler — Pengxuan Zheng

hotfix.xml: remove su; readded upstream. Remove empty hotfix.xml. — Nvertigo

revert "AOSP/Messaging: bump targetSDK to 28 — Raman Tenneti". — Nvertigo

Revert "current.pick.sh: Allow adjusting screen density to smaller sizes." — Nvertigo

SDCLANG-6: add SDCLANG_COMMON_FLAGS. — Nvertigo

op3: Move to common data-ipa-cfg-mgr — Ivan Grinko

arm64/configs: op3: increase log buffer to 1 MiB — Petri Gynther

arm64/configs: Remove LIMITS_LITE_HW config — TeYuan Wang

op3: set default readahead to 2048KB — Wei Wang

ANDROID: mm: add config for default readahead size — Wei Wang

Add AES-GCM support to op3 kernels — Benedict Wong

ANDROID: clock_gettime(CLOCK_BOOTTIME,

vdso updates

NLOS-Bootlogo

nlos_bootlogo-v0.1.zip

back_in_black_bootlogo-v1.0.zip(pre ob16 OxygenOS Bootlogo)

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

Happy flashing!
[OnePlus 3 & 3T Cross Device Development] pedritopl:
Hi. I dirty flashed it over 20181230 build.

Thanks for the SIM on/off switches!

I also tried switching the operator for my roaming SIM to see if anything changed. It didn't work (like in the previous build), but additionally it broke the SIM on/off switches temporarily. I had to kill the Settings app and the switches were back to normal (and functional).

Edit: oh, and a note - the SIMs were both online while Settings showed they're disabled without option to switch.
[OnePlus 3 & 3T Cross Device Development] :
It was merged upstream before I even found it...

As explained quite some times: I can't help you with multisim, since I'm on a single sim setup and - for me - developing is a mixture of knowledge, playing around and trail'n'error. I lack all three for multisim.

For the manual carrier selection I've just posted an issue report in the lineage-16.0 thread.
[OnePlus 3 & 3T Cross Device Development] pedritopl:
Yes, I saw that. Thanks for the effort!
[OnePlus 3 & 3T Cross Device Development] Syssx:
So i did something: https://streamable.com/eakam, i also made bootanimation.zip, but i dont know if its okay (because this was my first time creating it and messing with desc.txt)

WARNING: dont use this bootanimation yet, until [MENTION=4405529]nvertigo67[/MENTION] confirms its actually okay :)

View attachment 4680785
[OnePlus 3 & 3T Cross Device Development] 9Lukas5:
[MENTION=4405529]nvertigo67[/MENTION] thanks for your efforts. I clean flashed the latest build.

By now I have one issue I'm wondering about:

I have an pedometer installed, that continuously counts in background. Now if I reboot the device, the counted steps aren't there anymore.

Tried it with the latest December build yet, it was the same behavior.

Any idea what kind of log probably would be helpful to check this?

The app is the following from FDroid Store:

Pedometer (Count steps) - https://f-droid.org/app/org.secuso.privacyfriendlyactivitytracker

L
[OnePlus 3 & 3T Cross Device Development] :
First and most important: Thank you! I love it. The circling plus sign is great!

It doesn't show up at boot. At a first glance I would guess, it's the missing directory. If I remember correctly part0 is the first transition and part3 is the last transition. Both executed once. part1 and part2 are looping, after part0 was shown untill boot is completed, then part3 is run once.

I need to look closer - but not this night... ...would end in social issues... ;)

Will take a few days before I can look into. If I should guess: something with android permissions. Easiest: it's just not granted - worst case: permission handling of the app hasn't ported to pie, yet.
[OnePlus 3 & 3T Cross Device Development] Syssx:
Great! Theres one more thing though, i noticed that stock bootlogo changed (android logo is more bold, so is oneplus). Could you try and extract it from boot.bin? As i really dont know how (i looked already on google but every attempt failed :/)

Thanks!
[OnePlus 3 & 3T Cross Device Development] pedritopl:
That's too bad for us multisim users of NLOS, especially that I just found another multisim related glitch... ;)

Unfortunately I don't have a LOS 16.0 phone to verify if it's a bug in LOS or if it's NLOS specific.

If I go to Settings -> System -> Status bar -> "System icons" and switch _any_ of the options I get the SIM1 & SIM2 signal strength in the status bar switch places. I mean they switch places every time I change an option there, so if I change two options (or one two times) they're back where they should be, but if I change 1,3,5... times - the signal strength indicators are reversed. It might be difficult to spot if You have good signal strength for both SIMs, but in my case it's obvious as my SIM1 is in roaming and has that little "R" next to it and also "x" showing no data connectivity.

If anyone is able to confirm it's not NLOS specific I am more than willing to report that on the LOS thread.

Oh, and it was already like that in the previous build (20181230). Don't know how it was earlier as I was still on 15.1.
[OnePlus 3 & 3T Cross Device Development] Syssx:
I believe that this behavior is also on stock LineageOS by Dian. In fact, I think I also reported it but didn't paid much attention to it as it's just a visual bug. You could go ahead and report it again, as it looks like it can be a bit frustrating.
[OnePlus 3 & 3T Cross Device Development] pedritopl:
OK. I see Your post from 20th of December in the LOS 16.0 thread. I'll remind about that in the LOS thread in such case.

Thanks!
[OnePlus 3 & 3T Cross Device Development] :
A night of sleep is really great... ;)

I was completely wrong yesterday. You've adjusted desc.txt perfectly. part1 is the looper, part0 and part2 is intro and outro. The problem with not showing was the compression: bootanimation.zip (bz) shouldn't be compressed at all.

After unziping your bootanimation.zip and reziping with

zip -0qry -i \*.txt \*.png \*.wav @ ../bootanimation.zip *.txt part*

the bootanimation showed on boot. Now the bz was about 14 MB. Since you doesn't really need 8bit rgb, I changed all pngs to 256 colors

pngquant --force --ext .png *.png

and the size droped to 4 MB without any visible quality loss (expectable).

The resulting bz is attached. If you want to use it and your device is rooted, just copy it with a root enabled filemanger to /system/media/ replacing the existing bootanimation.zip, reboot and enjoy. If your device isn't rooted, save bootanimation.zip to /sdcard/Download, boot to twrp:

on the mount page mount system

start the terminal from the advanced page

copy the file:

cp /sdcard/Download/bootanimation.zip /system/media
chmod 644 /system/media/bootanimation.zip

reboot and enjoy

For the boot logo: for my personal taste (no law by nature, just my taste) the old pre-ob15 bootlogo is much nicer. Compared to the current bootlogo it's a bit smaller and more elegant: if the old one is speaking, the current one is shouting out loud. To get the old bootlogo just flash the back_in_black bootlogo.

On the other hand, the current bootlogo as base is more straight forward, since no additional flashing is needed.

On the third hand (yeah... ;) ) if remembering correctly the size and position is changed, meaning you need to redo nearly 700 pngs... Your decission. logo attached.

There's one problem left: the animation is slow at the beginning, halfway it speeds up to - what I guess - normal speed. I have no clue at all why... Because cpu and gpu should be able to handle that. Perhaps reducing the frame rate to 45 could help, but I havn't tested (that would also decrease the normal speed by 25%, which requires to drop some pics to get "normal" speed).

The "trick" with reducing the color depth is taken from:

https://github.com/aosp-mirror/platform_frameworks_base/blob/master/cmds/bootanimation/FORMAT.md . Which is also a great lecture on bootanimation.zip in general.

[MENTION=9350973]All[/MENTION]: it's save to check out the new bootanimation - if you don't like it, just dirty flash.

EDIT: OP3Tinject.zip contains a win executable. It's a commandline tool for extracting/changing pics from/to logo.bin . I havn't f9und something like this for linux, sadly. Any pointer is highly appriciated!

EDIT2: changing the framerate to 45 doesn't solve the slow animation issue - just tested.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Boot logos don't reset unless you flash a ROM that changes it right? Like OOS? Or is there a way to reset the boot logo to the default one?

Is there any way to switch to the original (new) OOS boot logo for comparison (without flashing OOS) ? I'm using the back to black logo right now.

And the new bootanimation isn't bad, but I prefer the old one for it's simplicity. So I hope you offer the old one as an option even if you decide to switch to the new one.
[OnePlus 3 & 3T Cross Device Development] :
If you flash a fw package the current logo.bin is restored. No caches wipe, nor somethimg else, just flash fw and reboot.