[ROM][EAS][7.1.2_r33]★ Pure Fusion OS ★[OMS / PocketLock / GCam / OOS Cam]

[EatBeans]

Use swift black theme but don't apply the overlay to androidsystem.

Why shouldn't he apply it on android-system? I'm using it currently and it works fine.

Edit: Sorry didn't read properly

 

[joakimbo]

Use swift black theme but don't apply the overlay to androidsystem.

If I do that my settings ends up like this..

 

[EddyH1993]

If I do that my settings ends up like this..

So you only want the settings app to be themed rather than the quick settings and notifications?

Edit: nevermind I thought not enabling that would work.

 

[joakimbo]

So you only want the settings app to be themed rather than the quick settings and notifications?

I want quick settings theme. Only thing I don't want themed is the dark notifications..

 

[EddyH1993]

I want quick settings theme. Only thing I don't want themed is the dark notifications..

Ah I see, I don't know of such theme, sorry for the confusion.

 

[uudruid74]

Also giving it a try after watching for a few days. Was on PAEX 4.4 and VERY happy with that. What I'm having an issue with on this one is the OOS-Camera Selfie Smile Capture option doesn't seem to work. I smile a bunch and nothing triggers. With the GoogleCamera the Processing of an image after Lense Blur photo is taken stops a 50% and after a bit crashes the app.

Well, ran into another issue. I set a PIN + Fingerprint during initial setup and it worked just fine until I rebooted. I, with PAEX and every other ROM I've used on my OP3T, have been doing this exact thing every time and when I rebooted with this ROM afterwards it keeps saying Wrong PIN. I went into TWRP thinking, lemme re-flash, see what happened... TWRP wouldn't recognize the PIN at startup so I tried my Google Account Password for giggles and it worked... What the what? So that got me back into TWRP. Reflashed the ROM, now a few times under an odd frustration, and no matter what, it won't recognize the PIN on first boot, just like when I rebooted after my first flash. I've tried entering the PIN as my password from my Google Account, like the old days of phone calls on a flip phone... nope, wrong pin. Tried 0000, I'm lost, what did I do wrong? I've not had an issue any other time before.

How can I wipe/reset it all to get back in my phone? I formatted the partitions again too.

Added Note: Did NOT restore anything from a backup, never do. Everything I find from searching is pointing me to files my phone doesn't have, since I wiped Internal, System, etc... already in TWRP. Being able to access TWRP using my Google Account Password is really odd. No idea how that's what it turned into instead of the PIN that's been there since every ROM before this one, and even used that same one this time too.

You can wipe pin using this ...
http://eddon.systems/Download/Pattern-Password-disable.zip

Sent from my OnePlus3T using XDA Labs

 

[Eremitus]

Is there any way to change lte+ indicator to 4G/4G+ instead. Tried to Google it but no luck without xposed.

EDIT. Damn, there was option for it. Was looking in the wrong place.

 

[RealDanyo]

Yes you can

Pure Nexus Settings -> Statusbarsettings -> Statusbarsymbols -> (First option, show 4G instead of LTE)

 

[siankatabg]

New build is UP!

Highlights:

• Removed TouchscreenGestures and OnePlusAmbient doubled options from the main Settings menu (You can now find them under "Settings > Gestures" only)
• AppOps moved to ROM Control tab in main Settings
• Fixed Notification/Battery led customisation
• Fixed Accidental touch blocking the BACK button on navigation bar

Full changelog: HERE

 

[redsmith]

White LED screen of death after dirty flashing... anyone else? Should I perform a clean flash?

 

[oux]

White LED screen of death after dirty flashing... anyone else? Should I perform a clean flash?

if a dirty flash doesn't work it sounds like a good idea to try a clean flash

 

[fcisco13]

White LED screen of death after dirty flashing... anyone else? Should I perform a clean flash?

Had one yesterday while making a call and pressing speaker phone, it froze, screen went black and white led. No f2fs all ext

Sent from my ONEPLUS A3000 using Tapatalk

 

[siankatabg]

Had one yesterday while making a call and pressing speaker phone, it froze, screen went black and white led. No f2fs all ext

This thing happens on random phones and I've no idea why, never happened to me and I never received a log for it. I'm almost sure it's caused by some mod.

 

[redsmith]

White LED screen of death after dirty flashing... anyone else? Should I perform a clean flash?

Dirty flashed once more and everything's fine now. That was weird.

 

[joakimbo]

Hmm.. when I press download update in the update app it says its 713mb, but it downloads in 1sek and then I'm able to press install. That can't be correct? I'm afraid to flash some half-downloaded file..

 

[afrob]

Thanks for your Work

 

[svandasek]

Hmm.. when I press download update in the update app it says its 713mb, but it downloads in 1sek and then I'm able to press install. That can't be correct? I'm afraid to flash some half-downloaded file..

You are probably downloading the wrong file, it is the one with the folder icon! (Zip)

 

[Skinpipe]

clean flashed today and my phone is super quick running f2fs also and latest bluspark twrp, thanks dev really great work

 

[siankatabg]

Hmm.. when I press download update in the update app it says its 713mb, but it downloads in 1sek and then I'm able to press install. That can't be correct? I'm afraid to flash some half-downloaded file..

The OTA app is under heavy work from @prstoreo and @tabp0le, so better use the normal download and flash method the next few days. When they're ready and all is fine there will be a note from me about what's happening and what's new.

Thanks and sorry.

 

[calvinistmac]

Had one yesterday while making a call and pressing speaker phone, it froze, screen went black and white led. No f2fs all ext

Sent from my ONEPLUS A3000 using Tapatalk

The white LED is caused by a kernel panic. It's a superiorly random bug. It happens more on the 3T than the 3. Last thing I remember causing it was SDCARDFS.