yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] pan_pietrek:
What's selinux status?
[Treble-Enabled Device Development A/AB ROMS] phhusson:
A GSI won't change SELinux status, this is mostly a matter of boot.img/vendor.img.
[Treble-Enabled Device Development A/AB ROMS] ohwarumbloss:
Moderate, whatever this tells you ;)

I never cared much about this Security Stuff in Kernel (or wherever in System) because I do trust in the Devs ;)
[Treble-Enabled Device Development A/AB ROMS] o1100101:
Not working change of accent color and button remaping in settings on mido
[Treble-Enabled Device Development A/AB ROMS] pchatzop:
To get FM Radio working on this rom again, and probably in any other gsi as well, extract the contents of FMRadio.zip(on the gdrive folder) to your devices /vendor/app location with any root file explorer. This is probably mido-specific, since i dont know any other treble device with FM radio capability.
[Treble-Enabled Device Development A/AB ROMS] ohwarumbloss:
Hey Sir, will keep this Project up for a longer Time and are you planning to come to MIDO Forum? I'm sure there is a bunch of People waiting for this ;)

Greetings and thanks once again :)
[Treble-Enabled Device Development A/AB ROMS] pchatzop:
The accent colors crash is a RR source bug, they are practically a mess after the introduction of styles and the march security patch. It will be fixed soon. The real issue are the overlays needed to enable hw keys remapping, notification led color customization and disabling the hw button backlight after they are turned off. I will probably have to introduce some some small changes to the vendor partition(like the fm radio apk i posted earlier) since i would like to keep this build Generic as in GSI :) . Mido has plenty of great roms, and if you are dependent on the broken functionality, or need an enforcing kernel, you are welcome to use any of them. Integrating the overlays in the system image is trivial, but it beats the purpose of keeping it generic.
[Treble-Enabled Device Development A/AB ROMS] darksam96:
Honor 9 Lite Bootoop

Flashed the RR v2 rom last night & it went to bootloop even after following all the steps precisely.

Then, flashed the AOSP v12 (PHHs) using the same procedure & although it booted, the rom is way too crappy for even a single day usage.Namely some issues are no VoLTE, frequent force closure of apps without even opening them & most of them don't even open, no extSD support etc.

No stock rom available for H9L as of now so stuck with this junk, SOMEONE PLEASE HEP ME OUT !!!!
[Treble-Enabled Device Development A/AB ROMS] phhusson:
Well you're running mido, AFAIK, mido is running permissive SELinux for the moment.

That's not really mido specific, and there is a standard Treble HAL for FM Radio,(android.hardware.broadcastradio) so it would make sense to include it in my GSI.

Especially my MTK test device declares android.hardware.broadcastradio, so I can even test it.

(And once I include it, it will be easy for [MENTION=7008679]pchatzop[/MENTION] to include it in RR)

Thanks for pointing this lack of hardware support out :)
[Treble-Enabled Device Development A/AB ROMS] pchatzop:
The hal support is definitely there, since i just had to include the application with its assorted lib to get the feature working. The patch part is mido-specific, since i wouldn't like others to get bootloops trying to get an apk specifically built for mido in their vendor partition :) Btw, is there an aosp equivalent for the fm radio application in the aosp oreo sources?
[Treble-Enabled Device Development A/AB ROMS] whiplash1:
V 1 didn't boot on the Honor 9 Lite. V2 went till the bootanimation and bootloops there.
[Treble-Enabled Device Development A/AB ROMS] pchatzop:
If you could kindly get me a logcat at boot time, i could find the issue causing the rom to not work on some huawei devices. I want to apply more huawei patches for the next build, but i want to know the issue first before blindly patching everything :)
[Treble-Enabled Device Development A/AB ROMS] ohwarumbloss:
One thing I noticed, there is now Signal while charging. The Lockscreen tells "slow charging" but Ampere shows full speed.

So no LED for charging and no animation in Status Bar but it is charging just fine. No big Deal, just telling :)
[Treble-Enabled Device Development A/AB ROMS] phhusson:
I didn't find one, sadly.

I guess I'll try CAF's of Lineage's app
[Treble-Enabled Device Development A/AB ROMS] whiplash1:
Sadly I can't pull a logcat while booting coz USB debugging is broken in the current ROM I'm using - phh's AOSP treble ROM. Otherwise I'd have pulled a logcat through adb while booting v2.
[Treble-Enabled Device Development A/AB ROMS] pchatzop:
I will disable adb authentication in the next build, should make it easier to find the issues.
[Treble-Enabled Device Development A/AB ROMS] danishaznita:
hello , tho i am not from Huawei , we at Mi5 has tested and ended up with the same bootloop, here is a word from our trebble developer [MENTION=3545504]smeroni68[/MENTION]

Hope this help :D
[Treble-Enabled Device Development A/AB ROMS] phhusson:
Nope. This is a proprietary HAL, so there is no way this is the reason it won't boot.
[Treble-Enabled Device Development A/AB ROMS] danishaznita:
Alright thankyou , will forward to them
[Treble-Enabled Device Development A/AB ROMS] hippow:
Does some1 have the problem, that the phone doesnt recognise any headphones?
[Treble-Enabled Device Development A/AB ROMS] phhusson:
Which phone? Direct 3.5mm headphone (i.e. not usb-c) ?
[Treble-Enabled Device Development A/AB ROMS] hippow:
ah sorry, forgot to mention it:

phone: Mido

its direct 3.5mm. I found a workaround for it with an app, which forces to play the music through the audio jack.
[Treble-Enabled Device Development A/AB ROMS] antaris108:
Thanks for the nice ROM... Its very smooth with the stock kernel...tried also the r5 treble kernel, but it doesn't work with this ROM...

Any one get it to work with this ROM on mido?
[Treble-Enabled Device Development A/AB ROMS] ohwarumbloss:
Nope, same here, ended in Bootloop but the stock Kernel is doing great.

(But it's strange as the Kernel works in phhusson's AOSP and in Treble LOS)
[Treble-Enabled Device Development A/AB ROMS] antaris108:
I find it strange too, but how you said before...stock is doing great:svetius:
[Treble-Enabled Device Development A/AB ROMS] Lokanath_405:
Hey guys, i am using the official rr rom on mido...and there is no support to specify notification lights....does the solution given in the thread is helpful for me???
[Treble-Enabled Device Development A/AB ROMS] pchatzop:
It will probably work, but keep a backup just in case.
[Treble-Enabled Device Development A/AB ROMS] darksam96:
---------- Post added at 09:39 PM ---------- Previous post was at 09:37 PM ----------

[/COLOR]

Have encountered the same problem in my H9L after flashing the RR v2 so had to flash the AOSP v12 but sadly its way too crappy even for a single day usage so can you kindly upload the stock rom if you happen to have the backup coz honestly I need a stable rom as my daily driver.
[Treble-Enabled Device Development A/AB ROMS] ohwarumbloss:
Whoops, edited, Peace :)
[Treble-Enabled Device Development A/AB ROMS] pchatzop:
Livedisplay is now fixed for mido, thanks to the new overlays by abhishek. Unfortunately his new vendor implementation breaks the rom completely.

It causes the rom to boot a black screen, the reason of which i am currently trying to find right now. Therefore, if you use this rom, dont flash his newest build to update the vendor partition, just update your framework overlay from the fixes folder and you will get livedisplay working.
[Treble-Enabled Device Development A/AB ROMS] Sudeep Duhoon:
The rom is in treble section so it is supposed to work with treble devices. If it doesn't, testers are supposed to give feedback/logs. His tone might be out of his league and he just complaint without helping op in any manner to fix the issue but the fault is not on his side.

People here don't appreciate the effort, which op took to compile this rom, they just complain without providing any help to maintainer and suppose to get perfectly stable rom. This is frustrating and disrespectful.
[Treble-Enabled Device Development A/AB ROMS] ohwarumbloss:
You are right, excuse me. Maybe I've spend to much time here the last 3-4 weeks and have seen to much of this. Should have just said nothing.

But for this Rom (Not the AOSP of course) there is also:

Once again, forgot my position and didn't want to hurt somebody. My serious apologies!

Peace!
[Treble-Enabled Device Development A/AB ROMS] pchatzop:
Treble is a new standard, and a new way that roms will be released and tested in the future. It is bound to have the usual growing pains associated with it when coming to use within the community. Everything released on xda, i believe it goes without saying, you use it on your own risk.

Phhusson has done a stellar job, and I spend many days trying to adapt it to a lineage based tom. Of course i cannot have every single device that is treble enabled for testing, and like most developers, i released something i created for personal usage to the good of the community. Unfortunately, and you can see that even in posts over at phh's thread, it gives some people a sense of entitlement, something that drove many developers away from xda.

For now, i cannot do much than ignore this post and ones in similar tone. If you want to help the development, use the newest rom that has adb auth disabled, and get any logs you can extract about your problem.
[Treble-Enabled Device Development A/AB ROMS] Sudeep Duhoon:
i believe you didn't get the gist of my reply. Let me rephrase.

Being rom in treble section a user flashed it on his device out of his free will, no one asked him to. That's what a tester should do.

Alas! It didn't worked for him. What can he do to make it work? Submit logs and request the maintainer to fix the issues. But he just compliant and compared it with other rom and moved on. This is pure disrespect and it is frustrating. Being a developer myself i know the feeling.

Even if a log is submitted, the maintainer is free to fix, ignore or even drop the project completely. No one is paying him for the work he is doing for the community.

I didn't favored any particular person in my reply. I tested this rom, didn't work for me (cursed Huawei treble device), tried other rom (huawei fixes inclueded), worked for me. No harm done.

I saw that this is somewhat mido oriented, didn't submit the logs as that could be more work for both of us, as there is other rom particularly for huawei devices.

I replied to that post because a senior member (962 posts) lashing out at a junior member (total 27post) is sad.

But i do understand that not appreciating someones work and even complaining without providing any support is even sadder.

I appreciate the work you have done and not complaining in any manner (never did). It takes time to do all this and a big heart to contribute to the community.
[Treble-Enabled Device Development A/AB ROMS] pchatzop:
Well, there has been a fair bit of misunderstanding in our communication. I understand your sentiment, though i would not call myself a developer. rather an android enthusiast.

This rom is not mido oriented, it is an attempt in lifting some work off phhusson shoulders and giving people with treble enabled devices another option. Phh himself stated that his work is directed to be used as a base for more advanced(or plainly put,more feature rich) custom roms to come forward. Seeing other more skilled devs and rom developers reluctant to use phh's work to release treble enabled versions of their roms(only some treble assisted/platform specific versions) i decided to take a crack at it myself, and the result booted on my mido.

My goal however, is not creating another rom for mido. Mido has plenty of good roms and developers,many of them much more skilled and experienced than I, and it will continue to be supported, treble or not. What i would like to see, is more people and developers coming to these forums and learning about treble development and the future it holds for custom roms.

Ideally, getting more skilled developers in building their favorite roms as generic system images.

Treble is the single thing i have been waiting for android since i first got my first smartphone, a moto g in 2013. It is the phone equivalent of IBM/PC-compatibility for the computers of the 80s. In a year from now, installing any rom in any new smartphone will be as trivial as installing linux on a windows computer. I felt compelled to contribute after seeing so little activity in this subforum, where the very future of android rom development is laid out.

That being said, everything about this rom is limited by my own skillset and testing environment. Therefore, any and all logs and constructive comments are welcome. My goal is getting this running in as many devices as possible, in line with the principles of treble development.

It should now be made clear, that the sheer importance of project treble as a whole(at least to me), does not allow me to engage in and entertain petty comments and needy requests. I agree with you in not favoring sides and not bulling other members, and therefore advise other members to to refrain from doing so, and keep the discussion relevant to development.
[Treble-Enabled Device Development A/AB ROMS] phhusson:
Here is the result on Mate 9
[Treble-Enabled Device Development A/AB ROMS] antaris108:
Running the test 1img and till now all is running fine :)

Thanks a lot for your work...i am running it in mido
[Treble-Enabled Device Development A/AB ROMS] pchatzop:
Thanks for the logs [MENTION=1915408]phhusson[/MENTION] , the problems seem selinux related it seems. The two failed services, i did not find them in the vndk-tests for mate 9, no wonder it passes the test but fails on the device . If i knew how to patch sepolicies now :confused: .
[Treble-Enabled Device Development A/AB ROMS] febry_valdy:
Any plans to make another custom gsi like aex, omni, etc?
[Treble-Enabled Device Development A/AB ROMS] pchatzop:
I want to try fixing this rom first for more devices. RR is my favorite rom, after all, and i hope other developers create their favorite roms and maintain them. I contemplated building aex, because since it's mostly aosp based, adapting overlays will be easier.
[Treble-Enabled Device Development A/AB ROMS] janver22:
Thanks for this rom. Been using it on my Mido for days now. Will you keep updating this?
[Treble-Enabled Device Development A/AB ROMS] pchatzop:
Yes, i will, since its also my daily driver. Abhisheks kernel(with my added exfat support) is probably the best for me, and i have tried and built dozens. Right now though i am building some test builds to improve compatibility, but not new sources by RR, dont want to take the gamble that new sources will break something. If they boot, i will upload them. But they will not make a difference for mido.
[Treble-Enabled Device Development A/AB ROMS] droidbot1337:
that...... would...... be.......... AMAZING!! extended is my favorite ROM. i used to prefer cypher but lately its far too watered down. AEx just has so many good features. i hope you eventually build it, it would be great. btw, thanks for your work. also, treble is truly awesome!
[Treble-Enabled Device Development A/AB ROMS] danishaznita:
hello [MENTION=7008679]pchatzop[/MENTION]

our developer has updated Mi5 treble and the F/ error from the log before is now gone

However , It still doesnt boot and now returns (full log attached)

[ 03-14 02:12:55.200 6822: 6838 E/AndroidRuntime ]

*** FATAL EXCEPTION IN SYSTEM PROCESS: android.ui

java.lang.ArrayIndexOutOfBoundsException: length=1; index=3

at com.android.server.am.ActivityManagerService$UiHan dler.handleMessage(ActivityManagerService.java:185 9)

at android.os.Handler.dispatchMessage(Handler.java:10 6)

at android.os.Looper.loop(Looper.java:164)

at android.os.HandlerThread.run(HandlerThread.java:65 )

at com.android.server.ServiceThread.run(ServiceThread .java:46)

at com.android.server.UiThread.run(UiThread.java:42)

thank you in advance
[Treble-Enabled Device Development A/AB ROMS] phhusson:
AOSP 8.1 GSI works on this updated vendor?
[Treble-Enabled Device Development A/AB ROMS] pchatzop:
Thank you for the logs. The true problem lies with android.hardware.weaver@1.0.so as i am seeing in the logs. What i found, is that this service is properly built and included in the image, therefore should not cause problems. There are a bunch of errors after that though, such as an error reporting "Vendor interface is incompatible" :p .Give my new test2.img a try with a clean flash(when you have time) and report back.
[Treble-Enabled Device Development A/AB ROMS] Carlosmff:
Hello, Does test2.img from today working in any Treble enabled phone?

I own a Mi6 and really tempted to try it...
[Treble-Enabled Device Development A/AB ROMS] pchatzop:
It works on mido, and thats why i posted it. All patches by phhusson are in place and I included a commit about android.hidl.base@1.0 that should improve compatability with 8.0 blobs, many of which are used to make the unofficial treble port of mi6. Unfortunately, it seems los-based roms need more patching to make a truly universal GSI. If you try it and it works, we will know that it works on mi6 as well :)
[Treble-Enabled Device Development A/AB ROMS] iamnotkurtcobain:
Does that mean your rom will work on S9 now?
[Treble-Enabled Device Development A/AB ROMS] 再飞行:
Have you try to install the mido rom on you Huawei P9?
[Treble-Enabled Device Development A/AB ROMS] HelpMeruth:
it does, ill test the "test2" image today
[Treble-Enabled Device Development A/AB ROMS] pchatzop:
Official twrp is out, take a backup and try it :) . I doubt it will work though, s9 sepolicies are hell, even phh has trouble with them. If someone builds a permissive kernel for s9, it may work.
[Treble-Enabled Device Development A/AB ROMS] HelpMeruth:
doesnt boot same error:
[Treble-Enabled Device Development A/AB ROMS] danishaznita:
hi

Yes absolutely , ive been using it for daily driver

i have tested Test2 and it didnt boot . log attached (i did leave it for a few minute )[MENTION=7008679]pchatzop[/MENTION]

EDIT : sorry , looks like HelpMeruth and i posted the log in the same time , so this is duplicated post (my log is longer :p ).
[Treble-Enabled Device Development A/AB ROMS] smeroni68:
Yes... is our main and only GSI reference for Mi5 vendor testing.

EDIT: Internally JDC dev and testers are using also a built LOS 15.1 trebelized for testing too. Both are perfectly working on Mi5.
[Treble-Enabled Device Development A/AB ROMS] ohwarumbloss:
[MENTION=7008679]pchatzop[/MENTION] , I lost my 18/02 build of treble LOS on Mido by accident, did I get it right your RR won't run on the new Vendor?

Thx in advance

Edit: jepp, got it right, does not work, nvw
[Treble-Enabled Device Development A/AB ROMS] RadixCube:
Just flashed.

Your v12 vanilla GSI boots successfully and everything related to system works flawlessly:highfive:
[Treble-Enabled Device Development A/AB ROMS] Woobhurk:
:oHello! How can I patch the latest Magisk to work on Treble ROM?

Thanks
[Treble-Enabled Device Development A/AB ROMS] theOriginalSuperl2:
[MENTION=7008679]pchatzop[/MENTION]

How did you fix the button backlights, and how did you modify framework overlay? I want to build my own GSI for my Mi 5s Plus.
[Treble-Enabled Device Development A/AB ROMS] Sithu Htun:
Doesn't work on Mi 6. After resurrection remix dots logo, it went back to recovery. Phh's RR is working fine though. Mi 6 Dual Camera portrait mode is also available there.
[Treble-Enabled Device Development A/AB ROMS] pchatzop:
You have to extract the framework-res__auto_generated_rro.apk from your vendor/overlay folder with any root explorer or twrp, decompile it with apktool, and then add to integers.xml(in the res/values folder of the working directory) the line <integer name="config_deviceHardwareKeys">83</integer> . The "83" part may be different depending on your device, you can search a device tree customized for your device to find the exact value. You also have to add this line to public.xml before recompiling. Then push the modified file back to the vendor partition. I can modify it for you if you find it difficult to achieve on your own, just attach it in a message here.

This is the proper way to do it, but i included a patch in the rom i built to always turn on the backlights, even if the overlay is not present. But having the overlay allows you to turn the backlight off and also customize the keys in roms that support it(like RR).

As for the rom still not working on some(or most) devices, well , i'm stumped. I completely cleared my working directory, resynced the full source using phh's scripts, applied the patches for the backlight and microg, and built it. Everything apart from these 2 things, should be the same as in phh's rom. It still works on my mido, but what good is a treble rom if it only works on one device?

Therefore i urge most users to just use phh's rom, since most dont actually use microg and the hw button backlights issues can be solved by simply modifying a vendor overlay.

And please dont post on the phh-treble telegram group about problems with this rom. Use this thread instead. The guy already has a tough job maintaining 3 roms and the underlying treble implementation, we dont need to further bug him about probable mistakes in my build environment.
[Treble-Enabled Device Development A/AB ROMS] theOriginalSuperl2:
Thanks for the detailed answer. I'll try modifying the framework apk myself, and I'll post if it worked.
[Treble-Enabled Device Development A/AB ROMS] theOriginalSuperl2:
I added the integer value (also 83 for my device) to the integers.xml, but I don't know what to add to the public.xml file. All the other lines in there start with public tags, so the integer value didn't look like it belonged there. I tried anyway, and it failed to compile, saying the value was already defined.

I then tried compiling with the value only added to integers.xml, and not to the public.xml file at all. This makes the button settings work, but I still have no backlight. What do I need to change? Thanks for your help.
[Treble-Enabled Device Development A/AB ROMS] pchatzop:
You can try searching in the framework overlay for building rr for your device, maybe there are some more strings related to button backlight, like devicehasvariablebuttonbrightness and buttonbacklightlevel. Add those to your overlay as well. To add those to public you have to adapt them, study the file format a little and I'm sure you will figure it out. You just have to declare the fields there, not their actual value.
[Treble-Enabled Device Development A/AB ROMS] chen8894:
Hi

What is the difference between the img with su and the one without ? Do we need to install Phhusson supersu to get it rooted

?

Many thanks.
[Treble-Enabled Device Development A/AB ROMS] pchatzop:
The img with su contains the standard lineage root, you need to enable it from developer settings. You dont have to install any other app, privacy guard(inbuilt within rom) handles the root.
[Treble-Enabled Device Development A/AB ROMS] culiacanazo:
im downloadfing for mate 10 pro but whats the difference in the two 64s one being su and the other nada? i dont wanna make assumptions since you dont mention it. also, by trebelize you mean the ones who arent natively treble? thank you for the work

----

10-9 the su question, answer to my right
[Treble-Enabled Device Development A/AB ROMS] theOriginalSuperl2:
[MENTION=7008679]pchatzop[/MENTION]

Can you please build a patched version of magisk 16.4?
[Treble-Enabled Device Development A/AB ROMS] jeuxtype:
the headphone won't work i'm on honor 8 lite,there are some dev who fixed it in other roms
[Treble-Enabled Device Development A/AB ROMS] phhusson:
Are those other ROMs opensource? Can you link them?
[Treble-Enabled Device Development A/AB ROMS] jeuxtype:
https://xdaforums.com/p8lite/p8-lit...m-lineageos-15-1-huawei-p8-lite-2017-t3774331

This is haky's i tested it and it works

https://xdaforums.com/p8lite/p8-lite-2017-development/rom-rros-pra-t3774444

And this is dil3mm4.dev's rom i didn't tested it but i think it works