yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] Syssx:
This could be due to animation being rendered already at 60fps, I changed framerates in my composition from 60 to 30 and animations still seems smooth to me.

I also took advantage of that rotating "+", and made whole bootanimation around it (basic idea is that the + disappears and then appears again every time) here: https://streamable.com/sna46

Also I'm not changing PNGs, After Effects can export video as PNG sequence :). I'm attaching new ZIP (which has 5ish MBs when rendered at 30fps), I zipped with with 7zip as "store" without compression, so it should be okay (I dont have time to test it tho, as I really need my phone to be functioning now).

View attachment 4681230
[OnePlus 3 & 3T Cross Device Development] :
I like the idea to usemthe plus sign as spinner. Overall I like your first version more:

The outro with text moving to the sides is just "wow". I love it, I want it!

The second version hit my problem with the new boot logo. It's hard for me to put it in words (I like talking of hard facts more, then putting personal taste in words): like with the bootlogo the "larger and fatter" lines and characters look somehow "cheaper". While the old bootlogo (and your first version for this matter) looks clean and precious, taking advantage of our device's great display, the new one looks like "wanting, but not able", as if the display lost it's brilliance - somehow "cheap", or "not good enough"...

BTW: take your time. Work on it, if you have the time. It should be fun for you. If there's time presure because of other tasks, stop working on it. I belive this all is an aesthetical matter, not a matter of today or next week/months.
[OnePlus 3 & 3T Cross Device Development] pedritopl:
BTW - off topic, but might be useful. I found this app, haven't tried it yet, but it looks interesting. Especially for all those that feel they *need* the latest firmware the very second when new OxygenOS is released ;)

OOS Firmware Extractor (Extract firmware from official Oneplus roms) - https://f-droid.org/app/fr.witchdoctors.c4ffein.oosfirmwareextractor
[OnePlus 3 & 3T Cross Device Development] Syssx:
Allright, so there's 2 things. First is that as you said, when I make it with the old bootlogo, then the first transition will just look bad without flashing old boot.bin, which is in my opinion not worth just for the sake of boot animation looking good.

So there are options:

1) old bootlogo

2) new bootlogo (fat one)

or 3) I could try and make it without transition from bootlogo into bootanimation (but I have no idea how that would look)

Just pick one (1 or 2 preferably), and I'll do it :)

Also, do you have by any chance NLOS logo in a PNG format without background? I've used the one from bootanimation, but removing background isn't always perfect in photoshop and the logo is not as crisp as it could be.
[OnePlus 3 & 3T Cross Device Development] :
Honestly: the bootanimation is all about looking good. Otherwise the bootanimation could be completely removed (then just the bootlogo is shown all the time).

My first idea was using the bootanimation update to get in inline with the current bootlogo. But the more often I look at it (compared from one boot to the next in a quick frquency), the more I think it's worth an additional flash. Therefor I opt for 1).

Sadly no. I havn't done the logo myself, and I have only the stuff in the rom.
[MENTION=4379461]UnbracedTundra[/MENTION]: if you are still around here on xda, would you be so kind to make a nlos-logo png without background?
[OnePlus 3 & 3T Cross Device Development] :
Did this work on other p roms? Did you check the android permissions? Is this also haening if you force close the app or only on reboots? If the steps are lost on force closes, too, get a log.

I've searched the web for over an hour without finding a support forum other then the reviews on ps: https://play.google.com/store/apps/details?id=org.secuso.privacyfriendlyactivitytracker F-Droid does not offer any support thread.
[OnePlus 3 & 3T Cross Device Development] 9Lukas5:
Short version:

Latest FDroid Version: 1.0.5

Latest version of GitHub: 2.0

App is faulty, not the rom

Huge thanks for the time you spent investigating this, if I've had known you still search for this, I've had posted the GitHub link earlier ????

P.S: small thing but wanted to mention it:

I used m4a files placed in Notifications folder, those didn't work on pie anymore, had to convert them to ogg^^

Long version:

I have no clue what's up with other pie roms, as this is the first pie I've installed and the phone is now fully configured again as it's my daily driver and I won't have time for flashing back and forth the next time (exam time's coming ?).

I've a Nexus 5 running pie, too. But sadly the sensors aren't working there, so also there's no way to test there ?*♂️

The GitHub repo is found here:

https://github.com/SecUSo/privacy-friendly-pedometer

The last version in FDroid was 1.0.5.

In GitHub they have version 2.0 yet, but scrolling through the issue tracker it seems v2.0 has still a few bugs here and there ?

With this v2 on force close the steps didn't get lost just now, but the chart when they got recorded changed ??

Nevertheless I have cloned it and build the latest codebase. The result is, autostart isn't working properly anymore and it seems a bit of a lottery how often I've to kill the app after a reboot until it starts counting again.

Seems not fully reliable that it counts, but we'll see if there happens something in the future^^.

But I'm pretty sure it's not the fault of your rom, but of the app.

I use the tracker to have a quick indicator of I should do a walk in the evening or not, but it's not necessary that the tracker works perfectly^^.

L
[OnePlus 3 & 3T Cross Device Development] Syssx:
What about this? It's just an idea again :) - https://streamable.com/u1mik - old bootlogo, and ending is combined ("+" and moving text together).
[OnePlus 3 & 3T Cross Device Development] :
Best of both - great! I like the visual "echo" of the logo in the looper sequence.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Sq

This is so much better than the earlier ones. I'm personally not fond of the tagline though since it seems a bit cluttered. I think no text at all looks better.
[OnePlus 3 & 3T Cross Device Development] mesziman:
I am glad it went well. Yes env only is more logical if you want to change you change in one place. More clear.

The ROM zip built by this also got noticably larger for me. There is around +30M for sdclang build compared to the very same build without it.
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (Jan. Security Patch: android-9.0.0_r30)

Build 20190109

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: 9 Jan 2019, 12:19:25 CET / 9 Jan 2019, 11:19:25 UTC):

Update bootanimation. — Syssx

Add OpenWeatherMapProvider. — Nvertigo

current.pick.sh: "Disable art debug and enable minimize debug info". — Nvertigo

current.pick.sh: pause for conflict resolving of 221716. — Nvertigo

Revert "current.pick.sh: "softap: sdk: Add 'vendor.' prefix to wlan.driver.config"." — Nvertigo

current.pick.sh: "power: Build with with BOARD_VNDK_VERSION". — Nvertigo

current.pick.sh: "power: msm8937: Update power profile settings". — Nvertigo

current.pick.sh: "power: Add specific powerhal for msm8937". — Nvertigo

current.pick.sh: Revert "AOSP/Messaging: bump targetSDK to 28". — Nvertigo

current.pick.sh: remove revert "AOSP/Messaging: bump targetSDK to 28 — Raman Tenneti". — Nvertigo

Revert "current.pick.sh: "op3: Update FOSS props for Pie"." — Nvertigo

current.pick.sh: "softap: sdk: Add 'vendor.' prefix to wlan.driver.config". — Nvertigo

Revert "current.pick.sh: "livedisplay: Update FOSS status prop for Pie"." — Nvertigo

current.pick.sh: "op3: Update FOSS props for Pie". — Nvertigo

current.pick.sh: "livedisplay: Update FOSS status prop for Pie". — Nvertigo

current.pick.sh: pie-qcom-wfd: exclude abandoned commit 237194. — Nvertigo

current.pick.sh: pie-qcom-wfd: exclude abandoned commit 237174. — Nvertigo

current.pick.sh: remove "common: Allow init to relabel I/O sched tuning nodes". — Nvertigo

current.pick.sh: remove "common: Label and allow access over LiveDisplay sysfs nodes". — Nvertigo

current.pick.sh: force pick: "Crash app on foreground service notification error". — Nvertigo

revert: current.pick.sh: "common: Expand labeling of sysfs_vibrator nodes using genfscon". — Nvertigo

NLOS: track our own chromium-webview. — Nvertigo

current.pick.sh: remove FDE stuff; merged upstream. — Nvertigo

current.pick.sh: remove "lineage-sdk: Start Weather service in onUnlockUser.". — Nvertigo

current.pick.sh: update pie-fde-crash-fix picks. — Nvertigo

current.pick.sh: "config: Add Deskclock to power whitelist". — Nvertigo

Revert "current.pick.sh: op3: Add QCOM's WFD implementation." — Nvertigo6.0

Revert "op3: Set new QSEE listener status flag on old one changed" — dianlujitao

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:
Thumbs-up for the new bootanimation :)

BTW: first time booting this build (after dirty flash over 20190105 build + wipe Dalvik&Cache) took significantly longer then usual (compared to other builds first boots after wipe Dalvik&cache). Is that an expected behaviour?

Second boot - perfectly normal.
[OnePlus 3 & 3T Cross Device Development] :
Yeah, I like it, too. It's not the final version (@Syssx: take your time, please), but definetly shipable.

Maybe the dex2oat after cleaning caches: The more apps and services needed to be "dex2oated", the longer the boot after clearing caches takes. The dex2oat takes longer if the device is on charger (thermal throttling is hit - especially when dash is used). Other then that I see no resons for a longer boot.
[OnePlus 3 & 3T Cross Device Development] pedritopl:
It was on charger, but not Dash, and it wasn't hot, because it was on 100% charge since a few hours already (overnight charging).

Anyway - don't know what was the reason, but after all it booted fine and second boot was normal, so no problem.
[OnePlus 3 & 3T Cross Device Development] Syssx:
The animation is really slow (as you mentioned), is this the 60fps version? I also noticed that after entering PIN for decryption, the animation plays from the beginning. Is it even possible to play just the middle part again after entering the pin?

And yeah, it's not the final version :) I'll definitely finish it when I'll have some free time.

Edit:

Im curious about these changes:

current.pick.sh: "power: msm8937: Update power profile settings". — Nvertigo

current.pick.sh: "power: Add specific powerhal for msm8937". — Nvertigo

MSM8937 is Snapdragon 430 according to Google, what does it have to do with our device? :) I'm really curious.

Thanks
[OnePlus 3 & 3T Cross Device Development] :
Yes, it's the 60fps version. I'm not sure, but since the normal speed comes while booting, I guess full performance is there, after the cpusets are setup. Currently I've no idea, how to circumvent the initial slowlyness.

It always starts over from part0. Nothing we can do about.

Lazyness: these are in the same relation chain as "power: Handle launch and interaction hints for perf HAL platforms". It's easier to merge without conflicts. This also reduces the chances of a mismerge. In the end just more comfortable for me.
[OnePlus 3 & 3T Cross Device Development] knpk13:
I can confirm that first boot after dirty flashing this build (compared to other builds) was significantly longer (around 15 min, as opposed to the normal 2-3 min). I use LiveBoot so I could see the boot log during the boot animation and most of the lines contained dex2oat. Is there any reason dex2oat is taking longer on this build compared to the previous ones?

Device was not being charged. And the number of apps hasn't changed in the last few builds.
[OnePlus 3 & 3T Cross Device Development] :
Is it reproducable? I can't reproduce it:

Wiped caches; reboot (time from encryption pin to sim pin) takes nearly 3 minutes.

Dirty flashed 0105 with caches wiped: reboot takes nearly 3 minutes.

Dirty flashed 0109 with caches wiped: reboot takes nearly 3 minutes.

Before starting with anything, uninstall (not only deactivate, but uninstall!!!) all mods and overlays. Uninstall all apps changing the boot sequence.

If you can reproduce it, take logs!

[MENTION=6561751]pedritopl[/MENTION]: I didn't understand, that long means something like 15 minutes. 15 minutes definetly means somthing is serioisly wrong.
[OnePlus 3 & 3T Cross Device Development] knpk13:
How do I take logs during boot without LiveBoot? That's why I had it installed in the first place.

And by uninstall overlays, are you referring to substratum? I don't have any mods installed other than magisk since I don't need Xposed anymore (which I used for Android P-ify). Should I uninstall magisk as well when taking logs (not sure if you support it after reading OP) ?
[OnePlus 3 & 3T Cross Device Development] pedritopl:
Yeah, I wasn't sure how long it took, but definitely was around 10-15 minutes...

I'll try reproducing.

Edit: sorry, no luck with reproduction. It now boots normally after Dalvik&Cache wipe.
[OnePlus 3 & 3T Cross Device Development] :
Taking logs with liveboot? I didn't know it's taking logs. But that's great. Share the logs from the long boot.

I always use logcat and dmesg to generate logs.

Yes.

Uninstall additional modules, because they change the boot sequence.

Anyway: since I can't reproduce this myself, I can't help without logs.

[MENTION=9350973]All[/MENTION]: Has anybody but [MENTION=7134312]knpk13[/MENTION] and [MENTION=6561751]pedritopl[/MENTION] expirienced boot times >10 minutes, when dirty flashing 0109 over 0105? Has anybody immediatly taken a log of this?
[OnePlus 3 & 3T Cross Device Development] dewa5227:
Uhm, nope. Mine boot normally fine. Under 10 minutes after dirtyflashing over 0105
[OnePlus 3 & 3T Cross Device Development] ileeba7:
Nope, dirty flashed over the last build. Wiped dalvik and cache and the phone booted up in few minutes. No problems here
[OnePlus 3 & 3T Cross Device Development] phoberus:
30fps is enough for animations. Over 24 is fluid for our eyes. If you want to make it smoother, use motion blur in after effects

I had 5 minutes instead of only one. Dirty flash from 30.12.2018 build to the newest
[OnePlus 3 & 3T Cross Device Development] Kimple:
[MENTION=9350973]All[/MENTION]: Has anybody but [MENTION=7134312]knpk13[/MENTION] and [MENTION=6561751]pedritopl[/MENTION] expirienced boot times >10 minutes, when dirty flashing 0109 over 0105? Has anybody immediatly taken a log of this?[/QUOTE]

Flashed over 0105.

1) wiped dalvik, cache and system

2) flashed 0109, opengapps 0110 pico, magisk 18.0

3) wipe dalvik and cache

4) reboot system

Time between encrypt pwd and sim pwd less than 3 minutes.

Thank you for this ROM
[OnePlus 3 & 3T Cross Device Development] :
Thanx for the feedback.

General note on dirty flashing:

My dirty flash drill is:

flash new rom zip

wipe caches directly from the flash sucess page

reboot to system directly from the wipe sucess page

If you don't wipe system and twrp finds scripts in /system/addon.d it uses them to backup files and restore them (including the scripts themselfs) after the rom was flashed. For me this is gapps and magisk. There's no need to flash gapps and magisk (or any other zip that creates a script in /system/addon.d for that matter) on every rom update (aka dirty flash).

If you prefer to wipe system, make sure you always use the very same package as on initial install: if an app or a service from the initially used gapps package is removed (which can happen on opengapps even if using the same package size, or if you interchange from opengapps to mindthegapps or vice versa) when using an updated version with a different file list, you'll be in trouble sooner or later (due to "stale" settings in the gservices db). Always remember: gapps suckz!

You don't need to care about updatimg gapps on a running setup: ps and pservices are auto updated from ps, not matter of your autoupdate settings, for the other apks from your gapps you'll be prompted by notification if autoupdate is disabled.
[OnePlus 3 & 3T Cross Device Development] matrixisreal:
I can not restore my whatsapp backup with oandbackup.

I had this problem since the first builds of this ROM (one of the reasons why I have not stayed on this ROM(performance was also bad, but testing now the latest version and it seems improved)

This is the only ROM I have seen which has this problem with oandbackup.

I also think I had other "storage" related problems on this ROM, but I can not tell what exactly because I have not used the ROM really for longer.

PS: I can not copy the text from the error message, that's why only screenshot

Edit: workaround was to install the apk manually and restore only the data with oandbackup.
[OnePlus 3 & 3T Cross Device Development] evopen:
can i ask why the gpu render time is so much lesser than original los? [MENTION=4405529]nvertigo67[/MENTION].

Doesn't seem to because of the kernel. Magic.
[OnePlus 3 & 3T Cross Device Development] :
Really?

https://xdaforums.com/oneplus-3/one...eplus-3-3t-t3739169/post78382733#post78382733

https://github.com/jensstein/oandbackup/issues/

https://www.google.com/search?ei=J1.......1..gws-wiz.......33i160j33i21.dwqDb7jY_9A

I guess you havn't looked close enough, if you really think: "This is the only ROM I have seen which has this problem with oandbackup. " :(

What a claim... ...this leaves me spechless behind... :(

Best practise: get a log.

Does it ever come to yoir mind, that this practise is the reason for your mysterious storage issues?

You best option is to give a proper issue report to the app dev. A proper issue repprt includes (not limited to) a detailed issue description (not: I also think I had other "storage" related problems on this ROM) including steps to reproduce and a log from doing these steps.

Personal note: "I also think I had other "storage" related problems on this ROM, but I can not tell what exactly because I have not used the ROM really for longer." Combined with "This is the only ROM I have seen which has this problem with oandbackup." makes me always wonder about the motivation of such postings... :(

None of these statements is helpfull for debugging and solving the issues, nor true... :(

I've no idea. If ther's no change in the display comtent the graph shouldn't move on both builds, it should stand still. The bars you see is the past. Maybe you've just done other actions before the display "stood still". Also: los is heavy wip currently. If you compare a build before this: https://review.lineageos.org/c/LineageOS/android_hardware_qcom_power/+/237002/3..8/power-8996.c with a build done after adding the timings, this may result in differences like you've observed. But in the end: I don't know.
[OnePlus 3 & 3T Cross Device Development] matrixisreal:
Its the only ROM for OP3 with this problem I have seen so far.

The other storage issue is that aurora store can't install the apps with root.

Performance seems to be really good most of the time actually. So far best performing Pie ROM I've tried

And sorry for not providing the logs in the first post.

In the screenshot you see " sdcardfs" and I thought you would already know that there's an issue because since the ROM is for people like us who don't use gapps, so I might be not the first one who has had issues with aurora store.
[OnePlus 3 & 3T Cross Device Development] evopen:
Ok~ I'm gonna report this to dianlujitao. BTW, it seems that color profiles with DCI-P3 won't survive reboot?
[OnePlus 3 & 3T Cross Device Development] :
The dci-p3 and srgb not persistimg through reboot if a boot password is set is by design of livedisplay. It's long known (since 15.1), there is an open jira ticket - but I doubt livedisplay will be rewritten.

EDIT:

Ok, there WAS a ticket. jira.lineagos.org redirects to gitlab issue tracker and I can't find the old ticket in gitlab. (Interesting method to get rid of open tickets... ;) )

Basically: for srgb and dci-p3 livedisplay uses /data/vendor/display/*, which is needed when the dialog for boot passwd is fired up, but this is available only after the data partition is decrypted... The panel modes (dci-p3 and srgb are kernel modes) are set much later in the boot process - which works well.
[OnePlus 3 & 3T Cross Device Development] :
Why do you repeat that after my posting clearly proving there are many roms oandbackup has issues with? I gave you a links that shows that you get storage issues if using oandbackup - across many roms and devices. Just repeating "Its the only ROM for OP3 with this problem I have seen so far." doesn't help anybody and it doesn't become true by repeating.

These are app issues:

I've no issues at all with restoring wa messages after a clean flash - you have issues with restoring wa, after using oandbackup. I have no issues with storage habdling, you get storage issues after using oandbackup... What more can I say? It's quite obvious, isn't it?

Do a clean flash, install wa from ps and restore your local (or clouded) wa chat backup and it will work perfectly.

For the logs:

aurora:

I can't even see an atempt to call PackageInstaller. It only shows that aurora wants to spam the log and the rom is suspressing the output:

01-11 12:57:45.757 W/RecyclerView(3857): RecyclerView does not support scrolling to an absolute position. Use scrollToPosition instead
01-11 12:57:45.857 V/chatty (3857): uid=10086(com.dragons.aurora) identical 12 lines

This is obviously a error in the app's use of RecyclerView.

oandbackup:

01-11 12:59:11.802 E/oandbackup(15523): cannot restore data without restoring apk, package is not installed: com.whatsapp

That's the only oandbackup error I can find, and that makes sense to me.

Both logs are incomplete. Are all requested permissions granted to oandbackup and aurora on boot while package parsing?

(disable chatty: https://code.i-harness.com/en/q/20fc289 )
[OnePlus 3 & 3T Cross Device Development] matrixisreal:
it may be that oandbackup and aurora store both have bugs which causes this issues.

But, as I've said, this is the only ROM I have had this issues with oandbackup and aurora store.

since both apps have problems installing the apk with root, the main problem might be not storage related but maybe packageinstaller (don't know how its called 100%) or the root counterpart of it since I can install the apk normally when selecting it manually.

And yes the ROM was clean flashed. Even with full /data wipe
[OnePlus 3 & 3T Cross Device Development] matrixisreal:
I have tried to disable chatty but nothing works.

logcat -P ""

This also doesn't work
[OnePlus 3 & 3T Cross Device Development] :
Seems to be broken for "-P 'uid/pid'. The list is properly set, but logd doesn't seem to care. Will look into.

Sidenote: the above command with an empty string clears the list. In other words: even with -P working, this command would enable chatty line collapsing for all processes again.
[OnePlus 3 & 3T Cross Device Development] :
On oandbackup

To use oandbackup you need to set sepolicy to permissive (which I don't recommend!!!). I don't know why, but oandbackup violates - at least - 3 never allow rules. It also triggers a denial by an never allow rule for system_server... Even /system/xbin/busybox can't be found by oandbackup, which is readable to the world...

Titanium uses root previlegs to circumvent these denials and I have no clue why oandbackup runs into them though it has root access granted.

All this relates to the apps permission and root handling and has to be fixed in the app, or the rom needs to be run in selinux' permissive mode.

If anybody feels that running selinux in enforcing mode is an error of the rom, I would kindly ask to use another rom with selinux set to permissive, because that will NEVER happen on nlos.

[MENTION=9012416]matrixisreal[/MENTION]: did you receive any feedback from the devs, yet?