Develop Bugs

LineageOS and Barclays apps

Hi. It looks like all barclays apps are not working on LineageOS any more. They find the phone rooted all of a sudden. Does anyone know of a solution??

Mine started playing up with the update on the 29th. But not sure if this is a Lineage only issue. Many users in the play store comments, saying the same thing. Can't get any further than the initial splash screen. No error codes or anything.

My girlfriend has her Oneplus One with LineageOS and since the last Barclays app update last week version 1.48, the app get always stuck during the loading screen. It was working perfectly fine. Updated LineageOS to latest version but no change, cleared Barclays app cache and data, still no luck. Cleared cache partition, no change.
The phone is not rooted, so Barclays app simply became incompatible with LineageOS since the last update on their app.

Yup same problem, I spoke with Barclays on the phone and on twitter....got nowhere.

my GF is trying support with Barclays over facebook, was told to call the support line after a while troubleshooting

Make sure she mentions the Play Store comments, to show this is not an isolated thing.

she called support and they mentioned they know already about this problem and are working to resolve it

Same issue here. Thought It was a ROM issue, thanks for clarifying.

Pommy192 said:
Same issue here. Thought It was a ROM issue, thanks for clarifying.
Click to expand...
Click to collapse
Not necessarily, several other phones with their original firmware are having the same issue.

Just to ad I found this thread for the same reason
Latest LineageOS , LG G4, Launch barclays it asks for call permissions - Granted, it then hangs on Barclays Logo
I know it doesnt work with root access and always moans i dont have AV installed when I do (maybe its looking for kaspersky that they promote)

I'm on the latest LineageOS update, LG G4. Even did a full factory reset with no luck.

I think this will not change, barclays has not updated their app in a while since this problem started and I reported a few times it to them, perhaps I'm the only one doing it

I've tried a couple of times, but they dont seem all that bothered. They are not even bothering to address the comments on the play store.

Gigabit88 said:
I've tried a couple of times, but they dont seem all that bothered. They are not even bothering to address the comments on the play store.
Click to expand...
Click to collapse
I've found it much easier just to use the Barclay's Mobile Banking site via a browser, they're not interested in fixing the app for rooted users.
It's secure and requires you set up a secret word, which during login, will ask you for a couple of letters from in a random order, over and above your passcode and form account details.
https://bank.barclays.co.uk/olb/auth/MobiLoginLink.action

mines not even rooted though? I lost root with the image, it normally moans about root but this is different I stuck on another image and it worked fine grrr
---------- Post added at 11:11 AM ---------- Previous post was at 11:01 AM ----------
This may fix it - let me know
https://www.reddit.com/r/LineageOS/comments/6vi5bp/heres_how_i_got_the_barclays_app_to_work_on_my/

So the new update to the Barclays app now thinks my LineageOS is rooted, when its not.

Gigabit88 said:
So the new update to the Barclays app now thinks my LineageOS is rooted, when its not.
Click to expand...
Click to collapse
same here. was working fine (on oneplus one lineage os 14.1), then barclays update the app to 1.48 and it started hanging at the splash screen. barclays app has been updated again to 1.52, but now thinks my phone is rooted.

Yup, Barclays have blocked LineageOS users on purpose. Why? Because they hate root access and in May an update to LineageOS could successfully hide root from any application (barclays included) as it changes the permissions on the su binary.
More details about that here:
https://lineageos.org/Changelog-9/
Thus, what did Barclays do? Well because they cannot check if device is rooted or not reliably with LineageOS, they decided to block the OS all together so now it simply checks if the device is running LineageOS.
It sucks, but it's the way it is. I've simply removed the Barclays app from my phone - A choice between Barclays app on Stock Rom running old android version and LineageOS with latest security updates? Well LineageOS wins.

The new barclay's update says "We're working to fix the problem with our app detecting some Android devices as rooted". They might change something for someone, can anyone confirm that this update fixes something? I would not be able to test it until tonight when arrive home, since it is my gf phone the one with lineage.
Cheers!

Nope, still detecting as rooted.
Nexus 6 - Lineage 02/02/2018

Android Pay Problem - error?

Hi guys
Few days ago came my Mi6, I flashed xiaomi.eu rom (it came factory unlocked) and got a problem:
my Android Pay doesn't work, my bank is mBank (Poland), supported by Android Pay.
The problem is that when I try pay by phone, terminal beeps 2 or 3 times like the card is unreadable or anything else (no idea).
Miui 9, TWRP, Magisk, Unlocked Bootloader
In attachments screenshots from Android Pay app and Settings app.
Any ideas what's wrong?
EDIT:// Magisk SafetyNet: Passed

Dose safetynet pass?

Switch NFC off and on. It worked for me in an identical situation.

Hi, did you ever find a solution for this? Having the exact same problem in the UK on MIUI Global 8.5

Also having same issue but with the Barclays app. 3 beeps and card error message

Solved - Working Non Stock Rom for Android Pay on M8

I am looking for any ROM that can be installed and allows Android Pay to work. I sometimes forget my wallet and would like to have the ability to use Android Pay. I was excited when I got AICP to install and pass safety check, but it doesn`t actually work at the terminal. I now read that all AOSP based roms have problems with NFC payments.
Does anyone have this working on an M8. There are some old threads, but none that actually report that it works.

Are you rooted with Magisk?

redpoint73 said:
Are you rooted with Magisk?
Click to expand...
Click to collapse
Yes. So far I have tried AICP 7.1 Rom, which passed safetynet check, but would not actually work on a store's terminal. Perhaps an NFC issue with AOSP Rom? I also tried Lineage 15, but could not get it to recognize google play services and could not get the play store to work as a result. I am now on lineage 14.1, which agains passes safetynet check but will not work at the terminal.
As I am aware, Magisk only allows Android Pay to be installed, but when it comes time to validate the purchase, there is either an NFC problem or something prevents the purchase from being validated.
So if anyone has a non stock rom that works with android pay on the m8, I would like to know about it. There have been a few threads, but none seem to offer a current resolution.

I'm not personally a user of AOSP ROMs, nor Android Pay, so my advice is limited. Just chiming in, as long as you are passing SafetyNet, and have Magisk Hide enabled (in Magisk Manager settings) than I don't think it's a safety net or root issue. Like you said, it might be an issue with AOSP ROMs and NFC.

I tried Resurrection Remix. Same result. Passed safety check but would not work at the store terminal.

Cannot use payments on nougat. Have to go to marshmellow.
NFC works, but HCE does not, which is whats required.

Success. I went to ViperOneM8 6.1.0. Installed the rom. Then deactivated Su in the Su app. Then properly installed Magisk by creating a new boot.img file and then flashing that new boot.img file with twrp. Magisk 14 showed safetynet passed both test. Off I went to the store to buy a chocolate bar, unlocked the phone, tapped it on the terminal and buzz buzz, payment approved. Very nice.

Android Auto Broken for me since Oreo! Problem persists across OOS and Custom Roms!

I am having major issues with android auto since Oreo
Essentially, what is happening is that the Android Auto app itself will work with two and only two apps. They are Google Maps and Google Play Music.
My problem is, none, and I truly do mean no other 3rd party apps will work with Android Auto.
I should also restate that this is a problem with the Android Auto app itself, so let's pretend no head unit or car is involved. This can be replicated on just the phone.
Here's the behavior:
-Open android auto
-Open any 3rd party app (Let's say IheartRadio)
Either one of two things happen next:
-Instantly get a screen that says "IHeartRadio Doesn't Seem to Be Working"
OR
-IHeartRadio starts like it should, and is able to play music for about 15 seconds, and then I get "Doesn't seem to be working" screen
-This happens for every 3rd party app, not just IHeart, but Plex, TuneIn, Radio Scanner, EVERYTHING except Google Play Music and Google Maps.
I should also state that Android Auto and 3rd party apps worked without a hitch, absolutely flawlessly in Nougat.
And, I've asked around the OP5t forums here and nobody is having the same problem.
-------
What I've tried so far (And hasn't worked)
-Re installing Android Auto
-Re installing every 3rd party app and re-trying
-Installing a custom ROM (Oreo) (Same exact behavior right after factory reset flashing new rom )
-Tried installing 3rd party apps from a non google play source
-Flashing OOS 8.0 Stable, as well as OB4 thru factory wipes
What I haven't tried:
-Re-locking the bootloader and flashing back to OOS nougat (Would this even help?)
I'm totally at wits end here, folks. I bought the OP5t to accompany my new car as my old phone couldn't handle android auto, this is one of the most imporatnt features to me.
Does anyone have any suggestions? Would flashing back to nougat and locking the bootloader like the phone was brand new help me? I've never seen such a problem that persists through clean flashes.
Thank you kindly everyone,

Hey!
I had this exact same problem.
I managed to solve this.
I am on OOS Open Beta 4.
Install latest:
Android Auto:
https://www.apkmirror.com/apk/google-inc/android-auto/
Android System Webview:
https://www.apkmirror.com/apk/google-inc/android-system-webview/
Google Maps:
https://www.apkmirror.com/apk/google-inc/maps/maps-9-74-0-release/
Google App:
https://www.apkmirror.com/apk/google-inc/google-search/google-search-7-23-24-release/
Google Play Services:
https://www.apkmirror.com/apk/google-inc/google-play-services/google-play-services-12-2-21-release/
After installing all the apps, reboot your phone.
Android auto should work smooth again!

Just FYI, the bootloader status (locked/unlocked) has nothing to do with this.

Nick502 said:
Hey!
Android auto should work smooth again!
Click to expand...
Click to collapse
Hey there, first and foremost, thank you so much for taking time to respond! I tried your suggestion, but I'm still not having any luck
I'm going to keep messing around with it, but thank you again for the reply.

captainstarbucs said:
Hey there, first and foremost, thank you so much for taking time to respond! I tried your suggestion, but I'm still not having any luck
I'm going to keep messing around with it, but thank you again for the reply.
Click to expand...
Click to collapse
Ohh that is really weird. Make sure you install all the Google Beta apps, and also the latest Android Auto version.
Are you using the Red Dash cable?

Nick502 said:
Ohh that is really weird. Make sure you install all the Google Beta apps, and also the latest Android Auto version.
Are you using the Red Dash cable?
Click to expand...
Click to collapse
Yes, I'm using the dash cable that came with the phone, but this problem is isolated within the android auto app. I don't need to connect it to the car to get the issues I'm having. Just launching the app on the phone itself and starting up a 3rd party app will trigger the "seems to not be working" screen.
If I connect it to the car, the same behavior happens. No issue with the connection to the car since I'm still able to use Maps and Play.
I'm considering flashing back to nougat to see if it works and OTA'ing til I get stable 8.0 and dirty flashing OB4 today.

UPDATE!!!
I got it working, and how I fixed it was a total PITA, but it works and I'm on OOS OB4.
Here's what I did:
1. Download the first available nougat OOS and flash it. Factory wipe from stock recovery. Once booted, install android auto and 3rd party apps. Test if it works, if so...
2. Sign in google account and update to 5.0.4 via OOS updater
3. Once rebooted into 5.0.4, take OB4 and stick it onto root, and reboot to recovery again
4. I dirty flashed OB4 over 5.0.4 and it seems to work fine!
I haven't tested this in my car yet, I will be on a long drive tomorrow and update results.

Waze on android auto
Waze is working parallel to google Maps without any problems. When you open navigate both programs are shown.

Damn I just noticed it. My maps work but I tried to open Google play music and got the same error.

That was the one thing that consistently worked for me. Which rom are you on?

Question [rooted device] Galaxy wear 4 not connecting

I was recently able to root my Oneplus 9 Pro, after getting all my data back on getting my device at least usable I decided to try and set back up my watch. I keep being unable to connect. I've blocked galaxy manager/wear from magisk and I've hit a brick wall any advice?

drybonesification said:
I was recently able to root my Oneplus 9 Pro, after getting all my data back on getting my device at least usable I decided to try and set back up my watch. I keep being unable to connect. I've blocked galaxy manager/wear from magisk and I've hit a brick wall any advice?
Click to expand...
Click to collapse
you most likely need to hide magisk from more (or all) google related apps and services on your device. had the same issue with me. i'm pretty google based sign in would also not be working for you in this situation. the solution for me was to re rehide magisk from everything.

That's what I originally thought and was racking my head against it. This is the only this I can't get working post root. I saw Samsung devices have a Bluetooth patch when searching but no universal patch, at least I can't find one

drybonesification said:
That's what I originally thought and was racking my head against it. This is the only this I can't get working post root. I saw Samsung devices have a Bluetooth patch when searching but no universal patch, at least I can't find one
Click to expand...
Click to collapse
is safetynet passing for you?

Seems to be so, everything other then my gear manager is working as intended

For me on a13 the galaxy wear app just crashes while trying to connect (non root)