Chase App doesn't work on new Samsung phones!!!

masonic

clarkey1984 said:

masonic said:

boingy said:

wmb194 said:

boingy said:

wmb194 said:

boingy said:

Am I the only person that think that a banking app should run on ANY 6 month old android phone?

No, not when the super cheap ones like the one in question, c.£50, has hardly any RAM and might have a 32-bit OS.

Banking apps are not heavyweight things. They don't require much in the way of memory or processing power. The lack of compatibility is a design decision on the part of the dev team. You could even call it laziness...

Banking apps should run on anything modern and they should definitely run on Android Go, given that many, many new phones are shipping with Go.

No, but the world's moving on from 32 bit and Go 12 isn't even the latest version (14).

Android Go 12 is only two years old. Banking apps should run on it. And it's not automatically 32 bit. It's designed to make the best of low spec phones, something that banking apps should seek to do too.

Banking apps would probably run on 64-bit Android Go. The reason modern apps don't work with legacy 32-bit operating systems is that the 32-bit architecture brings with it a limited instruction set, no native support for modern cryptography, a greatly increased code maintenance burden, and risk of vulnerabilities through working around the missing features. The more important security is for an app, the less sense it makes to compromise. App-only banks are at the extreme end of this, as they often lack some of the security features associated with website-based banking. Some rely entirely on the device for security. These are not the apps you want running with a portion of your CPU's capabilities switched off.

I gather from my limited knowledge that 64 bit is more secure than 32 bit, however ,my Barclays app installed and runs without incident, although I am yet to find a way of confirming if my android is one or the other.

One simple way to check is to download CPU-Z and that should tell you. Under System -> Kernel Architecture. A 64-bit OS should show something like "aarch64".

400ixl

boingy said:

wmb194 said:

boingy said:

wmb194 said:

boingy said:

Am I the only person that think that a banking app should run on ANY 6 month old android phone?

No, not when the super cheap ones like the one in question, c.£50, has hardly any RAM and might have a 32-bit OS.

Banking apps are not heavyweight things. They don't require much in the way of memory or processing power. The lack of compatibility is a design decision on the part of the dev team. You could even call it laziness...

Banking apps should run on anything modern and they should definitely run on Android Go, given that many, many new phones are shipping with Go.

No, but the world's moving on from 32 bit and Go 12 isn't even the latest version (14).

Android Go 12 is only two years old. Banking apps should run on it. And it's not automatically 32 bit. It's designed to make the best of low spec phones, something that banking apps should seek to do too.

Android Go is for developing markets where Chase UK banking app would not be available anyway. Very few phones for the UK market run Android Go.

Android will be dropping 32bit OS's soon anyway so putting development effort into supporting those when you had no legacy app that did is not sensible investment.

The likes of Samsung, Motorola, Sony etc should stop installing 32Bit OS's onto phones which are 64Bit capable. Unfortunately they are the ones causing issues for their unaware customers. They have been told not to be doing so on many occasions by Google.

boingy

400ixl said:

Android Go is for developing markets where Chase UK banking app would not be available anyway. Very few phones for the UK market run Android Go.

That's just not true. If you look at new phones in the UK under about £100 more of them run Go than don't. 
To take an example, one of the most popular budget phones at present is the Motorola E13. Released just over a year ago it's 64 bit, has a decent spec for the price and runs Android Go 13. Yours for about £70. The very lowest end smart phone finds an Alactel as the most popular. It runs Go 11. The lower end Samsungs also run Go. 

Don't assume that someone who buys a budget phone has no money. Often the very opposite is true.

400ixl

If you are buying sub £100 phones then they are likely to come with limitations. It is up to the purchaser to check it can do what they will need it to do. 

Android Go is for developing markets (thats why it was developed). They aren't restricted to there, and may well be sold in other countries. But I doubt they are even 1% of phones sold in the UK, So they are not popular across the UK demographic at all as you try to imply.

Where did I say anyone who buys a budget phone has no money? That is you putting words in other peoples mouths to try to prove your point.

Basically, buy budget to that degree at your own risk, as with most budget electronics there is a risk it does not perform all functions. Its the buyers choice and their consequences.

Its like saying I want to buy the cheapest new car on the market but expect it to have a DAB stereo system in it to listen to 5 Live. It won't.

clarkey1984

masonic said:

clarkey1984 said:

masonic said:

boingy said:

wmb194 said:

boingy said:

wmb194 said:

boingy said:

Am I the only person that think that a banking app should run on ANY 6 month old android phone?

No, not when the super cheap ones like the one in question, c.£50, has hardly any RAM and might have a 32-bit OS.

Banking apps are not heavyweight things. They don't require much in the way of memory or processing power. The lack of compatibility is a design decision on the part of the dev team. You could even call it laziness...

Banking apps should run on anything modern and they should definitely run on Android Go, given that many, many new phones are shipping with Go.

No, but the world's moving on from 32 bit and Go 12 isn't even the latest version (14).

Android Go 12 is only two years old. Banking apps should run on it. And it's not automatically 32 bit. It's designed to make the best of low spec phones, something that banking apps should seek to do too.

Banking apps would probably run on 64-bit Android Go. The reason modern apps don't work with legacy 32-bit operating systems is that the 32-bit architecture brings with it a limited instruction set, no native support for modern cryptography, a greatly increased code maintenance burden, and risk of vulnerabilities through working around the missing features. The more important security is for an app, the less sense it makes to compromise. App-only banks are at the extreme end of this, as they often lack some of the security features associated with website-based banking. Some rely entirely on the device for security. These are not the apps you want running with a portion of your CPU's capabilities switched off.

I gather from my limited knowledge that 64 bit is more secure than 32 bit, however ,my Barclays app installed and runs without incident, although I am yet to find a way of confirming if my android is one or the other.

One simple way to check is to download CPU-Z and that should tell you. Under System -> Kernel Architecture. A 64-bit OS should show something like "aarch64".

CPU - Z returned a thoroughly ambiguous response.

Kernel info states: 5.4 233+ (00WW_1_35B)

clarkey1984

Despite there being no clear way to tell when the phone is on, a dead battery, and thus a restart once on charge being a necessity, splash screen on start up says powered by android go edition.

Solved then.