yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] knpk13:
I followed the discussion but I'm a little confused. Why did the bugged build work for some people but not others? Shouldn't IMS not work for everyone? It was mentioned that it's not carrier dependent, and I use a 4G LTE SIM, Cricket.
[OnePlus 3 & 3T Cross Device Development] Yndi:
Hmm, well I won't do that(use the nav bar). Ever since it is possible I'm doing the exact opposite and hide the status bar too. But thanks.

I did that but in my opinion it does not shine much light on the problem/help much. top says nearly everything is used, only about 50-80MB free; 80-100MB buffer while htop shows around 2,5GB buffer (~40%).

Whatever that means, the resulting restart of my most used apps annoys me and it feels like I'm having 6GB of RAM for nothing.

It's probably Google's 'fault' not yours, just wanted to say it somewhere.
[OnePlus 3 & 3T Cross Device Development] :
This expirience is mostly related to some battery saver (*) of pie...

(*) I belive it's called a 'feature' in aosp... YMMV... ;)

I don't know exactly what's going on there, but I know for sure it's not the lmk kicking in.
[OnePlus 3 & 3T Cross Device Development] :
The calls to oos proprietary methods are not limited to lte on cdma, nor is 4g support completely broken.
[OnePlus 3 & 3T Cross Device Development] Yndi:
I get & thought that already. Nevertheless I see the compromise between battery life and UX torn too far. For me at least.
[OnePlus 3 & 3T Cross Device Development] 13THWARRI0R:
Android takes to minimum of 1 GB for its system services which it cannot shutdown... Rest is taken by the apps installed ... For staying in memory for faster loading ... They will never be shut down until manually done... Plus your games ... And caches from browser and Google's little secret are also kept in ram.

---------- Post added at 05:38 PM ---------- Previous post was at 05:33 PM ----------

Is your sim 4g only ... Or does it fall back to 3g or GSM or wcdma ... Because of that's the case then .. if 4g is broken Android switches back to 3g or GSM if needed without user knowing ... Is automatic ... You won't even know ims is broken ... Until your sim is 4g only... Were Android doesn't know what to do ... If it can't switch. Hence break ... And Jio is 4g only... Pretty much a corner case to handle.
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=5708300]13THWARRI0R[/MENTION] and [MENTION=7134312]knpk13[/MENTION]:

But now it gets really strange... los seems to work with the three OOS 9.0.3 ims blobs... :confused::confused:

I compare the repo which los is using with the one I've used prior to kanging the old ims blobs:

git diff los/lineage-16.0 403afc29 -- oneplus3/proprietary/priv-app/ims/
byte 0/0 (END)

I'm lost again.
[OnePlus 3 & 3T Cross Device Development] knpk13:
It falls back to 3G yes. But the icon says LTE+, is that inaccurate then and I'm actually using 3G?

And [MENTION=4405529]nvertigo67[/MENTION] I'm not an Android dev so can't really help much more than point you towards [MENTION=5091734]dianlujitao[/MENTION] because as you have already noticed, official LOS is switching to 9.0.3 firmware finally.
[OnePlus 3 & 3T Cross Device Development] :
For my sim (mcc=262/mnc=02/vodafone.de) Every fall back is visible (and was with 9.0.3 ims, too): LTE+->LTE->3G->H+(rarely).

I'm not asking - I'm pointing out to you the facts, because you've asked. Why should I be confused alone? ;)
[OnePlus 3 & 3T Cross Device Development] 13THWARRI0R:
It might go to LTE+ occasionally trying to switch ... For a sec or two ... But depends on what is happening really... But yes you were using 3g

---------- Post added at 03:40 AM ---------- Previous post was at 03:18 AM ----------

They might not have got the bug yet... Is what I believe...
[OnePlus 3 & 3T Cross Device Development] :
You are right again (kinda pattern of habbit... ;) ):

https://xdaforums.com/showpost.php?p=79742628&postcount=2442
[OnePlus 3 & 3T Cross Device Development] deepak jr:
I found a pattern, every time I connect or disconnect a Bluetooth device, it reboots to twrp. Well last time I told that I was facing random reboots... I am clearly wrong. There's some problem with the Bluetooth I guess.
[OnePlus 3 & 3T Cross Device Development] :
Connecting and disconecting a bt device works without any issue. There's no problem with the bt, I guess.
[OnePlus 3 & 3T Cross Device Development] abhibnl:
[MENTION=4405529]nvertigo67[/MENTION]

A small OT question:

This is in reference to the modified 9.0.3 firmware with 5.0.8 BL and KM. Does using an older bootloader from oreo OOS affects performance of usability of the device in any way?

What I'm trying to ask is, would an updated bootloader or key master affect the device performance or reliability in any way like a Bios update does on PCs? Sorry if this quesiton won't make sense
[OnePlus 3 & 3T Cross Device Development] 13THWARRI0R:
[MENTION=8206680]deepak jr[/MENTION] can you please capture a log of the same .... connect device in debugging mode and connect to pc via usb cable ... adb logcat > log.txt during the issue ... and attach it with post ... it would be helpful for devs like us to debug the issues. :cool:
[OnePlus 3 & 3T Cross Device Development] :
Thanx. My patience with dealing with such insufficient support requests like the one you are answering here has ended some months ago.

I've decided not to beg for information, if people arn't willing to read and follow OP. The minimal prerequisites for issue reports are clearly stated. In this case a detailed description of the setup is additionally necessarry to exclude mods or apps.

I.e.: https://xdaforums.com/showpost.php?p=79744248&postcount=1377

Sorry, if this sounds harsh: if somebody is not willing to spend some time on reading and composing an sufficoent issue report, does not deserve my time for begging for some essential information.

BTW: I don't think this is reproducable on a clean flash following OP's directions. If you want to spend time on this, check the device's setup... I have a gut feeling... And: thanx again.
[OnePlus 3 & 3T Cross Device Development] 13THWARRI0R:
LOL ... I won't check this one... Unless I get the issue on my device ... I have been using bt for daily basis on this device for testing and development of head units made of Android .. and if I didn't find one ... Then it's obvious that's there will be no issues if we clean flash .. the request was just out of curiosity... :fingers-crossed:
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=5868698]64ashg[/MENTION] and [MENTION=9350973]All[/MENTION] others, who has expirienecd ril/sim/ims problems with the first native pie blobs build:

Check, if this build is working properly for you, please.

Background: the device maintainer hasn't liked the way [MENTION=5708300]13THWARRI0R[/MENTION] and me has fixed the mentioned issue (https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/250329 ) and introduced this one (https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/250376 ) instead.

Before stoping the pie-blobs-alpha builds and introducing the native pie blobs to the standard beta builds, I would like to verify it's working.

(Changelog comes with next beta build; this is just about the ril/sim/ims)

ROM: https://drive.google.com/open?id=1KrsMB8zyjlfcGCazXj5fn1kTwWYQGYfx

MD5: https://drive.google.com/open?id=19V5f9AjK8JrliwB2xBafqM-tmawQY5fe

Happy flashing!
[OnePlus 3 & 3T Cross Device Development] 13THWARRI0R:
Better solution rather than taking from other phones.. y didn't I think of that
[OnePlus 3 & 3T Cross Device Development] :
It actually is from an other phone, too (I don't know which one though, maybe some generic qcom msm8996). But he replaces also qti-telephony-common.jar and stays with the jnis. Not the other ims.apk, but the other differences makes me ask for another test. It's real dev's luxuary: having one proofed to work solition while testing a second one... ;)
[OnePlus 3 & 3T Cross Device Development] 13THWARRI0R:
I believe it's made from source that tag is QCOM source .. not a phone...

Yes... :highfive:
[OnePlus 3 & 3T Cross Device Development] 64ashg:
Happy to report that it works as intended over a dirty flash on the 16th june build. No reboots and working ril/sim since the last 10-ish minutes.
[OnePlus 3 & 3T Cross Device Development] :
The tag looks like codeaurora forum, but to my knowledge there's no public available source code for qti-telephony-common.jar.

I would also wonder, why we use a prebuilt jar and apk, if the sources are available...

A better reference to the source (this time not in the meaning of source code, but where the blobs exactly come from) would have been nice.

Anyway: as long as it's working...

Apropos "it's working": Special thanx to [MENTION=5868698]64ashg[/MENTION] fpr testing and reporting.
[OnePlus 3 & 3T Cross Device Development] pedritopl:
I'm not in the expected testing group (never had those problems with pie blobs), but anyway - just confirming, build 20190618 still works fine, just like the 20190616. :svetius:
[OnePlus 3 & 3T Cross Device Development] :
https://xdaforums.com/showpost.php?p=79756437&postcount=2495

As long as you havn't access to the sources (like me), you can't think of a source build... But you were right again (this becomes a bad hibbit of you... ;) ), it's not kanged from an other device.
[OnePlus 3 & 3T Cross Device Development] 13THWARRI0R:
Actually I have access to those source but not a nice system to build them ...
[OnePlus 3 & 3T Cross Device Development] :
Ha, then - of course - you should have thought of... *lol*

Without your finding, we would still stick on 5.0.8 and [MENTION=5868698]64ashg[/MENTION] would go crazy in two weeks after the 57th alpha build... Thanx, dude!
[OnePlus 3 & 3T Cross Device Development] 13THWARRI0R:
Lol ... Welcome buddy ... Between very much appreciate your work and rom ... The best ...
[OnePlus 3 & 3T Cross Device Development] mumapizza:
why is the firmware file so big?
[OnePlus 3 & 3T Cross Device Development] :
Probably asked a hundred times already but what happens when I dirty flash NLOS over LOS?
[OnePlus 3 & 3T Cross Device Development] MJPollard:
I've been wondering that myself (I could probably dive in and figure it out, but between job and family, I barely have time for everything as it is). I've noticed that almost every OP3/3T ROM (both Oreo and Pie) I've seen is huge compared to ROMs for other devices. Big honkin' proprietary blobs, maybe? I dunno. I make my own custom Lineage-based ROMs for my 3T, and I'm probably going to just eliminate every system app that I already have better alternatives for (Messaging, Music, Browser, etc.) and keep only the absolute necessities to cut down on the file size.
[OnePlus 3 & 3T Cross Device Development] pedritopl:
Short answer: bad things.

Just don't. Generally speaking what will happen is non-deterministic, but the phone will most probably *not* work as expected (been there, done that) :)
[OnePlus 3 & 3T Cross Device Development] mumapizza:
Firmware from here https://www.celsoazevedo.com/files/android/oneplus3t-modem-firmware/ is 50mb, the firmware file from nvertigos github was 900mb, when i downloaded the zip file. Thats what i meant with my question.
[OnePlus 3 & 3T Cross Device Development] :
What the heck are you talking about???

https://github.com/nvertigo/firmwar...op3/oxygenos-9.0.3-bl-km-5.0.8-firmware-3.zip shows a file size of 47.1 Mb.

If you use "clone and download"->zip you get a ziped clone of the complete git, of corse: https://github.com/nvertigo/firmware-3t/archive/master.zip

Stick to the links I've provided in the releasenotes of each build if you don't want to deal with githubs web-interface.
[OnePlus 3 & 3T Cross Device Development] mumapizza:
oh yes, i went to the release section and downloaded the .zip from the assets. Does your firmware come with the modem files aswell? The other source firmware + modem file is 3mb larger than yours
[OnePlus 3 & 3T Cross Device Development] :
Yes it contains the modem. "firmware" contains "modem". I don't know why others say their baskets contain fruit and apples - my basket comtains fruit. Anyway: why don't you check the git or the zip?

For the size: I use zip -9, perhaps the fruit and apples basket is packed with lower compression. In htc magic times, -9 wasn't a good idea, but I'm pretty sure a sd820 can handle decompressing 50 Mb packed with -9 in a timely manner.

It's hard to satisfy you: my firmware packages seem to be either too large or too small for you... ;)
[OnePlus 3 & 3T Cross Device Development] rezaluchu:
Hi [MENTION=4405529]nvertigo67[/MENTION], does OP3T support ANT+?

Several month ago (I forget which ROM I had), I cannot connect my phone with Garmin HR and Cedence sensor.

Good to know if it is actually possible.
[OnePlus 3 & 3T Cross Device Development] Viper The Ripper:
I've been reading your last comments, but the latter has made my day ROLF :laugh:

---------- Post added at 04:05 PM ---------- Previous post was at 03:58 PM ----------

AFAIK ANT+ is there since the native pie blobs were updated, plus recently updated with the lacked LA.UM.7.5.r1-04000-8x96.0 https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/250375
[OnePlus 3 & 3T Cross Device Development] :
I think so, but I can't check myself since I don't have hands on an ANT or ANT+ device.
[OnePlus 3 & 3T Cross Device Development] MJPollard:
Oh. Sorry, I misunderstood. Lack of sleep. Yeah, that's it. ;)
[OnePlus 3 & 3T Cross Device Development] xdam57733:
Update from NLOS 15 to 16 like a charm

Just a short success message...

After using NLOS 15 for a long time on my 3T, last weekend I updated to NLOS 16 (Oreo firware version). Was easy going using the steps below.

1) Backup all apps and data using 3C

2) Updated to last official TWRP (I know some special version was recommended, but wanted to try official first and had no issues)

3) Wiped system, data and caches.

4) Flashed ROM, Gapps Nano + Magisk

5) Reboot (restarted once or twice, looked expected)

6) Restored apps with 3C

Even the first boot did not take very long. The above complete updatewas done in less than 2h, cool!

Since then the ROM is rock solid, using less memory than NLOS 15.

I am only missing the Google Camera, but hopefully that is coming soon.

Thanks and keep up the great work, [MENTION=4405529]nvertigo67[/MENTION]
[OnePlus 3 & 3T Cross Device Development] pedritopl:
What do you mean? Google Camera is available and working perfectly fine on NLOS-16.0. I highly recommend the latest Tolyan version.

https://xdaforums.com/oneplus-3/how-to/modded-google-camera-hdr-60fps-video-t3658552
[OnePlus 3 & 3T Cross Device Development] xdam57733:
Thanks for the info, that is great to hear. My understanding was that this was not yet stable on this ROM and Dirk hadn't included yet, because of that.
[OnePlus 3 & 3T Cross Device Development] pedritopl:
Maybe you mixed the threads? NLOS is not Dirk's project :)
[OnePlus 3 & 3T Cross Device Development] S4turno:
All but the "legacy" versions on that thread work on NLOS 16 (and Lineage, Oxygen Pie, etc). Some are marked as "testing" because they may not be as stable yet (it's a new base), but you don't have to use the latest in order to have a good GCam version.
[OnePlus 3 & 3T Cross Device Development] Dirk:
I own all i survey! :D
[OnePlus 3 & 3T Cross Device Development] xdam57733:
I only mixed up names, I meant Ingo, of course :D
[OnePlus 3 & 3T Cross Device Development] :
I want to encourage everybody to follow this thread for gcam ports:

https://xdaforums.com/oneplus-3/how-to/modded-google-camera-hdr-60fps-video-t3658552

This is the greatest resources collection for gcam on op3/t! [MENTION=3131539]s4u[/MENTION]rno has managed to compile a thread with different gcam mods and a huge amount of information. Behave nicely, press thanx and enjoy that thread - I belive that's the best practice to keep [MENTION=4487956]S4turno[/MENTION] motivated to keep the thread up to date!

Thanx, dude!

nlos additions are gpl3: everybody, who survived it, own it! ;)

Stallman rulez!

...but only commit reading people will make a connection from Ingo to nvertigo67...
[OnePlus 3 & 3T Cross Device Development] xdam57733:
Thanks for the pointer. I know the thread and that there are various ports and it is great s4turno maintains this comprehensive list.

My assumption was though, that since you [MENTION=4405529]nvertigo67[/MENTION] hadn't included in the ROM (which I think you did for NLOS 15), there were issues with it still.

Google Drive shows your real name (or what Google thinks it is) as well ;).
[OnePlus 3 & 3T Cross Device Development] :
If you use a modded gcam, it comes with it's own libs. If I integrate those libs in the rom (or install the modded gcam with included libs as system app for that matter), everything is fine for the shipped gcam mod.

But if one installs another modded cam package with libs included (i.e. OneplusCamera) you get really funny effects. For OPCam on top of a rom included gcam, you can use the torch offscreen gesture to reboot to recovery... (ok, until I found the cause, it wasn't that funny... ;) )
[OnePlus 3 & 3T Cross Device Development] bertino:
Hi. I am on Nitrogen OS pie with Oreo firmware (ext4, unencrypted) and wanna flash the latest NLOS. Do I need to format userdata, (very clean flash) or just clean flash as mentioned in the op? (You also say in the release notes something about losing userdata)
[OnePlus 3 & 3T Cross Device Development] :
That depends on which twrp was used for last format and the final setup after flashing you want to run. I:e. if you have formated data with twrp 3.2.3-1 the last time and want to run nlos with encrypted data (running a device with custom recovery and no secured boot passphrase set is grossly neglient), you need to format data.

The OP directions are the foolproof way to properly setup nlos. The releasenotes is additional build specific information: it's precisly on describing when loosing data. If you are already on 9.0.3, there's no need fpr any action.
[OnePlus 3 & 3T Cross Device Development] bertino:
Is there any security threat introduced by running unencrypted other than physical access?
[OnePlus 3 & 3T Cross Device Development] :
No.

But running the device WITHOUT ANY PROTECTION (I can delete your lockscreen setup and steel your digital identity including fingerprints with a custom recovery and data unencrypted) against physical access (lost or stolen)... That's not a minor threat, that's missing basic device intergrity.

(Because I can't use the hashed fingerprints now, doesn't mean I can use them in 7 years...)
[OnePlus 3 & 3T Cross Device Development] bertino:
Guess I should finally reencrypt my phone then...

Im 99.9% sure thieves in my country wouldnt think to steal my data too, so I don't think its such a big deal.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
You should encrypt and use an on boot password. Encryption with a default password is just as unsafe as unencrypted.
[OnePlus 3 & 3T Cross Device Development] cukierkas:
Hello all. [MENTION=4405529]nvertigo67[/MENTION], will you be able to include sbc HD codecs into nlos?

Works fine on derpfest with 5t.

https://github.com/Havoc-OS/android_system_bt/commit/62bec56036fe0df55dd14528b939acb37668b7e8

This upgrade makes cheap sbc headsets sound better :D
[OnePlus 3 & 3T Cross Device Development] 64ashg:
After reading the documentation, i would also like to +1 this.

It would be great for my car audio setup :)
[OnePlus 3 & 3T Cross Device Development] :
This patch doesn't work as standalone patch. It's part of a patchset consisting of 8 patches. All of them are merged to los on May, the 13th.

https://review.lineageos.org/q/topic:%22bt-sbc-hd-dualchannel-pie%22+status:merged

Also: the commit message suggests: "With 452 kbit/s, SBC outperforms aptX, with 551.3 kbit/s, on par or close to

aptX HD." Though this is true for bitrates, my real life expirience is the complete opposite: aptx sounds much richer, warmer and more natural then sbc - no matter how you setup sbc in devopts. (tested with Teufel MOVE BT)

Since the topic is already merged, the quality enhancememt can't be that much, otherwise you would have heard it... ;)
[OnePlus 3 & 3T Cross Device Development] 13THWARRI0R:
Well truth is that we have the encoder part which takes care of the encoding in dual channel sbc after that patch... But does the receiving devices have similar decoders to decode it ...?:confused: Food for thought... Hence the output remains same of the audio even though we have all the goodies integrated..
[OnePlus 3 & 3T Cross Device Development] :
Since no one has noticed a quality increase after this topic was merged...

It's always the same: claim some dramatic increase, throw around some numbers, and everybody "feels" the massive step in quality. Just put it in and tell nobody, and nobody notice. That's called placebo.
[OnePlus 3 & 3T Cross Device Development] cukierkas:
Just because after update, Bluetooth headset must be re-added and HD option selected. Let's guess, how many of us and how often are checking Bluetooth settings?

In other hand - not all cheap sbc headsets support dual channel :( having one in my other car - sadly, HD option or dual channel option must be deselected in developing section, just because its not made by manufacturer :(

€ 10,45 46%OFF | L15/G03K Wireless Headphones Sports Bluetooth Earphone 5.0 Stereo IPX5 Waterproof Bluetooth Headset with Mic for iPhone Xiaomi

https://s.click.aliexpress.com/e/cMmZDI4o

Don't buy them.
[OnePlus 3 & 3T Cross Device Development] xdam57733:
OK, first time updating NLOS caused problems...

I tried installing the 20190619 version which required me flashing 9.0.3 firmware first. Now after booting, it says my password was correct, but my data was corrupted and I need to do a factory reset. WHAT?!?

Any quick advice?

---------- Post added at 11:21 PM ---------- Previous post was at 11:11 PM ----------

Even booting to the installed TWRP wouldn't work anymore. So used fastboot to boot it, but it cannot decrypt the phone :crying:

Furtunately I have an app installed which automatically syncs photos to my NAS, once I am in the Wifi network, so damage will not be too big. But still...
[OnePlus 3 & 3T Cross Device Development] knpk13:
Did you follow the upgrade instructions properly?

I'm guessing you haven't been reading the OOS, LOS, NLOS, or the firmware threads. Very well known issue that flashing 9.0.3 firmware with an unlocked bootloader corrupts data. I'd recommend you read the forums a bit more carefully before attempting a major firmware update so you're aware of bugs/issues.
[OnePlus 3 & 3T Cross Device Development] :
Please honor the information in the releasenotes: if you use the regular 9.0.3 fw you need to format data, if your bootloader was unlocked. If you use the modded fw, you skip these problem (for now).

Do I guess correctly, that twrp boots fine, but userdata can't be decrypted? If so: format data.