yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] lokeshjt:
Addiing these to build.prop enabled the toggle for volte but IMS status shows it as not available(screenshot attached), and when I make a call it still drops to 2g/3g. Do you think we should still try building with the XML changes or the problem is somewhere else?
[OnePlus 3 & 3T Cross Device Development] Geenwor:
Hi all. Can anyone answer me why builds coming so slowly now? Before build servers were down builds was ready every day.
[OnePlus 3 & 3T Cross Device Development] Imnoa:
Builds are weekly instead of nightly now, but the last build did not run or has failed I guess, you can check buildkit
[OnePlus 3 & 3T Cross Device Development] :
I'm not sure. You can try nlos. Though it's 16.0 it has this commit over plain los 16.0: https://github.com/nvertigo/android...f06e7b5#diff-8479f823b5e4d42632a0336a42c68c78

Maybe apns-conf.xml, Phone.apk and CarrierConfig.apk arn't the only places with mcc/mmc configurations. Maybe framework-res.apk.
[OnePlus 3 & 3T Cross Device Development] remedya:
I've built unofficial signed yesterday. I also noticed the GPS changes were yesterday merged.
[OnePlus 3 & 3T Cross Device Development] PTuT:
Does your include GPS changes?
[OnePlus 3 & 3T Cross Device Development] :
https://lineageos.wickenberg.nu/oneplus3/

Latest build ;)
[OnePlus 3 & 3T Cross Device Development] remedya:
I'm not sure as the GPS changes were being merged around the time I was syncing the source code.
[OnePlus 3 & 3T Cross Device Development] giovanniro98:
[MENTION=5091734]dianlujitao[/MENTION]

There is a very big problem with Android 10 and chrome, the UI freeze so frequently that makes chrome unusable sometimes, already reported by Android police:

https://www.androidpolice.com/2019/...eb-pages-inside-apps-to-freeze-and-crash/?amp

I asked Alex from PA (dev of Op3) some time ago if it was possible to fix, and then he merged this commit: https://gerrit.aospa.co/c/AOSPA/android_frameworks_base/+/10734

The situation on PA became much better.

Could you please have a look at this? Sometimes it's really frustrating.

I can send you logs if you need it.

Appreciate your work on Op3.
[OnePlus 3 & 3T Cross Device Development] PTuT:
When I go back and forth between official built and your build, do I have to delete fingerprints and pattern unlock for starting the system?
[OnePlus 3 & 3T Cross Device Development] James Bottomtooth III:
Have experienced this myself, mostly in Chrome as well
[OnePlus 3 & 3T Cross Device Development] highdiver_2000:
I didn't experience any freeze on Nitrogen OS

Will keep an eye out
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
I'm aware of the bug but never investigated. the commit you mentioned was merged in lineage a month earlier than PA https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/271420
[OnePlus 3 & 3T Cross Device Development] :
it's not my build. Should work without deleting stuff, for me this is working for weeks without any issues.
[OnePlus 3 & 3T Cross Device Development] Drobcek28:
Hi Guys,

I don't know if someone else have same problem, but I can't pass safetynet test.

I have CTS profile match fail. It starts two days ago.

Do you have solution for it? I have official update from 2020/06/29
[OnePlus 3 & 3T Cross Device Development] pcesar.cercal:
Só, it is rom problem?

---------- Post added at 10:10 AM ---------- Previous post was at 10:03 AM ----------

O have flash with last firmware and nano gapps.

Do you do diferent?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
My bad. I didn't realise that there's a new version out. I was using 191120.

I'll try 191231 and get back with my results.
[OnePlus 3 & 3T Cross Device Development] pcesar.cercal:
Thanks,

tell us please. But it also says which firmware, twrp and gapps
[OnePlus 3 & 3T Cross Device Development] realtos:
sim dont work here either, didnt dirty flash . complete wipe :(
[OnePlus 3 & 3T Cross Device Development] pcesar.cercal:
You do clean?
[OnePlus 3 & 3T Cross Device Development] realtos:
yes wanted to wait for next build so just installed it and sim dont work, nothing else wrong thou
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
Confirmed, and I already have a fix locally. Just temp disable selinux before getting the next update.
[OnePlus 3 & 3T Cross Device Development] pcesar.cercal:
ok, just disable / enable slinux?

---------- Post added at 01:58 PM ---------- Previous post was at 01:44 PM ----------

Hi can´t find the Slinux to disable.....

some help?
[OnePlus 3 & 3T Cross Device Development] :
On a rooted shell (either adb or local terminal):

setenforce 0
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
this won't work, must disable on boot.

repack boot.img or use some magic magisk modules (if any?)

-----------

EDIT: instead of disabling selinux, add this line to /vendor/etc/init/hw/init.qcom.rc and it should work after reboot.
[OnePlus 3 & 3T Cross Device Development] pcesar.cercal:
with twrp local works?
[OnePlus 3 & 3T Cross Device Development] Imnoa:
Edit:

Nevermind
[OnePlus 3 & 3T Cross Device Development] ajash:
IMEI lost when flash Latest Update.... Any Solution
[OnePlus 3 & 3T Cross Device Development] rexit1979:
Restore backup or flash any other rom.
[OnePlus 3 & 3T Cross Device Development] gladiac:
Thanks for this hotfix - mobile data works fine now!
[OnePlus 3 & 3T Cross Device Development] pcesar.cercal:
how can i find the place to put the line you say?

sorry but i'm a little green on android ?
[OnePlus 3 & 3T Cross Device Development] chtitlou:
The added line in green has few lines above and below it to help you find the right place. Just look for the service qcom-c_main-sh section in your file and write the new line at the right place. Ensure you grant root permissions to you file explorer before saving the file.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Firstly, I've attached a copy of the fixed init.qcom.rc file. To install it extract the file and copy it to the /vendor/etc/init/hw (or /system/system/vendor/etc/init/hw if you're in TWRP, which is what I did).

Next, I tried to dirty flash this update (191231) over 191120 but after a long boot process I got dumped back into recovery by RescueParty. So I had to do a clean install and installed the fixed init.qcom.rc file before booting.

I'm using OpenGapps 10 nano 191209.

The main difference that I noticed was the theme feature in Settings>Display. Using it (select the custom option) I can now change the accent colour.

However, it seems that the Dark theme no longer includes Black :( unless I'm missing something.

The following issues are still present:

- battery text doesn't show (1024)

- NFC/Pay: Phone is not recognised by terminal (1024)

- Gallery/media manager shows album art in Music (1024)

- Digital Wellbeing keeps stopping (1024)
[OnePlus 3 & 3T Cross Device Development] zachcheatham:
Anyone else not able to complete the setup wizard? After I get to the point where I select how I want to restore data, it says "Checking info..." and then Google Play Services crashes and I get put back at how I want to restore data. I've attempted to restore from Google's backups and skipping with get the same result. I'm on a OnePlus 3 with the latest version of the ROM, wiped clean, using the latest "stock" version of OpenGApps for Android 10/ARM64. I'm not sure if this is a lineage issue or Google Apps'.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Works for me, try using the nano package instead of stock.
[OnePlus 3 & 3T Cross Device Development] giovanniro98:
Oh, ok thank you, but if you need logs to investigate I'm there.
[OnePlus 3 & 3T Cross Device Development] :
See https://www.xda-developers.com/safetynet-hardware-attestation-hide-root-magisk/

Give details on your setup, please!

Give the output of

adb logcat -d | grep decodedJWTPayload
[OnePlus 3 & 3T Cross Device Development] Drobcek28:
Hi,

grep command isn't recognized, I used adb logcat -d > logcat.txt

I split txt file to logcat1 and lgocat2 because logcat was over 512k

View attachment logcat1.txt

View attachment logcat2.txt
[OnePlus 3 & 3T Cross Device Development] :
The logs states your setup still uses basic evaluation type, so the latest update to gservices doesn't break safetynet api, but your setup. Sadly we can't help you with your issue, because you refuse to answer the most important question:

Additional question: what did you change on the setup from the last successfull passing safetynet api to first failure of sfetynet api?

EDIT: on linux, android and macos "grep" is present. On win you can try "find". But I'm not sure about the syntax, nor if find can read from win-pseudo-pipes.
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
How did you achive this result?

Is this a screen from los 17.1 on a op3?

Because I installed unoffical 0709 build from wickenberg and cannot find any galileo satelites.

I also wonder where the merge for "enablement for galileo" should be? In the several patches for gps fix?
[OnePlus 3 & 3T Cross Device Development] Drobcek28:
Could you explain me what exactly I have to send you?

I don't using nothing extra. I have last official update from OTA and pico gapps. I don't install new apps in last days or changing something.

In my phone is LineAgeOS 17.1 with pico gapps and some apps from google play store. Do you think clean installation of last build of 17.1 will help me?

I don't have problem with it
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
So does that mean you have also an open bootloader?

Then you have to close it or use Magisk with the hide function to gain safetynet / cts back...
[OnePlus 3 & 3T Cross Device Development] helderfp:
yep, this is lattest official lineage 17.1 on op3

My config is, lineage recovery, locked bootloader, encrypted.
[OnePlus 3 & 3T Cross Device Development] highdiver_2000:
GPS + Glonass lock, I get, when it works. I have not seen any Galileo. Only some Japanese sats
[OnePlus 3 & 3T Cross Device Development] Drobcek28:
Yes, bootloader is unlocked, but I don't need magisk to hide it till now

My config: TWRP, unlock bootloader. i don't know if I'm encrypted
[OnePlus 3 & 3T Cross Device Development] :
I don't want to. If you are posting a question on safetynet api, I assume you've checked the thread for sfaetynet and know which setup information matters. Please understamd that I'm no search-read-summerize engine.

Maybe. But that shouldn't happen just out of the void without changing the setup, if it has worked before as described in the original posting.

He also clearly stated only rom + gapps - no magisk mentioned.

I hate this begging for basic setup information.
[OnePlus 3 & 3T Cross Device Development] Siddk007:
Go to settings > security. You will know about your encryption status.
[OnePlus 3 & 3T Cross Device Development] :
That's just nonsense.

Plain los 17.0 and 17.1 with unlocked bl with only gapps and no modifications nor custom kernel (what you say is your setup) can't pass saftynet api because the verity bit is tripped. A tripped verity bit always makes saftynet api fail. You would know that, if you'd have read this thread.
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
Yep, I also only get GPS, Glonass and Chinse (I think it must be beidou 3, because otherwise I couldn't see the geostationary satellite here in Germany)

So can it be possible at all with current los 17.1 setting to get galileo, I thought we need an patch for our snapdragon 820..
[MENTION=4405529]nvertigo67[/MENTION], may you can bring some light into the darkness ;)

Yes, the only reason then would be a safetynet algorithm change - but for me everything works fine and if safetynet got updates, I think many more users would complain here...
[OnePlus 3 & 3T Cross Device Development] :
I'm in germany, too, and I've never seen a EU flag in the gnss column: neither with los nor with oos. To my knowledge the hardware (sd820/821) suppprts galileo, but our blobs don't. Don't overestimate the screenshot from [MENTION=2192357]Heider[/MENTION]fp:

The galileo sat isn't used (no U in the flags column).

Only one galileo sat is shown.

The galileo sat isn't shown in the satellite section, but as sbass.

The frequency is L1 - but galileo isn't on L1, it's on E1, E5, E5a, E5b or E6.

I don't know why and what the last line in the screenshot shows - but it shows for sure no working galileo nvigation.
[OnePlus 3 & 3T Cross Device Development] RKS96:
Is there an option to modify performance profile settings? And is there a quick way to switch between these profiles?
[OnePlus 3 & 3T Cross Device Development] klickig:
I extracted against the build provided here https://xdaforums.com/showpost.php?p=82932809&postcount=1678

and still unable to boot. 3 files where missing. I downloaded them from the Muppets repository and moved them accordingly. Do I still have to extract against an 9.0.6 zip?
[OnePlus 3 & 3T Cross Device Development] :
You are on your own. I always build my own repo by running against original oos 3t zip (with changes as explained in my previous posting). I never had missing files. Probably something wrong with extracting: you need to adjust some paths in proprietary-files.txt.... Again: you are at your own when running extract-files.sh against los instead of oos.

Is your build environment sane? (aka: Can you build a booting plain los?) Start debuging why it's not booting, see the last two points of: https://xdaforums.com/showpost.php?p=83003759&postcount=1750
[OnePlus 3 & 3T Cross Device Development] klickig:
I had no problems building before. My last working build is from 13/06/2020. I wanted to update to solve the GPS problem.

I was unable to find anything in sys/fs/pstore after endless Lineage loading logo and manually turning off and booting into recovery. I was able to capture proc/kmsg.
[OnePlus 3 & 3T Cross Device Development] :
That's the kernel output from a successfull twrp boot.

pstore persists for the very next boot.

Just to be accurate: there is no los bootlogo. boot logo is the static picture from the logo partition; boot animation is the animated los startup screen.

That means: if booting gets stuck on the bootanimation (which means kernel is booted and system is mounted - no bootanimation without mounting system), directly boot to twrp and try to get pstore. There's no last_kmesg in curtent lps kernel.

Since your buildenvironment is clean, I would check the changes and blobs (for the latter you need to understand extract-files.sh and proproetary-files.txt) - the idea to run against los without adjustments to proprietary-files.txt can't work if ypu think abou. E.g.:

https://github.com/LineageOS/androi.../blob/lineage-17.1/proprietary-files.txt#L485 moves dashd from oos /sbin/dashd to $vendor_repo/proprietary/vendor/bin/dashd. This results in a build rom with /system/vendor/bin/dashd. If you run the script without modification against the resulting rom (as you did) /sbin/dashd isn't found. Since it's not pinned....

Again: if you don't run the script against oos for op3 you need to make adjustments - and you are on your own and you need to know what you are doing, because the script and file list is made to be used against oos for op3.
[OnePlus 3 & 3T Cross Device Development] klickig:
About the bootlogo: I only see the circle animated running from right to left. Endlessly.

The thing is I never extracted blobs from OOS. I always used a lineage zip as stated here:

Proprietary blobs can be extracted either from a device already running LineageOS or from a LineageOS installable zip

As you stated one of file that was missing was dashd which I grabbed from the muppets repo.

Gonna try to grab pstore again. But how can I directly boot into TWRP after turning off?
[OnePlus 3 & 3T Cross Device Development] :
volume down andere power button together ;)
[OnePlus 3 & 3T Cross Device Development] :
Did you read my last posting? I've explained in detail why extracting from los can't work. If there is no /sbin/dashd, /sbin/dashd can't be found.

I want to stop here. I mentioned four times that extract-files.sh and proprietary-files.txt are made to be run against op3 oos zip - I've explained en detail on one example why this is. There's nothing more for me to do to help you.
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
https://mirrorbits.lineageos.org/fu...age-17.1-20200713-nightly-oneplus3-signed.zip

First official build with gps fixes, thanks again @ all for investiagtion
[OnePlus 3 & 3T Cross Device Development] sahed01:
just came here to say, i am satisfied with the rom. GREAT WORK DEV!
[OnePlus 3 & 3T Cross Device Development] jnsson:
Shame you can't turn off individual SIM-cards in LOS 17
[OnePlus 3 & 3T Cross Device Development] :
Do it like a man, pull the simcard with your teeth :good:
[OnePlus 3 & 3T Cross Device Development] rohan164:
official new build arrived (13-7-2020), hope it has GPS fixed, fingers crossed.
[OnePlus 3 & 3T Cross Device Development] :
Read the thread before posting in the thread, please: https://xdaforums.com/showpost.php?p=83051817&postcount=1807
[OnePlus 3 & 3T Cross Device Development] pijas82:
I search, but I need a better explanation

Thanks

I want back to lineage, it's safe data/cache on f2fs?
[OnePlus 3 & 3T Cross Device Development] mk_1996:
Yes. I have my data and cache on f2fs and everything works as it should
[OnePlus 3 & 3T Cross Device Development] HeyReaz:
How to install OTA?

I got a OTA update today, can I install it by downloading from updater or need to do it manually with TWRP?
[OnePlus 3 & 3T Cross Device Development] :
Downloading an ota with Update.apk has never been an issue - never, as already discussed in this thread.. Automatic flashing has been an issue depending on your setup, as already discussed in this thread.. This is most probably fixed in twrp-3.4.0-0, as already discussed in this thread.

Alway stick to xda rule #1!
[OnePlus 3 & 3T Cross Device Development] pijas82:
Delete (solved) amazing fluidity last buid, data and cache on f2fs

Thanks [MENTION=7554367]mk_1996[/MENTION]

Idc about sot, this is best build I tried in 3.5 years old on my 3t.

Thanks
[OnePlus 3 & 3T Cross Device Development] KamiGooDz:
is this rom caf or aosp?
[OnePlus 3 & 3T Cross Device Development] Sudhangshu:
I think its AOSP based.
[OnePlus 3 & 3T Cross Device Development] :
Taking this question literally the answer is: none of the above, this rom is los.

The answer to the question "On which code base is los developing?" is much more complecated. First of all: all code aurora forum sources are aosp based. So

can't be wrong.

To make it more complecated parts of caf code are imported to aosp.

Apart from this, los for op3/t uses a caf based kernel and caf based hardware modules like the open source parts of gps or ril.

Additionally see: https://github.com/LineageOS/android/blob/lineage-17.1/snippets/lineage.xml#L53-L150
[OnePlus 3 & 3T Cross Device Development] Triggerfinger68:
GPS problems are still there in LOS 17.1 build 13-07. It takes quite some time to get precise fixed position.
[OnePlus 3 & 3T Cross Device Development] MuckiM:
GPS works much better in 13-07. I get a fix Indoor where before no GPS was possible. Outdoor fix is very fast now 4-8 seconds in average. Feels like a new device. Tanks
[OnePlus 3 & 3T Cross Device Development] thesplitter:
After every update (dirty flashing) I still need to reflash opengapps or the launcher and recents stop working. Does anyone have the same problem? Recently with the new opengapps package the launcher keeps FC upon boot, so I'm stuck reflashing last month's package. Why could that be?
[OnePlus 3 & 3T Cross Device Development] Hemuli:
Which recovery version do you have?
[OnePlus 3 & 3T Cross Device Development] alexandre.ladeira:
Anyone facing the WhatsApp mic recording not working after a while? I searched this thread, but the solution is to disabled Google Assistant, and I believe that this is a way to bypass the problem, not a fix. Apart from that, really enjoying the ROM, on my device it's more fluid than pixel experience ROM.
[OnePlus 3 & 3T Cross Device Development] lokeshjt:
are you using trebuchet launcher ? which opengapps package are you using ?
[OnePlus 3 & 3T Cross Device Development] thesplitter:
The recovery is fine, system as root from here. The flashing process goes well, log gives no errors.

stock package. I use pixel launcher, now that you say it trebuchet is not present anymore, weird. I have never removed it and neither should have the opengapps script.

As far as I now launcher crashes because it needs some permissions (status bar and task something) but the recents I guess is because nexuslauncher is the recents provider.

I guess it's time for a clean flash soon
[OnePlus 3 & 3T Cross Device Development] :
Not weired - explained thousands of times in many source build rom's threads: use nano or pico - all other packages replace too much system partss. Read the thread as well as the open gapps package documentation.

If you read https://github.com/opengapps/opengapps/wiki/Stock-Package you would know that this package replaces the rom shipped browser (trebuchet) with pixel launcher. This is also true for other rom shipped system parts, which is asking for trouble.

A lack of knowledge and a lack of reading the available documentation is no good base for using custom roms.
[OnePlus 3 & 3T Cross Device Development] thesplitter:
My bad, now I remember, I messed up because when I firstly flashed 17.1 I used nano, that I why I had trebuchet, this started happening last month when I downloaded the stock package (either I don't know why :/)

True that, I remember opengapps explaining that on 10 needed an extra overlay for some apps and they firstly only supported limited packages because of some issues
[OnePlus 3 & 3T Cross Device Development] Drobcek28:
you wrote you have locked bootloader with lineageos recovery.

It is safe? what I need to do for it? these commands are enough?

fastboot flash recovery recovery.img

fastboot oem lock

please, could you tell me when use fastboot oem lock command if I will be doing clean installation?

thank you
[OnePlus 3 & 3T Cross Device Development] Nixeus2:
Hello guys, i'm on Evolution X with Mad Kernel and f2fs on Cache/data ( and twrp 3.4), is this LOS rom stable and good enough for all day use ? Better than evolution X ? Thanks
[OnePlus 3 & 3T Cross Device Development] Sudhangshu:
Well idon't know about evolution cause I haven't tested it but battery life in LOS is good, and it's stable no problems using as daily driver.
[OnePlus 3 & 3T Cross Device Development] sfoslino:
Hi, did a dirty flash from lineageos 16 this week, using twrp 3.4.0. Nice to see the 17.1. Thank you.

I had problems with the fdroid privileged extension (permissions not granted) and made some dirty tests with the zip.

I changed the following lines inside 'META-INF/com/google/android/update-binary' of the 'org.fdroid.fdroid.privileged.ota_2110.zip' to

SYSTEM="/system_root/system"

mount_system() {
mount /system_root
}

flashed it with TWRP 3.4.0 and it is working again for me. Not tested much.
[OnePlus 3 & 3T Cross Device Development] Celphor:
After deleting the A-GPS data with an app (don't remember which one it was) it works flawless again
[OnePlus 3 & 3T Cross Device Development] Nixeus2:
Hello guys, i have a big issue !

I did a google backup and wipe my phone and installed this rom.

I would like to load my backup...i do the pattern...i'm 100% sure the pattern is OK and google refused it :(

What is wrong with that ?

Thanks a lot :)
[OnePlus 3 & 3T Cross Device Development] :
Search will be your friend, for example: https://xdaforums.com/showpost.php?p=82299329&postcount=877
[OnePlus 3 & 3T Cross Device Development] wojtek007pl:
Hello, does this rom have same battery life as oreo now or is it still worse? And are scrolling lags and heating issues still present too? I am asking because I am unrooted and on locked bootloader and it would take me quite some time to change roms and even more to revert to stock.