yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] oF2pks:
June 114 release

Latest June 114 is uploaded : https://androidfilehost.com/?a=show&w=files&flid=286761

Changelog

:

- (phhusson changelog)

- F-DroidPrivilegedExtension integration ( F-Droid: Settings/ExpertMode/Privileged on)

- Webview 74

- latest Recorder & DroidGuard + fdroid/signed Netscope

- NEW rebuilt of GmsCore (Nanolx x2 editions) with anticipated 17.9.99 (PlayServices variants); for both vtm and mapbox (new MaR-V-iN integration, check Nanolx thread; apk is attached in post#1)

Broken

:

- SafetyNet (wip?)

- (Playstore registration with Webview74 & old previous 17999May's compatible gmscore)

- F-Droid V.102.3 auto-update needs Settings/ExpertMode/Privileged disabled

[MENTION=5870173]cercelcremene[/MENTION] Generic (GSI (AEX) was sole GSi stamp on AFH so) link goes fine to my phhusson's MicroG; [MENTION=3562143]ttocs99[/MENTION] , no need for twrp: only fastboot flash system [arm32/64].img
[Treble-Enabled Device Development A/AB ROMS] cercelcremene:
Just tried the latest version. Almost everything works lighter than on other GSIs. It is a pity that dark theme is not working.
[Treble-Enabled Device Development A/AB ROMS] oF2pks:
A bit tricky : apply a dark/black Wallpaper first, and then 2x toggle light & dark options in Settings/Display/Advanced/DeviceTheme (Automatic options seems buggy).
[Treble-Enabled Device Development A/AB ROMS] oF2pks:
July 115 Release

Latest July 115 is uploaded : https://androidfilehost.com/?a=show&w=files&flid=286761

Changelog

:

- (phhusson changelog)

- Webview 75 (systemWebview can be upgraded directly with https://github.com/LineageOS/android_external_chromium-webview/tree/lineage-16.0/prebuilt)

- Netscope 2.2-4

- LATEST rebuilt of GmsCore (Nanolx x2 editions) with anticipated 17.9.99 (PlayServices variants); for both vtm (default) and mapbox (new MaR-V-iN integration, check Nanolx thread; apk-v2 is attached in post#1)

Broken

:

- SafetyNet (wip?)

- (Playstore registration with Webview75 & old previous 17999May's compatible gmscore)

- F-Droid V.102.3 auto-update needs Settings/ExpertMode/Privileged disabled
[Treble-Enabled Device Development A/AB ROMS] oF2pks:
August 119 release

Latest August 119 is uploaded : https://androidfilehost.com/?a=show&w=files&flid=286761

Changelog :

- (phhusson changelog) use arm64_abSEAMLESS version for Samsung s10

- DejaVu Back-end updated to 1.1.12

- Browser (Quarks CarbonRom) bug fixes (:random crash)

- aosp Pie /system/bin/ curl added (embedded Terminal: curl --version)

- *xml readable via Files/HTMLviewer

- aosp Pie egg Paint accessible via launcher

- GmsCore updated to 19.9.999 mapbox. Switching between vtm & mapbox can need wipe for GmsCore GoogleServicesFramework DroidGuard apks' cache & account re-creation.

Broken

:

- SafetyNet (wip?)

- (Playstore registration with Webview75 & old previous 17999May's compatible gmscore)

- F-Droid V.102.3 auto-update needs Settings/ExpertMode/Privileged disabled
[Treble-Enabled Device Development A/AB ROMS] Fznwolf:
I think this might be my next S10 project.
[Treble-Enabled Device Development A/AB ROMS] Fznwolf:
Got this working quite well on my Snapdragon S10 (SM-G9730)!

A few notable items are:

-Auto Brightness isn't working - Perhaps you could help me with this? I tried the fix for PHH here: https://github.com/phhusson/treble_experimentations/issues/492 but it hangs on boot. I suspect there may be more work required on framework-res__auto_generated_rro.

-Signal strength appears to be empty.

-Using a modded Gcam appears to allow me to use the wide angle camera.

-Dual speakers works.

-Bluetooth works very well.

-Provided google maps works.

-Stupid fast, booting the OS takes below 3 seconds.

-Root works well.

-Fingerprint scanner untested

-NFC untested

I might start a thread documenting more of this if I can't find anything.

TYSM [MENTION=7489364]oF2pks[/MENTION] [MENTION=1915408]phhusson[/MENTION] and [MENTION=3149697]FlatOutRU[/MENTION]
[Treble-Enabled Device Development A/AB ROMS] MDV106:
any plans on supporting arm32_binder64 firmwares with A/B slots? the ones in op only support A_only
[Treble-Enabled Device Development A/AB ROMS] oF2pks:
Just uploaded v119 here : https://androidfilehost.com/?fid=1899786940962592691

(with Quarks' ad_block list an translations updated to latest, and webview 76)

... that issue is indeed the right way for solving this.
[Treble-Enabled Device Development A/AB ROMS] MDV106:
Thank you so much! I will try this out later.
[Treble-Enabled Device Development A/AB ROMS] guillermohs9:
Sorry to bother with this again... Will there be more Oreo builds?
[Treble-Enabled Device Development A/AB ROMS] MDV106:
DeviceID app reports that the Google Serivices Framework ID as not found. As a result I cant get app push notifications to work since Push Notifications Tester says push notifications have not been registered. What can I do to fix this?

EDIT: i've managed to fix this by re-installing microG through Magisk and rebooting.

BTW, are there any themes that work for AOSP? I tried a theme on f-droid and it failed to theme.
[Treble-Enabled Device Development A/AB ROMS] flash713:
I'm using substratum w/swift dark and it's beautiful.

I don't use Google store so I downloaded substratum theme manager apk off apk mirror and side loaded. Works fine. :)
[Treble-Enabled Device Development A/AB ROMS] XopmoH:
Thanks a lot, this is the best AOSP build! MicroG services work great! (like all applications that require Google Play services). I don’t understand why when I installed MicroG on LineageOS 16.0 myself, they didn’t work the same way as in your build... Please share the secret of building GSI firmware with MicroG services. :o
[Treble-Enabled Device Development A/AB ROMS] oF2pks:
Latest Nov 121 is uploaded : https://androidfilehost.com/?a=show&w=files&flid=286761

Changelog :

- pre release based on November aosp 9.0.0_r50, but security patch still reports August cve.

- Bromite latest webView v76 with ad-blocking, upgradable via F-Droid repo https://fdroid.bromite.org/fdroid/repo (Bromite 76 returns a 74/SamsungS9 webclient https://github.com/bromite/bromite/issues/156#issuecomment-445449741: Mozilla/5.0 [Linux; Android 8.0.0; SM-G960F] AppleWebKit/537.36 [KHTML, like Gecko] Chrome/74.0.3729.157 Mobile Safari/537.36); if v76 seems too selective, upgrade to latest Bromite without ad-blocking (v78)

- Optimized browser Quarks ( offline reading mht , print/pdf , share/clipboard target ...) https://gitlab.com/oF2pks/jelly/commits/jQuarksMore package is renamed org.lineageos.jelly for better LineageOS upstream.

- GmsCore updated to 19.9.999 mapbox. Switching between vtm & mapbox can need wipe for GmsCore GoogleServicesFramework DroidGuard apks' cache & account re-creation.

Broken

:

- SafetyNet (wip?)

- F-Droid V.102.3 auto-update needs Settings/ExpertMode/Privileged disabled

microG additional patches are attached in post#2, and all fdroid certified backends have elevated aosp privileges (/system/priv-app).
[Treble-Enabled Device Development A/AB ROMS] moctir:
Massive thanks for doing this! I recently bought a Cubot King Kong Mini which is a new model so there is no TWRP or custom ROMs, I managed to install the GSI but couldn't get signature spoofing working. I decided to try this and everything works great. Used Magisk to root and now have everything except the swipe library on the AOSP keyboard working (will keep trying though). It's going to be nice just following this thread and not having to follow and install microg updates for a change, flashing your ROMS will be much easier.

Great job and thanks for your work!
[Treble-Enabled Device Development A/AB ROMS] oF2pks:
Experimental builds (use with caution)

For 2x arm64 (a & a/b) powerful devices, I've uploaded experimental flavor of latest Phhusson Pie 123 build (cve: Dec2019); both generic permissions:

_Internet

_Wakelock

are switched to runtime and thus are user accessible. Like _Location permission, they can be turn on/off efficiently for all apps targeting minimal sdk23.

Specifically, _Wakelock is automatically granted safely at any time for all /system apps, including /vendor. Conversely _Internet can be turned off for any /system apps : by default at primary installation /vendor and 3x Google (Playstore ContactsSync CalendarSync) are off, and thus should not leak any data without user consent.

Be sure to backup /data partition prior to any toggled app: toggles will survive any rom upgrade/downgrade. Updating from previous ufOfficial will result with all apps turned on for both _Internet & _Wakelock. (Check attached minimal patch).

To ensure usability, I have added LineageOS

Caffeine tile (quick settings) with long-press activating the designated sub-menu with all Runtime permissions

(where dynamic Spoof Package signature is).

Remember that every new app install will have _Internet & _Wakelock turned off. Every app update will keep previous state. Every /system and /vendor apps will have _Wakelock on. Apps targeting sdk22 or lower will have _Internet on.

Depending your feedback, I may keep this changes in next Phhusson cve2020 release: don't hesitate to fire a post if you believe it's either dumb or dysfunctional (this will save my time...).

( [MENTION=1915408]phhusson[/MENTION] attached is paranoid patch to fix Nfc tile not showing in aosp/Pie)
[Treble-Enabled Device Development A/AB ROMS] silhouette_blacktea:
Thanks for your work,

Any plan or consider to build Android 10(Ten) Version?
[Treble-Enabled Device Development A/AB ROMS] Nickthegr8:
Hi, what's the dirfference between mapbox and foreground version?
[Treble-Enabled Device Development A/AB ROMS] oF2pks:
I'm still waiting for feedback on the internet & wakelock experimental wide runtime switch: if some want it in next release, please do express for it.

btw, for the ones with Magisk onboard, you can use my new appOps to manage your device deeper : https://xdaforums.com/android/apps-...etter-v1-0-t3637705/post81673275#post81673275 (, final release will be push by tomorrow).

GmsCore19999NanolxNEWmapbox-4b_Foreground.apk has latest marvin commits,

fix for 0-prefixed MNCs in Android 9 : https://github.com/microg/android_external_UnifiedNlpApi/commits/master

Run GCM services as foreground service if needed : https://github.com/microg/android_packages_apps_GmsCore/commits/master

Unfortunately my Sony xz1 doesn't boot any android10 (gsi aospXperia...), also microG is not 100% working on android10 (with or without my additional patches); moreover, latest marvin's SafeParcel major update is not in the Maven Central Repository yet: https://github.com/microg/android_external_SafeParcel

(if any confirms Xiaomi redmi k30 poco X2 compatible with [MENTION=1915408]phhusson[/MENTION] GSi, I may buy one for android10 microG specifically...)
[Treble-Enabled Device Development A/AB ROMS] sabotage154:
hello [MENTION=8725890]moctir[/MENTION]. its good to hear that there are other xda users who have the Cubot King Kong Mini. im trying to get microg installed on my device but since there is no custom recovery for this device i have been manually trying to remove the gapps to make way for microg. i see that you have been successful using this solution here on this thread. i dont see any instructions here on how to accomplish this . i know how to flash roms using custom recovery and things like that but i have never installed a rom w/out using custom recovery . would you be able to send me instructions on how you managed to get this working on the cubot king kong mini? thanks!!
[Treble-Enabled Device Development A/AB ROMS] sabotage154:
My device has a 64 bit processor but is running 32 bit kernel archtechture armv7l. i believe im supposed to flash:

V121system-arm32_binder64-ab-ufOfficial-nosu.img.xz (remove the .xz extension before flashing)

is that correct?

i dont have custom recovery so i was going to do the following:

1. for my current stock setup i have access to the stock boot.img and i patched it thru magisk but it didnt work so i found a boot.img on 4pda site for my device that another user had patched and flashed that via fastboot and got magisk root that way. should i remove magisk apk then flash stock boot.img then do factory reset before starting?

2. reboot into bootloader/fastboot mode

3. fastboot flash system V121system-arm32_binder64-ab-ufOfficial-nosu.img

4. reboot to rexovery and do factory reset, wipe dalvik cache and cache

5. reboot

6. get magisk/root: should i flash the same patched boot.img that worked for me before that i found on 4pda site or will just patching the stock boot image work on this GSI? (remember: magisk was unable to patch stock boot.img successfully)

7. install riru core and riru EdXposed via magisk to get xprivacy running on android 9 (this is what i currently have running on stock rom)

how do i know if i have to flash the dm-verity fix fastboot flash vbmeta name_of_vbmeta.img ?

any help would be greatly appreciated. this is the first time im going to be flashing a GSI AND w/out custom recovery.

DEVICE INFO:

Hardware : MT6761V/WE

Model : KINGKONG_MINI

Build number : CUBOT_KINGKONG_MINI_9101C_V06_20191121

Build date UTC : 20191121-130020

Android v : 9

Baseband v: MOLY.LR12A.R3.MP.V75.5.P2,MOLY.LR12A.R3.MP.V75.5.P2

Kernel v : 4.9.117+ (feserver@v121-T7910O) (gcc version 4.9.x 20150123 (prerelease) (GCC) ) #2 SMP Thu Nov 21 21:24:23 CST 2019
[Treble-Enabled Device Development A/AB ROMS] moctir:
Hi [MENTION=4002550]sabotage154[/MENTION], I've been meaning to do this since I got it working as there were 3 times I thought I totally bricked it! I've forgotten the full process now but hopefully this is everything. It's a little bit more complicated than my older phones because of the disable verification but you're most of the way there. I think this will answer you questions but you've the right system image, with the device you have to use vbmeta and with magisk you have to use the bootloader. Here are the full details.

Download the Stock Rom from here and SP Flash Tool just in case (this process probably can be done with SP Flash Tool but I wasn't able to manage it). Unzip the stock ROM.

When you reboot to bootloader and unlock via:

sudo fastboot flashing unlock

Then on your computer navigate to the folder with the unzipped ROM (for me was NA_mt6761p_d936p_9101cmp_chuanqi_cc_256gbitp24d3_p_lte_3m-fdd-cs_mul_20191121-210020_songlixin_PC) and type

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

That was the part that took me a while to figure out as if you don't do this it seems to work without it but then it will bootloop when you try to switch it on. From here on it's standard.

fastboot flash boot boot.img
fastboot flash recovery recovery.img

The flash whatever system you are using, I unzipped the .xz file so for me the command was

fastboot flash system V121system-arm32_binder64-ab-ufOfficial-nosu.img

I haven't updated to a newer version yet.

For root I installed magisk manager but had to patch the recovery to get root, not just boot, note I did both as flashing boot alone doesn't give you root but I'm not 100% sure if you need both or just recovery. So in magisk get it to patch you boot and recovery images and then put those on your computer, go to bootloader and use:

fastboot flash boot magisk_patched_boot.img
fastboot flash recovery magisk_patched_recovery.img

I hasn't used magisk this way before but you can read more about that recovery here.

To get root then you need to reboot to recovery, hold power button + volume up and select Recovery. This will appear to boot as normal but you will have root when you do it this way and not when you boot normally. Unfortunately I do not have reception when I do this but do have root, other users have this problem but I have not found a solution. I have to say since I started using this build I almost never use root so I rarely boot to this.

I hope all that works for you, let me know if you have any more questions. Note that if you think you bricked it it's actually quite hard, however what happens is you can't do anything until the battery has almost completely discharged, then when you hit the power button you'll get the no battery and when you plug in you can get to Recovery again. This is quite annoying if you've charged it quite high as you'll have to wait a long time to discharge and be tapping on the power button a lot!!
[Treble-Enabled Device Development A/AB ROMS] sabotage154:
i ran the treble check app and it appears like the Cubot King Kong Mini has a 64 bit processor with the 32 bit kernel BUT it DOES NOT have a/b partition. It uses just the A partition. So i was thinking maybe the correct file is:

V121system-arm32_binder64-aONLY-ufOfficial-nosu.img

but you said you used the a/b partition file here correct:

V121system-arm32_binder64-ab-ufOfficial-nosu.img

i had the same exact problem when trying to get magisk running on stock. The only way i could get the magisk to work was flashing the stock boot.img that i found on 4pda for this device that someone had made changes to after it was run thru magisk. But i did not have to patch the recovery partition. Im wondering if i can flash the same patched boot.img i found on 4pda that worked for me on stock after flashing this GSI?

When you say you dont have reception when you do this but do have root do you mean the phone doesnt get a signal? so the cell service does not work?
[Treble-Enabled Device Development A/AB ROMS] moctir:
I thought the check I did said it was a/b but maybe a is fine so. A/b is working for me anyway!

To get root I need to boot to recovery, it starts as normal except I have root access but for some reason no reception. If I reboot as normal then I don't have root but have signal, so it is a bit annoying but I tend to never need root access for very long. There has been a few updates to Magisk since and I haven't tried to repatch it.

However, if that one you downloaded works for it probably is okay, depends how much you trust downloading a random boot partition over the internet! I would recommend you try to patch it yourself first and if it doesn't work then use that one.
[Treble-Enabled Device Development A/AB ROMS] sabotage154:
i managed to get this installed on my device. i installed the following image: V121system-arm32_binder64-ab-ufOfficial-nosu.img.xz

everything seems to work expect for push notifications. here are the results from push notification tester app:

Play Services Installed : YES

Internet Connectivity : YES

Register for Push Notifications : NO

Connection to Server : YES

in microgsettings self test everything has a checkbox except for

Location backends setup

UnifiedNlp do not have location to test geocoder

In Microgsettings Google Services section

I dont have an account setup because i dont use google account (microg worked fine on another device without having an account setup)

Google device registration : Enabled

I also tried to manually dialing *#*#2432546#*#* to do a manual device registration. and still not working.

I dont see anything mentioned on the post about gsfproxy. that is required for push notifications to work correct?

are push notifications supposed to work on this GSI?
[Treble-Enabled Device Development A/AB ROMS] moctir:
I have no issue with push notifications on that build and also don't use a Google account. Have you got Google Cloud messaging turned on in microg? After you turn it on you might want to reboot and then when you install an app it should register for cloud messaging, hopefully that might solve it? I have also enabled Safetynet but not sure that is relevant. In Manage Accounts I also have Trust Google for app permissions on but I presume that was default.

Just texted the push notification tester app there and it was successful.
[Treble-Enabled Device Development A/AB ROMS] oF2pks:
Check your UnifiedNlp/Settings (backends) in microG; you may also need to 2x toggle off/on Location once in global aosp Settings/Security&Location .
[Treble-Enabled Device Development A/AB ROMS] sabotage154:
thanks for your guys help, much appreciated.

[MENTION=8725890]moctir[/MENTION], i didnt even notice the google cloud messaging menu option inside microg after the flash? maybe i just missed it? so what i did was i got impatiend and flashed the microg via magisk. once i did that i did i opened microg and noticed the layout was now in green compared to orange previously and noticed the google cloud messaging option in microg and enabled it and it push started working then. BTW, thank you for your help flashing this. I used your instructions along with this write up here.

@0F2pks, is it ok to run it with the microg from magisk? what is the difference (they seem to be different in layout colors at least). is there a way to revert to the microg backed into your GSI if needed (im curious as to if i just missed the google cloud messaging on your microg?

also playstore and 2 other gapps are installed. i went ahead and disabled per your instructions. are those needed? do they communicate with google if disabled? can i uninstall them, if so, how do i uninstall? i had issues uninstalling gapps on my stock rom thats actually why i switched to your gsi.

other than that the gsi seems great. even the block vpn function works which is a huge headache on custom roms (it rarely works on custom roms, i dont know why) . i also find flashing the gsi much easier and straightforward than custom roms. only drawback is backing up images of my device since i dont have twrp. any idea on how to backup this gsi install on my MTK6761V/WE device? (im tempted to try your experimental that you mentioned but would like to backup before i do).
[Treble-Enabled Device Development A/AB ROMS] TumbleTimble:
Thank you for this build! I installed v123 on my Fairphone 3 and it boots fine However, I'm getting weird problems when installing apps and my Play Store does not work either..

Problems I'm facing:

- Play Store does not boot. On first boot I toggle all MicroG settings and login to my Google account, self-check returns all OK. I force-stop Play Store but it crashes immediately. Sometimes I see the swipe menu open up but then it crashes too.

- Tried installing Aurora Store for apps. It boots but for anonymous login it says: "Permission denied (missing INTERNET permission?)". Google login returns "Webpage not available ERR_CACHE_MISS".

- Direct .apk installs run into problems. NewPipe cannot load/search for anything, Firefox crashes immediately.

I'm sorry for the long list but I really hope to get this magnificent build working on my phone. Any ideas?
[Treble-Enabled Device Development A/AB ROMS] oF2pks:
That is v123 specific purpose expected : https://xdaforums.com/showpost.php?p=81550957&postcount=66. Previous v121 (

post#1

) has normal _Internet _Wakelock behavior.

Even if you don't launch after first install, any new app can leak privacy straight (or upload malware...); that is why they are off by default: inconvenient yes, but with real privacy.
[Treble-Enabled Device Development A/AB ROMS] ulfw2018:
Hi, are there any plans to update this ROM to the April security patch? I'm really enjoying using it because it's the only GSI that has microG included. I've tried flashing other GSIs and then installing microG however it doesn't work.

Thank you.
[Treble-Enabled Device Development A/AB ROMS] HueyT:
"e" has microG included also. Check several posts above here.
[Treble-Enabled Device Development A/AB ROMS] MDV106:
Whats the safest way to upgrade to a later build of this rom? Do I need to backup everything, wipe phone then flash latest build and recopy backed up content? or can I just flash the latest build via TWRP without worry of losing files?
[Treble-Enabled Device Development A/AB ROMS] oF2pks:
Just flash system.img should be fine (+twrp Magisk if in-use).

For lucky ones with android10 GSi compatibility, I'm now testing latest [MENTION=1915408]phhusson[/MENTION] with microG + permissionsX; should be ready soon: let me know what arm32/64 flavor you need, I will start with a/b seamless first (dsu).
[Treble-Enabled Device Development A/AB ROMS] HueyT:
Arm64 AB for me, Moto g7
[Treble-Enabled Device Development A/AB ROMS] 1234newbie:
Arm64 a-only, Huawei Mate 10 lite, if i may ?