This is such a small supported device list specifically for scanning portals in ingress. I dearly hope there are plans to lengthen this supported device list to more phones because mine and many other people's devices are sufficient to scan in other niantic apps, so they should be able to do the scanning gameplay in ingress.
This should be considered an updated bug, not a solved bug.
Well that's the best way to demotivate your free workers willing to provide you with valuable data.
Instead of saying "Hey, sorry about the issues. The device requirements increased, we are sorry about it. But we are working on a solution to support more devices again soon™️", the requirements page just gets silently updated without any perspective for all the now unsupported phones.
Totally understand that not all phones are capable of these fancy realtime meshing things, but there should at least be a fallback for older or cheaper phones...
mine and many other people's devices are sufficient to scan in other niantic apps, so they should be able to do the scanning gameplay in ingress.
Other Niantic apps use an older version of the scanning tech from Niantics Lightship, Pokemon still uses the same method from 3 1/2 ago. Ingress uses the newest version which combines Meshing and Depth of Field. Niantic has to decide if it is worth for them to lock out a ton of devices, but devices that can scan in PoGo not being able to scan in Ingress is (according to Niantic) not a bug if they don't have one of the supported GPUs.
Niantic staff have said that the quality of scanning from Ingress players vs pokemon, is far higher.
So it is likely a strategic decision to have a lot of quality VPS enabled wayspots with the new method, before pokemon does, to weed out ouithe the junk scanning they do. Just a hypothetical scenario
I have the answer, It's necessary an specific Android phone. Please help me with closing this report Mr. @InvestigateXM . There is not a bug, is the programmed technological obsolescence of mobile phone. Thanks again and best regards.
I can't believe the lack of communication from Niantic on this issue. I just want to start scanning again, I'm prepared to upgrade my device to do it, but I want to make sure I buy the right device and not one that's not going to lose the scan function in the near future.
So can we please get a list of phones that can still scan? I want to know what my óptions are. I. really don't want to buy a new device only to find it won't scan.
I got a good gaming phone today ASUS ROG Phone 6D i can run my Unreal 5 projects that i exported to apk files but it will not run portal scans in ingress prime. Maby you should just get rid of you dev team and hire a new one?
Comments
I've just purchased a Pixel 8 Pro to find portal scanning is now disabled (worked fine on my Pixel 6 beforehand).
Device: Pixel 8 Pro running Android 14. Google AR services and latest version of Ingress installed.
OS: Android 13
Device: Samsung Galaxy Note 8
App version: 2.126.1-0a89604b
There is a updated list now what type of phones can support AR scanning.
Android
Portal Scanning officially supported on devices running Android 9+ that can support Google Play Services for AR and have the following mobile GPUs:
iOS
Portal Scanning officially supported on iPhone 8 and newer devices running iOS 14+.
https://niantic.helpshift.com/hc/en/3-ingress/faq/519-supported-devices/
ADRENO 642L, Snapdragon778G (Galaxy A52s) : scan not working.
Pay for your fracking! 😤
Hell NO. Since Machina, niantic is not getting a Single Cent!
But still, scan button is not there
They get never a cent from me!
This is such a small supported device list specifically for scanning portals in ingress. I dearly hope there are plans to lengthen this supported device list to more phones because mine and many other people's devices are sufficient to scan in other niantic apps, so they should be able to do the scanning gameplay in ingress.
This should be considered an updated bug, not a solved bug.
Well that's the best way to demotivate your free workers willing to provide you with valuable data.
Instead of saying "Hey, sorry about the issues. The device requirements increased, we are sorry about it. But we are working on a solution to support more devices again soon™️", the requirements page just gets silently updated without any perspective for all the now unsupported phones.
Totally understand that not all phones are capable of these fancy realtime meshing things, but there should at least be a fallback for older or cheaper phones...
mine and many other people's devices are sufficient to scan in other niantic apps, so they should be able to do the scanning gameplay in ingress.
Other Niantic apps use an older version of the scanning tech from Niantics Lightship, Pokemon still uses the same method from 3 1/2 ago. Ingress uses the newest version which combines Meshing and Depth of Field. Niantic has to decide if it is worth for them to lock out a ton of devices, but devices that can scan in PoGo not being able to scan in Ingress is (according to Niantic) not a bug if they don't have one of the supported GPUs.
Niantic staff have said that the quality of scanning from Ingress players vs pokemon, is far higher.
So it is likely a strategic decision to have a lot of quality VPS enabled wayspots with the new method, before pokemon does, to weed out ouithe the junk scanning they do. Just a hypothetical scenario
I have the answer, It's necessary an specific Android phone. Please help me with closing this report Mr. @InvestigateXM . There is not a bug, is the programmed technological obsolescence of mobile phone. Thanks again and best regards.
I doubt many agents will upgrade their phones just for scanning
Older flagships are cheaper and are supported
Obsolescence as a goal? For a smartphone from two years ago (Galaxy A52s)? Sorry, but I don't accept the excuse!
Niantic must be able to :
So brand new phone cannot scan: Galaxy A54 Android 13 One UI 5.1.
Not happy Jan.
https://m.youtube.com/watch?v=mG9tiaY-2Qo
What i can understad its not about gpu power but where The chip is from that is important. Asian technology is not welcome for niantec in The new list
They support old Qualcomm chips that is outdated
Nord V2 5G
Version visible on sshot
Google Play services for AR installed.
No scan options.
I can't believe the lack of communication from Niantic on this issue. I just want to start scanning again, I'm prepared to upgrade my device to do it, but I want to make sure I buy the right device and not one that's not going to lose the scan function in the near future.
So can we please get a list of phones that can still scan? I want to know what my óptions are. I. really don't want to buy a new device only to find it won't scan.
Got the new Pixel 8. Can't portal scan. Please fix this Niantic. It's a brand new phone and shouldn't be locked out of this function.
That's just what I want to avoid happening. I hope they can sort this out for you.
Requires I believe, for Ingress to utilize Lightship ARDK V3.
It currently uses version 2 of the ARDK afaik
I read that's been launched just recently.
Still doesnt explain why phones with supported gpu according to their own list has missing scan button, who is to blaim for that?
I got a good gaming phone today ASUS ROG Phone 6D i can run my Unreal 5 projects that i exported to apk files but it will not run portal scans in ingress prime. Maby you should just get rid of you dev team and hire a new one?
This is from Bing
As of Q3 2021, MediaTek holds a significant share in the smartphone chipset market. Their market share stands at 40%, showing an increase of seven percentage points compared to the same period in 202012. Additionally, in the fourth quarter of 2021, MediaTek chips accounted for 48.1% of Android phones in the United States, surpassing Qualcomm’s share of 43.9%3.
It’s impressive to see MediaTek’s growth and impact in the mobile industry!
And Niantec chose to not include Mediatek chips
Lightship ARDK 3 launched a few months ago in September
https://twitter.com/LightshipAR/status/1694129287300083733?t=QWx_hhr82bObfgOEx-puAg&s=19
What unreal projects
I think they've done half of that already...
Same problem.
Samsung Galaxy A54
Android 13