Hello,
Recently my bank (ING) has enabled NFC payment, but it seems not to work with CM13 (nightly). I've try to disable root from dev options and installing root cloack module to xposed. They didn't work.
Any ideas how to make it work?
Thanks
kno said:
Hello,
Recently my bank (ING) has enabled NFC payment, but it seems not to work with CM13 (nightly). I've try to disable root from dev options and installing root cloack module to xposed. They didn't work.
Any ideas how to make it work?
Thanks
Click to expand...
Click to collapse
I have it working in cyanogen os 13, obviously with out root, not full tested because I'm waiting for new card.
jjrojo said:
I have it working in cyanogen os 13, obviously with out root, not full tested because I'm waiting for new card.
Click to expand...
Click to collapse
My cyanogen 13 comes with root. How do you unroot it?
Thanks
don't use CM nightly, use Cyanogen OS
Related
Guys, the CM14.1 build is now available for download from the CM team.
Get it here, now.
-- Source
Check above page for list of all devices with CM14/Cm14.1/7.0 ROMs. Have fun!
Any major bug(s) found on cancro for this build so far?
I'm on cm14.1 (official) in my mi4.....proximity sensor is not working....and vibration intensity option Is also not there.....fast charging is not working at all.....
chiwawa10 said:
Any major bug(s) found on cancro for this build so far?
Click to expand...
Click to collapse
CM14.1 fo xiaomi mi4 lte-ct bug the proximity sensor,
speaker sounds with wheezing, audio fx It does not react to changes...this is ****ty cm for mi4
yuriylink said:
CM14.1 fo xiaomi mi4 lte-ct bug the proximity sensor,
speaker sounds with wheezing, audio fx It does not react to changes...this is ****ty cm for mi4
Click to expand...
Click to collapse
???*???
Let's be easy on the Dev, as this is the initial stage of CM14.1 for Cancro.
So far I have faced issue with 'Auto-Rotate' feature, only. Would wait for a more stable build, later next week.
Cheers,
Sarat
Testing and last update works fine (20161115)
Enviat des del meu MI PAD usant Tapatalk
when flashing 20161220 nightly from 20161213, it says
failed to mount system: no such volume
e1001: failed to update system image.
the system partition is just untouched and i cannot upgrade to this version, how can i do now. anyone please help
Pokémon Go compatible?
Any idea if this is Pokémon Go compatible*? I tried the OASP Nougat build before without any luck, even fully unrooting the device didn't do the trick.
*Pokémon Go uses the safetynet framework which doesn't work with rooted devices.
Axeia said:
Any idea if this is Pokémon Go compatible*? I tried the OASP Nougat build before without any luck, even fully unrooting the device didn't do the trick.
*Pokémon Go uses the safetynet framework which doesn't work with rooted devices.
Click to expand...
Click to collapse
It does work, but not out of the box. This seems to have to worked for me:
Go settings -> about phone
Tap the build number 7 times to enable Developer Settings
Go to settings -> Developer options
Scroll down to Root access and set it to Apps
Install SuperSU and grant it root access
Go to settings in supersu and click the Full unroot option
Reboot phone
Go to settings -> Developer options -> Root Access and disable it
And that should be it I think.
Hi guys,
I hope you can give me a hint.
With ressurection remix or Lineage OS is everything Working fine. The only Problem is, that NFC doesnt work. In the dropdown Menue is a clean place, where the NFC button should be. With the rooted stock Rom NFC worked fine! Has anyone an idea?
Pieronie said:
Hi guys,
I hope you can give me a hint.
With ressurection remix or Lineage OS is everything Working fine. The only Problem is, that NFC doesnt work. In the dropdown Menue is a clean place, where the NFC button should be. With the rooted stock Rom NFC worked fine! Has anyone an idea?
Click to expand...
Click to collapse
If you're using the OpenKirin RR and Lineage builds, neither of those include NFC. (Some of the other supported devices don't have NFC support.) The OmniROM build does.
irony_delerium said:
If you're using the OpenKirin RR and Lineage builds, neither of those include NFC. (Some of the other supported devices don't have NFC support.) The OmniROM build does.
Click to expand...
Click to collapse
thank you!
Hi there,
I just got my K30 pro, and installed MIUI 12.1 by xiaomi.eu 20.7.9 Beta, which is Android 10.
I installed ANT Tester and it shows that Built-in ANT detected. I tried to unlock the Built-in, which normally done by Permission>Additional permission>use ANT hardware, unfortunately, there's no this "Additional permission" under ANT radio service app's permission tab.
On my previous One plus 7 pro with Oxygen OS Android 10, I can enable Permission>Additional permission>use ANT hardware.
So, I guess it's the MIUI's issue?
Any suggestions?
Regards
Bump
droople said:
Bump
Click to expand...
Click to collapse
Have you got ANT Radio Service app from Google Play? If so, go to that apps permission and set the additional permission there. If not, download it and then do the above.
grt67DFqyu said:
Have you got ANT Radio Service app from Google Play? If so, go to that apps permission and set the additional permission there. If not, download it and then do the above.
Click to expand...
Click to collapse
Hi thank you for your reply. Please check my first post, no options in miui eu 12 (Android 10), I attached the screen shot.
I guess you're using some asop OS.
bump
Bump
bump
bump
Found this horrible looking work-around:
How to enable ANT+ on K30 pro
Hi there, I just got my K30 pro, and installed MIUI 12.1 20.7.9 Beta, which is Android 10. I installed ANT Tester and it shows that Built-in ANT detected. I tried to unlock the Built-in, which normally done by Permission>Additional permission>use ANT hardware, unfortunately, there's no this...
xiaomi.eu
grt67DFqyu said:
Have you got ANT Radio Service app from Google Play? If so, go to that apps permission and set the additional permission there. If not, download it and then do the above.
Click to expand...
Click to collapse
What was the rom was this working in?
jbm76 said:
What was the rom was this working in?
Click to expand...
Click to collapse
It was a custom ROM, LOS based, probably crDroid.
This Module enables RAW Capture on the Galaxy A20 and Galaxy A20e, and changes the camera Hardware Level from Limited to Full.
RAW Capture is required for most GCams to work.
For information about GCam, go to this thread.
Click to expand...
Click to collapse
How does it work?
It works by replacing the library located at /vendor/lib/libexynoscamera3.so with an edited one. For reverse engineering enthusiasts, here is the patch applied to the library.
Prerequisites
- Magisk v20.4 or newer
- Android 11 vendor and kernel (Not compatible with versions of the Eureka Kernel older than 9.0)
Installation
Install as a normal Magisk Module, through Magisk Manager or TWRP.
Troubleshooting
Camera doesn't work, shows Black Screen
Make sure you are using a compatible Android 11 kernel and vendor.
If this issue is happening after updating your firmware, please let me know.
Telegram
GitHub Repo
Download (Galaxy A20)
Download (Galaxy A20e)
great job, you should do one for the custom roms, i'm stuck on the samsung one cause this mod only works there, when i install in other roms the camera stops working
Arthurcfsousa said:
great job, you should do one for the custom roms, i'm stuck on the samsung one cause this mod only works there, when i install in other roms the camera stops working
Click to expand...
Click to collapse
In which ROMs have you tried it? It should work on any as long as they use an Android 11 vendor and kernel.
TBM 13 said:
In which ROMs have you tried it? It should work on any as long as they use an Android 11 vendor and kernel.
Click to expand...
Click to collapse
i tried on all android 11 custom roms really, lineageos dotos etc
Arthurcfsousa said:
i tried on all android 11 custom roms really, lineageos dotos etc
Click to expand...
Click to collapse
Did those ROMs ask you to flash a custom kernel/vendor? If that's the case i'd suggest to try in phhusson's AOSP GSI with stock Android R kernel and vendor.
I can't test it on my phone right now as i don't have enough free space to make a TWRP backup.
TBM 13 said:
Did those ROMs ask you to flash a custom kernel/vendor? If that's the case i'd suggest to try in phhusson's AOSP GSI with stock Android R kernel and vendor.
I can't test it on my phone right now as i don't have enough free space to make a TWRP backup.
Click to expand...
Click to collapse
I installed the GSI version of dotos and It worked! Thanks
After I flash and all of my phone's cameras is disappear. I'm using this rom
[ROM][12.0] DerpFest for Galaxy A20/A20e [OFFICIAL][a20/a20e]
This is a small project based on AOSP. We try to be a platform for beginners and support the Custom ROM community with our own unique contributions as well. This ROM exists thanks to inspiration of AOSiP, Thank you! #StayDerped /* Your warranty...
forum.xda-developers.com
ComefromVN said:
After I flash and all of my phone's cameras is disappear. I'm using this rom
[ROM][12.0] DerpFest for Galaxy A20/A20e [OFFICIAL][a20/a20e]
This is a small project based on AOSP. We try to be a platform for beginners and support the Custom ROM community with our own unique contributions as well. This ROM exists thanks to inspiration of AOSiP, Thank you! #StayDerped /* Your warranty...
forum.xda-developers.com
Click to expand...
Click to collapse
The kernel used by that ROM is using the camera drivers from Android Q, that's why it's not compatible with this module. You will have to use another kernel or build its kernel without this commit.
Edit: This module may work with the OneUI 3 variant of the Eureka Kernel, but you will most likely run into some issues. Feel free to try it and tell me if it worked or not.
Screenshots
Thread updated. Added module for the Galaxy A20e.
Version 2.1 of the module released, the biggest change is that there is no longer a need to change the Black Level in GCam settings, so GCams (or other camera apps) that don't have this option should now take photos without pink tint.
Full changes can be found here.
@TBM 13
Hi, i am a member of the Eureka Team. As you may know, we make AOSP ROMs too, but we were using Q camera blobs on our vendor, till now, and we are going to switch to R camera blobs.
I'm wondering if we can use this module's library for our team's roms, we will credit you correctly. On our posts and etc.
Royna said:
@TBM 13
Hi, i am a member of the Eureka Team. As you may know, we make AOSP ROMs too, but we were using Q camera blobs on our vendor, till now, and we are going to switch to R camera blobs.
I'm wondering if we can use this module's library for our team's roms, we will credit you correctly. On our posts and etc.
Click to expand...
Click to collapse
Sure, go ahead.
Some photos i took with Arnova's GCam 8.1, using HDR+
no android 10 support ?
im willing to downgrade to get apps working from sd card
cimon666 said:
no android 10 support ?
im willing to downgrade to get apps working from sd card
Click to expand...
Click to collapse
If you use Android 10 with an 11 vendor it should work fine. I don't know if it's possible though, maybe with PHH's GSI.
Do you work on this model?
a20 205f
Do you work on this model?
If it works please give me the right way to do it
Elsayed111 said:
Do you work on this model?
If it works please give me the right way to do it
Click to expand...
Click to collapse
Yes, the module should work on any A20 and A20e model. Install it through Magisk.
TBM 13 said:
Yes, the module should work on any A20 and A20e model. Install it through Magisk.
Click to expand...
Click to collapse
Thanks man, it worked successfully
The otg function works fine without rooting but after rooting it doesn't work. My otg settings is also active still not working. Can anybody please help
What method you used to root Android?
jwoegerbauer said:
What method you used to root Android?
Click to expand...
Click to collapse
The magisk method which is given in xda forum
Any updates anyone?
I've been using for a long time Magisk 23.0 stable from https://github.com/topjohnwu/Magisk/releases/
I have had no issues with anything (Google Pay and banking apps all ok), so I would recommend that version.
The issue is resolved. It was due to the Elemental X kernel which was not supporting otg. Once flashed another kernel all issues were resolved. Thank you .