yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] mottenkiller:
Then you should look for differences between your OP3 and the other phones.

Are the other phones running with Android 9, too?

There were connection-issues reported with lot of phones (which used to work earlier) after updating to pie. In those cases it mostly helped to wipe cache of AA-app and update firmware of the receiver (car-side device).

Since AA is working with at least two different OP3 on LOS16 and AA is known for issues like these, I would investigate in this direction:

Did you go through step-by-step google support?

If you did so and you can make sure your car-side device is up to date, I would recommend to contact google support. There is a link to a form at the end of the linked post.

Also it could be useful to read the whole thread following this post. I.e. somebody solved his connection-issues by disabling usb-tethering in his phone's settings.
[OnePlus 3 & 3T Cross Device Development] sky321:
hotspot not working

Thank you so much, you safed me from doing a clean install because of this problem.

Got this error everytime I started the hotspot and hotspot imediately switch back to off status.

My config:

- LOS16.0-20190924

- FW 9.0.5 BL-KM from 5.0.8

- encrypted

- system & data ext4

- open BL

- "Dirty" upgrade from 15.1

- no SU

- opengapps

used TWRP 3.3.0-1 to remove /data/vendor/wifi
[OnePlus 3 & 3T Cross Device Development] LorBer13:
I'm going to fill the Google form to receive some support, I am sure also that the car's fw is up to date (I updated it because of the connection problems).
[OnePlus 3 & 3T Cross Device Development] An68:
Sorry
[OnePlus 3 & 3T Cross Device Development] :
How does per app bg data restrictions relate to the changed location of /data/vendor/wifi (which results in the situation described in the posting you've quoted, if dirty updated between major versions)?
[OnePlus 3 & 3T Cross Device Development] mottenkiller:
Since there is only one DND-setting in pie, I guess this is LOS 16 standard-behavior, but maybe there is a solution for my need.

My alert slider setting is the following:

vibration

priority only

total silence

I would like to act 'priority only' the way, that my starred contacts may ring or notificate me (sound / vibration), but calls/notifications of every contact are shown visually.

'Total silence' should disable sound and any visual notifications.

Sound-side:

Everything is working as expected.

Visual-side:

Unfortunately 'do not disturb' settings may be customized only in general. Means when I disable visual notifications, they are disabled in both 'priority only' and 'total silence'.

I already had a glance on alert-slider customizing via app. Since I do not really want to root, I did not check xposed.

I would be willing to manipulate system files using shell or nano / vi(m) via twrp to reach the desired behavior.

But my thing is more like 'do not disturb'-customization...

For now I have to manualy switch notification-setting in DND.

Tasker could be a possible solution. But as I read, I need root to react in slider-actions.

Any ideas? :)
[OnePlus 3 & 3T Cross Device Development] realtos:
yes u need root and tasker
[OnePlus 3 & 3T Cross Device Development] bogachev:
[MENTION=5091734]dianlujitao[/MENTION] I tried changing my encryption password to something different from my lockscreen PIN for increased security. However, using

vdc cryptfs changepw 'newpw'

fails with

"Raw commands are no longer supported"

According to Gerrit, the changepw feature has been re-added on Aug 19 with commit 0ff3b953f43252294eea79f9cb8deec9bda99bae (can't link to it because I have too few posts).

Have you included this one in your builds? If not, can you please cherry-pick it? I think being able to have a long encryption password is very important considering we have unlocked bootloaders. A 4 digit PIN is too easliy bruteforceable.
[OnePlus 3 & 3T Cross Device Development] :
If you look at https://review.lineageos.org/c/LineageOS/android_system_vold/+/254062, you'll see this is already in all builds since August the 20th.

If you look at https://github.com/LineageOS/androi...bae#diff-c80f40bcaaefdbde60b7008de12ea476R124 you'll see that your command has not enough arguments, so the else is triggered, which prints the error message.

As I'd guess from the code the correct syntax is "vdc cryptfs changepw [type: pin|pattern|password|default] 'oldpw' 'newpw'".

Always read the code you are mentioning... ;)

EDIT: just checked for type pin - working as expected.
[OnePlus 3 & 3T Cross Device Development] dmaster2016:
hello everybody

official lineageos official opengapps.

****NO magisk or similar

"device is not certified" on google play.

I HAVE registered the device ID and still........

oneplus 3t a3010

is it normal for this device?

what will happened?

thank you.:)
[OnePlus 3 & 3T Cross Device Development] djplus:
Read the thread before posting. Use search function.

More here > https://lineageos.org/Safetynet/

Use magisk to pass safetynet. Or Lock Bootloader.
[OnePlus 3 & 3T Cross Device Development] Dirk:
The 3/T is already on the whitelist for Gapps certification. There is nothing to register, and this has absolutely nothing to do with the ROM passing Safetynet.

Adding to the good advice in the previous post, custom kernel as another option.
[OnePlus 3 & 3T Cross Device Development] dmaster2016:
first of all thank you for your response.

i didn't mean to upset anybody.

i bought this this device second hand about tow weeks ago in a rare condition .the device came with something called BLUSPARKS twrp or something like that but ever since I did put a stock oxygen on it just to start from scratch........

when i checked, the developer of this BLUsparks or what ever saying it doesn't mess with the file system.....

what am i missing,or not understanding correctly?!

i really don't mean to upset anybody.

thank you.

---------- Post added at 11:29 AM ---------- Previous post was at 11:27 AM ----------

if he put custom kernel on it doesn't reverting back to stock change it to factory condition?
[OnePlus 3 & 3T Cross Device Development] :
Oh, Bro, first of all you need to understand the mantra of quite some users: "If I can describe an issue with many precise words so everybody can understand my problem, or I can use fewer words loosing the precission or even the context, I'll always go for the latter! Let the people, who are willing to help, guess (so I can complain the helper doesn't understand) and ask - it's wasting their time not mine."

"registered the device ID" could probably mean: registered the device in the device manager of my g account. On the other hand: this is done automatically if you run through first time setup or delete and readd the g account on the running rom. If this is failing for any reason, it may break play protect certification -- I'm not sure, because I've never expirienced a non registered device.

'"device is not certified" on google play.' means: in the app settings of google playstore app the device is shown as uncertified in "play protect certification" (last item in settings; formerly "play store certification").

Some important information is missing at all: fw version, twrp bersion and bootloader configuration. Let's assume stock 9.0.5 fw with bl unlocked and twrp-3.3.1-0.

Now, that we've defined, what we are talking about:

Due to the lack of sources, I don't know if safetynet api relies on play protect certification or vice versa, but I've never observed one is working without tje other. In other words: if safetynet api is passing play protect shows certified - if play protect shows certified safetynet aüi is passing as well. I've never seen one passing without the other.

[MENTION=10055765]djplus[/MENTION] is most probably on the right track, when suggesting to get saftynet api to pass with magisk or relocking the bl (if it's unlocked as I've assumed, but this piece of information is missing). You are right in suggesting a custom kernel (with verified boot patches applied). The most important advice from [MENTION=10055765]djplus[/MENTION] is search before posting (which happens to be xda rule #1):

If [MENTION=9482890]dmaster2016[/MENTION] would have searched for "certified play store", he would have found i.e. (there are many others!):

https://xdaforums.com/oneplus-3/one...eplus-3-3t-t3866517/post79244779#post79244779

If [MENTION=9482890]dmaster2016[/MENTION] would have searched for "safetynet" after finding the above, the issue should have been solved in the first place...

For the record: I've answered this for [MENTION=1763460]Dirk[/MENTION] and [MENTION=10055765]djplus[/MENTION]. I don't care for postings with incomplete and misleading information, that proofes, that the original author doesn't respect the rules he has accepted on signup.
[OnePlus 3 & 3T Cross Device Development] dmaster2016:
first of all my English isn't my native language so i am still trying to understand what you were saying and i am a new user with this device not on XDA and this is the first time that somebody snipers me that way......

i didn't mean to upset and the last time i have checked this is isn't against the low.

i only asked a simple question.

A QUESTION and it turned out to be an exhibition on knowledge.

what i do understand is i need to dig a little more

and don't worry....ho great one! i wont butter you anymore.

only a question for god sake....
[OnePlus 3 & 3T Cross Device Development] :
No. Factory reset wipes data without media.

Now you've managed to make me beg for information: which version of bluspark twrp are you using? I'm not sure if you soft brick your device if you relock the bootloader if you doesn't use official twrp-3.3.1-0.

You should really read the official twrp thread, this thread, the threads about firmware (https://xdaforums.com/oneplus-3t/how-to/firmware-beta-10-t3631166 and https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164) and the thread of the custom kernel, if you are using one. There are many small and big traps (up to soft bricking) you can avoid by reading.

I would also strongly recommend to start from scratch (recovery, firmware and rom) after reading, if you don't exactly know what the prevous owner has done to the device!
[OnePlus 3 & 3T Cross Device Development] dmaster2016:
i didn't see some previous massages apparently.....:eek:

i am aware of saftynet .before this device i had tow more.

i thought i could just ask because i know it is kind of rare....

BTW.....my previous device was oneplus one and there was a problem with the signature for a brief as far as i clearly remember.

i only thought it is a bug or because something the previous owner did.

i am sorry but i am not into kernels or similar so my my knowledge lacks a bit there .i am a "simple" user and most probably not the only one.

i am NOT trying to justify....not at all.....i really want to understand things.

i guess if the store works and also the gmail....i live it like that......i don't want to mess things:eek:

i will read and learn more in the matter.

thank you for all the helpers.
[OnePlus 3 & 3T Cross Device Development] dmaster2016:
i installed magisk as you all suggested i am still whiting for the google play certified(or not) section to appear.

*magisk did show a cts profile false*

overall this is a great ROM.......as you might expect from lineageos.

thank you.:)
[OnePlus 3 & 3T Cross Device Development] djplus:
You can just use the unbrick tool and go to stock 9.0.5 directly.

BACKUP ALL YOUR DATA before using the tool.

Once on stock you can unlock bootloader and then flash latest lineage os build via official twrp.

This two steps will save your precious time asking questions and troubleshooting. As well save time of other people.

Good luck.

Edit. Use the appropriate unbrick tool as per your device.

Is your device a 3T or 3 ??

For 3T -

https://xdaforums.com/oneplus-3t/how-to/op3t-collection-unbrick-tools-t3896765
[OnePlus 3 & 3T Cross Device Development] dmaster2016:
magisk worked!!!

play store says device is certified.

thank you all for the advice and all the help.:):good:
[OnePlus 3 & 3T Cross Device Development] dmukhin:
I have problems probably related to replaced OnePlus 3T display. Very often screen doesn't switch on when woken up from sleep, it remains blank but I can use touch and buttons. Ambient display also seems to be invisible time to time because of this. I have to switch off and on again and maybe once again to make display works. On OnePlus stock there is no such problem. I tried other kernels like Holly Dragon and Maddy but it didn't help with LOS
[OnePlus 3 & 3T Cross Device Development] jerryhou85:
Dear all,

You may notice that I have revised and removed some posts on this thread. I have to do that as this is a development thread and posting posts not related to development is not very respectful to developers and users.

Searching is a great skill to master nowadays as we could easily learn from others' failure/questions. I strongly suggest everyone to learn some search tips either for Google or any other search engine you use.

For example:

How to Search the Internet

Hope you have fun in XDA and learn something along the way to Android Master. :)

Jerry

Forum Moderator
[OnePlus 3 & 3T Cross Device Development] realtos:
okay but why tell us this though? :)
[OnePlus 3 & 3T Cross Device Development] dmukhin:
Not sure, maybe somebody here had some experience to overcome it. It's quite common for this device to have replaced display
[OnePlus 3 & 3T Cross Device Development] :
I've seen some reports of this in different source build roms.

Would you get me a logcat when the display doesn't switch on, please? And would you get me the output of 'adb shell su -c "cat /sys/devices/virtual/graphics/fb0/msm_fb_panel_info"', please? It should look like this:

ingo@adler /tmp $ adb shell su -c "cat /sys/devices/virtual/graphics/fb0/msm_fb_panel_info"
pu_en=0
xstart=0
walign=0
ystart=0
halign=0
min_w=0
min_h=0
roi_merge=0
dyn_fps_en=0
min_fps=0
max_fps=0
panel_name=samsung s6e3fa5 1080p cmd mode dsi panel
primary_panel=1
is_pluggable=0
display_id=
is_cec_supported=0
is_pingpong_split=0
is_hdr_enabled=0
peak_brightness=0
blackness_level=0
white_chromaticity_x=0
white_chromaticity_y=0
red_chromaticity_x=0
red_chromaticity_y=0
green_chromaticity_x=0
green_chromaticity_y=0
blue_chromaticity_x=0
blue_chromaticity_y=0
ingo@adler /tmp $

EDIT:

Does anybody know, if this occurs only on 3T, ot if replaced 3 panels are effected, too?
[OnePlus 3 & 3T Cross Device Development] dmaster2016:
i saw many general questions on XDA and never i saw someone gets "punished" for that(i am not talking about you,you are doing you're job)

i personally thinks that my general point was genuine.

please......i don't mean to upset anybody...

but the fact is.....junior/simple users can contribute too.

anybody CAN learn from anybody period.

even android masters.

how to search the internet?!

PC world exists wayyyyy before android and even google and I was there!so......

ho wait.....that was mean wasn't it ?!(example)

bare with me a second......

what is it with you guys and getting some humility?!

that was my my point.

and now to my specific issue....that was resolved thanks to the community here:

saying that "device is not certified" on google play is not development related?!

i don't mean to be rude i really want to understand something:

for me and a lot of users opengapps is inseparable....

so for the sake of general experience it isn't important?

i didn't expect the developer to take responsibility for something he didn't built/supports directly(opengapps)

i was just looking at the bigger picture,that's it.

i will attach more info on my hardware next time...that I learned....but i will never disrespect anybody!

please somebody......at least.....tells me that i am making kinda since in my general point.

i am done excusing........and i do have a point.

thank you:)
[OnePlus 3 & 3T Cross Device Development] jakito:
It has happened to me too. I broke my OP3 screen and sent it to OP to repair it.
[OnePlus 3 & 3T Cross Device Development] :
Thanx.

Would you get me a logcat when the display doesn't switch on, please? And would you get me the output of 'adb shell su -c "cat /sys/devices/virtual/graphics/fb0/msm_fb_panel_info"', please?
[OnePlus 3 & 3T Cross Device Development] jakito:
I'll try to get the logcat, but it's just so rare that I forget it.

About the output of that command, does it also need to be during the "not turning on" problem? Or can it be while everything is ok?
[OnePlus 3 & 3T Cross Device Development] :
The cat on the info file is just to see, if something has changed by the replacement panel (I giess nothing is changed, but who knows?). It can be done at any time. For the logcat it's important that the "stay black" has just happend.
[OnePlus 3 & 3T Cross Device Development] djplus:
safetynet fails on magisk - more info here > https://twitter.com/topjohnwu/status/1179438355626393600
[OnePlus 3 & 3T Cross Device Development] dmaster2016:
i see that the word magisk doesn't appear there but thank you for showing that.

right now the issue appear to be fixed for me....i will follow this.....

BTW it is clearly says: "some custom ROM users" and my problem began WITHOUT having magisk installed....thats why it was a little weird.

i have uninstalled magisk and it is still ok with the google play....so i have to be optimistic and trust what i see :)

thanks. ;)
[OnePlus 3 & 3T Cross Device Development] :
The statement from [MENTION=4470081]topjohnwu[/MENTION] you are quoting relates to huawei devices. Why should Oneplus devices be affected?

There are many statements out there, that oppo/oneplus isn't effected, i.e.: https://www.forbes.com/sites/jaymcg...impact-android-in-one-clear-way/#2222af635317

Despite of this: yesterday evening 6 pm UTC+2 safetynet api was passing ctsprofilematch, this morning 8 am it fails... :(

BTW: after flashing a new build (incl. wipe caches), playstore shows uncertified... :(

EDIT: according to https://support.google.com/googleplay/answer/1727131?hl=en&ref_topic=3364265 A3000 is still in the list of supported devices (in the pdf). I wonder why A3003 and A3010 arn't listed, though for 5, 6 and 7 all models are listed?
[OnePlus 3 & 3T Cross Device Development] djplus:
So now either locking bootloader or flashing custom kernel remain the two viable options .

After using so many roms the roms which work perfect and stable are only two roms

1. Nlos thanks [MENTION=4405529]nvertigo67[/MENTION] & [MENTION=5091734]dianlujitao[/MENTION]

2. Sultans 14.1 thanks [MENTION=4800121]Sultanxda[/MENTION] & [MENTION=3916420][denser][/MENTION]

I always come back to sultan's rom. It seems its the most optimised rom for oneplus 3. It passes safetynet. No need to root. No need to customize the kernel. App management is perfect. Very low standby and active drain.

[MENTION=3916420][denser][/MENTION] has maintained the ROM over a year now, but its not updated since two months. Hope he continues to update it or atleast someone from the community decides to do so.
[OnePlus 3 & 3T Cross Device Development] djplus:
Then ?
[OnePlus 3 & 3T Cross Device Development] knizmi:
MagiskHidePropsConf works quite well. It' s a Magisk module, so you just install it, run it, change your ro.build.fingerprint to official OnePlus 3t, and you are ready to go.

More info here - https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/README.md

EDIT: You could also install the SafetyPatch module instead. It does pretty much the same as MagiskHidePropsConf.

The good thing is that it requires no config; you install it and done.

Cons: You can't choose the fingerprint. It uses one for Huawei Pro 20 (or something like that). This means that your phone will be recognized as a Huawei and you'll have to confirm a nasty warning after every boot that there is something wrong with your system.
[OnePlus 3 & 3T Cross Device Development] :
That's a good one...

I've do e some test builds with different fingerprints. To now advance. My last build was with 9.0.5 fingerprint - same result.

Then [MENTION=5354072]knizmi[/MENTION] made my day!

While reading through the documentation of the module, my eye was caught by the section https://github.com/Magisk-Modules-R...E.md#matching-the-android-security-patch-date . On lineage we have:

ro.build.version.security_patch=2019-09-05

So I've installed the module, set exectly the same fingerprint ("OnePlus/OnePlus3/OnePlus3T:9/PKQ1.181203.001/1907311932:user/release-keys") as it already was in my test build, rebooted and - voila - sf passed again. Then I've checked the the sec patch level:

ingo@adler /usr/local/src/los16 $ adb shell getprop ro.build.version.security_patch
2019-08-01
ingo@adler /usr/local/src/los16 $

Now I can answer the good one: g hasn't checked if fingerprint is matching sec patch level until tonight. For now the solution is the above module, or faking ro.build.version.security_patch (it's in build.prop) to the matching date for the current fingerprint the los builds are using (which is ""OnePlus/OnePlus3/OnePlus3:9/PKQ1.181203.0

01/1905251415:user/release-keys" for 3; and "OnePlus/OnePlus3/OnePlus3T:9/PKQ1.181203.

001/1905250152:user/release-keys" for 3t): 2019-04-01 (OOS 9.0.2).

The matching of sec patch level and fingerprint is mandatory, no matter of bl state, magisk or kernel verity patch.

Since los (or aosp for that matter) are using the aosp patch level for builds, I don't see a smart way out of this so that it works out of the box. The cleanest way would be setting ro.build.version.security_patch on build time from the device tree, and from build/make (https://github.com/LineageOS/android_build) something like ro.build.aosp_version.security_patch to the actual sources sec level. I need to think about this.

Thanx to [MENTION=5354072]knizmi[/MENTION] for showing me the direction to look in, and [MENTION=10055765]djplus[/MENTION] for verifying that sf still passes on stock oos!

OT: [MENTION=10055765]djplus[/MENTION]: how many oneplus3/ts do you have hands on??? ;)
[OnePlus 3 & 3T Cross Device Development] knizmi:
Yup, when you use the preconfigured devices it sets both the fingerprint and the security patch date. Neat.

However, I tried what you suggested - changed the fingerprint back to the original LineageOS one, modified ro.build.version.security_patch to 2019-08-01 and I get a CTS profile fail. To me it looks like both values have to be set.
[OnePlus 3 & 3T Cross Device Development] :
For the current los' fingerprint (which is from 9.0.2) use 2019-04-01.

I'll push a commit for 9.0.5 fp (2019-08-01) later today.

EDIT:

Done. https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/259997
[OnePlus 3 & 3T Cross Device Development] djplus:
I have a single device. For calls i use nokia.

Actually I reverted to stock as i was checking magisk. I never save any important stuff on my phone.
[OnePlus 3 & 3T Cross Device Development] :
This is a really dirty hack and I don't know if that triggers any unwanted side effects, but together with https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/259997 this patch allows safetynet api to pass again:

https://github.com/nvertigo/android...mmit/102e27b2819115740e5136ad4105f762aa38ad33

[MENTION=5091734]dianlujitao[/MENTION]: I'm assuming you doesn't like that one. If I'm wrong, drop me a note and I'll push it.
[OnePlus 3 & 3T Cross Device Development] knizmi:
As far as I know LineageOS will reject any patches that are submitted just for the sake of passing SafetyNet, but it's worth a shot, I guess.
[OnePlus 3 & 3T Cross Device Development] PiereMallao:
I have already LineageOS 15 and TWRP 3.3.1 installed. Do i need to downgrade to the Stock-Rom or is this only for those who have only a Stock-Rom installed older then 9.0.2?

What to i need to do to upgrade to 16? Is it enough to Wipe data/factory reset and then flash the zip?