yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] uehlsh:
Take the sdcard from the May version and replace it with the July version. But, as far as I understand, you are not smart enough to do this operation correctly. Ask the person who understands how to do it correctly.
[Treble-Enabled Device Development A/AB ROMS] 1234newbie:
Yes, u have absolutly right...

So don't bother to answer me and thanks for advice.
[Treble-Enabled Device Development A/AB ROMS] uehlsh:
Hello maestro.

The firmware works better than others, but there are bugs.

1. The screen is not blocked by two taps. (Perhaps this is a launcher bug)

2. Sometimes the interface freezes in the "Settings" application

3. The same errors are repeated in the log

Device UMIDIGI A3 ARM64A mtk6739

П.С.

I understand that at the word "mtk" your hand reaches for the revolver

I attach the log
[Treble-Enabled Device Development A/AB ROMS] jadephyre:
Is there any way to convert the GSI into a ROM for a specific device?
[Treble-Enabled Device Development A/AB ROMS] RedSkull23:
An eventual maintainer should apply for being recognized as an official maintainer for that specific device. Then, device specific ROM can be built.
[Treble-Enabled Device Development A/AB ROMS] jadephyre:
I was actually asking for some sort of information to do that for myself, and no, I was not looking to become an official maintainer...
[Treble-Enabled Device Development A/AB ROMS] uehlsh:
There is no such way.

Firmware for a specific device is assembled with the vendor, and not converted.

To build the firmware, the developer needs the vendor's source codes.

To test the firmware, a developer needs a smartphone of your model.

These are the minimum requirements.

In addition, the developer needs to eat and drink something;)

If you have experience and knowledge, you can delete files from the firmware that are not related to your device.

---------- Post added at 08:37 PM ---------- Previous post was at 08:36 PM ----------

There is no such way.

Firmware for a specific device is assembled with the vendor, and not converted.

To build the firmware, the developer needs the vendor's source codes.

To test the firmware, a developer needs a smartphone of your model.

These are the minimum requirements.

In addition, the developer needs to eat and drink something;)

If you have experience and knowledge, you can delete files from the firmware that are not related to your device.
[Treble-Enabled Device Development A/AB ROMS] thecoolkid:
Are Gapps included? Why is system so big? Any love for devices with 2,5GB system partition? ;)
[Treble-Enabled Device Development A/AB ROMS] uehlsh:
Nobody bothers you to unpack the system image and remove unnecessary files.

Google services are included in the firmware.

I was able to reduce the image size to 2.1 Gb
[Treble-Enabled Device Development A/AB ROMS] thecoolkid:
I would love to be able to do that, and I tried and looked it up, but there seem to be no tools for windows... Can you point me in the right direction of how you did that?
[Treble-Enabled Device Development A/AB ROMS] uehlsh:
https://yadi.sk/d/vwkBuifkwpfqtg

It is Portable. Program and fix

OR Linux:

Required: good command line knowledge

OS: I did in Ubuntu 18.04 / 16.04

0.open the terminal

1.sudo su

2.apt install simg2img

3. go to the directory with the .img firmware image

4.simg2img system.img system.img.ext

5.mkdir -p / mnt / loop

6.mount system.img.ext / mnt / loop

7. go to / mnt / loop and delete what you want (you can only delete under root!)

8.we leave / mnt / loop in the directory with the image

9.umount / mnt / loop

10.e2fsck -fy system.img.ext

11.resize2fs -M system.img.ext

12.img2simg system.img.ext system-mod.img

that's all)

the penultimate command will reduce the image as much as possible. if after that the size does not fit, repeat the steps from step 6, removing more programs or unnecessary vndk. keep in mind that there is something like a limit - even if there is 200-300MB of free space at some value, the image will stop shrinking!
[Treble-Enabled Device Development A/AB ROMS] thecoolkid:
Is that the one?

Android ROM Tool v. 2.0.3

I'll try that thx. The thing with Linux is I'd have to set-up a virtual machine for that, for all my usual needs I use Linux subsystem in Windows 10, but it just can't mount ext4.
[Treble-Enabled Device Development A/AB ROMS] uehlsh:
Yes. Consider fix
[Treble-Enabled Device Development A/AB ROMS] AsrielDash:
Just updated to latest version

Can I make notification icons all white like previous version?
[Treble-Enabled Device Development A/AB ROMS] uehlsh:
put the previous version
[Treble-Enabled Device Development A/AB ROMS] alvinprimo:
But we have to do this again on every update yes?
[Treble-Enabled Device Development A/AB ROMS] smvsmv:
This is the GSI that works best on my UMIDIGI Power 3. I need and got root, but want to install Magisk. There's no TWRP for the phone and installing magisk zip from SD card doesn't work. The flashing fails - I tried the phh version of magisk as well as the stock. So does the direct install method from magisk.

I have a patched boot image from stock that works on stock, but when I flash it on the GSI, ended up with a boot loop into fastboot.

Is there another way to install magisk? Does someone have a boot.img from this GSI or know how to extract it? I can patch it myself.
[Treble-Enabled Device Development A/AB ROMS] Rush:
For extracting a boot IMG generally, there is a command

Execute this with some sort of root permissions (adb root, or else)

Adb shell dd if=/dev/block/bootdevice/by-name/boot of=/data/media/0/bootimg4magisk.img

Then select wait, and patch that image, this can't be executed without root, but might work with Adb
[Treble-Enabled Device Development A/AB ROMS] smvsmv:
Thanks! On the UMIDIGI Power 3, the command to retrieve the boot.img to Downloads folder is

dd if=/dev/block/by-name/boot of=/storage/emulated/0/Download/boot.img

However, my theory that patching this boot.img with Magisk will help, was wrong. Still ended up with a boot loop.

---------- Post added at 03:33 AM ---------- Previous post was at 02:41 AM ----------

I have the issue with the SD card not being available.. Formatting doesn't resolve it. A few posts back I saw a sdcard file that is supposed to be replaced.. Anyone know what to do with it? or another way to resolve this issue?
[Treble-Enabled Device Development A/AB ROMS] Rush:
Try formatting it with a different device (eg:Pc) first
[Treble-Enabled Device Development A/AB ROMS] uehlsh:
This will depend on the size of the updated firmware image.

---------- Post added at 05:19 AM ---------- Previous post was at 05:16 AM ----------

This will depend on the size of the updated firmware image.
[Treble-Enabled Device Development A/AB ROMS] TheDevelopper:
[MENTION=9034316]Dil3mm4[/MENTION], please kindly make a vanilla version for arm64-AB as you did previously last year, the raw image size is a little bit big for my system partition, I really enjoyed this rom on pie but can't use the Q version because of the raw image size
[Treble-Enabled Device Development A/AB ROMS] Dil3mm4:
I'm not interested in doing so.
[Treble-Enabled Device Development A/AB ROMS] Dil3mm4:
Changelog:

Security patches

5 August

Bugs addressed:

Fixed an edge case where clicking on ticker notifications would lead to a SysUI crash.

Fixed an edge case where bluetooth battery icon would get a wrong tint on lockscreen.

Fixed an edge case where SystemUI would crash with Fingerprint on display animations enabled.

Fixed Descendant Guardia icon with reticker on dark themes.

General round of optimization to ThumbUI.

Download it at:

https://downloads.descendant.me/
[Treble-Enabled Device Development A/AB ROMS] sooheb:
In recovery, he gave me a message that the file is large
[Treble-Enabled Device Development A/AB ROMS] Dark_Lion64:
Is this ROM passing safety net with or without Magisk? Or is Google Pay working? Sorry for asking, but I searched for keywords in the Thread but didn't find anything
[Treble-Enabled Device Development A/AB ROMS] uehlsh:
Disassemble the image, remove unnecessary vndk from the image, collect the image and flash

I did so - no problem
[Treble-Enabled Device Development A/AB ROMS] Tweaker Z:
How, do disassemble a system img file
[Treble-Enabled Device Development A/AB ROMS] uehlsh:
Have you tried to read the discussion thread?

https://xdaforums.com/showpost.php?p=83164657&postcount=155
[Treble-Enabled Device Development A/AB ROMS] Dil3mm4:
Changelog:

Security patches

5 September

Download it at:

https://downloads.descendant.me/

Cycle infos:

With these update Descendant X cycle ceases.

See you back on R when I'll release it.
[Treble-Enabled Device Development A/AB ROMS] Gomeman:
Hi

Flashed latest GSI on my device.

Things not working;

-Offline charging.

-Fingerprint sensor.

Things working.

-Camera back and front

-Bluetooth

Using supersu to root the phone. Magisk unstable, not posible to root.

Would like to know what would happen if my battery drains out. How am i going to charge it.?

Thanks.
[Treble-Enabled Device Development A/AB ROMS] TheBestKmanEver:
How do i remove the onscreen navbar (aswell as the gesture part)??
[Treble-Enabled Device Development A/AB ROMS] 420fox1:
Is the site down, Can't seem to get to it
[Treble-Enabled Device Development A/AB ROMS] uehlsh:
Go settings

---------- Post added at 08:11 PM ---------- Previous post was at 08:09 PM ----------

It is the problem you brpwser
[Treble-Enabled Device Development A/AB ROMS] Dark Stranger:
This gsi will no longer have an update. And the bugs that you report are not from the gsi but from the vendor that you are using.
[Treble-Enabled Device Development A/AB ROMS] Gomeman:
hi, not even using this gsi. I am using bliss. At least i got it rooted and passing safetynet.

Probably can live without fingerprint sensor and offline not charging.

Is it posible to flash another vendor?
[OnePlus 3 Guides, News, & Discussion] Deleted member 4405529:
I've not decided which way to go, so I've no zip currently. For testing I've made a build with the mentioned commits and deleted the fw stuff manually with find and xargs.

On los17 (sar) you should be able to locate init.environ.rc and delete the boot jar entry manually.
[OnePlus 3 Guides, News, & Discussion] Deleted member 4405529:
Can somebody confirm the validity of this information, please? With the op-mentioned files removed only the fingerprint authorized payment is lost, but Alipay and WeChatPay is still working with apps installed from playstore.

Thanx in advance.
[OnePlus 3 Guides, News, & Discussion] Deleted member 4405529:
[MENTION=10511117]Johan2020[/MENTION]

for find: you need to make sure that the wildcards are passed to find and arn't substituted by the shell. If you don't escape the wildcards for the shell, they are only passed if the shell can't expand the expression.

for lag: you need to check the log. Increase the logbuffer size to 1 Mio (at least) to catch the complete boot, reboot and do something like

adb logcat -d | grep -i -e ifaa -e soter -e ali
[OnePlus 3 Guides, News, & Discussion] GuestK00458:
I guess I found something:

03-12 12:58:12.521 1818 1818 E dex2oat : Could not create image space with image file '/system/framework/boot.art'. Attempting to fall back to imageless running. Error was: Unexpected component count in /system/framework/arm64/boot.art, received 14, expected non-zero and <= 13

No output on ifaa, soter or ali though, but seems some checks are done in boot.art which are not correct anymore because of removed blobs?

Edit:

Did a new flash without removing the blobs (script from above) and do not have those errors in logcat.

So seems indeed related to removal.

Let me know if I can help with some other testing... ;)
[OnePlus 3 Guides, News, & Discussion] Deleted member 4405529:
The number of boot jars seems to be somewhere, if rebooting to twrp and wiping caches doesn't help, I've no idea where to start searching. Maybe google is your friend to start investigating this.
[OnePlus 3 Guides, News, & Discussion] GuestK00458:
Ok, thanks. I always clear caches after new flash; rebooting and wiping did not solve the issue.

I probably have to live with it and keep the Ali, Soter and Ifaa stuff there where it is.
[OnePlus 3 Guides, News, & Discussion] Phaech4x:
I only tried Alipay and it still works after removing these files. Fingerprint authorization payment for Alipay does not seems works on lineageos-17.1 tho (with official modem and keep these proprietary files), but I remembered it works on lineageos-16.0

I'm a bit curious now about who wrote IFAA Manager (org.ifaa.android.manager), where are these source code from and how was it been adopted by LineageOS. The comment message says IFAA protocol support fingerprint and iris authorization.

[MENTION=4405529]nvertigo67[/MENTION] Thanks for your information, I didn't know removing these files cause lags for app start before. I can also confirm it cause noticeable lag, 1.30s to open settings, but cost 2.10s after remove these files.

[MENTION=10511117]Johan2020[/MENTION] I have update the post and add a link to the updated zip, does not seems lag here after flash the zip which deblobbed the modem and removed IFAAService+SoterService apk but keep ifaa manager and other proprietary files.

This command output every *.odex file in `/system`, {boot,boot-org.ifaa.android.manager}.{oat,art} and org.ifaa.android.manager.jar

grep -rl org.ifaa.android.manager /system

Maybe this explained why it still lags after removed ifaamanager from init.environ.rc, then the only solution to remove these proprietary files without performance drop is remove them at build stage.
[OnePlus 3 Guides, News, & Discussion] Deleted member 4405529:
Thanx! I hate not being able to test something myself.

BTW: Is there any source of current data of WeChatPay usage? Honestly, I havn't known about the existence of WeChatPay until the tencent security/privacy flaw some time back...

It's from oss (don't mix with oos): https://github.com/LineageOS/androi...0ee28ea#diff-1eba4e28cf441865f85a2298f9bd8312

The very first version has been reverse engineered: https://github.com/LineageOS/androi...b113b64#diff-1eba4e28cf441865f85a2298f9bd8312

I guess it's safe to disable the ifaa daemon service as well, as long as the manager jar is available for assembling the boot jar.

Yep. Removing all ifaa, soter, AliPay stuff at compile time works flawlessly - inspired by your first posting: https://github.com/nvertigo/android...mmit/d8f0471eee92fe608b5e9b0b30d52b63d6d3d79f

JFYI: I've made alipay* and soter* free firmware packages with referenve to this very thread: https://xdaforums.com/showpost.php?p=81997531&postcount=164

I'm running this combination without lag, drain or side effects (so far ;) ). Though I've done it for los-16, I see no reason why it shouldn't work for los-17.1 as well.
[OnePlus 3 Guides, News, & Discussion] Phaech4x:
Ipsos's Report of Market Share of Third Party Mobile Payment in China (in Simplified Chinese)

Chi*na’s Mo*bile Pay*ments Mar*ket Grows Over 15% in Q3 2019, Ali*pay’s Mar*ket Share Ex*ceed Half | China Banking News (in English) seems the articles is about this report

In mainland China, Alibaba and Tencent own over 90% of mobile payment market, Alipay almost own the whole mobile payment market a few years ago, probably because of Alibaba's Taobao which is one of the most popular online shopping site in China.

Tencent has WeChat Pay, QQ Wallet and Tenpay. these reports which mentioned market share Tencent owned probably include them. WeChat Pay is included in WeChat and QQ Wallet is included in QQ, WeChat and QQ are most most popular instant messaging app in mainland China. imo the main reason WeChat Pay been popular in China is it has Red Envelope (Alipay also has it tho), Chines ppl like social, WeChat and QQ are more like social network than other instant messaging platform. WeChat Pay require fee for withdraw while Alipay is free to withdraw, and lots of Chinese ppl love the Red Envelope thing. It's like almost every smartphone/"internet" user in mainland China has a WeChat account, not only just for communicating with others, they use it to order a takeout, use Mini Program or something.

And Tencent also own the most Gaming Market in mainland China, there is QQ Currency which is usually used to buy items in games.

https://www.scmp.com/lifestyle/gadg...-wechat-pay-and-payme-put-test-find-out-which

I think Alipay and WeChat Pay are almost only used in China and Hong Kong. The only reason I can think of those mainland Chinese smartphone manufacturers include ifaa/soter in their international firmware/modem is that Alipay and WeChat Pay is also popular in Hong Kong where people have access to Internet and use GMS, beside they are too lazy to maintain variants of firmware/modem.

Thanks I have confirmed just keep ifaa manager won't cause lag on app start. In the other words, all of related blobs, proprietary files and related services files are been removed, only keep ifaa manager the open source part.
[OnePlus 3 Guides, News, & Discussion] Galiis:
Confirmed. Alipay and Wechatpay still works by typing password.

Firware: OP3T-9.0.6-fw-without-ifaa/soter

Rom: nlos-16.0-20200312

PS: It also affects unlocking Alipay using fingerprint which I don't use.
[OnePlus 3 Guides, News, & Discussion] ΦDroid:
In case anyone is wondering:

I installed this with LineageOS 17.1 and nothing appears to be broken.

I do not use AliPay or any of those services so cannot comment on related effects.
[OnePlus 3 Guides, News, & Discussion] metterschling:
Installed it on Lineageos 17.1 with SAR TWRP and it terminated with success. However, when rebooting to system and cross-checking, I recognised that the Blobs were still there. So I edited the updater script to replace /system with /system_root and voila, after flashing the modified package the Blobs are finally gone.

Ideally we'd have a check in the script if we're on SAR (check fstab?) and change the mount point accordingly, I think I've seen that somewhere here in the forums but lost the reference...
[OnePlus 3 Guides, News, & Discussion] GuestK00458:
{Deleted, was sleeping I guess, had already answered my question myself....}
[OnePlus 3 Guides, News, & Discussion] GuestK00458:
FYI, this is how I am removing Soter, Ifaa and Alipay stuff now, which is actually just a one-liner:

# Set root correctly depending on system as root or not
if [ -e "/system_root/system" ]; then
root="/system_root"
else
root="/system"
fi

# Mount firmware_mnt if not mounted already
if ! mountpoint -q "$root/system/vendor/firmware_mnt"; then
mount /dev/block/by-name/modem $root/system/vendor/firmware_mnt
fi

sleep 0.5

# Find and remove alipay, soter and ifaa stuff except boot-org.ifaa.android.manager
find $root/system ! -name "*manager*" -name "*alipay*" -name "*soter*" -name "*ifaa*" -type f -exec rm -f {} + 2>/dev/null

# Unmount firmware_mnt
umount $root/system/vendor/firmware_mnt

So the line which is removing the stuff is just:

find $root/system ! -name "*manager*" -name "*alipay*" -name "*soter*" -name "*ifaa*" -type f -exec rm -f {} + 2>/dev/null
[OnePlus 3 Guides, News, & Discussion] Adam Hui:
Can u pls make it a flashable zip?
[OnePlus 3 Guides, News, & Discussion] GuestK00458:
No, you can just make a bash script which you run after flash from TWRP command line ;)

But if you want, feel free ofcourse :):good:
[OnePlus 3 Guides, News, & Discussion] :
This is a semamtical error:

For non-sar roms root is "/" not "/system". As you striped "/system" from "/system_root/system" you need to strip it for non-sar roms, too:

For non-sar roms "$root/system/vendor/firmware_mnt" expands to "/system/system/vendor/firmware_mnt" which is not ptesent, because it's "/system/vendor/firmware_mnt".

Fix: set root for non-sar roms (else part in the first if clause) to "/".

I'd also suggest to put in some checks with message and exit if a command errors. E.g.: if the mount command fails print something like "mounting fw failed." to the console and exit tje script.

Also keep in mind that a mounted system is a result of a long term bug of twrp (system is always mounted after flashing a zip). If a user decides to run your script in twrp without flashimg a zip before your script will fail, because system isn't mounted. Best practise: unmount system (without error exit - if it's not mounted) and mount it (again).
[OnePlus 3 Guides, News, & Discussion] :
Hi [MENTION=4405529]nvertigo67[/MENTION]; thanks for your input.

I think partly the misunderstanding is because of translation, as you know I am not native english, partly because I just copied in a part of my script.

I know three situations, where with a SAR twrp /system is sometimes mounted as /system_root/system and sometimes as /system/system.

This is what I have tackled in my script, but the description is not right as both situations are for SAR twrp.

The third situation is for non-sar twrp / rom where /system is mounted as /system, the one you are referring to.

In my original script, where I am doing more then only removing the soter/alipay/ifaa stuff, I am using the following, based on the fact that I am always using the latest SAR twrp in combination with Q roms:

# Mount or remount drives read-write
drivelist="
/cache
/data
/sdcard
/system
/system_root
"

for mdrive in $drivelist
do
if mountpoint -q "$mdrive"; then
mount -o remount,rw "$mdrive" 2>/dev/null
else
mount -o rw "$mdrive" 2>/dev/null
fi
done

# Set root correctly depending on system as root or not
if [ -e "/system_root/system" ]; then
root="/system_root"
else
root="/system"
fi

What I could change to be sure all situations are covered is changing the last part into:

# Set root correctly depending on what is mounted
root=""
if [ -e "/system_root/system" ]; then
# SAR mounted as /system_root
root="/system_root/system"
elif [ -e "/system/system" ]; then
# SAR mounted as /system
root="/system/system"
elif [ -e "/system"]; then
# NON-SAR mounted as /system
root="/system"
else
echo "ERROR: It seems /system is not mounted, exiting script"
exit;;
fi

Ofcourse I have to change the rest of the script so that $root/system is only $root ;)

But... good points and appreciated, I will change stuff to make it usable for every twrp / rom combi and post it back later! :good:

With above, the firmware issue you mentioned for non-sar is covered also.
[OnePlus 3 Guides, News, & Discussion] :
But then rename the varible to $system to avoid misunderstandings and to understand your code in two years... ;)