yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] TechTiks:
I am using the new Nanodroid package.

I didn't use the systest. Like previously I installed microg and used its selftest. Spoofing is detected as supported, permission is granted, but the signature doesn't get spoofed.

Of course the havoc option for signature spoofing is enabled.

I've done the Nanodroid systest for you and that's the output: https://pastebin.com/Tk5egtkC

The patcher detects sigspoofing support and aborts. So I can't use the new patcher (as expected).

Nonetheless microg still shows that the signature does not get spoofed.

I noticed that there is no signature spoofing permission listed under app permissions settings like in other ROMs. Maybe that's connected to the problem.
[OnePlus 3 & 3T Cross Device Development] grandpajiver:
I forgot to bookmark the thread.

Search Androidfilehost for [Oreo-Pie]Dolby+Digital+Plus-[UNiTY][Light]_by_repey6-20181127.zip

I had v4a+ice+aml for audiomods. I flashed that zip in magisk and it worked with viper.

I eventually removed ice sound and just have v4a, Dolby digital, and aml for audio mods.

Note: this is not Dolby Atmos.

Before flashing any of the above, I froze musicfx.
[OnePlus 3 & 3T Cross Device Development] jaymoker:
Can you post a screenshot of microg checkboxes ?

And also one for app permissions list please.

For the app permissions, sometimes you have to enable "Show system" under the right top corner 3 points menu.

Edit: Did you need to enable an option in SkyDragon or AOSiP to enable signature spoofing ?

Or it was working out of the box ?
[OnePlus 3 & 3T Cross Device Development] TechTiks:
I flashed back to another ROM and can't give you a screenshot anymore. What's important: The first two microg selftest boxes are checked and the third isn't.

In short the first is sigspoofing supported, the second is sigspoofing permission granted and the third is the test for signature itself.

The other ROMs worked out of the box.

EDIT: I will just wait now for another reaction here. There wasn't anyone besides me that could confirm or deny my bug report.

It feels like going round in circles. I think this whole thing is reproducible.
[OnePlus 3 & 3T Cross Device Development] tigerputzi:
at my phone the toarch light not working too, did dirty flash from kast buld 31.12.18, with the last buld torch was working.
[OnePlus 3 & 3T Cross Device Development] MarkusJu:
After a few days running (build 11.01.19), alarm clock didn't work in the morning; it was 0:22 for a few seconds when i activated screen and then actualized to 6:25.

Widgets crashed.

Flashed HolyDragon kernel back, i'll try if it works with this kernel.

Clean flashed.
[OnePlus 3 & 3T Cross Device Development] Tronje:
in developer options there is a point

Bluetooth -A2DP-Hardware-Offload disable

but it's greyed out and I don't know what it means and how to disable

maybe this would solve my problem with no ringtone over car handsfree audio (there is absolute silence on incoming call)
[OnePlus 3 & 3T Cross Device Development] jaymoker:
It would be better to use this app to check if signature spoofing is working or not.

I toggled the "Allow signature spoofing" switch, checked in terminal with the command

settings get global allow_signature_fake

I'm getting 1 when the switch is enable, 0 when the switch is disabled.

So the switch is working.

I went through the source code of Havoc and SkyDragon to see if I could find something related to signature spoofing and that could explain why it works on SkyDragon and not on Havoc.

What I found so far about fake-signature is :

Havoc's signature spoofing implementation in ServiceWatcher.java and PackageManagerService.java (search mayFakeSignature in PackageManagerService).

SkyDragon's signature spoofing implementation in PackageManagerService.java

No modification has been made to ServiceWatcher.java in SkyDragon (related to UnifiedNlp)

The only difference in the modification of PackageManagerService.java between Havoc and SkyDragon is that, in Havoc, the value of the switch "Allow signature spoofing" is retrieved and checked in order to allow signature spoofing for any package :

Havoc

if (permissions.contains("android.permission.FAKE_PACKAGE_SIGNATURE")
&& p.applicationInfo.targetSdkVersion > Build.VERSION_CODES.LOLLIPOP_MR1
&& p.mAppMetaData != null
&& [COLOR="Red"]android.provider.Settings.Global.getInt(mContext.getContentResolver(),
android.provider.Settings.Global.ALLOW_SIGNATURE_FAKE, 0) == 1[/COLOR])

SkyDragon

if (permissions.contains("android.permission.FAKE_PACKAGE_SIGNATURE")
&& p.applicationInfo.targetSdkVersion > Build.VERSION_CODES.LOLLIPOP_MR1
&& p.mAppMetaData != null)

So, maybe, one of the 'if' condition is never true.

Maybe because the FAKE_PACKAGE_SIGNATURE permission has been added for microg core in privapp-permissions-platform.xml (see this commit).

Annex:

MicroG PackageManagerService patch for Android O and UnifiedNlp patch for Android N.

NanoDroid core_services patch (GeneratePackageInfoHook.java)
[OnePlus 3 & 3T Cross Device Development] nazfalas:
You can change this by going to Havoc Settings -> Screen -> set Corner Content Padding to lowest value.

Can confirm, using Shuttle as an alternative right now.
[OnePlus 3 & 3T Cross Device Development] vikram.mohal:
Battery drain is faster than previous build. Now flashed Mady's xtended kernal reborn 6. Hope it will be good.
[OnePlus 3 & 3T Cross Device Development] vip57:
a clean flash is necessary in this build
[OnePlus 3 & 3T Cross Device Development] naveenk.g29:
Anybody How to downgrade to my stock OOS 5.0.8?
[OnePlus 3 & 3T Cross Device Development] TheMystic:
1. Install blu_spark twrp

2. Reboot to recovery

3. Wipe all partitions (internal storage wipe is not necessary) - system, data, dalvik, cache.

4. Install OOS from internal storage/ USB OTG/ ADB.
[OnePlus 3 & 3T Cross Device Development] vikram.mohal:
Use official twrp
[OnePlus 3 & 3T Cross Device Development] TheMystic:
My device failed to boot with official TWRP, despite several attempts and multiple methods. Blu_spark was successful the 1st attempt itself. This problem happened when trying to switch from Havoc to OOS.
[OnePlus 3 & 3T Cross Device Development] Kamkol:
So i found few bugs. (OP3T)

1. After reboot you have to lock and unlock device to get hardware home button working.

2.when clock on status bar set to appear on right side sometimes it shows both on left and right side.

3. front facing camera does not work (all green photos) with Oneplus camera included with ROM
[OnePlus 3 & 3T Cross Device Development] Bhavd Singh Khanpuri:
How to update already on havos pie ! Do i have wipe data n system again ???

How to update already on havos pie ! Do i have wipe data n system again ??? ????
[OnePlus 3 & 3T Cross Device Development] MarkusJu:
Must be a OP3T problem. None of them exist on the OP3.
[OnePlus 3 & 3T Cross Device Development] vip57:
i faced green selfie pictures also

but you can fix it

download oneplus camera version 2.0.0 and install it works flawlessly

---------- Post added at 10:55 PM ---------- Previous post was at 09:57 PM ----------

yes a clean flash is necessary on the latest build

so when installing

wipe system and data and cache

( don't wipe internal storage)

and install it
[OnePlus 3 & 3T Cross Device Development] CopyRight90:
Hi, I was having the same issue with low volume on the ear speaker and after modifying that it works fine now. My question is why not everyone is complaining about that? Why only some of us need to modify that? I understand that not everyone is having this issue, why the behavior is different?

Thanks man,
[OnePlus 3 & 3T Cross Device Development] vikram.mohal:
Strange. I used official with no problem.
[OnePlus 3 & 3T Cross Device Development] KUPOinyourWINDOW:
After a few days of letting it settle, the battery life of this rom is drastically worse for me (I'm guessing because of the new kernal?)

Anyone else finding this?
[OnePlus 3 & 3T Cross Device Development] ps_minky16:
Unmount system in twrp before doing anything related to oos.
[OnePlus 3 & 3T Cross Device Development] ReekyMarko:
I have nothing to add to this conversation wise, but it's kernel, not kernal!
[OnePlus 3 & 3T Cross Device Development] KUPOinyourWINDOW:
OH GOD, ahahaha thanks man, my main desktop OS is Linux so I see the word a lot. No idea why I didn't catch that.
[OnePlus 3 & 3T Cross Device Development] deepak3048:
Whem i tap on batyery icon in qs ui stopped any one have same issue in 11 build
[OnePlus 3 & 3T Cross Device Development] Bearthquake:
Stop asking for updates
[OnePlus 3 & 3T Cross Device Development] SlyUK:
Keep the faith would be more accurate.
[OnePlus 3 & 3T Cross Device Development] mk_1996:
Yeah but they're developers,not god?
[OnePlus 3 & 3T Cross Device Development] ZeNiXxX:
To stop that crying here:

We are still active and working every second we have on that rom. If you want we can release an update in 20 min.

But don't spam that thread and our group with bug report or feature request or something else. I'm also running the release build and it's stable enough for daily usage. So what's your problem with the current build ????!!

When our build is done and we thinks it's good we will release it.

People are crying here while sitting at home and dying because it's to boring. We work 8 hours a day, we have family, we are normal people with ( sometimes) health issues and we have to work on that rom every second ?

Cmon really ... Our team has two main Devs and we make better work then lots of other Devs and rom while there are much more.

So sry that it takes so long. But we are normal People. If u want anything new .. flash other ROMs. Op3 has thousands ROMs.

After said this. Keep calm and let us continue our work. And don't stress us with that comments here.

Thx

EDIT: I'm reading all and every message here. So some people complain that we are bad Devs that we don't react and arent active. But image u read everyday the same bug reports and the same questions. And that for month every time the same. And ask yourself. Would u still answer every question ?
[OnePlus 3 & 3T Cross Device Development] filip98r:
Is there a way to bring back default UI corners,instead of rounded ones?
[OnePlus 3 & 3T Cross Device Development] ZeNiXxX:
We will provide a zip for that. Otherwise enter our telegram group and ask for it. There should be a flashbale zip for that
[OnePlus 3 & 3T Cross Device Development] filip98r:
Thank you,great rom!
[OnePlus 3 & 3T Cross Device Development] mk_1996:
This explanation was much needed for some ppl. Thanks man.
[OnePlus 3 & 3T Cross Device Development] SlyUK:
The morale of the story is, just because there is silence doesn't mean tragedy is unfolding. Sometimes silence is golden and peaceful :)

Edit:

Patience is a virtue.
[OnePlus 3 & 3T Cross Device Development] SlyUK:
Sorry i'm religious, I keep the faith with everything including rom development where applicable :)
[OnePlus 3 & 3T Cross Device Development] sam 4x:
The ROM has Spectrum and a default battery manager under battery settings. Both have different profiles for battery preservations. And both are running at the same time, won't that cause any overriding with each other. Can that be a contributing factor for a mediocre battery backup ?

What set up are you guys running ?

Can someone please enlighten me ?
[OnePlus 3 & 3T Cross Device Development] uudruid74:
It shouldn't be. If the Dev was in here replying to all tjid trash, he'd NEVER get anything done. That's why I try to answer as much as I can.

---------- Post added at 02:30 PM ---------- Previous post was at 02:24 PM ----------

I believe they control different things in different ways. The battery is the primary power source, not a "backup", and I've not had any battery issues at all. It's been much better than OOS. I'm not sure what ROM you are comparing to (don't tell us), but most battery problems are your apps, nothing else.
[OnePlus 3 & 3T Cross Device Development] sam 4x:
Thank you for responding but maybe you didn't understand my question well. On the contrary, I'm aware that the battery is the 'primary power source' and not a 'backup' but being an alternate source it's the only means of backup. Secondly, I didn't mention any battery 'backup' issues nor am I comparing it to any ROM. Thirdly, when I say 'mediocre' it refers to 4-4.5hrs of SoT which compared to OOS (as you mentioned) is a marginal increase for me.

Again, I'm not raising any complaints against the ROM, my experience has been excellent with Havoc. I'm searching an answer for my logical confusion.

Peace !
[OnePlus 3 & 3T Cross Device Development] yeahitsmeak:
ShareIt app ain't working ... Don't know why.. Cleared data and cache but doesn't work. Help.
[OnePlus 3 & 3T Cross Device Development] SlyUK:
[MENTION=5328643]sam 4x[/MENTION] I like your banner "Wreaking HaVOC on the Flagship Killer titled OnePlus 3" :)
[OnePlus 3 & 3T Cross Device Development] sam 4x:
Have you tried using Airdroid ? Its much easier to set up and use for file transfers between multiple devices with fast transfer speeds.
[OnePlus 3 & 3T Cross Device Development] uudruid74:
Means of "backup"? Backup means an alternative to the primary. There is no backup on a phone.

Better than stock is mediocre to you? And it's STILL your apps. Here
[OnePlus 3 & 3T Cross Device Development] uudruid74:
I use FX File Manager. WiFi direct between devices and a web app for sharing with desktops that basically looks and feels like a desktop file manager. Just tap a QS tile to turn on.

---------- Post added at 04:48 AM ---------- Previous post was at 04:47 AM ----------

Stop clearing caches and post a log

---------- Post added at 04:52 AM ---------- Previous post was at 04:48 AM ----------
[OnePlus 3 & 3T Cross Device Development] sam 4x:
Definitions of terminologies can be universal but our interpretations differ. Your responses are appreciated but it still doesn't answer my 'logical confusion'.

To make it simple, is this like a car that needs only one driver at a time for its maneuverability or like an airplane which needs 2 pilots for the same job ?

Thanks you.

Peace !
[OnePlus 3 & 3T Cross Device Development] milomak:
i'm running twrp 3.2.3

i created an update.zip file using tibu size of 1.18GB

however when i try to install, it seems to install the packages and comes to a part where it says it will reboot in 5 seconds. however it seems to get stuck here and i don't any options such as reboot at the bottom. any ideas what could be the issue?
[OnePlus 3 & 3T Cross Device Development] Bhavd Singh Khanpuri:
update issues

Will that erase my issues and sings I've installed in the phone memory or only the cache n other files will be erased, n do i have to install firmware and gapps again while installing this.... I use to do dirty flag when i was using oxygen os to update , can't we do the same here as the rom I'm running is already havoc os ? Noob don't mind my questions, just curious to know. Been using custom roms since Google g1 - and moto g 1 . But still want to know how is it worth the custom roms n updating them

Thanks for your quick reply..
[OnePlus 3 & 3T Cross Device Development] hawki:
I'm having issues as well with 2.1. Clean flashed. Pico gapps, even tried Aroma Gapps - no keyboard shows up (others have had this issue), Home button doesnt respond. can't get into settings. Thoughts or suggestions?
[OnePlus 3 & 3T Cross Device Development] milomak:
When I reboot it keeps on going back to vibrate after a short while

Clean wipe
[OnePlus 3 & 3T Cross Device Development] vip57:
i clean flashed the rom with nano GApps and everything works fine

are. you sure you flashed the desired gapps package for the rom ( android 9 Arm64) package
[OnePlus 3 & 3T Cross Device Development] straike:
Hello,

Thanks for this perfect ROM ! Absolutely no bugs and really fast. Just one question, I don't find a shortcut in the tiles on the top to toggle DATA between SIM1 and SIM2? This button was available on last stock beta FW :)
[OnePlus 3 & 3T Cross Device Development] hd21337:
What kernel can you currently recommend for a good battery performance?
[OnePlus 3 & 3T Cross Device Development] AnnoyingZlatan:
I would recommend Caesium.
[OnePlus 3 & 3T Cross Device Development] AkkerDK:
Same problem here, clean flashed, AROMA Gapps (Arm64, 9) ... No keyboard and no mobile connection = No use.
[OnePlus 3 & 3T Cross Device Development] TheMystic:
I will recommend a power bank. No matter what kernel you use, or what tweaks you do, you will gain very little by way of SOT. so, if you are a user who currently charges the phone twice a day, you will still be needing two charges a day, no matter what you do.

So get yourself a power bank and let go of battery annoyances.
[OnePlus 3 & 3T Cross Device Development] lordcheeto03:
Anyone having a weird encryption issue?

I'm not encrypted, didn't try to encrypt on accident, so where this is coming from blows my mind. I've been using the latest Havoc but decided to go back to a saved restore of RR nougat. After the restore completed I rebooted and it went to the "encryption unsuccessful, perform a factory reset" screen. Now, my computer died a few weeks back so I just knew I was screwed. I booted straight into recovery, all my files are there, and nothing about encryption in recovery.

I wiped and did a clean flash of RR and got the same problem. Since I could still access my files via recovery I restored back to the Havoc backup I just made, and it started up without saying anything about encryption, just when I went to unlock my screen it said "phone is starting" or something and heat looped back to the lock screen.

I tried a clean flash of Havoc and it started right up, allowed me to set up everything, etc. It works just like it's supposed to. Settings->Security says phone is not encrypted, I can download from the play store, access all my data, etc.

So I try a clean flash of RR again, but just like before it says encryption unsuccessful.

I'm asking if, perhaps Havoc has anything to do with this and if there is anything short of booting into fastboot and using fastboot format userdata to clear the issue up..

I've tried using RedWolf TWRP v3, and TWRP-x..
[OnePlus 3 & 3T Cross Device Development] TheMystic:
So your phone is now un-encrypted and you want to encrypt it, isn't it?

If you are unable to encrypt the device from within the system, backup all your stuff (you can take a nandroid backup, but remember though that user files on internal storage must be backed up separately) and clean flash OOS. This will encrypt your device. If for any reason official TWRP fails to successfully flash OOS, then use blu_spark TWRP. Once you boot with OOS for the first time, you will see that the device has been encrypted.

Now flash TWRP recovery again (you can use official this time), reboot to recovery, wipe all partitions and clean flash havoc (or you can restore your nandroid backup).
[OnePlus 3 & 3T Cross Device Development] lordcheeto03:
No no I don't want to encrypt it. Whatever happened, that was not my goal. I'm not even certain this event is related to Havoc, I just asked in this thread because everything else has been the same, the only thing changing has been the version of my ROM. I've been using Havoc for about a month or so, clean flashing and restoring my apps after each update and I haven't added any new apps in just about as long. I haven't been encrypted for ages so that's why it blew my mind being told encryption was unsuccessful. I didn't do anything to initiate encryption in the first place.

And whatever happened, I'm not exactly encrypted because it says not encrypted in Havoc settings->security, I can browse my files both in Havoc and recovery. It's just when trying to flash RR nougat does it tell me that encryption was unsuccessful. So I guess I'm stuck somewhere between encrypted and not encrypted.
[OnePlus 3 & 3T Cross Device Development] programmeraditya:
On Havoc OS 2.0, the Fingerprint sensor is too much slow. It takes a whopping 1 second to fully unlock the device. I updated the Dec 30/31 (don't remember exactly) update and after that the Fingerprint sensor has become really slow. This is very irritating.
[OnePlus 3 & 3T Cross Device Development] TheMystic:
My guess would be the RR ROM is trying to encrypt your device, but is unsuccessful. That error isn't new, so I would like to think there are solutions available. With this 11012019 build, I formatted my data partition which meant my device encryption was lost. I clean flashed Havoc and it ran fine without any errors. But because I wanted my phone encrypted, I did what I suggested to you. Now my device is encrypted and Havoc runs fine. So I don't think Havoc is doing anything here.

If I may ask:

1. Why do you leave your device un-encrypted? My device has always been encrypted and I have tried different (popular) custom ROMs.

2. Why do you clean flash with each ROM update? It is both unnecessary and a waste of time.

---------- Post added at 19:03 ---------- Previous post was at 18:52 ----------

Since when did one second become ‘whopping’ long? :)

1. Delete all your fingerprints, reboot and add them again.

2. If you have assigned the home button with additional functions, like long press (e.g. Google Assistant) or anything like that, disable that and see if that helps.
[OnePlus 3 & 3T Cross Device Development] lordcheeto03:
It is just odd that this happened. I've been able to jump back to RR with no issues previous to this version of Havoc, and I really honestly think I've reverted for some reason on the 20190111 version as well with no problems; until this morning when I got that error message out of nowhere.

As for why I leave it decrypted: no real reason. I want to say I did something or flashed a ROM early on that required the phone to be decrypted and I just never encrypted again.. plus, there was the problems with encryption when Pie ROMs were released I believe.

As for why I clean flash: just to make absolutely sure nothing lingers between updates that shouldn't. So I can know without a doubt that any issues I may encounter aren't from a dirty flash.
[OnePlus 3 & 3T Cross Device Development] TheMystic:
It could well be a TWRP thing. Did you change your recovery recently? Try with blu_spark if you are getting errors with official.

Again, why do you keep going back to Nougat? Any specific reasons? Havoc_Pie runs great and is just as customizable as RR.

As with encryption, good and well built ROMs should support encryption, and you are better off with an encrypted device.

Unless the ROM build specifically requires a clean flash (like the 11092019 Havoc build), I don't think a clean flash has any benefits. Of course, Dalvik & Cache partitions must be wiped when dirty flashing.
[OnePlus 3 & 3T Cross Device Development] lordcheeto03:
Haven't changed recovery in a while, been using TWRP xtended v2 for a good while, then after this happened I flashed Red Wolf just to see if it would take care of the "encryption" but no dice. As for why I go back to nougat: I use the Sultanized RR because it gives me the absolute best battery life out of anything I've tried.. no other ROM/kernel/settings I've tried comes close to the 6 to 7 hour screen on time I get with that ROM. Havoc was getting close there a few updates back, but the last couple updates I'm lucky to get 4 hours SOT.. under the same usage conditions.
[OnePlus 3 & 3T Cross Device Development] Kundan Wadkar:
I had to switch back to the earlier version since i was facing lots of issues even with clean flash , i stopped receiving notifications of apps also the gaming mode tile was not working for some reason and the background recent apps used to get cleared as soon as i exit the app may be aggressive ram management thing. Also saw many others are facing issues with this build hope so we receive a stable build soon,waiting for the next build, till then will stick to the earlier version December build.

Waiting for the issues to get solved and for a stable build.