yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] Uumas:
Of course formatting deletes everything including internal storage!
[OnePlus 3 & 3T Cross Device Development] Uumas:
Yes, I did. Changing filesystem completely changes the way data is handled, so it wouldn't be possible even in theory to change fs without losing all data.
[OnePlus 3 & 3T Cross Device Development] 9Lukas5:
Are you sure didn't want to write it DOES wipe your data?

I'm using f2fs since the beginning and hadn't ever any problems (even with the updated f2fs drivers)

But, I guess (as reported before if I'm not mistaken), it doesn't matter if you change to ext4 or reformat with the new f2fs drivers and copy your stuff back.

L
[OnePlus 3 & 3T Cross Device Development] 9Lukas5:
Dude, you can't reformat /data without loosing all your stuff in data partition aswell as your stuff on the sdcard.

If you didn't loose your files, the format didn't work ?

L
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=5924669]BlankBlackDroid[/MENTION]

Couldn't agree more
[OnePlus 3 & 3T Cross Device Development] sonst-was:
Hi everyone,

since end of December I have a problem with my OP3 with Lineage OS 14.1. From time to time the phone eats the battery away like fresh pancakes. I noticed it the first time in the last week of december (with the nightly from December 1st or 29th). Since then I had the issue from time to time with all nightlies since then (I installed the one from January 5th, 19th and 26th).

The battery screen shows that "Android-System" and "Android OS" (or "Lineage OS") is using most of the battery, but I'm unable to see the real problem. I also tried to find the issue with Wakelock Detector but other than that my phone hasn't been in sleep the whole day I was unable to find any clues.

I've uploaded a few screenshots of the battery info of Android and Wakelock Detector here: https://imgur.com/a/bQeZE

Does anyone has the same issue or does anyone knows what I could try?

Greeting

sonst-was
[OnePlus 3 & 3T Cross Device Development] mk_1996:
+1

Formatting is impossible without a data wipe in data partition. Make sure you use the latest twrp
[OnePlus 3 & 3T Cross Device Development] ageback:
Hi [MENTION=5091734]dianlujitao[/MENTION] dear dev, I'm from China. First I want to thank you for your work on this ROM. Now I have a problem, hope you can help me.

I have two SIM cards. One is China Telecom and the other is China Mobile. When I use them together in my Oneplus 3T, then the China Telecom sim has no network signal, no matter it's in which sim card slot. If I use China Telecom sim card alone, it has network but I can use only 3G not 4G(LTE). Can you please fix the China Telecom issues?

Now I have to flash OOS to use the 2 SIM cards together without issues.
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
You can manually set CMCC sim slot network mode to any non-CDMA ones, then CT sim should work.
[OnePlus 3 & 3T Cross Device Development] ageback:
I'll try your suggestion next time I flashing LineageOS. Thanks!:)
[OnePlus 3 & 3T Cross Device Development] :
I'm observing kernel wakelocks (mainly NETLINK, timerfd and qcom_rx_wake) increasing Screen Off Awake from formerly 2-4 % to 9% and increasing screen off bat drain from <0.5%/h to >1.3%. (For wifi always on.)

I also observed WhatsApp complaining about "waiting for internet connection" on its backups. This happens as well with "wlan always on", as with "only if connected. Mobile data is enabled, anyway. I have to toggle wifi, to continue the backup.

I highly doubt it's device tree or kernel related, because I expirienced something very similar on my chagallwifi (since this is a wifi only exynos powered device, I belive we can reasonable exclude kernel- or device tree changes): wlan_rx_wake keeps the device awake with screen off and increases idle drain from formerly 0.1% to 1%...

After checking lineage (non-kernel and non-device-tree) commits, I'm quite clueless because I havn't found anything that seems related to me. I'm not even sure if it's rom related at all, on the other hand: how can an app trigger that massive amount of kernel wake locks? Could this be caused by some app update?(BTW: I uninstalled k9 to exclude, and it can't be whatsapp, because it's not installed on chagallwifi.)

I also belive, we both are not the only ones suffering from this, because some custom kernels (like boeffla) have implemented a kernel wakelock blocker with NETLINK, timerfd and qcom_rx_wake blocked all together - why should [MENTION=947981]Lord Boeffla[/MENTION] write a dedicated wl blocker, if those wls arn't commonly expirienced?

The question is: what the heck is triggering these?

Meanwhile I found, if I set wifi to "only if connected" the screen off drain is down to 0.6-0.8 again. I havn't tested a wl-blocker enabled kernel, because (like my suggestion with wifi settings) this is only a workaround for the symptoms, but I want to get down to the cause.
[OnePlus 3 & 3T Cross Device Development] sonst-was:
Interestingly I did experience this issue a few times over night where I have WiFi and mobile data disabled. I will change the WiFi setting as you suggested in the mean time and see if anything changes.
[OnePlus 3 & 3T Cross Device Development] :
As stated above: this is no real solution and the drain does NOT went down to the former values.

To realy solve this, we need to know, what exactly is triggering the kernel wakelocks.
[OnePlus 3 & 3T Cross Device Development] 9Lukas5:
Hey guys, if I enter the about phone menu from dialer with code '*#*#4636#*#*', under the three dot menu, IMS state it says IMS not registered.

Also if I'm going to the dialer settings->call accounts->my simcard->IMS-settings com.android.phone fc's and my signal goes a way a few seconds.

Is there something with LOS and IMS service not working, or should that work fine and I have to figure out whats going on here?

L

Edit: Attached a logcat with filter for Warnings and worse

The trouble is starting with a NoSuchMethodError:

02-04 14:57:01.339 3972 3972 E AndroidRuntime: FATAL EXCEPTION: main
02-04 14:57:01.339 3972 3972 E AndroidRuntime: Process: com.android.phone, PID: 3972
02-04 14:57:01.339 3972 3972 E AndroidRuntime: java.lang.NoSuchMethodError: No static method shallTransmitStaticImage(Landroid/content/Context;)Z in class Lorg/codeaurora/ims/utils/QtiImsExtUtils; or its super classes (declaration of 'org.codeaurora.ims.utils.QtiImsExtUtils' appears in /system/framework/telephony-common.jar)
02-04 14:57:01.339 3972 3972 E AndroidRuntime:	at com.qualcomm.qti.ims.ImsSettings.displayStaticImageOptions(ImsSettings.java:202)
02-04 14:57:01.339 3972 3972 E AndroidRuntime:	at com.qualcomm.qti.ims.ImsSettings.onResume(ImsSettings.java:87)
02-04 14:57:01.339 3972 3972 E AndroidRuntime:	at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1270)
02-04 14:57:01.339 3972 3972 E AndroidRuntime:	at android.app.Activity.performResume(Activity.java:6788)
02-04 14:57:01.339 3972 3972 E AndroidRuntime:	at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3431)
02-04 14:57:01.339 3972 3972 E AndroidRuntime:	at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3494)
02-04 14:57:01.339 3972 3972 E AndroidRuntime:	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2757)
02-04 14:57:01.339 3972 3972 E AndroidRuntime:	at android.app.ActivityThread.-wrap12(ActivityThread.java)
02-04 14:57:01.339 3972 3972 E AndroidRuntime:	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1496)
02-04 14:57:01.339 3972 3972 E AndroidRuntime:	at android.os.Handler.dispatchMessage(Handler.java:102)
02-04 14:57:01.339 3972 3972 E AndroidRuntime:	at android.os.Looper.loop(Looper.java:154)
02-04 14:57:01.339 3972 3972 E AndroidRuntime:	at android.app.ActivityThread.main(ActivityThread.java:6186)
02-04 14:57:01.339 3972 3972 E AndroidRuntime:	at java.lang.reflect.Method.invoke(Native Method)
02-04 14:57:01.339 3972 3972 E AndroidRuntime:	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:889)
02-04 14:57:01.339 3972 3972 E AndroidRuntime:	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:779)
[OnePlus 3 & 3T Cross Device Development] mk_1996:
If you've been dirty flashing all along,i think its time to clean flash. Maybe installing the latest nougat firmware could solve the issue.
[OnePlus 3 & 3T Cross Device Development] 9Lukas5:
Yeah, could be time by now^^ I'm consider waiting for the official nightlies of Oreo to make a clean flash, as the ims settings is a thing, I don't need to touch on a daily base ?

L
[OnePlus 3 & 3T Cross Device Development] mk_1996:
You still on nougat fam? Just switch to oreo already?
[OnePlus 3 & 3T Cross Device Development] 9Lukas5:
So you're saying nothing big that's not working on 15.1? ??

L
[OnePlus 3 & 3T Cross Device Development] :
Already great as daily, stable driver (no FC's, no reboots, ...), at least for me.
[OnePlus 3 & 3T Cross Device Development] mk_1996:
+1. Though i tried the alpha build for only a day and it was too early to judge the battery life but it was quite good. Will jump to LOS 15.1 once its in beta.
[OnePlus 3 & 3T Cross Device Development] drmcatchr:
Head's up guys, trying to dirty flash the latest lineage-14.1-20180209-nightly ended up in TWRP getting stuck at patching system image unconditionally. Thankfully was able to restore, do make a backup before you flash this one. Also there is a privacy error, while trying to download from the server.

[IMG="Error"]https://s17.postimg.org/tjc18nwbz/Screenshot_from_2018-02-12_00_04_56.png[/IMG]
[OnePlus 3 & 3T Cross Device Development] gcsuri:
Hi, check your system date and time.
[OnePlus 3 & 3T Cross Device Development] devnerd:
Yes that could be the issue.

Dirty flashed it on two phones since Friday and had no issues at all so far. I flashed it through the official TWRP 3.2.1-0 via sideload
[OnePlus 3 & 3T Cross Device Development] xpissio:
https://review.lineageos.org/#/c/206798/

[emoji39]
[OnePlus 3 & 3T Cross Device Development] mk_1996:
Yay!
[OnePlus 3 & 3T Cross Device Development] grant3r:
volte(jio) not working on 3t

i recently flashed the latest build with twrp 3.2.1(this is the first time im trying flashing a custom rom) and then gapps. when i try to call via jio network it is showing call ended. i dont know what mistake i did ? can anyone help me with this???pls
[OnePlus 3 & 3T Cross Device Development] nitz2889:
Make sure you have latest nougat open beta firmware not oreo.

Enable "improve voice call using lte services" or something like this in settings, network, sim settings.

If you dont have correct firmware better do a clean flash again.

And flash in the order, firmware-rom-gapps.
[OnePlus 3 & 3T Cross Device Development] grant3r:
I did trying with stable nougat firmware+rom+gapps....but no use

But i'll try with beta firmware once again

Can any of the 3t user respond whether volte is working or not on your device with this rom running? Thanks in advance!
[OnePlus 3 & 3T Cross Device Development] Yamato-san:
I'm sorry, I'm probably an idiot, but I can't find which is the latest beta firmware/modem for OP3T with LOS 14.1.

Really idiot, this is this OnePlus3T_Beta15-(19-9-17)-FIRMWARE-flashable.zip https://androidfilehost.com/?fid=961840155545597164, have I right?
[OnePlus 3 & 3T Cross Device Development] mk_1996:
I would recommend you to flash the stable nougat firmware.
[OnePlus 3 & 3T Cross Device Development] Yamato-san:
OK, but which is stable?
[OnePlus 3 & 3T Cross Device Development] xpissio:
Open Beta 15.
[OnePlus 3 & 3T Cross Device Development] Yamato-san:
But... this not the same beta in my post #6262?
[OnePlus 3 & 3T Cross Device Development] xpissio:
They just merged some things for Wiki about Oreo and related Gapps.

(On the OnePlus3 wiki page we can read that he supports 15.1 version)
[OnePlus 3 & 3T Cross Device Development] mk_1996:
Aaaand its official. Enjoy oreo guys?
[OnePlus 3 & 3T Cross Device Development] Diaze:
Link for official 15.1 ?
[OnePlus 3 & 3T Cross Device Development] Mcenzie:
https://download.lineageos.org/oneplus3
[OnePlus 3 & 3T Cross Device Development] pcesar.cercal:
Firmware for oneplus 3 lineage 15.1

So lineage 15.1 is oreo 8.1?

for oneplus 3 we have to flash beta 31 firmware correct?
[OnePlus 3 & 3T Cross Device Development] Mcenzie:
Correct
[OnePlus 3 & 3T Cross Device Development] pijas82:
New thread?
[OnePlus 3 & 3T Cross Device Development] mk_1996:
Not trying to be rude but you could've searched instead of asking. It would have taken less than 10 secs
[OnePlus 3 & 3T Cross Device Development] xpissio:
There's already, and probably he will update it tomorrow.
[OnePlus 3 & 3T Cross Device Development] PavJhita:
Yes flash latest beta for the firmware. If anyone has questions about the ROM, I am running it right now, feel free to ask questions.

It's awesome.
[OnePlus 3 & 3T Cross Device Development] :
If we don't flash ob31 but keep the stable 5.0.2 is it okay? Or it's necessary to have only ob31.. Thank you in advance
[OnePlus 3 & 3T Cross Device Development] hc8708:
Can you please confirm if OOS camera port listed on the first page of this works in 15.1?
[OnePlus 3 & 3T Cross Device Development] PavJhita:
I think that this would be fine, however, I am not 100% sure. Just to be on the safe side, just flash the open beta and then lineage.

---------- Post added at 12:28 AM ---------- Previous post was at 12:26 AM ----------

It does work, just tested it for you. However, you're far better off using the Google Camera mods for superior quality.
[OnePlus 3 & 3T Cross Device Development] hc8708:
There are so many of Gcam mods I can't figure out. Can you please suggest?
[OnePlus 3 & 3T Cross Device Development] theo.j22:
I use the one by SKULLSHADY, try that
[OnePlus 3 & 3T Cross Device Development] PavJhita:
Arnova or Skul Shady
[OnePlus 3 & 3T Cross Device Development] S4turno:
Use one of the apk's on the first post of this thread: https://xdaforums.com/oneplus-3/how-to/modded-google-camera-hdr-60fps-video-t3658552

Follow the "suggested settings" guide and install the front camera fix if you're able to.
[OnePlus 3 & 3T Cross Device Development] hc8708:
Thanks guys :)
[OnePlus 3 & 3T Cross Device Development] S4turno:
This is my mirror for all OP3/3T LineageOS 14.1 builds since 2017-07-27:

- celsoazevedo.com/files/android/oneplus3-lineageos/

I though I'd share this here since LOS 15.1 is out and old builds will soon be removed from the download page.

I've uploaded these files to the Internet Archive (IA). Sadly download speeds are not the best, but files will stay online for a long time. Checksums are hosted by me, the idea is that the checksum verification will fail if someone modifies the files on IA's servers.

I also archived two complete weeks of builds for all supported phones: 20180212 to 20180217 and 20180219 to 20180224.
[OnePlus 3 & 3T Cross Device Development] negiwryk:
Tried to upgrade my op3t without wipping data and run into TWRP 7 error (verify digest file missing).

I used OOS 5.0.0 firmware + modem (from https://xdaforums.com/oneplus-3t/how-to/firmware-modem-collection-flashable-zips-t3565535) but looks it isn't the good firmware.

What is the required firmware on op3t for lineage 15.1 ?

Sorry if it's a stupid question, I dunno why my upgrade failed ...
[OnePlus 3 & 3T Cross Device Development] S4turno:
Check the 15.1 thread, people have shared the right firmware there.

OP3: open beta 31

OP3T: open beta 22
[OnePlus 3 & 3T Cross Device Development] negiwryk:
Thank you, my phone is now fully working again and on 15.1 !
[OnePlus 3 & 3T Cross Device Development] HAN216256:
Install 15.1lineageos oneplus3t error 7
[OnePlus 3 & 3T Cross Device Development] highdiver_2000:
Check your TWRP version
[OnePlus 3 & 3T Cross Device Development] Kurt Krummbein:
... and the firmware (guess you have to reboot to recovery to get the updated firmware acitve).

Gtz

Kurt

P.S.: ... and off cause, go to the right thread: [ROM][Alpha] LineageOS 15.1 for OnePlus 3/3T :)
[OnePlus 3 & 3T Cross Device Development] HAN216256:
This is the latest version!

！！
[OnePlus 3 & 3T Cross Device Development] unimke:
You guys need to try LOS 15.1 first build. Really good so far..??... For root, su ad-on 14.1 still works.
[OnePlus 3 & 3T Cross Device Development] Yamato-san:
I try it, but on still only "Setup wizard has stoped" . OpenBeta31-FIRMWARE+MODEM, lineage-15.1-20180226-nightly-oneplus3-signed, open_gapps-arm64-8.1-nano-20171215-UNOFFICIAL

Oho, bad gapps, with MindTheGapps-8.1.0-arm64-20180223_195845 works all fine.
[OnePlus 3 & 3T Cross Device Development] Yamato-san:
I have a weird problem. When I make a screenshot, it is damaged, it can not be displayed. But if I restart my smartphone, then this screenshot is OK. For a long time I did not make a screenshot, so I do not know what version of LOS it is related to, or whether it's at all with LOS. Anyone have any idea what to do with it?
[OnePlus 3 & 3T Cross Device Development] Uumas:
There's also official opengapps now if you want to use them.
[OnePlus 3 & 3T Cross Device Development] trigonX:
So I am on this 14 LOS because 15 is in alpha state still and to be honest I was on stock rom since the day 1 so I had Android 5.0.1 but I was NOT impressed at all... This Lineage OS is excellent and I only have one bug. The fingerprint unlock is sometimes unresponsive... No sure why. Did you guys see such a behaviour?
[OnePlus 3 & 3T Cross Device Development] Uumas:
I never experienced that. Make sure you're using the correct firmware. And LOS 15.1 is stable, not alpha and I've had no problems with it.
[OnePlus 3 & 3T Cross Device Development] trigonX:
Yes Iam on correct fw. And check Lineage OS first post at the end - version info: alpha...
[OnePlus 3 & 3T Cross Device Development] pitrus-:
I can only concur, I'm running daily builds of LOS 15.1 since two weeks ago and I'm very pleased with performance and functionality.

My daily LOS 15 builds can be found here -> https://lineageos.wickenberg.nu
[OnePlus 3 & 3T Cross Device Development] Uumas:
It's just a leftover the OP didn't remember to change when the official builds started.
[OnePlus 3 & 3T Cross Device Development] trigonX:
Damn ? I wouldnt install this if I knew better ?
[OnePlus 3 & 3T Cross Device Development] unimke:
Guys! Any forum for lineage 15.1??
[OnePlus 3 & 3T Cross Device Development] Fobos531:
Really? Is it that hard to take the effort to look a little bit down the ROM list in the cross device development section?

https://xdaforums.com/oneplus-3/one...ment/rom-lineageos-15-1-oneplus-3-3t-t3739169
[OnePlus 3 & 3T Cross Device Development] delaya73:
Hello.

What is the latest recommended version of firmware + modem for LineageOS 14.1 for OP 3T?
[OnePlus 3 & 3T Cross Device Development] mk_1996:
It is the last stable nougat firmware.
[OnePlus 3 & 3T Cross Device Development] delaya73:
I'm interested in a separate file with the firmware and modem that can be installed using TWRP.

Please link.
[OnePlus 3 & 3T Cross Device Development] mk_1996:
Use the search function. You'll get what you want
[OnePlus 3 & 3T Cross Device Development] delaya73:
Thanks.
[OnePlus 3 & 3T Cross Device Development] trigonX:
Guys I have this 14.1 for quite some time now and its all great except my WiFi is dropping sometimes... Is there a way to fix this? I tried searching it here but no luck... Check the screen...
[OnePlus 3 & 3T Cross Device Development] Dirtystirix:
Did you found any fix?
[OnePlus 3 & 3T Cross Device Development] amplatfus:
LineageOS 14.1 for OnePlus 3T

Hi,

Could you please help me to find the latest LineageOS 14.1 ROM zip file? I cannot find it any more on official servers and I didn't find it on web until now.

Thank you!
[OnePlus 3 & 3T Cross Device Development] devilsworkshop:
Why do you need it? It would have outdated security patches. For daily use, try sultan's 14.1 builds. Sultan himself has stopped making builds, but there's someone on the thread continuing the builds with his sources.

If you'd rather not use an unofficial build, try the official 15.1. It works well.
[OnePlus 3 & 3T Cross Device Development] S4turno:
I have a copy here:

But as the guy before me said, 15.1 is stable and it's what we should use now.
[OnePlus 3 & 3T Cross Device Development] :
If one insists on using 14.1, it's absolutly mandatory to build from source, since all the asb patches since February are missing from the latest official build:

https://review.lineageos.org/#/q/project:LineageOS/android_build+branch:%5E.*cm-14.1.*

For the standrad user not knowing how to build los from source, [MENTION=4487956]S4turno[/MENTION]'s advice to use 15.1 is absolutly mandatory to have a build without serve security hazards!
[OnePlus 3 & 3T Cross Device Development] jianwen03:
Yo guys I think this commit:

https://review.lineageos.org/#/c/LineageOS/android_packages_apps_Calendar/+/231627/

broke the calendar app & now it's stuck at 1 January 1970

How do i report this to the lineage team?
[OnePlus 3 & 3T Cross Device Development] Dirk:
Not the only thing stuck in 1970 apparently! :eek:
[OnePlus 3 & 3T Cross Device Development] :
https://wiki.lineageos.org/bugreport-howto.html

Does it work again, if switch to English language?
[OnePlus 3 & 3T Cross Device Development] jianwen03:
Tried on both English UK & US. Google Calendar keeps crashing. Same issue on my P024.

No issues on previous own build (28 Sept). Only calendar related changes I could narrow down to is:

https://review.lineageos.org/#/q/st...ject:LineageOS/android_packages_apps_Calendar

Matlog didn't record any errors while opening Calendar, only on Google Calendar.

:crying:
[OnePlus 3 & 3T Cross Device Development] :
The change is just some translation strings. No English strings (no matter which English version you use is effected).

More important: the patches are for com.android.calendar (obviously the rom shipped calendar app), but the crash from the incomplete logcat is from com.google.android.calendar (obviously the closed source version for calendar from google). So the commit in question can't be the cause for the crash - just not possible.

May I kindly ask, if you've choosen to replace com.android.calendar by com.google.android.calendar, or if you've choosen to install the latter from playstore?

If you have com.android.calendar in place, check how the rom shipped com.android.calendar is behaving?

BTW: The logcat is quite pointless. Important parts are filtered, the lines are crippled (ppid missing).
[OnePlus 3 & 3T Cross Device Development] jianwen03:
Installed latter from apkmirror.

Stuck in 1 January 1970. (Full?) log attached.

Reported to jira using

Device: P024

Last working build: lineage-14.1-20181020-nightly-P024-signed.zip

Affected build: lineage-14.1-20181027-nightly-P024-signed.zip

Luckily P024 is still having official cm-14.1.
[OnePlus 3 & 3T Cross Device Development] Rapoooo:
cm-14.1-20161113-UNOFFICIAL-oneplus3 - https://nyyu.tk/cm/
[OnePlus 3 & 3T Cross Device Development] mido25:
Thanks for the heads up buddy. Care to link to the commit which fixed battery icon. I believe it's a fix in source. Thanks in advance.
[OnePlus 3 & 3T Cross Device Development] simmeone:
Thank you for clearing, I wasn't sure if you need firmware 3.5.5 before flash CM 14.1
[OnePlus 3 & 3T Cross Device Development] ivicakc:
Firmware is included, no need to flash it separately..
[OnePlus 3 & 3T Cross Device Development] Rapoooo:
cm-14.1-20161114-UNOFFICIAL-oneplus3.zip - https://nyyu.tk/cm/
[OnePlus 3 & 3T Cross Device Development] EP2008:
This thread is for official builds. These unofficial builds seem to be different from the official builds (both from the changelog and file size).
[OnePlus 3 & 3T Cross Device Development] Rapoooo:
[MENTION=763497]EP2008[/MENTION] changelog - https://nyyu.tk/jenkins/job/cm14.1_oneplus3/changes
[OnePlus 3 & 3T Cross Device Development] EP2008:
I follow the unofficial builds, but this thread is for official builds. Should we be posting both builds on this thread? I don't think OP intended this thread to be a build dump (just like the mess it caused on the original cm14.x thread that taker18 started).
[OnePlus 3 & 3T Cross Device Development] dheerajverma143:
Thnkz