yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] Dirk:
Thanks. I'm at home all day today so i went ahead and clean flashed. First thing i did was connect to my PC. Notification came up as it's supposed to. Problem solved! :good:
[OnePlus 3 & 3T Cross Device Development] Playa82:
flash the newest beta available for your device when you do a new update next week. flash modem - firmware first and after that the new weekly build.
[OnePlus 3 & 3T Cross Device Development] hsquare:
Thanks! Where can I see which version I currently have?

And should I really use your link and not this one? https://xdaforums.com/oneplus-3t/how-to/firmware-beta-10-t3631166

If so, why?
[OnePlus 3 & 3T Cross Device Development] trigonX:
Guys I am still on LineageOS 14.1 and I would like to update - and I am a bit confused about kernel... Currently I am on kernel 3.18.31-lineageos-ge1576f5. Should I flash a different one or can I simply flash the LineageOS 15.1? And one more thing - is there a way to update from 14.1 to 15 without losing data? I really dont want to go through the hell of installing everything and reconnecting all accounts :(
[OnePlus 3 & 3T Cross Device Development] megatomic:
As noted earlier, the bug where the phone storage isn't browsable (is that even a word?) on a PC without enabling MTP mode in Developer settings seems to be fixed. The bug where location data isn't recorded by the Snap camera is not fixed yet though. I'll just disable the app (as usual/yet again) and use Gcam. [MENTION=5091734]dianlujitao[/MENTION], I know your plate is full and you made a ton of changes on this week's build (thanks a bunch), is it possible for you to say if the Snap/location data bug is on your radar in the near future?
[OnePlus 3 & 3T Cross Device Development] yarpiin:
clean flash is recommend , you can use app like titanium backup for your data
[OnePlus 3 & 3T Cross Device Development] VincentJoshuaET:
[MENTION=5091734]dianlujitao[/MENTION]
[OnePlus 3 & 3T Cross Device Development] Dirk:
Is the wakelock issue fixed for everybody that had it now?
[OnePlus 3 & 3T Cross Device Development] h4rl4n:
Can this firmware be flashed over latest weekly build?
[OnePlus 3 & 3T Cross Device Development] mk_1996:
Depends. Do you own a 3T or a 3? If you owe a 3T,you can flash this over
[OnePlus 3 & 3T Cross Device Development] Dirk:
I'm using OB23 without any problems. (3T)
[OnePlus 3 & 3T Cross Device Development] Playa82:
[MENTION=5091734]dianlujitao[/MENTION]

i restartet my phone to see if the usb problem (pc is not recognizing the phone) is back again. and yes it is. the only workaround is to enable and disable usb debugging. for your info
[OnePlus 3 & 3T Cross Device Development] Doc Sniper:
Still the same for me ...
[OnePlus 3 & 3T Cross Device Development] :
In the last 30 pages - at least - three different wl issues are mentioned. I could only reproduce one of them: wlan_auto_shutdown_wl. This is fixed with [MENTION=4329165]ivanich[/MENTION]'s patch.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Which 15.1 ROMs have you flashed, i.e Experimental>Weekly, and when did you clean flash, if at all?

I clean flashed for the Experimental build and Dirty flashed each subsequent Weekly. The issue was there for me since the Experimental build. I clean flashed today and the issue is gone. I'm working on the theory that there was a bug in Experimental. Any clean flash on a Weekly build should get rid of it.

One thing i noticed, before today (with the bug) USB was set to Charging by default in Dev Options. After a clean flash it's set to MTP by default.

Did you clean install this weeks build?
[OnePlus 3 & 3T Cross Device Development] Doc Sniper:
I did a clean flash of 2018-03-12 and today a dirty flash of 2018-03-19.

Do you think a clean flash (or factory reset) helps with the wakelocks ?
[OnePlus 3 & 3T Cross Device Development] pcesar.cercal:
where I find the Lockdown option

I havê op3
[OnePlus 3 & 3T Cross Device Development] hsquare:
Hello again,

does someone kindly know the answer to this? Thanks a lot!
[OnePlus 3 & 3T Cross Device Development] DasBaumchen:
Anyone else has the problems that the camera isn't responding at all?

I'm using:

- Firmware + Modem OpenBeta 32

- lineage-15.1-20180319-nightly-oneplus3-signed

- open_gapps-arm64-8.1-mini-20180320

- Google Camera Mod 5.1.018 v3.0 Full Auto - SKULSHADY

- Frontend Camera Lib Fixes by defcomg

The default camera is just not responding, the camera mod is crashing and every camera app I've installed can't use the camera.

It worked in 14.1 with a bigger loading time(phone crashed while using google maps and since then compass doesn't work and camera takes a long time to react, applied for RMA already since it doesn't seem to work with 15.1 for me, the experimental build before it was official was working fine strangely)
[OnePlus 3 & 3T Cross Device Development] Dirk:
Already answered....

It might. Bugs tend to carry over on dirty flashes in my experience. Wait until more people report in, see what they say about it.
[OnePlus 3 & 3T Cross Device Development] devnerd:
So if you want to be completely sure that you only flash official OnePlus firmware, build it yourself instead of waiting for others to do it for you.

That's how I did it:

1) download latest official OOS beta from oneplus website for your device (3/3T)

2) create a temp folder on your machine and place all files for your zip in there

3) extract firmware-update folder and radio image and put them all in the folder firmware-update

3) also extract the update-binary and update-script from META-INF/com/google/android/ out of the official OOS zip and create the same folder structure as in the zip

4) open the updater-script with a text editor and remove everything except the commands for the firmware files you want to flash and don't forget to edit the line for the static_nvbk as you will also flash it from the folder firmware-update

5) zip everything and flash it via twrp

Now you know that you have only installed what will be installed by oneplus during a system update.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Was the default camera working before you started flashing camera mods?
[OnePlus 3 & 3T Cross Device Development] chewdaniel:
came from OB23. Started off with 0312.

caesium kernel

opengapps stock
[OnePlus 3 & 3T Cross Device Development] Dirk:
Settings>System>Buttons>Power Menu>Lockdown
[OnePlus 3 & 3T Cross Device Development] SeberNoid:
I can't believe people here won't even bother to try clean flash before whining about issues.
[OnePlus 3 & 3T Cross Device Development] Playa82:
i'm on weekly build. i flashed my first build (clean, i came from OOS 5.0.1) on Saturday. yesterday i dirty flashed the new weekly.

i noticed after every reboot it shows only loading in developer options. i cant set it to mtp by default when i do a reboot. it shows only loading after every reboot. maybe this should be fixed next realease.
[OnePlus 3 & 3T Cross Device Development] SoMeiBoL:
I do not have any problems with those mentioned here.

Installed last build LOS 15.1, opengapps AROMA 16-03, magisk 16.2, elementalX kernel 4.05, Google Camera Mod 5.1.018

v3.0 Full Auto skulshady, Oneplus camera M and firmware of open beta 23.

Oneplus 3T. Very happy with this rom :)
[OnePlus 3 & 3T Cross Device Development] Sam Nakamura:
It's a security thing and not a bug, it's intended to be like this...

It should be somewhere in the changelogs, if I remember correctly
[OnePlus 3 & 3T Cross Device Development] megatomic:
Now we give it a few days to see if the "white LED of death" lockup has been fixed. I had two such lockups on the last build (clean flashed that one also).
[OnePlus 3 & 3T Cross Device Development] Playa82:
to be fixed ?
[OnePlus 3 & 3T Cross Device Development] Dirk:
Don't hold your breath! It seems so random. Some people get this bug, others not. When i first connected to my PC after a clean flash today, the notification appeared as expected. Now it doesn't again. I don't know what's going on with it. I keep thinking it must be some setting i've changed during setup,or some app i've installed, but i can't think what.
[OnePlus 3 & 3T Cross Device Development] hsquare:
Thanks, but you're already the second person who did not answer my question. So it is probably my fault. I try again:

Phone: Oneplus 3T

OS: LineageOS 15.1

1. Where in the settings of LineageOS can I find out the version of my firmware? If not in the settings of the firmware, how can I find out else?

2. If I need to update the firmware, is this the correct download? https://xdaforums.com/one...ta-10-t3631166

Thanks a lot!
[OnePlus 3 & 3T Cross Device Development] devnerd:
1. Not possible afaik as you are flashing multiple small firmware files for different hardware components. Nowhere is written something like "OpenBeta23 firmware". Also the firmware doesn't change with each new beta. But as you don't know if something changed, you flash it to be sure.

2. I generally don't comment unofficial firmware packages. No idea if that zip works
[OnePlus 3 & 3T Cross Device Development] Dirk:
Re: USB Connection Notification not appearing after reboot.

Haven't found a fix, but there's more people having the problem discussing it on the Google Product Forums:

https://productforums.google.com/forum/#!topic/phone-by-google/DfpqXN1UfWY

The only common link i can find is Oreo itself.

---------- Post added at 17:12 ---------- Previous post was at 16:23 ----------

It can't be intended behaviour that Developer Settings have to be enabled and USB Config set to MTP before someone can transfer files via MTP. Most Android users won't even know how to enable Dev Settings or that they even exist. People plug in their phone via USB and expect a notification with the options to appear. Without the notification, what are people supposed to do?

---------- Post added at 17:16 ---------- Previous post was at 17:12 ----------

Is yours still working after reboots? My clean flash only fixed it for initial boot up. Since then the problem is the same as before.
[OnePlus 3 & 3T Cross Device Development] megatomic:
No, my work laptop is not detecting my phone without me to forcing MTP mode in Developer Mode settings.
[OnePlus 3 & 3T Cross Device Development] trigonX:
Guys is it rooted? I guess not but I only found SU binaries for 14.1:

https://download.lineageos.org/extras

should I use it for this rom?
[OnePlus 3 & 3T Cross Device Development] joakimbo:
First day on the new update, some stuttering and a bit slow app opening. Not impressed with the battery life either. Will see after some days. Dirty flash.
[OnePlus 3 & 3T Cross Device Development] airtower:
It isn't fixed - just happened to me for the first time. I wouldn't call it the LED of death though lol just a lockup.
[OnePlus 3 & 3T Cross Device Development] timvonlee:
Flash light / torch not working, stock lineage kernel.

Anyone?
[OnePlus 3 & 3T Cross Device Development] megatomic:
I didn't coin the term, I borrowed it from another post here in this thread. I thought it was funny. Bummer to hear that the problem still exists.
[OnePlus 3 & 3T Cross Device Development] counterfeit187:
It works for me unless the camera app is open, but that makes sense because the camera has it's own flash options.

I get that on the first boot whenI do a clean install and adding magisk. I just hold the power button to restart and it usually works the second time I try to boot up.
[OnePlus 3 & 3T Cross Device Development] Sam Nakamura:
It's a AOSP standard, MTP is never default even if it is intentionally changed by the user a reboot will revert it, that's all I meant - not saying that the current implementation is great or anything, just saying I was not sure if it's a bug as it's actually intended behavior defined by El Google, which of course doesn't mean it's intended on LineageOS too... So actually no idea really but chances aren't too bad for "not a bug but a feature" side

It was previously discussed on OMNI8

https://xdaforums.com/oneplus-3/one...ent/8-x-omni-oneplus-3t-t3695992/post75638841

https://xdaforums.com/oneplus-3/one...ent/8-x-omni-oneplus-3t-t3695992/post75655939
[OnePlus 3 & 3T Cross Device Development] Dirk:
Sorry, we're having a misunderstanding. The bug we're talking about has nothing to do with MTP not being the default mode. It's the missing notification with the USB connection options when connecting phone to pc. See here:

https://www.theandroidsoul.com/unable-to-connect-pixel-nexus-to-pc-android-o-fix/

A Google search reveals many Reddit/Oneplus/Google Product Forums etc, threads with people having this issue on Oreo. Consider this.... Oreo penetration is really low right now and there are already many people complaining about this problem. Imagine how bad it's going to get once Oreo is at Nougat levels of user base.

It would be great if the LineageOS team can come up with a fix. After all, isn't that one of the reasons we use custom ROMs? I've been looking for other workarounds too...but all i can see are alternate ways of transfering files that don't require USB. Maybe there's a WiFi solution that i haven't found yet.
[OnePlus 3 & 3T Cross Device Development] EddyH1993:
When I plug my USB lead it shows as a small notification at the bottom of the notification panel and theres no sound or no pop up.

If you expand it and swipe slowly to view the cog icon, click on that to adjust the notification settings, you could change it to high or urgent priority and next time you plug in your cable it will show a notification. Have a look at the screenshots.
[OnePlus 3 & 3T Cross Device Development] joakimbo:
After latest OTA I cannot access twrp. It asks for a password to encrypt data? Any ideas?
[OnePlus 3 & 3T Cross Device Development] Dirk:
Thanks, but we know what the Notification looks like. The bug is that the Notification doesn't appear for a lot of people, therefore making it difficult to enable MTP mode for file transfers.

Don't get me wrong. This isn't LOS specific or anything. The people who are affected are using Oneplus phones on OOS, Nexus 5X on Official Oreo, Pixel users....etc. Basically all the devices that have had Oreo already. It's a Google cockup again which means if we wait for them to fix it, it'll never get fixed. Hopefully the non-Google devs of the world will find a solution.

Can anyone recommend a good WiFi file transfer solution, or is it not worth the effort?
[OnePlus 3 & 3T Cross Device Development] Sam Nakamura:
You're probably looking for a Wi-Fi direct solution, on rare occasions I used "superbeam" from Playstore which is fast and convenient, there are lots of solutions, you may find something better but for the time being it should do the job...
[OnePlus 3 & 3T Cross Device Development] Dirk:
Thanks, i'll check it out.
[OnePlus 3 & 3T Cross Device Development] S4turno:
Not a viable solution for everyone, but I use Syncthing to sync folders between my phone and computer. I haven't used a USB cable for data transfer in months.
[OnePlus 3 & 3T Cross Device Development] caryle:
Does lastest los 15.1 official work fine with open gapps official's setup wizard?:)

---------- Post added at 01:40 AM ---------- Previous post was at 01:38 AM ----------

Xposed beta3 doesn't work fine right? Cause I sometimes have soft restart.
[OnePlus 3 & 3T Cross Device Development] sharkyslo:
Try to install TWRP again.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Just to be absolutely clear...

Below are screenshots of how it works on my phone. I do not have USB debugging enabled and i haven't changed any developer settings other than to enable Advanced reboot.

1. Plugged into PC, but no notification in the status bar. My PC registers the device being plugged it, but cannot see the phone storage.

2. Drag down on the status bar and I can see this notification item.

3. Tap on the item and it expands a bit and provides more information.

4. After tapping it again, I'm prompted to select the choice I want. If I select MTP then my PC sees the internal storage.

Are you saying that you don't get the entry shown for item 2 or 3?
[OnePlus 3 & 3T Cross Device Development] Dirk:
That's exactly what we're saying. Couldn't be any clearer about it. We all know how it's supposed to work.

The trick would be finding out why it happens to some Oreo users and not others. Other than the Android version, what on earth could be a common factor across multiple devices and multiple ROMs, both Custom and Manufacturer? Or maybe it's a fools errand trying to find a commonality and it's just completely random.
[OnePlus 3 & 3T Cross Device Development] the00guy:
Got it, the different kernel may be what's fixing it.
[OnePlus 3 & 3T Cross Device Development] trigonX:
I woke up, and theres a location icon stuck on status bar.. any ideas?
[OnePlus 3 & 3T Cross Device Development] :
Well known issue: https://xdaforums.com/search/thread/3739169?query=location stuck
[OnePlus 3 & 3T Cross Device Development] Playa82:
we already noticed it. the only fix for me now is restart it the phone once every morning. but don't forget to go developer settings and change charging options to mtp.
[OnePlus 3 & 3T Cross Device Development] Dirk:
If people can live without the Location Icon, it can always be disabled in Status Bar settings.
[OnePlus 3 & 3T Cross Device Development] :
USB data transfer notification

Honestly I don't see a real problem:

Since we all doesn't report any issues without logcat, we have usb debugging enabled all the time anyway. This is a karmatic issue: if you are not prepared to get a logcat any time, universe let's you expirience the abscence of the notification. *lol* (only half kidding... ;) )
[OnePlus 3 & 3T Cross Device Development] Playa82:
but is it only the icon ? or does it search for signal all the time ?

if it is just the icon you are right, if not this should be fixed.
[OnePlus 3 & 3T Cross Device Development] :
It should be fixed any way!

If you stop your gps requesting app before the gps is locked, the icon disapears (yeah, really... ;) ). If the gps is locked once, the icon does not disappear since next reboot. You can't tell from the icon if gps is in use or not. Even with no gps request at all, the icon still shows up.

From the sensor activity I guess gps is working flawlessly (not active if not used), but the icon doesn't.

On the other hand: the icon broken (always on) does NOT mean, there is no activity on gps.

The "alwas on" location icon does currently mean: there has been a gps fix between last boot and now.
[OnePlus 3 & 3T Cross Device Development] VincentJoshuaET:
GPS icon can't be hidden, I don't see the option in settings.
[OnePlus 3 & 3T Cross Device Development] Playa82:
i didn't had the phone in deep sleep the last 2 hours and i got the GPS icon stuck again now. :-/

I got chronus widget active with sync every hour. but it doesn't show up the whole day yesterday.
[OnePlus 3 & 3T Cross Device Development] maxauvy:
Do you know where is hidden the "barcode scanner" mode that was present in the 1st nightly? Can't find it in the new UI. Thx!
[OnePlus 3 & 3T Cross Device Development] :
The malfunctioning loc icon is not related to deep sleep. See my last answer: it stays in statusbar after the first gps lock. If you have 2h screen on and a gps lock occurs meanwhile, the icon is there.
[OnePlus 3 & 3T Cross Device Development] megatomic:
I'm not sure I see how a logcat is supposed to work in this situation. It's not like a crash is happening, but maybe the absence of an event would be as obvious to the devs as a crash event would be? We'd need someone to post a logcat whose system is working normally also? I'd be willing to do it if it wasn't a fool's errand (feeling like Don Quixote here lol).
[OnePlus 3 & 3T Cross Device Development] :
If you have adb debug enabled, you will be notified on usb connect - also after a reboot... It's about "we have usb debugging enabled all the time anyway".

To avoid further misunderstandings:

Workaround: enable usb debugging to always get notified on usb pc connection.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Once again, enabling USB debugging and leaving it enabled does not make the notification appear after every reboot. The notification will not appear after reboot no matter what. Toggling USB Debugging, or USB Configuration , after a reboot will make it appear again...but only until the next reboot.

https://www.google.co.uk/search?sou....1.64.psy-ab..1.6.718...0i131k1.0.psRgsoxf8TQ

Edit: If you think about it the answer is somewhat obvious. There's clearly some part of the Android system dealing with USB, a service perhaps, that's supposed to start at Boot but doesn't. Toggling anything to do with USB once the device has started then starts the service. Normal operation resumes. I'm certain that if we pursue this line of reasoning it will lead us to the answer.

[MENTION=5958244]megatomic[/MENTION] [MENTION=5091734]dianlujitao[/MENTION]
[OnePlus 3 & 3T Cross Device Development] blaze95rs:
I have noticed touch input not being properly registered on this ROM. Like when I play games like mini militia, the aim flickers like I am holding down 2 points(very close in location) at the same time on the virtual aimer. This happens only a few times, not always, but I didn't have this problem on lineage 14.1 or OOS. I tried changing kernels and the battery profiles but nothing helps. Though this is not noticeable anywhere else.
[OnePlus 3 & 3T Cross Device Development] pro_drive:
[MENTION=5091734]dianlujitao[/MENTION]

Daul SIM card(China Unicom and China Telecom) were enabled at the same time.

The Telecom one couldn't search any network. But the daul SIM card networks could be searched under ROM Omni 8.1 works fine.

3T. Lineages OS 15.1 20180319

Stock kernel.
[OnePlus 3 & 3T Cross Device Development] megatomic:
I'd say this is a concise summary of the problem. It's not present in OOS 5.0.1 but it's been a problem in LOS since the 0225 experimental build.
[OnePlus 3 & 3T Cross Device Development] trigonX:
I am gonna go back to 14.1 cause this is far from stable. (clean flashed it) My observations:

1) stuck location icon

2) overal design is kinda ugly

3) network data get stuck sometimes for a long time on a slow connection

4) settings in very weird groups

5) cant set all three bottom buttons shortcuts

6) camera app....ehm... no comment needed here I guess...

7) nothing significant new or better in Droid 8 (same applies to stock roms)
[OnePlus 3 & 3T Cross Device Development] :
Sorry, then we have two different variants of this issue: If I have enabled usb debugging, I have the notification each and every time, no matter if rebootet, switched off and on or coming from a dirty flash: no single failure on usb notification. If I disable usb debugging and reboot: no notification. On my device I can reproduce both scenarios 100%.

As soon as usb debugging is enabled, I have no issues any more - even through reboots. You cannsee in the attached logcat, that usb dev-ops isn't touched at any time before the connect. Then you can see switching to mtp (from the notification pull down).

I'm on op3t, though I don't belive, that this makes a difference on this matter. Win 10 on a usb3 port with original cable.
[OnePlus 3 & 3T Cross Device Development] SoMeiBoL:
I do not use xposed
[OnePlus 3 & 3T Cross Device Development] joakimbo:
I second most of the points here. Battery life is also quite bad for me. Snapchat lags as never before (I know it's a **** app, but compared to other ROMs). Also switching ROM until more mature. But props to the dev doing great work. Looking forward to later releases. Thanks
[OnePlus 3 & 3T Cross Device Development] HiBoU974:
I did a clean flash (wipe system + install LOS + GAPPS) on a clean install of first nighty (full wipe) and the ROM is pretty stable.

No location icon

Good battery life

No USB/mtp bug

WiFi access point works
[OnePlus 3 & 3T Cross Device Development] Playa82:
when ? today ? maybe you get the icon tomorrow. let's wait
[OnePlus 3 & 3T Cross Device Development] HiBoU974:
Wait and see, but I have dirty flashed the 19th and had the location icon the 20th, clean flashed the 20th and today no icon...
[OnePlus 3 & 3T Cross Device Development] Playa82:
do you flashed the 19th (weekly) again or the nightly from today (20th) ?