yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] Y2Ne1:
OMFG you and me on the same boat bro :crying: i still don't understand why it shows for rom tweaks but not inside the rom :silly:

I'm on the same set up as you btw if you want those features use this rom https://androidfilehost.com/?fid=6006931924117881494 EVERYTHING WORKS on my end ..

im on Pixeldust atm using button mapper to fix my button problems hope this helps ....

Keep in touch im looking for same feature on pie rom :P so many says they do but dont lol like wtf

... edit..... btw try this https://xdaforums.com/project-trebl...ment/rom-msm-xtended-xp7-release-v15-t3942924 amazing rom with tons of features but missing Button Customization options .... i asked the same in thread NO LUCK btw stay with speedy =)
[Treble-Enabled Device Development A/AB ROMS] Hutch MD:
I am actually running Current Guido's build of LiquidRemix 6-24, and the Button Remapping features exist, but it doesn't have Slim-Recents.

And even more importantly, it doesn't have Double-tap to Wake!

But anyways, I really like Havoc, but I guess what's making me sad is that not all the features in the 'features-list' exist in the actual GSI build.

Are there plans to bring Button Remapping back in the Havoc GSI?
[Treble-Enabled Device Development A/AB ROMS] Y2Ne1:
omg i didnt even know 6-24 was OUT :P well looks like its back to Liquid :highfive: thanks for the info mate :good:
[Treble-Enabled Device Development A/AB ROMS] mhhashemi02@gmail.com:
Hi one question, I have a kernel image file I want to know which partition I should flash in recovery?
[Treble-Enabled Device Development A/AB ROMS] dwapking:
I guess you mean boot image. If so, simply flash into the Boot partition.
[Treble-Enabled Device Development A/AB ROMS] mhhashemi02@gmail.com:
Does the kernel image on boot partition ??
[Treble-Enabled Device Development A/AB ROMS] extranoise:
Hi,

i tried to run this rom on my xiaomi mi9. but I have the problem that the fingerprint doesent work from the ambient display (AOD). it showes always that the fingerprint is not accepted. but when i press once the powerbutton and try to unlook it from the looking screen it works always by the first try. when i go back to the ambient display it showes fingerbrint unrecognized again.
[Treble-Enabled Device Development A/AB ROMS] vince31fr:
[MENTION=6316701]dwapking[/MENTION] [MENTION=4482311]Y2Ne1[/MENTION]

Guys, button customization options where not activated. I did not see it because I don't have navbar hardware buttons on my device, so I did not miss them...

They will be activated for everyone in the next build (so even people with devices that don't have hardware buttons will see these options, useless for them), and thanks for pointing out that to me.

In the meantime, if you need these options, put the file View attachment 4785604 into the /vendor/overlay folder and reboot. You can wee what options that activates in the screenshots.

As an explanation to everyone of such issues, here are some more details.

The Havoc ROM can be seen as an addition of many, many features on top of AOSP. Some of them are hidden to the user, working in the background and providing improvements over the AOSP base. They may increase performance, reduce power consumption, etc.

Some other options, visible to the users, can be activated or not. Why ? Because Havoc is not devoted to one device, but to all devices. So hardware key customizations for instance must be disabled for devices that don't have hardware keys.

The problem in building a GSI out of Havoc, whose task I do alone even if I can get some help from the Havoc team, is that I cannot test all the features; and even more, for some features like hardware keys, I don't even think about that because my device doesn't have them. The other problems is that I must activate all options which may not be harmless for some devices, which may lead to some difficult choices. For the few options that I don't want to activate for everyone, I put overlays in the OP.

So, please, don't complain, and don't tell why you don't understand this or that: ask questions, wait for my answer (and ping me if I don't answer, it's more and more difficult for me to see all the messages and reply to every question), and let's see together how we can increase the quality of that GSI.

It may be also understood to everyone that it is not possible to solve all the problems, to make everything work for everyone... Even on device-specific devices it is not so easy and there are always some problems for some users, so you can imagine for a GSI which is run on hundred of different devices.
[Treble-Enabled Device Development A/AB ROMS] Y2Ne1:
:highfive: You sir are epic .... I just wanna thank you for taking your time out to answer on why and pointing out not all phones are created equal :silly: needless to say This has once again became my daily driver :P

Ps.... will report back later ..... im sure it will work .... i used button mapper which solved that problem AGAIN thank you for the Quick answer and solution:victory:
[Treble-Enabled Device Development A/AB ROMS] vince31fr:
You're welcome. And it's pleasant for me to easily solve a few problems, while there are tons of other ones for which I cannot do a lot ;)
[Treble-Enabled Device Development A/AB ROMS] Y2Ne1:
lol amen brother amen lol if you need a test for the device shoot me a pm ;) whats the wrost thing i can do never brick it :p

Edited ... btw I tested hkey on 2 other roms just now :P i have 3 axon 7 phone ( smh ) but congrats @ vince31fr (will get you a beer soon buddy ) you're about to make at least 30 people happy

We now have working Button Customization options on all roms which doesn't show it .... put the file treble-overlay-hkey.apk into the /vendor/overlay folder and reboot
[Treble-Enabled Device Development A/AB ROMS] vince31fr:
Happy to have improved some other GSIs :cool:

Btw all the things I put in the OP can work in other GSIs too...
[Treble-Enabled Device Development A/AB ROMS] Y2Ne1:
You know whats funny you and my dad have the same name ;)

here's the beer i owe you buddy ...

Transaction ID 8WW48532LT275373K Paypal :good:
[Treble-Enabled Device Development A/AB ROMS] piyushmehta24:
Bluetooth not working on Galaxy Note 9 Crownlte, any solution?

I'm unable to switch on/off bluetooth.
[Treble-Enabled Device Development A/AB ROMS] Mr.R™:
Set kernel to permissive
[Treble-Enabled Device Development A/AB ROMS] piyushmehta24:
Thanks! It works like charm now!
[Treble-Enabled Device Development A/AB ROMS] ls117:
OP should be updated to tell people how to resize their system partitions, to install gapps. Not to sound like an ***, but if you're gonna give people instructions, they should be

clear and concise

. Saying "you may need to resizr your system partition in TWRP", leaves people needing to ask where and how. People asked before me so I'm good, just pointing that out.
[Treble-Enabled Device Development A/AB ROMS] Hutch MD:
You are the best! Thank you so much for this explanation!

I apologize if it sounded like I was complaining earlier, it was meant to be a genuine question. I really do appreciate your work on this ROM.

I'll try to implement your apk when I get home today! You're amazing!
[Treble-Enabled Device Development A/AB ROMS] ls117:
Man. This is another thing the OP doesn't clearly clarify. There's factory resetting in TWRP, then there's the factory reset in the actual rom, which I've probably never used and forgot even existed. Without reading this comment I would've just skipped that step, but apparently it's necessary so I'll start over. I'm doing all this JUST to make sure V4A works. But the OP needs to say "Boot the OS, go to settings/system/factory reset". I'm thinking I gotta go back to TWRP to reset, hella confusing.
[Treble-Enabled Device Development A/AB ROMS] vince31fr:
Really ?

Well, is it a good or bad thing, I don't know ;)

Thanks for the beer, I'll savour it soon.

But, you don't owe me anything, no one owe me nothing. I do that job for fun first, and will continue as long as I find that fun.. I appreciate beer though ;) Well my discourse is a bit incoherent, I know.
[Treble-Enabled Device Development A/AB ROMS] vince31fr:
Thanks to the solution given by [MENTION=1139083]Mr.R™[/MENTION] we know that it was a sepolicy problem.

We also know that the last sepolicy rules I added lastly allowed a Samsung xxx9 to boot, which was not the case in previous builds.

But, nothing can be gained to improve the gsi!

So if you have some free time, what could be great, would be to boot again in enforcing mode, try to activate Bluetooth, and send me a Logcat. I could then add sepolicy rules which could permit to use Samsung xxx9 in enforcing mode, which would be better...
[Treble-Enabled Device Development A/AB ROMS] Mr.R™:
If pi doesn't first I can do that for you in a couple of hours
[Treble-Enabled Device Development A/AB ROMS] vince31fr:
No problem. I know it can be frustrating sometimes when things don't work as expected, as they should, or as promised ;)

Sometimes there are good reasons, sometimes no one knows and have time to investigate in depth!
[Treble-Enabled Device Development A/AB ROMS] vince31fr:
There's nothing urgent you know. But maybe for these series of devices we are not so far from a clean boot in enforcing mode, so if we could get there it would be a progress. Thanks by advance to anyone willing to contribute ;)
[Treble-Enabled Device Development A/AB ROMS] Hutch MD:
I am a fool who has no experience with /vendor/overlay business

I am however a bit embarrassed to say.... That I am doing this incorrectly, and I still don't see the button options... (I'm Sorry!)

Am I understanding this incorrectly? In TWRP File Manager, I went to the /vendor folder and didn't see an overlay folder, so I created an overlay folder, and put the apk inside it.

Did I do that wrong....? What would be the proper way to do this?

Thank you for helping me out!

EDIT: I ended up installing Magisk, then a root explorer to put your apk into the overlay folder, it works now! Thank you so much!
[Treble-Enabled Device Development A/AB ROMS] noslen69:
Great rom in my Huawei P10 Lite . The only problem I detected so far is that I can not pair my huawei watch GT.

Someone have this problem. Is there anything I can do? Thanks for you work.
[Treble-Enabled Device Development A/AB ROMS] mhhashemi02@gmail.com:
Hello my dear, I have a CUSTOM kernel which file is an image. In the recovery section, which partition should flash ?
[Treble-Enabled Device Development A/AB ROMS] vince31fr:
My dear ? Wow, I didn't we had a such personal relationship :)

In twrp: boot partition
[Treble-Enabled Device Development A/AB ROMS] vince31fr:
Ok great, you found yourself the solution... Every location in the file system outside the home folder (usually /sdcard) require root permission..
[Treble-Enabled Device Development A/AB ROMS] vince31fr:
Does Bluetooth works for other devices?
[Treble-Enabled Device Development A/AB ROMS] mhhashemi02@gmail.com:
:D Sorry I want to write a mistake, thanks for the guidance
[Treble-Enabled Device Development A/AB ROMS] noslen69:
Yes it work. Whit MI Airdots for example it works, but with smartband MI Band don't work too. Thanks
[Treble-Enabled Device Development A/AB ROMS] vince31fr:
You should take a logcat, just the moment when you try to connect. I can take look, and if I have no quick solution you could open an issue at phhusson github: he is the specialist of hardware problems. But a logcat is required for such a problem.
[Treble-Enabled Device Development A/AB ROMS] vince31fr:
Yeah I know your english is still a work in progress, gently kidding ;)

(and my english is far from being perfect too, btw)
[Treble-Enabled Device Development A/AB ROMS] ls117:
So this is weird. Earlier, before I did a factory reset, I had already rooted and installed v4a. It processed ONLY on speakers, for some strange reason it absolutely refuses to process on headset. Thats with and without ainur/aml flashed. After following the instructions in the OP all the way, rooting with magisk 19.3, the v4a driver won't even install. It keeps saying I need to install the driver, installs and reboots, and still needs to be installed. Getting v4a to work is crazy frustrating. I've been at it for 4 days now and 4 different roms. This is all on axon7.
[Treble-Enabled Device Development A/AB ROMS] ls117:
Most devs in general are rude/harsh, and besides the exceptions for lazy people who don't search before asking, most of that rudeness is uncalled for. Everything you said has nothing to do with the OP simply clarifying two things. Generally speaking, bad instructions are not only common on the forum and elsewhere, they're also the cause of a lot of problems. Trying to unlock my phone's bootloader a few years ago was a tour of bad instructions all over. Everywhere I looked, xda, reddit, google, it seemed like there was a different, poorly written method. Having to search for answers because of bad instructions is not at all constructive, its a waste of time. If it can be clarified in the OP, to help people avoid doing that and making time wasting mistakes, its better for everyone.
[Treble-Enabled Device Development A/AB ROMS] noslen69:
Can you teach me how to take a logcat. Excuse me but i am new in this things. Thanks from Portugal.
[Treble-Enabled Device Development A/AB ROMS] vince31fr:
There are some instructions in the bottom of OP, several methods. And good memories from portugal, been there once few years ago :)
[Treble-Enabled Device Development A/AB ROMS] vince31fr:
It seems that you did not understand what I wrote.

To be clear and concise:

- if I knew the clear and concise instructions, I would have perhaps written them

- I maintain "you may need to resize" : some people need, some not. If you try without and get an error, you have the keyword to find a solution. No error, no problem. If you hesitate, ask to get some feedback. Even if some answers may lead to errors, participation, communication, help between users is a nice and good aspect.

- same for factory reset, I don't have the ultimate answer that will work for everyone, so I don't want to be more precise, it will always be erroneous for at least a few users.

People have to search, and from trials to errors, if they persevere, will find a solution (which I have not, for their particular device/twrp/kernel/vendor).
[Treble-Enabled Device Development A/AB ROMS] noslen69:
See please if you can help. Thanks.

https://xdaforums.com/attachment.php?attachmentid=4785980&stc=1&d=1562015462
[Treble-Enabled Device Development A/AB ROMS] Mr.R™:
Logcat attached

Also noticed you have a bt fix in the op, I haven't tried that as wasn't aware of it so it might just be that I need but I'm sure you'll be able to tell from the logs
[Treble-Enabled Device Development A/AB ROMS] Rashad79:
Hi [MENTION=7932843]vince31fr[/MENTION]

Refer to above issue, please find attached logcat and kernel logs taken when i tried to dismiss Magisk notification. please i need to know the root cause of this issue even it's related to vendor side, I need your help in this, please it's important to me.

Thanks in advance.
[Treble-Enabled Device Development A/AB ROMS] Hutch MD:
Prefacing this post with love:

I love this rom, and all the work that [MENTION=7932843]vince31fr[/MENTION] has put into this. He's an amazing developer that is one of the few that are interactive with the thread. (Some don't respond to posts, and only posts when there are major updates or new releases). Vince is great and talks to us!

A few questions:

Does anyone else here like to use Notification Ticker?

It doesn't seem to be working properly and ticks blank notification regardless of the animation style.

Does anyone like to use different fonts in the StatusBar Clock? I usually like to use Condensed Light, but it seems to be the same font.

Has anyone here successfully got the stock File-browser to work? I have been using MiXplorer in the meantime and it's fine.
[Treble-Enabled Device Development A/AB ROMS] ls117:
I heard you the first time, you're just being stubborn for no reason. All this stuff you're saying, all these explanations, they should be in the OP. Not on page 109. All this "find" stuff is unnecessary. Unless the OP has a character limit that forbids you from explaining "you may need to resize", all this back and forth over not clarifying two steps is ridiculous. There's no justification for not clarifying those posts. You typed a whole lot of nothing to explain why the OP doesn't say

5. Boot

System

and perform a factory reset

(Settings>System>Reset options>Erase all data). **Factory reset may not be required for all users**

6. (Optional) Reboot and flash GApps, Magisk, and maybe additional files (see below, GSI Specific Information). If you don't flash GApps with the MagicGapps Magisk module, you may have to resize your system partition in TWRP.

To resize system in TWRP, Wipe>Advanced Wipe>Select System>Repair or Change Filesystem>Resize File System.

How hard is that? Why are you so defensive? These are simple additions, if the explanation for not doing that is several times more lengthy than those additions, it makes the explanation sound silly. Again, all of that would've sounded better in the OP, not on page 109
[Treble-Enabled Device Development A/AB ROMS] vince31fr:
Well, I just realize that one important thing is missing in my instructions for Logcat Reader: all checkboxes in Settings / Logcat / Buffers must be checked, particulary Events to get selinux denials. I you have time and it don't bothers you too much, please send logs again.

From what I saw, a rule may be clearly missing for the S9 bluetooth problem (a bt related file cannot be open, certainly because of a denial event).

For the other problem, I'm not sure of anything and will perhaps have a better idea with a more complete logcat.
[Treble-Enabled Device Development A/AB ROMS] Rashad79:
I already sent you mate full log as you descried above. here it is attached again. but kindly check my issue description in my previous reply first before looking in the logs. Thanks
[Treble-Enabled Device Development A/AB ROMS] vince31fr:
Wow, now that we are the step of personal attacks (stubborn, ridiculous, sound silly), I prefer stopping before reaching the godwin point, so these will be my last words.

First, I think and maintain all what I said. Nothing more to add, even if you have a bad opinion of my way of seeing things. Not everyone should have the same opinion, after all.

Second, jumping back to your first post, you should understand that the way you write is simply unpleasant : OP should be update, things should be done like that in that way (which is better than yours, implicitly), using bold, italics, underline... This does not render people very cooperative, you know.

Sorry if things turn for you in such an INFURIATING way, as you wrote in another thread.

During a moment, I forgot one of the oldest adages of internet:

DO NOT FEED THE TROLL

.

This will be a lesson.
[Treble-Enabled Device Development A/AB ROMS] vince31fr:
Sorry, I included your message in the multi quote reply, but you were not concerned, there is everything in your logs. I'll take a look, but I have to stop now and will be traveling next day, so everyone will have to wait a bit. And as I always recall, I'm not sure that I will be able to find a solution ;)
[Treble-Enabled Device Development A/AB ROMS] Rashad79:
It's OK and no problem if you won't able to find a solution, I'm just need to know what is the root cause because i installed so many ROMs in my device and the most of them generating this issue, except one or two ROMs. that's why i want to know why it's happening in most of them :o Thanks for your support and help.
[Treble-Enabled Device Development A/AB ROMS] noslen69:
Thanks. Here is another logcat. When you have time take a look please. Thanks for you suport.

https://xdaforums.com/attachment.php?attachmentid=4786031&stc=1&d=1562024860
[Treble-Enabled Device Development A/AB ROMS] ls117:
Yeah whatever, stay sensitive.
[Treble-Enabled Device Development A/AB ROMS] jojofreddy:
Hey,

Only minor issues. Sometimes, apps start very slowly. The camera isn't very smooth, too. I'm using Speedy Vendor plus Baddar 1.1. then, the A2017x_LineageOS15.1_UniversalBootstack_v2_by_DrakenFX.zip — there's a Axon Trebleshoot Telegram group which really helped my with picking the right files.

I'm also using latest Magisk and CombiFix where you can at least swap buttons afaik. You could also try finding a Magisk Module that can remap your buttons to your likings.

Hope that helped x

---------- Post added at 08:10 AM ---------- Previous post was at 08:05 AM ----------

Well ? I used this link https://www.paypal.me/vhermann

That shows this page: PayPal https://imgur.com/a/y9KVxx4

---------- Post added at 08:19 AM ---------- Previous post was at 08:10 AM ----------

At last, you could have written an extensive guide as a comment or an own post for fixing known issues in a post and Vince could link it in the OP. That's usual here on xda, you get linked to a specific comment, sometimes to another thread, very often.

That's just how it is in such a community, where contribution is everything. Don't be a **** just help developing a better ROM by writing an extensive guide to issues you found yourself in.

Lastly, here in germany, we say: "Der Ton macht die Musik" which means "It's not what you say, but how you say it."

Cheers x
[Treble-Enabled Device Development A/AB ROMS] ls117:
I already did that. He decided to be sensitive and cry about simple additions to the OP. His first comment towards me mentioned the attitude most devs display on this site. Which is being a ****. I'm not being a **** if I'm pointing out how the op could be clearer. That saying of yours in Germany isn't unique to Germany either, all he had to say was "I'll make the OP clearer". Instead he decided to patronize me, as if I'm being slow. I already explained exactly why I feel the way I feel about half *** directions. Having to search for answers sometimes is a given, having the OP be clearer in general should be a necessity. And it doesn't really matter to me anymore because I'm using another rom. Enjoy yourselves.
[Treble-Enabled Device Development A/AB ROMS] Mr.R™:
My bad, I usually use terminal but decided to use an app for ease without checking it lol. Logcat with events captured attached.
[Treble-Enabled Device Development A/AB ROMS] Akhayev:
For s9/+ users , if you facing some lags or the ROM is not smooth try this , wipe data,system,cache,dalvik cache and then do a factory reset then flash vendor BRK3 then flash the rom then flash endurance aosp kernel,gapps and magisk and then again wipe cache and dalvik cache and then reboot , if u still have lags again flash kernel and magisk and then wipe cache and dalvik cache , I had issues with lags but after doing that the rom works fine , smooth and no lags
[Treble-Enabled Device Development A/AB ROMS] rohheat:
How to find which of this supports my device ???

ARM64-AONLY

ARM64-AB

ARM-AONLY

A64-AONLY (ARM32-BINDER64)
[Treble-Enabled Device Development A/AB ROMS] noslen69:
Error when trie to pair my Smart Band.

here is a video of the error (error on 0:57min).:

https://drive.google.com/open?id=1Dh1ukkdPm_Ea-PgZ8Ts73CfSAbAVv1Kk

I have send a logcat in post #1098. Thanks for any help.
[Treble-Enabled Device Development A/AB ROMS] jazzyd1:
The stock file manager always work out of the box for my Redmi 3- ido and the hardware buttons have always been available for use on my phone (a vendor overlay always provide this).. Because I prefer using double tap home button to sleep my phone.. And so far the array of possibilities available for hw-buttons customization found on Havoc GSI is the most extensive I have observed.
[Treble-Enabled Device Development A/AB ROMS] vince31fr:
You should tell first what's your device
[Treble-Enabled Device Development A/AB ROMS] vince31fr:
That's fine, the donation links in the OP concern the main devs and leaders. Supporting them is good to let havoc being improved..
[Treble-Enabled Device Development A/AB ROMS] vince31fr:
I'm sorry but I don't see the problem. You should try with other GSIs, other vendors, ..