yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] djplus:
Guys is this the optimum charging ?

Is 7.8 normal or there should be 9.0 ?
[OnePlus 3 & 3T Cross Device Development] djplus:
Couldn't attach image in previous post
[OnePlus 3 & 3T Cross Device Development] TheBestPessimist:
Hey guys,

I'm having a bit of a problem with the number of background apps that are kept: at all times no more than 5 apps are found in recents, and whenever i open the 6th, the last (earliest) used one is closed and disappears from recents. I have looked in developer options and it seems that i'm using the default for background apps, and if i try to edit that i can only chose 0 - 5.

Is there a way to have more apps remain idle in memory? 6GB of ram must be enough for storing more, right?

If anyone has any tips on how to edit the number of background apps, I'd very much appreciate the advice.

Thanks
[OnePlus 3 & 3T Cross Device Development] SenseSei:
I personally disabled LMK (low memory killer) with Kernel Adiutor. Maybe the helps

Edit: it probably only helps after rasing the limit of background apps (from developer)
[OnePlus 3 & 3T Cross Device Development] TheBestPessimist:
As far as i can see, it's disabled by default (i think i attached the picture)
[OnePlus 3 & 3T Cross Device Development] :
Disabled with latest upstream device tree commkt on July the 28th: https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/251923

BTW: recents and memory managment doesn't really correlate: i.e. removing one, more or all apps from recents doesn't close them, nor does it free any memory. Killed bg apps arn't neccessarily removed from recents (barely happens, since the recents are truncated long before bg is killed by lmk), but you can force the situation by intentionally killing an app.
[OnePlus 3 & 3T Cross Device Development] TheBestPessimist:
(clean flash btw, deleted EVERYTHING from /data since i formatted to etx4 from f2fs; forgot to say this first time)

Then i don't know what's exactly going on, but the 6th most recent app i open is always reopened as if it was closed :-?
[OnePlus 3 & 3T Cross Device Development] :
I don't know what's exactly truncating the recents - your observation is correct, but (though almk definetly has some glitches) not because of lmk... I'm behind this since earliest 16.0 builds...
[OnePlus 3 & 3T Cross Device Development] TheBestPessimist:
So what you mean is i just have to use it as it is, since there's nothing to fix. (we don't know where the problem lies)
[OnePlus 3 & 3T Cross Device Development] :
I don't know how to fix this - and even worse: I don't know who to ask... ;)
[OnePlus 3 & 3T Cross Device Development] thomasnsr:
I have tried to flash NLOS over LOS by following the steps: wipe system, wipe cache, wipe dalvik, then flash nlos, gapps and magisk 19.3. I have not encountered any lagging or reboot, not even once. NLOS brings me fast response and better standby battery drain. Feels like a brand new 3t again. Thank you very much [MENTION=4405529]nvertigo67[/MENTION] :good::good:
[OnePlus 3 & 3T Cross Device Development] :
You'll run into trouble sooner or later. Keep in mind, that sound indexes (for notifications, alarms and ringtones) differ, as well as some tiles and some settings... If issues occur (perhaps after the 11th futute update) you are on your own - this thread doesn't support dirty flashing nlos over an other rom.
[OnePlus 3 & 3T Cross Device Development] TheBestPessimist:
One other issue I'm having: it seems that on wireless ac, reconnecting (I had wireless turned off for 30 minutes, then took my phone and turned it on via the quick toggle) takes a good 15 - 20 seconds. It's as if the phone is waay slower to search for ac networks, than it is to search for n networks (which is instant).

On OOS stable 905 the reconnection lasts less than 5 seconds almost always.

Are there any knobs to be tuned here for a faster experience?
[OnePlus 3 & 3T Cross Device Development] :
As discussed in the los thread: there are - at least - two serious issues in wifi handling: the one you ate describing and not being able to use 5GHz hotspot in Europe. I guees both are related to the use of SRD channels. The check if there's no radar burst on those channels takes about 20 seconds (explains your observation); if the hotspot is setup on a SRD channel, no device sticking to Europe regulations can ever see i.e. a hotspot running on channel 159.

Especially on the second issue I've provided a lot of debugging information (including logs with additional debug statements) in the los thread. Sadly nobody knows how to change this to not using SRD (and DFS - no device manufactured 5 years ago can handle theses) channels.
[OnePlus 3 & 3T Cross Device Development] TheBestPessimist:
I think you're referring to this discussion: https://xdaforums.com/showpost.php?p=79488475&postcount=1969? My router is an asus ac87u, and afaik the channel on auto-select is 100.

I have tried also channel 44, and there's no difference: it still takes a good long long time to detect the AC network :(.

In this case i'm gonna check an AOSP rom, and see if there's something different happening.
[OnePlus 3 & 3T Cross Device Development] :
...but it will never use (nor is it manually selectable) SRD channels (higer then channel 142).

As said: I'm guessing here, and I would reallyreallyreally apriciate any help in hard blocking SRD channels and taking the additional logic for using SRD channels completely out of the game.

If you look in the specs, using SRD chanmels needs much more care, because the frequencies are used in other - higher priority - services, too. The additional care takes time. This is performed, no matter if you use them or not.

Since 5GHz hotspot has worked on 15.1 and 14.1 I havn't debughed at that time back. My best guess is: since the wifi handling has changed (SRD channel use was introduced; 15.1->16.0) the additional ürocessing time was added as well as the constant usage of channel >142 for 5GHz hotspot.

If my assumptions are at least partly right, the test with channel 44 yields the expected result (still long time to successfull negptiation).

Great idea. Would you like to check if the hotspot is run on channels <=142, please?

EDIT: I use the term "hotspot" in the meaning of "tethering hotspot of the device".
[OnePlus 3 & 3T Cross Device Development] Siddk007:
Finally, switched from OOS to NLOS 16.0. Might not switch to another rom for a long time I guess. It's that good :good:
[OnePlus 3 & 3T Cross Device Development] djplus:
The Rom is exceptional and fluid, just turn on backlight dimmer and set battery to efficiency, and still the phone runs smooth ( and keeps the phone cool )
[OnePlus 3 & 3T Cross Device Development] Siddk007:
[MENTION=4405529]nvertigo67[/MENTION] bumped into one issue ?

In Poweramp, there is no sound when Hi-Res audio (Direct HD) and Direct Volume Control (DVC) both are active. Disabling Direct HD gives sound. Never faced this issue on stock rom. even removed Ainur audio mod that had flashed but still same issue
[OnePlus 3 & 3T Cross Device Development] Mizart:
I'm currently unencrypted. Does this ROM have force encryption like OOS ?
[OnePlus 3 & 3T Cross Device Development] S4turno:
It doesn't force encryption.
[OnePlus 3 & 3T Cross Device Development] :
Direct HD and DVC refer to poweramp specific technologies, don't they? I can't find any documentation on those protocols/codecs (currently I even don't know if these are codecs or whatever). If you find out on which prerequisites these codecs (?) depend on, I'll try my best to implement those.

For the usb dac offload: I have no clue what our usb dac is capable of and I've never used external usb dacs.

If you have bought pa, you may want to contact the support to shine some light on the above.
[OnePlus 3 & 3T Cross Device Development] Siddk007:
Thank you for the response. Can this info in pic help, because I also dont have any idea about the codec and other stuff. Will contact Poweramp support if required
[OnePlus 3 & 3T Cross Device Development] :
Delayed 5GHz AP scan

Symptom/issue:

5GHz APs show up after a delay of 20 - 30 seconds compared to 2.4 GHz APs.

Possible solution (please test and report back):

Delete or comment out line 6 ("gInitialScanNoDFSChnl=1") from /system/vendor/etc/wifi/WCNSS_qcom_cfg.ini:

reboot to twrp

mount system

open a terminal (Advanved->Terminal]

type exactly:

/system/xbin/vi /system/vendor/etc/wifi/WCNSS_qcom_cfg.ini

move the curser to line 6 ("gInitialScanNoDFSChnl=1")

press d twice ("dd"); the line is deleted now

press (without the quotes): ":wq"; press "enter"; this writes the changed file and quits vi

umount system

reboot to system

If you are rooted feel free to use the rooted filemanager and editor of your choice.
[OnePlus 3 & 3T Cross Device Development] :
That tooltip does not really enlight us/me.

But if it's working on oos we may can get it to work here, too - i.e. missing blobs or something else from oos.

I'd like you to ask the support. Before digging in logs, specs and documentation, I hope it's an easy one, which is known to the pa staff (hope dies last...). ;)
[OnePlus 3 & 3T Cross Device Development] TheBestPessimist:
YESSSSSS THAT WORKS!!!!! now my phone connects to my AC network in about 5 seconds after i turn the wireless on.

The only bug that i have found (in 5 minutes of testing) is that the wireless "off" icon looks like autorotate now (see img 1,2,3).

I have also attached the commented line, for everyone who's interested (editing done with solid explorer).

Many thanks for the fix @nvertigo67!
[OnePlus 3 & 3T Cross Device Development] :
Thanx for testing and reporting.

I'd like to see more feedback and longer term testing - I want to avoid strange side-effects before suggesting this to los upstream.

For the icon: that must be something else - though I've no clue what. I've deleted line 6 (and I strongly doubt commenting out makes any difference to deleting):
[OnePlus 3 & 3T Cross Device Development] TheBestPessimist:
the way i see it (since nobody else complained: how did this not bother everyone?!?!!?), if i have any other wireless issues, i'll ping here again. Therefore, if i am silent, you may say that this issue is fixed for me, and nothing else broke.
[OnePlus 3 & 3T Cross Device Development] pedritopl:
And how about that setting from the same file?

Looking at the description only - looks promising as well.

#If set to 0, will not scan DFS channels

gEnableDFSChnlScan=1
[OnePlus 3 & 3T Cross Device Development] :
Tried that. AP is still started on channel 159... I guess the term "scan" refers here to the search of p2p wlans (client mode instead of AP mode).
[OnePlus 3 & 3T Cross Device Development] TheBestPessimist:
Here comes another issue I'm having (haven't you already gotten sick of my complaning?)

I have the following settings:

Ambient display:

- always on: false

- pick-up; hand wave; pocket (pulse notification on removal from pocket): true

Gestures:

- haptic feedback: true

- swipe down with 2 fingers: play/pause music playback

- draw a "<" and ">": previous and next song respectively

(just like OOS has implemented the music controls)

The issue i'm having is that whenever Ambient display is on, Gestures no longer work. I have to wait for the screen to be turned off before attempting to gesture (change track, pause, etc). This is rather bothersome as whenever i take the phone out of the pocket the Ambient display is on, so i cant do anything for like 5 seconds (not sure exactly what the timeout is).
[OnePlus 3 & 3T Cross Device Development] hellcat50:
I have the same problem, but with other rom's as well. I am annoyed too to wait so long for 5ghz network but I guess i just accepted it
[OnePlus 3 & 3T Cross Device Development] knpk13:
I don't think anyone was able to fix that. This was the last message I could find related to the topic.

https://xdaforums.com/oneplus-3/one...velopment/rom-nlos-16-0-t3879405/post78704225
[OnePlus 3 & 3T Cross Device Development] :
I'm not getting sick of issue reports, nor feature requests.

What I really don't like are postings, which demonstrate that the user doesn't like to follow xda rule #1:

https://xdaforums.com/oneplus-3/one...-nlos-16-0-t3879405/post78704225#post78704225 (any help on this will be highly appriciated!)
[OnePlus 3 & 3T Cross Device Development] Siddk007:
I'm really happy with the battery backup of your rom [MENTION=4405529]nvertigo67[/MENTION]

Extremely satified:good:
[OnePlus 3 & 3T Cross Device Development] :
Workaround/hack for the second one (5GHz tethering hotspot is run on high channels my other devices can't see): uncomment line 238 and set it to IL (Israel, most restrictive on chanmels >=100):

gAPCntryCode=IL

With this setting I've a wunderfully working and visible tethering hotspot.
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (wifi channel scan tuning; maintainance)

Build 20190920

Releasenotes:

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

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

Oneplus 3T: OxygenOS 9.0.5 firmware

Oneplus 3: OxygenOS 9.0.5 firmware

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

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

Oneplus 3T: OxygenOS 9.0.5 firmware with 5.0.8 bootloader and keymaster

Oneplus 3: OxygenOS 9.0.5 firmware with 5.0.8 bootloader and keymaster

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

Changelog (Last repo sync: 20 Sep 2019, 10:08:43 CEST / 20 Sep 2019, 08:08:43 UTC):

op3/t: wifi: enable initial scan for DFS channels. — Nvertigo

current.pick.sh: force picking abandoned "pie-msim-ringtones" commits.

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] :
I've just added posting #2, including a flashable zip to accomblish the above.

https://xdaforums.com/oneplus-3/one...-nlos-16-0-t3879405/post78433984#post78433984
[OnePlus 3 & 3T Cross Device Development] vinoxflame:
did you pull back the sound control by flar2, and also the usb fast charge?
[OnePlus 3 & 3T Cross Device Development] :
Read before posting: https://xdaforums.com/showpost.php?p=80230482&postcount=1033
[OnePlus 3 & 3T Cross Device Development] pijas82:
I love this rom, but I hate lineage icons and apps, that's why I stay in aosp ROMs like DU ,nitrogen.

I want see in future nvertigo rom without lineage ?
[OnePlus 3 & 3T Cross Device Development] knpk13:
What do you mean you hate lineage icons? Can't you just use an icon pack to change the icons you want? And apps? Don't AOSP ROMs have the same default apps as lineage?
[OnePlus 3 & 3T Cross Device Development] abhibnl:
This rom is really stable and smooth. But what i dont get is, why the signal indicator is broken or shall I say uncalinbrated? I'm not sure what to call it. Even in locations where I had full signals on oos and usually my colleagues have full bars on same carrier, it shows 50-70% signal. At my hometown, I usually have about 80% bar but in NLOS, I have zero bars all day. I'm just curious if its all right and if it'd have negative impact on battery.
[OnePlus 3 & 3T Cross Device Development] :
It has no impact on bat life. OOS shows the same signal strength with more signal bars. OOS and nlos/los uses the same proprietary, prebuilt ril blobs:

grep ril proprietary-files.txt
etc/permissions/qcrilhook.xml
framework/qcrilhook.jar
-priv-app/qcrilmsgtunnel/qcrilmsgtunnel.apk
vendor/lib64/libril-qc-ltedirectdisc.so
vendor/lib64/libril-qc-qmi-1.so
vendor/lib64/libril-qc-radioconfig.so
vendor/lib64/libril-qcril-hook-oem.so
vendor/lib64/librilqmiservices.so
vendor/lib64/vendor.qti.hardware.radio.qcrilhook@1.0.so
vendor/radio/qcril_database/qcril.db
vendor/radio/qcril_database/upgrade/0_initial.sql
vendor/radio/qcril_database/upgrade/1_version_intro.sql
vendor/radio/qcril_database/upgrade/2_version_add_wps_config.sql
vendor/radio/qcril_database/upgrade/3_version_update_wps_config.sql

See also:

https://xdaforums.com/oneplus-3/one...eplus-3-3t-t3866517/post80010208#post80010208

https://xdaforums.com/oneplus-3/one...eplus-3-3t-t3866517/post80009918#post80009918

https://xdaforums.com/oneplus-3/one...eplus-3-3t-t3866517/post79050134#post79050134

Sidenote: often it's usefull to do a quick search in the official los thread, because we share the same codebase.
[OnePlus 3 & 3T Cross Device Development] djplus:
[MENTION=4405529]nvertigo67[/MENTION] , When i set the battery saver & performance mode to efficiency , the values of cpu do change, but once i reboot the values dont stick inspite the mode is stuck to efficiency. Is is a normal phenomena or is it a bug ?
[OnePlus 3 & 3T Cross Device Development] pijas82:
No
[OnePlus 3 & 3T Cross Device Development] :
Interesting answer for "What do you mean you hate lineage icons?" *lol*

Only quote what you are refering to - otherwise we can't understand what you want to say.

If you don't like the icons and apps of los beased roms, don't use los based roms. nlos-16.0 is los based and I don't plan to change the code base.

For the icons: I like them.

For the apps: without specific explenations (like missing features - preferable with links to the neccessary commits) I can't help you. I like the los apps (besides the few I remove, of course).

What "values" are you talking - you need to be more specific.

I've just tried setting the power save profile (most obvious change: cpu3 is switched offline), as expected after rebooting cpu3 is still offline.
[OnePlus 3 & 3T Cross Device Development] djplus:
Regarding the cpu frequency,

In efficiency mode , the cpu frquencies drop on lower side, but once the phone is rebooted the cpu freq values ramp up to the normal ( balanced ) state inspite the mode is on efficiency.
[OnePlus 3 & 3T Cross Device Development] :
Which sysfs file(s) are you monitoring?

BTW: power profiles are applied after boot completed prop is set. The complete booting process (which is not ended when the lockscreen appears, but when boot completed is set) is run at full speed for various reasons. Also take into account, tjat the power profiles do much more the just lowering freqs.

As already stated: the easiest way to tell if power save profile is applied or not, is checking if cpu3 is online or offline (as long as nat is over 20%).
[OnePlus 3 & 3T Cross Device Development] djplus:
I was just using Franco kernel manager (as well as ex kernel manager sometimes) to monitor the max CPU frequencies.

Edit - I think I am expecting that CPU is under clocked when using efficiency mode (battery settings ). Maybe my assumption is wrong.
[OnePlus 3 & 3T Cross Device Development] abhibnl:
Appreciate the knowledge brother.
[OnePlus 3 & 3T Cross Device Development] :
I know, how this conversation continues:

Me:

When talking about "values", please tell me what exactly you are monitoring and which numbers you read and which numbers you'll expecting. Please look at cpu3, if it's emabled or disabled.

[I'm starting to feel annoyed, that somebody is constantly speking of "values" without giving their exact source and numbers - I really can't understand why somebody would talk on "values" without numbers. Annoyence level is increased by one because I needed to mention cpu3 state as indicator for power save profile a third time. Another increase of two annoyenc levels, because of first time mentioning, the measurement (giving a physicaly measured quality a number) tool a third party tool - which measuring methods may differ from an other third party tool - instead of sysfs files, like I've requested.]

You:

[Start feeling annoyed, because you belive "Regarding the cpu frequency,

In efficiency mode , the cpu frquencies drop on lower side, but once the phone is rebooted the cpu freq values ramp up to the normal ( balanced ) state inspite the mode is on efficiency." is a perfectly good description everybody in the universe can understand, but this nvertigo67 - as good as numbers.]

The numbers from efficiency vs. the numbers from powersave. How to check for cpu3 state.

Me:

I need to know the exact numbers. And please use the sysfs nodes for monitoring, I can't install each and every kernel manager/monitoring/tuning app and verify valid measurement.

For cpu states:

adb shell "ls -la /sys/devices/system/cpu/cpu[0-3]/online"

[I hate begging for information all over again and again. My annoyence level is reachning the end of the scale. I wonder, why I start this ALLWAYS THE SAME conversation. I wonder why I do this: why I answer on vague descriptions? And if doing so, why answering a second time, when it shows, that the repprter is not willing to associate "value", "numbers", "validity" and "reliabiluty"? I know were this leads up too...]

You:

Oh, you mean exact numbers. How should I know that.

[You are confused, why I don't understand your perfectly good issue report. Your annoyence levvel increases. You think, that you've described a valid and for everybody reproducable (reliability) issue; and it's the tesponsibility of the dev to get his ****ing numbers.]

Me:

[No numbers, no cpu3 info. I don't feel annoyed anymore. I'm in desperation on the future of menhood. Some secret society must have invented a slow-motion-for-brains-serum. Why does nobody understand that I need some numbers, logcats, step-by-step-reproduction-descriptions or detailed setup information, to help. Still wondering, why I've continued to answer after the first reply, I bite in my keyboard and start a disrespectful, sarcastic, unpatient and snotty posting...]

I think we stop our conversation before all of the above happens one way or another. I don't mean to offend you, I just want to save our time, dude.
[OnePlus 3 & 3T Cross Device Development] djplus:
I got your point, thanks for your effort !!
[OnePlus 3 & 3T Cross Device Development] BillGoss:
What?! No absolute values for your annoyance levels?

Lol!

I'm at the coffee shop, so my annoyance levels are a cool -5.
[OnePlus 3 & 3T Cross Device Development] :
Test build (AudioFX)

Hopefully this commit fixes AudioFX.

This build has AudioFX readded. Please check if any of the formerly known issues (No sound on calls, media audio stops working after some time, etc.) is still present.

[MENTION=4954690]Siddk007[/MENTION]: You may want to check if the poweramp stuff works with AudioFX included again. If not (honestly, I don't expect this to solve your issue, but who knows), increase the log bufger size to 4 Mio, reboot and try playimg Music with hd applied. Then get a complete log. Perhaps (hopefully) it's something easy to fix like sepolicy or a missimg sysfs node.

The build has no new nlos commits and is symced with los at 23 Sep 2019, 13:24:12 CEST / 23 Sep 2019, 11:24:12 UTC.

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

MD5: https://drive.google.com/open?id=19nNimHVtBAYjkiVI0Wwd9ap7te9Ue9xj

Happy flasing and testing!
[OnePlus 3 & 3T Cross Device Development] Siddk007:
thank you for your efforts. will definitely test and report
[OnePlus 3 & 3T Cross Device Development] Siddk007:
[MENTION=4405529]nvertigo67[/MENTION] dirty flashed latest build and rebooted. Poweramp Hi-Res audio (DirectHD) is now working as it should but now songs are played in 16bit 48Khz instead of 24bit 192Khz:D

update - again i rebooted and now the issue is back to as it was in last build. How to take logs?:silly: