yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] ithilstone:
I did report problem with dirty upgrade 16 to 17.1 0406 to let guys know that if they try and it do not work then they might try 0402 as it worked for me - it was intended as a information and possible workaround

Problem with flip case was reported as an information and to let others know that it is potential issue - first person to reply let me know that on clean upgrade there is no issue so to me it was confirmed as a problem with dirty upgrade and that's end of problem for me - if that's wasting precious resources than i am sorry and will not report anything else back
[OnePlus 3 & 3T Cross Device Development] Eggstones:
As my phone stopped getting the nightly updates since the 4th do I need to install all the inbetween ones and install them or can I just use the latest. Phone is not decrypted so not sure why the OTA stopped working unless it has to do with magisk/The magisk modules i've been trying out.
[OnePlus 3 & 3T Cross Device Development] counterfeit187:
Deleted. Issue was user error... I'm an idiot and flashed the wrong file. Didn't realize Twrp kept last used directory.
[OnePlus 3 & 3T Cross Device Development] BRDigung:
Is there a way or an app to get this feature back?
[OnePlus 3 & 3T Cross Device Development] :
No, manually updated and nicely saying 07/04 build.
[OnePlus 3 & 3T Cross Device Development] :
No; screen lock none, swipe, pattern, pin, fingerprint.

Btw; asking once is enough....
[OnePlus 3 & 3T Cross Device Development] Viper The Ripper:
Please don't repeat the same post, we've seen your post once... No, if you want Face Unlock feature go for Pixel Experience ROM, the latest build has it as announced in the changelog
[OnePlus 3 & 3T Cross Device Development] Eggstones:
Did it manually as ota stopped working and I see the right date.
[OnePlus 3 & 3T Cross Device Development] Adam Hui:
I saw [MENTION=3456089]nvertigo[/MENTION] 's post about system app called "soter" which supports alipay, etc., but didnt find it anymore as now. Just curious why it deleted or somethin' & can someone pls rewrite it again for me as completely it was?
[OnePlus 3 & 3T Cross Device Development] :
Honestly, I don't remeber I've discussed this here. The most comprehensive thread on this topic is

https://xdaforums.com/oneplus-3/how-to/guide-deblob-alipay-ifaa-tencent-soter-t4064893

some discussiom is here:

https://xdaforums.com/oneplus-3/one...oneplus-3t-t4034869/post82030693#post82030693

And - of course - some discussion can be found in the nlos thread.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I always charge my phone before I go to bed, so I've never seen what the overnight drain is at the other end. But, just for you, I didn't recharge it last night and here's the result: 31% down to 28% for a loss of 0.4%/hr.

This is a lot better than your 2.2%/hr so maybe my battery is holding up better. It's just over 3 years old - bought it in March 2017.
[OnePlus 3 & 3T Cross Device Development] LettucePie:
Hey I'm having a very strange issue relating to Hotspot and Tethering. I'm not sure if it's an error in Lineage or with my provider Tmobile. When connected to the default Access Point Network "T-Mobile US LTE" if I enable either hotspot or usb tether, the signal bars get a tiny X, and neither the phone or anything connected to it can connect to the internet. This problem persists until I restart the phone or switch Access Point Networks. Now if I add another Access Point Network "epc.tmobile.com" and switch to it as my active network, all tethering and hotspot functions work as expected.

If this is the wrong place for this bug post please direct me to where it can be more helpful.

Worth noting, I did a full wipe + format before installing the latest version using TWRP 3.3.1-1
[OnePlus 3 & 3T Cross Device Development] :
Interessting. At least the 0%/h is not reproducable at lower bat levels.

My device's 0%/h "highscore"... ;) See attachment...

My device is from December 2016 and overall bat performance has decreased.
[OnePlus 3 & 3T Cross Device Development] tim-scrap:
Am I right that LOS 17.1 doesn't use max. dash charging?

Otherwise an awesome good Rom. Fast, battery good, reliable. :)
[OnePlus 3 & 3T Cross Device Development] Mata99:
I would like to signals that notification sound croak and Instagram notification doesn't work.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
How do you define max dash charging? Subjectively I think it charges the same as OOS.

Notification sounds are fine for me.
[OnePlus 3 & 3T Cross Device Development] tim-scrap:
The OP3 can go up to ca. 3,5A (until approx. 80%). with los the charging seems to go not that high.
[OnePlus 3 & 3T Cross Device Development] votz11:
bluetooth is locked to default codec, can someone change that ?
[OnePlus 3 & 3T Cross Device Development] Spanking Time:
I take it you have the Google app disabled or not installed? Google app on my system is literally in constant active use, taking a good chunk of battery daily. I've looked around and haven't found a solution, other than disabling it, which I really don't want to do. :(

---------- Post added at 10:01 AM ---------- Previous post was at 09:54 AM ----------

I believe you must be connected to a bluetooth device which supports any of those other various codecs in order to change it in the settings. For instance, when I connect my aptx enabled headphones, the option automatically switches to aptx codec.
[OnePlus 3 & 3T Cross Device Development] Eggstones:
Just realised why I didn't get any OTAs. The settings were set to weekly checks...
[OnePlus 3 & 3T Cross Device Development] sephk:
I did a complete wipe, formatted "everything" and then flashed latest nightly. It worked fine for 3 days and then mic stopped working again today, happened after a whatsapp call. Reboot fixed it again.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I have Google app installed as a user app and it's not disabled - I use it a fair bit. I don't have assistant set up.
[OnePlus 3 & 3T Cross Device Development] Spanking Time:
Ah, Assistant seems to be the culprit then. Turned it off and the constant active use stopped! Don't have anywhere near as good stats as you're showing though.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Right. I'll check and report back. It'll take a couple of days.
[OnePlus 3 & 3T Cross Device Development] thesplitter:
Yeah but isn't that supposed to be a preference?

My autoradio supporta LDAC but it always defaults to AAC, i Need to manually select LDAC from dev options
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Usage varies by user and environment. Things like signal strength, app usage, screen brightness, background services, scanning settings, connected devices, etc all affect battery usage and make it difficulty to compare battery usage.

I've been running essentially the same setup for a number of years so I know what to expect from my phone: no overnight drain and at 10%/hr or better SOT.

And I get this from both OOS and Los on stock kernels and no tweaking.
[OnePlus 3 & 3T Cross Device Development] Spanking Time:
I have screen brightness all the way down, scan settings are off, use very few apps, so I really try to mitigate power usage from those things. I have awful mobile signal strength where I live, however. Usually none at all to maybe 1 bar if I'm lucky. Would it help conserve battery to turn off mobile data, even though I'm always on Wifi at home?

---------- Post added at 06:14 AM ---------- Previous post was at 06:09 AM ----------

If the codec doesn't automatically switch in the settings upon connecting that bluetooth device, I'm thinking this ROM doesn't support that particular codec. I may be wrong, but I don't think every codec listed in the settings actually is supported by the ROM. I noticed you can also go to the setting of your bluetooth device and there should be a switch that you can turn on/off for its particular supported codecs. If LDAC isn't listed there, then it's probably not supported.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I would definitely turn off mobile data.
[OnePlus 3 & 3T Cross Device Development] rlees85:
Probably better and more convenient to just disable "always on mobile data" in developer options, this way if you are on WiFi at home your mobile data should drop anyway.

That said probably wont help, even searching for a none-data signal eats battery, aeroplane mode + just wifi would help a LOT but obviously no calls/texts will work

---------- Post added at 01:43 PM ---------- Previous post was at 01:37 PM ----------

Interesting commit: https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/272534/

Does this mean we are using some blobs from Xiaomi A2 Lite now?

Ever since OnePlus3 9.0.x firmwares & blobs I've had a weird issue where phone just crashes on aeroplane mode during the night. If it is working OK it says working as long as I don't reboot. If I have to reboot (ie. to update) it may/may not start crashing during the night again. This happens on any ROM (OxygenOS or otherwise).

Wishful thinking, but I am hoping its blobs and not lower down in the firmware. I'm 99.9% sure its sensor related as if I leave it in a light room on aeroplane mode it never crashes. Tried to get kernel panic logs but pstore is always empty.

So my life story aside, curious about these new blobs for OnePlus 3 :)
[OnePlus 3 & 3T Cross Device Development] adithya2306:
Can anyone confirm if VoLTE works?

Edit: never mind
[OnePlus 3 & 3T Cross Device Development] Imnoa:
The search button can:

https://xdaforums.com/oneplus-3/one...eplus-3-3t-t3990061/post80684689#post80684689
[OnePlus 3 & 3T Cross Device Development] adithya2306:
Yeah, never mind. The first time I searched it for some reason the website didnt load properly so I mistook it for "no results". But 5 mins later when I searched later again I found the answer, volte doesnt work.
[OnePlus 3 & 3T Cross Device Development] tehchap:
Flashed last build, everything seems to work pretty good except for the Gcam which is stuck on "processing HDR" so the notification won't go away unless you force stop it. I'm wondering if it's a rom related issue or not, Google brings up other results but Lineage 16.0 was working perfectly.

Other than that, battery is kinda bad, I assume it's because the phone doesn't enter deep sleep. Waiting for a new build, keep up the great work!
[OnePlus 3 & 3T Cross Device Development] Lord Broker:
Try HyperCam

https://www.celsoazevedo.com/files/android/google-camera/f/changelog744/
[OnePlus 3 & 3T Cross Device Development] serj.borgore:
It’s a gcam problem, you have to use <7.0.. but they aren’t good enough in terms of quality.

Inviato dal mio iPad utilizzando Tapatalk
[OnePlus 3 & 3T Cross Device Development] felixchris:
For me newest GCam from Tolyan009 works fine.

Managed to get safety-net pass with magisk and the proposed script, thanks for that ?

Will test NFC/GPay when I get the chance.

For now there is no other accent color than teal which is fine for me, it's alpha after all :D

For some reason Quick Settings are super sluggish while the rest is snappy. Will have to investigate whether that's a general thing or only with media controls running or something like that. I should say I activated dark theme and switched to black.

So far so great, thanks again for keeping this device up to date.
[OnePlus 3 & 3T Cross Device Development] tehchap:
You can get other accent colors in developer options :)

Thanks for the info on Gcam, I'll try the new one from Toylan and report back.
[OnePlus 3 & 3T Cross Device Development] felixchris:
Thanks man. It is a 6.2 GCam though.
[OnePlus 3 & 3T Cross Device Development] tehchap:
Is anyone else experiencing frequent cellular line drops while calling? I can't get past a ~20 seconds call.
[OnePlus 3 & 3T Cross Device Development] PlayFriik:
Cellular connectivity hasn't dropped while calling yet, but LTE drops occasionally.
[OnePlus 3 & 3T Cross Device Development] chtitlou:
Yes I do. Not only LTE drops but also full disconnection. It doesn't last very long -few seconds- but is much less frequent than you seem to experience though, since I can make quite long calls.

Grabbing a logcat is really difficult due to pretty random and rare occurrences.

Besides I got the logcat for the Wifi Access Point issue, resulting in a soft reboot. It's pretty big since there is quite a long time between the activation and the crash. In the meantime, several devices can connect to the WAP but no data can pass through. Hope that would help.

At last, when a devices is connected through WAP, LTE and even cellular drops often happen. Don't know if there is a direct link between those two but I can grab a logcat in this situation if needed.
[OnePlus 3 & 3T Cross Device Development] Imnoa:
My device (soft) reboots after about a minute after a client connects to my wifi-hotspot.

Logcat attached.
[OnePlus 3 & 3T Cross Device Development] akkikr19:
Which month security patch has been patched into this ??
[OnePlus 3 & 3T Cross Device Development] Imnoa:
October
[OnePlus 3 & 3T Cross Device Development] percyylin:
Is there any chance that my OnePlus 3T could upgrade

from LineageOS 16 (say, lineage-16.0-20191110-nightly-oneplus3-signed.zip)

to LineageOS 17 (say, lineage-17.0-20191025-UNOFFICIAL-oneplus3.zip)

WITHOUT WIPE DATA partition?

I want to verify an app's behavior after system upgraded from Android 9 to 10.

I tried installing my app on LineageOS 16 and upgraded to 17 via TWRP 3.3.1-0 without wipe data partition.

It seems that system apps would force-closed and after a while the phone automatically reboot to TWRP.

I also tried wiping data partition afterwards and the phone behaved normal - without my app of course.

Is there any chance I could achieve that?

Thanks in advanced.
[OnePlus 3 & 3T Cross Device Development] Imnoa:
It might be possible, but don't expect a stable or otherwise usable rom.

Just backup your files, use the migrate app for apps and perform a clean flash
[OnePlus 3 & 3T Cross Device Development] MJPollard:
Upgrading from one major version to the next (i.e. LineageOS 16.0 to 17.0) is never a good idea. Too many things are changed, making it a very risky proposition. At the very least, you'll end up with an unstable phone. At the very worst, your phone will probably go into an endless bootloop. In either case, you'd have to do what you really should have done all along: wipe everything and install from scratch.

So, my recommendation would be to back up all of the apps and data (and whatever else you want to keep, just to be on the safe side), wipe the data, cache, and system partitions, install 17.0, and restore your apps and data. You may still encounter problems (the current 17.0 is still experimental, after all), but it won't be because you dirty flashed on top of an older ROM.
[OnePlus 3 & 3T Cross Device Development] Dirk:
You've both missed the salient point in percyylin's post. He didn't ask if it's possible to have a stable or otherwise usable ROM, or whether it's a good idea to update that way. He's trying to test the behaviour of an App and it's associated Data through the update. To do that he needs a way to do the update without wiping Data:

It has been possible in previous generations, but now we have system as root... which to my mind makes it almost impossible to go from Pie to 10 without a clean install.
[OnePlus 3 & 3T Cross Device Development] MJPollard:
Given the fact that dirty-upgrading a ROM from one previous generation to the next

will

cause problems, any test on this particular app would not yield accurate results, as there's no way to determine if anomalous behavior is due to the new ROM itself or because the system is unable to cope with the configuration of a previous ROM. That's a point that

you

seem to have missed.
[OnePlus 3 & 3T Cross Device Development] ithilstone:
In Dev options you can switch off "Mobile data always on" it will kill mobile data the moment you connect to WiFi

---------- Post added at 02:49 PM ---------- Previous post was at 02:44 PM ----------

my phone defaults to LDAC on all 3 LDAC supporting HPs and in Dev option it shows LDAC and let me change all related options - I can also change connection to AAC manually but next time i connect HPs it will go back to LDAC.

On the other hand my DAP that is supporting LDAC connects to SBC only and no matter what i change in Dev option it is only using SBC ( annoying as hell but i am sure it is a DAP fault)
[OnePlus 3 & 3T Cross Device Development] mangokm40:
I was on LOS 16.0 and using addonSU. I am now on LOS 17.1 and using Magisk.

The file explorer that comes with LOS 17.1 allows me to install apps from an apk. However, I am unable to do it from another file explorer (Total Commander).

I have allowed unknown sources for the app. I have given the app root access, through Magisk. When I select an apk file, I can "open as zip". However, when

I try to install, I get "Error: Can't open file/folder".

As it worked fine in LOS 16.0, I thought I'd ask if there's something new in 17.1 I may be missing.

I'm not sure this is due to the ROM, so forgive me if this is posted in the wrong place...

Thank you.
[OnePlus 3 & 3T Cross Device Development] PTuT:
Install beta Total Commander and it will work.
[OnePlus 3 & 3T Cross Device Development] :
There is already said a lot which I also would suggest, as for example switching off "Mobile data always on" in Dev options. Additional I think it could help to switch mobile network to 2G instead of 4G because it is more long-range and so would have better mobile signal strength AND lower power usage.
[OnePlus 3 & 3T Cross Device Development] thesplitter:
Then it's my damn radio, it has a companion app from Sony and it goes on LDAC only when that's running, it's annoying having an app always in background just for that..
[OnePlus 3 & 3T Cross Device Development] rg_gapa:
Dirty flashing is (at least) not recommended, that's understood, but can I safely restore user apps with data from Titanium Backup? I mean backups made at LOS 16.
[OnePlus 3 & 3T Cross Device Development] :
I've hunted for an issue with notification led since 15.1. I thought notification led was working correctly on 14.1 the last time. I can't get it working reliable on 15.1 nor on 16.0. I've always clean flash on major version changes and restore some apps with data from tb. I never restore system apps or system data.

Some weeks ago I accidently uninstalled spiegel app (a german news magazin, with push notifications - I was to lazy to resetup those notifications). I was on the road when this happens and my usb stick with my tb backups was at home. So I've installed spiegel app again and set it up manually. Suddenly the notification led started to work reliably...

I was hunting a phantom issue for over two years.

I think the answer to your question is: yes it's safe, most of the time... ...until it's not.
[OnePlus 3 & 3T Cross Device Development] ithilstone:
So in other words restoring apps with backup soft is as bad as dirty upgrade at least in phantom issues department right?

I will keep my dirty 17.1 till i have a spare day to do a clean one and restore everything from scratch till then i will have to bare some small inconveniences
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Ok, I collected the charging statistics for both Los 17.1 and OOS 9.0.6. the command I used was:

dumpsys batterystats --checkin | grep ",csd" > /sdcard/batt.csv

Ref: https://developer.android.com/studio/command-line/dumpsys#battery

I used the phone until the battery level was below 30%. Then I plugged it in to recharge and left it with the screen off. When it got to about 90% I ran the command to collect the data.

I then graphed the results (screenshot) and it shows that the initial charge rate is the same for Los and OOS, but Los charges more slowly towards the end.

Note that the graph is battery level as a function of time, not Amperes because the system doesn't record that.

I've also attached the spreadsheet with the raw data.
[OnePlus 3 & 3T Cross Device Development] zazenoz:
What is the android security pack version?

The alert slider works?
[OnePlus 3 & 3T Cross Device Development] :
You can check the max amps using "Ampere" app when the battery level preferably below 15%. Look at the min max on the top, not max usb current below.

With

los 16

, it goes to 3.6A max so i don't see any problem
[OnePlus 3 & 3T Cross Device Development] :
I was digging in some build.prop settings because I would like to increase all volume steps to 30.

Working for media volume, call volume and alarm volume, but can not get it working or ring volume and notification volume.

The last is bothering me because even the lowest setting (step 1) is too loud for me.

I thought these were the settings to add to build.prop but as said above not all seems to work:

# Volume steps to 30 and remove high volume warning
ro.config.alarm_vol_steps=30
ro.config.media_vol_steps=30
ro.config.ring_vol_steps=30
ro.config.system_vol_steps=30
ro.config.vc_call_vol_steps=30

Who knows how to change volume steps for ring and notification volume?

16-04-2020 Edit:

After more research I came to the conclusion that only the following settings really do have a function:

# Volume steps to 30 and remove high volume warning
ro.config.media_vol_steps=30
ro.config.vc_call_vol_steps=30
audio.safemedia.bypass=true

It is not possible to add more volume steps for ring volume and notifications using build.prop settings.
[OnePlus 3 & 3T Cross Device Development] :
No. I want to say it's quite complex and the original question can't be answered with an absolute yes or no.
[OnePlus 3 & 3T Cross Device Development] PlayFriik:
I have found this app quite handy: https://play.google.com/store/apps/details?id=com.kozhevin.rootchecks

This app found that LineageOS 17.1 is only failing at "dangerous props".

I don't think the issue is user.debug though, since I run my PixelExperience builds the same variant and the app doesn't fail at "dangerous props".

The variants may vary ROM by ROM..?
[OnePlus 3 & 3T Cross Device Development] :
Probably. That's also the reason I added all settings Magisk Hide is using, with the effect I hoped for... ;) I did not want to check which setting was the problem but it can even depent on how the app is checking stuff, so replacing all settings is probably the safest way to go.
[OnePlus 3 & 3T Cross Device Development] :
We need a comprehensive list of dangerous props.

I'm pretty sure one of them is ro.debuggable (which is set on userdebug build type by default on aosp and los - which can be overwritten, of course). The problem is that unsetting e.g. ro.debuggable has more consequences then getting rid of one of the dangerous props.

Some companies don't want that their apps are used on non-vendor roms and some users want to use these apps on non-vendor roms. This is always the same race.

Sidenote and OT: the legal terms of an app are interesting stuff to read... ;) Most companies manufacutring apps which check for root don't see the customer as the owner of a device, who is in full control of the device, but as an object to get money and data from, who shouldn't be able to limit getting money and data. If you don't like this attitude, stop using those apps and stick to foss.
[OnePlus 3 & 3T Cross Device Development] Eggstones:
Would this help with the appealing reception I have in my flat? Tried to figure out how to do this but failed miserably.
[OnePlus 3 & 3T Cross Device Development] :
I don't know. In most countries 3G (WCDMA) will be switched off the coming years, but 2G (GSM) will probably stay. As 2G is mostly using the 900Mhz band, is is more long range then 4G (mostly the higher bands like 1800Mhz etc..).

When bandwidth is not an issue you could choose GSM/WCDMA/LTE in your network settings to see if it makes any difference.

I know MSM and probably some other ROMs do have an option to switch to 2G when phone is entering sleep, and remember some apps (for rooted phones) which are giving the same option. I guess this is what would be preferred in your case ;)
[OnePlus 3 & 3T Cross Device Development] Eggstones:
Thanks I'll try this and see if it helps. Currently I have one bar in my garden.