yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] Immortalis:
Unfortunately I can't build a ROM without bugs since kernel sources are missing, aka LiveDisplay and alert slider doesn't work on my build.

Can't be opensource if there is no source ¯\_(ツ)_/¯
[OnePlus 3 & 3T Cross Device Development] :
I've always thought it's this: https://github.com/SKULSHADY/android_kernel_oneplus_msm8996/tree/pie , isn't it?
[OnePlus 3 & 3T Cross Device Development] MoistPicklez:
New update up on Telegram. Thanks [MENTION=7578917]SKULSHADY[/MENTION] !
[OnePlus 3 & 3T Cross Device Development] Immortalis:
Ah yes, the secret sauce ?

I haven't seen it earlier, maybe I should try building again, thank you for link
[OnePlus 3 & 3T Cross Device Development] BrahmaGandhi:
safetynet status on latest build 12.14?
[OnePlus 3 & 3T Cross Device Development] MoistPicklez:
Not sure, I haven't bothered to flash it yet.
[OnePlus 3 & 3T Cross Device Development] rasikreality:
I would appreciate it if you could help me with the Android Auto bug. This ROM is great, and I would not like to have to change it for another just for this bug
[OnePlus 3 & 3T Cross Device Development] Reomar:
is VoLTE working on this rom ?
[OnePlus 3 & 3T Cross Device Development] deepak3048:
In my case not working I am on OOS 9.0.6 if any one have working volte then please tell me the installation process
[OnePlus 3 & 3T Cross Device Development] sun.sky4u:
[MENTION=7578917]SKULSHADY[/MENTION] Cts profile issue on latest build of 14th dec

View attachment 4902145
[OnePlus 3 & 3T Cross Device Development] BrahmaGandhi:
same here :confused:
[OnePlus 3 & 3T Cross Device Development] :
Have you tried setting ro.build.version.security_patch to match the build fingerprint of the build?

Read - not blindly flash!!! - this posting: https://xdaforums.com/oneplus-3/one...-nlos-16-0-t3879405/post78433987#post78433987
[OnePlus 3 & 3T Cross Device Development] BrahmaGandhi:
thanks, i've used magiskhide prop config. magisk module it passes safetynet for now

btw had no problem with previous 12.05 build
[OnePlus 3 & 3T Cross Device Development] seacowx:
Because the build fingerprint has changed on latest build using Pie;

OnePlus/OnePlus3/OnePlus3:9/PKQ1.181203.001/1907311932:user/release-keys

While previous build used Oreo; (which is passed safetynet)

OnePlus/OnePlus3/OnePlus3:8.0.0/OPR1.170623.032/02281230:user/release-keys

Hope that answer your curiousity.

__________________________

I notice few changes in /system/build.prop; ro.build.version.security_patch=2019-04-01

(Line also can be found in a /system/vendor/build.prop --Wild guess is a vendor thing, and shouldn't be a problem?)

And there's new line added; ro.havoc.build.version.security_patch=2019-12-05

(It seems ROM uses/read this one, as shown in about phone. So i think not a biggie).

Any idea/thoughts?
[OnePlus 3 & 3T Cross Device Development] Dsn Fouad:
I flashed this rom yesterday it's quite stable and smooth but can you add dark mode in phone dialer and sms ? That will be nice.
[OnePlus 3 & 3T Cross Device Development] :
ro.build.version.security_patch should only be in /system/build.prop.

ro.vendor.build.security_patch should only be in /system/vendor/build.prop.

ro.havoc.build.version.security_patch (surprise... ;) ) is havoc specific.

Only ro.build.version.security_patch (only occuring in /system/build.prop) has to match ro.build.fingerprint in order to apply to safetynet api (which is one reqirement to have a play protect certified status, which again is one requirement for gpay).

ro.vendor.build.security_patch may be used to indicatr the date of the used prebuilt blobs. ro.havoc.build.version.security_patch may be used to indicate the asb status of the havoc sources. You can always check the sources if interested in details. For the original issue/problem only ro.build.version.security_patch and ro.build.fingerprint are of interest.
[OnePlus 3 & 3T Cross Device Development] Egooo:
Way fast charge dont work ???
[OnePlus 3 & 3T Cross Device Development] Donglip:
Can you give a copy of the right built.prop (12 14 built) working ?
[OnePlus 3 & 3T Cross Device Development] seacowx:
I've red few.. I understood the "trick"..but uhm..I am not sure that's simply the case or the only culprit for safetynet fails. I am not an expert (for sure) and this is only for..let say a lite discussion..Also i'm willing to learn more from you.

For comparison...

Previous 12/05 system build.prop;

ro.system.build.fingerprint=OnePlus/OnePlus3/OnePlus3:8.0.0/OPR1.170623.032/02281230:user/release-keys

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

ro.build.fingerprint=OnePlus/OnePlus3/OnePlus3:8.0.0/OPR1.170623.032/02281230:user/release-keys

------------------------------------------------------------------

Latest 12/14 system build.prop;

ro.system.build.fingerprint=OnePlus/OnePlus3/OnePlus3:9/PKQ1.181203.001/1907311932:user/release-keys

ro.build.version.security_patch=2019-04-01

ro.havoc.build.version.security_patch=2019-12-05

ro.build.fingerprint=OnePlus/OnePlus3/OnePlus3:9/PKQ1.181203.001/1907311932:user/release-keys

------------------------------------------------------------------

If its the case the "ro.build.version.security_patch" has to be matchd with "ro.build.fingerprint"--vice versa. The 12/05 clearly didn't, but it still passed safetynet though. *Which i guess (one of the reason) because it use Oreo's certified fingerprint* cmiiw

So on latest 12/14 both "ro.build.version.security_patch and ro.build.fingerprint" has been changed. With safetynet fails.

<1st attempt> That case i simply tried to change only the ro.build.version.security_patch=2019-12-05 (it fails, as expected).

<2nd attempt> Changed only the fingerprint to Oreo: "8.0.0/OPR1.170623.032/02281230" (still failed).

<3rd attempt> Used same both fingerprint+security patch from working previous build 12/05 (it still failed, and it weird).

<4th attempt> Tried using the module.. and i chose the exactly same "Pie" fingerprint for OP3T: "9/PKQ1.181203.001/1907311932" and it worked and safetynet passed (and it really weird).

So, uh huh..What could've been wrong?

---------- Post added at 13:43 ---------- Previous post was at 13:32 ----------

Works fine here. And how do you know it doesn't work?

~Try drain your battery below 55% and plug in to your original dash charger specified, make screenshot, upload here.

*Make SS on lockscreen to see the current *mah

*Or use the Ampere app.
[OnePlus 3 & 3T Cross Device Development] Egooo:
When I plug charger max is 1.4A and dont see fast charge only charging ... And how to enable screen buton ?
[OnePlus 3 & 3T Cross Device Development] Dirk:
What did you test with and what steps were taken after each attempt? It would be a shame to have spent all that time editing and testing, only to have missed important steps like clearing Data on the Play Store App each time.
[OnePlus 3 & 3T Cross Device Development] seacowx:
On what percentage of battery while you plugged in and saw the 1.400mah?

*And it should say "dash charging" except you're using non stock charger, are you?

~dash charging could reach max. 3400±mah (typically below ±50%) and when the battery goes up to 60, 70, 80, so on.. it will gradually decreasing. See SS and you'll understand
[OnePlus 3 & 3T Cross Device Development] seacowx:
I've already prepared an edited original build.prop for each attempts. I copied/replaced within twrp.

After each attempts--clear cache/storage--force stop--re'open.

Of course, l've tried all on the first place; toggled on/off magisk hide, clear storage both MM and PS, hide MM.

Not a biggie anymore, module handled it.

So do you think which manual method should work? Or none.
[OnePlus 3 & 3T Cross Device Development] :
It is that easy. Please read the posting I linked for fp date doubles.

You can't just change the fp in the file, because they get also set via init (https://github.com/Havoc-Devices/android_device_oneplus_oneplus3/blob/ten/init/init_oneplus3.cpp). The magisk module uses resetprop.

For details see the conversation with [MENTION=2911853]BillGoss[/MENTION] on this in the nlos thread.

If your fp is OnePlus/OnePlus3/OnePlus3:9/PKQ1.181203.001/1907311932:user/release-keys you need a date of 2019-08-01 as explained in the posting I've linked.

---------- Post added at 16:24 ---------- Previous post was at 16:17 ----------

Yes. Always check with "adb shell getprop ro.build.fingerprint" if tbe file edit has worked. Keep an eye on permissions, sepolicy context and encoding (i.e. edited on windows and ****ed up the encoding) on replaced files. As soon as "adb shell getprop ro.build.fingerprint" returns 2019-08-01 you shpuld be good. For additional requirements to pass safetynet see the posting I've linked.
[OnePlus 3 & 3T Cross Device Development] Egooo:
good check in the evening, just tell me how to turn on the keys on the screen?
[OnePlus 3 & 3T Cross Device Development] babo1069:
Hi

How do I prevent the status bar from opening when the phone is locked?

Does Havoc OS have this feature?
[OnePlus 3 & 3T Cross Device Development] Dsn Fouad:
Yes look it up in settings
[OnePlus 3 & 3T Cross Device Development] Akagami1994:
Updated to 14/12 = works flawlessly. Again.

Hello! Just an update. wiped cache and dalvik cache and then dirty flashed Havoc 3.0- 14/12 with - ( ExliteGapps & Magisk 20.1 ) same files every time --> works flawlessly. No problems with Google accounts, banking apps or GPay or any other app. :)

to the DEV - forgot to thank you for the status bar DATE and TIME centered setting in the last update! This OS just keeps getting better. :angel:
[OnePlus 3 & 3T Cross Device Development] babo1069:
Thanks. I found.
[OnePlus 3 & 3T Cross Device Development] Master_TC:
Banking apps and Gpay work without magisk hide?

Whitch banking apps do you use?
[OnePlus 3 & 3T Cross Device Development] prateektaneja:
Same here, doesn't work even on the latest build. Any help?
[OnePlus 3 & 3T Cross Device Development] Tech35:
Screen off gestures

I noticed that i cant disable double tap to wake. I can change it to sth other action like next track etc, but that is it.

Is there a config i can mess with to do that?
[OnePlus 3 & 3T Cross Device Development] KamiGooDz:
works on Oneplus 3t????
[OnePlus 3 & 3T Cross Device Development] Viper The Ripper:
The ROM?

ALL ROMS YOU FIND IN THIS SECTION WORK ON BOTH MODELS op3/op3t!!
[OnePlus 3 & 3T Cross Device Development] trinimike100:
Anyone whatsapp freezing when typing and force closing?
[OnePlus 3 & 3T Cross Device Development] deepakd:
Dash charging support?

Does it support Dash charging?
[OnePlus 3 & 3T Cross Device Development] PWMx:
Encrypting is still broken. Data needs to be formatted in order to recover from resulting bootloop.
[OnePlus 3 & 3T Cross Device Development] KamiGooDz:
doesn't facial unlocking work?
[OnePlus 3 & 3T Cross Device Development] kkshines:
Notch cutout on top right

I have been using Havoc OS 3.0 for some weeks, everything works fine.

Recently out of nowhere a notch type cutout appeared on the top-right corner. All of the icons are condensed(battery and network icons etc.) to fit this cut out

I searched in the settings to disable if I had accidentally enabled it. No luck so far.

How to correct this?
[OnePlus 3 & 3T Cross Device Development] rohan164:
upload screenshots!!
[OnePlus 3 & 3T Cross Device Development] StanvdT:
After formatting data, installing 9.0.6 firmware and installing havoc 3.0 with gapps and magisk, I get a 'Android Setup keeps stopping' error when the phone boots.

Anyone any suggestions?
[OnePlus 3 & 3T Cross Device Development] rasikreality:
Please :(
[OnePlus 3 & 3T Cross Device Development] closedcircuit:
Havoc 12-15 - Phone is randomly muting ringer and notifications

Is anyone else experiencing random ringer and notifications muting? This happened when I upgraded from Havoc 2.8 to Havoc 3.0 12-4 and now with 12-15. Does anyone know where to look or what app to use to see what's changing the sound settings? Thanks.

---------- Post added at 02:26 PM ---------- Previous post was at 02:02 PM ----------

By any chance are you using the nano package of opengapps beta for Android 10? I normally use the stock package and found that it wouldn't complete a cloud restore and would keep on crashing until I reinstalled Havoc using the nano package.

Edit: 12/19/19

911 emergency calling also seems to broken on the 12/14 build. In the past when I experienced 911 call issues on other ROMs, the call would still connect but you lost access to the dialer and could not end the call or access the numpad. In this instance when attempting to call emergency services (911), the dialer just refused to connect the call. This error was repeatable even with a reboot
[OnePlus 3 & 3T Cross Device Development] StanvdT:
Yes, I used nano package. I fixed it however by deleting a setup folder in file manager via TWRP, I believe it was something like /system/data/priv-app/Setupsomething. Can't remember exactly what it was but it wad something like that.
[OnePlus 3 & 3T Cross Device Development] bkuri:
I have a similar problem with the 12/14 build, except that my battery percentage is stuck at 0%. I just tried rebooting and the problem remains. Did you manage to fix this somehow? Thanks!

EDIT: The battery level shows up ok in TWRP. Also, wiping cache/dalvik seems to have helped for now.

EDIT 2: Reading just went back to 0% as soon as I finished sending this message. :/
[OnePlus 3 & 3T Cross Device Development] mnsiw:
Havoc 3.0 December 14 build, it does not show weather with text clock or am I missing something.
[OnePlus 3 & 3T Cross Device Development] bkuri:
EDIT: Found the issue. Switching SELinux to permissive did the trick. Pretty sure that it must have something to do with the Magisk+Xposed combination that I'm running right now. Quick tile long press on "Battery Saver" tile still doesn't work, though!

Apologies for the noise! Hope this helps someone.
[OnePlus 3 & 3T Cross Device Development] gps3dx:
1. I hope that when you "upgraded" you wiped "Data" partition - made a CLEAN UPGRADE.

( otherwise expect bugs ).

2. about the 911 issue... check you gave the built-in dialer app (com.android.dialer) all the permissions it wants.

I suspect for some time (and HAVOC v3.0 releases) that the dialer don't have and don't ask for permissions - even though it is a 'system app'.
[OnePlus 3 & 3T Cross Device Development] Nixeus:
Hello, anyone know if Encryption on this on the road ?
[OnePlus 3 & 3T Cross Device Development] closedcircuit:
I followed the dirty flash upgrade instructions from skullshady that only stated to wipe dalvik and cache and in addition also wiped system, I did leave /data intact. Thankfully I was able to resolve the auto muting issue. By sheer luck I happened to be using the phone with the screen on when the ringer mute engaged and I imediately checked my notifications widget and found the culprit. It turned out to be Accubattery, some of it's notifications needed to be turned off, more specifically "Charge alarm", "Charge alarm (DND)" and "Other" Since turning off these notifications I haven't experience a single random muting incident. :victory:

Regarding 911 emergency services bug. The phone app has all requested permissions and there are no permissions denied. See attached screenshot. Can anyone reccomend a good logcat app that works in android 10. Syslog doesn't seem to work on Q and I want to be ready to pull the logs in the event this happens again.
[OnePlus 3 & 3T Cross Device Development] mnsiw:
:good:
[OnePlus 3 & 3T Cross Device Development] :
adb logcat -d (if you don't like wired adb, use adb over network).
[OnePlus 3 & 3T Cross Device Development] LastWord92:
Hi, i can't find the option to clear all recents, please help. Another thing, i want to install one plus launcher and file manager, can i do that?
[OnePlus 3 & 3T Cross Device Development] aimanfaeiz:
Recent button problem

Hi.. just flash this rom recently.. I've got some issue regarding the hardware button.. can't use the recent action.. and also of i disable the hardware button, there's no navigation button appear.. also can't use the gesture feature..
[OnePlus 3 & 3T Cross Device Development] ememeh:
Hi. I'm thinking of using Havoc now that OOS-based ROMs won't get further updates. I have two questions though:

Are the OS 3 nightlies still pretty buggy? That's what I've heard.

Does the latest OS 2.9 have the Dec '19 security patch? That's my main motivation for flashing a new ROM at this point.

Edit: grammar
[OnePlus 3 & 3T Cross Device Development] :
https://github.com/Havoc-OS/android_build/blob/pie/core/version_defaults.mk#L234
[OnePlus 3 & 3T Cross Device Development] Immortalis:
Mine unofficial does, but I'm not sure if it's ok to publish it here
[OnePlus 3 & 3T Cross Device Development] tim-scrap:
As long as you not say it is your Rom just offer an update. Why shouldn't?

I also would like it. Will go later to 3.0.
[OnePlus 3 & 3T Cross Device Development] rohan164:
please suggest me good and recommended GApps, which are stable & with no issues!
[OnePlus 3 & 3T Cross Device Development] Donglip:
Use Gapps nano
[OnePlus 3 & 3T Cross Device Development] Immortalis:
Havoc 3.0 users: please ignore this post.

Havoc 2.9 update 2019-12-22

A few users (including me) were interested in an update of Pie-based ROM, but

since official version is end-of-life, I decided to do it myself.

Credits to [MENTION=7578917]SKULSHADY[/MENTION] and [MENTION=4608158]ZeNiXxX[/MENTION] for creating original HavocOS ROM

and [MENTION=4405529]nvertigo67[/MENTION], because I yoinked a few things from your device tree ( ͡° ͜ʖ ͡°)

Changelog:

Merged October, November and December security patches

Bumped audio bitrate to 320 kbps

Disabled noise suppression in audio recordings (but volume might be low to avoid clipping)

Enabled initial DFS Wi-Fi channel scan

Use OOS 9.0.5 fingerprint

Known issues:

SafetyNet will fail because fingerprint and security patch date do not match.

Please use MagiskHide Magisk module or read this post
​

All remaining official Havoc OS bugs

Installation guidelines:

Make (as always) a backup of your current system (boot, system and data)

Clean flash not needed, but clear cache and dalvik-cache

Flash like official

Download
[OnePlus 3 & 3T Cross Device Development] Donglip:
Why ? Not identical ?
[OnePlus 3 & 3T Cross Device Development] Immortalis:
Havoc 2.9 is based on Android 9, while Havoc 3.0 is based on Android 10, so these two are different major Android versions
[OnePlus 3 & 3T Cross Device Development] migui7:
Hello, I have Havoc 3.0. I have many problems with android auto. It work 1/10 times. Somebody have one solution to android auto?
[OnePlus 3 & 3T Cross Device Development] LS.xD:
Encryption password?

I'm coming from stock OOS 9.05 and would like to switch to Havok 3.0. My problem is that I have to enter an encryption password, if I want to boot up Havoc 3.0. Will I need to decrypt the storage before installing the custom rom?
[OnePlus 3 & 3T Cross Device Development] faiz5200:
Thank you so much. I not sure what you did because since 2.9, one of my banking app cannot pass login page even after hide magisk. But now the app work in your current build. Awesome work :good::good::good:
[OnePlus 3 & 3T Cross Device Development] AlfaRune:
Havoc 3.0 2019-12-23 changelog?
[OnePlus 3 & 3T Cross Device Development] Viper The Ripper:
https://t.me/Havoc_OS/1740
[OnePlus 3 & 3T Cross Device Development] xNAPx:
What about the pico version? Is it stable too? I like to be as minimal as possible

---------- Post added at 03:42 PM ---------- Previous post was at 03:41 PM ----------

What about the pico version? I like to stay as minimal as possible
[OnePlus 3 & 3T Cross Device Development] Immortalis:
Good to know, thanks and enjoy :)

Merry Xmas everyone, have a peaceful and wonderful time
[OnePlus 3 & 3T Cross Device Development] Donglip:
https://github.com/opengapps/opengapps/wiki/Package-Comparison#wiki-pages-box
[OnePlus 3 & 3T Cross Device Development] pxrave:
works superb, thanks you very much for update. so i will wait a bit to upgrade to buggy 3.0..btw why you forced 320kbs audio?
[OnePlus 3 & 3T Cross Device Development] Immortalis:
A small price to pay for salvation

...i mean it's free real estate quality upgrade with small increase in file size
[OnePlus 3 & 3T Cross Device Development] Unlimate:
hello everyone

I have successfully installed Havok 3.0 only having one problem recent app button is not working any suggestions?
[OnePlus 3 & 3T Cross Device Development] prajjwal2345:
Have a few doubts, if anyone can help (I'm currently on Pixel Experience - Android 10)

-Do I need to again FORMAT data (& not WIPE DATA) for switching to Havoc 3.0?

-How's the battery life on this ROM?

-Does the 'enabling gesture navigation' zip work and enables gesture nav-BAR? (like that bottom bar being visible and functional?)
[OnePlus 3 & 3T Cross Device Development] iceman0826:
Nice! Seeing that all eyes are on the Android 10 and the audio Mods (Sauron) that I'm using are still inckmpatible with it, this is a godsend ?

Will continue to use this, until Havoc 3.0 can match the 2.0. :)
[OnePlus 3 & 3T Cross Device Development] xoancg:
Yes. First, make a backup and save it out of the phone as EVERYTHING will be deleted except recovery. Then, format data: TWRP > Wipe > FORMAT DATA

Then, follow the clean installation instructions:

Clean Flash:

Wipe all partitions except internal

Flash Havoc, GApps, Magisk

Reboot to System​
[OnePlus 3 & 3T Cross Device Development] Keyvannn:
Is this rom good for daily driver and better than oos 9.0.6?
[OnePlus 3 & 3T Cross Device Development] xoancg:
I come from OOS 9.0.6 and for two days I have been testing this ROM. In my experience, it is a very stable and fully functional ROM for normal daily use. Also, I think the update to Android 10 looks great on our device.

In another order of things, I see that it is necessary to decrypt the storage to install this ROM. Is there a problem if, after installation, we encrypt again from Settings> Security> Encryption and credentials> Encrypt phone? Would the system work and could updates be installed from TWRP? (Or am I asking nonsense?)
[OnePlus 3 & 3T Cross Device Development] :
If you search the thread, you'll find current state of encyption implementation:

https://xdaforums.com/search/thread/3782811?query=encrypt

(Sidenote: searching before ppstimg is xda rule #1: https://xdaforums.com/announcement.php?a=81 )
[OnePlus 3 & 3T Cross Device Development] B0mbsp4tz:
I'm using BiTGapps, it's minimal and working on android 10.

https://xdaforums.com/android/software/custom-bitgapps-android-t4012165
[OnePlus 3 & 3T Cross Device Development] lancebuks:
WORD!!!
[OnePlus 3 & 3T Cross Device Development] xNAPx:
Wow didn't know about it. Unfortunately I already clean flashed the rom and used Pico gapps, how is pico gapps compared to BiTGapps? What are the differences?
[OnePlus 3 & 3T Cross Device Development] :
Google Camera

After installing the latest version, my google camera app no longer working.
[OnePlus 3 & 3T Cross Device Development] Chevan94:
Hello!

I'm currently on Skydragon OS Pie, on 5.0.6 (?) firmware I believe ( didn't update to Pie blobs for sure), encrypted, and I want to install Havoc 3.0.

What are the steps I need to take? Which is the correct firmware I need to install?

I've heard encryption doesn't work. Does that mean I need to wipe internal storage first before installing?

I'm on Skydragon TWRP right now. Is there a specific version of TWRP I need to install the firmware and ROM?
[OnePlus 3 & 3T Cross Device Development] xoancg:
What version of Google Camera do you mean? Do you mean the port for 3/3T devices or the application that you download from Google Play for Pixel devices that you can download with Havoc OS?
[OnePlus 3 & 3T Cross Device Development] :
The app dowloaded from Google Play.

The app whit Havoc OS is still working fine.

Is it posible to install the oneplus camera?

If yes how or where can i download it?
[OnePlus 3 & 3T Cross Device Development] blue-gem:
The November version feels smooth to use; now, it feels more dull as it gets updated.

--------Now I think that the stutter should be caused by opengapps.