yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] FlyingHelix:
Hello,

i have problems with root in this Rom. I am on the latest version, although I have the problem since the beginning of this ROM, and I am on the latest magisk versions. The recovery is twrp SAR and I also tried the lineageOS recovery (latest version).

The problem is, I can't modify system files from apps. In the recovery with twrp its no problem, like deleting, but with SD maid, root explorer and such I have no luck. Magisk module installation works as far as I can tell, but no root access in apps, they say it's write protected. I'd like to delete unwanted system apps where I use alternatives and change some settings, but no app I use is able to do so.

I tried clean flashes, different recoveries, looking for options in the developer options, and the apps also say they have root, but still can't change anything. They have the storage permissions and in magisk manager they also appear to have root.

Anyone having the same problem or knows how to fix that?

Thanks in advance already!
[OnePlus 3 & 3T Cross Device Development] CHAO5:
My encrypted OnePlus 3 is stuck in a reboot loop after I attempted to upgrade from lineage-17.1-20200423-nightly (official) to a more recent official version from https://download.lineageos.org/oneplus3. I even tried to re-install the same (lineage-17.1-20200423-nightly) that was working before and it's still not booting correctly.

Do you guys have any idea what the problem might be? I don't want to end up doing a clean flash for every single upgrade.

TWRP: 3.3.1-20200107
[OnePlus 3 & 3T Cross Device Development] thesplitter:
Disable mobile data on one sim and enable it on the other sim
[OnePlus 3 & 3T Cross Device Development] nucleerz:
check this out: https://www.reddit.com/r/LineageOS/...st_current/?utm_source=share&utm_medium=web2x

---------- Post added 3rd June 2020 at 12:07 AM ---------- Previous post was 2nd June 2020 at 11:54 PM ----------

It's been answered before in this thread. It seems that encrypted and using TWRP, if update through the OS Update is used, the update will fail and a boot loop will happen. I just download the nightly zip and update through the special TWRP listed on the first post. A thread search will yield your answer.
[OnePlus 3 & 3T Cross Device Development] knpk13:
That's weird, but I managed to grab logs because this happened on my OP2 as well and reported it to [MENTION=2010892]Nezorflame[/MENTION] in the opengapps thread. Hopefully we'll hear from them soon, so follow that thread for updates.

https://xdaforums.com/android/software/pa-gapps-continuation-t3098071/post82702117
[OnePlus 3 & 3T Cross Device Development] rohan164:
After flashing ota's buildprop settings will change again?

---------- Post added at 04:29 AM ---------- Previous post was at 04:28 AM ----------

Hello

After flashing ota, buildprop settings will change again?
[OnePlus 3 & 3T Cross Device Development] sobhan06:
Lineage does not show a direct option to toggle the Data from one network to another neetwork. You have to go into the selected and toggle the Mobile data where it will show a pop-up like rohan164 has shown.
[OnePlus 3 & 3T Cross Device Development] mukesh.mac:
I am not able to find the process how to toggle can you pls share screen shot or link where incan find the same.
[OnePlus 3 & 3T Cross Device Development] saspipi:
No, it's not "not as good"... For many of us GPS is just practically unusable as reported here too.
[OnePlus 3 & 3T Cross Device Development] :
Yes, build.prop is part of system en replaced on flash.

As I remember correctly you could make a script which is placed in addon.d which adds the needed lines, though not 100 percent sure if this is executed on reboot after OTA.
[OnePlus 3 & 3T Cross Device Development] :
addon.d is handled by twrp while flashing. If you use Magisk you can see when it's executed (Magisk addon.d script has an output to the twrp console; gapps doesn't produce output). addon.d scripts arn't executed on rom boots.

BTW:
[MENTION=5996692]rohan164[/MENTION]: please help keeping the thread readable and searchable. Edit you posting: reduce the quoting to what you are refering to. Your quoting just demonstrates bad manners!
[OnePlus 3 & 3T Cross Device Development] emrekasikara:
Pixel Launcher has stopped working after latest nightly update released on June 2, 2020.

Recent Apps capacitive button also not working
[OnePlus 3 & 3T Cross Device Development] emrekasikara:
i have clean flashed the latest build and the problems solved but restoring all apps were a bit time consuming
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Have a look at https://xdaforums.com/android/apps-games/app-migrate-custom-rom-migration-tool-t3862763
[OnePlus 3 & 3T Cross Device Development] Sudhangshu:
So do you clean flash every time there's an update?
[OnePlus 3 & 3T Cross Device Development] emrekasikara:
not all the time. this update created problems and i have clean flashed it.

---------- Post added at 08:50 PM ---------- Previous post was at 08:48 PM ----------

i am restoring the apps from google backups instead. migrate app or google backup, doesn't matter which one, both of them are time consuming because there are many apps that i need to re-register.
[OnePlus 3 & 3T Cross Device Development] Cullub:
Yep, just tried to make sure. Turned the screen off, the AOD turned on (the built-in one in LOS, not a third party app), I double tapped, and the screen turned on. Note that I have the Display > Advanced> Tap to Wake toggle enabled. I'm on a OnePlus 3T. I don't have the tap to sleep setting turned on

---------- Post added at 05:57 PM ---------- Previous post was at 05:53 PM ----------

App pinning is messed up for me. I can pin an app from the recents screen (tap app icon and select Pin), but unpinning doesn't work. I have to restart the device. Also tapping the Emergency icon from the power menu does nothing while pinned. Can anyone confirm this or is it just me?
[OnePlus 3 & 3T Cross Device Development] thesplitter:
Many secure app are tied to the device ID and that resets on every format :(
[OnePlus 3 & 3T Cross Device Development] ZZZOOONNNTTT:
It also worked for me, BUT ONCE, then again the gesture did not work if you did not unlock the phone.

For example: I’m blocking the phone, (the AOD turns on), double tap, and the screen turns on. Then I turn off the screen again (DO NOT UNLOCK) and the double tap no longer works until you unlock the phone! That is, a double tap works with the AOD turned on Once! Are you sure that your double tap works constantly? Several times in a row? (it’s just really hard for me to reflash and set up the phone)
[OnePlus 3 & 3T Cross Device Development] Cullub:
Oh I guess you're right there - multiple times seems to have a problem here too. Huh.
[OnePlus 3 & 3T Cross Device Development] LorBer13:
I confirm the quick settings problem... I think in the 20/11 build it had been fixed because I am not facing it anymore.
[OnePlus 3 & 3T Cross Device Development] Angel Cubero:
Mod edit - Translated by https://www.deepl.com/translator:

I can't install the rom on my device

*************************************

no puedo instalar la rom en mi dispositivo
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Without details of any errors you're getting and the process you followed to install the rom, we can't possibly help you.
[OnePlus 3 & 3T Cross Device Development] Oswald Boelcke:
XDA Forum Rules (excerpt):
[OnePlus 3 & 3T Cross Device Development] felixchris:
Yeah I guess the Vulcan graphics fix could have something to do with that. For me it's also fixed. :good:

What about NFC?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I find that NFC toggles on/off properly and recognises another NFC device (eg a credit card) but I can't get a Google Pay transaction to work - the phone isn't recognised by the terminal.

And it's not a Gapps issue because Google Pay with the same Gapps works on NOS.
[OnePlus 3 & 3T Cross Device Development] felixchris:
Did try it today again same experience. It'll register other nfc devices but Gpay won't work.

Can we help with logs somehow?
[OnePlus 3 & 3T Cross Device Development] bfm.95:
Battery percentage not showing even when I choose option next to icon
[OnePlus 3 & 3T Cross Device Development] Oblias:
I'd like to get confirmation on the fact that I can install this rom without having to decrypt my OnePlus 3T.

I read what [MENTION=2911853]BillGoss[/MENTION] wrote a couple pages back, that he was able to boot without being decrypted, but then I've also read after that where a couple of people have had to format their Data (Internal Storage or /sdcard/ whatever you want to call it) to get this rom working .

So, can someone confirm for me, one way or the other, if I need to decrypt my phone (like all the other Android Q roms require) before installing this rom?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Simple: don't decrypt your phone. Do a clean install of Los 17. If it boots up your good to go. If it doesn't then just restore your backup of the previous rom.
[OnePlus 3 & 3T Cross Device Development] Oblias:
I appreciate your fast reply, Bill! But my way of thinking, that's not really a black and white answer, wouldn't you agree? Shouldn't the answer to my question (and that of most newbies to this rom) be a 'yes' or 'no' ??

I'm trying to 'read between the lines' in your answer, and what I'm getting is that maybe one has to decrypt, and maybe one doesn't have to decrypt to install this rom. Would that be close to being right, and that there is no black or white answer?
[OnePlus 3 & 3T Cross Device Development] :
If your data partition is encrypted, it gets decrypted on every boot. Decrypting is making an encrypted piece of information readable again. You can't decrypt by formating! You can only remove the complete content of the data partition - including the encryption information - by formating, resulting in an unencrypted data partition. Using "decrypting" in the meaning of "removing encryption" doesn't make sense and will lead to misunderstandings.
[OnePlus 3 & 3T Cross Device Development] Viper The Ripper:
Encryption is supported as reported before...

You do NOT! need to format data in order to get it working, so flash it as always
[OnePlus 3 & 3T Cross Device Development] Oblias:
Outstanding! Finally, I have found a Q rom that can just be flashed. This has to be the only Q rom for the OnePlus 3T that can be installed this way. Makes me wonder why all the others aren't like this also......

---------- Post added at 05:08 AM ---------- Previous post was at 05:07 AM ----------

Understood. I was following the syntax used by Bill, in order to make the 'conversation' contiguous. I think most understand the implied meaning of the word, as used within this thread.
[OnePlus 3 & 3T Cross Device Development] Viper The Ripper:
It has been reported to work in the Unofficial PixelExperience Q too, as it's using LOS17 as base
[OnePlus 3 & 3T Cross Device Development] gaizkaxda:
Does anyone can get 1080p 60 fps videos with any cam app available?

I tried many GCam ports but videos are choppy and not fluid.

Oneplus 3
[OnePlus 3 & 3T Cross Device Development] Botzer:
Nano is buggy on LineageOS.
[OnePlus 3 & 3T Cross Device Development] rohan164:
Dark theme sunrise to sunset is not working for me. (Auto)

I have to manually enable dark theme at sunset and disable dark theme at sunrise.

Does anybody know what could be the issue?
[OnePlus 3 & 3T Cross Device Development] :
Woukd you like to give more details, please?

What bugs are you talkimg about?

Is every gapp version effected or only some? Which exactly?

Can you provide more details on your setup and logs from the bugs, please?
[OnePlus 3 & 3T Cross Device Development] MeTheFlea:
Double tap to wake doesn't seem to work for me while the ambient display is showing.

After some testing it looks like it works as expected if it's set to always on, but not when it turns on via pickup or handwave, can anyone else reproduce?
[OnePlus 3 & 3T Cross Device Development] knpk13:
Not sure what he's referring to, but this is the only bug (getting past through voice match in system setup on a clean flash) I've been experiencing with gapps for the past few months on my 3T (I've always used nano). On my OP2, I had trouble installing apps from the play store in addition to the voice match bug. Please check the quoted posts in the links for reports by other people, details, and logs.

https://xdaforums.com/android/software/pa-gapps-continuation-t3098071/post82159535

https://xdaforums.com/oneplus-3/one...ageos-17-0-oneplus-3-3t-t3990061/post82732363
[OnePlus 3 & 3T Cross Device Development] counterfeit187:
I don't clean flash, but I wipe the system folder and then flash the ROM and the gapps. This prevents the issues with the app switcher not working.

This is not a clean flash because I do not wipe the data folder, and then I do not have to reinstall my apps or fix settings.
[OnePlus 3 & 3T Cross Device Development] Botzer:
https://xdaforums.com/showpost.php?p=82702117&postcount=6685 (exactly the same issue)

https://xdaforums.com/showpost.php?p=82723925&postcount=6687

https://xdaforums.com/showpost.php?p=82745111&postcount=6696
[OnePlus 3 & 3T Cross Device Development] :
Obviously we disagree on detailed information needed to hunt this down... My fault. I shouldn't have asked in the first place.

BTW: From the original posting I've understood that only the nano package is buggy but not the other sizes.
[OnePlus 3 & 3T Cross Device Development] Muralidharc22:
Does mentod work to switch between 2 different ROMs by just wiping cache,dalvick cache and system?
[OnePlus 3 & 3T Cross Device Development] gamernabby:
Clean installed Lineage OS 17.1(June 3) with OpenGapps on my OnePlus 3T & not rooted.

Pressing call record icon on call screen displays "Failed to start call recording".

Tried clearing cache and data, rebooting and even fresh installation of Lineage OS but still getting 'failed to start call recording'.

Any workaround?

Also, signal strength seems to be much feeble than stock OOS. As I am using this phone as my daily it's difficult to live with feeble signal strength.

Otherwise this version of Lineage OS is so fabulous, I really felt sad rolling back to stock OS.
[OnePlus 3 & 3T Cross Device Development] pro_drive:
Yes I go back to OOS for daily use after trying LOS17.1 for a month.
[OnePlus 3 & 3T Cross Device Development] aaronautical:
I am having the same issue on 20200604. Also, the notifications for the current alarm and upcoming alarms trigger a notification sound.
[OnePlus 3 & 3T Cross Device Development] knpk13:
What do you mean? My post links to a detailed description and logs.

I have only tested nano.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Problem: The Files app is showing a number of files (all 0 bytes) in Downloads that don't actually exist in /sdcard/Download (as seen by using a file manager - Solid Explorer - or using 'ls -la' in terminal or browsing the device and selecting the Download folder in Files).

Selecting these files and deleting them in Files doesn't delete the files and gives a notification that the files couldn't be deleted.

Additionally, if I try to download one of these files using Chrome I'm asked if I want to download the file again, indicating that the Downloads app also knows about these files.

Actions I've performed: I've cleared the storage of Files, Downloads, and Download Manager, but it makes no difference.

Question: where is Files getting the list of files in Downloads from? It's clearly not just a list of files in /sdcard/Download.
[OnePlus 3 & 3T Cross Device Development] christantoan:
AFAIK if you go directly to Downloads in Files instead of Root_Storage/Downloads, it will list file you have downloaded through cached Media Storage. Try clearing data from Media Storage and reboot so it does a rescan.

EDIT: Changed 'or' -> 'and'
[OnePlus 3 & 3T Cross Device Development] BillGoss:
That's it! The Media Store database /data/data/com.android.providers.media/databases/external.db seems to hold a complete list of all files on /sdcard including some obsolete files. I cleared the storage of Media Store and rebooted the phone. Now Files>Downloads is showing the correct information.
[OnePlus 3 & 3T Cross Device Development] rohan164:
Please disable the default clock app using adb commands and download google clock app

Works flawlessly

---------- Post added at 08:39 AM ---------- Previous post was at 08:36 AM ----------

Signal strength is not as OOS, but works fine there is no call drop.

For call recording use boldbest call recorder works flawlessly.

Native call recorder doesn't work.

I use boldbest call recorder whenever i want to record any call.

Otherwise it is greenified using greenify app
[OnePlus 3 & 3T Cross Device Development] gamernabby:
I was looking for some workaround for native call recorder. I do not want to use third party call recorder,even though I purchased a few, none worked well as the native call recorder.

Call recorder was fine on Lineage OS 16.

And signal strength, it's not good either, its almost 1/3rd of what I get on OOS. Talking about Call drops, I wasn't able to make calls from the same place I used to make 'HD' calls.

Apart from these few quirks,I feel, Lineage OS 17.1 is much better than stock OS.
[OnePlus 3 & 3T Cross Device Development] :
Signal Strength

As explained really many times and should be well known: the signal bars differ from oos to los, since los uses aosp translation from dbm/asu to bars and oos is using a [euphemism]more friendly[/euphemism] translation. If you want to compare oos signal strength to los signal strength never ever use the bars but the dbm/asu values - comparing the bars is well known to be nonsense.
[OnePlus 3 & 3T Cross Device Development] rohan164:
[MENTION=4405529]nvertigo67[/MENTION]

Can you please through some lights on native call recorder.

Well i too did not found any work arround for native call recorder. I searched whole thread. May be it is yet to be fixed.

May be some senior members can answer this.

Regarding native call recorder.
[OnePlus 3 & 3T Cross Device Development] gamernabby:
Understood.

But I think inability to initiate a call in Lineage OS at the same place where a clear call can be initiated in OOS justifies the comparison??

I'll definitely post comparative dbm/asu values here whenever I get back to Lineage OS.
[OnePlus 3 & 3T Cross Device Development] :
Absolutly. But to narrow this down (pitty user, who decides to do so) it's important to check if this is a general issue, or if only some usecases are effected - and a general "me too" to the general statement "signal strength on loss is less then on oos" is no help to find the pattern if it's not a general problem...
[OnePlus 3 & 3T Cross Device Development] aaronautical:
Thanks, but I am not looking for a work-around. I am running gapp-less and prefer not to install the google clock app. I installed a previous build where the clock still works as desired. This bug was introduced at some point in the past month while the build servers where down.
[OnePlus 3 & 3T Cross Device Development] gamernabby:
I did not understand your response. I don't know how many users are facing similar issue neither I asked/requested for resolution of the same.

My main concern was native call recorder which,at this point of time, I am unable to use and research didn't returned any resolution.
[OnePlus 3 & 3T Cross Device Development] _Thomie_:
Hi,

I want to install Lineago OS 17.1 on my OP3 but it is encrypted (dm-verity).

Is this a problem or can i just flash TWRP with Odin and then flash LineagoOS and Gapps?

The recommended link for TWRP in the first post isn't available anymore.

Can I just download the newest one from dl.twrp.me/oneplus3/

or is there a new link?
[OnePlus 3 & 3T Cross Device Development] :
Please understand that begging for information is the most annoying task related to android I've expirienced since starting to post on xda. This is so frustrating, that I've decided not to beg for information and logs. Sometimes I violate this rule, just to find that if I do so, a dialog starts off making me to write KBs of explanations ending up with answers like "I get the logs next time" or "the logs are in xyz-device's thread" or other sh!t.

This teaches me the hard way to stick with my rule: don't beg for imformation - only start answering if all information is in place.

No offense meant to anybody. It's just I've to protect myself from the way xda threads have changed.

---------- Post added at 20:35 ---------- Previous post was at 20:32 ----------

Don't mix topics: verity bit is tripped by an unlocked bootloader and doesn't relate to userdata encryption.
[OnePlus 3 & 3T Cross Device Development] _Thomie_:
Ok, if I wipe the memory, cache etc to flash Lineage encryption shouldn't be a problem but can I install TWRP and flash Lineage without trigger verity?
[OnePlus 3 & 3T Cross Device Development] sobhan06:
Hi guys, When a call is missed, it is not showing in the main screen notification or while waking up the screen. Anyone else facing this issue? I do not find any option in settings specifically for this.
[OnePlus 3 & 3T Cross Device Development] :
That's a very good way of hunting down bugs, which is actually the main purpose of XDA; helping the dev's to make their product even better ;)

Btw, I am using the guide line this post as help for getting logs.

You should have enabled adb in developer settings ofcourse and logging must not be disabled in any way (default logging is on, so no issue when you did not disable it).

--------------------------

Enclosed my log;

8.10 Alarm set two minutes back, connected to pc, flip case open, screen off; Alarm is working normal and popping up;

8:15 Alarm set three minutes back, connected to pc, flip case closed, screen off; Alarm is working normal and NOT popping up after opening flip case;

alarm-issue1.txt is made with adb logcat -v long > alarm-issue1.txt

alarm-issue2.txt is made with adb logcat > alarm-issue2.txt

Because I read the post above also where a missed call is not popping up, I have the feeling it is not related to alarm only though...

Please let me know if more info is needed to track down the issue.

.
[OnePlus 3 & 3T Cross Device Development] Yudh:
Dev please add

Back button customisation in buttons section so we can customize back button long press & back button double tap

Also i encountered a bug that button backlight isn't working .

I don't use it button i like to report it
[OnePlus 3 & 3T Cross Device Development] :
You need to lock the bootloader. This has been discussed many times in this thread and the los16 thread. Always search/read the thread before posting, please.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
And for me, an expresso without sugar and two croissants... what else ?
[OnePlus 3 & 3T Cross Device Development] Yudh:
Come at my place i will ;)

I mentioned these things because in pie rom they were available in Lineageos
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Take a look here regularly : https://review.lineageos.org/q/project:LineageOS/android_frameworks_base+branch:lineage-17.1

As reminder : Do not ask for features to be added ... The LOS team does not accept feature requests. If you want to implement a new feature, the LOS team accepts patches through gerrit at http://review.lineageos.org.
[OnePlus 3 & 3T Cross Device Development] :
Do I guess correctly that "popping up" means the deskclock page showing the dialog to snooze/disable the alarm? The other mentioned issue (missed calls arn't shown in notifications) is about notifications. I think these are two different issues.

Anyway: I can't find anythng in your log. In both cases the intent for deskclocks alarm service is started, and I can't see a reason why it's not shown in tje second case. Mayby some race in deskclock, flip cover handling and keyguard, but I don't see something in the logs giving a hint.