yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] :
That's the posix behaviour of the -b argument. /system/bin/ls is a symlink to toybox. [polemics]Obviously replacing (posix compliant) busybox with her ugly, stupid, (non-posix compliant) little sister toybox wasn't enough, g managed to hardcode an argument as default, which has no opposite argument... Geniuses...[/polemics]

1|OnePlus3T:/ $ which ls
/system/bin/ls
OnePlus3T:/ $ ls -l $(which ls)
lrwxr-xr-x 1 root shell 6 2009-01-01 00:00 /system/bin/ls -> toybox
OnePlus3T:/ $ ls /sdcard/Download/pp*
/sdcard/Download/pp\ (1).txt /sdcard/Download/pp.txt
OnePlus3T:/ $ toybox ls /sdcard/Download/pp*
/sdcard/Download/pp\ (1).txt /sdcard/Download/pp.txt
OnePlus3T:/ $ busybox ls /sdcard/Download/pp*
/sdcard/Download/pp (1).txt /sdcard/Download/pp.txt
OnePlus3T:/ $

Possible solutions:

unescape the ls output (like sed -e 's/\\//g')

use busybox (installed additionally to toybox - root requiered)

use a rom, which shipps with busybox added
[OnePlus 3 & 3T Cross Device Development] undrwater:
Would termux help? You get a more posix friendly terminal, though it appears to be somewhat sandboxed.

[MENTION=4405529]nvertigo67[/MENTION], display mode works, though I prefer a temperature approaching "orange", and I perceive the lowest setting to be a bit "yellow". Minor quibble, I'm satisfied. Thank you.
[OnePlus 3 & 3T Cross Device Development] mumapizza:
can we please stick to stable kernel upstreams, using release canidates is not worth the risk of having little issues.

I also find the night mode color off, should be orange and not yellow. see iOS
[OnePlus 3 & 3T Cross Device Development] knpk13:
What? You can manually select the color temperature you want in livedisplay though based on your preference. I don't see the issue. Perhaps you could play with the RGB values and the picture adjustment settings (hue, saturation, intensity, etc) if the color is still off?

[MENTION=2799078]undrwater[/MENTION] the lowest temp (1000K) is well past orange and quite reddish for me, far from yellow.
[OnePlus 3 & 3T Cross Device Development] :
If you refer to the "quoted ls output"-issue, it won't help. Look at my command listing, it's clearly hardcoded in toybox. Also: local interactive shells has been broken since 14.1 - no matter, which terminal app is used. I'm using adb for shell access since two years or so. It's quite comfortable with adb over network.

That's basically the strategy. I've used the latest rc build three times, when I was waiting for a kernel release. In two occasions it was the VERY SAME code to the byte (but the version string) as the finally released kernel, one time there were later addition to arch/x86* and arch/mips/*.

I try to keep the risk minimal and I'm very carefull about merging rcs.

Did you find any actual issues on the builds with rc kernels?

First of all: I don't have hands on any apple products. Any references to iOS are completly pointless to me.

Second: please be precise in phrases.

On "Color temperature": it shifts the color balance towards red.

On "Color profiles: the "Astronomy" Color Profile is yellowish. I don't know if that is correct, because the op3t calibration file comes with modes named eye0 to eye7, the mappings to human readable strings (like "Astronomy") are community choosen. I've asked for feedback in 14.1 times, and using the result of your all feedbacks till now. If you feel something is wrong with the mappings (for op3t - op3 calibration file has human readable strings allready), feel free to discuss better mappings.

On kcal: kcal is not supported in the rom. Even if I'd merge the kcal patches in the kernel, it would need an additional app (and user attention to disable all(!) livedisplay features) to acually use kcal. Since one thing I like about los is livedisplay, I don't want to use kcal additionally.

If somebody likes kcal over livedisplay, I'd suggest to try a rom supporting kcal natively. One thing I like about op3/t: there are so many custom roms, that everybody's taste should be matched.
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (kernel: 3.18.139; webview: 74.0.3729.112)

Build 20190429

Releasenotes:

NLOS-16.0 relies 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: 29 Apr 2019, 11:01:46 CEST / 29 Apr 2019, 09:01:46 UTC):

current.pick.sh: "Update Chromium Webview to 74.0.3729.112". — Nvertigo

Merge tag 'v3.18.139' of git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable into linux-stable/merge-16.0 — Nvertigo (very same source code as rc2)

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] pijas82:
First time in this rom ? amazing

Thanks

---------- Post added at 08:08 PM ---------- Previous post was at 07:33 PM ----------

I cant install my purchased apps
[OnePlus 3 & 3T Cross Device Development] serj.borgore:
Microg ready means that is already installed with everything we ne? If not, what's the best way to install it? Maybe nanodroid?
[OnePlus 3 & 3T Cross Device Development] undrwater:
Can you recommend any documents or links to look into this?
[OnePlus 3 & 3T Cross Device Development] :
https://xdaforums.com/oneplus-3/one...-nlos-16-0-t3879405/post79116196#post79116196

Additionally needed information:

Do you pass safetynet? Is playstore certified? Detailed description of your setup (like: Mods, Magisk, any specials).

From OP:

Calibration files:

op3: https://github.com/nvertigo/android..._samsung_s6e3fa3_1080p_cmd_mode_dsi_panel.xml

op3t: https://github.com/nvertigo/android..._samsung_s6e3fa5_1080p_cmd_mode_dsi_panel.xml

mapping commit: https://github.com/nvertigo/android...mmit/c6ac51dfc3c68fdf591bce98634840db8adfe33c
[OnePlus 3 & 3T Cross Device Development] pijas82:
Safetynet -done

PlayStore certified-done

I flash Oreo firmware 5.0.8 ,rom,opengapps pico and last stable magisk .

I had same issue on DU ,but reboot solves my problem.

I contact APP developer . Change rom, same gapps, apps,magisk , no problems
[OnePlus 3 & 3T Cross Device Development] :
Honestly, I don't understand your "issue report". Do I get this posting, if I think it's solved fpr you?
[OnePlus 3 & 3T Cross Device Development] pijas82:
Sorry bro, fix with last open Pico gapps, so problem is not ROM but gapps

Thanks
[OnePlus 3 & 3T Cross Device Development] sandeep_kumar:
Is it possible to lock bootloader on custom ROM?
[OnePlus 3 & 3T Cross Device Development] :
I use this patch (https://github.com/nvertigo/android...mmit/c6ac099e9e960d294d6b994d830138753221f7b9 ), which is needed to run the rom with a relocked bootloader. I havn't tried myself - obviously a locked bootloader is less then useless for a dev testing... ;)

Test relocking and tell us.

[MENTION=9350973]All[/MENTION]:

If you use other then OP recommended setup and sofware versions, please mention that first on an issue report.
[OnePlus 3 & 3T Cross Device Development] meiser:
I don't get the question. What does the used ROM have to do with locking the bootloader? This is done with "fastboot oem lock". If you want to unlock the bootloader again, the commit mentioned by nvertigo67 is needed so that the option is available under the developer options.
[OnePlus 3 & 3T Cross Device Development] deepakpc007:
Awesome smooth ROM. Well done Dev?

One issue that I have is that the phone automatically turns into Vibrate mode somehow. I have this issue in Havoc ROM as well. They had fixed it. If possible can u please fix this in the coming builds? Thanks.
[OnePlus 3 & 3T Cross Device Development] :
In deed...

If the bootloader is locked, it will only boot roms and recoveries with "bootable images with arbitrary signatures to boot".

https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/245235

Conclusion: rom and recovery needs to be signed in order to work with an locked bootloader. That's what the used rom has to do with relocking the bootloader.

No. I can't. Lack of information. How to reproduce - I've never expirienced this? Which patch(es) solved that?

https://xdaforums.com/showpost.php?p=79116196&postcount=555
[OnePlus 3 & 3T Cross Device Development] Dirk:
[MENTION=4405529]nvertigo67[/MENTION]

Have you had any experience on Pie of what appear to be systemui 'delay' when waking the device? I have upward of five seconds delay from the screen waking to the Status Bar clock updating, or any app responding to it's shortcut. Not all the time, but mostly when the screen has been off a while.

As an experiment i just excluded 'System UI' from Battery Optimisation. Too early to say if it's helped yet. It really behaves as if it's a Doze issue though. Shouldn't systemui be excluded by default anyway?

Edit: Didn't help.

Would love to hear your thoughts. Thanks.
[OnePlus 3 & 3T Cross Device Development] deepakpc007:
I don't know how to reproduce it. It randomly it does switch to vibrate mode. Almost all the time when I enter an elevator it behaves like this. I don't have any other proof. How to take the log for this? I haven't done it before that's why I'm asking. Sorry.
[OnePlus 3 & 3T Cross Device Development] :
I'm afraid it's one of those...

My setup:

screen lock: fp & pin

Ambient display: on; Always on: off; Pick-up, Hand wave and Pocket: on

Cover with flip magnets

If I use the flip cover: Lockscreen comes up immediatly (<0.5s)

If the device lays on the table with flip cover folded back: picking it or waving: Ambient display lights on immediatly (<0.5s)

unlocking with fp from Ambient display: immediatly (<0.5s)

unlocking with fp from "real" display off (not from active Ambient display): immediatly (<0.5s)

Either I got your description wrong, or it's config dependend (...one of those...).

Please read the op including the links I've given (I gave them for a reason). It's all there.

What about the Havoc Patch? Or at least a link to the discussuion of the fix?

Dude, you expect me to work myself through the havoc's thread and the complete sources, but don't even read the first tenth of the op...

Do you think that's a smart way to motivate me to fix something I do not expirience myself? If you've just read, that I'm more then tired of begging for the same information all the time, do you think that asking me how to get a log (basic andriod knowledge, a minute of googling away) is a smart move?
[OnePlus 3 & 3T Cross Device Development] deepakpc007:
Calm down man. I don't know how to take the log. That is why I asked. If u can't help, then it's fine. Just forget that I even shared this feedback. Thanks.
[OnePlus 3 & 3T Cross Device Development] Dirk:
No, nothing like that. Screen turns on immediately, no delay in unlocking. Once screen is on there's a delay before the status bar clock updates, or any app can launch from shortcut. Never seems to happen when screen is off a short time which i why i believed it to be doze related. Seems like the system is sluggish getting going.

Perhaps there's something else i can try excluding from doze. Android System perhaps?
[OnePlus 3 & 3T Cross Device Development] :
But there's a manual for issues and logcat in the OP... Search before posting is the first xda rule...

You're attitude is respectless, like your last response is.

I'm not expirience this lag. I can use the lockscreen shortcuts as soon as the screen comes to life. The statusbar is shown immediatly and I can pull down the notifications at the moment the screen comes to life.

Can you reproduce this with a clean flash with only gapps or microg installed? I guess it's config/mod/setup related. I remember there was a magisk version delaying the unlocking; though this is different, I'd start with a clean flash and a minimal and basic configuration to get a log of this.

Do you have an icon of any third party app in the statusbar? Perhaps (guessing again) some app needs to connect to some server, before the icon can be updated and the clock is rendered after the third party action has finished?
[OnePlus 3 & 3T Cross Device Development] Dirk:
No, but i am wondering if something might be getting priority in waking leaving everything else waiting in a queue. Gonna try turning off Adguard for a while, see if that helps.

Bear in mind this isn't your ROM. (It is LOS Based though). Just picking your brain here. Also my setup is as bare, clean and minimal as any in existence. I do not run mods. (Thought that was well known) I only have a handful of apps installed and they are the same ones i've used for years. I don't use anything more resource intensive than Chrome. Gapps Pico....

I guess the thing i find strange is that nobody else is talking about it, making me think it's my setup. Which would be weird as my setup is as vanilla and stable as possible. It was only today when a Havoc OS user reported the same problem. First time i've seen anyone else with the issue. Different ROM. Now i need to find what our setup has in common i guess. :)
[OnePlus 3 & 3T Cross Device Development] cukierkas:
I'm guessing it's doze or scheduler related. Having same ghost clock freezes on 5t derpfest rom aoisp related. But I'm not complaining, it vanished in less than a second. Had checked the cpu steps while unlocking - there's a small gap between boosting kicks in. My wild guess is that all this done for battery sake.

Ot question - does it worth waiting fuchsia os? Will it land on our devices someday?

https://fuchsia.googlesource.com/
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (May security patch; busybox fixes & static build; maintainance)

Build 20190507

Releasenotes:

NLOS-16.0 relies 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: 7 Mai 2019, 15:22:50 CEST / 7 Mai 2019, 13:22:50 UTC):

apns-conf.xml: fix "T-Mobile US LTE" tethering. — Nvertigo

current.pick.sh: fix picking p-display-shrink. — Nvertigo

Patch up to android-9.0.0_r37. — Nvertigo (nvertigo/nlos-16.0

current.pick.sh: "SystemUI: Add Profiles tile". — Nvertigo

current.pick.sh: "SystemUI: Advanced location tile". — Nvertigo

current.pick.sh: "SystemUI: Enable and fix QS detail view, adapt layout to Pie". — Nvertigo

Android.mk: fix static_busybox. — Nvertigo

util-linux: fix implicit function declaration. — 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] hattorihansou:
Can someone please explain to me, why it tells me january even though the latest build was updated to android-9.0.0_r37 and it should display may?
[OnePlus 3 & 3T Cross Device Development] :
I've no clue at all. What does "getprop ro.build.version.security_patch" return? Whats the value of ro.build.version.security_patch in build.prop?
[OnePlus 3 & 3T Cross Device Development] hattorihansou:
2019-05-05

Maybe it displays the wrong date because of dirty flashing.

I don't mind as long as its up to date.
[OnePlus 3 & 3T Cross Device Development] :
No. I've dirty flashed, too.

If getprop and build.prop are reporting 2019-05-05, set the logbuffer to 1 Mio, reboot, go tho the versions window (likemthe screenshots) and get a complete log, please.
[OnePlus 3 & 3T Cross Device Development] hattorihansou:
hmmm...

I'll try to attach a log when i'm back home from work.

Never done this before.

edit: log attached
[OnePlus 3 & 3T Cross Device Development] S4turno:
Not sure if it's your case, but if you are using any magisk module to allow ARCore/Playground to work on your phone, that might be the reason.
[OnePlus 3 & 3T Cross Device Development] hattorihansou:
Great, thanks!

Disabling solved it.
[OnePlus 3 & 3T Cross Device Development] S4turno:
No problem. It's mentioned under "warnings":

Keeping the module ON doesn't affect the security patches, but it changes what it says on the about menu. This happens because the module changes the phone's fingerprint to Pixel 2 and the security patches have to match the fingerprint in order not to break the safetynet on all phones.

Everything is right your builds [MENTION=4405529]nvertigo67[/MENTION].
[OnePlus 3 & 3T Cross Device Development] Mata99:
[MENTION=4405529]nvertigo67[/MENTION] I flashed last firmware and last update, but after reboot I can't unlock the phone; on unlock screen the phone said that the pin is not correct (of course I digited the correct one)
[OnePlus 3 & 3T Cross Device Development] :
Which fw package?
[OnePlus 3 & 3T Cross Device Development] abhibnl:
Sorry for OT post [MENTION=4405529]nvertigo67[/MENTION] but can I use your custom firmware (the bootloader and and keymaster partition to OxygenOS 5.0.8) to flash OOS Pie CB 2 without having to reformat userdata partition? What I am not sure about is if the CB2 installation zip corrupts userdata on first boot or immediately after it is flashed. The steps I have in mind are: Flash CB 2 Zip > Flash your customer firmware > flash twrp > reboot to recovery > flash magisk.
[OnePlus 3 & 3T Cross Device Development] Mata99:
The first one
[OnePlus 3 & 3T Cross Device Development] abhibnl:
You should go through his complete post related to this update and you will understand why you are facing the issue.
[OnePlus 3 & 3T Cross Device Development] :
I guess that should work - I would make a nandroid first. Since the oos zips contain the fw, it's important to flash the modded fw after the rom, as you've described above.

If you use the plain 9.0.1 fw on an unlocked bootloader setup, you need to format userdata and reencrypt. If you don't want to loose your current userdata partition you need the modded fw.
[OnePlus 3 & 3T Cross Device Development] cukierkas:
Hello all. My 5t's screen went with brown spots, two if them. I'm not sure, if I pushed the screen in jeens backpocket while driving or screen decided itself to die slowly. But those dots are especially seen in white areas and they are getting bigger after a usage. After some deep sleep, it recovers for some minutes, but afterwards, 2mins or less, starting to appear again :)

Should I come back to nlos? I'm still reading this thread and admiring the devs, who finds everytime something to be fixed. Kudos!
[OnePlus 3 & 3T Cross Device Development] 9Lukas5:
Thank you for the update and especially the extra effort providing a flashable firmware update for upgrading keeping the data in place [emoji108]

It worked like a charm, flashed your firmware file with 5.0.8 bootloader and key part, flashed update, and everything's working luke like it should.

Just a report of 'all well', as these are very rare compared to the 'there's a bug' ones [emoji1]

L

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] LonelyDay:
Hello everyone, what this rom prebuilt with OpenWeatherMap?
[OnePlus 3 & 3T Cross Device Development] 64ashg:
Hello.

And yes it does.
[OnePlus 3 & 3T Cross Device Development] LonelyDay:
Thanks before, but where the app? App or priv-app dir?
[OnePlus 3 & 3T Cross Device Development] :
find system/ -name \*Weather\*
system/app/OpenWeatherMapProvider
system/app/OpenWeatherMapProvider/OpenWeatherMapProvider.apk
system/priv-app/WeatherProvider
system/priv-app/WeatherProvider/WeatherProvider.apk

The WeatherProvider is previleged - the OpenWeatherMapProvider is just the "data fetcher" and doesn't need to be installed previledged.

I'm confused.

As far as I understand the above, my answer is: nlos for op3/t will not fix a physical damage on op5t... ;)
[OnePlus 3 & 3T Cross Device Development] LonelyDay:
Thanks, Sir.
[OnePlus 3 & 3T Cross Device Development] cukierkas:
I do in mind taking out from drawer old trusty and rusty 3t and using it :D

Of course nlos won't cure hw damage on other handset :D
[OnePlus 3 & 3T Cross Device Development] devilsworkshop:
I tried the latest build on my oneplus3, and my SIM cards are not detected. Additionally, my phone randomly reboots into recovery with a "powering off" message.

Often, the phone reboots shortly after booting (around a minute or so) but sometimes, it reboots much later (5 minutes or so after booting) and a couple of times it didn't reboot at all.

I've tried it with various combinations of firmware, opengapps, magisk, and userdata formatting. I've been able to ascertain that the reboots occur with or without opengapps and magisk, with the modded and unmodded firmware, and both with clean flashes (after formatting userdata) and dirty flashes (without formatting userdata).

In all scenarios, my SIM cards are not detected.

I tried to capture a logcat for the reboots, but it would either reboot before I could do it, or it wouldn't reboot at all.

However, I did manage to capture only one logcat for the following setup: userdata format + unmodded fw + latest nlos + opengapps pico 0516 + magisk 19.1. The logcat can be downloaded here.

I was able to reproduce the reboots thrice (3 out of 4 tries) by removing and re-inserting the SIM card tray. Around 20-60 seconds after re-inserting the tray, the phone reboots to recovery.

On one of the attempts, the SIM cards were briefly detected. When I tried to place a call, the SIM cards disappeared and the phone rebooted.

On the fourth attempt, I tried to capture a logcat, but this time it refused to reboot.

I use two SIM cards, but I have been able to reproduce the issue with just one SIM card as well.

Occasionally, I get the error "Phone services has stopped".

Please advise if there is any further testing I can do and if I am doing something wrong.

Thank you.
[OnePlus 3 & 3T Cross Device Development] cukierkas:
Fastboot installation always helps :D
[OnePlus 3 & 3T Cross Device Development] 64ashg:
I have the same problem.

I haven't verified it with a clean flash, but my setup has been able to reproduce the problem the same way. Will come back from work to verify the same.

I had this problem back in march second week build too, but WiFi also refused to work in that case. And i was the only one having it back then. I had to solve it by going for a clean flash and i assumed the same today until your post. Thanks.

Right now i am using the 7th may build with the firmware posted for the 16th may build, for now. It seems to work as intended. I will try a clean flash to verify nonetheless.
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=6789884]devilsworkshop[/MENTION], [MENTION=5868698]64ashg[/MENTION]:

From the logs it looks like the communication of ril and modem (aka radio) is broken. ATM I've no clue why.

The both of you are on op3 (without t), arn't you?

Which recovery was used?
[OnePlus 3 & 3T Cross Device Development] devilsworkshop:
Yes, I'm on the 3 (without t).

I tried it with both the official TWRP 3.2..3-0 and the recommended recovery in the OP (dianlujitao's 3.2.3-10).

After flashing the CB2 firmware, the Nlos 0507 build works fine, and so do RR, Nitrogen and Havoc. So the issue doesn't seem to be in your firmware package, but rather the actual ROM build itself.
[OnePlus 3 & 3T Cross Device Development] phoberus:
On my 3T it works very good with the OxygenOS 9.0.1 firmware + 5.0.8 bootloader and keymaster. Smooth and no problems at all
[OnePlus 3 & 3T Cross Device Development] knpk13:
I flashed your unmodded firmware package for OOS 9 CB2 and reformatted data and clean flashed the new build. Is there any way to tell what firmware version is being used? When I flash builds in TWRP, there's a line that says target, and it still ends with 8.0.0, so I wasn't sure if the firmware flash worked. Everything seems to be working fine though.
[OnePlus 3 & 3T Cross Device Development] 64ashg:
I am on the 3t.

And i used twrp 3.3.0-1, the latest one. I upgraded from 3.2.3-10 just because it involved pie firmware. I will downgrade my recovery to see if anything else happens.

Ps. I have the same problem with a clean flash. Will downgrade recovery to see if something changes.