yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] suolrihm:
Okay. Backup the files of your phone to your PC.

Open a Terminal Emulator (Linux) or cmd.exe/PowerShell (Windows). Boot into fastboot mode and type in

1. fastboot format userdata

2. fastboot format cache

3. fastboot format system

4. fastboot erase boot

Reboot into fastboot and flash again TWRP, now restart into TWRP, go to wipe, select format and type yes. Restart your phone again into recovery, wipe everything (cache, dalvik, system..., except USB-OTG), restart again and flash LineageOS and if needed Gapps.

So basicly clean flash. This way, atleast the full storage should be useable again. Keep in mind that this storage deletes every data on you saved on your phone.

You could try to restore the Backup again after this, maybe it works. Like i said in the first place, i haven't made this expirience atleast with TWRP Backups yet

I guess the F2FS stuff is still broken in TWRP. The best thing for those who want to use F2FS is to revert back to Stock (iirc OOS used it, don't know if this is still the case with recent releases) or use Arter's TWRP release to format to F2FS, some say he is the only one who managed to properly implement F2FS into TWRP
[OnePlus 3 & 3T Cross Device Development] Uumas:
Oh, I think you're right. I had this same problem a while back and had to run the command from TWRP terminal. Iirc the built-in format uses some argument that doesn't exist (maybe -p) but I just ran the same command without it and it worked.
[OnePlus 3 & 3T Cross Device Development] Playa82:
Then all in ext4 ?
[OnePlus 3 & 3T Cross Device Development] suolrihm:
Yes. Until the day F2FS is completly fixed i would recommend ext4. If you really want to use F2FS, in my last reply are two ways how you can use it
[OnePlus 3 & 3T Cross Device Development] Uumas:
My phone's internal microphone isn't working. It works after clean flash but once I've setup the phone it no longer does. Headphone mic works fine. Could someone give some direction on how to debug this. I tried taking a logcat but at least I can't find anything relevant in it.
[OnePlus 3 & 3T Cross Device Development] Playa82:
ok guys. format was the key to success. thanks everbody for helping me.
[OnePlus 3 & 3T Cross Device Development] :
A clean flash should solve this.

If you want to know, what's filling up your data partition, use du and sort (root via adb is needed) to find the largest file on /data:

oneplus3 / # du -sm /data/*|sort -nr|head -1
23111 /data/media
oneplus3 / # du -sm /data/media/*|sort -nr|head -1
22992 /data/media/0
oneplus3 / # du -sm /data/media/0/*|sort -nr|head -1
13760 /data/media/0/Download
oneplus3 / # du -sm /data/media/0/Download/*|sort -nr|head -1
542 /data/media/0/Download/nlos-15.1-20180720_081313-beta-oneplus3t.zip
oneplus3 / #

The "head -1" is to limit the oitput to the first item of the list. You can change the number of lines or drop the "head" at all. If you are descending the file system tree, you can also see large directories (in the above example you can see that much more then the half of /data/media's data lives in /data/media/0/Download).

If doing this from time to time, you will be surprised what unswd files you see... ;)

BTW: complete usage of mounted fses can be obtained with "df".

---------- Post added at 14:32 ---------- Previous post was at 14:27 ----------

What do you mean by "setup"? Just setting up the device to your preferences, or restoring/installing apps and mods? If it's the first, just check the mic after every setting; if it's the latter, just do it step by step and not all together - check every time which mod/app is breaking the phone.
[OnePlus 3 & 3T Cross Device Development] Playa82:
See my post above yours. formatting was the solution. now i got around 33 gb free space. thanks for helping me out.
[OnePlus 3 & 3T Cross Device Development] Uumas:
Installing all apps, setting up Google accounts, logging in to apps... The weird thing is I don't recall doing anything that could possibly cause mic to break.

I was hoping there would be some log or something where I could check what's causing the issue rather than doing everything all over again...
[OnePlus 3 & 3T Cross Device Development] :
Side effects can be *****es... Honestly, I've hoped "mod" would ring a bell. (I suspected a sound enhancing mod.)

Are you using the buildin dialer, or the google one? (Some opengapps packages - larger then nano and pico - replace the Dialer.apk)

Do you use an music app with soumd enhancements?

Fot the logcat: I would look at the beginning after a reboot - the important line may be in the initializing, not neccessarily where the call takes place. The device of the speaker you hold to your ear is a different one, then that one, which is used for handsfree... If you check with alsamixer, there are a lot of audio output devices... You could try calling the time service (or some other service, someone is always talking at) and while the call is active start playing with alsamixer...

And don't forget the upside: you have already excluded an hardware failure.

Good luck!
[OnePlus 3 & 3T Cross Device Development] Uumas:
Google dialer courtesy of OpenGapps stock, no sound enhancements (other than AudioFX) This also happens when trying to use Google Assistant or Shazam, so it can't be a dialer problem.

Thanks for the tips. I'll start debugging [emoji1][emoji849]
[OnePlus 3 & 3T Cross Device Development] Dirk:
Point of interest Uumas:

https://xdaforums.com/showpost.php?p=77125696&postcount=868

Are you using OB30 Firmware? That post is suggestive of a possible issue there. I feel like i've seen a few of these posts recently. Speaker/Microphone issues. I'll update this if i find another.

Also OpenGapps 'Stock' Package is rather large and not recommended on Custom ROMs.
[OnePlus 3 & 3T Cross Device Development] Uumas:
I'm using 5.0.3 firmware. Will try OB but I don't think it makes a difference considering it worked after clean flash.

I strip a few apps off of the OpenGapps using their config file, but I would download most of them anyway and I like not having to uninstall AOSP apps myself.
[OnePlus 3 & 3T Cross Device Development] Dirk:
If it were me.... Clean Install, Gapps Pico, don't replace any system apps immediately. Set up phone, install essential apps. Keep testing mic. As nvertigo said, step by step add stuff back and test.

Change things you can during flash. OB Firmware, perhaps Cesium Kernel (Additional benefit of using Banking Apps)
[OnePlus 3 & 3T Cross Device Development] Uumas:
Yeah, I think I'll only have time for deep testing tomorrow (like about 35 hours from now), but thanks.

PS. Don't need caesium for banking because magisk but will try anyway even though it's unlikely to help.
[OnePlus 3 & 3T Cross Device Development] Dirk:
I think you're better off leaving all mods out of the equation until you've tried and ruled out everything else. That's why Caesium. You'll still have Banking App usage in the meantime. As you're leaving out mods until the end, Magisk last and then any mods you're using Root for. If mic is working fine until the mod stage, you know where the problem lies.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Wi-Fi doesnt turn on Automatically after Reboot. Setting greyed out. Is this the current situation in LOS or just fubar in RR?
[OnePlus 3 & 3T Cross Device Development] laupuy:
Yep, the same on LOS..
[OnePlus 3 & 3T Cross Device Development] Dirk:
I wonder when that started! I rarely have it on these days and hadn't noticed. Someone else pointed it out in the RR thread.

Possible fix...? https://www.xda-developers.com/turn-on-wifi-automatically-nexus5x-nexus6p/
[OnePlus 3 & 3T Cross Device Development] lammpat:
[MENTION=5091734]dianlujitao[/MENTION] I dont know its new feature or what, but it wasn't the same way in 14.1.

When receive an SMS and open it via clicking on the notification and after reading press back button, its still showing as unread SMS in the list. It should have marked read isn't it?

#NoOffense
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=5965255]Uumas[/MENTION]:

The problem with larger gapps then pico or nano are the replaced system files: i.e. if you install chrom from playstore, webview is installed additionally and you can chose in dev opts which one to use. If you install chrome as system app (aka flashing with a larger opengapps package) the system's webview, which is compiled and ship for/with the rom is entirely replaced. No way of selecting.

For Dialer.apk it's similar: if younflash opengapps larger then pico/nano, the Dialer.apk shipped with the rom is replaced - if you install Google Dialer.apk from pstaore it's just installed as user app and you have the freedom to choose. The first throws away the shipped dialer and it's libs. The latter doesn't touch the rom's own system files, but the needed libs are inside the additional apk and are only used for the apk itself.

It's obvious that not messing with system files is less prune to issues.

This happens with other libs, too. In other words: from a systematically point of view using anything larger then pico/nano is modding the rom (system libs from the rom are deleted and replaced).

It's also much safer to install additional apps as user apps, because a user app can't do as much harm to your installation then a previleged app.

These are the main reasons, why most custom rom devs highly recommend using pico/nano and install apps you are missing from these packages as user apps from playstore. Some custom rom's devs are not supporting anything larger then pico/nano at all.

That's way [MENTION=1763460]Dirk[/MENTION] and me are recommending pico/nano if you want to use open gapps.

BTW: I'm still happy with MindTheGapps, because there are NOT autobuild very night (which means YOU are the man doing the beta testing). Often enough there are issues build in, vanished again on the next build. If one is using opengapps, I highly recommend to stick to a proofed to be working version, and not blindly using always the newest build.

BTW2: on firmware: before playing around with different fw versions (especially if hunting down issues), I would go with exactly that version, the rom's blobs are taken from. For current los builds this is ob29/38. Though I doubt it's the reason for your issue, it reduces the possibility of strange side effects. For debugging you want to exclude as much additional issue sources as possible.
[OnePlus 3 & 3T Cross Device Development] pitrus-:
This function is ment for activating wifi automatically at places with quality wifi like home, at friends or in public places. For it to work, you must choose a provider of quality check under advanced (Google is only available from what I know). If you don't choose any provider, the feature will be grayed out.

See included screenshot from my settings (in Swedish but you'll understand what I'm pointing at)

View attachment 4554689

Skickat från min ONEPLUS A3003 via Tapatalk
[OnePlus 3 & 3T Cross Device Development] Dirk:
So 'Network Rating Provider' was greyed out too. Then i found this on Reddit:

"Wi-Fi won't turn on automatically when:

Location is off

Battery saver is on

Airplane mode is on

Tethering ("hotspot") is on

Background Wi-Fi scanning is off"

In my case turning on Background Wi-Fi Scanning and GPS allowed 'Network Rating Provider' to be changed to 'Google' and 'Turn on Automatically' to be Enabled.

Mystery solved. Thanks!

---------- Post added at 13:15 ---------- Previous post was at 13:10 ----------

There is a new open Ticket on Jira for the Camera Flash issue. Please add your voices!

https://jira.lineageos.org/browse/BUGBASH-2032
[OnePlus 3 & 3T Cross Device Development] okaysee:
Call recording is back!

https://review.lineageos.org/#/c/219890/
[OnePlus 3 & 3T Cross Device Development] Dirk:
Never understood why people would want to do this. It's creepy. I bet most don't disclose to the other party that they're being recorded, which is illegal in many countries and US States.

It's okay when it's the NSA though. Also, hai to GCHQ. That's right, i can hear your breathing. Go nab a crook or something!
[OnePlus 3 & 3T Cross Device Development] okaysee:
I mostly use it when calling customer service and I live in a one-party consent area.
[OnePlus 3 & 3T Cross Device Development] Dirk:
What happened to the ability to Toggle Data modes? I'm sure i remember having 2G/3G Toggles in Quick Settings once upon a time? Am i wrong? Anyone seen such a thing for 3G/4G? :confused:
[OnePlus 3 & 3T Cross Device Development] S4turno:
You're now on the list.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Lol, i think i always was! :laugh:
[OnePlus 3 & 3T Cross Device Development] Uumas:
It's really helpful to be able to listen back to the recording because my memory isn't the best and I'd feel awkward calling back like two minutes later and asking what did we decide to do again or something. Also, I live in Finland and it's okay to record your own calls without disclosing to the other party.
[OnePlus 3 & 3T Cross Device Development] b.roid:
I'm not using this ROM but wondering if protected apps is back yet?
[OnePlus 3 & 3T Cross Device Development] :
But only theoretically... ;) It's explicitly disabled for these mccs:

ingo@adler /usr/local/src/los15/packages/apps/Dialer/java/com/android/dialer/callrecord/res $ grep -lr '<bool name="call_recording_enabled">false</bool>' values-mcc*
values-mcc202/config.xml
values-mcc206/config.xml
values-mcc216/config.xml
values-mcc218/config.xml
values-mcc219/config.xml
values-mcc231/config.xml
values-mcc232/config.xml
values-mcc246/config.xml
values-mcc247/config.xml
values-mcc248/config.xml
values-mcc262/config.xml
values-mcc268/config.xml
values-mcc270/config.xml
values-mcc272/config.xml
values-mcc278/config.xml
values-mcc280/config.xml
values-mcc284/config.xml
values-mcc293/config.xml
values-mcc310/config.xml
values-mcc362/config.xml
values-mcc505/config.xml
ingo@adler /usr/local/src/los15/packages/apps/Dialer/java/com/android/dialer/callrecord/res $

For legal weightment: The lineage implementation is not autorecording. You have to activly press a button to start recording.

EDIT:

for the home builders: https://github.com/nvertigo/android...mmit/4d36333adfbbc3b8fbb831d9fb5bc6578a9a85a8
[OnePlus 3 & 3T Cross Device Development] gruntyoldbag:
Am I the only one who has problems with the built in browser?

It stops working on every website after only 1 or 2 pageviews.

I know I can use other browsers but I have all my bookmarks in that browser (and that is also why I do not reset the app).
[OnePlus 3 & 3T Cross Device Development] :
The sqlite database files with your bookmarks and your history live in

/data/data/org.lineageos.jelly/databases

Save the directory, reset the app and copy them back. Boot to recovery and run restorecon on the copied dir.
[OnePlus 3 & 3T Cross Device Development] gruntyoldbag:
Thx - I will try that later today.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Camera Flash Issue:

Add your comments and votes on Jira.

https://jira.lineageos.org/browse/BUGBASH-2032
[OnePlus 3 & 3T Cross Device Development] :
Relax. I'm pretty sure [MENTION=5091734]dianlujitao[/MENTION] (and other los team members) have knowledge of this bugbash. I'm not a device maintainer, but following Snap development since Snap was activated in op1 builds. I'm sure the issues with Snap (and the fixes) does not relate to too less jira voters... ;)

In deed, our device maintainer is always the first trying to get Snap working on this device!

Honestly, if I would be in charge, I would wait for the blobs with the fixes for third party cam apps (oneplus promised to port them from 5/t to 3/tnwith one of the next 5.x.x updat2s) before spending time on fixing Snap. Just my two pence.
[OnePlus 3 & 3T Cross Device Development] Dirk:
This isn't just Snap and i doubt if any of the team members have taken much notice so far. It's only been up a few days. I say strike while the iron is hot. This issue has been ignored for months and we've had no feedback from anyone on it so far. Not even to acknowledge it. So no, i won't relax.

I urge people with Reddit accounts to get active on the subreddit too. This has gone on long enough.
[OnePlus 3 & 3T Cross Device Development] :
Acknowledging issues could be better on los jira . On the other hand, have you ever thought about that nobody has a solution, yet - and therefor no one is willing to take the assignkent of the bugbash? I think, as long as the bugbash isn't rejected, it is somehow "acknowledged".

The movie in my head: I know of a bug that is not only really annoying. I'm hunting that one for months in every spare second (the los people are normal people with normal jobs and normal private lives - I hope that for them! - doing los voluntarily). Now I get flooded with "Fix it, asop!" messages, but though I'm investigating this for months, I have no clue at all how to fix it. More pushing from others wouldn't generate a setting, where I could "think" faster and better... At least for me, this scenario is not very motivating.

I understand your mindset and frustration (I've been there many times and had to learn the hard way)! But I can't force people to be brilliant.

Snap suckz users as well as devs - perhaps the devs even more...

Preasure won't bringup brilliant, creative solutions.

Surely I want the flash issue, the broken livedisplay and the non-working volte with some carriers fixed. I still doubt that I can motivate a volunteer by pressure to fix it.

As stated: I learned that the hard way. Honestly, I forget this from time to time - I hope someone (perhaps you) remembers me if I forget again... ;)
[OnePlus 3 & 3T Cross Device Development] Dirk:
If you order the reports by 'Created' you can see that they're working through them in that order. They're currently up to 2002. This one is 2032. If this is really the first time that this issue has been posted, (which boggles the mind), the more comments and votes we have the more it'll be taken seriously when they reach it. If i were being told that an issue affects every single OP3/T user on LOS 15.1, and every derivative ROM based on it, which must be thousands of people...and then saw only three comments on a report that should have been made months ago..i might be a little skeptical. Fifty votes and comments would be another matter.

Let me ask you, why do you think it's taken so long for someone to try and get something done about it? I'll tell you what i think. Users always follow the path of least resistance. Making a proper bug report on Jira takes time and people can't be bothered with the process. Easier to dump a "OMGZ, phone broken, pls fix" post on xda. When people do bother to take the time to do it properly, nobody else can be bothered to take the time to back them up.

Yourself excluded, it increasingly common for devs to ignore ROM threads on xda, preferring social media, or Telegram even. Some don't want to deal with xda at all. Some maintainers openly admit to never visiting their threads here, or even owning the device they're maintaining. In those cases the same applies to their own forums, which they ignore, and on their own social media where they use any excuse to reject a bug report and send people back to xda, (which none of their devs actually read!) Not surprisingly, bugs never get fixed in those cases.

It's fortunate that LOS has Jira but instead of people using it, they just dump their less than useless 'bug report' here and are never seen again. I think all ROM threads on xda should be made to use the title, either 'Actively supported by Developer' or 'Community Support Only'. In the former case the dev should be actively communicating with people and acknowledging bug reports, demanding where necessary a minimum requirements for those reports. In the latter case, where support is basically people helping each other out, there should be links at least to the Official Bug Report method, like Jira.
[OnePlus 3 & 3T Cross Device Development] ignitionnight:
Does anybody know of an alternative to Notification Slider (App force closes and dev hasn't responded) as a way to "fix" the alert slider functionality in LOS for the one plus phones? Of all Roms LOS implementation of the alert slider is the most useless to me, was hoping I could get a decent workaround to have it set audio profiles instead of just DND mode.

Rather not just jump back to Omni, i was hoping to use LOS as my daily driver for a while.
[OnePlus 3 & 3T Cross Device Development] :
Disclaimer: please don't kill the messenger.

Sadly, I don't know of an alternate app.

Sadly, there are reasons, that make me think, we won't see additional slider options in los:

https://review.lineageos.org/#/q/status:abandoned+topic:tristate-vibration

(read the comments in https://review.lineageos.org/#/c/LineageOS/android_device_oppo_common/+/215212/, you'll find the abandon reson: "Abandoned let's hold on for this - we might use another approach" - this was six weeks ago)

Sadly (again), the former (cm14) solution, putting the vibrate and silent mode in the extended power menu and on themslider only the dnd modes, seems not to be ported to lineage-15.1.

Now for semi-good news: homebuilders can include

https://review.lineageos.org/#/c/LineageOS/android_device_oppo_common/+/215212/

https://github.com/nvertigo/android...mmit/4c62ec5fc4a8393d11197c70ec812e85883255a1

in their builds.

Non-homebuilders can try to find los based builds with these two patches included. They have some glitches with the status bar icon, but work flawlessly otherwise.

And now for something completely different...

[MENTION=1763460]Dirk[/MENTION]:

I'm completely with you. Great writeup! I would like to add "in quite some threads, the job of a dev seems to be begging for information and logs, or searching and linking already given answers."

I'm just not sure, on how to motivate volunteers...
[OnePlus 3 & 3T Cross Device Development] Immortalis:
Can confirm it does work, but not with every custom kernel (Mady's works fine, EX doesn't), is this caused by different slider implementation in the kernel?
[OnePlus 3 & 3T Cross Device Development] :
Yes, the qcom-common patch and the kernel patch have to match each other.

Some months ago I tried to use the omni implementation, but that was causing a serve side-effect with magisk installed: bootloop. The abandoned los implementation is working for me flawlessly for at least 7 weeks, now.

To my knowledge there are - at least - three different implementations out there: this one, omni and rr - I guess they are all different and need different kernel patches.
[OnePlus 3 & 3T Cross Device Development] SpitFire-ZX:
For me a clean install did the trick.
[OnePlus 3 & 3T Cross Device Development] Thorst1:
Thanks for the reply! A reboot or two fixed it for me too :)
[OnePlus 3 & 3T Cross Device Development] shouhu1993:
I use gcam today, and I found that camera flashlight work normal with HDR off when i change camera focus. does anyone confirm?

I flashed the 20180717-lineageos and opengapps
[OnePlus 3 & 3T Cross Device Development] lammpat:
today's build failed :(
[OnePlus 3 & 3T Cross Device Development] Playa82:
relax. they will start it again later.
[OnePlus 3 & 3T Cross Device Development] multiwirth:
The old CyanogenMod (13) camera apk does work very well but does not support 60fps@1080p or some other cool features.

It's a basic camera app.

Flashlight works as expected - anyways a general issue with LineageOS but it seems like a app issue not a rom issue.
[OnePlus 3 & 3T Cross Device Development] kenboyles72:
Ok, so for a while now, in settings, it states my sim is disabled, but phone functions without issue. I can still make calls and data is working fine. But now after flashing latest build, I get sim disabled along with the data icon missing from status bar, this happens a few hours after flashing. For now I reverted back to a Jun 14 build and all is fine.

BTW, I am using OB38 firmware/modem
[OnePlus 3 & 3T Cross Device Development] Dirk:
When did you last clean install? Have you checked APN settings? Perhaps something changed between builds? Perhaps that Firmware/ROM combination just isn't working well together. Try another Firmware version?