yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] Namelesswonder:
They are all there.

[nameless@5900x:/tmp/cheetah-td1a.220804.031]$ mkdir vendor
[nameless@5900x:/tmp/cheetah-td1a.220804.031]$ sudo mount -o ro vendor.img vendor
[nameless@5900x:/tmp/cheetah-td1a.220804.031]$ file vendor/lib/libril.so
vendor/lib/libril.so: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked,BuildID[md5/uuid]=4dc2e1078c37743b14f468897322e46f, stripped
[nameless@5900x:/tmp/cheetah-td1a.220804.031]$ file vendor/lib64/libril.so
vendor/lib64/libril.so: ELF 64-bit LSB shared object, ARM aarch64, version 1 (SYSV), dynamically linked, BuildID[md5/uuid]=03597a2f2c3f0d3319f467b434d84957, stripped

Zygote32 is even still there.

[nameless@5900x:/tmp/cheetah-td1a.220804.031]$ file system/system/bin/app_process64
system/system/bin/app_process64: ELF 64-bit LSB pie executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /system/bin/linker64, BuildID[md5/uuid]=6f97a590777bd06f31784c7272763a35,stripped
[nameless@5900x:/tmp/cheetah-td1a.220804.031]$ file system/system/bin/app_process32
system/system/bin/app_process32: ELF 32-bit LSB pie executable, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /system/bin/linker, BuildID[md5/uuid]=8911da270a05209e7fd1978c74dd3330, stripped

Google did the laziest thing possible and simply just changed ro.zygote to zygote64.

During init, inside /system/etc/init/hw/init.rc it will import another init.rc, but based on what ro.zygote contains.

On the Pixel 7 it will import /system/etc/init/hw/init.zygote64.rc, which only launches app_process64.

On the Pixel 6 (and all other multilib phones) ro.zygote is set to zygote64_32 which means it will import /system/etc/init/hw/init.zygote64_32.rc which then starts app_process64 as the primary zygote and app_process32 as the secondary zygote.

I don't know if the changes are done any further, I'm currently in the middle of doing strenuous debugging on trying to find out why bootloader unlocked Pixel 7s keep on failing CTS profile checks even when hiding root and unlock status.

If they didn't make any changes to the package manager then this will literally be the easiest revert, just set ro.zygote to zygote64_32 before the init scripts are ran.

This is honestly pathetic on Google's part.
[Google Pixel 7 Pro] manueltimz:
my whatsapp mods are all 32bit. It sucks.

Now I had to root to use OG whatsapp +tweaks
[Google Pixel 7 Pro] netgar:
Why do you need to root it to install OG Whatsapp?
[Google Pixel 7 Pro] manueltimz:
Not to install but to tweak the app with xposed tweaks
[Google Pixel 7 Pro] Ghisy:
Wait, does this mean we can potentially do something to allow 32-bit apps to run?
[Google Pixel 7 Pro] Namelesswonder:
I'm running out of time today and I'll be busy over the weekend, I might be able to get something out if I sacrifice some sleep.

It seems like it should be possible.

I think all that's going to be needed is a Magisk module that overwrites ro.zygote before the processes are started, assuming that Magisk is capable of setting them that early. I believe it should be, Magisk allows you to set properties very early in boot.
[Google Pixel 7 Pro] Namelesswonder:
Didn't sleep, I have gotten closer, but Magisk modules aren't going to be the solution.

The earliest Magisk allows you to modify properties is after the post-fs-data trigger, which is well inside the init.rc. This is problematic because the property needs to be set before init.rc is even read.

Using a Magisk module to replace the init.rc with something else also isn't possible, since Magisk doesn't setup the overlays until well into the boot process.

This replacing is necessary because init.zygote64_32.rc actually has the secondary zygote service disabled, so the file needs to be modified to enable it, or with control over init.rc just stuffing a custom zygote service into it.

I don't think slipstreaming a modified init.rc and init.zygote64_32.rc into the ramdisk in init_boot will work since they would be overwritten once the system partition mounts. Could just modify the system partition, but that'll be for another day.
[Google Pixel 7 Pro] Ghisy:
Wow. Thanks for trying!

I'm not familiar with any of this because I'm not a dev. But isn't the system partition read-only nowadays on Android, even with root? Could this be achieved with a systemless mod?
[Google Pixel 7 Pro] twotonekarma:
Thanks, I have several running including StbEmuPro, a set top box emulator that I use for TV on the go, very frustrating.
[Google Pixel 7 Pro] Renate:
Just polishing the cannon ball.

Versions-1.0.apk now support all ABIs, including obsolete.

The main list shows 32/64/+ if there are other libs included.

32 only refers to armeabi-v7a, 64 only refers to arm64-v8a, "+" is anything else.

Grab a new version at https://xdaforums.com/t/32-bit-arm-application-checker.4505193/post-87572575
[Google Pixel 7 Pro] diesteldorf:
Thanks for designing the app. I was disappointed to find out Tubemate 3.9 is 32 bit only. Hopefully, someone will update or find a workaround in the future.
[Google Pixel 7 Pro] xgerryx:
Is there a 64 bit version of a hacked spotify app? Not asking for a link, but if it exists. Only problematic ones for me seem to be Instander and Spotify. The Vanced stuff is 64 which is good, as is Adaway.
[Google Pixel 7 Pro] whatsisnametake2:
yeah hanging out for instander here too. someone on reddit said it's possible to decompile a 32bit app and make it 64 (if you know what you're doing lol). any truth in that?
[Google Pixel 7 Pro] Ghisy:
Hmmm, that sounds way too easy to be true but I'm ready to be proven wrong!
[Google Pixel 7 Pro] roirraW "edor" ehT:
That is generally true about any program. The key is if you know what you're doing - so it might take more effort than it sounds like, and not necessarily be simple in the end.
[Google Pixel 7 Pro] Samuel Holland:
I seen an article saying it was just a flag that was keeping us from installing 32-bit apps. Maybe soon we could figure a way to set it.

The Pixel 7 tests out 64-bit-only Android, can’t run 32-bit apps

64-bit only Android promises better performance and security, if we can get there.

arstechnica.com
[Google Pixel 7 Pro] Ghisy:
Good find! So the P7P isn't using a 64-bit only OS after all.

So, can we set that zygote_force_64 flag to false instead of true somehow? @Namelesswonder

(I might be saying something completely dumb here but I'm not a developer so sorry in advance if I did 😅)
[Google Pixel 7 Pro] Namelesswonder:
In theory.

Today I had some time so I spent it on modifying the images to enable the secondary zygote service in init.zygote64_32.rc and changed ro.zygote to zygote64_32.

Problem being that it would just hang on boot. I don't know if that is due to dm-verity and verified boot, or because I haven't updated the super partition when flashing my modified system and vendor images.

Well since I'm going to have to wipe to clear the verity failure, I might as well disable verity and verification and test again.

Edit: Going to need to make a modified super partition. Ugh I wish I had more time to do this.
[Google Pixel 7 Pro] whatsisnametake2:
thanks for your efforts with this. getting 32 bit working would be a big plus!
[Google Pixel 7 Pro] Nekromantik:
according to that script i got no 32 bit apps lol

but still got random issues like some apps have no notification and by default ir sets no notifications in app permissions
[Google Pixel 7 Pro] Ghisy:
Alright, I've replaced or uninstalled these apps, including the Amazon App Store because I realized I had no interesting apps installed from there.

Still no news about the Instagram mod from the dev... The official Insta is ridiculous (ads everywhere). I tried the mobile version with an ad blocker, it's decent but not as good as the app.

I don't know what to do. I don't wanna wait forever to switch to my 7 Pro! :(
[Google Pixel 7 Pro] rester555:
Wouldn't this be minimized by AdAway inside the app?
[Google Pixel 7 Pro] Ghisy:
If I remember correctly, it doesn't really work. They have ads within stories and sponsored posts on your timeline. I don't think any ad blocker is picking these up unfortunately :/
[Google Pixel 7 Pro] rester555:
This is the same with Twitter.
[Google Pixel 7 Pro] whatsisnametake2:
adaway doesn't work on instagram official app. I find it pretty much unuseable. instagram official i mean not adaway.
[Google Pixel 7 Pro] rester555:
Makes sense since most companies have wised up to OS ad blocking and DNS blocking.
[Google Pixel 7 Pro] whatsisnametake2:
instander is by far and away my favourite choice for insta. mainly because its default theme is dark and not amoled black, which I can't stand.
[Google Pixel 7 Pro] Ghisy:
Agreed about the official Insta. I don't know how people can tolerate so much cr*p in their apps?!

Like I said earlier, an alternative is the mobile website with an ad-blocker. It does the job but it's not great. I could use that instead but I don't know.
[Google Pixel 7 Pro] narcisrm:
the_dise, the dev of Instander, said on Reddit that he already started working on the 64 bit version, and he expects to have it working before 10th of November. source

So we just need to wait a little bit longer.
[Google Pixel 7 Pro] jucin:
I used instander too and tryied the Others even if they where based Upon the New Versions they dont Work this is very sad and the dev of Instander has paused the Development
[Google Pixel 7 Pro] whatsisnametake2:
hurrah! everyone go and offer encouragement on that reddit post.
[Google Pixel 7 Pro] GrandMstrBud:
I'm sure others are wondering this also, I'm curious if there is a way to somehow install a 32bit application maybe if rooted? I use an older modded Kik because I can't stand the adds and also an app called Gallery KK. I don't anticipate then being updated but I use them both daily. Maybe there's alternatives but I can't deal with adds on Kik that's for sure. I wish they have you an option to buy an add free one. Anyway, hopefully there is a way or this will not be my new phone.
[Google Pixel 7 Pro] Samuel Holland:
Hopefully soon, maybe someone w/ the skills will make a magisk module,or Xposed, that could add the libraries needed for our devices, and to be able to once again install 32bit applications.
[Google Pixel 7 Pro] Namelesswonder:
These steps are currently only for the November update, if you are on QPR1 you will have to wait until later for my tutorial on that.​

A wipe is required. It appears that for some reason the 32-bit libraries inside APEXs aren't loaded, I think the libraries that are required get put into a list on first boot. If first boot was 64-bit only, then the 32-bit libraries can't be loaded. There might be some way around this, but for now the easiest solution is to just wipe the phone and first boot with the 32-bit patch.

The work for this is thanks to ThomasKing2014.​

https://github.com/ThomasKing2014/Pixel7_32bit_helper

Directly download Magisk-v25.2_patched.apk from here

On your phone uninstall the Magisk app and then reboot to the bootloader. Do not use the uninstall Magisk button from within the app, simply just uninstall the app itself.

Pull the stock init_boot.img from image.zip inside the firmware image for your version.

Reboot your phone into the bootloader.

Flash the stock init_boot.img and then boot into Android.

Install the patched Magisk v25.2 APK from the repository.

Copy over the stock init_boot.img to your phone and patch it in the Magisk app.

Copy the patched Magisk init_boot.img over to your computer

Reboot your phone into the bootloader.

Flash and wipe via fastboot --skip-reboot -w update image.zip

Wait for it to finish, then reboot back into the bootloader either on the device or with fastboot reboot bootloader

Flash the patched Magisk init_boot.img

Go through setup and do not open the Magisk stub and do not download Magisk from within it, instead install the patched Magisk v25.2 APK.

These steps could be followed on QPR1, however Zygisk will not function and the zygote processes will keep on crashing resulting in a stuck boot. I'll have the steps up at some point soon once I can verify that another Magisk fork is fully functional. For now here is a sneak preview on QPR1 with Zygisk (maru).

Spoiler content hidden.
[Google Pixel 7 Pro] Ghisy:
@Namelesswonder, that's great news!! However, I don't wanna wipe in order to use 32 bit apps. I only need it for an Instagram mod, which I'm using on my work phone for now.

But as soon as this doesn't require a wipe, I'll probably try it! Thanks :)
[Moto G 5G Questions & Answers] mathew2214:
the website says i am ineligible.

if it is straight-up impossible, what model of 5G ace do we know for a fact IS unlockable?

i intend to use with T-Mobile in the US.
[Moto G 5G Questions & Answers] RETIEF:
Not AT&T, not Verizon. Not a used phone with a relocked bootloader.
[Moto G 5G Questions & Answers] mathew2214:
i beleive it is the ATT varient of the phone, but i am using a TMO sim card with it and it works just fine. no carrier lock here.
[Moto G 5G Questions & Answers] RETIEF:
You cannot unlock the bootloader on the AT&T variant.
[Moto G 5G Questions & Answers] mathew2214:
is there a list of varients and model numbers we know for certain CAN be unlcoked?
[Moto G 5G Questions & Answers] RETIEF:
I have read of a large number

I have RETUS. It is unlocked. This I know for certain. I can only know for certain what I have experienced.
[Xiaomi Redmi 7 ROMs, Kernels, Recoveries, & Other ] melles.android:
SCREENSHOT

View attachment 5733919View attachment 5733921View attachment 5733923View attachment 5733925View attachment 5733927
[Xiaomi Redmi 7 ROMs, Kernels, Recoveries, & Other ] melles.android:
UPDATE

NIGHTLY

Changelogs :

/ 2022-10-15
• Update the screen density
• Set device specific fstab
• Fixed interface display
• Some features of OFOX are enabled

Discuss device's, feature's, or just chat about everything.

CHAT | NEWS​
[Xiaomi Redmi 7 ROMs, Kernels, Recoveries, & Other ] melles.android:
UPDATE

NIGHTLY

Changelogs :

/ 2022-10-15
• Use fscrypt policy v2
• vendorsetup.sh: Overhaul script
• Delete AROMAFM
• Update the platform version, for Android 13 decryption

Discuss device's, feature's, or just chat about everything.

CHAT | NEWS​
[Xiaomi Redmi 7 ROMs, Kernels, Recoveries, & Other ] melles.android:
UPDATE

RELEASE-UNOFFICIAL

Changelogs :

/ 2022-10-25
• Use lzma compression (this is needed)
• Update the cpu prop
• Enable adb
• Disable FDE, and provide warning on any attempt to enable it
• Fix target device list (onc, onclite)
• Delete INITD addon
- Causes bootloops sometimes
• Also include NTFS driver
• Full Android 13 decryption fixes

Discuss device's, feature's, or just chat about everything.

CHAT | NEWS​
[Xiaomi Redmi 7 ROMs, Kernels, Recoveries, & Other ] melles.android:
Don't work MTP for some redmi y3 (onc) revision FIXED NOW
[Xiaomi Redmi 7 ROMs, Kernels, Recoveries, & Other ] melles.android:
UPDATE

UNOFFICIAL

Changelogs :

/ 2022-11-04
• Bump up FOX_VERSION to R11.1_6
• Rewrite and move *.fstab to root directory
• Update twrp.fstab for correct work with the /data partition (Fix format /data)

Discuss device's, feature's, or just chat about everything.

CHAT | NEWS​
[Xiaomi Redmi 7 ROMs, Kernels, Recoveries, & Other ] melles.android:
UPDATE

OFFICIAL

Changelogs :

/ 2022-11-12
• Initial R11.1 beta release
• Set original screen density
• Some mount point hide to "Show advanced partitions to backup" option
• Changed fscrypt policies flag to v1 - fixed backup and restore /data
• Fixed Android 12/13 decryption
• Added OEM otacert location
• Migrate to Android 12.1 source

Discuss device's, feature's, or just chat about everything.

CHAT | NEWS​
[Xiaomi Redmi 7 ROMs, Kernels, Recoveries, & Other ] Hinokami Enbu:
So good work, sar! All functions working great! I advise others!
[Xiaomi Redmi 7 ROMs, Kernels, Recoveries, & Other ] m01775537773:
All works fine.

There is no bugs which i faced.

Everyone, who has "onc/onclite" can flash this ofox zip without facing any problem.
[Xiaomi Redmi 7 ROMs, Kernels, Recoveries, & Other ] m01775537773:
Me also, recommended it to use other.
[Xiaomi Redmi 7 ROMs, Kernels, Recoveries, & Other ] m01775537773:
All works fine...💌💌💌🥰💌💌💌
[Xiaomi Redmi 7 ROMs, Kernels, Recoveries, & Other ] melles.android:
Nice
[Xiaomi Redmi 7 ROMs, Kernels, Recoveries, & Other ] melles.android:
UPDATE

OFFICIAL || BETA

Changelogs :

/ 2022-11-12
• Initial R11.1 beta release
• Set original screen density
• Some mount point hide to "Show advanced partitions to backup" option
• Changed fscrypt policies flag to v1 - fixed backup and restore /data
• Fixed Android 12/13 decryption
• Added OEM otacert location
• Migrate to Android 12.1 source

Discuss device's, feature's, or just chat about everything.

CHAT | NEWS​
[Xiaomi Redmi 7 ROMs, Kernels, Recoveries, & Other ] melles.android:
UPDATE

OFFICIAL || BETA

Changelogs :

/ 2023-01-28
• Update to the latest upstream source
• Set 4th partition as OFOX alt block device for external storages
• Add "printk.devkmsg=on" to kernel commandline
• Opt out of the entire MiUi OTA menu

Discuss device's, feature's, or just chat about everything.

CHAT | NEWS​
[Xiaomi Redmi 7 ROMs, Kernels, Recoveries, & Other ] Daflow77:
Hi can someone please point me to the right point is there a orangefox A12 recovery for Moto g stylus 5G 2021 if there is plz link me 🙏🙏🙏
[Xiaomi Redmi 7 ROMs, Kernels, Recoveries, & Other ] melles.android:
UPDATE

OFFICIAL || BETA

Changelogs :

/ 2023-10-25
• Update to the latest upstream source
• Introduce and full-fix charger_led daemon
• Added App Manager.
• Rewrite the OrangeFox-specific build vars
• Allow overriding TW_USE_FSCRYPT_POLICY

Discuss device's, feature's, or just chat about everything.

CHAT | NEWS​
[Xiaomi Redmi 7 ROMs, Kernels, Recoveries, & Other ] melles.android:
UPDATE

OFFICIAL || BETA

Changelogs :

/ 2024-06-15
• Set a specific starting point for the core to load faster (0x80000000).
• Named the core file (Image.gz-dtb) and made sure it's the right size (2048 pages).
• Checked if certain necessary files are present before doing anything.
• Fixed problems that happened after updating a part of the system.
• Made sure everything works smoothly with standard settings.
• Updated how the system handles external devices like USB drives for better compatibility.
• Managed how the system uses power to save energy and improve performance.
• Ensured the system works well when using an external memory card.
• Improved the overall stability and performance of the system's important functions.

Discuss device's, feature's, or just chat about everything.

DISCORD CRAFTROM | NEWS​
[General Topics] lawny:
Hello, I own a HTC Neo with WM6.1. When I connect to AC I would like that the Screen switchs to Landscape Mode and back zo Portait when I unplug the Device form AC.

Does someone know how to configure that ? Greetings from Berlin, Lawny.
[Google Pixel 7] Jonnyswboy:
[Re-posting this here after I confirmed it work with the Pixel 7 as well]

To be clear, this is not the same as the developer option.

Enter the following ADB commands (you can also modify these values using the app SetEdit in the Play Store, no root required):

adb shell settings put system peak_refresh_rate 24.0
adb shell settings put system min_refresh_rate 24.0

The reason this works is because by assigning it a random and unsupported value, we are [kind of] breaking the refresh rate. As a result of which, the OS won’t be able to adjust this rate, and hence stick with the maximum available rate.
[Google Pixel 7] bobbyphoenix:
You can also enable the "Force Refresh Rate" in Developer Options. I tried it, but don't really care to keep DO enabled. Also you can enable "Show Refresh Rate" in DO. I did that also, and realized that with keeping it at 60(normal), and keeping "Smooth Display" on, the phone kicks it into 90 the moment you touch the screen. So forcing 90 100% of the time is a waste of battery in my opinion. Only when the phone is not touched for three seconds does it drop back to 60. Otherwise any use of the phone it stays at 90 normally.
[Google Pixel 7] Jonnyswboy:
Started my day today at 100% 7AM and am at 52% 11PM so I am happy. I can't stand Snapchat being 60.
[Google Pixel 7] bobbyphoenix:
Update on my observation. It may be a placebo effect, but knowing that it changes makes me see a slight stutter. Forcing 90 at all times "seems" much smoother, so I'm leaving it on also. Cheers!
[Google Pixel 7] Vio281:
this trick is irrelevant, you can do it in developer tool....
[Google Pixel 7] Jonnyswboy:
The developer option does not force in many cases. In Snapchat when you swipe to the left and the camera is still initialized it stays at 60hz. Once the camera is not initialized it goes to 90hz. I believe it is the same in Instagram.
[Google Pixel 7] lukeah02:
Has a fix been found for this cause I found this doesn't seem to be an issue at all on iPhone but incredibly frustrating on Android especially Snapchat.
[Google Pixel 7] Jonnyswboy:
My fix is in the original post. Has been working great for me.
[Google Pixel 7] heisenberg17:
Been using this for a while, but let's saym hypothetically if I wanted to restore it to default settings, which values do I need to put on the adb commands?
[Google Pixel 7] engadgetnerd:
If I do those ADB commands and decide I want to not have them anymore, how would I revert?
[Google Pixel 7] xduox:
To get your default values before doing the change, use:

adb shell settings get system peak_refresh_rate

and

adb shell settings get system min_refresh_rate

For me on stock firmware unrooted, peak_refresh_rate = null, and min_refresh_rate = 0.

Thanks for your fix! I was wondering why some apps were low hz.
[Google Pixel 7] xduox:
Get default values before doing the change:

adb shell settings get system peak_refresh_rate

adb shell settings get system min_refresh_rate

Default values (stock unrooted):

peak_refresh_rate = null

min_refresh_rate = 0

Thanks for your fix! I was wondering why some apps were low hz.
[Google Pixel 7] MrPeaski:
I've just got a Pixel 7 and thought I'd try this.

Observations, stock not rooted etc

Peak refresh rate = 90

min refresh rate = null

Applied the settings in post 1

and both come back as 24 when 'getting' peak/min rates from adb.

However, turning on show refresh rate in developer options show 90 when using the screen, but drops back to 60 if you leave it for a few seconds.

it only stays at 90 if you turn on Force peak refresh rate in Developer options.

This is only so far when messing about on the home screen, not tested in any apps etc, but it looks like these settings can't be fixed by setting a random number as post 1 implies
[Google Pixel 7] MrPeaski:
As a quick follow up, setting both peak and min to 90 does fix them, but seems a bit pointless as you can turn it on/off within developer settings.

This is not a bash at the OP, but maybe recent update have taken this 'feature' out
[Google Pixel 7] Pixel86:
Does this survive a reboot?
[Google Pixel 7] Shinika:
Though the above might be a possible solution, here is the proper way to revert using ADB:

adb shell settings reset system peak_refresh_rate

To dig further into the possible System settings (amazing topic ^^)

adb shell settings list system
[Google Pixel 7] Jonnyswboy:
You can't force peak refresh rate in developer settings. It will still drop at times, like in Snapchat when the camera is accessed, on Google Maps, etc. It still automatically drops to 60hz despite the developer option being enabled.

And after updating to the Android 14 beta this workaround does not work anymore, and I am very frustrated that I am unable to truly force 90hz anymore.
[Nexus 5 Q&A, Help & Troubleshooting] caofedo:
Im using an old nexus 5 and im not really into this stuff, can anyone tell me if its still possible to root and if so how?

Thanks
[Sony Xperia 1 III] tiinpii:
Hello Every one , mine has Xperia 1 iii bc62 ariginal firmware :61.0.A.11.23 release-keys, when i flashed with lasted firmware 61.1a.11.36 after completed with the newfasher tool i unplug the device press power button but it boot loop several time and show error "Your device is corrupt it cant be trusted and will not boot"

I try with different firmware but get no luck . can some one experient help me with that. thanks