[ROM] [10.0] FireHound v5.0 [2019/01/26] [OFFICIAL]

[PrathameshMS]

FireHound is a Custom ROM developed focusing on Stability carrying many features hand in hand. We strive a lot in the back end to provide our users with all the necessary components a daily driver ROM should include.​

Ashes:

Status Bar

• Status Bar Icons
• Battery Percentage
• Network Traffic Indicator
• Battery Bar
• Battery Bar Location
• Battery Bar Style
• Charging Animation
• Battery Bar Color
• Battery Bar Thickness
• Slide for Brightness Control
• Quick Pulldown
• Smart Pulldown
• Show seconds
• Bluetooth battery status
• Notification Ticker
• Battery Icon Styles
• Clock and Date customizations

Quick Settings

• Heads Up customizations
• DND
• QS Tiles title
• Qs alpha
• QS tiles custom numbers
• Haptic feedback on qs tiles
• Disable Immersive Messages
• Force Expanded Notifications
• Notification Access
• Custom Small QS tiles
• Custom rows,portrait,landscape tiles
• Disble QS on secure lockscreen
• Notifications Filter
• Quick Settings Headers
• QS Scroller
• QS transparency
• QS Footer Warning toggle

Buttons

• Navigation Bar Enable/Disable
• Backlight Control
• Navigation Bar Layout Control
• Power button press twice for Camera
• Power Button End Call
• Home Button Customizations
• Menu Button Customizations
• Back Button Customizations
• Volume Button Customizations
• Keyboard Cursor Control
• Playback Control

Display

• Rounded corners
• Full screen apps
• Toast Icon Switch
• Double tap to wake/sleep
• Wake on Plug
• LCD Custom Density
• Daydream
• Font Size Control

Lights

• Battery Lights Customizations
• Notification Lights Customizations

Sounds

• Notification Tones
• Increasing Ring Volume
• Launch Music App on Headset connected
• Other Sounds Customizations
• Charging Sounds
• Enable/Disable screenshot sound
• Live Volume Steps
• Force Expanded Volume panel
• Camera Shutter Sound Enable/Disable

Gestures

• Three Finger Swipe Screenshot

Lock Screen

• Quick Unlock
• Double tap to sleep on lockscreen
• Smart Lock
• Album art filter
• Fingerprint vibrations
• Show lockscreen date/clock toggle
• Signature spoofing
• Emergency Button Switch
• Battery Info on lockscreen
• Hide power menu on lockscreen
• Live Lock Screen
• Lock Screen Shortcuts
• Music Visualizer
• Show Weather
• Ambient Music Ticker

Animations

• System Animations
• Listview animations
• Toast animations style
• Screen Off animations
• XUI-mod toast animations

Miscellaneous

• App Ops
• Media scanner on boot

Downloads
FireHound

How to flash:
Download the ROM and Gapps
Boot into recovery mode [TWRP]
Wipe System/Data/Dalvik Cache/Cache
Select both the ROM and Gapps zip files
Flash
Reboot!
​

Links:
Crowdin
Telegram Channel

We also encourage users to report bugs and issues at our G+ Community with proper logs.
We also welcome a “x” feature request from users and if we really feel it to be useful, we will push it in.

Sources:
Kernel
ROM

Screenshots​

Thank You!​

XDA:DevDB Information
FireHound, ROM for the Xiaomi Mi A3

Contributors
PrathameshMS
ROM OS Version: Android 10
Based On: AOSP

Version Information
Status: Stable
Current Stable Version: 5.0
Stable Release Date: 2020-01-26

Created 2020-01-26
Last Updated 2020-01-26

 

[sushil11]

Finally released, congratulations buddy.?

 

[garylawwd]

Bad download link?

Edit: can download on PC but not in the mobile app. Copying the text of the op and copying the gdrive link also works but not directly clicking on the link in the op.
Could just be me also.

 

[nofx161]

nice rom with nice features, but for me notification sound is chittery, disturbed,...

 

[Meraj018]

Looks great:good:

 

[suschmania]

"Wipe System/Data/Dalvik Cache/Cache
Select both the ROM and Gapps zip files
Flash
Reboot!"

no twrp is included in the installation process, so you will loose twrp recovery after reboot. In addition, opengapps can't be installed in one hand with the rom as it doesn't recognize the rom.
Previous rom was V10.3.14.0.PFQEUXM (directly flashed via fastboot method and one time initial setup)

 

[colonho]

Wow, sounds good! waiting a stable (without bugs) to test! Thanks for developing!!!

 

[chineel]

So Finally Firehound Has Hit the dack. Nice ROM loved it on the first test.
Audio is shattering in Media playing rest is fine till now.
I will check it by installing another kernel for this.

 

[Technical]

So Finally Firehound Has Hit the dack. Nice ROM loved it on the first test.
Audio is shattering in Media playing rest is fine till now.
I will check it by installing another kernel for this.

I'm using it too. How is your fingerprint (FOD)? Mine is not very accurate...
I didn't notice audio setting (maybe due to Viper?).

 

[chineel]

I'm using it too. How is your fingerprint (FOD)? Mine is not very accurate...
I didn't notice audio setting (maybe due to Viper?).

Whatever I use I always make it clear, always. Fod works ok media audio never plays on Bluetooth headset it always shattered and from speaker only.
Even tested with another kernel Fenix same.

 

[garylawwd]

Whatever I use I always make it clear, always. Fod works ok media audio never plays on Bluetooth headset it always shattered and from speaker only.
Even tested with another kernel Fenix same.

I use Bluetooth in my car everyday since installing the rom with no issue at all that's strange

 

[chineel]

I use Bluetooth in my car everyday since installing the rom with no issue at all that's strange

Are you on firmware with january update? or earlier?

 

[garylawwd]

Are you on firmware with january update? or earlier?

Yes January stock rom. Could be Bluetooth version issue. The device I connected to was Bluetooth 4.0.
Anyway you could check with a Bluetooth 4.0 device/speaker?
I could be completely wrong, just eliminating some possible issues

 

[suschmania]

After nearly 2 days i finally have a working fingerprint with a custom rom. Thanks to the developer.
But, why is the install instruction that "simple" - there are more steps to do bring this rom to live.

I am on stock EEA rom and want to change to this rom. So I installed TWRP (fastboot flash boot RECOVERYNAME.img).
After reboot into recovery i am in boot slot a.
I cleaned the partitions as indicated (wipe system / data / dalvic+cache).
i installed the rom.
Next step is not possible, gapps (opengapps open_gapps-arm64-10.0-pico-20200127.zip) tells me it's not the correct version and i need version 16.1 SDK 28 (?) to proceed (doesn't matter if i was putting gapps in a queue together with the rom as indicated or as a single install afterwards). In addition, i have to flash now the twrp installer otherwise i'm loosing the recovery).
I rebooted the phone: FASTBOOT mode or i see the bootlogo for nearly 1 hour and nothing happens.
Nothing is written about the no_fde patch or what kind of stock rom is needed, what to install in which partition etc...

Install instruction 2.0: after installation of the rom, you must reboot the phone into recovery again (that changes the slot from a to b or vice versa) and there install the opengapps and the no_fde patch. Otherwise, your reboot will end in a bootloop or simple in fastboot mode.

Is the instruction just a copy / paste from the original thread of the rom developers?

 

[Technical]

Next step is not possible, gapps (opengapps open_gapps-arm64-10.0-pico-20200127.zip) tells me it's not the correct version and i need version 16.1 SDK 28 (?) to proceed (doesn't matter if i was putting gapps in a queue together with the rom as indicated or as a single install afterwards).

You need to reboot to recovery after flashing the ROM, otherwise you'll be in the wrong slot.

 

[Technical]

Is there any way to encrypt the phone after installing this ROM? (and have flashed the No_patch_fde.zip)

 

[Sapper Morton]

Is there any way to encrypt the phone after installing this ROM? (and have flashed the No_patch_fde.zip)

The patch_no_fde much for contrary belief, won't remove FBE encryption from Mi A3, it rather relies on modifying metadata encryption and disabling AVB, the latter being the most important for us, that disables boot verification, thus allowing custom software booting.
For those who want to remove force encryption, use something like Zackptg5's solution, and of course, format data before system boot. Dm-Verity, Forced Encryption, and Disc Quota Disabler.

Edit: Indeed the patch removes forceencrypt, however it's not mandatory, and you will still need to format data if you want to remove FBE encryption; to encrypt again, you must restore fstab.qcom default strings.

 

[Technical]

The patch_no_fde much for contrary belief, won't remove FBE encryption from Mi A3, it rather relies on modifying metadata encryption and disabling AVB, the latter being the most important for us, that disables boot verification, thus allowing custom software booting.[/URL].

But I'm facing two issues:
1. While TWRP loads it says FBE data can't be decripted. Is it an issue from this TWRP version?
2. I can't encrypt the phone. The process starts but the phone reboots and enter the system again, unencrypted.

 

[suschmania]

The camera app is working great with automatic and Pro mode. Changing to other presets like hdr, beach etc. results in a very blurry or grainy image. I am fine with the pro mode, but want to mention it. Any of you with the same problem?

 

[Technical]

The patch_no_fde much for contrary belief, won't remove FBE encryption from Mi A3, it rather relies on modifying metadata encryption and disabling AVB, the latter being the most important for us, that disables boot verification, thus allowing custom software booting.
For those who want to remove force encryption, use something like Zackptg5's solution, Dm-Verity, Forced Encryption, and Disc Quota Disabler.

As suggested elsewhere, I tried not flashing patch_no_fde. Then I cannot boot into FireHound system. I tried just wiping data twice and it does not boot. It bootloops to TWRP.
So (for me), if I do not flash patch_no_fde, no boot at all.

And, if I flash patch_no_fde and boot FireHound, I cannot encrypt the phone anymore..., as the encryption process reboots the phone and do nothing.

Are you sure you're booting the ROM and the phone is encrypted after flashing patch_no_fde?
If so, would you be so kind to post the step-by-step? Thanks.