[ROM]-[23.07.20]-Havoc-OS-3.7-[10.0.0_r40]-[Official]

[hkdoublecat]

Can I safely assume the installation procedure on page 1 also apply to Havoc 4.6?

As I cannot find a Havoc 4.X thread but just 3.7 here on OP7pro forum.

 

[rustydusty222]

Hey dude,

I had the same exact issue. I tried doing a clean flash several times, with no luck. It's not just the proximity sensor, it's all the sensors. The ambient light sensor, the compass, gyroscope, barometer. None of them work at all.

But, I figured out how to get them working.

You just need to flash the persist partition.

1) Download this zip file, extract the .img file from it. https://androidfilehost.com/?fid=6006931924117929081

2) Enter fastboot mode, and type:

fastboot flash persist persist.img

Now all of your sensors will work perfectly under Havok.

if this dose not work then flash your stock rom and then flash custom recovery
and flash persist img via custom recovery

 

[hkdoublecat]

is the Op7pro scrolling-screenshot not working on this rom?

 

[DannSmith]

is the Op7pro scrolling-screenshot not working on this rom?

Nope, no scrolling screenshot.

 

[HippoMan]

I have a question about how the Havoc ROMs handle Doze.

The stock Oxygen OS 10.x on my OnePlus 7Pro is horrible with regard to Doze mode. A number of apps do not get timely push notifications, even when whitelisted (i.e., even with Battery Optimization turned off), and even when the App Standby Mode is set to "active" for those apps (in fact, it seems like OOS sets all apps to be in "active" App Standby Mode and then totally ignores that setting). Furthermore, all the Doze profiles I've set via settings put global device_idle_constants [settings values] do not fix this problem with missed push notifications.

How does Havoc behave with regard to this? Are there problems with delayed push notifications? Or does Havoc manage this more effectively and intelligently than OOS?

I'm gladly willing to live with somewhat worse battery life in return for always receiving all push notifications in a timely manner.

Thank you in advance for any information about how Havoc behaves in this regard concerning Doze.

 

[Toutatis_]

I have a question about how the Havoc ROMs handle Doze.

The stock Oxygen OS 10.x on my OnePlus 7Pro is horrible with regard to Doze mode. A number of apps do not get timely push notifications, even when whitelisted (i.e., even with Battery Optimization turned off), and even when the App Standby Mode is set to "active" for those apps (in fact, it seems like OOS sets all apps to be in "active" App Standby Mode and then totally ignores that setting). Furthermore, all the Doze profiles I've set via settings put global device_idle_constants [settings values] do not fix this problem with missed push notifications.

How does Havoc behave with regard to this? Are there problems with delayed push notifications? Or does Havoc manage this more effectively and intelligently than OOS?

I'm gladly willing to live with somewhat worse battery life in return for always receiving all push notifications in a timely manner.

Thank you in advance for any information about how Havoc behaves in this regard concerning Doze.

I can't answer you unfortunately, I never had this kind of issue back in the days when I was using A10 custom ROMs, including Havoc.

Just curious, why don't you update to OxygenOS 11/A11 custom ROM/A12 custom ROM?

 

[HippoMan]

I can't answer you unfortunately, I never had this kind of issue back in the days when I was using A10 custom ROMs, including Havoc.

Just curious, why don't you update to OxygenOS 11/A11 custom ROM/A12 custom ROM?

Thank you very much.

I am staying with OOS 10 because if I upgrade to A11 or A12, I will then have to go down into the dizzying rabbit hole of trying to get Magisk and TWRP to work with those OS versions, which currently is not possible without lots of painful headaches ... if at all.

A10 works fine for me with Magisk (stable version 23.0) and TWRP ... just not with push-notifications.

If some day Magisk and TWRP can function well under A11 or A12, I will then consider upgrading.

But actually, it's promising that you didn't have push-notification issues under Havoc and other custom A10 ROMs. I am considering moving to one of these custom ROMs now.

 

[Toutatis_]

Thank you very much.

I am staying with OOS 10 because if I upgrade to A11 or A12, I will then have to go down into the dizzying rabbit hole of trying to get Magisk and TWRP to work with those OS versions, which currently is not possible without lots of painful headaches ... if at all.

A10 works fine for me with Magisk (stable version 23.0) and TWRP ... just not with push-notifications.

If some day Magisk and TWRP can function well under A11 or A12, I will then consider upgrading.

But actually, it's promising that you didn't have push-notification issues under Havoc and other custom A10 ROMs. I am considering moving to one of these custom ROMs now.

I see.

If you don't care about running unencrypted, you could also use crDroid. Still on 11 but encryption is disabled on purpose to allow users to use TWRP and flash updates "the old way". I don't think it's worth the risk but it's an option and some people are still using it.

I'm on Android 12 and while things are slightly different when it comes to flashing, it's not that difficult in my opinion. If you're familiar with adb and fastboot commands, you're almost good to go.

The only new stuff is that you need to extract the boot.img file with a tool called "Payload Dumper" to access the built-in recovery. Once again, it sounds way more complicated than it is really. There is a bit of setup depending on your OS and the tool you choose but once you're done, it's only a matter of one command. As far as I'm concerned, I just have to run:

payload-dumper-go -p boot ROM.zip

and it takes 5 seconds or so (again, depends on your hardware). Plus, you can use the same boot.img to flash a different ROM. Recently I used an old ArrowOS boot.img to flash EvolutionX because the latter had some issues with the recovery, it worked perfectly fine. Some maintainers even directly provide a separate download link and some users (including me) upload it if people ask for it, for convenience.

I don't even miss TWRP now, I just got used to how things work on Android 12. I miss Android 10 because of Resurrection Remix though.

Hopefully you'll somehow find a fix for your delayed push notifications issue, this must be annoying for sure.

 

[SlyUK]

Wishing everyone hear a Merry Christmas and Happy New Year

May I ask:

What are the chances of this Rom being developed for the OnePlus 10 Pro in 2022/23 kindly ?

 

[samslam41]

I can't answer you unfortunately, I never had this kind of issue back in the days when I was using A10 custom ROMs, including Havoc.

Just curious, why don't you update to OxygenOS 11/A11 custom ROM/A12 custom ROM?

Havoc is has been on android 11 for a while now. They mentioned somewhere else that they won't be updating much here anymore. Lol, the number one spot to post updates and support the development of this ROM with the community. Talk about setting yourself up for failure

 

[samslam41]

I see.

If you don't care about running unencrypted, you could also use crDroid. Still on 11 but encryption is disabled on purpose to allow users to use TWRP and flash updates "the old way". I don't think it's worth the risk but it's an option and some people are still using it.

I'm on Android 12 and while things are slightly different when it comes to flashing, it's not that difficult in my opinion. If you're familiar with adb and fastboot commands, you're almost good to go.

The only new stuff is that you need to extract the boot.img file with a tool called "Payload Dumper" to access the built-in recovery. Once again, it sounds way more complicated than it is really. There is a bit of setup depending on your OS and the tool you choose but once you're done, it's only a matter of one command. As far as I'm concerned, I just have to run:

payload-dumper-go -p boot ROM.zip

and it takes 5 seconds or so (again, depends on your hardware). Plus, you can use the same boot.img to flash a different ROM. Recently I used an old ArrowOS boot.img to flash EvolutionX because the latter had some issues with the recovery, it worked perfectly fine. Some maintainers even directly provide a separate download link and some users (including me) upload it if people ask for it, for convenience.

I don't even miss TWRP now, I just got used to how things work on Android 12. I miss Android 10 because of Resurrection Remix though.

Hopefully you'll somehow find a fix for your delayed push notifications issue, this must be annoying for sure.

Resurrection remix was amazing! I hope they start developing again and never stop after they do so. I wish evolution x made a vanilla version .

 

[singingandroid]

Any tips for running this on Visible Wireless?

 

[HippoMan]

I see.

If you don't care about running unencrypted, you could also use crDroid. Still on 11 but encryption is disabled on purpose to allow users to use TWRP and flash updates "the old way". I don't think it's worth the risk but it's an option and some people are still using it.

I'm on Android 12 and while things are slightly different when it comes to flashing, it's not that difficult in my opinion. If you're familiar with adb and fastboot commands, you're almost good to go.

The only new stuff is that you need to extract the boot.img file with a tool called "Payload Dumper" to access the built-in recovery. Once again, it sounds way more complicated than it is really. There is a bit of setup depending on your OS and the tool you choose but once you're done, it's only a matter of one command. As far as I'm concerned, I just have to run:

payload-dumper-go -p boot ROM.zip

and it takes 5 seconds or so (again, depends on your hardware). Plus, you can use the same boot.img to flash a different ROM. Recently I used an old ArrowOS boot.img to flash EvolutionX because the latter had some issues with the recovery, it worked perfectly fine. Some maintainers even directly provide a separate download link and some users (including me) upload it if people ask for it, for convenience.

I don't even miss TWRP now, I just got used to how things work on Android 12. I miss Android 10 because of Resurrection Remix though.

Hopefully you'll somehow find a fix for your delayed push notifications issue, this must be annoying for sure.

Thank you very much. Based upon your suggestion, I might try crDroid.

Yes, I know about payload_dumper and flashing the ROM that way.

The only thing I really want TWRP for is nandroid backups. I want backups for more than just my apps, contacts, media content, etc. With nandroid, I could back up boot, system, vendor, and data, then try a new OS, and then go back to the old OS simply by restoring the nandroid backup.

 

[TheBassDude]

Use this method to install custom roms:

Boot to TWRP
Format Data
Reboot to TWRP

Install latest Stock OOS
Install Havoc
Install TWRP
Reboot TWRP

Install latest Stock OOS again
Install Havoc again
Install TWRP again
Reboot TWRP

Install Gapps (optional)
Install Force Encrypt Disabler
Format Data again
Install Magisk
Reboot System

If you it in that order you should have no issues. I've always done it that way since Android 10 and never once had any issues.

Been struggling to get a solid install with working OTA's and this did the trick. Followed your instructions with one exception; I did not flash OOS either time, just HavocOS and TWRP. As for OTA's, I was finally able to flash the TWRP retention script and install Magisk to inactive slot after OTA installation but before the reboot. Wasn't able to do that before. Thanks for the instructions. This is the way!

 

[sagit12138]

Question! Does this rom feature Slim recents, or some alternative to the stock recent option?

 

[sagit12138]

hi, Does this rom feature Slim recents, or some alternative to the stock recent option?

 

[malik6520]

Does this rom has built in phone recorder and can I install kali nethunter on it.

 

[vladvlad12]

I need to activate VoFi now but need to enter enginerr mode and activate full switch, how to do that?

 

[J_E_N_K_O]

to delete

 

[N-Gage4ever]

Thank you very much.

I am staying with OOS 10 because if I upgrade to A11 or A12, I will then have to go down into the dizzying rabbit hole of trying to get Magisk and TWRP to work with those OS versions, which currently is not possible without lots of painful headaches ... if at all.

A10 works fine for me with Magisk (stable version 23.0) and TWRP ... just not with push-notifications.

If some day Magisk and TWRP can function well under A11 or A12, I will then consider upgrading.

But actually, it's promising that you didn't have push-notification issues under Havoc and other custom A10 ROMs. I am considering moving to one of these custom ROMs now.

I think same like you. Never update to A11 or A12...