Fair enough, I guess.
Itâs a bit flippant to dismiss a loss of established functionality as annoying. I find it a bit more than annoying.
Iâm sure you do, and I would too if I were using the app on /e/OS. But the fact remains that, for a number of reasons, itâs not a bug that qualifies as a âshowstopperâ or merits a new 1.n.1
release, which a: risks causing problems by the fix not being properly tested, and b: delays the release of the next scheduled version.
Thanks for the additional explanation, but youâve already stated its not a showstopper, and I donât dispute that decision or the rationale for making that decision. I also accept the fact that the new bug created by the update isnât going to be patched and weâll have to wait for a future update. Repeating that wasnât productive, I understood the first time.
What I donât accept is your flippancy around it being annoying for users. Itâs more than annoying to lose previously reliable functionality in a commercial product that I paid for, and was using day to day to support my work. Your unhelpful response is making me less likely to replace this e/OS phone with another.
I hope that better illustrates my level of dissatisfaction and hopefully youâll understand that this is more than a mere annoyance.
Firstly, none my posts in this thread were in response to you: there were responses to posts by @GreyLinux and @jdaviescoates .
Secondly, I really donât care whether you âacceptâ what you choose to see as flippancy, and what I choose to see as having a sense of proportion about what, in reality, and in the grand scheme of things, is a relatively minor problem. Feel free to not accept it - I can probably live with the consequences
Really? You would let your high level of âdissatisfactionâ with the comments of a forum user who has no formal connection to /e/ affect your decision about what phone and what phone OS to select? You clearly do see it as more than a mere annoyance, but you really might want to check out your own sense of proportion and perspective. The phrase âGet over yourself!â, springs to my mind for some reason.
You might also want to find out how easy it is to mute a forum user whose views, posts, or attitude upset , offend, or bore you. (Open that userâs profile, and select âMutedâ from the drop-down box which defaults to 'Normal`). I am about to use that facility Good night!
mobi.inthepocket.bcmc.bancontact
This app does not work on this OS e
It is the most widely used payment app in Belgium
It would be nice if this ever works out.
Only then I can inform friends about this fine degoogled daily use.
Is this the right place to ask this question?
ING (DiBa) App for Germany works well without restrictions.
It took longer than anticipated, but we finally finished our analysis of which all Slovenian mobile banks work with /e/OS as well as online banks (text in Slovenian)
Relevant for this thread is that the following bank apps work on /e/OS out of the box:
- Addiko bank â Addiko Mobile Slovenija (tested)
- Delavska hranilnica â DH Mobilni (tested) (note: their other app âDH Denarnikâ does not work though)
- DeĹželna banka Slovenije â mDBS (tested)
- N Banka â Mobilna N Banka (bank claims it should work, it is in Huawei store)
- Banka Sparkasse â M.Stik (is in Huawei store, should work, bank says they donât guarantee it though)
- NLB â Klikin (tested) (note: their other app âNLB Payâ does not work though)
- Nova KBM â mBank@Net & mDenarnic@ (tested)
- UniCredit Banka Slovenija â Mobila Banka Go! (tested)
In addition many banks use the following app for 2FA for their online banks as well as for 3D Secure:
- Rekono OnePass (tested)
For all Nationwide Banking app users the new update to /e/ 1.9 , fixes the app , it now works as expected.
LCL (Le Credit Lyonnais) works well without restrictions: v5.12.0
e1.9
RBC Canada working.
Was not working when I tested last I think e1.5.
Thanks, I just came here to say exactly that! Hooray!
Hi
Belgium:
- KBC mobile banking app works fine apart from the QR code reader. It has camera access but does not recognize QR codes.
I am on a FP3+
1.9.1-s-20230405276851-stable-FP3
I have a problem setting up my Triodos banking app for The Netherlands. Itâs the exact problem described in the list for the UK version. When setting up the app on a device with /e/OS it asks to install Google Play Services. But MicroG does what Google Play Services does, isnât that right?
I really want the Triodos banking app to work on my /e/OS device. What can I do?
Same problem here for the Dutch version.
Complain to Triodos.
I complained both that the app doesnât work on DeGoogled phones, and that you can only open new accounts using the app, both incongruent their stated ethical values.
I just sent an email to Triodos Bank Netherlands with my complaint.
Would you share their reply here? Much appreciated!
Will do. I think, when they are willing to re-activate my Digipass, I can register the app anyway and after that, use a pincode for further usage (within the app or at my pc). That happened to one of our fellows here, so I will try that too. I won´t go back to the stock Android in order to get the app working. Luckily, I have the app on the former phone, so I can do banking at the moment. I would be very frustrated if I had wiped that phone.
Perhaps this could help
Did this in a rom with MicroG and mobile pay was working
goto magisk setting enable zygisk and denylist after this on installation section install these two module https://t.me/UnmoveDsquad/1144?single
After this goto termux give root permission by typing " su "
Type props after this edit device fingerprints by typing 1
Select f
Select redmi
Select redmi note 10 pro
Reboot