yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] :
Somedays it's a tough task to stay polite and non-sarcastic. I'll try hard in this posting, but if I'm not tough enough and fail on doing so, please be patient with me; I don't want to offend anybody.

Over the last months the bad habbit of not collecting and sharing as much information and just throwing some catchwords in and answreing by just throwing some wild guessings in jas dramatically increased in the op3/t forums and other areas of life.

Gopd examples are the talks of volte working/not working. Though it's completely clear that this may differ from carrier to carrier, and some users explicitly ask for mcc/mnc no single mcc/mnc double has been shared or taken in acount - the discussion just continuous... :(

Another good example is tbe change of habbits regarding logs on xda in general: 7 year ago all issue reports without logs has been ignored - nowadays all request for logs after a log free issue report ate ignored.

And my current favorite example: "I've read that bleach kills SARS-CoV-2." Leading up to people drinking bleach to prozect themselfs from cpvid-19. (BTW: strictly logical this is true: if the host dies, all SARS-CoV-2 will die after a üeriod of time; or the deceased will not be infected.)

Lack of information will lead to stupid, random and/or dangerous guessing mask as decisions. These mask guessings are taken as educated decissions by others basing their discisions on and spreading the results. These results are taken as facts by otjers, basing their actions...

That being said: I've never expirienced random freezes nor overheating my device - this may be due to the fact, I've never run my device longer then 1 days, 7 h and 31 s (my highscore!!! ;) ) without intentionally rebooting it. Considering this I've no information I can base any comment on [MENTION=5925270]hellcat50[/MENTION]'s question on.

Just a note: the more complex socs became, the smaller the operating limits got. At the same time it gets mote and more difficult to ensure the manufacturing tresholds. That's why the nlos' shipped kernel doesn't offer any undervolt/overvolt and underclock/overclock (not to be confused with max clock limiting) features.

Anyway: don't drink bleach, don't inject germicide to your body - this will kill you!

Take care of each other!
[OnePlus 3 & 3T Cross Device Development] :
UPDATE?

I wonder if a new webview version is worth an update:

Kevin Hagerty has managed to build a working chromium-webview (81.0.4044.117). This is the ONLY change an update would offer. What do you think? Ship an update?
[OnePlus 3 & 3T Cross Device Development] MSe1969:
AFAIK, there hasn't been any major security issue, which is fixed with this WV update - you're currently providing a late M80 version and M81 simply is a maintenance evolution. Looking at the fact that 1st Monday each month is ASB day, we would therefore talk about ~ 2 weeks to publish the next regular update with ASB patches. If you ask me, not worth it (I have however to admit, that I am not a direct user of NLOS, but taking advantage of the fact that the two of us follow each other's OP3(T) thread and share thoughts)
[OnePlus 3 & 3T Cross Device Development] :
I greatly appriciate your input!

I think the same - and due to no other posings I guess most other users think so, too.

In deed there's no chamge effecting our builds but https://review.lineageos.org/c/LineageOS/android_packages_apps_Snap/+/272554 - but since quickreader is not accessible at all on op3/t builds... ;) (The ppp fixes are in my last build - you've pulled them earlier; so it's really only the webview.)

I've just thought I ask; maybe someone has isuues with webview or I've overseen some major security flaw with chromium webview 80.0.3987.162 - and signal implicitly that I've an eye on the necessarity of updates. ;)
[OnePlus 3 & 3T Cross Device Development] hellcat50:
I usually use bromite webview, so that's not a problem for me :)

BTW I am sorry for the post i did earlier. I will try to not post something like that again in the future.
[OnePlus 3 & 3T Cross Device Development] :
No need to feel sorry. Let's try to get information on this - at least to me it seems - very complex issue. It was just that morning when I felt like all Enlightment (philosophic), sience and Epistemology are thrown away to take random action.

"I read somewhere" was just like a penalty without goalkeeper. Putting a try of undervolting in a row with recommending lifethreading sh!t was offensive - I appologize for that.

Back to the complex issue: it's important to het as much information as possible. The first step is to describe the issue as detailed as possible. E.g. if the heatiing is notible before the freeze, try getting logs and view the processes with e.g. htop, or logs e.g. fetched via adb can run in the background (this can get ugly large, but may allow a view on why thermal throttling doesn't kick in). As stated, I belive this gets complex, ugly and dirty; and maybe will not yield any fix - but just shooting in the woods without seeing the rabbit will most probably end in no rabbit for dinner...
[OnePlus 3 & 3T Cross Device Development] andrew2511:
Hi [MENTION=4405529]nvertigo67[/MENTION], thank you for your awesome work! I've just one question about these commits, is audio transmitted using WiFi Display? In all the other Pie roms it's not working. Thank you :good:
[OnePlus 3 & 3T Cross Device Development] :
Working for me with the last build. For widi/miracast as well as for chromecast.
[OnePlus 3 & 3T Cross Device Development] abhibnl:
Hello, sorry for asking so many questions but were you able to find any way to hide Sim is HD capable persistent notification? It actually is an indication that SIM supports VoLTE but in almost all pie roms i tried, VoLTE appeared as an icon in status bar rather than this persistent notification. I know lineage has a different base but is it safe to disable the package org.codeaurora.ims to get rid of this notification or is it an important system component?
[OnePlus 3 & 3T Cross Device Development] :
You can try. To my knowledge all ims based stuff will be disabled if ims package is not present.

Since my carrier doesn't support volte for my device, I can't test that. My way of developing is often just trial and error, I can't help you. I would suggest to wait untill los 16 goes nightly and open a jira ticket.
[OnePlus 3 & 3T Cross Device Development] abhibnl:
Thank you good sir for your insights. And thanks for developing such a stable ROM for OP3. Everything just works fine and I love the no random BS approach you have here. I am only using Magisk and no custom kernel or exposed or any other "tweaks".
[OnePlus 3 & 3T Cross Device Development] netmm:
quick question: the performance slider in battery settings was set to the far right (max. performance) for me.

Did I do that by accident or is this how it's supposed to be? Any major battery hits with the setting?

Regards
[OnePlus 3 & 3T Cross Device Development] :
It's not intended. It should be balanced. Before spending a night on searching in the code, can another user confirm the performance profile is on max performance after a clean flash, please? Thanx in advance.
[OnePlus 3 & 3T Cross Device Development] abhibnl:
I flashed this as a clean flash coming from OOS, and the profile its running on is Balanced. I don't think it's a ROM issue by any chance. he might have been using a custom kernel or some kernel tweak app or similar tool.
[OnePlus 3 & 3T Cross Device Development] andrew2511:
I clean flashed too (27 Dec build), profile was set on balanced.
[OnePlus 3 & 3T Cross Device Development] cukierkas:
https://ibb.co/XLDtcdd

Balanced. Made a a fresh flash yesterday from latest stock. Wanted to see how it behaves, but nicht, nlos is like mother, calls back with a hug ;)

Regards.

Edit: had problems installing latest mindthegapps package, arm64 , pie. Installation wrnt OK, but the setup wizard, at first launch always crashed with WiFi error and pixel setup error :)

Reflashed with opengapps pico - all is fine and rock solid.

Edit 2:

Guys, what gcam version you're using? If yes, what your fave settings? Op5t makes photos clearer and sharper, even compared gcam by arnova on 3t. Looking for setup to try and forget.
[OnePlus 3 & 3T Cross Device Development] 64ashg:
The latest tylon build in the gcam thread is what you are looking for :)
[OnePlus 3 & 3T Cross Device Development] ramspeed22:
nice rom
[OnePlus 3 & 3T Cross Device Development] phoberus:
Got the logs with the newest 20181227 build.

Found this lines, maybe they are related:

12-28 22:36:50.458 I/ActivityManager(827): Displayed com.nianticlabs.pokemongo/com.nianticproject.holoholo.libholoholo.unity.UnityMainActivity: +895ms

12-28 22:36:50.515 I/ActivityManager(827): Start proc 30445:com.nianticlabs.pokemongo:fitness/u0a110 for service com.nianticlabs.pokemongo/com.nianticlabs.background.fitness.FitnessJobService

12-28 22:36:50.522 I/Magisk (507): proc_monitor: com.nianticlabs.pokemongo/com.nianticlabs.background.fitness.FitnessJobService PID=[30445] ns=[4026534457]

12-28 22:36:50.601 E/kemongo:fitnes(30445): Not starting debugger since process cannot load the jdwp agent.

12-28 22:36:50.623 I/PBSessionCacheImpl(2968): Deleted sessionId[1802166725038] from persistence.

12-28 22:36:50.627 W/SurfaceFlinger(666): Attempting to set client state on removed layer: Splash Screen com.nianticlabs.pokemongo#0

12-28 22:36:50.628 W/SurfaceFlinger(666): Attempting to destroy on removed layer: Splash Screen com.nianticlabs.pokemongo#0

....

12-28 22:37:01.954 I/ActivityManager(827): Process com.nianticlabs.pokemongo:fitness (pid 30445) has died: cch+6CEM

12-28 22:37:01.961 W/libprocessgroup(827): kill(-30445, 9) failed: No such process

12-28 22:37:01.961 I/libprocessgroup(827): Successfully killed process cgroup uid 10110 pid 30445 in 0ms

12-28 22:37:02.015 I/WorkerManager(2968): Unloading disused workers

12-28 22:37:02.047 I/Finsky (2976): [2] com.google.android.finsky.dc.d.onTrimMemory(4): Memory trim requested to level 10

app in this case: com.nianticlabs.pokemongo

not app related, I can also sent logs from an other app if you want.

full logs attached
[OnePlus 3 & 3T Cross Device Development] :
Please do a clean flash with only gapps or microg and reproduce with no other apps installed and get a log.

The log you provoded shows a crash (and many premature dyings) of com.theappninjas.gpsjoystick and some com.nianticlabs.pokemongo services:

12-28 22:33:01.407 I/ActivityManager(827): Process com.nianticlabs.pokemongo:pgp (pid 14048) has died: prev LAST
12-28 22:33:02.473 I/ActivityManager(827): Process com.nianticlabs.pokemongo (pid 6575) has died: prev LAST
12-28 22:35:54.502 I/ActivityManager(827): Process com.nianticlabs.pokemongo:fitness (pid 28672) has died: cch+4CEM
12-28 22:36:06.225 I/ActivityManager(827): Process com.nianticlabs.pokemongo (pid 28598) has died: cch CAC
12-28 22:37:01.954 I/ActivityManager(827): Process com.nianticlabs.pokemongo:fitness (pid 30445) has died: cch+6CEM

This seems related to the more restrictive battery manager. Have you tried my suggestions from my last posting regarding battery manager or have you tried disabling the battery optimizations for pokemon and all apps related apps like com.theappninjas.gpsjoystick? Did you check the real mem consumtion with free while pokemon is running?

I doubt the premature dying of apps in recents is reproducable on a clean flash.

Why exactly pokemon itselfs decides to exit normally (it's not crashing like it's services) is completly unknown to me, since the app doesn't offer any information on it's activities. (Maybe the log is not complete: it's NOT a logcat [i.e. the lines are refprmated amd the ppid is striped]. If lines are reformated and information is droped, who knows if not complete lines are droped???)
[OnePlus 3 & 3T Cross Device Development] knpk13:
Gps joystick is an app used for GPS spoofing. In this case, for games like Pokemon Go. If there are any crashes or related problems I'd imagine it would be unsupported by you. I tried it out myself and pushed GPS joystick to /system/priv-app using a magisk module and I have no such crashes or other issues. The issues [MENTION=5499170]phoberus[/MENTION] is experiencing is likely due to them using a different spoofing method in the app used instead of using system privs (which is the recommended method for Oreo and above)
[OnePlus 3 & 3T Cross Device Development] :
True, true and true: as stated above, gps joystick is one of the crashing services pokemon relies on. May relate to the gracefull exit of pokemon or not. I've asked for a log from a clean flash, and of course I don't spend my time on supporting a commercial app I've no output from, because it's a closed source non-debug build... ;) I'm good ar guessing - but not that good... Every single point from my last posting is taken from the log - I havn't known of pokemon and it's crashing services before...
[OnePlus 3 & 3T Cross Device Development] Rammit:
Thanks for working screen mirroring. Have tried with other ROMs, sound use to come from mobile...with this ROM it works perfect.

Awesome work.
[OnePlus 3 & 3T Cross Device Development] phoberus:
yes, i did both

No, i'll do it next time.

I used matlog to get the posted zip. The lines I copied out, were from the 2018-12-28-22-37-20.txt

Can't do a clean flash, learning exams at the moment. sorry

First tame I had this bug, also other apps had the same thing. After a restart it's ok again.

I'm also using App Systemizer for Magisk and pushed it to /system/priv-app + simulated gps (mock location).

For me it's not e problem to live with this. I only wanted to share my experience, because it could have been a bug for all
[OnePlus 3 & 3T Cross Device Development] knpk13:
Clear data or reinstall the app, and push it to /system/priv-app

DON'T enable mock locations or anything in dev ops, or change any other settings in the app. The app will configure itself automatically to work in system mode as opposed to using Android's mock locations. I had no memory/RAM issues or any crashes when I played PoGo yesterday with this setup.

Sorry OT , since it's not related to NLOS.
[OnePlus 3 & 3T Cross Device Development] :
Sitting here smiling at you and laughing with you (yes, you will laugh after reading the next sentences), Dude. Welcome to my world. It's such a great activity to pull together all tiny pieces of information over several pages of a thread: the actual issue arn't any crashes that stop one from playing 0okemon with faked locations, but that apps in recents needs to be restarted (exited or died in the background), though there's enough free mem. That's why we try to check if lmk, memory management or battery managment can be the culprit... :) :) :) ;)
[OnePlus 3 & 3T Cross Device Development] devilsworkshop:
Hello [MENTION=4405529]nvertigo67[/MENTION],

Could you please (at least briefly) suggest what I need to do in order to build your ROM for a different device?

I would imagine the process would be more or less the same except for the device-specific bits, but I'm not exactly sure what the device-specific bits are.

While I have built Lineage before (with Sultan's patches), I'm not an expert. If you have a bit of time, I'd appreciate any pointers in the right direction.

(I've been using NLOS as my daily driver on the Oneplus3 for a long time, but recently had to move to the Oneplus 6 due to hardware issues that I couldn't fix thanks to the COVID lockdown)
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=6789884]devilsworkshop[/MENTION]

On this general level it's hard to answer. If the device you want to port to has los-16 device specific files it makes things easier as starting from scratch, of course.

Generally answered:

Setup an build environment and build nlos for op3/t:

https://github.com/nvertigo/local_manifest/blob/nlos-16.0/README (maybe a bit outdated and/or paths has to ne adjusted for your build environment)

This way you'll see how I glue nlos on top of los.

Since I always rebase nlos specific commits and changes on top of the los code base, you can easily see what's nlos specific. You'll also see what I've added to the device spefic repos - depending on the device you may or not may use some of these changes (e.g. you need to include the vendor_nlos repo in your device tree makefiles, but you may not include the kernel toolchain, if your kernel sources doesn't support it; the same goes for kernel). The qcom llvm I'm using to build the rom's c and c++ code other then kernel, may not yield good results on non-qcom-socs.
[OnePlus 3 & 3T Cross Device Development] devilsworkshop:
Thanks for your reply.

I think my best bet would be to first try and build it without the NLOS kernel, with just the userspace stuff. From what I understand, everything except the kernel should be completely device-agnostic, right?

Correct me if I'm wrong - the NLOS kernel is patched by you privately and simply hosted on your github, right? The LOS build process simply pulls it and builds it. Do you provide the patch files or list of changes you make to the official LOS kernel? If your patches are available publicly, I could probably try patching my device's kernel.

PS: The Oneplus 6 was well-supported by LOS 16.0, so all the devices files do exist. I'm not starting from scratch!
[OnePlus 3 & 3T Cross Device Development] knpk13:
I just flashed LOS17 on my 7T Pro. I dont really use the feature but i remembered you were hunting for the QR scanner on snap cam. Well its there in the UI for the 7T so I thought I'd attach a screenshot. I have no idea why its not on the 3T. The app versions on both phones are the same too. For 7T Pro, version 2.02.037 (eng.luk.20200427.114201-00)
[OnePlus 3 & 3T Cross Device Development] devilsworkshop:
Thank you so much for the input. I haven't had the time to get my hands dirty with this yet, but I'm looking forward to it. I think the info you've given me will help get me started. Thanks again!
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (kernel upstreamed to aosp android-3.18; May security patch)

Build 20200508

Releasenotes:

This is the first time since nearly one year, that the kernel jas all ASB patches. Since you know that I failed on upstreaming 3.18.140 to https://android.googlesource.com/kernel/common/+log/refs/heads/android-3.18 (the place where 3.18.y is continued), I'm using the kernel from [MENTION=7929484]MSe1969[/MENTION]'s hardened LineageOS.

This build relies on OxygenOS firmware. OxygenOS 9.0.6 firmware is required. At this point you have two options:

You don't care about loosing data on an unlocked bootloader and clean flash including format userdata according to the first time installation instructions in OP (recommended):

Oneplus 3T: OxygenOS 9.0.6 firmware without alipay and soter files

Oneplus 3: OxygenOS 9.0.6 firmware without alipay and soter files

You want to keep your current setup and like to dirty flash on top of beta builds:

I've created a firmware package from OxygenOS 9.0.6. To avoid issues due to an unlocked bootloader and/or encrypted userdata partition, I've kept the bootloader and and keymaster partition to OxygenOS 5.0.8. This allows to run the pie-blobs builds with native Oneplus OxygenOS 9.0.6 firmware, but you don't need to reformat the userdata partition (for details see: https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164 ).

Oneplus 3T: OxygenOS 9.0.6 firmware with 5.0.8 bootloader and keymaster and without alipay and soter files

Oneplus 3: OxygenOS 9.0.6 firmware with 5.0.8 bootloader and keymaster and without alipay and soter files

If you need to pass safetynet api flash sec-patch-2019-08-01_v02.zip from https://xdaforums.com/oneplus-3/one...-nlos-16-0-t3879405/post78433987#post78433987 .

Before you ask: though I've updated the blobs used in the rom to OOS 9.0.6, I've decided to stick with OOS 9.0.5 build fimgerprint, because 9.0.5 is the only version with identical fingerprint strings for op3 and op3t.

If you want to use Alipay with fingerprint authentication, follow [MENTION=9998549]Galiis[/MENTION]' directions in posting #6.

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

Changelog (Last repo sync: 8 Mai 2020, 10:48:22 CEST / 8 Mai 2020, 08:48:22 UTC):

oneplus3t.xml: switch to lin-16.0-mse2 (MSe1969@xda) — Nvertigo

Patch up: P_asb_2020-05. — Nvertigo

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] devilrunner:
Love your ROM !

I was browsing you Gdrive and found messages.zip file.

What does this zip do ?
[OnePlus 3 & 3T Cross Device Development] :
https://xdaforums.com/showpost.php?p=79061310&postcount=1030
[OnePlus 3 & 3T Cross Device Development] phoberus:
I think the site from shadow53 isn't updated some time ago, but with Google you find also other step-by-step tutorials. I would also go with Nanodroid. You can also install it over f-droid (with the microG repo)

Found an important statement on Reddit:

Maybe nvertigo67 or a user has tested the various options on this rom
[OnePlus 3 & 3T Cross Device Development] devilrunner:
Thx nvertigo67 !

I just keep flashing it out of habbit never thinking about why I needed it...:)

Do you think this fix is still needed?
[OnePlus 3 & 3T Cross Device Development] :
Did you check the link I've given??? This workaround has been necessary for los - it has never been made for nlos: nlos was always patched until it has been fixed upstream... I've never asked any user to flash this with nlos!

https://github.com/nvertigo/local_manifest/commit/158b5ccf4eccbc5f0338e0b673fbe39f5c270a07

https://github.com/nvertigo/local_manifest/commit/24abb8ffde0a637a9f8158cdd4ba90109674d664

(The patched messages app version: https://github.com/nvertigo/android_packages_apps_Messaging/commits/nlos-16.0 )

BTW: first you've said you found the zip while browsing my gdrive - now you claim you've flashed that "out of a habbit" since over a year. These narratives doesn't match. Do you tell stories to keep me busy?
[OnePlus 3 & 3T Cross Device Development] karakanto:
Thanks for keeping building nlos-16 (instead of 17.1). I tried los-17.1 recently and really did not like how notifications are handled there (it's a lottery as to which actually show when you want them to, silenced or not). It's also not possible to disable SIM2 there either. And since clipboard access had been revoked from apps it meant my KDE Connect couldn't work how I wanted either.

I'll be staying on 16 for the foreseeable future.
[OnePlus 3 & 3T Cross Device Development] undrwater:
Can you describe what you mean in terms of clipboard access? I use kdeconnect as well, so was curious.

Staying (somewhat) on topic; thanks again from me, nvertigo. Looking at all the Q threads, I'll be staying here as well.
[OnePlus 3 & 3T Cross Device Development] karakanto:
Android 10 restricts what apps can do with the clipboard. See: https://github.com/andyholmes/gnome-shell-extension-gsconnect/issues/702

I use it where I can copy text on my phone and it appears on the clipboard of my PC, and vice versa.
[OnePlus 3 & 3T Cross Device Development] bertino:
I think that it won't work even if the rom disables the restriction, kde connect is still blacklisting android 10