yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] legendavey:
Calm down, buddy. Best to wait patiently until someone answers, a gentle reminder is usually a nice way to bump your question up.

LineageOS has never supported removing the tint from the wallpaper, or hiding the VPN footer on the QS panel. I believe you know of other custom ROMs that offer these features, best to use them if this is important to you. :)
[OnePlus 3 & 3T Cross Device Development] galaxykeks:
I get this:

Did you do anything else?

Edit:

Also going through all packages with Titanium Backup I saw only "Quickstep" as laucher possibility

Edit2:

It is Quickstep. After I froze it with TB. I have the old app switcher.
[OnePlus 3 & 3T Cross Device Development] :
-c from su only takes one string as argument, the next string is taken as new argument. This works:

su -c "pm disable com.android.launcher3"
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I was expecting you to try it for yourself. :)

See the attached screenshots for 1 and 3. The answer to 2 is no.

Note, I've never used wallpaper-need theming.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Oops, forgot the screenshots

Edit: I'm doing really well this morning. I missed the reply from [MENTION=7403273]legendavey[/MENTION] and XDA screwed up the second attachment showing the VPN listing on the QS panel. (Another edit: and now it is showing properly)

I think I'll go back to bed!
[OnePlus 3 & 3T Cross Device Development] enochpc:
Thought I would point out for those of you worried about alarms, I plug my phone in at night and the alarm goes off every morning. I wonder if the people that are having alarm issues don't plug in at night?

EDIT: Might be kernel related as I am running HolyDragon kernel I find my battery life is substandard on stock LOS kernel.
[OnePlus 3 & 3T Cross Device Development] jianwen03:
Sry was trying to make things easier by shrinking 2 lines into 1. Forgot to test it myself. :silly:
[OnePlus 3 & 3T Cross Device Development] michie:
My alarm goes off every morning using stock kernel. I was struggeling with battery life on the previous 2 updates but the latest is superb ?
[OnePlus 3 & 3T Cross Device Development] PlayFriik:
If anyone find himself facing the same crashing issue, then I got it fixed by using QuickSwitch Magisk module which allows you to change the current recents provider (the crash is probably caused by missing recents provider as LineageOS' default launcher is using it by default).
[OnePlus 3 & 3T Cross Device Development] :
ISSUES: manual carrier selectinon & 5GHz SAP in Europe

I found two annoying issues:

If you go to Settings->Network&internet->Mobile network->Advanced and disable "Automatically select network" and get presented the carrier list (after 2 m of searching), the Mobile network setting is crashing, and you find yourself at the Netwok&internet settings page. (carrier-selection.log in issues.zip)

This is especially annoying, because manually forcing a network is the only way to disable voice call roaming: if Network auto selection is in effect, a carrier is autoselected (sic!) if crossing boorders.

If you activate 5GHz SoftAP, it gets fired up, but on channel 5785.

hostapd : wlan0: IEEE 802.11 driver had channel switch: freq=5785, ht=1, offset=1, width=3 (80 MHz), cf1=5775, cf2=0

My carrier is mcc=262 (Germany). In Europe/Germany 5785 is reserved for short range devices, but prohibited for wifi. A European wifi enabled device will never see 5785. (5GHz-ap.log in issues.zip)

This behavior renders 5GHz Hotspot for - at least - all European users pointless.

If setting the country code for wlan incl. SoftAP from the sim's mcc is currently broken, the default should be the definitions of the world regulation domain to be as compatible as possible for all users all over the world.
[OnePlus 3 & 3T Cross Device Development] pedritopl:
deleted
[OnePlus 3 & 3T Cross Device Development] pedritopl:
Note for the manual network selection bug. Maybe it can help narrowing it...

Under similar conditions in 15.1 the example network list looked like on the first screenshot (all networks appear on the list 3 times, not necessarily sorted like on the screenshot).

In 16.0 (second screenshot) each network is only listed once.

From my experience in 15.1 only one of the 3 options for each network worked.

First question to answer is why the networks were listed more than once in 15.1? Was it once per technology (GSM, WCDMA, LTE) or maybe those networks have various MNC (MCC+MNC)?

In 16.0 it seems like the list is filtered and maybe the item left is one of those that didn't work in 15.1?
[OnePlus 3 & 3T Cross Device Development] pedritopl:
BTW: any idea how to select the operator from the terminal on a rooted LOS 16.0? I'm reading that it should be possible using the AT commands (specifically AT+COPS), but I'm having trouble finding how to actually send the AT commands from the terminal.

Some reading I've done: https://xdaforums.com/galaxy-s2/help/how-to-talk-to-modem-commands-t1471241

Edit 1:

I found a way to communicate with the phone via AT commands. Now I "only" need to find out how to change the selected operator ;)

To communicate on OP3T LOS16.0 I had to:

1) switch the "mobile data" SIM in the Settings to the SIM I want to check the settings for

2) in terminal (root):

# cat /dev/smd11 &

# echo -e "AT+COPS?\r" > /dev/smd11

That should return the current operator.

Warning: don't do that if You don't know what You're doing! You could brick your phone by writing to random /dev files and/or sending random AT commands.

Edit 2:

Solved :)

Sending AT+COPS=1,2,"334050" worked in my case :) [MENTION=4405529]nvertigo67[/MENTION] - You might be interested as well :)
[OnePlus 3 & 3T Cross Device Development] pedritopl:
Hi,

I just noticed the same issue.

If I go to Settings -> System -> Status bar -> "System icons" and switch _any_ of the options I get the SIM1 & SIM2 signal strength in the status bar switch places. I mean they switch places every time I change an option there, so if I change two options (or one two times) they're back where they should be, but if I change 1,3,5... times - the signal strength indicators are reversed. It might be difficult to spot if You have good signal strength for both SIMs, but in my case it's obvious as my SIM1 is in roaming and has that little "R" next to it and also "x" showing no data connectivity.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Thanks Bill. I've been using my OP5 for testing. It looks like the Tints are still a thing. Which is weird because they disappeared on the Pixel phones. Another example of Google trolling in AOSP. "Hey, we got rid of those ugly tints y'all hated so much, but only on Pixels. Please buy one."

Luckily the LWP+ App still works the same as it did on Oreo and fixes the Tint.

Shame the VPN jank is still a thing on LOS. Do they think that people who use a VPN 24/7 are just gonna forget that they use one and should have a constant, ugly reminder? Right. That's logical. I turn on my phone, look at the Status Bar and think to myself, "just as well that stupid key icon is there otherwise i might have forgotten that i've been using a VPN based ad-blocker on my phone for two years. It's just as well you remind me every time i look at my phone as otherwise there's no telling what disaster might happen"

Edit: Someone said earlier that LOS never did anything about the Tints. Those of us with better memories remember that they tried to do something about it:

https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/217499/
[OnePlus 3 & 3T Cross Device Development] legendavey:
There's a reason those VPN icons and warnings exist, and that's because not every user is a power user. Also, malicious apps that might set up a VPN connection (or a person that might do it) could do quite a bit of damage if it was running without telling you anything. Blocking ads via VPN like you mentioned is just a small use case scenario, while having an icon (and more importantly, the warning) is very important to know when I'm connected and when I should be reconnecting in case I get disconnected.

This is the same reason why the R icon for roaming exists and why ROMs shouldn't allow users to hide it. Some do, and then run up massive bills and then blame the ROM developers. These features exist for a reason and should ideally never be turned off, especially in the name of cosmetic convenience.

And as for the commit you linked, that was related to the media art on the lockscreen affecting the tint applied, though I could be wrong. However, you could still compile your own personal build with the patches for tint removal and hiding those important messages (look at the patches from other ROMs and try to port them forward) so that you can use these "features" right away. :)
[OnePlus 3 & 3T Cross Device Development] evopen:
Hello. I'm getting this error.

storaged E getDiskStats failed with result NOT_SUPPORTED and size 0

But nothing went wrong.

Thanks.
[OnePlus 3 & 3T Cross Device Development] jerryhou85:
Dear all,

I have remove some posts as they violates our rules. Please do follow our rules when you post and be civil during discussion. Thank you.

Rule refresher:

2.3 Flaming / Lack of respect: XDA is about sharing and this does not involve virtual yelling (flaming) or rudeness. Flaming or posting with a lack of respect is unacceptable. Treat new members in the manner in which you would like to have been treated when you were a new member. When dealing with any member, provide them with guidance, advice and instructions when you can, showing them respect and courtesy. Never post in a demanding, argumentative, disrespectful or self-righteous manner.

Regards

Jerry

Forum Moderator
[OnePlus 3 & 3T Cross Device Development] Red5:
This also made me laugh. :laugh:
[OnePlus 3 & 3T Cross Device Development] evopen:
GPU rendering time is longer in recent builds. I tested 3 los build and get different results.

See attachments. 12-22 12-30 and 1-1. btw, nlos recent builds are ok.
[OnePlus 3 & 3T Cross Device Development] matrixisreal:
This is NLOS 16. it proves SDCLANG does improve the performance
[OnePlus 3 & 3T Cross Device Development] pedritopl:
FYI https://xdaforums.com/oneplus-3/one...opment/rom-skydragon-os-t3858177/post78655119

HolyAngel claims he fixed the WhatsApp video call lagging. The problem is also present in LOS. Maybe someone with enough skills could look at the Skydragon OS sources to see how it has been fixed and port to LOS? :)
[OnePlus 3 & 3T Cross Device Development] :
Without a pointer to the actual fix, a changelog or at least a hint in which project the fix is, this is a tough task you are asking for.

It seems NOT to be in

https://gitlab.com/HolyDragonProject/android_device_oneplus_oneplus3/commits/ndp

https://gitlab.com/HolyDragonProject/android_frameworks_base/commits/ndp

https://gitlab.com/HolyDragonProject/android_frameworks_av/commits/ndp

If you can tell me where to find the fix, I'll check it.
[OnePlus 3 & 3T Cross Device Development] pedritopl:
[MENTION=1211160]HolyAngel[/MENTION] - could You please shed some light on the WhatsApp video call fix, so that we could also benefit from it in LOS based ROMs? :)
[OnePlus 3 & 3T Cross Device Development] kryzeK:
NLOS 16? Where did you find this?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
https://xdaforums.com/oneplus-3/oneplus-3--3t-cross-device-development/rom-nlos-16-0-t3879405
[OnePlus 3 & 3T Cross Device Development] H. K. ROY:
bullet type c isn't working but if i use non-type c headphones with dongle it's working fine. [MENTION=5091734]dianlujitao[/MENTION] can you please look for it?

(fw-oos 5.0.8, los-16-20190101)
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
I don't own such device so can't fix. patches are always welcomed.
[OnePlus 3 & 3T Cross Device Development] DroidFreak32:
Has anyone been able to compile the ROM on macos successfully?
[OnePlus 3 & 3T Cross Device Development] 64ashg:
Wrong thread buddy

https://xdaforums.com/android/general/guide-how-to-build-custom-roms-kernel-t3814251/

And the lineageos wiki how to build page is more than apt in explaining how to do the same last i built my builds (los 14.1)

The above mentioned just might help you out :)
[OnePlus 3 & 3T Cross Device Development] DroidFreak32:
I did check the guide. I can build for my other device but in op3, I get some byteshift header errors. I was able to solve it but not sure if it's the proper fix. Just wanted to verify if others had this problem or if it was just on my end
[OnePlus 3 & 3T Cross Device Development] Mcenzie:
New Build is up

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] 666biker:
works fine? dirty flash after 1.1. release?
[OnePlus 3 & 3T Cross Device Development] detective zero:
No problem!
[OnePlus 3 & 3T Cross Device Development] darthchicken:
I did a dirty flash, and messages still isn't blinking the notification light more than about 3-4 blinks before it stops. I tried uninstalling messages and reinstalling, didn't make a difference, so that fix may require a clean install.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Yep, still not getting any notifications on Messaging. Replacing the APK with the one from 181222 fixes the problem.
[OnePlus 3 & 3T Cross Device Development] kenboyles72:
Yeah, never noticed till mentioned, but the txt notification led is is kinda sporadic. It blinks fine one or two times, then blinks very faint and rapidly a couple times and not in a consistent sequence. I'm not using the stock messaging app, using textra.

Edit: Had a brain fart and flashed the previous build. I downloaded the new build, but didn't transfer it to the phone, lol. The notification led is working like it should now. Was also wondering why AOD wasn't present in the settings, now I know why. Also, for AOD to work properly, you must disable ambient display and AOD, then re-enable for it to work.
[OnePlus 3 & 3T Cross Device Development] jabashque:
I took a look at the Havoc OS op3 device tree and saw this: https://github.com/Havoc-Devices/an...mmit/65be9bf117b22d2e6436445b64cffb12b76049c7

So apparently they just force WhatsApp to use HAL1 camera.
[OnePlus 3 & 3T Cross Device Development] :
Which won't work on los, because los/aosp doesn't handle camera.hal1.packagelist. For havoc the additional handling of camera.hal1.packagelist is here (at least - maybe there are more commits in other projects):

https://github.com/Havoc-OS/android...558678d#diff-925034363271b2b3a8a0750a8c76504e

which needs addiionally:

https://github.com/Havoc-OS/android...b8c63e4#diff-925034363271b2b3a8a0750a8c76504e

[MENTION=5091734]dianlujitao[/MENTION]: I guess we won't get this oneplus specific additions merged in los?

EDIT:

the oneplus commits relay on even more commits. This would be needed - again: at least:

https://github.com/Havoc-OS/android...df1446d#diff-925034363271b2b3a8a0750a8c76504e

EDIT2:

https://source.codeaurora.org/quic/...0&id=27b661ad0a3ba4c759e29a9651afc25cb6c33df2 should work for us.

EDIT3:

https://github.com/nvertigo/android_frameworks_av/commit/4b16bd7568a152bfc997ef85bf71479fc7a557fd should do something similar, with the same result for whatsapp, but without the need of carrying a list in build.prop. I would opt for merging this, because no additional props are needed.
[OnePlus 3 & 3T Cross Device Development] CodesCodger:
I don't think it's going to be merged on los. Since it might break things for other devices.

Edit: was talking about havoc commits.
[OnePlus 3 & 3T Cross Device Development] :
That's what I guess.

[MENTION=5091734]dianlujitao[/MENTION]:

I prepared a commit for 15.1 and 16.0:

https://github.com/nvertigo/android_frameworks_av/commit/26ecf86a382cbacd7ff0aa23fb1fd22e6fa3a7cd

https://github.com/nvertigo/android_frameworks_av/commit/eca9ac656aefe71298094e2a8349802d53842e92

Drop me a note, if it makes sense to push them to gerrit.
[OnePlus 3 & 3T Cross Device Development] ayysir:
anyone having quick battery drain using this rom?
[OnePlus 3 & 3T Cross Device Development] legendavey:
Nope. Battery life is pretty decent, tbh. Try clean flashing the latest build with 5.0.7 firmware. :)
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
I pushed the package list commit to gerrit instead, please test while you're at it. btw do we need to add more packages to that list?
[OnePlus 3 & 3T Cross Device Development] :
If I remember correctly: hangouts (don't know if it has been fixed, or nobody is using it anymore), some oneplus cam mods and two chatting apps, I've never heard of before (and therefor can't remember the names). Currently reported by users on P roms there's only whatsapp left, to my knowledge.
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
Can you try this build and give feedback? https://androidfilehost.com/?fid=11410963190603900981
[OnePlus 3 & 3T Cross Device Development] pedritopl:
Hi, sorry, can't flash LOS-16.0 right now. I'm currently on NLOS-16.0 and the fix provided by nvertigo67 did work for me.

https://xdaforums.com/oneplus-3/one...velopment/rom-nlos-16-0-t3879405/post78673202
[OnePlus 3 & 3T Cross Device Development] legendavey:
This build fixes the WhatsApp video call lag for me. But tbh, it never was that noticeable even on previous builds.

Oh well, if it was present before, it doesn't seem to be happening now. Thanks for the fix! :)
[OnePlus 3 & 3T Cross Device Development] enochpc:
I have to use HolyDragon kernel to get decent battery life, but others don't seem to have those issues. I honestly haven't tried not flashing the last few builds without flashing HolyDragon so might not be an issue now but if you have battery issues give the kernel a try.
[OnePlus 3 & 3T Cross Device Development] knpk13:
That's what I thought initially, that it was fine before. But once I tried a build that fixed the lag, I immediately noticed the difference. It was significant.
[OnePlus 3 & 3T Cross Device Development] legendavey:
How has battery life on the Jan 15 build been like for you? Feels like it has reduced *considerably* on my end. Perhaps time for a clean flash. :)
[OnePlus 3 & 3T Cross Device Development] knpk13:
I'm on NLOS so can't comment :P

I believe it got the same fix for WhatsApp that LOS did
[OnePlus 3 & 3T Cross Device Development] growlygoof:
HDK + LOS 16 = bad batterry backup bro.. Dnt flash it..
[OnePlus 3 & 3T Cross Device Development] :
Maybe somebody can help me with this:

https://xdaforums.com/oneplus-3/one...-nlos-16-0-t3879405/post78704225#post78704225
[OnePlus 3 & 3T Cross Device Development] kenboyles72:
With only 5 posts on this board, don't think you qualify to give advice and your advice is far from the truth. If you are having issues, it may be an error on your part. I have been running HolyDragon for a long time now and have zero issues and battery life is excellent. I average 0.7% drop per hour and my battery usually lasts me 4 days and around 3 hrs SOT.
[OnePlus 3 & 3T Cross Device Development] matrixisreal:
from NLOS 16

https://mega.nz/#!JspjEQLD!49NmxpCssbTnUaPD3TNQT9RfkNVrUf3ry7LNnHSMrnI
[OnePlus 3 & 3T Cross Device Development] H. K. ROY:
flashing the 5.0.8 firmware fixed the issue or a dirty flash on top of oos 5.0.8 full zip
[OnePlus 3 & 3T Cross Device Development] pedritopl:
Hi. [MENTION=5091734]dianlujitao[/MENTION] - please add Camscanner app to the list as well. I tested it, and there's a huge difference in photo quality with default setup and when the app is forced to use HAL1. Please see the difference on the pictures attached to my post in NLOS thread:

https://xdaforums.com/oneplus-3/one...velopment/rom-nlos-16-0-t3879405/post78712050

I'm using NLOS-16.0 where this was fixed with a "generic" approach (the first patch proposed by nvertigo67), but I'm sure that LOS-16.0 users who also use CamScanner app would also like to have it fixed :)

CamScanner = com.intsig.camscanner
[OnePlus 3 & 3T Cross Device Development] legendavey:
Nice find! Perhaps apps like Instagram which usually take low quality pictures could be tackled with the same approach, if they have the same HAL1 issue. ?

Edit: com.instagram.android is the package name, if anyone wants to test
[OnePlus 3 & 3T Cross Device Development] Mr.Jay:
Found one issue that I had too on Pixel Experience Pie, so I'm guessing it's an Android Pie issue more than a ROM issue.

When I'm using the phone and the battery level gets under 15%, the phone turns the interface into dark mode and due to that it's like the whole system UI restarts and no matter what app are you using, it will be closed and your work gone. This is especially annoying while playing online games that you can't pause at your will.

Enviado desde mi ONEPLUS A3003 mediante Tapatalk
[OnePlus 3 & 3T Cross Device Development] simthadim:
Very battery friendly on idle (about 0.5% per hour, perhaps little less on my set-up: no WiFi, no Data, no Gapps).

While screen is on, battery will drain as fast as any other ROM I tried (Lineage 14, SultanXDA's version, AOSPA).

Only thing that makes me consider switching ROM is the fact that I can't get signature spoofing to work (used Tingle by Ale500 on LOS14, for MicroG). Other then that this ROM is a keeper for me.
[OnePlus 3 & 3T Cross Device Development] ivanich:
Hey [MENTION=5091734]dianlujitao[/MENTION] , looks like old bug is came back https://xdaforums.com/showpost.php?p=75837317&postcount=1069

EDIT:

Caused by https://github.com/LineageOS/androi...mmit/e973896cc44991b891768bed789bef9588f1f930

Just a suggestion - avoid to use commits from Sultan, most of them untested and create more problems than they solve.
[OnePlus 3 & 3T Cross Device Development] abhibnl:
This comment was oddly disrespectful towards Sultan's work. If his work was untested, then hundreds of users would have same issues which clearly they didn't have. You can go and read the whole thread from start to end. If anything, he was the only person in OP3 forums who actually brought some actual original work to this device (another example is [MENTION=4898097]arter97[/MENTION] but we don't deserve him for this device anyway considering the user base). We respect developers here for their contribution and work without getting paid (donations don't count, they are voluntary). Just my 2 cents.

P.S. What I can agree on is that sultan has dropped OP3 after Nougat so his work maybe Semi or non-compatible with Oreo and Pie ROMs :)
[OnePlus 3 & 3T Cross Device Development] ivanich:
I worked with Sultan a few years ago (good old cyanogenmod times) on another Android device so I know what I'm talking about. It's just a fact that if you have a dozen of Sultan's commits and some exotic bugs appears the first thing is to start reverting his commits one by one.
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
You're right, he has many breaking commits but on the other side he's actively cleaning up op's garbage code, fixing upstream bugs and doing various experiments to improve perf. It's my fault forgetting to drop that commit during rebase.
[OnePlus 3 & 3T Cross Device Development] abhibnl:
Again, I'm not a developer but i think his own rom/kernel combo was tweaked for his changes maybe? All I would guess is, his work maybe obsolete at this point for these new Android versions. But my experience with his rom/kernel combo in the past has been nothing but awesome
[OnePlus 3 & 3T Cross Device Development] CodesCodger:
Speaking of [MENTION=4898097]arter97[/MENTION]. It feels sad that aospa dropped oneplus 3/T. AOSPA nougat was a great rom and on the contrary people all over the community are picking up sultan's stuff randomly and they do break time to time.

---------- Post added at 09:58 PM ---------- Previous post was at 09:57 PM ----------

Sultan is still working on op stuff? I thought he moved to pixel since pixel has a clean code base