yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] theduke7:
Ahrion's audmodlib and v4a modules caused me issues even on the latest OOS beta...it's something to do with the new magisk 13.3, and i know that Ahrion is working on an update i think... i;m not sure if that's what's causing your issues, for me it caused wifi issues, so try and remove those 2 modules and reboot and see if the issue persists.
[OnePlus 3 & 3T Cross Device Development] sjknight413:
Thanks for the heads up, although looking at the files it changes I'm not sure how they could affect WiFi, it literally only touches audio config files
[OnePlus 3 & 3T Cross Device Development] joshuous:
Turn off all magisk modules first and report again after a day, and yeah I still need the list of apps
[OnePlus 3 & 3T Cross Device Development] sjknight413:
Okay I'll try disabling magisk modules tonight!

Apps are attached.
[OnePlus 3 & 3T Cross Device Development] ram4ufriends:
Congrats on your RD [MENTION=6745491]joshuous[/MENTION]...you deserve it...
[OnePlus 3 & 3T Cross Device Development] RMarques:
[MENTION=6745491]joshuous[/MENTION] Thanks for your reply...I believe I failed miserably trying to explain myself. ?

My doubt is about if can I flash your ROM over the OOS 4.1.6 Stable version or do I need to flash the latest OB version first and after that flash your ROM as you said in your 1st post instructions?
[OnePlus 3 & 3T Cross Device Development] uudruid74:
Short term solution would be to use the scheduled DND to silence the phone during sleeping hours. That would be easier than turning on airplane mode before you go to bed. Granted, you still have a WiFi issue, but you'll get some sleep
[OnePlus 3 & 3T Cross Device Development] oyogen:
You don't have to flash OB first. As long as you follow all the instructions in the OP, it'll be fine irrespective of stable or OB.
[OnePlus 3 & 3T Cross Device Development] kyledowling:
No need to flash the entire stable or open beta OOS ROM, only flash the latest stable firmware (linked in OP) then flash vertex.
[OnePlus 3 & 3T Cross Device Development] ochomak:
To what extent the room is polished?

ONEPLUS A3003
[OnePlus 3 & 3T Cross Device Development] F3ELING1337:
I forgot to mention that I hadn't enabled anything Substratum related. Anyway, here's the log: https://hastebin.com/lutadefose.sql

And concerning the camera, I didn't know that this behavior is stock. But what's the point of using the circle shortcut when you still have to unlock your phone after it? Would you mind looking into it? Given it doesn't differ from your "stock philosophy" too much.

Thanks in advance:)
[OnePlus 3 & 3T Cross Device Development] sjknight413:
Depends how much polish you've used throughout the room?

The room I'm sitting in currently for example, is very highly polished.
[OnePlus 3 & 3T Cross Device Development] AlemanSantos:
[MENTION=6745491]joshuous[/MENTION] With double power button it goes directly to the camera, no need to unlock, with the circle gesture should be like this too I think, better UX
[OnePlus 3 & 3T Cross Device Development] calvinistmac:
It's quite dusty
[OnePlus 3 & 3T Cross Device Development] omar77w:
You still have to unlock the phone after using the shortcut because you don't want someone grabbing your phone, drawing a circle, and boom, they just skipped your fingerprint/pin and went straight into your phone. Same goes for double pressing the power button. As Joshua said this is the same behavior found in stock Android as well as on iPhones.

Edit: didn't notice you only had swipe to unlock with no other real security measurement. Still as the dev said this is the stock behavior. I'm assuming because even after the gesture, your phone is still 'unlocked,' and you still need to 'swipe to unlock' it :)

While iOS is not completely relevant, but once again I actually tried disabling my passcode on the iPhone and it's also the same behavior.
[OnePlus 3 & 3T Cross Device Development] uudruid74:
I have both fingerprint+password lock (not swipe). Swiping the camera icon on the lockscreen requires that I unlock the phone. If I just double-tap the power button (while screen is locked) the camera opens without needing password. This is the inconsistency that the OP mentioned.

As for security, the camera is supposed to open "above" the lockscreen, keeping the phone locked so that any attempt to get access to anything other than the camera (even the gallery) requires unlocking the phone, but you can quickly take new pictures without unlocking in case you need to "capture the moment" before it passes.
[OnePlus 3 & 3T Cross Device Development] omar77w:
Strange–swiping the camera icon on my lock screen does not require that I unlock my phone, actually. :/ I have fingerprint+pattern.
[OnePlus 3 & 3T Cross Device Development] joshuous:
Same here, I don't need to unlock my phone to use camera
[OnePlus 3 & 3T Cross Device Development] sneakerspark:
That's how it should be. Note that you can take a quick picture and even view that picture in the camera gallery but you can't view any other photos while doing that.
[OnePlus 3 & 3T Cross Device Development] AlemanSantos:
The problem with screen off and circle gesture on my end was a bug because i restored nandroid backup and used the zip to delete pin, testing just now I realized I didn't set up the pin again, after that circle gesture with screen off goes to camera.
[OnePlus 3 & 3T Cross Device Development] omar77w:
Yup I know. I meant [MENTION=2323827]uurdruid74[/MENTION]'s behavior was strange. :)
[OnePlus 3 & 3T Cross Device Development] uudruid74:
Weird. I just tried it again and it works now! No unlock. I wonder if the dialog asking which camera to use was requiring the unlock? Everything works the way it should and I promise I tried everything before typing my previous post!

Gremlins!
[OnePlus 3 & 3T Cross Device Development] sneakerspark:
Yup the dialog is normal when you install an additional camera Apk.
[OnePlus 3 & 3T Cross Device Development] uudruid74:
I know that. The question was if the dialog appearing could have caused the device to require unlocking.

Update: I just cleared the app defaults on the camera, and its back. So that seems to have been the issue. The default camera for icon-swipe and power-double-tap are set separately and must be set to "Always" to prevent asking as the device must be unlocked to display the dialog asking which camera to open.
[OnePlus 3 & 3T Cross Device Development] joshuous:
Yes the dialogue appearing will necessitate an unlock. This is from a security standpoint
[OnePlus 3 & 3T Cross Device Development] Sir_gpm:
I have HAL3 enable and using SultanSnap Camera...but tonight taking photos during a celebration it lags a lot.....any recommended setting?.
[OnePlus 3 & 3T Cross Device Development] joshuous:
I can't help because I don't use that camera. The lags occur because the camera needs to keep it's aperture open for longer time to let in sufficient light. If you're able to manually adjust, you can decrease ISO (I think) but your pictures will appear darker
[OnePlus 3 & 3T Cross Device Development] F3ELING1337:
The strange thing is that when I enable some kind of security as Pin, fingerprint etc. I can normally use the circle gesture. It only doesn't work when swipe to unlock is activated. And I only have the camera app that came with your rom so no confirmation dialog there.
[OnePlus 3 & 3T Cross Device Development] sjknight413:
Magisk modules disabled last night, phone wasn't on charge, airplane mode, WiFi on, the usual. Still woke up to notifications. The only constant is that I have alarms set.

I can't be the only one experiencing this? I really can't find anything to pin it down.
[OnePlus 3 & 3T Cross Device Development] Puddi_Puddin:
Perhaps those are timed notifications?
[OnePlus 3 & 3T Cross Device Development] sjknight413:
I don't think so because they come from a multitude of apps, usually about seven hours into my sleep!

[MENTION=6745491]joshuous[/MENTION] is there a wake up process the phone starts when it knows alarms are due to go off? I'm wondering if it's related to something like that. The notifications usually arrive exactly one hour before my first alarm.
[OnePlus 3 & 3T Cross Device Development] omar77w:
Interesting. If you didn't know, the clock app pushes a notification–the one with the Dismiss button–exactly two hours before the alarm goes off. I suspected it could be that, but I tried reproducing the problem on my end by putting the phone in airplane mode and sending an online message to myself just before the 2-hour notification mark, but still nothing out of the ordinary.
[OnePlus 3 & 3T Cross Device Development] joshuous:
Check all your app permissions via Google Play. See that Flud has the permission to enable WLAN?
[OnePlus 3 & 3T Cross Device Development] sjknight413:
That's a good point, okay uninstalled flud and another possible culprit, my network provider's WiFi calling app. I haven't opened either since they were installed though, but hopefully this solves it!
[OnePlus 3 & 3T Cross Device Development] Simonis:
Hi there I flashed newest ROM it's running so far very smooth, but how to make a screenshot?
[OnePlus 3 & 3T Cross Device Development] _millig_:
Volume down+power buttons alltogether
[OnePlus 3 & 3T Cross Device Development] RMarques:
Sup guys. I've been kinda busy these days.

I did flashed Latest vertex beta 3.3 and so far it is working great! Not even one FC so far. I haven't had enough free time in order to have calculated a SOT time though.

Here are the steps I took to go from OOS 4.1.6 stable to Vertex 3.3 Latest test build.

Take note that I already was bootloader unlocked and rooted (SuperSU-2.82)

1. Flashed TWRP 3.1.1-0 official

2. Flashed OB 9

3. Flashed Vertex 3.3 Latest test build

4. Flashed GApps micro

5. Flasehd Magisk-V13.3

6. Reeboot

7. Around 5 mins later

8. "Dont worry, be happy..."
[OnePlus 3 & 3T Cross Device Development] joshuous:
Excited to say that OOS camera is now compatible with latest VertexOS on HAL3 thanks to [MENTION=3012129]azaidi[/MENTION]'s discovery! No HAL switcher needed. Commit here if anyone is interested: https://github.com/VertexOS/android_frameworks_base/commit/b4d4fe19a717c2207ca4b2f50c68fd6ef840474a

There are several other significant camera framework changes to come from him in future too :D

Furthermore I've got charging sounds working, and I'm at the moment delving deep into the OxygenOS framework and studying the optimisations made in their framework. There's something called Embryo, which seems to deal with app launching. I'm analysing this and hoping to port to Vertex, although I have to say that it's gonna be really tricky to get it up and running. Stay tuned!
[OnePlus 3 & 3T Cross Device Development] ram4ufriends:
Awesome work Josh on porting OOS stuff to AOSP
[OnePlus 3 & 3T Cross Device Development] sjknight413:
Amazing!

Does this also equal full functionality or will it still effectively work the same as it does in hal 1 currently? (Processing dialog, no 60fps etc)

Second question, and one I hate to ask, is there any possibility of getting access to the slack group and test builds? :)
[OnePlus 3 & 3T Cross Device Development] adpro:
Found a minor bug:

Wifi keeps scanning in background when it is turned off from shortcut toggle...can be seen in battery graphs.

However, when it is turned off from Wi-Fi settings instead of shortcut toggle, then it turns off completely.
[OnePlus 3 & 3T Cross Device Development] AcmE85:
I've got a response on Reddit by azaidi:

https://www.reddit.com/r/oneplus/comments/6qvdbp/oxygen_os_457_coming_with_4k_eis_and_more/dl0w9ti/
[OnePlus 3 & 3T Cross Device Development] F3ELING1337:
Nice! Thank you for always improving this great ROM. Looking forward to the new version.

Regarding the com.android.phone fc bug: I looked through my log which I posted on hastebin and noticed that it had something to do with a null array returning after querying some VOLTE preferences. So I looked through my framework-res.apk and in \res\values\bools.xml I set config_device_volte_available, config_carrier_volte_available and config_volte_preferred to false and no more force closes:) Maybe that helps you pinpointing the bug.

edit: I figured setting only config_volte_preferred to false was enough.
[OnePlus 3 & 3T Cross Device Development] sjknight413:
[MENTION=6745491]joshuous[/MENTION] didn't you say a while back that you disabled carrier provisioning? Perhaps that's why this force close is happening? Would make sense because it seems like the rom can't detect whether VOLTE is available if this solution works.

EDIT: ignore me, don't think you did ever say that, not sure where I got it from!
[OnePlus 3 & 3T Cross Device Development] Vincent_40:
Hi all,

I'll try this Rom tomorrow (never flashed).

I come from official RR. So, do I need to flash 4.1.6 fw and official Twrp or I can flash with blu_spark Twrp version and OB 20 fw like RR ?

Thx for reply.
[OnePlus 3 & 3T Cross Device Development] Puddi_Puddin:
Both OB20 and 4.1.6 work flawless.
[OnePlus 3 & 3T Cross Device Development] Vincent_40:
Cool, willl try tomorrow.

Thx [MENTION=6669873]Puddi_Puddin[/MENTION]
[OnePlus 3 & 3T Cross Device Development] danmit:
I think I may be finally ready to move from OOS Beta to a custom ROM.

EAS seems interesting and now that camera is getting wild I should be trying it soon.

I read something about restoring apps using Titanium Backup could give you problems.

Does that apply to restoring apps or apps + data only?
[OnePlus 3 & 3T Cross Device Development] omar77w:
Can't imagine restoring the apps (apk only) giving any problems. If anything it's the apps+data that might give trouble.

You could install the apps+data and see for yourself. If you run into any problems you can simply clear the data from the settings and it'd be as if you installed apk only.

Also for quicker batch restoring, I'd recommend using an app called oandbackup. It's essentially Titanium Backup but open source, has better UI, and does not require a Pro version for a zero-click batch restore. :)
[OnePlus 3 & 3T Cross Device Development] uudruid74:
People aren't getting notifications if you restore your data for messaging apps that use Google cloud messaging. For details on why, see https://stackoverflow.com/questions/34958132/should-i-backup-gcm-registration-id-with-google-cloud

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

I would try Backup+ I looked into oandbackup and it was not as fluid of an experience

---------- Post added at 12:22 AM ---------- Previous post was at 12:17 AM ----------

So does this change any quality settings? HDR and such? I know OnePlus's HAL3 has issues with ISOs above 799 and such.

The embryo concept looked interesting. I read about it and not sure if its really going to improve things all that much since everything is so fast as it is. Will be nice to see how it comes out as far as app launch speeds.
[OnePlus 3 & 3T Cross Device Development] joshuous:
Just send me a pm
[OnePlus 3 & 3T Cross Device Development] joshuous:
No idea either, but wouldn't make sense for OnePlus to implement it so deeply if it doesn't provide some decent improvements. Just gotta experiment and hope it works
[OnePlus 3 & 3T Cross Device Development] uudruid74:
Wow. Sounds like it can be a lot of work to get it right and not introduce weird bugs. From what I read though, it basically keeps the process in memory. I don't know if never calls onDestroy() and just sends onStart() again the next time you run it, or if it does a full onCreate() again. I guess it would be simple enough to boot the latest OpenBeta with a logging test app and find out.

When I read about it, I always wondered how long it would be until custom ROMs tried it. I guess I have my answer :)
[OnePlus 3 & 3T Cross Device Development] Ferbee:
Sorry if i'm blind and didn't see it.

But is the kernel currently working with OOS Beta 10 for 3t, and does EAS work?

Thank You
[OnePlus 3 & 3T Cross Device Development] aPeN.Jr:
Joshuous just make kernel EAS for custom rom only not for OOS.

If you want to try EAS kernel OOS maybe you can try RenderBroken kernel.
[OnePlus 3 & 3T Cross Device Development] Sir_gpm:
If I like to stay hal1, is there a way to fix the front camera?
[OnePlus 3 & 3T Cross Device Development] StarShoot97:
I have a weird bug with this rom (clean install)

I go to settings and disable backlight on capacitive buttons lighting up, but they still do, even if the option is turned off

Also when using on-screen buttons and pressing the capacitive ones they light up, although they have no funtion
[OnePlus 3 & 3T Cross Device Development] AndreiVolk:
It's already been reported. Disable the backlight with a kernel manager until it gets fixed ;)
[OnePlus 3 & 3T Cross Device Development] Vincent_40:
Ok ROM clean flashed on my Op3 (and my wife's Op2).

So far so good.

Very strange when like me, you came to RR with lot of features. But it's simple, smoothie and no bug for the moment.

Oos camera port work better than on LOS ROM based.
[OnePlus 3 & 3T Cross Device Development] sjknight413:
The front camera always worked fine on OOS camera for me in Hal 1 mode, is it actually crashing for you?
[OnePlus 3 & 3T Cross Device Development] Vincent_40:
I've a little bug, when I stop wifi by the toggle, it doesn't switch to LTE.

Clean install

OB 20 fw

Opengapps
[OnePlus 3 & 3T Cross Device Development] uudruid74:
Mine does. Did you manually turn off LTE?
[OnePlus 3 & 3T Cross Device Development] Vincent_40:
I need to reboot my phone each time and my wife with his Op2 no.

I will try again after flash 4.1.6 fw. Maybe this issue is caused by OB fw.

Do you think same [MENTION=5880917]uudruid74[/MENTION] ?
[OnePlus 3 & 3T Cross Device Development] uudruid74:
I'm on latest OB firmware and weak signal. Very odd
[OnePlus 3 & 3T Cross Device Development] Vincent_40:
I'll try 4.1.6 fw this evening and repport
[OnePlus 3 & 3T Cross Device Development] uudruid74:
Does turning airplane mode on and off not bring it back?
[OnePlus 3 & 3T Cross Device Development] Vincent_40:
I don't know i have never tried
[OnePlus 3 & 3T Cross Device Development] Scarface1991:
Anybody here using Spotify? Sometimes it's getting out of control for me in the Background and killing my battery. I only listened to Spotify on the way to work and back which is a drive of about 15 minutes. While I was working it killed my battery doing whatever it was doing in the Background.

When I came home from work I had only about 50% left while usually I have over 70. It also consumed more battery than the display.

Also it has a pretty weird bug for me. The notification of my last played song would show up out of nowhere with the cover as if I just hit pause. The only thing that helps is killing the process by force which fixes both, the battery drain and thr notification bug.

Anybody else had an experience like that with Spotify?

However Android System is also a battery hog and I don't know how to "fix" it since I don't know which specific service is draining the battery. I rarely get over 3 1/2 hours of SOT doing ordinary stuff like texting, reddit, a little YouTube and no gaming.
[OnePlus 3 & 3T Cross Device Development] Sir_gpm:
No I tested and see no problem at all but was thinking about an improvement. But is not crashing and will stay in Hal1.
[OnePlus 3 & 3T Cross Device Development] Puddi_Puddin:
It keeps you device a wake? Can you try installing better battery stats.
[OnePlus 3 & 3T Cross Device Development] Scarface1991:
I have it installed but haven't used it for a while and just rebooted my phone so it could only show the data since boot. I'll post a Screenshot next time the battery drain happens.

How much drain is Android System causing you guys? It's on the top most of the times, often even draining more than display itself.
[OnePlus 3 & 3T Cross Device Development] RMarques:
Almost 10hrs sort of usage. Cellphone has been basically idle, but yeah Google Services is the villain of the story!
[OnePlus 3 & 3T Cross Device Development] Puddi_Puddin:
Android system drain is normal. Really depends on how bright your screen is.
[OnePlus 3 & 3T Cross Device Development] Scarface1991:
What SOTs are you guys getting on average?

I know everyone uses its phone different but it's just out of curiosity.
[OnePlus 3 & 3T Cross Device Development] Pollie81:
No issues over here with Spotify.

I use it on a daily basis..

Verstuurd vanaf mijn ONEPLUS A3003 met Tapatalk
[OnePlus 3 & 3T Cross Device Development] Scarface1991:
Weird, I already tried to Uninstall and re-download it from the Playstore and even redownloaded all my playlists but no luck.
[OnePlus 3 & 3T Cross Device Development] Diaze:
Does this rom have any status bar customization?
[OnePlus 3 & 3T Cross Device Development] uudruid74:
Best not to even ask since they aren't comparable. I would look at idle drain percentage, but even that should be measured by the same app. I see around 1%/hr idle drain measured by EX kernel manager.

It has substratum :) Subs can do anything. Also look in Settings -> System UI Tuner for the usual Statusbar tool to turn icons on and off.
[OnePlus 3 & 3T Cross Device Development] Diaze:
Any good substratum module to customize statusbar on this rom?
[OnePlus 3 & 3T Cross Device Development] uudruid74:
Depends on what you are trying to do. Xettings will give you center clock, more QS columns, and get rid of the "x" on disabled services. I mainly use it for the QS tile change because I want my QS columns to match the number of columns in my launcher (OCD). I don't do any wild changes
[OnePlus 3 & 3T Cross Device Development] kyledowling:
Can confirm. Happens to me often but not all the time. I turn on airplane mode for 1 minute and turn it off and problem is fixed.
[OnePlus 3 & 3T Cross Device Development] Boozzzr:
Long time lurker here, really like your work on this Rom. Clean and fast.

Just experienced a small issue taking a photo: it wasn't saved to the phone's memory. Started the camera app using the double press on the home button, shot the photo, and pressed the home button again after a short moment (after the 'gallery' thumbnail had disappeared). Checked in Google Photos and the pic wasn't there. Took the pic again and this time it did save. I've pasted the logcat of the first pic here: hastebin.com/kugufajapo.vbs
[OnePlus 3 & 3T Cross Device Development] _millig_:
I've experienced that twice too, I thought it was a missclick when it happened.
[OnePlus 3 & 3T Cross Device Development] phoberus:
Only asking because there are already some AOSPA features baked in here:

Do you want to include also the newer AOSPA features like Accidental Touch and Pocket Lock in the next builds?

The sources are released: https://github.com/AOSPA

Would be great, but now it's also great because of the cleanness
[OnePlus 3 & 3T Cross Device Development] Vincent_40:
After flashing 4.1.6 FW, the switch between wifi and LTE work fine. I think this issue is caused by OB FW.
[OnePlus 3 & 3T Cross Device Development] Lock:
Just a quick question as I seem to have missed the answer when looking through the thread.

Will the Waze issue be looked into? or is the advice just to use google maps with this rom and waze users should flash another?
[OnePlus 3 & 3T Cross Device Development] uudruid74:
I'm running latest OB firmware and switch between LTE and WiFi constantly. I've seen phones do this before. Try flashing OB firmware again and see if the problem comes back.
[OnePlus 3 & 3T Cross Device Development] Vincent_40:
Yes I will try with next update bcz it's very stable now
[OnePlus 3 & 3T Cross Device Development] RMarques:
Are we good to go with OB12?

Edit: Nope...not yet. It works OK with OB11 though.
[OnePlus 3 & 3T Cross Device Development] Kartike:
Congratulations on the recognised developer tag!

You deserved it very much:)

( I'm not late to the party..right?)
[OnePlus 3 & 3T Cross Device Development] uudruid74:
What issue is there with OB12?
[OnePlus 3 & 3T Cross Device Development] ram4ufriends:
I flashed OB 12 firmware and no issues yet
[OnePlus 3 & 3T Cross Device Development] RMarques:
Error 7 for me... I've tried just once though.
[OnePlus 3 & 3T Cross Device Development] uudruid74:
Error 7 doing what?