yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] Rada23:
I have a problem. I can't activate the flashlight because it says "camera in use". How do I solve this? I have PixelOS android 13.

Other Mi A3 users with Pixel OS A13 don't have this happen to them, to clarify. It may be the version of Xposed or magisk? Xposed I have the version listed in the post of AOSP MODS, and magisk I have the "normal" version 25.2 25200.
[Xposed Framework Modules] dyval:
Bro can you also please link me to the telegram channel? PM if it's not allowed to link it here. Thanks.
[Xposed Framework Modules] Thebear j koss:
AOSPMods Discussion

You can view and join @AOSPMods_Support right away.

t.me
[Xposed Framework Modules] dyval:
Getting this error bro..
[Xposed Framework Modules] Thebear j koss:
No idea, works for me.
[Xposed Framework Modules] dyval:
All good now. Thanks man.
[Xposed Framework Modules] siavash79:
This is not a bug actually

Network monitor on QS panel is always at the center and thus not suitable for phones with center camera notches
[Xposed Framework Modules] siavash79:
2.5.0

released in stable channel

Changelog:

Added:

- Option to hide mobile roaming indicator (Statusbar)

- Option to show charging information on lockscreen (Lockscreen)

- Option to hide user avatar from lockscreen (multi-user mode) (Lockscreen)

- Option to enable smart actions to the clipboard overlay (Misc)

- Built-in bootloop/system crash protector

Removed:

- Lockscreen shortcut mods

- Statusbar center-area adjustment

- Combined signal icons

Fixed:

- Compatibility issues with Android 13 QPR1

... And bugfixes
[Xposed Framework Modules] i5lee8bit:
Yooooooo, this charging info on lockscreen mod is absolute fire!!!! 19.8W, 9.0V 2.2A atm... so detailed! Also, thank you so much for fixing the light theme on QS a few canary versions ago. One of those things I didn't realize how much I missed till I didn't have it anymore for a while.

I'm actually kinda sad you guys don't take donations, lol. Instead, here is my sincerest THANK YOU and ♥️ to you guys!!

Edit: just hooked into a PPS charger and getting 24.2W, 11V, 2.2A (P7 Pro on Spigen 45/30 PPS car charger). See attached screenshot. Technically higher than the supposed max, but I don't expect it to be 100% accurate anyway considering limitations of measuring not directly from hardware but what's reported by system - but great to know the PPS charger is working as expected without whipping out my meter or using annoying apps, especially seeing as how we're in the middle of a road trip haha. Huge props, again, guys!
[Xposed Framework Modules] antonio_d25:
Flashing over current installed version won't mess my settings/configuration up ? Or do I have to configure all over again?
[Xposed Framework Modules] siavash79:
P7 supports 20w, but P7P supports 25

You don't need to be worried. Just install it over the previous version
[Xposed Framework Modules] i5lee8bit:
Every article says it's still 23w, but it wouldn't surprise me at all if under the hood it can indeed handle 25w. I mean, I was already at 83% battery and got that 24.2W reported. Curious what it'll say when I try it when I'm dipped well below 50%!
[Xposed Framework Modules] siavash79:
The number is not the actual power transmitted. It's the charger capacity at its maximum. So your actual number might be lower
[Xposed Framework Modules] Ghisy:
Speaking of charging, can anyone recommend a third-party charger that can do 25W on the P7P? (sorry for the OT!)
[Xposed Framework Modules] siavash79:
I recently tried mcdodo brand. Surprisingly, it delivered the promise

Mcdodo Official | Your Best Fast Charging Choice

Discover the optimal solution for everything mobile device charging on Mcdodo and shop fast chargers, wireless chargers, portable chargers , cable, earbuds, and more...

www.mcdodolife.com
[Xposed Framework Modules] letmedanz:
Just updated to the latest Canary 196.

Would that be 'ahead' of the newly released stable?
[Xposed Framework Modules] ekeppel:
Yes, welcome to the bleeding edge.

Edit: Technically the stable build is 197, but staying on canary should guarantee the latest.
[Xposed Framework Modules] Admiral2145:
Are you talking about magisk or what exactly?
[Xposed Framework Modules] ekeppel:
The AOSP-Mods module.

Btw, I base my answer above on best practices, but not all developers do things the same way. Perhaps siavash79 will clarify where Stable 197 stands in relation to Canary 196.
[Xposed Framework Modules] antonio_d25:
..... and here I am wondering why the latest release is not working with my Nov. Firmware 🤦‍♂️🤦‍♂️🤦‍♂️
[Xposed Framework Modules] heij20032003:
The lockscreen shortcut is so so so useful....any difficulty encountered therfore needs to remove it?
[Xposed Framework Modules] siavash79:
Google has changed that part in a way that I still don't have the knowledge to mod those shortcuts
[Xposed Framework Modules] Pandemic:
+1

Same here, there is always something 🤦
[Xposed Framework Modules] Thebear j koss:
Update to December. November is in the past. Too many changes from November to December. There is nothing to add or fix in the November patch. V2.4.1 is the last version to work on November. All future releases will be for newer updates.
[Xposed Framework Modules] Pandemic:
Then i revert back.to 2.4.1 because all is working fine there on my device.
[Xposed Framework Modules] fullmetal509:
Awesome update, getting my notifications underneath the clock. How to fix? Not sure if it's a bug or not.

UPDATE* NVM got it fixed. Had to change something else. Thank you!
[Xposed Framework Modules] krilok:
Would you mind letting me know what's the font you're using? Looks quite good... 😉
[Xposed Framework Modules] linus207:
Wow, it's awesome. I am also very curious ☺️
[Xposed Framework Modules] fullmetal509:
Google Product Sans 2.0 By D4rk

Magisk Module!
[Xposed Framework Modules] krilok:
Thank you. Was already using Product Sans myself, but hadn't enabled bold fonts under my roms display settings... 😉
[Xposed Framework Modules] DanielMode:
LSPosed telling me to update but i'm on 1.85 (6695) it's driving me crazy
[Xposed Framework Modules] Zaxx32:
Was getting the same after manually updating to the latest 'full' aosp...wouldn't let me back to the main menu until I did a force stop and restart...seems ok since. Like the new icon btw...colors! :p
[Xposed Framework Modules] Eleo:
Stable version is directly equal to latest canary before that. Stable version is released once users test canary version and report back. It wouldn't make sense to add something new untested over canary version when releasing stable build
[Xposed Framework Modules] Daax:
Hi, can you tell me the name of this widget? It looks awesome!
[Xposed Framework Modules] DanielMode:
doesn't help..... still the same
[Xposed Framework Modules] Schroeder09:
I just completed and install of AOSP mods on a second p7p. One the first p7p I had when the option to decrease the amount of space under the space bar was enabled I had more space than what's shown here reduced. It was on Canary build 196, and if I remember right it did go from what is shown here to an even more reduced version where the space bar was right on the bottom of the screen on its own. The arrow to hide the keyboard was gone entirely. I use gesture navigation so a quick swipe back from the side of the screen hides the space bar anyways and is even more convenient than the little down arrow.

I liked this even more reduced version. It gave my more screen real estate. Was this even more reduced version a glitch, is it a function of the canary build, or is there another option I need to enable in AOSP mods? I'm on a p7p with the December update, krishrikua kernel, with 2.5.0 AOSP mods, 1.8.5 LSposed, and magisk stable 25.2.
[Xposed Framework Modules] fullmetal509:
Its from One4kKWGT Reloaded: KWGT Widget on the play store! Its it payed widget, worth it though!
[Xposed Framework Modules] iamMG:
I wan to request a feature. Please add the ability to add a QS tile to switch the SIM being used for data. Such a tile can be found on Oxygen OS. Looks like this:
[Xposed Framework Modules] sutur:
I think I have an important question?

In what way (if at all) is this module reversible, in case of issues?

Or phrased differently: can every change made by this module be "undone", and if yes, how would the developer(s) suggest we do this?
[Xposed Framework Modules] siavash79:
Nothing is permanent here. You can simply turn off any option you enable, or simply uninstall it in magisk. No special care required
[Xposed Framework Modules] sutur:
Okay the reason I ask is that once in the past using gravitybox (which is similar) enabled a "quick unlock" feature, and even after disabling gravitybox, the quick unlock behaviour never went away.

Quick unlock in this examples makes the lockscreen accept your code once you've entered it without hitting OK. In retrospect, that would make bruteforcing very easy...
[Xposed Framework Modules] siavash79:
In AOSPMods even if you enable that option, trying too many codes will lockout the device. So still secure
[Xposed Framework Modules] sutur:
Oh yeah true.

But once your module is magisk disabled, the default behaviour would return?
[Xposed Framework Modules] nIsmoAddict:
Hi all, this might be a dumb question but how in the effing eff do I install the module? Do I do it through magisk? I cannot find a way through the lsposed manager to install from local disk.

Any help would be so appreciated.

Edit: NM, I just installed it through magisk (slaps forehead).
[Xposed Framework Modules] jejemc:
hello @siavash79 would it be possible to add the crt-off mode? thank you
[Xposed Framework Modules] siavash79:
The main concentration is on functionality mods. So the chances aren't high
[Xposed Framework Modules] jejemc:
very good thank you and thank you for your work ;)
[Xposed Framework Modules] A$hr@j:
I'm probably gonna get slammed for asking this question but do we have a list of things broken on not working by applying this mod? Like Android auto or Google pay etc? I tried searching for those words but they are pretty generic and almost every post shows up on the search result.
[Xposed Framework Modules] letmedanz:
Both gpay & Android auto working.
[Xposed Framework Modules] siavash79:
The mod itself doesn't break anything

But it requires magisk and lsposed and they would probably have some impacts. How to handle them isn't necessarily within capacity of this thread
[Xposed Framework Modules] iRhyiku:
Pixel 7 Pro - Stock December stable

using AOSPMods breaks brightness slider in QS, the animation of it sliding with your finger doesn't play and only updates on finger release. The brightness still works as intended and is purely visual.

This is the only mod I have installed and that includes theming apps, no brightness options checked in app.
[Xposed Framework Modules] antonio_d25:
I'm having the same small issue. Even though I'm pretty good at eyeballing where the level is at
[Xposed Framework Modules] Pandemic:
Yes same here
[Xposed Framework Modules] otonieru:
Same here. December build. P7P
[Xposed Framework Modules] Schroeder09:
My brightness level slider also only updates upon release. It is not "live" while using it. I too am on the December update with a pixel 7 pro.
[Xposed Framework Modules] ekeppel:
In case anyone is wondering about the January update, I just installed it on my Pixel 7. From what I can tell, all of the (many) AOSP-Mods features I have enabled seem to be working without issue. YMMV ;-)
[Xposed Framework Modules] siavash79:
Thanks. I personally don't expect anything to break until the next feature drop, which I guess will be June 23
[Xposed Framework Modules] shouk_1987:
I have installed latest 2.5.0 over previous version and after reboot mods are not applied as if i didnot install AOSP mods at all

I have experienced this behaviour before and i cannot recall how did i fix it, i have revoked root rights from aosp mods such that when i open aosp mods then it asks me again, it did not solve the issue, restored previous xml file and didnot solve as well

I have removed the mod completely and will install it again and see then report back

Edit : Side mounted physical Fingerprint also stopped working even after the mod has been removed 🥲
[Xposed Framework Modules] siavash79:
I believe you're installing a wrong version. Try checking the OP for correct version and try again
[Xposed Framework Modules] shouk_1987:
It did show to me as an update from Magisk modules page

I am on A12L ( 12.1 ) with pixelOS aosp rom

What is the exact compatibility of 2.5.0 as it confuses me in github page

Edit : you were correct as 2.4.1 worked for me, i believe it would be better to not show the 2.5.0 to non compatible devices ( i am jealous as i needed the charging parameters on the lockscreen )

Thanks a ton for your marvelous work on this Mod
[Xposed Framework Modules] Schroeder09:
Has anyone seen this? Can the developer or others address this? @siavash79 can you address this?
[Xposed Framework Modules] Pandemic:
Are you in a rush ?! Stay calm the dev will probarly see it.
[Xposed Framework Modules] Schroeder09:
considering the question was initially posted five days ago I have been plenty patient. Consider this a *bump* on the question. If you don't know the answer don't post. Settle down. I never tagged your username in the question.
[Xposed Framework Modules] Pandemic:
Oke and xda is an open site so everyone can respond on your question, dont be brutal to me man
[Xposed Framework Modules] Admiral2145:
Can the feature hold the back button to kill on screen app be added back? It was available before.
[Xposed Framework Modules] Thebear j koss:
Navigation bar is deprecated. Gestures are only being updated I believe.
[Xposed Framework Modules] ekeppel:
If you are looking for extreme gesture configurability beyond what AOSP Mods is doing, you might consider trying 'Gesture Control' from the Play Store. It can do that and much more.
[Xposed Framework Modules] alsansan:
I'm having the brightness slider animation bug also since Dec Update. I updated today to Jan and the bug still there. Hope it's fixed by next aospmods update :)
[Xposed Framework Modules] XtraWater:
Hi. Friend of mine updated today to the latest version of the AOSP mods on his Pixel OS. Then he ended up in a bootloop. He removed the module in orange fox and restarted into system. Now the phone boots until the Google Logo appears and freezes then.

What's the best thing to do?
[Xposed Framework Modules] Thebear j koss:
From dev on telegram - Animation is not that huge of an issue right now. Brightness slider works, that is important. The animation is pushed to backlog and will be dealed later
[Xposed Framework Modules] Thebear j koss:
Read comparability. Pixel OS isn't updated to December or January builds, so you have to use version 2.4.1 I think was the last version for December builds. No idea what orange fox is, but you would need to uninstall magisk mods using adb command
[Xposed Framework Modules] XtraWater:
Thanks. Orange fox is another recovery like TWRP. In there is a Magisk section which lists the installed modules. He removed this module.

Now i wonder if there is a way to do a kind of safe boot without modules. It works for still suggests to do the adb way?
[Xposed Framework Modules] XtraWater:
Edit: is there s way to downgrade to 2.4.1?
[Xposed Framework Modules] Thebear j koss:
Yes. Download 2.4.1 from GitHub repo or actually right in OP of this thread. Last line in OP
[Xposed Framework Modules] XtraWater:
Cool. And then flashing via recovery?
[Xposed Framework Modules] Thebear j koss:
I've only flashed using magisk. Pixel 6 has no recovery. Probably need to uninstall other version and install however you install magisk mods.
[Xposed Framework Modules] XtraWater:
Didnt work. This module update destroyed everything. Even after reflash the custom Rom, it doesn't boot.

I'll uninstall the module on my phone and never touch it again.

This module is experimental sh%t
[Xposed Framework Modules] Thebear j koss:
No. You just failed to follow directions. Module has worked fine since day 1. Never had any issue with it. Maybe you should take the time to read before just installing things. It is completely unfair to the devs who have continued this project to have a user not follow directions and blame them/the module.
[Xposed Framework Modules] AlDollaz:
The only supported custom ROM is Pixel Experience. Works fantastically on my stock P6P.
[Xposed Framework Modules] XtraWater:
It worked just fine. Untill the update. The update should check if it is compatible to the system.

Even now, nobody knows what was going wrong and fire to fix it. I also installed previous version. Same, boot freezes.

Finally, re-flashing the rom should bring the phone to normal boot. But didn't help. Flashing Firmware and boot.img didn't work. Not much options left besides flash the original Miui Rom
[Xposed Framework Modules] Thebear j koss:
I don't know. From what I know magisk mods can be uninstalled using adb. I don't know anything about custom recovery and different devices other than pixels. I'm just saying it isn't fair to blame the mod/devs because you installed the wrong version. Before flashing anything I always read as much as I can before flashing. Instructions couldn't be clearer than what is written in the op. Pixels have boot loop protector and safe mode which disables all modules so we can boot back without losing anything.
[Xposed Framework Modules] Thebear j koss:
How to uninstall Magisk Modules if it caused bootloop? - Xiaomiui.Net

As you know Magisk Modules are indispensable for us. But we can get bootloop after installing a module. In this case, you do not need to panic and reset your

xiaomiui.net
[Xposed Framework Modules] XtraWater:
We did that too.
[Xposed Framework Modules] Thebear j koss:
Then you have another issue going on outside of this mod. If the module was deleted, there is absolutely no way that it can cause any sort of bootloop. Maybe grab a logcat using adb during boot.
[Xposed Framework Modules] Eleo:
You probably flashed it on MIUI 🤣🤣

Incapability of reading is major problem of this century
[Xposed Framework Modules] mackdacre:
The OP literally says the module is ONLY compatible with AOSP/Pixel and that it's NOT compatible with "heavily modified" firmware. MIUI is basically the most heavily-modified firmware that exists, lmao. Just because incompatible software previously worked for some reason doesn't mean it always will. If I put E100 in my gas tank when my car needs 10% or less ethanol and it happens to work but the next day it doesn't start and I'm stranded, who's fault is that?
[Xposed Framework Modules] XtraWater:
Did you even read the posts?
[Xposed Framework Modules] XtraWater:
I didn't. Read my posts again
[Xposed Framework Modules] Thebear j koss:
He flashed new aospmod build on a November Pixel Experience ROM. If he just would've deleted magisk modules thru USB he should've been fine. I think the issue is he was using fox's recovery on his device, or something else is causing the boot loop because he said he deleted the mod in recovery.
[Xposed Framework Modules] XtraWater:
TO be clear. Pixel OS 12 is installed. That's everything else than heavy moded
[Xposed Framework Modules] siavash79:
Ok I suggest to close this argument:

As mentioned in the second post, magisk and Xposed mods are very tricky and should be used with lots of precautions and only by users with very high experience about rooting.

In this specific case I guess at least one of these requirements (no matter which) was omitted, and as the result (also mentioned in post 2), the device had to be reset.

Even I lost a whole pixel 6 phone because I ran a command when I was sleepy and not careful enough.

My suggestion to everyone working with rooted devices is to read a lot, think about consequences of actions and finally be very, very careful. Always
[Xposed Framework Modules] antonio_d25:
It works fantastic on Corvus OS also.
[Xposed Framework Modules] antonio_d25:
Does the "Built-in bootloop/system crash protector" disable magisk modules if there is something wrong with them so the system can boot ?
[Xposed Framework Modules] siavash79:
No it auto-disables only AOSPMods after 3 system crashes
[Xposed Framework Modules] otonieru:
If the original ROM was MIUI, then i assume the phone is xiaomi ? Just flash everything, wipe data and everything, that's the risk of flashing & modding something in an incorrect manner, you need to be ready to wipe data/system anytime.
[Xposed Framework Modules] Schroeder09:
Whose screens lose the down carrot error when enabling the "reduced space below keyboard spacebar" option? Mine randomly started doing this I think on the canary 186 build and it was AWESOME. The spacebar was really low with lost of screen real estate. It stopped though on a fresh install and now the space below the spacebars is as the AOSP option suggests- slightly reduced but still very much there. There really is no use or need for the down carrot to minimize the space bar when a simple back swipe from the edge of the screen will minimize the keyboard.
[Xposed Framework Modules] Pandemic:
Luckily i have bootloop protector, if something went wrong, it reboots and disable all magisk modules 😊
[Xposed Framework Modules] antonio_d25:
I've been trying to find this module but haven't been able to... Is it compatible with A 13 ?

Could you point me to the thread you got it from ?

Thanks
[Xposed Framework Modules] mingaldrichgan:
Everything you're looking for is in the OP.

EDIT: Just realized you meant the Bootloop Protector. Sorry. Fox Magisk Manager has it, but I don't know if it's been updated for A13.
[Xposed Framework Modules] Schroeder09:
Not sure why I've been able to get any input on this even after having directly messaging the dev after receiving zero replies in this thread, but for everyone's information to eliminate the space below the keyboard entirely we can enable the option to hide the navigation bar under the "navigation bar" menu in the AOSP mods app. It looks really nice and clean. Of course you lose the ability to swipe left or right between recent apps when the keyboard is up because you're swiping on keyboard buttons. I really like it though. Disabling the navbar gives lots of screen real estate. Typing is easier, faster, and the keyboard buttons are all easier to reach for fast thumb typing. I make less typing errors.

I hope this helps others who may have seen the repeated question.
[Xposed Framework Modules] n53r10us:
Im facing a little problem with the notification icons in the statusbar.

They arent in line with the clock.set a Bit down.

Thus happens straight when i enter the aosp mod after a fresh Installation.

Only happens with the newest 2.5 Version of it.

With 2.4 i got no problems with the icons.

Actually im in cherish os 4.3, but im facing the same problem on other roms like crdroid,ricedroid,sparkos.

Dont know about Arrow and lineage.

All roms are with the december secruity Patch. So im a little bit forced to usw 2.5 insteed of 2.4.

Someone else faced the same issues and maybe found an solution for it?
[Xposed Framework Modules] siavash79:
Yes it seems on some roms the notification icons don't sit exactly where they're supposed to.

The "reason" why compatibility of AOSPMods is limited to pixel roms is that I don't have access to other custom roms to test the mod on them and find possible issues to solve (finding issues is not enough of course, the causes have to be identified). (Of course I can download and install those roms, but having limited resources - device and time -, it's not practical to support more)

Edit: I do hope other Xposed devs can participate in the mod so that the range can get extended