thanks for the guide, how can i easily switch between one gsi rom to another? just flashing img to system via fastbootd would be enough? do i need to wipe anything?
Yes.
Wipe is only needed if you migrate from vanilla to gapps or viceversa. No need if you try same variants. Google play services messes up booting, which is the main reason.
Read prerequisites section from OP for more details.
You can disable it. Should be somewhere
settings > Display > Lockscreen > Always show time & info or phh settings > misc > Force allow AOD
I reflashed the entirety of Stock ROM using Fastboot AGAIN and redid the entire process (including erasing userdata), I don't know what the hell happened but Magisk doesn't complain anymore. I'm really not sure what the hell happened because it should produce the same results.
A few things I noticed:
- No double tap to wake, weird
- My linux partition(Tumbleweed) can't see my device when I connect and try to transfer files, windows can see it no problem
- I think there's something wrong with the notch and status bar. The status bar has the right height, but here they are in the center of the height, which makes the clock really close to the edge. As I remember, on stock it is a little bellow the center so that the bottom of the items align with the bottom edge of the notch.
I think los doesn't include that. Try phh settings > Misc > Double tap to wake
Depends on what DE you're on. On gnome & other environments, try gvfs tools (gvfs-mtp). KDE, try kio. I'm on arch & have no issues with mtp.
Would you mind screenshot it & annotate the positions
I think LOS itself does, you can see mention of it in the requirements list, but not the GSI, or maybe it's an issue with Neternels, idk
I tried, but it didn't work. What's weird is that it always worked before moving to GSI, so again, idk
As far as I can guess it's because Xiaomi put the notch touching the bottom of the navbar, where on most devices it sits in the middle.
Edited everything to be more clear:
I've found some old screenshots so we have a way of comparing how different ROMs worked.
Here's how MIUI 12 worked:
Here's how Alonso's LOS build worked:
And here's how it shows up with Andy's LOS GSI build:
For some reason, Andy's LOS has a slightly different icon placement on the lockscreen, being closer to the bottom edge of the Status Bar, which feels more natural, IMO
There's a difference on Icon size, but the issue is more clear once you consider the Vertical Alignment of those:
Last edited:
Still testing but just a little update.
Had only one random freeze since new overlay. Happened while watching a video on FB. Got back to normal after like 30 seconds so didn't need to restart device. Not sure if it's related to overlay tho. Other than that so far no crashes/freezes.
Also here's memory usage. Android System and OS alone consuming 2.8 GB. Idk if it's normal or not.
Attachments
No it's not normal. Did this issue exist on roms ?
I also don't think this is overlay specific. Phhusson said it's nothing to do with power profiles.
Need more details such as on what GSIs it occured, did you test both custom kernels? Also just try using stock kernel from stock boot & lemme know.
Just flash boot image from your stock mojito firmware. Both kernel & recoveries get replaced btw.
I'm on neternels/phh aosp too, but it's 6 gig variant (with avg memory of 3.1gB). So I'm not sure it's a specific issue with 4 gig variants. Try without overlay too once (you might face some issues like brightness & usage stats).
Also screenshot this page once.
Update:
I think phone just restarted "System UI", coz it went into full brightness for a second and took me to lockscreen. And everything seems normal now(I didn't restart myself)
Memory stats still show 2+ gb but I believe it will gradually go down in next 3 hrs.
Sorry for spamming too much. If you want, I can keep you updated in PM and keep this thread clean.
Attachments
Last edited:
The screenshot I actually wanted to see was Android System (as Android OS is the lesser one in your case)
Caz sometimes dev options mess up graphics allocator, hardware acceleration, etc.
Issue might be something completely different. Did you have developer options enabled? Lemme know if you have the same issue after disabling it.
Caz sometimes dev options mess up graphics allocator, hardware acceleration, etc.
No prob. Spam in this thread as much as you want. I just want all discussions to be public.
Yes, will disable it. Also ejected memory card just incase.
Downgrading firmware could be helpful as well I guess.
Attachments
When did you restart phone last time?
Are you facing any crashes/freeze or anything?
35 hours ago
Nope.
Bear in mind, I flashed the latest Stock Rom through fastboot (mojito_global_images_V13.0.10.0.SKGMIXM_20220829.0000.00_12.0_global), so I might have a different firmware than you.
An easy way to tell was that before flashing the stock rom, my Fastboot screen had the Xiaomi mascot (a white Rabbit), after flashing it was simply the word "FASTBOOT"
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1Andy warned about the QPR2 changes and how he needed more time to update his LineageOS GSI. Might take a while until GSI ROMs stabilizes
-
15
Why should I use a GSI ? Mojito already have custom ROMs ¯\_(ツ)_/¯
Yes. But this thread exists due to the following reasons:
- You don't wanna fear about devs stop shipping updates.
- You don't wanna re-flash your custom recovery / kernel after each update.
- Unlike some ROMs, no clean flashes necessary after you update.
- You don't wanna be a flashoholic / beta tester of a ROM maintainer.
- GSIs are like Linux Distros. Flexible, hasslefree & minimal.
- All GSIs support signature spoofing out of the box.
- ROM updates modify all the partitions (boot, recovery, kernel, system, vendor, etc). A GSI update is just a system partition that updates "only" the system, that runs upon stock firmware.
- You can't flash gapps on vanilla GSIs, as you do on vanilla ROMs. You must use bgS/bgN GSI variants.
- For now, GSIs have to be installed via fastbootd, as recoveries still yet to support logical partitions. So you need computer available when you update or change them.
PREREQUISITES
- Stock ROM (fastboot)
- vbmeta.img (from google)
- Pixel Experience (thanks to ponces)
- More to test from here
INSTALLATION
NOTE:I'm assuming you've already unlocked bootloader, backed up your data & know all the technical consequences of flashing & modding.
- Download / extract all prerequisites in one place.
- From stock firmware, edit
flash_all_except_data_storage.bat/sh& modify last line tofastboot reboot fastboot - Enter fastboot mode
{vol_down+power},connect to PC & flash firmware using above edited script. When device enters fastbootd, from terminal/cmd execute : fastboot erase userdatafastboot flash vbmeta vbmeta.imgfastboot flash system <gsi-file.img>(ignore INVALID SPARSE warning)fastboot reboot& make sure your GSI boots up. Power off & return to fastboot again.fastboot boot <twrp-file.img>, head to Advanced & run flash current TWRP to make recovery persistent across reboots.
UPDATE / DIRTY FLASH HOW ?
fastboot reboot fastbootfastboot flash system <new-gsi.img>& reboot twice
POST CONFIGURATION
- Enable the following Settings > Phh Treble Settings:
- Misc features / Disable audio effects
- IMS features / Install IMS Apk for Qualcomm vendor from notification panel.
MAGISK NOT WORKING ?
In this case, the GSI you selected isn't securized (comes with su bydefault). Through TWRP, do
mount -o rw /dev/block/mapper/system_a /system_rootfrom terminal-
Code:
rm /system_root/system/xbin/su rm /system_root/system/bin/phh-su rm /system_root/system/etc/init/su.rc - Or instead, you can use recovery's file manager to delete the above files. Then reboot.
EXTRAS
My Recommendations for great experience:
- SPKM to set
GPU > GPU Governor > Performance(fixes UI lags) - Lineage Dialer for built-in call recording (push into
/product/priv-app/Dialer/Dialer.apk). - ANXCam for MIUI camera's post processing.
- GCam for google camera's post processing.
- Aurora Store / Droid for microg users.
- Migrate to backup / restore user apps & data, incase you lose your setup.
3Here's the report for the current GSI development state. This is to keep this thread alive.
- Phhusson now moved from his personal builds to CI/CD builds (testing, automated) which is now called TrebleDroid (AOSP-TD).
- But he still hasn't decided to ship secure builds yet (which help pass CTS & magisk compatibility)
- Lot of AOSP-TD based builds have been released by many developers/builders, which some also happened to have secure builds. Links are in the OP.
- A13 forks are still in development stage. So you might experience couple of bugs here & there.
- As of now, the last stable A12 builds held to November sec patch. Beware if you still on Nov patch, since it has a serious security vulnerability (CVE-2022-20465) that allows anyone to unlock your encrypted device through sim PUK reset, which has been patched on December sec patch.
- Andy's maintaining his own phh treble patchset builds which he calls LineageOS Light. It might or might not be dirty flashable over other TD based builds.
- The current overlay state is the same as of last year. If anyone have any requests regarding overlay modification, plz do.
android_13.0.0_r14 ci-20221219(system-td-arm64-ab-vndklite-vanilla), securized, magisk rooted, microg moduled & passing safety net via kdrag0n fix & redfin props.
MERRY JINGLE CHRISTMAS
3
I don't really care. Discuss anything mate. This thread is all about gsi support for community.it is okay for us to give review about the GSI that we have been tested ? or better on the other thread ? asking for an opinion here
The more you guys talk, the more better.
(just dont private msg. I want all discussions to be public
)3
If you want to gain more space (≈ 200mb) in system you can delete 2 folders safely without problems :
/system/system_ext/apex/com.android.vndk.v28/
and
/system/system_ext/apex/com.android.vndk.v29/
Already did it in DSSI builds without issues.
