yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] :
Someone else, please. Someone activly using voice control. I'm not willing to allow any gapp to use the device's mic. (Read the terms and conditions!!!)

Is this a regression? Was it working before 20190526? If so, get a log from toggle, register and toggle off sequence.

Do you have set google as assistent app?
[OnePlus 3 & 3T Cross Device Development] knpk13:
No more pie blobs builds though? I thought we were switching to it for good.
[OnePlus 3 & 3T Cross Device Development] :
I'll switch, when the builds work for everybody's device. I'll make the next alpha-pie-blobs build, when a new idea for fixing the alpha-pie-blobs build for everybody's device is available.
[OnePlus 3 & 3T Cross Device Development] S4turno:
Build 20190530 with the "oxygenos-9.0.2-bl-km-5.0.8-firmware-3.zip" zip is working well on my OP3. At least I haven't noticed any problem.
[OnePlus 3 & 3T Cross Device Development] Ormad:
Seems so. I didn't change absolutely anything besides updating builds and opengapps during flashes like I always do :( so it's either rom or recent opengapps.

Yes I'm using Google app to set assistant and as said when I do the 4 ok Google vocal sequence "voice Match" toggles back.

Tried all generic fixes I could find on web (un install updates of Google app, try beta version, un install and reinstall it and so on but nothing worked). Also tried both 9.0 firmware and 5.0.8 because I tought maybe the new one was culprit but on 4th June build with 5.0.8 issue remained ?

So I'm currently out of ideas (and thank you for replying and the rom nvertigo, you are amazing!)

I guess I need to find the force to flash old builds and try hoping it doesn't screw up data flashing older builds, so at least I'll know if it's the rom or Google side
[OnePlus 3 & 3T Cross Device Development] :
Don't do that! Don't! Don't! Don't! Unless you know what you are doing, stick to the word to the directions given in OP!

I've explaimed that many times:

gservices is autoupdated - no matter of gplay update settings. An update of the gservices may include a database update of the gservices settings db. If it happens that a gservices update has updated the db level of the settings db, but even the newest gapps package (pulled from some pixel devices images) contain gservices with an older db level you are lost in strange effects. Nasty things will also happen if you change the size of the gapps package (i.e. flashing nano on a setup originally created with pico - or vice versa).

Recomendation: clean flash. (Or restore working backup and use OP's directions for update.)
[OnePlus 3 & 3T Cross Device Development] AndreiVolk:
[MENTION=4182338]Ormad[/MENTION] [MENTION=4405529]nvertigo67[/MENTION]

Every time i had a problem with a google app it was because of a broken opengapps build. Dirty flash rom + different opengapps build usually is enough.
[OnePlus 3 & 3T Cross Device Development] :
PLEASE!!!! ONLY FLASH GAPPS ON CLEAN FLASHES! REFLASHING GAPPSMON A RUNNING SETUP WIL GET YOU IN TROUBLE SOONER OR LATER!!! Read my previous posting on changing gapps on a running setup! If you've grabed a broken gapps build (happens more often then users think, because of untested auto-building) for your clean flash, clean flash with a non-broken gapps build again, unless you can be absolutly sure (and I don't know how one should know that) that the db level hasn't changed (compared to gservices auto-update)!

STICK TO OP!!!
[OnePlus 3 & 3T Cross Device Development] AndreiVolk:
Sorry for that. I forgot this rom preserves gapps.

Clean flash + different gapps should solve the problem of google apps not working properly
[OnePlus 3 & 3T Cross Device Development] :
Flashing gapps adds a script to addon.d. twrp honors that and save/restores according to the script. Nothing about the rom.

...and if one found a running gapps build, take care of it: you can always use it (till next major release, of course), because contained apps and services are updated via playstore.
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (mainly maintainance; bring back left vol panel; Wallpaper cosmetics))

Build 20190609

Releasenotes:

NLOS-16.0 relies on OxygenOS firmware. OxygenOS 5.0.8 firmware is required:

Oneplus 3T: OxygenOS 5.0.8 firmware

Oneplus 3: OxygenOS 5.0.8 firmware

For a complete list of additional cherry picks see: current.pick.sh.

Changelog (Last repo sync: 9 Jun 2019, 12:27:16 CEST / 9 Jun 2019, 10:27:16 UTC):

current.pick.sh: "pie-audio-panel-location". — Nvertigo (now runtime configurable: Settings->System->Buttons)

make NLOS Wallpaper the default and add LineageOS wallpaper (original default) to Backgrounds app:

NLOS: bringup LineageOS Wallpaper. — Nvertigo

NLOS: rmove default wallpaper overlay. — Nvertigo

overlay: add NLOS default wallpaper. — Nvertigo

NLOS: include vendor/nlos/overlay/common.

NLOS-Bootlogo

nlos_bootlogo-v0.1.zip

back_in_black_bootlogo-v1.0.zip(pre ob16 OxygenOS Bootlogo)

[SIZE="+2"]DOWNLOAD[/SIZE]​

Happy flashing!
[OnePlus 3 & 3T Cross Device Development] pedritopl:
Cool! :)
[OnePlus 3 & 3T Cross Device Development] pedritopl:
Awesome!

And again, it _feels_ like wifi (2.4GHz) works "better" (more stable at least, maybe faster).
[OnePlus 3 & 3T Cross Device Development] 9Lukas5:
Newest Pie Blob build running fine here [emoji106]

L

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I believe it's the rom install updater script that invokes the backuptool shell script which preserves what's listed in addon.d.

See the install directory in a Los zip and the following line in the updater script:

run_program("/tmp/install/bin/backuptool.sh", "backup", "/system");
[OnePlus 3 & 3T Cross Device Development] :
...and the line before backuptool.sh is upacked from inside the rom zip... Never realized that... Maybe, I've read not enough recovery logs from an update... ;) Thanx for pointing out!

I guess it's either population of the 5GHz range or dfs channel handling or both. I'm not expirience that on 5GHz/ac on non-dfs (channel 44 or 40 - autoselect of my router, which dosn't support dfsmchannels at all). Since dfs channel usage requires additional care (radar has priority over wlan usage) an additional scan cycle before connecting makes sense to me.

Since my router doesn't suppport dfs channels, I can't test this - that's why I need to guess here.

What I can check is throughtput: transfering a build from build host to op3t is about 70s on 5GHz/non-dfs/ac; and abput 130s for 2.4GHz/n. Both with no other devices connected to the ap.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Yeah, but backuptool seems to be present on every ROM I've ever used, so it's not unnatural to assume that update support is baked into gapps (I used to think that's how it worked too). The only ROM I've encountered so far that doesn't use backuptool is GlassROM. It has some very different defaults from most other ROMs which is interesting.
[OnePlus 3 & 3T Cross Device Development] :
Actually the support for peristant flashable zips IS baked in the gapps package's flashable zip. This is populating addon.d.

[MENTION=2911853]BillGoss[/MENTION] just pointed out, that honoring the content of addon.d happens from inside the rom's flashable zip. The failed part of my assumption that addon.d content is triggred by the recovery.
[OnePlus 3 & 3T Cross Device Development] 64ashg:
i still have the same problem, no sim detected after switching to pie blobs build.

my procedure

wipe system,

flash modified fw

flash rom file and gapps

flash magisk 19.3

reboot.

no sim found and within a minute, automatic reboot

now i had seen somewhere in this or the fw thread that someone flashed in the following order

flash original pie fw

wipe system

flash rom file

flash modified fw

flash gapps and magisk

reboot

in both the methods, no reboots in between.

now i want to ask to anyone having the pie build running fine on their setup, is the second method any good?

will my data be locked out and i will need a data partition wipe if i do that? if not, then can i safely execute the second approach without having my /data wiped?
[OnePlus 3 & 3T Cross Device Development] pedritopl:
Why don't you just (coming from previous build and 5.0.8 FW):

- reboot to TWRP

- flash 9.0.3 FW with 5.0.8 elements

- reboot to TWRP

- flash new build (with 9.0.3 blobs)

- wipe Dalvik/cache (from the screen after end of flash)

- reboot to system

Magisk and gapps will be preserved. It was already stated *many* times not to re-flash gapps. There's also no need to wipe system before flashing new build.

If You're flashing clean from a different ROM, at least try adding the reboot to TWRP step after flashing new firmware.
[OnePlus 3 & 3T Cross Device Development] 64ashg:
the steps you mention, is a dirty flash, that i have already tried. the clean flash method of the same is in the first approach i mentioned.

but thanks :)
[OnePlus 3 & 3T Cross Device Development] pedritopl:
So have You tried adding the reboot to TWRP after flashing firmware as I suggested?

Also, for clean flash You should also wipe data and cache. Not only system.
[OnePlus 3 & 3T Cross Device Development] :
Let's get this straight:

Flashing the fw after the rom is necessary for roms, which contain the fw (I know only of OOS). It should be obviious why.

For all non-fw containg roms (like nlos) you need to flash the fw before the rom.

Theorethicaly it's not needed to reboot after fw flashing before flashing the rom. I recommend rebooting to twrp, because it doesn't hurt and you can check if userdata is still accesseble.

The recommended procedure (see release notes) is a clean flash with unmodified fw. You will loose the complete content of userdata:

reboot to twrp

flash unmodified fw 9.0.3

reboot to twrp , if userdata is not decryptable anymore, hit "cancel"

wipe system, cache and dalvik

format data from the main wipe page

reboot to twrp (the console output of formating data clearly states to do so)

Optional:

now you are on ext4, if you want to change to f2fs, do it now and reboot to twrp after formating to f2fs

make sure your partitions are formatted like this (if you need to change this, reboot to twrp after formatting):

system: ext4

cache: ext4

userdata: ext4 or f2fs

flash rom and gapps (pico or nano)

reboot to system

run first time setup

Optional:

reboot to twrp

flash Magisk

wipe cache and dalvik

reboot to system

If you want to keep your userdata partition and it's content, dirty flash with modded 9.0.3 fw:

reboot to twrp

flash modified fw 9.0.3

reboot to twrp (you should still be able to decrypt userdata)

make sure your partitions are formatted like this (if you need to change this, reboot to twrp after formatting):

system: ext4

cache: ext4

userdata: ext4 or f2fs

flash just the rom

wipe cache and dalvik

reboot to system

Always check the twrp console output and/or the recovery log.

Never flash gapps without wiping (or formating) data! Never! I've explained that many times, the last time one or two pages back.

If something is wrong with the resulting setup (especially if Magisk is involved), power of from the running system, wait 30 seconds and power your system on again.

Happy flashing & good luck!
[OnePlus 3 & 3T Cross Device Development] 64ashg:
yes, yes i have done that the reboot between fw changes and before flashing rom files too. and yes, by system i am also referring to wiping the data, cache, dalvik partitions too

all without success.

yes, i had done the exact steps for both the methods, I'm running ext4 on all three partitions.

i haven't had a successful sim detection following it.

im back on running the oreo fw rom on oreo fw.

thanks :)
[OnePlus 3 & 3T Cross Device Development] pedritopl:
I'm running out of ideas ;)

Last one: have You checked the md5 of all flashed zip's (ROM, FW, gapps-nano(?), Magisk)?
[OnePlus 3 & 3T Cross Device Development] 64ashg:
i wish that was the problem,

i did that, without any success.

thanks for the suggestions
[OnePlus 3 & 3T Cross Device Development] deepak jr:
I've just updated to this version and I did a clean flash and followed all the steps that you suggested but there are some random reboots to recovery every once in a while. For this issue, which logs do you want? Or is it because of the latest firmware?
[OnePlus 3 & 3T Cross Device Development] :
Please redo your quoting. Quote only what you are refering to. Thanx in advance to keep the thread readable and searchable.

Apropos readable and searchable: If you follow the thread, you'll find two points:

The native oos pie blobs build work for the vast majority, but for four people (ncluding yoi) it's not working.

I've spended three nights on the logs to no advance - I'm absolutely clueless and idealess on this.

You'll also find, that it doesn't really matter, because there is no advantage from a users point f view, but the higher vendor security patch level.
[OnePlus 3 & 3T Cross Device Development] deepak jr:
I'm sorry about the quote thing as I'm really not used to xda but it's not a major bug, it just reboots randomly to recovery and it happens not very often. So if I can be of any help I'd be glad to help.
[OnePlus 3 & 3T Cross Device Development] :
I'd be happy if I would have any idea howmyou could help me. I'm the first one asking for logs, but atm this would just be bumbledom... I'm going to come back to yoir offer, if I have a new idea.

On quoting: imagine someone has issues with gps and searchs for gps. This user will find your posting (among others), though it's not related to gps in any way. The longish quoting is also bad for reading the thread, because one have to scroll a far way without any new information or information on your question. These are the two main reasons, why longish, unrelated quotings are considered bad manner.
[OnePlus 3 & 3T Cross Device Development] 13THWARRI0R:
[MENTION=4405529]nvertigo67[/MENTION]

It seems ... going to flight mode immediately on startup on 9.0.3 fw on pie blobs seems to stop random reboots on pie native blobs ..... and i'm able to get signal on normal 9.0 build and not on pie native blobs with pure 9.0.3 firmware .... seems to be missing some blob or some ril mishap i believe :confused:
[OnePlus 3 & 3T Cross Device Development] :
Expectable. I'm pretty sure it would also work without sim inserted.

It's much more comfusing, if you look at your device's logs (ril communication is failing from the beginnimg), and keep in mind, that it's working flawlessly for others (I've used the 0530 for 5 days without a glitch and the 0609 build for 3 days).

If the issues would start AFTER the sim is detected and unlocked, we could conclude it's carrier dependend, but it starts failing BEFORE.

Coming back on missing blobs, the only carrier which needs some special blobs is verizon. But even if that would be the case, the trouble should start AFTER detecting sim (and therefor: carrier detect)...

I agree with you: it's really confusing.
[OnePlus 3 & 3T Cross Device Development] 13THWARRI0R:
Actually during the setup of device or after flight mode is down or a restart ... I could see the first sim was detected for a second or two ... And then .. the device restarts ...

So i do suspect it is after sim detection ...

Well let me have a look ... With respect to rils from the official package if they have a change with region ... And if they work ... We could add a fix then ... Might take some time though...
[OnePlus 3 & 3T Cross Device Development] :
Interesting! Perhaps it's happening on sim detection. Can you see a successfull ril communication in the logs (something detecting the carrier)? Maybe you see something from the first sim, because the crash is delayed because of the secomd sim? (I'm pretty sure, I've only seen logs from simgle sim setups.)

You are welcome to check the blobs - I appricoate that!

https://github.com/nvertigo/android...ed93e28#diff-e18a190ec9e1d301d38ff968dea34a59
[OnePlus 3 & 3T Cross Device Development] Yndi:
Hi there,

just wanted to report that I clean installed the pie blobs build today (OP3, EXT4, Not Encrypted, 2 SIM, minimalized P-GAPPS, Magisc, TWRP 3.3.1.0) and it runs great.

I tried F2FS when I upgraded from 15.1 to 16 but I had some hiccups so I went back.

Two questions:

Does One-Handed-Mode work for anyone?

Does the device not use it's memory well? Don't know if I can trust that but memory usage in the Dev Options never even shows 2GiB and yet it closes background apps pretty fast.

Cheers and good luck for all those struggeling with pie-blobs, especially nvertigo67
[OnePlus 3 & 3T Cross Device Development] 13THWARRI0R:
[MENTION=4405529]nvertigo67[/MENTION]

I found the issue with the rils .... it is ims.apk in /system/priv-app/ims is trying to access a private method in framework causing a crash during lte ims start with lte supported devices .... causing rest of the blobs to fail to load ..... replaced it with old ims.apk and libimsmedia_jni and libimscamera_jni.so .. fixed the rils ...

you can revert the ims.apk with daisy ims or stay with old one ... 9.0.2 ims is having some patch with framework ... oneplus has screwed it
[OnePlus 3 & 3T Cross Device Development] :
Sadly, there's only one trigger, yet: use onscreen navbar and swipe the navbar.

First of all: to get a an acurate overview use free and top/htop (cli).

The memory gui bar isn't really inacurate, but the algorythm to tell what's available memory is some kind of inovative... I havn't completely understood the way the bar calculates used and free mem, but when free or top/htop adds the mem used for buffers/cache to free mem, the bar adds something more (maybe(!) mem of background apps, which arn't pinned nor are a service - maybe the [euphemism]intelligent[/euphemism] adaptive battery saver's information is added in some way...).

Thanx. I'm quite relaxed with the native oos pie blobs, because I'dpesn't see any real life benefit. It's nice to have, but far from being necessary.
[OnePlus 3 & 3T Cross Device Development] 13THWARRI0R:
and i can guarantee that .. LTE works and and call works and sms works on the pie based blobs after replacing ims with old one
[OnePlus 3 & 3T Cross Device Development] :
Most important: thank you very much! You can't imagine how much I appriciate your efforts and findings!

I'll try to put out three builds:

pie-blobs-alpha build with the latest commits in gerrit. Especially this addition (in patchset 7) looks promising: https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/244335/6..8

same as 1., but with the three blobs you mentioned changed

5.0.8 based blobs build

I'll try to finish them all today, but maybe one or another will be finished tomorrow.
[OnePlus 3 & 3T Cross Device Development] 13THWARRI0R:
:) welcome .. i like to contribute as a small dev in free time ...

dont bother with the first .. i already tried that .. didnt work, showed no improvement ...

ro.telephony.default_network=22,20 .. manual selection of a network list ... could be used .. but if i were u .. i would not find it better than normal present builds

telephony.lteOnCdmaDevice=1 this is for CDMA device to get LTE ... but as i have seen this thread from its start i have not seen even one person commenting about LTE on CDMA
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=5708300]13THWARRI0R[/MENTION]:

I'll drop 1., and if 2. is working for [MENTION=5868698]64ashg[/MENTION], I'll drop 3., too.

The thre daisy blobs are from https://github.com/TheMuppets/proprietary_vendor_xiaomi/tree/lineage-16.0/msm8996-common , arn't they?
[OnePlus 3 & 3T Cross Device Development] 13THWARRI0R:
Nope actually I took those three blobs from your 6.9.2019 build ... Made for 5.0.8 fw ... They work for 9.0.3 too...

Actually I mentioned daisy blobs as you have ... Has kanged them in your GitHub
[OnePlus 3 & 3T Cross Device Development] :
https://github.com/nvertigo/android...mmit/2a1230bd37d102e9940fbdeb4a8f434b5a75d5c0

https://github.com/nvertigo/proprie...mmit/4e9999540c7e09c0939fd85d00187e473f18b91d

ims.apk on 5.0.8 based builds was already kanged from daisy. It's the very same as https://github.com/TheMuppets/propr...-16.0/msm8996-common/proprietary/priv-app/ims

Thanx.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Do you know if that Daisy ims.apk has the modifications to disable the 'SIM is HD capable' Notification? I'm still using a modified .apk from March.

Also, why did everyone start using that Daisy ims.apk in their ROMs? Is it super awesome or something?
[OnePlus 3 & 3T Cross Device Development] :
Seems so: https://github.com/TheMuppets/propr...m8996-common/proprietary/priv-app/ims/ims.apk

EDIT: we (los/nlos) use the daisy ims.apk since December the fith 2018. It was needed to get ims to work at all. See [MENTION=5708300]13THWARRI0R[/MENTION]'s findings. I think OnePlus has ****ed up ims with proprietary callbacks long before 9.0.2, but it shows on 9.0.2, because the pinning was thrown away with my first native oos pie-blobs attempts.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Thanks.

Looks like i've been flashing the ims mod for no reason. (The Daisy apk was adopted by crDroid some time ago). Guess i can stop now. :)
[OnePlus 3 & 3T Cross Device Development] :
Update pie-blobs-alpha

Native OnePlus Pie Blobs Build 20190609

Releasenotes:

This build relies on OxygenOS firmware. OxygenOS 9.0.3 firmware is required. At this point you have two options:

You don't care about loosing data on an unlocked bootloader and clean flash including format userdata according to the first time installation instructions in OP (recommended):

Oneplus 3T: OxygenOS 9.0.3 firmware

Oneplus 3: OxygenOS 9.0.3 firmware

You want to keep your current setup and like to dirty flash on top of beta builds:

I've created a firmware package from OxygenOS 9.0.3. To avoid issues due to an unlocked bootloader and/or encrypted userdata partition, I've kept the bootloader and and keymaster partition to OxygenOS 5.0.8. This allows to run the pie-blobs builds with native Oneplus OxygenOS 9.0.3 blobs, but you don't need to reformat the userdata partition.

Oneplus 3T: OxygenOS 9.0.3 firmware with 5.0.8 bootloader and keymaster

Oneplus 3: OxygenOS 9.0.3 firmware with 5.0.8 bootloader and keymaster

For a complete list of additional cherry picks see: current.pick.sh.

Changelog (Last repo sync: 16 Jun 2019, 10:52:55 CEST / 16 Jun 2019, 08:52:55 UTC; relative to 20190609 pie-blobs-alpha build):

current.pick.sh: force picking "Sounds: Squashed cleanup of sound files". — Nvertigo

current.pick.sh: remove "Crash app on foreground service notification error". — Nvertigo

current.pick.sh: remove pie-qcom-sepolicy. — Nvertigo

op3: Remove unused thermal-engine header — dianlujitao

op3: VR: Reset thermal setting if runtime crash — Wei Wang

op3: Address denials of VR HAL — dianlujitao

op3: Add Timeout attribute to powerhint.xml — dianlujitao

op3: remove wcnss_filter — Demon Singur

op3/t: pin ims.apk, libimscamera_jni.so and libimsmedia_jni.so. — Nvertigo

op3/t: kang ims.apk from daisy. — Nvertigo

NLOS-Bootlogo

nlos_bootlogo-v0.1.zip

back_in_black_bootlogo-v1.0.zip(pre ob16 OxygenOS Bootlogo)

[SIZE="+2"]DOWNLOAD[/SIZE]​

Happy flashing!

Personal note: Please test this build compared to 5.0.8 based builds. If no one is complaining, nlos moves pie-blobs-alpha to beta to make it the standard release. Thanx again to [MENTION=5708300]13THWARRI0R[/MENTION] for his finding, which makes perfect sense to me!
[OnePlus 3 & 3T Cross Device Development] 64ashg:
i see a 16th june pie alpha build in your drive link. is it the no.2 build with modifird blobs you were talking about?

edit: you released the notes. ok my download is complete, fingers crossed.

edit 2: it works, thank you you beautiful strangers on the internet in some other part of the world [MENTION=4405529]nvertigo67[/MENTION]

[MENTION=1763460]Dirk[/MENTION]

i am quoting you as i cannot successfully mention you with an @

edit 3 i am using reliance jio sim, which is a 4g volte only isp. it is possible for it being a 4g over cdma..
[OnePlus 3 & 3T Cross Device Development] 13THWARRI0R:
Thanks :)

Well Jio is not a CDMA network