yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
phh doesnt have A13 gsi's yet. i dont. care about the latest android version nor the features. but the stability. A13 gsi's are way ahead in smoothness.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Honestly, I haven't seen much of a difference between PE 12/13 when it comes to smoothness or battery life. But one thing android 13 has that I really appreciate, is that notifications are now a permission, and disabled by default for user apps. I always hated it when games like call of duty mobile would pester me with notifications to come and play, then having to turn off the notifications for it. Some of my other apps send unwanted notifications too.
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
yeah but i couldnt update to latest A12.1 build for PE since i have a mediatek device. it rebooted on the splash screen
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
finally ricedroid gsi has popped up. i am gonna go give it a try. i hope it works.
[Treble-Enabled Device Development A/AB ROMS] rafik25:
My LG tws works only with spark os A13 gsi.....
[Treble-Enabled Device Development A/AB ROMS] T_Tank:
I will say with my brief time with pe android 13 I think Google made scaling better on smaller devices just notice how more stuff is cramped or cut off on v414 compared to the latest 13 alpha
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
You want better scaling on smaller devices, I want to see a GSI that has more tablet-oriented optimizations. So far I've found none, they all act as if the device is nothing more than a phone with a huge screen. It's evident to me, when things like the lockscreen stubbornly display in portrait mode, instead of matching the landscape orientation I use it in most of the time.

I can't tell any difference between PE12/13 in this regard. They say Android 13 is supposed to have more tablet optimizations, but I'm not seeing it.
[Treble-Enabled Device Development A/AB ROMS] T_Tank:
Those optimizations might not be baked in yet with PE but there may be still a way in adb to enable screen rotation for the lock screen.

And better screen scaling should help with big and small screens I've just noticed it more on my jelly-2 between 12 and 13
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Right now I'm using AOSPMods with Magisk and LSPosed. It has an option that force allows the lockscreen to rotate into whatever orientation is detected by the device sensors.

I just feel like I shouldn't have to use a mod to correct something which should be in a GSI dy default. Mods can bring unintended bugs. I try to avoid using them if there's a native solution.
[Treble-Enabled Device Development A/AB ROMS] Finnit0:
I am using my Poco M4 Pro 4G with this rom and it seems to work fine. Thank you! One thing I noticed is that my refresh rate is at 60 Hz, anyway to change it to 90 Hz?
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Check Treble menu in settings. There is an option in there to force refresh rate. But first, you must be sure that your device's hardware supports the Hz you want to set, or else it won't work. My Tab supports up to 120Hz. But I think the default Hz of this GSI is 60.

There is another option in Developer settings that you can use to confirm that your Hz change is really working. I forget what it's called, you'll have to check yourself.
[Treble-Enabled Device Development A/AB ROMS] 73sydney:
If you want more fun, have a look at

GitHub - Firefds/FirefdsKit: Xposed module for Samsung devices (Android 6, 7, 8, 9, 10, 11, 12, 13, 14)

Xposed module for Samsung devices (Android 6, 7, 8, 9, 10, 11, 12, 13, 14) - Firefds/FirefdsKit

github.com

one setting allows you to fingerpritn unlock on reboot/...worth installing for that alone

my next fave lsposed module is:

GitHub - tianma8023/XposedSmsCode: :lollipop: An Xposed Module which can recognize, parse verification code and copy it to clipboard when a new message arrives . / 识别短信验证码的Xposed模块，并将验证码拷贝到剪切板。

:lollipop: An Xposed Module which can recognize, parse verification code and copy it to clipboard when a new message arrives . / 识别短信验证码的Xposed模块，并将验证码拷贝到剪切板。 - tianma8023/XposedSmsCode

github.com
[Treble-Enabled Device Development A/AB ROMS] Finnit0:
Ahh didn't think it was forece fps. I was able to focrce 90 Hz refresh rate. Thank you.
[Treble-Enabled Device Development A/AB ROMS] Sentyreon:
Hello. I have a Lenovo X606X, it's the same tablet, only with LTE. Do you think I will have problems with PE? I'm going to just install TWRP and install this firmware.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
It seems like they're probably in the same model family, there are likely only very minor differences between yours and his/hers (in terms of hardware). It will most likely work for you too.

4gb isn't a lot of ram though, you will probably get better performance from a leaner GSI like the ones released by @phhusson. Just pick the one that has Google apps built in, if you'll be using them. PE is mostly based on his source code anyway.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I just noticed that fingerprint reader isn't working on my Tab S7+ running PE13. For awhile I had only set a PIN lock, until just now when wanting to add fingers. My tab does have a reader, but it's built into the screen.

The enrollment wizard just assumed there is a hardware reader on the back of my device (there isn't).

The reader also didn't work in PE 11, but it did work in the PE 12 releases I tried. 13 kind of feels like a step back in this regard. But since it's an alpha, I'll just ignore this for now, I'm sure it'll get fixed eventually.
[Treble-Enabled Device Development A/AB ROMS] scottyrick2:
You should be fine. Let the new firmware settle in for 30-60 minutes before starting to use it.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
No need for "settling in', that's a load of horse****. Esp not 30-60 mins like you've said. It should run smooth right after the very first clean boot. It will take a few mins for the system processes running in the background to "calm down" but that's the worst of it. I've been flashing roms ever since the earliest days of android. And I've seen so many devs recommending a settling in period. But in my exp, it's just not necessary. It's kind of like an urban legend, believed by many but not necessarily true.

And these days Android devices are so powerful that any settling in time is reduced to a bare minimum. Back in the days when mobile devices had relatively weak specs, settling in had a bit more truth to it.
[Treble-Enabled Device Development A/AB ROMS] 73sydney:
Actually there is a grain of truth in it, there are deferred jobs etc after a clean flash

You can "speed" part of the process up, if you like by opening a terminal and doing:

su -c "cmd package bg-dexopt-job"
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
While that may be true, I've never felt the need to adhere to any "settling in" rituals, like "don't touch for 10 mins" or whatever. I tried that a few times, it didn't seem to make any difference to me. So I stopped doing it.

I'm fully aware that android's dexopt process runs background jobs for apps. It also does this when you install new apps. It's not a 1 time thing that happens after a clean boot only.

I prefer to not intervene in regards to whatever processes android needs to run after a clean ROM boot. Best to just let the system handle it while using it normally.

I've also seen a lot of users complaint about **** battery life after running a ROM for just a few hours or a day. The best battery life in a ROM will be achieved after around 5-7 days, on average. So sit back, be patient, battery life will improve. Assuming that you use it normally and not run things that are known to cause high drain. Or install things like malware/adware/spyware/etc.
[Treble-Enabled Device Development A/AB ROMS] Joran01:
Latest A13 build doesn't boot on my OG Pixel 1. Latest A12 build does boot perfectly
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I find it funny that PE 13 doesn't boot for you on a Pixel. Out of all the devices that should work without issues, Pixels should def be supported 100%.
[Treble-Enabled Device Development A/AB ROMS] 73sydney:
yeah, that sort of stuff is horse output

Anyone who owns a Watch 4/5 knows to not whinge about battery life until at least 3 days after you get one, though reddit is daily getting a post from newbs titled "is this for real?"

My personal favourite is the numpties who turn up every couple of weeks posting "how od i remove this scratch" <insert picture of Watch with scratched screen or frame>....it still boggles my mind (EVEN after seeing this a millionty times by now" that people will spend $$$$$$ on a smart watch but not $3 on Ebay/Ali Express/Amazon to buy a $3 TPU full cover for it....more signs humanity is in decline....im surprsied some people of later generations can tie their own laces. We have gone backwards as a species
[Treble-Enabled Device Development A/AB ROMS] Joran01:
It's an OG Pixel that only officially supports up to Android 10 so it's expected that an unsupported Android version doesn't boot on the Pixel. It's already an amazing achievement that Android 12 runs without any issues on the OG Pixel (that was released in 2016 over 6 years old now).
[Treble-Enabled Device Development A/AB ROMS] BuyuluMahmut:
As a Mi Note 10 user I cant boot with A13 build. Is that about my TWRP version or build has problems with it?
[Treble-Enabled Device Development A/AB ROMS] Sentyreon:
I installed latest Pixel Experience 13.0 v2022.10.17 and got bootloop (infinity loading) Can you tell me more about how you installed this firmware and which version you chose? (Default or Slim) And have you updated to the latest version? I just wiped DATA, Dalvik and cache via TWRP and flash PE via Platfrom-tools
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Bootloop? Or just infinite loading screen (Google logo)? If you're using TWRP, try formatting data, instead of wiping. Wiping doesn't remove encryption, formatting does.
[Treble-Enabled Device Development A/AB ROMS] Sentyreon:
Yeah, just infinite loading screen (firmvare logo). I formatted DATA via TWRP and it did not help. Just now tried to flash SparkOS GSI 13.1(latest update) and got the same problem. I understand that I can try to install the stable A12.1 from phhusson as you advised me, but I want to run A13, if it possible :)
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
If they're not booting after formatting data and wiping cache, then 12 may be your only choice.

Have you also disabled AVB/dm-verity in your vbmeta partition? This can be done via fastboot.

Also make sure you're using the stock unmodified boot.img from your firmware.

As for flashing the GSI image, you don't need fastboot for that. Since you have TWRP, you can just use the dd command if it's a raw image, or simg2img if the image is sparse.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Here is a good test, for troubleshooting purposes:

Do the exact same steps you have already done, but with an A12 GSI. Don't do anything different. Try more than one GSI, if needed. If it boots, then your issue is down to the A13 gsi just not being compatible for your device yet.

if it too doesn't boot, then some other unknown factor is in play.
[Treble-Enabled Device Development A/AB ROMS] Sentyreon:
Yeah, A12 GSI works fine. So I have to wait for more stable versions of A13. Thank You!
[Treble-Enabled Device Development A/AB ROMS] nietschu:
where’s that?
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
here is a list of gsi's
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
for me using an galaxy A32 i had to downgrade my firmware to android 11 (one ui 3.1). then flashed any A13 gsi on top. works fine. one ui 4.1 some dont boot at all and some get stuck at boot screen or reboot immediately at splash screen. bur A11 firmware works fine
[Treble-Enabled Device Development A/AB ROMS] nietschu:
thanks! you’re a lifesaver.
[Treble-Enabled Device Development A/AB ROMS] 73sydney:
Most A13 GSI ive tried on my S20+ 5G work, in fact theres only one major reason im not using one full time, none enable the fingerprint reader, and thats a non-optional thing in my life :)

CherishOS takes the phh level of customisations a step further in case anyone hasnt tried that GSI

But when in doubt i always come back to PE, used across several devices over years now...
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I'm just using the latest A12 stock firmware for my device. On top of that I flashed Magisk, TWRP, a neutralized vbmeta, and the GSI img. PE13 works fine here, but with bugs. So far it's nothing too serious, the ROM is very smooth and stable. No system crashes as of yet.I 've also flashed Multi Disabler, to disable forced data encryption. Samsung hasn't released A13 firmware for my device yet.
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
same here but on A12 all gsi's just have infinite boot screens
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
all A13 gsi's*
[Treble-Enabled Device Development A/AB ROMS] rafik25:
last release dont boot for me....
[Treble-Enabled Device Development A/AB ROMS] DocMAX:
Well, working on Jelly2. Don't know about other devices.
[Treble-Enabled Device Development A/AB ROMS] vewu101:
Thanks for the PE 13 gsi, it has been working well so far (on a Nokia 3.2)
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Also working fine here. I'd say PE13 is an improvement over PE12 in terms of BT. On PE12, my speaker acted wonky and would disconnect frequently, sometimes requiring it to be hard resetted. I thought the speaker must be going bad, but I've had no issues with it on PE13.

I also haven't had to change any BT settings in the Treble menu, it just works.

I have yet to test file transfer over BT, I had issues with that in other GSIs. If it doesn't work then it's not a huge deal to me, since copying large files over BT takes an eternity. It's only good for small stuff.
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
for me BT is behaving terribly and is the only reason i am not switching to it. bluetooth just crashes once i am listening to some audio and then I let pause the audio and let it sit idle. bluetooth restarts immediately and then connects again. otherwise PE 13 is amazing. i loved it way smoother then any of the other gsi's.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
What BT audio device do you use? If you had issues with it on the stock ROM, then a GSI probably won't be any better, no matter which one you choose. If your device doesn't have a headphone jack, you can get a wired headset and a USB C adapter that will let you connect it. They even make adapters that will let you charge while using your headphones. That's always an option if BT is just too unreliable for you.
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
nah only in this gsi. and i dont have any other headphones and if i pick some dirty buds for cheap they are gonna sound 💀💀💀
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I currently use BT earbuds. They work fine for podcasts, YT videos, movies. But I'm considering a USB c headphone jack adapter for gaming. Wireless audio doesn't sound nearly as good as wired anyway.
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
i don't do gaming all i do is listen to music or watch videos/ movies thats it
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I've never had any musical interests. A rare thing in society these days. I'm just weird like that. I've tried listening to all kinds of genres, I just don't get any pleasure from it. I find music to be boring and unnecessary, sometimes even annoying. I have a hard time focusing with music playing in the background. I'm already a distracted scatterbrain, so I try to avoid anything that interrupts my concentration. My needs when it comes to audio devices are pretty simple.
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
sometimes i am bored and all i can do is listen to music. anyways let's not take this thread off topic
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
This thread barely gets any traffic anyway. A little OT/small talk isn't bad, helps keep it alive. Still testing as much stuff as possible in PE13 to see what bugs I encounter. So far, not much, except what I've already posted about here.
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
does anyone have any idea on how to fix my problem. basically when using BT headphones and i play something then stop it. bluetooth turns off and turns on immediately. then the cycle continues. PE 13 has been the best GSI for my phone so far battery life all amazing except this bluetooth problem. i am using a galaxy A32 4G. i am ready to provide logs etc. no other gsi performs as great as PE 13 for me.
[Treble-Enabled Device Development A/AB ROMS] 73sydney:
Its in alpha

Bugs are to be expected

I imagine when it gets to Beta, you maybe be able to submit bugs, but probably by then it will be fixed anyways
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
ah. just hoped that there would be something to get it working in the meanwhile. because my phone is just sitting in a half dead state right now.
[Treble-Enabled Device Development A/AB ROMS] 73sydney:
well then the sane thing to do would be to flash it back to stock while waiting, or flash PE12

sitting round waiting for a fix is not the way i would go....

as previously mentioned i would be using it if it werent for the fact i need my fingerprint reader to work....so back to stock for me for now
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
stock has a huge bug.... mobile data crashes every 15 seconds... i wouldn't want to deal with that. the latest firmware didnt fix that.. i am going back to some other gsi i guess...
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Honestly, it sounds like device issues to me.

Translation: I think your phone's hardware isn't that great.

Mobile data constantly crashing on the stock ROM is a surefire indicator that the device has potato hardware, or of it being defective. That's a huge red flag. It could also be a faulty sim card, but that's very unlikely. The cheaper the device, the lower the build quality will be, which means the internal components won't be the best either.

You did also mention that you downgraded to Android 11 firmware. Might be worth the effort to flash a newer stock firmware and try a GSI again. But no matter what stock firmware's my devices have been on, I've never encountered mobile data crashes, except with a particular custom kernel on a very old phone. Flashing another kernel solved the issue immediately.

Maybe you could RMA it to get a replacement. Or spend more on something better, which should hopefully be more GSI-worthy.
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
the issue fixed itself on the older firmware but its super laggy and the phone is unusable. my phone is fine. its just that Samsung can't get their own software right and have to push broken firmware updates out of no where. i am forced to use gsi's here. there are no roms for this device.
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
i am actually getting a better User experience on the gsi's except MTP not working. everything else is amazing actually.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Mtp working fine here, on both A12/A13 GSIs. However, it didn't work with A11 GSIs. I read some bug reports about this on GitHub, the answers given was basically "recompile your kernel from source code but with a few modifications". MTP not working on some Samsung devices has been a known issue for quite awhile. Glad to see the newer GSIs addressing it.
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
mtp worked for me when I used A12 vendor. bit with A11 vendor it doesnt work
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Well, there you have it, you know why it isn't working. I kind of suspected this would be the case for you.

But maybe you can mix and match a bit:

1. Use an A11 stock firmware as your baseline

2. Use the latest vendor.img from an A12 stock firmware FOR YOUR DEVICE

3. GSI of your choice.

You've said you have a Samsung device. Download your latest A12 firmware. Extract the AP tar.md5 file. From that, extract the super.img.lz4. up until this this step, you can use 7-Zip for the extraction.

Then use 7-Zip zstd to extract super.img from super.img.lz4 (not regular 7-Zip)

Unsparse the super.img with simg2img.

You can then use 7-Zip (regular non zstd version) to extract the vendor.img from the unsparsed (raw) super.img.

Flash the vendor.img in TWRP, and clean flash the GSI.

This may not work at all, you might not be able to boot, but it's worth a try.

If you know how to use Linux, you can use lpunpack to extract vendor.img from super.img (it still must be unsparsed first).
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
i ditched A12 vendor for a reason. first of all all the gsi's seemed super laggy. 90Hz feels like 60. although on the A11 vendor it is amazing. A13 GSI also boot on this one while they did not on A12 vendor.
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
i meant 30 Hz not 60* its super laggy...
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I'll be leaving PE for awhile, so you'll have one less person to test PE13. I want to give the LeOS GSI a try. Before I went back to Google, I was using MicroG as a replacement for Play Services, until it became unreliable. Just want to see if the situation has changed in the few years since I stopped using it. I may install PE13 via DSU Sideloader, though.

So far I've only used PE and phhhusson GSIs. I just want to step out of my comfort zone and give something else a go.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Unfortunately I couldn't get the LeOS T Beta GSI to boot, it just kicked me back into recovery after the bootloader screen. The 2nd build I tried booted, but it took me to a screen where I couldn't do anything except power off, reboot, or make an emergency 911 call. So, not usable. I'm trying LineageOS 19.1 build next, which means I'll be running A12, not A13. There is an A13 LOS, but it isn't yet offered in a vndklite version. I absolutely must have read/write access to the partitions. And working Magisk.

Edit: LOS 19.1 boots. I think I'll install PE13 as a secondary ROM in DSU Sideloader. Is there a way to make Magisk work in a DSU ROM?
[Treble-Enabled Device Development A/AB ROMS] Captain_cookie_200:
for me i already rooted using the AP file method since i have a samsung device. whatever gsi i flash or whatever gsi i try with dsu all i have to do is install Magisk and it just works!. although enable sticky mode if it asks to reboot for setup otherwise you'll boot into your main os. you could do this by typing this in a terminal emulator or through adb shell.

gsi_tool enable

after then reboot. to disable stick mode just type

gsi_tool disable
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I'm liking LOS 19.1, it feels cleaner and a bit less bloated than PE. PE is great, but IMO it should only include core Google apps like Play Store, Play Services, not much else. Apps like Maps, Photos, Keep etc are unnecessary and can be installed by the user if they want them. The only downside of LOS is that it doesn't read my exfat Microsd.

Will try installing PE as a DSU ROM later today. My boot.img is already Magisk patched, so hopefully it will work in PE by just installing the app.