Related
Hi!
I've written another Xposed module for my LEX720 for a very specific purpose, so probably it won't be of much use for the most. But I'm still publishing it for reference reasons.
Background:
First the good news: The stock firmware of LeEco includes the "SmardcardService" (which also often is referred to as "Open Mobile API" or short "OMAPI") which is an extension API to plain Android (i.e. not existing in the Nexus devices or the Pixels) to allow apps accessing Secure Elements (i.e. secure applications embedded in a tamper-resistant hardware) within the SIM-card.
A real world example: in Austria some banks (in cooperation with the 3 largest network operators) support Tap'n'Pay with your phone by installing the NFC-capable banking card as an additional application into the SIM card (which is the same secure chipcard technology as a banking card). This means you get a new SIM card and then you can tap'n'pay with your phone (without Google, without VISA or MasterCard, just as with the Austrian NFC banking cards). AFAIK in some other countries the same concept is used for public transport and others.
The main difference to Android Pay is, that this system is backed by the chipcard (the SIM) and not by a cloud service. But this just as background information.
The problem:
The LEX720 is a dual-sim phone, and so the (banking) apps could read SIM-cards from either SIM1 or SIM2 slot (I tested, SmartcardService works with both). But if you also want to use NFC for payment it has to be inserted into SIM1 (as it seems that only the SIM1 slot ist connected over an SWP line to the NFC chipset). Unfortunately the Austrian banking apps don't seem to handle the dual-SIM situation correctly and only try to read SIM2 (which is empty for me) and therefore don't work.
Additionally, at the end of an transaction, when the application running within the SIM card signalizes that it just had finished a payment transaction to the Android system, the NFC service (/system/vendor/app/NQNfcNci/NQNfcNci.apk) broadcasts this message as an intent to the relevant (banking) app, so that the app can display a transaction result activity.
Unfortunately this mechanism is implemented often very different by different OEMs and so also by LeEco. There exists a standard (GSMA NFC Handset APIs Requirement Specification) but it seems there are a lot of different implementations in the wild.
(Note: this is probably the case because this type of functionality is not part of the official reference Android source code. Plain open source Android like it is running on all Nexus phones and the Pixels just doesn't support these type of applications - which is very unfortunate).
My workaround:
TL;DR I just made an Xposed module which fixes these 2 issues for me. Look into the README on Github for more details.
Source on Github: https://github.com/johnzweng/XposedOmapiBankcardFix
Download Xposed Module: Xposed-module-OMAPI-BankcardMobil-Fix-1.1.apk
Maybe it's also useful for other applications which use the SIM card as secure storage for keys of any type. Use at your own risk.
As a reference: these are the Austrian banking apps this module should work with:
Bank Austria Mobile Geldbörse
BankCard Mobil
Oberbank Bankomatkarte Mobil
Raiffeisen ELBA-pay
VKB-Pay - Bankomatkarte mobil
The module might also help to get other similiar apps working which have problems with Dual-SIM or don't show Transaction confirmation screens. I am talking here about apps which use a special SIM card for payment, ticketing or similiar use-cases via NFC. This has nothing to do with "normal" NFC apps or cloud-based HCE (host card emulation) NFC apps. This module is only for apps which use special SIM cards.
[edit]
Updated download link to version 1.1.
For details see the CHANGELOG in the Github repoistory.
[/edit]
Btw, during debugging I noticed another small bug in the LeEco NFC service:
The package com.android.nfc (/system/vendor/app/NQNfcNci/NQNfcNci.apk) declares a permission which allows apps to receive Intents about EVT_TRANSACTION events. On the LeEco LePro 3 (LEX720, running 5.8.018S, WAXCNFN5801811012S) this permission looks like this
Code:
declared permissions:
com.gsma.service.nfc.permission.TRANSACTION_EVENT: prot=dangerous, INSTALLED
You can check this easyily yourself with this adb command:
Code:
adb shell pm dump com.android.nfc > dump-nfc-service.txt
This will dump all infos into a file named dump-nfc-service.txt. Open the file with an editor and search for "declared permissions:".
The problem with this permission is, that its name is missing a letter!
Correctly it should be called: com.gsma.services.nfc.action.TRANSACTION_EVENT (note the missing "s").
This is specified in the GSMA NFC Handset APIs Requirement Specification (see at the top of page 13 in the PDF)
Funny enough the specification in the PDF also contains a typo in the very same permission name the Intent action name (the dot "." after the word "gsma" is a comma "," in the PDF). It must be really hard to type this correctly.
Nevertheless this typo leads to errors like:
Code:
W/PackageManager( 2357): Unknown permission com.gsma.services.nfc.permission.TRANSACTION_EVENT in package ......
and prevents applications of requesting the correct permission.
Does anybody know if and how it's the best way to report bugs to LeEco?
[edit1]
I contacted them on Twitter. I hope they will forward this issue to developers.
Btw, it seems that also LG had included the same typo in some of its devices:
Devices without the "s": https://census.tsyrklevich.net/permissions/com.gsma.service.nfc.permission.TRANSACTION_EVENT
vs.:
Devices with the "s": https://census.tsyrklevich.net/permissions/com.gsma.services.nfc.permission.TRANSACTION_EVENT
[/edit1]
Hi androcheck,
first i am really impressed that somebody found a solution for that problem (i already have several posts with no answer at all)
But now i have a problem as when i install the fix i stuck in a boot loop. Is this maybe cause i am on custom ROM (Turbo MIUI) ?
Hope you have an idea
thanks
Robert
viercp said:
Hi androcheck,
first i am really impressed that somebody found a solution for that problem (i already have several posts with no answer at all)
But now i have a problem as when i install the fix i stuck in a boot loop. Is this maybe cause i am on custom ROM (Turbo MIUI) ?
Hope you have an idea
thanks
Robert
Click to expand...
Click to collapse
So far seems a "one time bug" - all ok with patch but i still get the very same error mssg
Any poss to tell me where i can check if entries provided by fix are really done ?
viercp said:
So far seems a "one time bug" - all ok with patch but i still get the very same error mssg
Any poss to tell me where i can check if entries provided by fix are really done ?
Click to expand...
Click to collapse
Hi!
Sorry for the delayed answer.
First of all the ROM you are using must have the SmartcardService (=implementation of OpenMobile API), the corresponding library (org.simalliance.openmobileapi.jar) and permission manifest (org.simalliance.openmobileapi.xml) installed. I downloaded miau_destroyer_v12.zip from this thread here, extracted it and it seems that it contains all three of them.
My Xposed module "XposedOmapiBankcardFix" doesn't do very much besides forcing the apps which are using the OpenMobile API to always use "SIM1" as SmartcardReader. This was necessary because at the time of writing the Bankcard apps in Austria from PSA (Payment Services Austria) didn't correctly check for multiple SIM slots. So in fact this was a bug in the PSA apps, not in the phone.
Back then I reported this back to the developers (of the banking app) and today it seems to be fixed (I didn't check in detail but the Bank Austria app now is working for me on Android 7 without Xposed installed - with the SIM inserted in slot 1).
Another point I realized: By looking into the build.props of the miau_destroyer_v12 ROM it seemed to me that this ROM is configured for single SIM use. This means that the SmartcardService also only sees one cardreader (SIM slot). Maybe this also interferes with the Xposed module?
For clarification:
Before I wrote my Xposed module, the Bank Austria banking app worked already perfectly (no errors displayed, recognized the NFC SIM card, personalization of the bankcard worked ok) when I inserted the SIM card into slot 2. It just didn't work when the SIM card was inserted in slot 1. The problem is that it must be inserted in slot 1 if you want to use it over NFC. This is why I decided to work around this limitation with my Xposed module.
The second feature ("Fix EVT_TRANSACTION Intent") of my module was just a gimmick "on the way". I realized that the confirmation dialog after paying is not displayed, but this was just a "cosmetic" problem. Payments did still work, even if the confirmation dialog on the phone is not displayed.
Another sidenote:
As I have mentioned before I have switched already to an Android 7.1 based ROM on my personal phone (as a developer I want to use some of the new APIs) so I don't have Xposed anymore (as Xposed is not available for Android 7). So at the moment I cannot really test anything.
Which error exactly do you get? What do you see in logcat?
Kind regards,
john
androcheck said:
Hi!
Another point I realized: By looking into the build.props of the miau_destroyer_v12 ROM it seemed to me that this ROM is configured for single SIM use. This means that the SmartcardService also only sees one cardreader (SIM slot). Maybe this also interferes with the Xposed module?
Click to expand...
Click to collapse
Changed in build.prob to enable Dual SIM
Which error exactly do you get? What do you see in logcat?
Click to expand...
Click to collapse
Havent worked with before - which entry you are looking for ?
Lot Of Thanks for your great work！
Btw,Do you use AOSP 8.1(such as AICP8.1)
On these roms,after add SmartCardService.apk ,it still cann't work with these bank apps. Actually,it can read other nfc tags,but it's HCE (Host-based Card Emulation) can not work
Could you have a try to fix it?
My post:
https://forum.xda-developers.com/le...a-zl1-x727-x720-t3698058/page356#post76274677
Hi,
Google says that Pixel 7 series don't support SWP-SIM while Pixel 6 and others supported.
So I started googling that if there's any 'Magisk way' to solve this issue, then I find your xda posts.
If you happen to be a Pixel 7 user, are you interested in looking into this issue?
I'd like to buy you a $30 coffee or more if I can use the SWP-SIM for payment on my Pixel 7.
jasonlee0315 said:
Google says that Pixel 7 series don't support SWP-SIM while Pixel 6 and others supported.
So I started googling that if there's any 'Magisk way' to solve this issue, then I find your xda posts.
Click to expand...
Click to collapse
Hi!
I don't have Pixel 7 and currently I am not working in this field, but for clarification:
"SWP-SIM support" is (also) a hardware feature.
To be able to use SWP-SIMs there must be a physical connection between the SWP pin of the NFC controller (this is a separate chip on the mainboard of your phone, not the main application processor, where Android runs on) and the respective pin of the SIM card slot.
Google in the past tended to not connect these 2 pins. I don't know if the Pixel 7 has this connection. I just wanted to let you know, that if this connection does not exist, there is no way to solve this in software.
[edit]
(see also this old question on stackexchange, this was about the Nexus 5X and 6P: https://stackoverflow.com/questions...-to-the-uicc-on-the-nexus-5x-and-the-nexus-6p)
[/edit]
androcheck said:
Hi!
I don't have Pixel 7 and currently I am not working in this field, but for clarification:
"SWP-SIM support" is (also) a hardware feature.
To be able to use SWP-SIMs there must be a physical connection between the SWP pin of the NFC controller (this is a separate chip on the mainboard of your phone, not the main application processor, where Android runs on) and the respective pin of the SIM card slot.
Google in the past tended to not connect these 2 pins. I don't know if the Pixel 7 has this connection. I just wanted to let you know, that if this connection does not exist, there is no way to solve this in software.
[edit]
(see also this old question on stackexchange, this was about the Nexus 5X and 6P: https://stackoverflow.com/questions...-to-the-uicc-on-the-nexus-5x-and-the-nexus-6p)
[/edit]
Click to expand...
Click to collapse
Thanks for replying. I guess I might give up trying to get SWP-SIM working on Pixel 7.
Hey guys! I'm not sure if I should post this thread in the Poco F1 section, the WearOS section or the NFC section, so I'll try it here first.
Like the title says, my bank application denies adding my credit card to Google Pay on the Poco F1, probably because of it's missing NFC chip. The thing is: I want to use Google Pay with my Fossil Gen 5 smartwatch and not with the phone itself.
It's worth mentioning the phone has Magisk installed and I'm using the Pixel Experience ROM. I've hidden the Magisk Manager package and I've activated Magisk Hide for several packages but it didn't change the outcome. I tried the same Magisk settings on a Samsung Galaxy S7 Edge (which has a NFC chip) and adding the card worked flawlessly. The customer service of my bank also told me the problem is most likely the missing NFC functionality of my phone. Too bad the watch is synced to the Poco F1 and I want to keep it that way. Now I'm running out of ideas.
Is there a way to make apps think the phone comes with a NFC chip?
Can I use this method to temporarily sync my watch with the S7, add my card and then switch back to the F1 without losing any data?
Thank you for your time.
If anyone is still (trying) to use daydream on normal devices, I'm going to share my experiences with getting it to "work" in a redmi note 4 (sd625 variant), along some other problems I do still face.
First of all, you need to know that daydream is designed to have always reprojection on, if you don't know what that is, take a look at this. This means that unless you have an oled display, with their inherit characteristics (low persistence), or an lcd that's capable of doing 90hz or more, you're going to experience a lot of motion blur with fast head movements or circular movements. That's not a bug, it's how it's supposed to work, that's why if you go check the list of official compatible daydream phones all have oled displays. The benefit of that blur is the buttery smooth head tracking, use it for 5 min, and you won't be able go back.
Once you have prepared your stomach for the ride;
1st: You need a rooted device (easiest method is flashing with a custom recovery the latest magisk version). You might be able to avoid rooting if somehow you manage to modify the files in the next steps, but at least for me, to access those files I needed root permissions.
2nd: Go to the play store and just search for daydream (do not install it), if you're able to see the app, you could jump to the next step. If you don't, download a file explorer with root capabilities (I personally like fx explorer) and paste the "android.hardware.vr.high_performance" file attached to the following route;
Code:
/system/vendor/etc/permissions
.
In this same folder you'll find the handheld_core_hardware that's mentioned in other guides, you might be also capable of getting it working by editing handheld_core_hardware, just like the old tutorial said
3rd: In order to get most of the daydream apps to render in SBS mode or even open, you need to spoof the id of your device to one of the certified ones. This is exactly the same step contained in the tutorial above, but at least in my case, once I opened the build.prop in the /System folder, I didn't saw a "ro.product.device", but a "ro.product.system.device". What I did was modify the latter by changing "mido" (the name of my device) to "walleye" (pixel 2) and adding a new line with "ro.product.device=walleye"
4th: Restart your phone and install Daydream, google vr services, and daydream keyboard all three from version 1.13. Daydream
Google vr services
Daydream keyboard
This version, along with 1.14 are the last ones that at least in my phone don't distort the aspect ratio, making it all squezzed. Version 1.14 has some handy implementations but worse performance and the lack of a developer option that I find really interesting for our unsupported phones that I will mention later.
5th: Now that's all installed, open the app and it will tell you that it need some permisions to work, press cancel and it will exit itself. go press it again and this time you'll see the daydream menu, swipe to the right to open the side menu, go to settings, VR settings, and if you don't have developer options, press compilation version several times to make them appear. Once you're inside those developer options, check the "skip VR entry screens". This is essential for all of us that don't have nfc, otherwise we wouldn't be able to run any app.
6th: Go to to visor and select your daydream version, bare in mind that if want to use a controller, you'll need to chose between gen1 and gen2, as cardboard custom profiles gray out the controller.
7th: Go to the controller tab and press and new controller, you'll be asked to fix the permissions, by enabling bluetooth, gps, and location you should be good to go, but considering we are using google play and google already knows all about us, I would say go ahead and try go give all permissions, just in case some specific app requires them.
Now follow the tutorial and the controller should pair... or maybe not. This is one of the problems that I don't know how to fix. The controller appears to be paired, as the light no longer blinks, but the daydream app doesn't detect it. At least for me, I couldn't get it to work in android 7 or 9, android 8 I (think?) I managed to get it working, and all android 10 roms I tried worked fine. I suspect it has something to do with the bluetooth settings, as it's a low energy device.
8th: You're good to go. Depending on your display and calibration, you might want to download an app called sa2ration that allows you to boost the intensity to get a more vivid image, I personally use 1.25 and it works wonderfully. Bare in mind that this works system wide, you could toggle it on and off whenever you want, and the settings don't reset with phone restarts.
---------------------------------------------------------------------------------------------------------------------------------------
Now that everything is "working", If you want to avoid the blur, and the app you're going to use is capable of holding a steady 60fps, you could go to developer setttings, and tick the "Force undistorted rendering". This will supress most of the motion blur at the cost of smoothness. This for me also reveals another problem, the resolution/dpi settings, as the image "bleeds" outside the supposed rendering area.
@Retrete: THX for your hints.
Any xiaomi/redmi or oppo/realms device you can recommend? Is the experience as good as on official daydream phones?
I remember that on my axon7 the amoled needs to be switched to low persistence mode via fw command.
---------- Post added at 08:22 PM ---------- Previous post was at 08:21 PM ----------
[/COLOR @Retrete: THX for your hints.
Any xiaomi/redmi or oppo/realms device you can recommend? Is the experience as good as on official daydream phones?
I remember that on my axon7 the amoled needs to be switched to low persistence mode via fw command.
hmn, i cant get to edit neither the build.prop nor the folder where i have to paste the vr file. I have magisk root, OnePlus 5T Android 10 OxygenOS 10.0.0
Redmi Note 9 Pro : I've had a lot of cell phones, but only on my Redmi Note 9 Pro does the following happen:
Miui 12 has a function "Automatically on/off speaker ...". But this only works with "talkback". For generations of mobile phones there have been extra programs for this function that either run separately or are built into audio recorders or phone apps. However, these apps do not work on my Remi 9. That was the reason why I rooted the device. However, there was no change. The rooting process had no effect. E.g. I would like to send an SMS to myself using "AutomateIt" when I receive an email. - But it doesn't work either. AI asks for permission to read emails. I give permission. Everything looks well, but if I check the permissions under "additional permissions" afterwards, no permission has been granted.
At first I thought it was due to AI - but I think it is due to Redmi n9: I tried to rename any file in the root - e.g. "media / mybootanimation.zip". A message appears that this cannot be carried out. Whereby it doesn't work with multiple explorers. If I change the rights of the file to "755", that doesn't work either
Accordingly, there is generally a write block.
Can someone tell me what to do to make this work?
Hint: Add "Redmi Note 9 Pro" to front of this thread's title thus owners of such a device get addressed.
Hi there.
Yesterday I received Nord 2 and I'd like to debloat it from non-useful software using ADB. Any of you could attach a list of apps is it safe to remove (or just disable) as it was for Nord 1? I tried to compare some system apps to those of that thread but they are not the same... thanks!
LS
labentia.signa said:
Hi there.
Yesterday I received Nord 2 and I'd like to debloat it from non-useful software using ADB. Any of you could attach a list of apps is it safe to remove (or just disable) as it was for Nord 1? I tried to compare some system apps to those of that thread but they are not the same... thanks!
LS
Click to expand...
Click to collapse
Propably all googl apps like youtube and crap + anythink you do not like
see here, and share your experience
I removed heytap cloud, red cable etc. Also removed youtube and such.
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
check out this.