yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] tmvkrpxl0:
Hi, how's your process going? i mean, what bug are you going to fix? or what feature are you going to add? tell me about it detail
[Treble-Enabled Device Development A/AB ROMS] nobody9147:
Does anybody why passwords or fingerprints wont be saved when using apps like banking? Im using a Note 9.

Gesendet von meinem Phh-Treble vanilla mit Tapatalk
[Treble-Enabled Device Development A/AB ROMS] phhusson:
Would you have an app with this problem that wouldn't require an account?
[Treble-Enabled Device Development A/AB ROMS] Chr1stOnABike:
Removing magisk and kernel patch fixed this for me. I just use the prerooted rom.
[Treble-Enabled Device Development A/AB ROMS] Ivanbarker:
Quick question, does this have widevine security level L1 or L3?
[Treble-Enabled Device Development A/AB ROMS] Genie's:
I tried this ROM after flashing Stock Firmware with MTK SP Flash Tool, so I think that will not be helpful.

---------- Post added at 02:49 PM ---------- Previous post was at 02:47 PM ----------

No, in my M5S, when I tried to turn on bluetooth, FC message of Bluetooth popped up and bluetooth is turned off briefly.

And, I have already tried this ROM after flashing Stock Firmware via SP Flash Tool, but the result is same.
[Treble-Enabled Device Development A/AB ROMS] nobody9147:
No, all of them need an account to function.

Gesendet von meinem Phh-Treble vanilla mit Tapatalk
[Treble-Enabled Device Development A/AB ROMS] requiiiem:
[MENTION=1915408]phhusson[/MENTION] lastest build boot on Moto e5? in mine not: /
[Treble-Enabled Device Development A/AB ROMS] Zhifu_Yu:
Great Job, Thanks! Most of things work.

I tested it on the Xiaomi Mi 8 Pro (Mi8UD, equuleus), for now, 2 things still don't wokr:

- sound is broken, need to delete /vendor/lib/soundfx and /vendor/lib64/soundfx to fix

- in-screen fingerprint is not recognized.
[Treble-Enabled Device Development A/AB ROMS] phhusson:
Widevine level depends exclusively on vendor support.

I think Pixel's vendor support Widevine L1, but I think that's the only ones.

Yup that's a known issue, which is fixed for next release.

You can fix it by yourself by editing /system/etc/init/cameraserver.rc and removing the last line starting with rlimit

For the first one, what is your device code name? ("equuleus" doesn't sound right, I'm guessing there is a typo in there?)

For in-screen fingerprint , I'll need logs. please open an issue at https://github.com/phhusson/treble_experimentations/issues
[Treble-Enabled Device Development A/AB ROMS] heitang:
My phone is XZ1,G8342. Everything goes well except the crasy brightness. I believe there's something wrong with the brightness bar. When I slide it from left to right, it doesn't change normally. It changes from the most brightly, and then suddenly becomes the least, and then the most again. There are four times of the change. Can you work on fixing it?:victory:
[Treble-Enabled Device Development A/AB ROMS] Zhifu_Yu:
Thanks for reply.

The code name equuleus is correct, it's another variant of Mi 8... Hardware specification of Mi 8 Pro (or Mi8UD) should be fast the same as Mi 8 EE (code name ursa) except the 3D Facial Recognition is replaced with Infrared Face Unlock... Speake of this, the setup menu for Infrared Face Unlock is not listed in security settings.

The offical site of Mi 8 Pro is mi.com/global/mi-8-pro/. You can find the fastboot rom under bigota.d.miui.com/8.12.13/equuleus_images_8.12.13_20181213.0000.00_9.0_cn_e243f943f1.tgz,

I can see the fingerprint setup menu in Security settings. But when I start the wizard, It tell me to touch the fingerprint sensor on the back which is actually in front of it under the display.

I noticed there is no overlay of this type of hardware in /system/overlay/treble-overlay-xiaomi-*., could you please add this hardware? Thanks.
[Treble-Enabled Device Development A/AB ROMS] HueyT:
I bet its due to arm64 binder for 64 bit devices using arm32 android--v105 does not have this
[Treble-Enabled Device Development A/AB ROMS] CreateYourDream:
no go version for pie?
[Treble-Enabled Device Development A/AB ROMS] phhusson:
Yup that's fixed in current git.

You can fix it before the next release by replacing /system/bin/rw-system.sh with latest in git: https://github.com/phhusson/device_phh_treble/blob/android-9.0/rw-system.sh

Well, we need a stock Pie ROM running Android Go to extract gapps from, and I'm not aware of any.

Wrong bet.

What was previously called "arm" was arm32 binder32, and still is. "arm_binder64" is something new for arm32 binder64.

No actually the issue was a change in a init script due to Android "9.1"

https://github.com/phhusson/platform_frameworks_av/commit/11fa6964aa3f75d0988bdc32ba584ea3bef2b69a
[Treble-Enabled Device Development A/AB ROMS] SkyWorldWide:
Just tried the ARM32_Binder64 and I get this error in ADB Fastboot: FAILED (remote: sparse flash write failure) ☹️ maybe you guys can help ?

Device: Mobicel HYPE

OS: Android Oreo GO 8.1.0

SOC: MT6739

CPU: 64 bit (32 bit mode)
[Treble-Enabled Device Development A/AB ROMS] KaMyKaSii:
Hi, [MENTION=1915408]phhusson[/MENTION]. Sorry for the off-topic question but I just bought an Asus Zenfone 4 (KE554KL) which has treble support but does not have a dedicated vendor partition. I wish I could flash the GSIs on it. The part of creating the vendor partition is no problem, but would you have any tips or tutorials on how to properly move the files from /system/vendor to /vendor in a functional way? Should I just move the files while retaining all linux and selinux permissions? And then hex edit all files replacing /system/vendor with /vendor, would it be that simple?
[Treble-Enabled Device Development A/AB ROMS] HueyT:
Try v105
[Treble-Enabled Device Development A/AB ROMS] Ssssss8622:
I have a vivo y83 device. It supports treble. But unfortunately there is no developer support for this device. Do you think the boot image can interfere in it. It has a mediatek p22 SoC and I think it is permissive as others
[Treble-Enabled Device Development A/AB ROMS] phhusson:
I'm 95% sure your device is arm, not arm32_binder64.

What's the size of your system partition?

It doesn't have Treble support, since having a vendor partition is required for Treble support.

Now the question is, to which point did Asus lie.

If they lied just a bit, you should be able to really just create a partition, and move /system/vendor to vendor partition, and that's all.

I'm sorry, I don't understand.

I'm guessing you have a problem booting my GSI...?

If that's the case:

- Use UNMODIFIED STOCK ROM images (boot.img, vendor.img, recovery.img, ...)

- First try my AOSP 8.1

- Please tell PRECISELY what happens when you try to boot GSI

- Try to recover logs from recovery. Reboot into recovery, and try to do adb pull /proc/last_kmsg last_kmsg.txt (it might or might not work...)
[Treble-Enabled Device Development A/AB ROMS] KaMyKaSii:
Well, I'm not sure if it can be considered a lie because as far as I know Asus has not bragged about it or something. This device originally came out with Android Nougat and until then there was no need to have a dedicated vendor partition. From what I understand, they made the necessary modifications to the bootloader/kernel according to the treble project and standardized the BLOBs, but still keeping them in /system/vendor (they probably did not want a headache having to repartition the devices during the upgrade to Oreo ). There is a very simple post here on the XDA about this:

https://www.xda-developers.com/asus-zenfone-4-android-oreo-project-treble/

And I know that just for an image is difficult to say, but for you, does the content of /system/vendor "seems" to what it should be in /vendor? With both partitions mounted I could simply do the migration with the "cp -a /system/vendor /vendor" command? Would not there be a need to hex edit the files?
[Treble-Enabled Device Development A/AB ROMS] I1V1A1N:
I have on my box X96 amlogic s905x your android 8.1 v25 and v26 is already working well.But on android 9.0 runs the android logo and it does not go.The screen

appears for a short time and breaks .Indicator from blue to red.ADB fastboot does not work on my box so i did a zip file program.In included boot.img , vendor.img , and your system.img also file_context.My files that run on android 8.1 v25 are here.

https://github.com/s1a1g1e1r1t/AOSP_8.1_V_25_phhusson_on_amlogic_s905x/projects

There is dmesg from twrp after firmware.
[Treble-Enabled Device Development A/AB ROMS] king1990:
[MENTION=1915408]phhusson[/MENTION]

Thanks for your great work

I trying to build specific hardware overlay for my device without success even when i try to build .apk for the existing overlays I'm getting this error :

"Generating treble-overlay-xiaomi-mia2 build/build.sh: line 23: 3222 Aborted" and does not generate anything
[Treble-Enabled Device Development A/AB ROMS] Rmihaja:
mtk incoming call bug

Hi [MENTION=1915408]phhusson[/MENTION]

I know mtk ril issue is a common bug of mtk devices. And there's a fix from your GitHub page (MTK RIL Problems #57). Unfortunately, that doesn't work in my phone :( so please help me out. Only incoming call has a problem, making calls and messages is fine. USSD works too.

I've taken two logcat when someone is calling me. The first is when I leave the mtk-ril.so unmodified and the second when I edit the lib file from "AT+EAIC=2" to "AT+EAIC=3".

My phone : Tecno R8O (shipped with android 8.1 go)

chipset : mt6737

rom used : aosp 9.0 v108

Thanks a lot for your support:)
[Treble-Enabled Device Development A/AB ROMS] bendep:
seems like this image doesnt work with my mi pad 4 plus. i came fro miui.eu latest rom and flashed the recent aonly treble image by phh. everything went fine while flashing, but then during the installation, bluetooth and gboard stop working. therefore i tried to finish the installation by disabling my wlan password, and then i am stuck during the searching for update screen.

any advices?

---------- Post added at 10:13 PM ---------- Previous post was at 10:12 PM ----------

seems like this image doesnt work with my mi pad 4 plus. i came fro miui.eu latest rom and flashed the recent aonly treble image by phh. everything went fine while flashing, but then during the installation, bluetooth and gboard stop working. therefore i tried to finish the installation by disabling my wlan password, and then i am stuck during the searching for update screen.

any advices?
[Treble-Enabled Device Development A/AB ROMS] phhusson:
I'm guessing you disabled encryption and/or you installed magisk.

Try to disable both of those. and use stock boot.img.
[Treble-Enabled Device Development A/AB ROMS] Fersho:
Hey bro, ROM is not booting on Moto E5 v108
[Treble-Enabled Device Development A/AB ROMS] bendep:
thanks for your fast reply phhusson :)

i didnt disable encryption and havent installed magisk. i am going to search the forum for how to extract the stock miui boot.img and will try to flash it. hopefully this solves the issues on my mi pad 4 plus.

anyway, how to know about all these things?

i followed those tutorials:

https://www.xda-developers.com/flash-generic-system-image-project-treble-device/

https://github.com/GBouerat/xiaomi_mi_pad_4/tree/master/ROM

none of these things are mentioned there ;)
[Treble-Enabled Device Development A/AB ROMS] dcraffam:
[MENTION=1915408]phhusson[/MENTION] hey thanks I appreciate all of the work I was hoping if you can answer a ?? do you think or know if the (mtk ril data problem) will be fixed in the next build? Thanks hope for a reply ..
[Treble-Enabled Device Development A/AB ROMS] nebkas:
Hi, are there any news with the not working ril on the galaxy a6 plus?
[Treble-Enabled Device Development A/AB ROMS] Shobit Joura:
Hello devs , I found in aosp8.1 thread that u told that if microg users are in enough amount then u will make a patched version ,

Sir this is a request only if u can make , there are few users who uses microg ,

So if possible plzz make a microg supported aosp version with signature spoofing ,

Yours ,

Aops Roms user:)
[Treble-Enabled Device Development A/AB ROMS] aljoscha81:
Will there be a android 9.1?
[Treble-Enabled Device Development A/AB ROMS] KaMyKaSii:
[MENTION=1915408]phhusson[/MENTION] sorry for boring you, but could you answer this?
[Treble-Enabled Device Development A/AB ROMS] HueyT:
https://xdaforums.com/project-trebl...arm64aosp-9-0-0r21-microg-ufofficial-t3878115
[Treble-Enabled Device Development A/AB ROMS] Shobit Joura:
This is for a only , I am having a device with a/b partition...
[Treble-Enabled Device Development A/AB ROMS] SkyWorldWide:
Will do bro

---------- Post added at 03:57 PM ---------- Previous post was at 03:51 PM ----------

Sorry for the late reply

System Partition Size: 1,3 Gig
[Treble-Enabled Device Development A/AB ROMS] MartinX3:
[MENTION=1915408]phhusson[/MENTION]

Tested your v108 build with the latest Sony Xperia XZ2 December 9.0 patch (.126 version).

It is a AB device with treble support.

Your GSI booted fine :)

But there was screen flickering touching on a wlan in the assistant at the first time.

But it gone away.
[Treble-Enabled Device Development A/AB ROMS] MotoX4:
I am seeing a few people not paying attention to this important detail.

- A bug without a device name doesn't exist
- A bug without a log doesn't exist

It helps everyone to help you to know the details beyond just saying something does not work. If you're new and are unsure how to make a log, this easy to follow guide will help you. https://xdaforums.com/showthread.php?t=2774386
[Treble-Enabled Device Development A/AB ROMS] JBolho:
Few people? Man, that's more like a fast spreading disease on XDA now... "this doesn't work, FIX IT!", or the other one "when update? No update? Want update! This dead?"
[Treble-Enabled Device Development A/AB ROMS] :
...and on the other side devs more and more forget to update header, changelog, give up a project without message and so on...so keep calm my friend!
[Treble-Enabled Device Development A/AB ROMS] JBolho:
One thing does not excuse the other. Many often than not, devs just quit and leave because of frustration caused by the attitude of users that simply don't read, don't search, and don't care if their question has already been answered or not. (many times the answer is 1 post behind but they just don't give a crap)

I have a huge OP and 2nd post on my kernel, full instructions and Q&A, full changelog since version 1, you don't imagine how many times I noticed many people just ignoring everything that's written there. We write warnings, they don't care. We say we don't support a specific thing, they come complaining about that same thing. As long as a Developer comes here and shares his work, taken out of his time, out of his own headaches, out of his own sweat and knowledge, for free, no one here is entitled to demand anything.
[Treble-Enabled Device Development A/AB ROMS] :
Very good example is when an ota comes, everyone asks how to update rooted oxygen os, very few bother to read the OP which has clear instructions.
[Treble-Enabled Device Development A/AB ROMS] MotoX4:
Amen! Very well said. :good:

You've just outlined the reason why I often feel obligated to help whenever and wherever I can. Sometimes that means contributing my very limited coding skills. Most times it means me trying my best to answer questions or nudging users here in the right direction (as my previous post was doing), so as not to boggle down the developer. And sometimes it means putting my money where my mouth is and giving a donation or two because I realize everyone's got to eat and while I appreciate folks do things in their free time, I'm OK with contributing some of that free time into paid work. ;)

I guess my point is that a lot of folks come into XDA feeling entitled and forget that the ROMs here are both privilege and a gift. It is important to show all the developers here some appreciation and respect for their work. That means making it easier on them and contributing how you can. :)

But I also realize not everyone is as good or is as able to code or Q&A or offer financial backing. But the least they could do is provider logs, which in turn, helps the developer, help us. Well, at least here is hoping. :good:
[Treble-Enabled Device Development A/AB ROMS] phhusson:
Yeah known bug. Will be fixed in v109.

Someone else is doing it:

https://xdaforums.com/project-trebl...arm64aosp-9-0-0r21-microg-ufofficial-t3878115

I'm not sure I understand your sentence.

Anyway, screen flickering should be fixed in next release.

You can test it ahead of time by replacing system/bin/rw-system.sh with https://raw.githubusercontent.com/p...0d5fdb393a21159195fc80d9bee9b1e3/rw-system.sh
[Treble-Enabled Device Development A/AB ROMS] MartinX3:
Sorry, i come from Germany. :)

The flickering only appeard a short time tugging on a WiFi network in the first installation assistant.

Maybe it would appear again , but the time period I tested the system was too short. :)
[Treble-Enabled Device Development A/AB ROMS] Wyzco:
Do you get a detailed break-down of the battery usage on a per-app basis?
[Treble-Enabled Device Development A/AB ROMS] MartinX3:
Sorry, I don't have one.

I only tested something because of a bug in my last AOSP build I delivered in XDA. :)
[Treble-Enabled Device Development A/AB ROMS] phhusson:
If it's missing for you, you can fix it by doing a GSI device overlay:

https://xdaforums.com/project-trebl.../guide-how-to-make-gsis-overlay-file-t3878974
[Treble-Enabled Device Development A/AB ROMS] conanedogawa1011:
Sir, I need assistance. I have a treble device but it has a MT6739 chipset, and I have literally no idea which image should I choose. Is there a universal TWRP that can work for my device?

Cherry Mobile Flare 7

2GB RAM, 16GB ROM

MT6739
[Treble-Enabled Device Development A/AB ROMS] michael_hamada:
Have you tried Treble checker?

Search in Play store " Treble Check" , it might help you... I wish.
[Treble-Enabled Device Development A/AB ROMS] SkyWorldWide:
But whenever I try and download Gapps my phone gets detected as a 64-bit ?

---------- Post added at 04:49 PM ---------- Previous post was at 04:36 PM ----------

But whenever I try and download Gapps my phone gets detected as a 64-bit ?
[Treble-Enabled Device Development A/AB ROMS] hamzio7:
Hi dev....I tested it on Huawei Mate 10 Pro after upgrading to EMUI 9.0/ ANDROID 9.0 and i got a bootloop is it possible that this ROM doesn't support EMUI 9.0 vendor?
[Treble-Enabled Device Development A/AB ROMS] ImKiira:
It doesn't boot on emui 9. I have the same device
[Treble-Enabled Device Development A/AB ROMS] phhusson:
It boots fine on my EMUI 9 device (Honor View 10)

So as usual.. LOOOOGGSSSS
[Treble-Enabled Device Development A/AB ROMS] tmvkrpxl0:
Hi, i used this rom and i found some problems.

My device: A605K

And i don't know how to get log. I'll search on internet if that is necessary to fix

Problems:

Mtp not working(even after remove sd card and reboot)

Touch function dies after turn off screen about 5 minutes

NFC is missing. NFC button cannot be found in where it should be.

Sim card is not detected. But stock rom can detect it

Sorry for my english

---------- Post added at 03:38 PM ---------- Previous post was at 03:36 PM ----------

And could you tell me how does process gong?

I'm keep waiting for new version since last month(November)
[Treble-Enabled Device Development A/AB ROMS] HueyT:
Originally Posted by michael_hamada:

It's the illusion of GSI or should I say... it's the illusion made by Google.

GSI won't promise 100% compatibility.

GSI is just a some kind of framework, so the developers of each ROM have to consider its compatibility for every device even though they can't test them all.

So that if he wants to add some cool feature, he might sacrifice compatibility unconsciously sometimes.

Though your device is Treble-compatible, not all of GSI ROMs make you happy.

(I'm HueyT and I support this message)
[Treble-Enabled Device Development A/AB ROMS] phhusson:
(I prefer the marketing name rather than code name. Codenames are very annoying to keep track of)

Most of those issues are known issues (with no fix yet, except for MTP sadly), except for touch.

Do you have Magisk installed? That might explain the touch issue.

If that's not the case, please dump the output of "mount" command when run from su
[Treble-Enabled Device Development A/AB ROMS] phhusson:
(I prefer the marketing name rather than code name. Codenames are very annoying to keep track of)

Most of those issues are known issues (with no fix yet sadly, except for MTP) except for touch.

Do you have Magisk installed? That might explain the touch issue.

If that's not the case, please dump the output of "mount" command when run from su
[Treble-Enabled Device Development A/AB ROMS] SkyWorldWide:
Hey guys so I flashed the AOSP 9.0 arm vanilla no su GSI. How do I root it? tried Magisk (18.0) but it shows "Core Only Mode" no root. I tried phhusson's root it gives error 255 then I tried SuperSU but it fails to patch. I need root to move some apps to system as it does not have gapps. When I try to flash gapps it gives error 70 well and checking system partition I'm only left with 60mb so I can't flash gapps. Any help will be welcomed.
[Treble-Enabled Device Development A/AB ROMS] DarkFrenzy:
display theme is not applying, hide notch is not working, icons not stable in notch arear
[Treble-Enabled Device Development A/AB ROMS] Shiroyasha21:
Redmi S2 (ysl)

uncertified and brightness buggy

this overlay using old system dump

https://github.com/phhusson/vendor_hardware_overlay/blob/master/Xiaomi/RedmiS2/AndroidManifest.xml

redmi s2 is not using "ro.vendor.build.fingerprint" anymore but "ro.vendor.build.fingerprint_real"

"ro.vendor.build.fingerprint" will read as polaris (MiMix2S)

also "android:requiredSystemPropertyValue="+*iaomi/ysl*" its xiaomi not iaomi
[Treble-Enabled Device Development A/AB ROMS] tmvkrpxl0:
here's the log from mount command. log was too long to write here. so i uploaded into Google drive.

and touch error has fixed mysteriously. i didn't do anything about this, but fixed

i have Magisk installed, but what can i do with this? Installed mod: fbind, xmlpak, Youtube Vanced black themed, Gboard Themes, Busybox, DNS Switcher, ADB & Fastboot, Sudo4Droid, Modded Pixel2 launcher

and version is 18.0v
[Treble-Enabled Device Development A/AB ROMS] phhusson:
This sounds like a (terrible) joke.

Could you link me to stock ROM dump, so I can witness this by myself?

Yeah I'm pretty sure it's not fixed, and as soon as your device really gets into deep sleep, you'll get the issue again.

So yeah, it sounds like an issue that I've already fixed, but Magisk prevents my fix from working.

The fix is to delete/disable /vendor/bin/hw/android.hardware.power@1.0-service

I'll let you live with that
[Treble-Enabled Device Development A/AB ROMS] Shiroyasha21:
its not joke :D

vendor/build.prop is different from https://github.com/TadiT7/xiaomi_ysl_dump/blob/CORRUPTED---ysl-user-8.1.0-OPM1.171019.011-8.7.12-release-keys/vendor/build.prop which is used for overlay Referrer

compare it with attached build.prop

I'm using xiaomi.eu 8.12.20

I can't upload system dump my net is too slow (I hope someone could do it :p )
[Treble-Enabled Device Development A/AB ROMS] DNS_HM_0301:
I think xiaomi.eu rom use fingerprint of Xiaomi Mi Mix 2S for certified on Play Store and real fingerprint as "ro.vendor.build.fingerprint_real"
[Treble-Enabled Device Development A/AB ROMS] phhusson:
Sorry, but I'm only supporting Google certified devices.

I recommend you flash official stock ROM from Xiaomi for your device.
[Treble-Enabled Device Development A/AB ROMS] DNS_HM_0301:
yes, bro!

I will try again with official rom soon.

but on xiaomi.eu base rom, I find some way to fix some bug:

- for brightness, I add to build.prop "persist.sys.qcom-brightness 4095"

- fingerprint sensor problem same as some Xiaomi devices, from your v107 build, it's fixed with 2 file in system/usr/keylayout: "uinput-goodix.kl" and "uinput-fpc.kl"

Can you add to next build?

Device: Xiaomi Redmi S2

Code name: ysl

Thank you very much! Sir.