yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] Dirk:
Another happy punter. Time to go to bed while i'm still ahead.

No lag on the 3310 either. Just thought i'd mention it.
[OnePlus 3 & 3T Cross Device Development] mk_1996:
Well i booted my nokia e5 after almost 7 years. Things haven't changed a bit
[OnePlus 3 & 3T Cross Device Development] Dirk:
I hope you fired up some Snake! My last was an E60 which survived everything i threw at it for years. That thing was an absolute unit! It was sat in my drawer until last year when it was put back into service as the emergency phone at work. Unfortunately it didn't survive my colleagues. RIP. :(
[OnePlus 3 & 3T Cross Device Development] Dirk:
Here's an interesting read about Camera blobs, api support and custom ROMs for those who care about such things:

https://www.reddit.com/r/oneplus/comments/7cz7t5/oneplus_roms_camera_situation/
[OnePlus 3 & 3T Cross Device Development] geogaddi47:
Does the latest build have battery drain issues? I'm wondering whether to update. Thanks.
[OnePlus 3 & 3T Cross Device Development] Dirk:
I haven't had a single 'battery drain' issue since Oreo development began, and i've flashed a new build every week since then.
[OnePlus 3 & 3T Cross Device Development] user7743:
Then you have been lucky. I have had a few builds where battery drain was inexplicably high... But then these are dev builds so such things have to be expected.

Does anyone have any issues with Bluetooth in a car? For the last few builds (I couldn't tell you how far back), my phone connects in the car. The signal strength is shown but never updates whilst being connected. This is problematic if you have no signal to start with. You cannot make calls from the car as it thinks you have no signal.
[OnePlus 3 & 3T Cross Device Development] s.teunissen:
Trying to install this rom, but downloading from lineageOS site is practically impossible as speed is around 20k/s and cancelling all the time.

And it has been for over a week now. Is there another way to get hold of this rom ?
[OnePlus 3 & 3T Cross Device Development] Dirk:
Latest build:

https://mirrorbits.lineageos.org/fu...age-15.1-20180710-nightly-oneplus3-signed.zip
[OnePlus 3 & 3T Cross Device Development] s.teunissen:
Thanks, but it is not working:

"Downloading.. 11 hrs left"

---------- Post added at 03:32 PM ---------- Previous post was at 03:27 PM ----------

Strange. Just did another try and it flies in !
[OnePlus 3 & 3T Cross Device Development] Dirk:
You should definitely wait longer than a picosecond. Long enough at least for a single Packet to travel half way around the world at light speed. Unfortunately, nothing is faster than impatience. Even light. ;)
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
I can confirm that the download speed is not that high as expected (around 60KB/s).

But I have already the file and I'll need the speed only again on tuesday with the new build :)
[OnePlus 3 & 3T Cross Device Development] Dirk:
Bookmark this page:

https://www.lineageoslog.com/15.1/oneplus3
[OnePlus 3 & 3T Cross Device Development] Darkje:
So guys, how's Los doing these days as a daily driver. Since OnePlus dropped support. And I still like the phone IAM thinking of Los. But battery needs to be good, just like all basic functions. So basically, what are the pros and the cons?
[OnePlus 3 & 3T Cross Device Development] Explorer23:
It's doing great. I'm using it as daily driver since stable branch went live.

Pros: it's LOS, what more needs to be said? Stock Android, fast, stable, reliable, with regular (weekly) updates.

Cons: uh, nothing? Could say stock camera, but even a quick glance at this thread reveals that noone is using it as pretty much everyone (including me) went for a GCam mod (personally using Arnova's version). And that does make nice pictures.

Battery life should be fine, try and see for yourself. If you're not exactly satisfied, try custom kernel. I'm using Franco's atm and I'm happy with it.
[OnePlus 3 & 3T Cross Device Development] :
May I ask for the source of this information?

My last information from the official oneplus road map: 2 years from release date we get regular updates containing new versions/features/security updates; plus one additional year of regular security updates. Chances are high, that the op3 receives updates til eol of op3t.

This would mean support for op3t (and most probably for the op3, too) will continue for 16 months (until Nov. 2019).

If you have more current information, please share with us.
[OnePlus 3 & 3T Cross Device Development] counterfeit187:
I think he means now that open beta program has ended. We'll see one more update for official oxyOS, (maybe this week) then probably just security patches for a year. This downtime is going to bring a lot of us back to the custom roms. There has been rumors about the next update bringing us up to 8.1 or maybe even Android P so we'll likely all switch back to try that out if it happens.
[OnePlus 3 & 3T Cross Device Development] :
If [MENTION=1316691]Darkje[/MENTION] has known and meant what you summerize, "Since OnePlus dropped support." is intentionally spreading misinformation...
[OnePlus 3 & 3T Cross Device Development] Darkje:
Ow iam sorry all for the misunderstanding, off course I mentioned active development of the beta channel
[OnePlus 3 & 3T Cross Device Development] Spanking Time:
I was on a build from about 3 weeks ago when I got my OP3T. Idle battery drain was off the charts. In less than 4 hours of screen off, phone doing nothing, battery went from 100% down to 86%. Unacceptable, so I flashed stock OOS. Battery life is now extremely improved from LOS. I do miss some of the extra features LOS offers, but man, that battery drain is ridiculous. I'll come back to try LOS whenever there's an Android P build, since OP isn't updating this phone after Oreo.
[OnePlus 3 & 3T Cross Device Development] Playa82:
Wow. I got a battery drain of 1-2 % overnight with los and madys kernel. A night is usually 6-7 hours for me. Same is when i do nothing with my phone (screen off)
[OnePlus 3 & 3T Cross Device Development] :
Sometimes there is an unexeptable idle drain (and 3.5%/h is unexeptable). I've expirienced that from time to time since the early alpha builds. At first I thought it's a build issue.

There have been builds never going to deepsleep due to errors in the wlan driver regarding thermal shutdown. So I continued to belive the idle drain is build specific (so called "bad builds").

Then I found, whenever the idle drain shows up, the deepsleep time decreases to an amount that isn't nearly covered by the wakelocks (i.e. 4h screen off, 1.5 h active while screen off, but only accumulated wakelocks for 20 minutes) and the top kernel wakelock is not PowerManagerService (this is the placeholder for partitial wakelocks, and normaly it's the top one), but timerfd.

In this situation (though it makes no sense on the first glance, since all wakelocks doesn't nearly sum up to the time the device is active, while screen is off) a custom kernel with [MENTION=947981]Lord Boeffla[/MENTION]'s awesome kernel wakelock blocker intergrated will help.

The other solution is: patience. After a couple of days and some reboots, this mysterious "device active, while screen is off" vanishes again.

I havn't found the trigger (neither for appearance of the bug, nor for the vanishing), yet. And honestly I have to admit I gave up on digging for it - I just use the wakelock blocker. Since then this bug never bugged me again.

For reduced battery usage I strongly recommend reading this writeup from [MENTION=4487956]S4turno[/MENTION]: https://xdaforums.com/oneplus-3/one...eplus-3-3t-t3739169/post76827895#post76827895
[OnePlus 3 & 3T Cross Device Development] Playa82:
try madys kernel and put the apps who drains the most battery to sleep with pivacy guard feature from LOS.
[OnePlus 3 & 3T Cross Device Development] :
...or any other kernel with [MENTION=947981]Lord Boeffla[/MENTION]'s wakelock blocker:

https://github.com/mady51/unifiedOp3/commits/8.1/drivers/base/power (commits from Jan. 8th)

This is not limited to [MENTION=431778]mady[/MENTION]'s kernel. From memory:

boeffla's (of course)

[MENTION=3292224]franciscofranco[/MENTION]'s

[MENTION=6552280]MSF Jarvis[/MENTION]' caesium

This list is NOT complete and doesn't priorize them in any way - it's just my memory. I've tested myself with caesium, boeffla and my own kernel: as soon as [MENTION=947981]Lord Boeffla[/MENTION]'s wakelock blocker is merged I have an idle drain of 0.8%/h (droping to 0.4 -0.6%/h if I disable background data for k9 and whatsapp).

As stated above: ANY kernel with the wakelock blocker solves the mysterious "device active, while screen off"-drainer.
[OnePlus 3 & 3T Cross Device Development] Spanking Time:
These custom kernels (I've never used one), they automatically enable this wakelock blocker? If so, to what extent? I do want some apps to use wakelock obviously, such as music/podcast apps. Do these kernels cause any new unexpected issues when used with LOS and Magisk?

---------- Post added at 02:46 PM ---------- Previous post was at 02:43 PM ----------

I think I tried 2 consecutive LOS builds and both gave me awful battery drain. I'd rather not have to cross my fingers, wondering whether the next build is going to have a battery "bug" or not. Oxygen OS is pretty dang slick, and with Magisk I'm happy for now with that.
[OnePlus 3 & 3T Cross Device Development] :
Exactly these: https://github.com/mady51/unifiedOp...d/drivers/base/power/boeffla_wl_blocker.h#L19

Please understand the kernel wakelock blocker is for kernel wakelocks - PowerManagerService.* (aka Partitial Wakelocks, aka App Wakelocks) are not touched at all.

I'm using the 4 commits I linked in my last posting for about 20 weeks now without noticing any drawbacks. I'm using Magisk as well without issues. The only streaming app I'm using on a regular basis is lastfm - no issues. As stated: the PowerManagerService.* are not touched, so I don't think you have to consider any app issues. On the other hand: who knows before testing each and every app. So I can only be sure for apps I'm using myself.
[OnePlus 3 & 3T Cross Device Development] Spanking Time:
Got it. Thanks!
[OnePlus 3 & 3T Cross Device Development] oprz_5:
I'm on 07/10 nightly build. Couple of issues I have had are these.

1. Search function in settings menu is broken. It's not a big deal, but a good perk to have.

2. Connecting to a Bluetooth device while connected to a WiFi network is giving me issues. Sometimes the playback via Bluetooth gets interrupted and at other times, I get disconnected from the WiFi network. I have had this issue on OOS oreo as well but not this severe. But nougat OOS did not have this issue.

3. Network connectivity, especially LTE reception is worse than stock OOS( Vodafone India). Both the range and data speed gas taken a hit. I tried flashing the modem to see if anything changed, but it didn't.

4. Network settings in profile menu gives FC. Once again not a big deal.

5. The off screen gestures sometime results in a reboot. I had this issue twice while trying to enable the flashlight. Haven't been able to reproduce this. Sometimes instead of a reboot I don't get any response. And then when I try to open the camera, all I get is a black screen.

Other than these I am happy with the rom. Performance is great. No idle battery drain, both on default kernel and Mady's. Also the new black mode is great.

Also is there a way to get the oneplus dialer app and messaging app on los? I tried installing the apks, but it failed mid way.
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
1.-3 & 5 is working fine for me.

To 2. & 3: Do you have the newest Modem from here: (OB38 / 39) https://xdaforums.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628

5.: I don't have this reboots, but for the camera thing you could try the GCAM Mods: https://xdaforums.com/oneplus-3/how-to/modded-google-camera-hdr-60fps-video-t3658552
[OnePlus 3 & 3T Cross Device Development] :
search. Hotfix posted many times. (change language)

working for me. In deed most music is on my internal wlan server.

search. Answered many times. (oos just tunes the bars a bit, check dbm in settings in oos and in los, compare them within the same location)

network type is crashing, other network settings are working fine, here.

it's not the gestures, it's only the torch gesture: uninstall third party camera app, which doesn't release the flashlight probably. In most cases some OPCam mod.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Reveille...

New build up!

https://www.lineageoslog.com/15.1/oneplus3
[OnePlus 3 & 3T Cross Device Development] Dedojyoti:
Is any trable support are coming for one plus 3/3t??
[OnePlus 3 & 3T Cross Device Development] xpissio:
No, it isn't
[OnePlus 3 & 3T Cross Device Development] Dedojyoti:
Is any possibility to come???
[OnePlus 3 & 3T Cross Device Development] :
To have treble supported, you need a vendor image containing the proprietary blobs. You also need an unsed partition. Since the latter is available on our devices (a reason many people - including me - thought this may be a hint, that treble support from OnePlus would come sooner or later), the remaining problem are the vendor image files. Meanwhile OnePlus has stated that there will be NO support/migration for/towards treble. Since we have not the source code to build treblized versions of i.e. all hals, los for op3/t will not be treblized.

If you want treble, get a used op5/t (or a new op6). Last op5/t openbeta is treblized.

BTW: for the user a treblized los is not different from what we use - treble is an advantage for devs, because the same generic build can be uswd across differnt devices without recompiling. The advantage for the users would be more custom roms available - on the other hand: there are not much devices with a wider variety of custom roms then op3/t.

Question: One of the great pros of trebelized should be the possibility to update the vendor files via playstore. Has anybody heard of this in real life for real devices?
[OnePlus 3 & 3T Cross Device Development] Dedojyoti:
Thanks bro
[OnePlus 3 & 3T Cross Device Development] Dirk:
Honestly, i have no interest in project Treble and never will. Why would i want a barely working generic image on my phone when i can have a bespoke, fully optimised and fully customised device specific ROM?

It's like going to a Tailor and saying, "nah, don't measure me up. I'll just take whatever you have in a Medium"

Bonkers! :rolleyes:

Speaking of Bonkers, Apex Launcher just got a big update. Everything is broken of course. The Launcher that i've been using since it's inception, has worked perfectly and seamlessly for many years, across so many devices...and now a shambles. apkmirror to the rescue of course. Disable Updates, reinstall App Backup, all good again.

My list of Apps with Automatic Updates 'disabled' grows daily, my collection of apk's too. Soon i won't need the Play Store at all.
[OnePlus 3 & 3T Cross Device Development] Robbo.5000:
Because that is not what Project Treble is about. It is not about having a generic AOSP build that can run an any device, that is just a small consequence of the Treble design.

Once vendors/manufacturers start releasing sources to the dev community for Treble enabled devices, then you will see many of the fully optimised ROMs become Treble ROMs very quickly indeed. What you will also see, because there will already be working sources, is porting of these ROMs to Android P and beyond, probably within a day or 2 of Android source releases.

Custom ROM communities have always relied on manufacturers to release some sources in order to get the most from the devices and this hasn't changed. But once the first Treble sources arrive, there should be little need for further releases, at least for one or 2 Android versions beyond, for each device.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Call me cynical, but this whole thing might end up in the Expectation vs Reality subreddit. Sounds great in principal though.
[OnePlus 3 & 3T Cross Device Development] d0s1s:
Hi,

[MENTION=5091734]dianlujitao[/MENTION] Could you take a look at the configuration of this file https://github.com/LineageOS/androi...rameworks/base/core/res/res/values/config.xml ?

At line 212 there are the settings to "<!-- Enable overlay for all location components. -->" could you please set config_enableNetworkLocationOverlay and config_enableFusedLocationOverlay to 'true' to make our device compatible with UnifiedNlp and gms as location providers. Or just comment the lines 213 to 216 like OnePlus Cheeseburger/Dumpling... Lineage Os device tree.

The problem is that with the current configuration, if we use another provider other than com.qualcomm.location, we can not get a location (GPS).

Thanks in advance!
[OnePlus 3 & 3T Cross Device Development] Thorst1:
Hi Spitfire, I realize I'm dragging up a very old post of yours, but I'm experiencing the same issue on my OP2 at the moment, and Google pointed me here :) Did you fix this issue, any advice?
[OnePlus 3 & 3T Cross Device Development] :
Don't you need the signatute-spoofing-patch (if the UnifiedNLP apk isn't signed with the platform-key from the installed rom) and the allow-location-provider-outside-system-patch (if you want to use fused location providers installed from f-droid microg repository) in order to get UnifiedNlp working?
[OnePlus 3 & 3T Cross Device Development] bavay:
No sound during calls

As I've seen some comments about LineageOS release 2018-07-10, I have a problem since the upgrade: the speaker on the phone does not work during calls. I always have to switch to hands-free mode (using the integrated loudspeaker) in order to hear the call going on. Does anybody knows how to debug such audio issues (ie if there is a way to force routing music through this speaker, to check mixer settings for this speaker, etc)? I guess the speaker is on mute, but I have no way of checking it nor changing it...

Mathias
[OnePlus 3 & 3T Cross Device Development] Dirk:
Yes you do. Try using Volume + while in call. Can you hear it now? There will be a Volume slider, titled 'Call' at the top of screen when you do this. Was it at minimum?
[OnePlus 3 & 3T Cross Device Development] Dirk:
So glad i don't own an A/B device:

https://lineageos.org/Changelog-19/

Sounds like a headache!
[OnePlus 3 & 3T Cross Device Development] DeadFox-xda:
Lol read the first sentence and I need an aspirin already.
[OnePlus 3 & 3T Cross Device Development] Dirk:
I think they're trying to put a positive spin on it:

"Many around the Android community have bashed A/B as being “hard to support” and “not developer friendly”, when in fact, properly implemented it is easier to support and just as developer friendly."

Hmmm. Not sure about 'user' friendly though. These Google brainwaves, i.e Project Treble and A/B Partition schemes, are not created to make life better for the Custom ROM community. They're for the benefit of the other 99% of Android users. Google don't do anything with us in mind. Of course the community will always find a way to manage the situation, but none of this is simplifying anything.

I'll stick to doing things in the traditional manner and avoid complications like A/B devices for as long as possible. :)
[OnePlus 3 & 3T Cross Device Development] d0s1s:
Yes but Signature spoofing is not supported by LineageOS. https://review.lineageos.org/#/c/LineageOS/android_frameworks_base/+/195284/

There are alternative installations.

Best Regards
[OnePlus 3 & 3T Cross Device Development] :
I know that - my builds have the patches and UnifiedNLP is working great without the two changes you mentioned. But I havn't known:

I also know the arguments on the sig-spoofing-patch... ;)

If you like, I can push a commit with the changes, you are suggesting - but I surely won't go into religous-like arguments!
[OnePlus 3 & 3T Cross Device Development] d0s1s:
If it's not too much trouble, I'd appreciate it.

Thanks
[OnePlus 3 & 3T Cross Device Development] bavay:
Yes, of course I did! The "in call" volume is at the maximum. If I tap on "loudspeaker", I hear the sound nice and loud. Without, there is just no sound. So I guess that for the handset speaker, the volume might be set to mute while in the higher level (ie Pulseaudio's application volume), it is set to 100%. But don't know any way of testing this hypothesis...
[OnePlus 3 & 3T Cross Device Development] :
Good luck!

https://review.lineageos.org/#/c/LineageOS/android_device_oneplus_oneplus3/+/220842/

---------- Post added at 19:57 ---------- Previous post was at 19:54 ----------

https://alsamixer.de.aptoide.com/

Root needed. This was on play store, but I can't find it anymore.
[OnePlus 3 & 3T Cross Device Development] Playa82:
Is there a bug in storage ? My system data is very high.
[OnePlus 3 & 3T Cross Device Development] arifnasirshaikh:
Do you use es file Explorer?? If yes then disable recycle bin and delete all the files inside it.
[OnePlus 3 & 3T Cross Device Development] Playa82:
No i dont use it. Tried the whole day to unbrick my device with msmtool. Is this junk from the canceled downloads ? I had to try it maby times till it worked.
[OnePlus 3 & 3T Cross Device Development] Zelete:
Sorry wrong information. Edited post...
[OnePlus 3 & 3T Cross Device Development] Playa82:
Is there a way to delete old system data without formatting ? I setup my device for 2 hours yesterday. As i said, msmunbrickbtool restarted a lot and everytine it downloaded and failed. Maybe thus are the old files. Can anybody help me fix this ?
[OnePlus 3 & 3T Cross Device Development] pro_drive:
Can not obtain IPv6 address when using mobile data(China Telecom LTE), is it the bug of LineageOS?

But I could get correct IPv6 address under the stock Oxygen OS 5.0.4.

[SOLVED] Check APN setting, turn APN stack IPv4/IPv6 network stack on. It works.
[OnePlus 3 & 3T Cross Device Development] morphvale:
Did you restore a backup after unbricking?

If you copy files to storage inside the TWRP folder that TWRP creates, that'll be under /data/media/TWRP instead of /data/media/0/TWRP. Android storage manager will show this as System data, instead of user data. Check if you have the folder under /data/media and either move it to /data/media/0 or delete it.
[OnePlus 3 & 3T Cross Device Development] Playa82:
ok, i saw it. i got the same data in /data/media/0 as in sdcard folder. can i delete the folders in /data/media/0 ?

i restored a backup, yes. i copied it in sdcard folder in twrp via pc

or ist it better to back up current system and format everything ?
[OnePlus 3 & 3T Cross Device Development] suolrihm:
I haven't made this expirience yet but i think you should try:

Format with fastboot (userdata, cache, system).

Format in TWRP and Reboot

Open TWRP, go to settings and tick rm instead of formating.

Restore your Backup.

Can't tell if it works, but if you want you can try and let us know
[OnePlus 3 & 3T Cross Device Development] morphvale:
No, you should not delete /data/media/0 nor /sdcard. The /sdcard, as far as I remember, is just a symlink to /data/media/0

You should, however, delete /data/media/TWRP if you have that folder.
[OnePlus 3 & 3T Cross Device Development] Playa82:
whats rm ? i make a backup of my current setting. after that i format everything and set it to ext4. then i copy my backup to the folder in sdcard that i see at my pc, right ? then i restore it and it should be done.

am i right ?
[OnePlus 3 & 3T Cross Device Development] suolrihm:
Right on the first page of the settings you get several options, like turn on or off the question to install the TWRP App. On this package should be this rm instead of formatting question (Went back to Stock for the moment so i can't tell how it's called exactly). rm is a Linux command and simply stands for remove. It's faster and should not mess up the format of your device
[OnePlus 3 & 3T Cross Device Development] Playa82:
ok. i try to format everything in ext4 and reinstall a clean system. is this better ? i just want to have my 64 gb back. the system is 34 gb at the moment.
[OnePlus 3 & 3T Cross Device Development] Uumas:
I'd try formatting data to ext4, then back to f2fs in TWRP (Everything including internal storage will be wiped ofc)