yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] :
I've used 3.3.0-1 (forgot to go back to 3.2.3-10 after testing). No need to test.

Last night I found something concerning (when thinking it's only op3):

ingo@adler /usr/local/src/oxygenos $ git diff 9.0.1 op3-9.0.1 -- $(find * -name \*ril\*)
diff --git a/system/vendor/lib/libqcrilFramework.so b/system/vendor/lib/libqcrilFramework.so
index e097413a..2c59fad6 100644
Binary files a/system/vendor/lib/libqcrilFramework.so and b/system/vendor/lib/libqcrilFramework.so differ
diff --git a/system/vendor/lib/libril-qc-hal-qmi.so b/system/vendor/lib/libril-qc-hal-qmi.so
index 64c0d293..52c6ad70 100644
Binary files a/system/vendor/lib/libril-qc-hal-qmi.so and b/system/vendor/lib/libril-qc-hal-qmi.so differ
diff --git a/system/vendor/lib64/libqcrilFramework.so b/system/vendor/lib64/libqcrilFramework.so
index 7e5284a3..3f321b83 100644
Binary files a/system/vendor/lib64/libqcrilFramework.so and b/system/vendor/lib64/libqcrilFramework.so differ
diff --git a/system/vendor/lib64/libril-qc-hal-qmi.so b/system/vendor/lib64/libril-qc-hal-qmi.so
index 4f73ee23..94121076 100644
Binary files a/system/vendor/lib64/libril-qc-hal-qmi.so and b/system/vendor/lib64/libril-qc-hal-qmi.so differ
ingo@adler /usr/local/src/oxygenos $

On 5.0.8 these files were the same for op3t and op3. On 9.0.1 they differ...

Currently I don't know what can cause these problems. I can only exclude some points:

twrp: [MENTION=5868698]64ashg[/MENTION] (broken setup) and me (working setup) used 3.3.0-1.

model (due to different blobs - see above): it's broken for [MENTION=5868698]64ashg[/MENTION] (op3t) as well as for [MENTION=6789884]devilsworkshop[/MENTION] (op3).

fw package: [MENTION=5868698]64ashg[/MENTION] (broken setup) has fw working with older build.

For completeness: does anybody run 20190516 on op3? I don't think it's fs related, but who knows? I'm on f2fs encrypted.

Any ideas, what can cause this are highly welcome - atm I've run out of ideas... :(
[OnePlus 3 & 3T Cross Device Development] :
In a rooted adb shell:

dd if=/dev/block/bootdevice/by-name/modem bs=1024 count=62 2>/dev/null|strings|grep Time_Stamp

Compare the date string to version release date to match the oos version (release date is about two days later then the build time stamp you are getting with the above command.

Or just remember, what you've flashed... ;)

It's the build finger print. It's the last one working with safetynet api and playstore certification.
[OnePlus 3 & 3T Cross Device Development] 64ashg:
These are logs from my restored setup and dirty flash, this is of any use..

I will be posting the clean setup logs once i have formatted again, yesterday i repeatedly tried to realize now that i forgot to give '>' in the logcat command to point it to the address to store it in a filename and restored my phone after giving up.
[OnePlus 3 & 3T Cross Device Development] devilsworkshop:
I tried the official LineageOS 20190517 nightly, and it works fine (with CB2 fw). So I suppose it must be something specific to the patches NLOS uses.

I also did try it with Franco Kernel (r45), and the same problem persists, so I guess it isn't the kernel, either. (Franco Kernel r45 works fine with CB2 fw and other ROMs)

In the setup wizard, on the very first step, the "Emergency call" button doesn't work. Sometimes it does nothing, sometimes it causes com.android.phone to crash. Considering this and the lack of SIM card detection, I seriously doubt it has anything to do with the FS.

Incidentally, why do you use f2fs? You have specifically recommended against it yourself, haven't you?
[OnePlus 3 & 3T Cross Device Development] :
No ril errors, nor teelphony crashes. Honestly, I can't see any issues in the log you posted...

[MENTION=6789884]devilsworkshop[/MENTION]: the issue from [MENTION=5868698]64ashg[/MENTION] is different from yours. Wich brings me back to my thought from the last night: ****, the blobs of cb2 differ from op3 to op3t.

I'll make a build with the very same codebase, but with blobs generated from the op3 zip instead of the op3t zip (two or three hours).
[OnePlus 3 & 3T Cross Device Development] undrwater:
Did I miss what's causing the new procedure? Something specific in the firmware?
[OnePlus 3 & 3T Cross Device Development] pedritopl:
Just reporting. OP3T, dirty flash from 20190507 build. Used the modified firmware (with 5.0.8 parts) - at first boot the phone asked for SIM PINs and then was stuck at "Phone is starting" screen for a few minutes, but after forcing a restart all seems to be working fine (calls, SMS, WiFi, Bluetooth checked) :)

TWRP-3.2.3-10, OP3T 128Gb, NLOS-20190516.
[OnePlus 3 & 3T Cross Device Development] :
What new procedure are you talking about?
[OnePlus 3 & 3T Cross Device Development] undrwater:
I may be confused but the update appears to REQUIRE a new firmware. Then, the new firmware cannot just be flashed if one wishes to maintain their data, so your modified firmware is required.

That's new compared to just flashing update. But again, I may be confused.
[OnePlus 3 & 3T Cross Device Development] :
No new procedure. I've always updated the firmware requirements if the blobs were updated. It's the same procedure then always, if blobs are updated. That the community beta bootloader will require a format of userdata, if the device is not running with an locked bootloader, is done by intend by OnePlus. Modding a firmware package to use cb2's fw without the need of formatting userdata is just for your convenience.
[OnePlus 3 & 3T Cross Device Development] undrwater:
Thank you, that clears it up for me.
[OnePlus 3 & 3T Cross Device Development] :
rom: https://drive.google.com/open?id=1VxgvlDXQ8P07mYnuJ5YpfyIYO21Du3UZ

md5: https://drive.google.com/open?id=1qsQ7w38SWoYDLxT4g3t0v8lrvKz9gflUu
[OnePlus 3 & 3T Cross Device Development] 9Lukas5:
As you asked: I'm using a op3, running the 16th May build, dirty flashed over the last one.

I'm using the firmware with 5.0.8 parts, and phone is working stable here, no Simcard problems or reboots.

My data is encrypted on f2fs.

L

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] 64ashg:
I have more logs

New is clean flash with modified firmware and newer is using Oreo firmware. Using Oreo firmware it doesn't reboot every two minutes, but I lost my sim connection in two minutes. Sim is being detected, so progress? I haven't flashed your op3 file though.

edit, after a full wipe with the new unmodded firmware, the same problem persisted on the 18th may build with the shutdown in about two minutes. it detected the sim, but then it disables it and then the shutdown

very reminiscent of the newest log in the zip.

I'm back to using 7th may build
[OnePlus 3 & 3T Cross Device Development] :
Did you read the releasenotes: you need 9.0.1 firmware. With 5.0.8 firmware you get what you've describe above... That's why I wrote the release notes and made an assert that avoids flashing 0516 and 0518 over 5.0.8 fw.

Please read my last postings: the 0518 build is for [MENTION=6789884]devilsworkshop[/MENTION] because he is on op3 and some of the ril related blob files differ on cb2 from op3 to op3t.
[OnePlus 3 & 3T Cross Device Development] phoberus:
Every 5 minutes my internet doesn't work anymore. If I go into the flight mode and out again, it works again. Logs are in the attachment.

Oneplus 3T

OxygenOS 9.0.1 firmware with 5.0.8 bootloader and keymaster

Build 20190516
[OnePlus 3 & 3T Cross Device Development] devilsworkshop:
I just tried this on my OP3, and I'm afraid I have exactly the same problem as before. I got a log, you can download it here.

I dirty flashed it over the previous build.
[OnePlus 3 & 3T Cross Device Development] :
After [MENTION=3320665]9Lukas5[/MENTION] of working setup on op3, I've expected that.

Anyway, I'm going back to old blobs.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Everything works well for me too. OP3T, 9.0.1 firmware, 16 may build, ext4 unencrypted (I don't need another warning, I know the risks of running unencrypted)

Does this mean we have to reformat data and flash the old firmware again for the next build?

Edit: actually there is one issue. This dci-p3 issue is persistent after all these builds Dci-p3 doesn't stick through reboots.

Running: cat /sys/devices/virtual/graphics/fb0/srgb /sys/devices/virtual/graphics/fb0/dci_p3

returns 1

But dci-p3 clearly isn't enabled, since switching the display setting back to standard and then to dci-p3 produces a noticeable difference. Not a big issue, I just enable it manually, but thought I'd mention it since I heard it was fixed upstream a while ago.

Also if I'm not experiencing/noticing any issues in particular, but the log has multiple errors in it, does that mean it needs to be investigated?
[OnePlus 3 & 3T Cross Device Development] phoberus:
Sorry, I cleared the entries before I re-tested it. I made new ones again, this time they are complete. The problem occurs in the mobile internet, I could not test WLAN yet. I noticed that I only have no Internet with LTE. LTE+ works, but then changes to LTE after a few minutes. If I only use H+ and 3G, the mobile Internet will work forever.

It probably shows these errors because I needed the MCD kernel with blu_schedutil. For the new logs I used your stock kernel.
[OnePlus 3 & 3T Cross Device Development] :
If you have used the 5.0.8 bootloader and keymaster, you don't need to do anything else then reflashing the 5.0.8 fw and reboot to recovery. If you have used the 9.0.1 bootloader and keymaster reformatting is strongly recommended.

I'm considering that fixed: https://github.com/nvertigo/android_device_oneplus_oneplus3t/commit/5ae0d628

Not by me... see below.

I'm speechless. That can't work, because for the new blobs you need a kernel patch.

Don't you think that would have been a usefull information? I've spended a night on your log...

Conclusion: From now on I'll only accept issues, I can reproduce myself.
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (kernel: 3.18.140; webview: 74.0.3729.157; 3 finger swipe for screenshot)

Build 20190520

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 (relative to 20190507; Last repo sync: 20 Mai 2019, 09:59:32 CEST / 20 Mai 2019, 07:59:32 UTC):

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

Revert "oneplus3t.xml: temporary: use branch pie-blobs for vendor, device and kernel." — Nvertigo

Revert "Patch up to android-9.0.0_r37." — Nvertigo

oneplus3t.xml: temporary: use branch pie-blobs for vendor, device and kernel. — Nvertigo

current.pick.sh: swipe_screenshot. — Nvertigo

op3: Wait for MPCTL to start on boot — dianlujitao

Merge tag 'v3.18.140' of git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable i

nto linux-stable/merge-16.0 — 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] Mata99:
I have installed last firmware Cm_beta 2 for 3T; have I to flash 5.0.8 firmware before install last version?
[OnePlus 3 & 3T Cross Device Development] knpk13:
I used 9.0.1

Hm, I'm just gonna stay on the 16 May build until you switch to pie blobs I guess if it's not safe to update. Reformatting again is a pain. Thanks!
[OnePlus 3 & 3T Cross Device Development] sandeep_kumar:
[MENTION=4405529]nvertigo67[/MENTION],

Post#711

You mentioned "3 finger swipe for screenshot"

I want to know is it the same 3 finger swipe as good as oxygen OS.

In oxygen OS unlike other ROMs that I have flashed afaik, swiping 3 fingers on youtube or web page does not move the screen to the down side. It does make still the screen page as soon as you press the 3 fingers. Therefore actual visible screen shot is captured.
[OnePlus 3 & 3T Cross Device Development] :
Wuy do you address this question directly to me? Everybody, actually using this rom, can answer this.

3 finger swipe doesn't move the page.
[OnePlus 3 & 3T Cross Device Development] sandeep_kumar:
I just thought you may reply in a better way. Thanks for the reply.
[OnePlus 3 & 3T Cross Device Development] serj.borgore:
Hey [MENTION=4405529]nvertigo67[/MENTION], can you add dts hpx and ultra commits to your kernel? I've always used DTS with other roms and kernels, so now the only way to use it is to change the kernel with another one but.. I don't want to change it because is awesome Ahah

Thank you for the Rom
[OnePlus 3 & 3T Cross Device Development] :
Would you link the kernel commits in question, please?
[OnePlus 3 & 3T Cross Device Development] cukierkas:
Hello all. [MENTION=4405529]nvertigo67[/MENTION], are you still insisting to use ext4 or we can go easily with f2fs? Only /data and /cache? Decided to give a chance ride for week time for my beloved 3t 128gb version. Hope it will leave 5t in a dust :D

GCam on 3t is still not very good or now usable? Which version is recommended?

Regards.
[OnePlus 3 & 3T Cross Device Development] Remorcer:
https://gitlab.com/dts_project/intro
[OnePlus 3 & 3T Cross Device Development] cukierkas:
Here I'm, with 3t.

Officially updated to pie. Afterwards unlocked bootloader, twrp, installed 0520 rom with magisk 19.2. No firmware instalation, thought will be enough of native oos. Running on ext4, made easily 4 fingerprints, 6 digits passcode. No issues observed, phone is nearly as fast as 5t and stable as rock. Very happy to use it.

Simple question about one hand mode, how does it work and how to enable it? :) Found under display settings.

Regards.
[OnePlus 3 & 3T Cross Device Development] :
Only currently available trigger is "swipe over (on-screen) navbar".
[OnePlus 3 & 3T Cross Device Development] cukierkas:
Would you consider to update dialer app for having dark background theming and wonders , including fantastic call recording feature you have enabled?

Regards.
[OnePlus 3 & 3T Cross Device Development] :
I've tried to use the commits. Sadly, these patches need to be backported from 4.4 to 3.18, they go quite deep into the driver and changes the error handling. Currently I have not the time frame necessary for me to do that.
[OnePlus 3 & 3T Cross Device Development] :
Update to what? Commits?
[OnePlus 3 & 3T Cross Device Development] serj.borgore:
Sorry for the late reply. However, no problem If you cannot add it.. Thanks anyway!
[OnePlus 3 & 3T Cross Device Development] 64ashg:
just like before, i have the 5.0.8 blobs based 20th may build working with the modified stable firmware.

i remember getting problems when using the 16th build which had pie blobs.

does anyone have that build? links are removed. though i'd rather test the future nlos build based on stable pie blobs rather than community beta blobs.
[OnePlus 3 & 3T Cross Device Development] cukierkas:
https://drive.google.com/file/d/1udis9tso7UilSCHKrmciEs4H5yKJQ7GF/view?usp=drivesdk

Of course, if Ingo doesn't mind.

---------- Post added at 09:13 AM ---------- Previous post was at 08:58 AM ----------

Have no knowledge about commits, but I can give you a link to latest stable.

Theming, easier handling, better suggestions, nicer iu, nice bubble while minimised.

https://www.apkmirror.com/apk/google-inc/google-phone/google-phone-31-0-241960258-release/

19 version vs 31.
[OnePlus 3 & 3T Cross Device Development] devilsworkshop:
But why do you want the proprietary google dialer built into the ROM? Wouldn't it be better to install it yourself if you need to?
[OnePlus 3 & 3T Cross Device Development] cukierkas:
Default dialer has nicely programmed call recording feature, easy
[OnePlus 3 & 3T Cross Device Development] :
I don't mind. I've just decided not putting any more effort and time into debugging this, since the native blobs doesn't have any single benefit compared to what we use now.

The google dialer is not part of the rom - so it can't be updated within the rom.

As already explaimed, I don't want to include more theming then los in the rom (this is not only an endless task, since everybody has his own taste and preference, this is also prune to introduce more troible then benefit), for everything else use substratum. I.e. Swift dark makes the dialer dark (wow, what a sentence... *lol*)
[OnePlus 3 & 3T Cross Device Development] cukierkas:
Hehe, just noticed "less annoying rom" picture while starting :D Well done!

Happy to have this kind of influence :D

Regards.
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (mainly maintainance)

Build 20190526

Releasenotes:

NLOS-16.0 relies on OxygenOS firmware. OxygenOS 5.0.8 firmware 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: 26 Mai 2019, 12:10:54 CEST / 26 Mai 2019, 10:10:54 UTC):

current.pick.sh: "SystemUI: Fix several layout bugs". — 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] Eric_Lev:
For information, the link of 5.0.8 fw (OP3T) is broken ... You can use this one :

==> https://www.celsoazevedo.com/files/android/oneplus3t-modem-firmware/
[OnePlus 3 & 3T Cross Device Development] Mata99:
[MENTION=4405529]nvertigo67[/MENTION] do you'll create a build based on oos pie firmware?
[OnePlus 3 & 3T Cross Device Development] 9Lukas5:
As a report from op3:

The current build seems to be working with the pie firmware aswell. Was too lazy to flash back and tried it, it's working fine.

But be aware: this is not officially supported by [MENTION=4405529]nvertigo67[/MENTION] !

L

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] cukierkas:
All fine on 3t as well. Was flashing without any firmware
[OnePlus 3 & 3T Cross Device Development] :
Thanx for the heads up! Fixed.

Please search/read the thread: there's no benefit. Ril is broken for - at least - three users. That's why I pulled the native pie blob build. Since I can't reproduce the broken ril and it has no benefit for those the build is working for, I've decided NOT to pit any effort/time on a native pie blobs buid.

Since I can't exclude any strange side effects for this setup, I can't support it. If one needs support I would like to ask to stick to OP. If you look at our expiriences with nlos/los and fw versions, or at our expiriences with the native pie blobs build, you can't state "The current build is working with the pie firmware aswell"; you can just state "The current build seems to be working with the pie firmware aswell for some setups".
[OnePlus 3 & 3T Cross Device Development] 9Lukas5:
Yeah sure, I'll add a 'seems' to my post.

If you won't support such setups, you should change your update posting text:

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

+ NLOS-16.0 relies on OxygenOS firmware. OxygenOS 5.0.8 firmware is required:

L

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] cukierkas:
https://play.google.com/store/apps/details?id=com.rovio.angrybirds

Having problems with this classic game, it hangs after couple minutes of the game, just hangs :eek:

Even with quick battery profile. Performance wasn't able to try, phone's battery went out. :(

https://ibb.co/6WvyMY3

Edit, I have found the answer, if someone is interested. I have disebled Internet for app to avoid app ads, so birds just hangs in the moment when app is trying to access the amasonaws website... :D Please have that in mind

Regards.
[OnePlus 3 & 3T Cross Device Development] kbr0:
Is anyone else using this Rom with magisk having the issue that the magisk manager announces a new update but in the manager itself it says that magisk is not installed? A reboot fixes that behaviour for a couple of days most time.
[OnePlus 3 & 3T Cross Device Development] 64ashg:
no i don't have that issue. i would recommended uninstalling using the magisk uninstaller and then re installing magisk 19.2
[OnePlus 3 & 3T Cross Device Development] :
I'm still using 17.1 (18.x flooding the log with spam because it disables noaudit rules; I've never tested 19.x).

That being said, I've expirienced the "not installed" situation after updates. I havn't found a way to reliably reproduce it, it happens about one out of ten times. I've never ever experienced, what you describe: root is working properly after reboot and vanishes (not installed) after some time.

Anyway: since all of the above (log spammimg, "not installed" after update, "not installed" suddenly while running) are Magisk issues, I can't help you on this.
[OnePlus 3 & 3T Cross Device Development] himsin:
[MENTION=4405529]nvertigo67[/MENTION] can you please package your kernel also. Or can I flash your boot.img without any side effects?
[OnePlus 3 & 3T Cross Device Development] :
I've not the time to pack, maintain and support a nlos kernel package.

For los it should work, if you manually add https://github.com/nvertigo/android...s3t/blob/nlos-16.0/rootdir/etc/fstab.qcom#L11 to /system/vendor/etc/fstab.qcom. For other roms then los most properly it won't work.
[OnePlus 3 & 3T Cross Device Development] cukierkas:
[MENTION=4405529]nvertigo67[/MENTION], could you please update language files? Lithuanian (lt-lt) is really poor, maybe 30-40% only translated.

Regards.
[OnePlus 3 & 3T Cross Device Development] :
Yes of course! Just tell me where to get the update from.
[OnePlus 3 & 3T Cross Device Development] MJPollard:
You'd probably have to ask the LineageOS team about that, as NLOS is basically "LineageOS with some nifty enhancements." I doubt that Nvertigo67 is going to want to get involved with the language files; too much work.

EDIT: Didn't speak fast enough before he replied. Never mind! [emoji854]
[OnePlus 3 & 3T Cross Device Development] :
Since [MENTION=2606021]cukierkas[/MENTION] knows I can't do the translation myself (lack of knowledge of the Lithuanian language), his request only makes sense, with a pointer to the updated language files he is requesting - otherwise the request doesn't makes sense.
[OnePlus 3 & 3T Cross Device Development] pedritopl:
I had this issue a few days ago after _update_ from Magisk 19.1 to 19.2.

What I did and since then have not experienced the problem was:

- download latest Magisk uninstaller

- download 19.2 installer

- flash uninstaller in TWRP

- clean Dalvik/cache (probably not necessary)

- reboot to recovery (probably not necessary)

- flash Magisk 19.2

- clean Dalvik/cache

It was just 2 or 3 days ago, so it might be too early to say for sure, but for the moment it seems that fixed the problem.
[OnePlus 3 & 3T Cross Device Development] cukierkas:
https://review.lineageos.org/admin/repos/LineageOS/getcm-translations

Hope that helps. No need to translate by our own everything :)
[OnePlus 3 & 3T Cross Device Development] :
Please eloborate what you think. You've lost me. I have no idea what's the purpose of this repo.
[OnePlus 3 & 3T Cross Device Development] cukierkas:
Never mind, taking my words back. Wasn't thinking that language translations are difficult to find and add for such guru. There were roms, where authors were mentioning in changelogs about updated translations. I have no knowledge to point it properly with guidelines. So, let's leave it as one of the cloudy user requests.
[OnePlus 3 & 3T Cross Device Development] :
We have that, too:

https://review.lineageos.org/q/bran...*+message:%5E.*Automatic+translation+import.*

As you know, I'm only listing device specific and nlos specific changes in the nlos changelog. Everything else is in the los changelog.

BTW: the repo you mentioned is six year old javascript code for the cyanogenmod.org web page.
[OnePlus 3 & 3T Cross Device Development] cukierkas:
Thanks for clearing that up, that link was my wild guess. YOUR link was first one in search sequence, but my choice was wrong one m)

Take care.
[OnePlus 3 & 3T Cross Device Development] Luiscasanova78:
You have Oneplus3 and Stable Pie Firmware 9.0.2?