yashsingh1/xdaforums huggingface dataset:
[Advantage X7500, MDA Ameo General] royalmail:
pls help

thanks for the respond chan, i only have A4 pinyin installed in the system.

seems that the default english input method doesn't come with the ROM.

so i don't have the default on-screen keyboard as u recommended. the only on-screen keyboard is ZTA4 keyboard. whenever i try to type on the magnet keyboard, it always come with pinyin.

is there any way i can install the default english input back via certain CAB file?

there is another possibility. maybe i have flashed a defective ROM. could u give me an indication where i can download the latest Chinese ROM?

thanks!
[Redmi Note 10 Pro] Vaatito:
The NFC of my Redmi Note 10 PRO no longer works after having flashed the PIXEL EXPERIENCE rom (I have done the procedure again, but the NFC still does not work) the same thing happens to me when I have Arrow OS installed, it appears where the NFC icon was grayed out and could not be enabled.

Any solution?

I've been trying for three days to get NFC to work, but it still doesn't work.

It is not ideal to go back to the garbage that is the customization layer of MIUI
[Redmi Note 10 Pro] Ozymo:
I have the same problem
[Redmi Note 10 Pro] Elinx:
If a custom rom give problems with sensors, camera's etc. mostly the hardware is changed by Xiaomi and that custom rom missed the drivers for it.

Best chance is to use one of the recent new rom developements, but no guarantees.
[Redmi Note 10 Pro] RAMBO29:
Do you see NFC repair/reset options? It's most likely due to drivers though in some cases kernels can affect as well.
[Samsung Galaxy S8 Questions and Answers] BigRedChopper:
Hi all,

My S8 SM-G950F is no longer recieving regular security updates so I would like to install a new ROM that gets regular updates.

As I like the phone but don't want to keep using it long term if its going to have unpatched vulnerabilies.

Could I get some suggestions on what to replace the stock ROM with?

PS I am based in the UK

Thanks,
[Android Apps and Games] Quinny899:
Classic Power Menu is a Power Menu Replacement for Android 11+, with the main aim being restoring power menu options (Device Controls & Quick Access Wallet) on Android 12.

Classic Power Menu Requires root access to function, it is not possible without root

Please read the FAQ before downloading or replying with an issue

Features​

Up to 10 power options in the Power Menu, including the non-stock options of Screenshot, Reboot Recovery, Reboot Bootloader and Restart SystemUI

Fully customisable, including rearranging and hiding buttons you don't use

Quick Access Wallet in the Power Menu, accessible while locked or unlocked

Optional blurring of card numbers while locked

Optional showing of loyalty cards, restoring a previous feature from Android 10 which was removed. Loyalty cards' codes can be shown while locked and without needing to open Google Pay, if you wish.

Device Controls in the Power Menu, accessible while locked or unlocked

Optional ability to interact with controls while locked, without requiring authentication

Material You inspired theme, using Monet colours and background blur on the Power Menu

Xposed is not required, interception of the power button is done via Accessibility Service, with only normal root required

An optional Xposed module is included, which can react quicker than the Accessibility Service

Screenshots​

Download​

Download the latest release from the GitHub Releases page

Changelog​

Content Creators​

If you are making a video or article about Classic Power Menu, you will want to hide your card numbers. Enable the developer options in Classic Power Menu by triple tapping the "About" option, and enable Content Creator Mode. This will always blur your card numbers and will show a fake QR code for loyalty cards, keeping your data safe.
[Android Apps and Games] pbanj:
it works pretty good, but i noticed that with lsposed it still asks for you to activate the accessibility service during setup.

also it seems after a reboot the first time you open the power menu it is using the stock power menu. but only that 1 time, every time after it's the one from this. it's probably something android related and out of your control, but i figured i would let you know anyways.

not sure if this is a bug or a design choice but the menu is transparent other than the power/reboot area, it would be nice if it wasnt transparent at all or at least a toggle for it

pixel 5a, rooted stock.

View attachment 5419701
[Android Apps and Games] Quinny899:
You need to reboot after enabling the module, then it will detect during the setup and not ask to enable accessibility.

The background is supposed to be blurred. What Android version are you on?
[Android Apps and Games] pbanj:
i've rebooted multiple times and it still shows the screen asking to enable the accessibility service. thats why i mentioned it.

andorid 11 the September update
[Android Apps and Games] Enddo:
any reported success with MIUI? I was unable to get this working on the Redmi Note 10
[Android Apps and Games] Quinny899:
If it's crashing, send a logcat. If it's just straight up not working, it's probably MIUI's customisation and not a lot can be done.
[Android Apps and Games] Quinny899:
Version 1.1 now available with some bug fixes:

Download on GitHub, or in the app. You may see a crash when opening with the update, if this happens just go to the GitHub and download the update manually, it's fixed in this update for next time.

@pbanj and anyone else with blur issues, you need to run the shell commands in the FAQ to enable blur across the system for it to work. Note that doing so will also apply blur to other parts of SystemUI, so obviously don't do this if you don't want it. Classic Power Menu will use a solid background if blurs aren't supported now.
[Android Apps and Games] Enddo:
I'm not seeing any specific app crash popups. But if you think a logcat taken after pressing the power button will help, I'll be happy to send one along.

I just see the usual MIUI power menu appear when long pressing the power button (after granting root and enabling the accessibility service)
[Android Apps and Games] pbanj:
Works, thanks for the fast fix.
[Android Apps and Games] PritamGhosh8009:
Nothing is working... I have enabled both xposed module on lsposed and accessibility and rebooted multiple times... Still stock power menu appears

Using app version 1.1 on pixel 3a android 12 beta 5 gsi on Redmi S2

Edit: Working after system reinstalled
[Android Apps and Games] pbanj:
Scoop | F-Droid - Free and Open Source Android App Repository

Catches a stack trace when an app crashes unexpectedly.

f-droid.org

Give that a try. It works great for catching logs for app crashes
[Android Apps and Games] Jiggs82:
Hey flashed latest v1.1 and still not seeing blur background, it's just transparent. Pixel 5 Android 12 beta 5. By the way can you add an option for black/dark grey/opaque background ?

Thanks
[Android Apps and Games] pbanj:
Not sure why that double posted
[Android Apps and Games] Enddo:
appreciate the suggestion. it hasn't detected any crashes yet. I've reset the app and gone through the setup process again. restarted. etc.

it hasn't detected any crashes

guess it's MIUI breaking it. i'll check out the app on LIneageOS or something
[Android Apps and Games] AyHenry:
FATAL EXCEPTION: main

Process: com.kieronquinn.app.classicpowermenu, PID: 14525

java.lang.NullPointerException: isAccessibilityServiceEnabled$default must not be null

at com.kieronquinn.app.classicpowermenu.utils.extensions.Extensions_AccessibilityServiceKt.isAccessibilityServiceEnabled$default(Extensions+AccessibilityService.kt:12)

at com.kieronquinn.app.classicpowermenu.ui.screens.setup.rootcheck.SetupRootCheckViewModelImpl$showNext$1.invokeSuspend(SetupRootCheckViewModel.kt:50)

at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)

at kotlinx.coroutines.internal.DispatchedContinuationKt.resumeCancellableWith(DispatchedContinuation.kt:377)

at kotlinx.coroutines.intrinsics.CancellableKt.startCoroutineCancellable(Cancellable.kt:30)

at kotlinx.coroutines.intrinsics.CancellableKt.startCoroutineCancellable$default(Cancellable.kt:25)

at kotlinx.coroutines.CoroutineStart.invoke(CoroutineStart.kt:110)

at kotlinx.coroutines.AbstractCoroutine.start(AbstractCoroutine.kt:126)

at kotlinx.coroutines.BuildersKt__Builders_commonKt.launch(Builders.common.kt:56)

at kotlinx.coroutines.BuildersKt.launch(Unknown Source:1)

at kotlinx.coroutines.BuildersKt__Builders_commonKt.launch$default(Builders.common.kt:47)

at kotlinx.coroutines.BuildersKt.launch$default(Unknown Source:1)

at com.kieronquinn.app.classicpowermenu.ui.screens.setup.rootcheck.SetupRootCheckViewModelImpl.showNext(SetupRootCheckViewModel.kt:49)

at com.kieronquinn.app.classicpowermenu.ui.screens.setup.rootcheck.SetupRootCheckFragment.handleState(SetupRootCheckFragment.kt:38)

at com.kieronquinn.app.classicpowermenu.ui.screens.setup.rootcheck.SetupRootCheckFragment.access$handleState(SetupRootCheckFragment.kt:12)

at com.kieronquinn.app.classicpowermenu.ui.screens.setup.rootcheck.SetupRootCheckFragment$setupState$1$invokeSuspend$$inlined$collect$1.emit(Collect.kt:135)

at kotlinx.coroutines.flow.FlowKt__ChannelsKt.emitAllImpl$FlowKt__ChannelsKt(Channels.kt:62)

at kotlinx.coroutines.flow.FlowKt__ChannelsKt.access$emitAllImpl(Channels.kt:1)

at kotlinx.coroutines.flow.FlowKt__ChannelsKt$emitAllImpl$1.invokeSuspend(Unknown Source:13)

at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)

at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)

at androidx.lifecycle.DispatchQueue.drainQueue(DispatchQueue.kt:75)

at androidx.lifecycle.DispatchQueue.enqueue(DispatchQueue.kt:112)

at androidx.lifecycle.DispatchQueue.access$enqueue(DispatchQueue.kt:31)

at androidx.lifecycle.DispatchQueue$dispatchAndEnqueue$1$1.run(DispatchQueue.kt:100)

at android.os.Handler.handleCallback(Handler.java:938)

at android.os.Handler.dispatchMessage(Handler.java:99)

at android.os.Looper.loopOnce(Looper.java:201)

at android.os.Looper.loop(Looper.java:288)

at android.app.ActivityThread.main(ActivityThread.java:7842)

at java.lang.reflect.Method.invoke(Native Method)

at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)

at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1003)
[Android Apps and Games] AyHenry:
From scoop app.

V1.1 crashing on my pixel 3a xl running android 12 beta 5
[Android Apps and Games] AyHenry:
dogbin - afilololom

FATAL EXCEPTION: main Process: com.kieronquinn.app.classicpowermenu, PID: 14525 java.lang.NullPointe

catbin.up.railway.app

Link to log if that's not readable
[Android Apps and Games] Quinny899:
Known bug, enable the accessibility service
[Android Apps and Games] Bxperiaz3:
Is there any app like this for android 10?
[Android Apps and Games] Quinny899:
No, the APIs are not there in the system on 10 so it's not possible.
[Android Apps and Games] Quinny899:
I don't know. They still work on all my devices, it's impossible to debug something like this without physical access to a device that's doing it. Normally I'd just ask for a copy of the database from a device with the issue, but these databases contain payment cards so I can't do that here. Until it actually happens on one of my devices, there's nothing I can do. Loyalty cards have always been a hack, not an official feature of the quick access wallet API so are prone to issues like this.
[Android Apps and Games] tonysunshine:
Hi is there a list of which smart home apps the classic power menu supports? Or Im wondering if there is a way to get it to work with samsung smartthings or hubitat? Right now only have options for Google Home and Tasker
[Android Apps and Games] Quinny899:
Anything that uses the Controls API
[Android Apps and Games] toolhas4degrees:
Any hope to port this to a13. Oos 13 hopefully? Miss having home and pay on long prees of power button
[Android Apps and Games] Slim2none4u:
It works on A13. Can not speak for OOS13.
[Android Apps and Games] toolhas4degrees:
I can't get it to work and when installing latest accessibility option is not there. Greyed out to enable. Doesn't change anything the way it is on oos13
[Android Apps and Games] Quinny899:
You need to allow restricted settings in the app info > overflow menu. OxygenOS is so far from AOSP now that it's like MIUI - would require community support to implement the Xposed method since I don't have a device with it.
[Android Apps and Games] toolhas4degrees:
I know, but I read that you had accessibility service before and revoked it with later method. Is there a version with accessibility I can try? Or was the reason accessibility service didn't work?
[Android Apps and Games] Quinny899:
Like I said, all you need to do is allow restricted settings on the app info page. This is an Android 13 thing, it happens to every app that uses accessibility.
[Android Apps and Games] toolhas4degrees:
Tried all enabled restricted access. Doesn't work on oos13. Thanks for your work
[Android Apps and Games] Quinny899:
You will need to disable the Xposed module and reboot if it's still enabled. Other than that, if it still doesn't work than OnePlus broke yet another thing in OOS and I won't be adding support unless someone adds it as a PR.
[Android Apps and Games] toolhas4degrees:
No the restricted worked OnePlus broke it. Bc it's not OnePlus anymore it's oppo.
[Android Apps and Games] rom4ster:
Is there a specific reason that generic passes cannot be accessed while others can for example my flight passed that I added was instantly detected and even instantly prioritized however I was unable to detect any passes added with the generic pass api.
[Android Apps and Games] Quinny899:
It's not that they can't, it's that the app isn't built to access them, as I have previously stated. It's not magic.
[Android Apps and Games] rom4ster:
So flight pass is different from generic pass ? good to know
[Android Apps and Games] Quinny899:
Yes, they all have different protobuf.
[Android Apps and Games] Quinny899:
I suggest you read the recent comments, the app is perfectly fine but the Xposed module is not compatible with every device. Disable the module, reboot and use the accessibility option. If that doesn't work, there's nothing that can be done - OnePlus is to blame, not me.
[Android Apps and Games] Bunecarera:
Works fine on my 9 Pro....
[Android Apps and Games] toolhas4degrees:
Doesn't work for me on 10 pro. Maybe detail what you did and I'll try again. But 9 pro and 10pro file system is different. Also don't know if you are on a13 or not
[Android Apps and Games] rom4ster:
Random question but is there any way to disable the standard home screen pay option. right now this app actually doesn't do much for payment it's simply looks like it does but in reality anything will work as long as your phone is unlocked because Android does that. Is there a way to disable the standard Android behavior and make it so that payment only works when the classic power menu screen is there
[Android Apps and Games] Quinny899:
Not that I know of.
[Android Apps and Games] Ysar57:
Thanks! Works fine on my Oneplus 8T with OOS13.
[Android Apps and Games] emretwolf:
guys how can i change the language of this app? There is the language in the apk, but I couldn't find how to change it.
[Android Apps and Games] acwcanada:
It was working fine with A14 DP1, but with the new releasing of A14 DP2, the app has stopped working.
[Android Apps and Games] Quinny899:
Could you post a log please, I don't have a device running A14.
[Android Apps and Games] acwcanada:
Phone is my daily drive and the A14 DP2 has really given me a lot of trouble so I already flashed back to A13, sorry couldn't provide log anymore. Based on my memory, the situation is like these:

1. Running it without LSPosed, "Accessibility" couldn't turn on as it was greyed out in system setting.

2. With LSPosed v1.8.6-6851 (it was said supporting A14 DP2 starting v1.8.6-6849), it would crash immediately after Classic Power Menu is enabled.

I would say that I am not so sure that it is a Classic Power Menu issue as I do encounter "process system isn't responding" error with LSPosed although they said it supports A14 DP2.

Hope my explanation can give you a little bit of idea and perhaps some other people still have their A14 DP2 installed could provide you more details.

Sorry again for not much help and thanks for your support of the app.
[Android Apps and Games] Quinny899:
Accessibility isn't a bug, it's just how Android works now. You have to allow restricted settings, same as on 13.

As for the crash, that's not an Xposed issue if it launches and then crashes. Unfortunately though, without a log, nothing I can do.
[Android Apps and Games] acwcanada:
I know the "Accessibility" issue. Perhaps I didn't explain myself clear. I remembered that on A13, once Classic Power Menu is enabled on Xposed, "Accessibility" of the app would be indicated as "on", but now on A14, even the app is enabled on Xposed, it's "accessibility" would be greyed out and indicated as "off" and nothing I can do with it. I know nothing about Xposed and your app but just a plain user, but common sense makes me to guess that in this case, seems Google has tightened up security in A14 and Xposed is not able to really "enable" your app although it shows that it is enabled.
[Android Apps and Games] Quinny899:
The Xposed module is entirely separate to the Accessibility option. If you enabled both then it will ignore the accessibility option, but Xposed does nothing to make it show as enabled. This isn't a bug.
[Android Apps and Games] Swap_File:
Works on my 10 pro fine, on the latest A13. Like others have said, make sure the module is disabled and use accessibility.
[Android Apps and Games] rom4ster:
I am having a newish oldish issue. It used to be that flight passes were instantly recognized even if loyalty was not. That is no longer the case. Nothing is recognized at all now. Transport, loyalty, etc... Only payment. Any remedy for this? I could remove all my payments and give you a copy of that database... if you tell me where it is.
[Android Apps and Games] rom4ster:
I modified this function

override fun getGooglePayDatabaseForLoyalty(): ParcelFileDescriptor? {

Log.e("CPM", "DATAAAA BAS3")

try {

val googlePayContext = getGooglePayContext()

val googlePayAccountId = getGooglePayCurrentAccountId(googlePayContext) ?: throw IllegalAccessException("Damn")

val hashedAccountId = Hashing.md5().hashUnencodedChars(googlePayAccountId)

val database = googlePayContext.getDatabasePath("${hashedAccountId}_tapandpay.db")

if (!database.exists()) throw IllegalAccessException("Damn 2")

return ParcelFileDescriptor.open(database, ParcelFileDescriptor.MODE_READ_ONLY)

}catch (e: Exception){

Log.e("CPM", "Failed to get Pay database", e)

return null

}

}

and I do get an error called "Damn" but I cant get this to run in a debugger so idk where to go from that. perhaps you could shed some light on what parts of the code are doing what.
[Android Apps and Games] Quinny899:
If the database doesn't exist as your code says, then it stands no chance at all of reading loyalty cards. That's where they're stored.
[Android Apps and Games] rom4ster:
I have Loyalty cards in the wallet app though and I even added new ones
[Android Apps and Games] rom4ster:
One more thing. I am on a beta of google wallet.
[Android Apps and Games] Aldwarii:
Thank you for this sophisticated module!

I was wondering, Is it possible to support other 3rd party wallet apps rather than Google wallet? In our country the google Wallet isn't supported yet, although, we have an application that is called Mada Pay. Would you please add the option to replace the google wallet with this app?
[Android Apps and Games] Quinny899:
It's impossible for me to debug this more, because I can't ask for people to upload their databases or send their filenames because they contain very sensitive data. If you figure out why it's not loading, if it's a different name or location, then feel free to make a PR, but anything more on my end won't be happening.
[Android Apps and Games] Quinny899:
Not possible.
[Android Apps and Games] rom4ster:
Ok so I found something. The shared prefs folder is empty, meaning when you try to get the hashed account id it will fail. Direct hardcode of my hashed user works (NOT going to commit that but it was just to see) but the thing is, the hashed account ID is just the file name of blahblahblah_tapandpay.db

If you were to simply scan that directory for that db file, you would find it and then you can call it as normal. The problem isnt that the database does not exist, its just that the xml file that tells u where it is does not. So what do you think?

Also, I was able to find out that if you remove the db, it will regenerate with the *exact* same hash, so it must be getting it from somewhere...

Look I dont have a huge expertise on android, but you do. Could you shed light on what the xml file is for, how this works, and possible things i could try? By myself im just stumbling along but you should understand whats going on pretty well so together we could do this a lot faster.

Could you or someone give me a copy of that XML file WITHOUT any user data, like just the xml tags? I want to try searching for those.
[Android Apps and Games] Quinny899:
That would also cause it. It doesn't just use the first database of that format as that would break for multiple accounts, which isn't acceptable for an app like this.

How many accounts do you have added? Perhaps it only gets filled if there's multiple.
[Android Apps and Games] rom4ster:
i have /data/user/0 and /data/user/10 but besides a work profile i have no other users
[Android Apps and Games] rom4ster:
is there a way to detect the number of the currently logged in user. I assume /data/user has all the users in it.

I wonder if the path /data/user/<number>/<wallet_app_package_name>/databases would only contain the database for that user.

IF that is the case. Then you could scan that directory, provided you can get the number of the current user.
[Android Apps and Games] Quinny899:
I meant Google accounts, but instead I've just added some code to default to the first database & first valuables images folder if the account ID lookup fails. My theory is that the shared pref doesn't get filled if there's only one Google account in Wallet, and that since I always have multiple accounts signed in (personal + work), it's just never happened to me.

Pushing a new build with that + Android 14 fix now
[Android Apps and Games] rom4ster:
AWESOME ill try your new build in a bit
[Android Apps and Games] Quinny899:
Version 1.6.1 now available

Download from GitHub releases as usual

Thanks to @rom4ster for your help in figuring out what was different and probably causing the Loyalty Cards issue
[Android Apps and Games] rom4ster:
You missed a small thing that breaks it

you do

context.databaseList().firstOrNull {...

but that uses OUR application context which is empty

you need to do

googlePayContext.databaseList().firstOrNull...

around line 175

so that way it uses the google wallet context :)

It works for me after that change
[Android Apps and Games] Quinny899:
Goddammit of course 😂

I'll fix it later
[Android Apps and Games] Quinny899:
Pushed 1.6.2 with that fix

Download from GitHub releases as usual
[Android Apps and Games] Bxperiaz3:
Is there a way to show the loyalty cards in the space under the regular cards? Mine appear at the end of the row cards and I keep having to scroll to the end of the normal debit cards to get to it, if that makes any sense.
[Android Apps and Games] Quinny899:
Nope, only one row
[Android Apps and Games] Swap_File:
I never tried using loyalty cards before, so I decided to give it a try.

I'm only seeing one Loyalty card show up in the app (1.6.2), and only one shows up in the "Rearrange and hide" screen.

Do I need to do something special to get all of them to show up?
[Android Apps and Games] Bxperiaz3:
Thanks. I'm sure I had it underneath before but not to worry. You can't make the loyalty ones show first which is a shame.
[Android Apps and Games] Quinny899:
Below is usually where the home controls go.