Arcore-android-sdk: ARCore Device Support Requests

[inio]

This issue is to track/dedup requests for device support.

See the official Supported Devices page for the complete list of currently supported devices.

Device-specific details/issues:

• #183 Asus' ZenFone AR never starts tracking
• Samsung S8(+) and S9(+) devices with model numbers ending and 0 sold outside of China may be used for development by side-loading the ARCore APK.

Besides these devices, we cannot comment on supporting any specific devices in this forum.

[Thaina]

I have seen preview 2. Is it already support motorola Nexus 6 ?

Also I want to ask for Nexus 6P
and Nokia Android announced in 2017
and ZTE Blade Z Max

[inio]

Sorry, none of those are supported with the developer preview.

[Svoka]

It's sad that only certain people in big companies can touch ARCore :( I think you can work on support of other platforms first, or just remove code which check if you have phone from the list and get people opportunity to try ARCore even if it's fail somewhere

[Thaina]

@inio Will it supported in ARCore 1.0 ?

[lvonasek]

If you open ARCore.apk there are assets and inside are calibrations by device codenames.

List of devices which have calibration in the apk:
Google Nexus 6P
Google Pixel
Google Pixel XL
Google Pixel 2
Google Pixel 2 XL
HTC 10
Samsung Galaxy Note 5
Samsung Galaxy S6
Samsung Galaxy S6 edge+
Samsung Galaxy S7
Samsung Galaxy S7 Edge
Samsung Galaxy S8
Samsung Galaxy S8+
Sony Xperia XA1
Sony Xperia XZ
Xiaomi Mi 6

Codenames of devices with names I did not find:
Lucye
Nash Sprint
sdm660

Note that support of 100M+ devices means support few popular models e.g. Samsung S7 with 55M+ https://www.google.de/amp/s/www.androidauthority.com/sales-samsung-galaxy-s7-cross-55-million-units-768359/amp/

[Svoka]

Facebook with their AR Studio (Player) can support a lot of devices and Google with their power can't, funny.

Support a list of 10 devices makes it totally useless, why learn AR Core for 10 models if Vuforia works everywhere :(

[inio]

@Thaina:
Right now we can't commit to supporting any specific devices other than the Google Pixels and some models of the Samsung S8.

[gitunit]

@Svoka do your research! since when is Vuforia the same as ARCore? if you can do it better, just do it but stop throwing your uninformed opinion around.

[Svoka]

@gitunit
first,

stop throwing your uninformed opinion around

stop telling others what to do (oh, the irony). And I don't think you have the right to insult people you don't know so easily

second, interesting part how you skip facebook AR-studio.

third, you tell to do my research, but ar-core doesn't work on plenty devices so I can't do it and it makes me feel sad with so much hype around it. 100M devices actually 10 (or so).

[romanvfp]

Could you add support for Lenovo Phab2 Pro, too, please? Otherwise it is kind of weird that it supports more advanced TangoCore but does not support ARCore, while I am sure that technologically it can support ARCore

[lvonasek]

@romanvfp I think you will get never official answer from GoogleAR.

ARcore requires Android 7. Lenovo Phab2Pro uses chinesse fork of AOSP 6. Merging it with AOSP 7 is almost impossible because of the stuff in the fork.

Tango was unofficialy killed in July 2017 (in this moment Tango support email ended own existence), GoogleAR announced the end of Tango support on March 2018. They have to officialy support Lenovo until this date because of laws in Europe.

They will bring ARcore to Asus Zenfone AR because it was released after March 2017 and they have to support it for at least one year.

[romanvfp]

@inio Sorry for the duplicate - was not sure where to write. As not sure now where to reply to your message. So I will copy my question to you here, too:
Is there no way for ARCore developers to add support for older versions of Android?

@lvonasek Thank you for the reply. Hope that ARcore developers can add support for older versions of Android. Android eco-system seems to experience a fragmentation due to certain features supported only for certain Android versions and/or devices...

[wynwas4]

Despite the fact that I have a Samsung SM-G950U running Android 7.0, Google Play Store says my phone is not compatible (while according to the compatibility list it should be). Why is that?

[inio]

@wynwas4 Currently the Play store only offers a pre-DP2 version of ARCore for Pixel devices running O MR1 to support AR Stickers. For development with ARCore DP2, all developers (including those on Pixels running MR1) should side-load the ARCore APK supplied on the developer website here:

https://developers.google.com/ar/develop/java/getting-started#prepare-device

[fredsa]

An up to date list of ARCore supported devices can be found here:
developers.google.com/ar/discover#supported_devices

[inio]

ARCore 1.0 released today now supports (newly supported devices in bold):

• Google’s Pixel, Pixel XL, Pixel 2 and Pixel 2 XL
• Samsung’s Galaxy S8, S8+, Note8, S7 and S7 edge
• LGE’s V30 and V30+ (Android O only)
• ASUS’s ZenFone AR
• OnePlus’s OnePlus 5

[congguohua]

Hello, we are device manufucturers, could you tell me how to pass the "supported device" test?

[KnIfER]

still v1 does not support s7 edge:SM-9350(with Qualcomm Snapdragon 820 Processor ),I can install arcore on it but can's run examples

[inio]

@KnIfER What is your device fingerprint? Capture it with:

adb shell getprop ro.build.fingerprint

Posted this as a separate issue #197. Respond either there or here.

[inio]

#198 Known Issue: ARCore 1.0 is not supported when running on Android 8 "Oreo" on many devices (FIXED)

[alchemz]

Nobody has mentioned OnePlus 5T, @inio do you know how to add the calibration for 5T? OnePlus 5(A5000) and 5T(A5010) are two different models.

[inio]

@alchemz The 5T is mentioned a few lines up where I deduped your #185 onto this bug.

[Thaina]

@inio Will nokia 7 plus that would be launch this year be supported?

[inio]

@Thaina While we're working with many device makers including HMD/Nokia to enable upcoming devices, as far as I know we have not committed to supporting any particular unreleased models except the Samsung S9.

[jituijiaqiezi]

ARCore doesn't support samsung galaxy s9 ! It's unbelievable!!

[Thaina]

@jituijiaqiezi I think what he means is, there is no plan to ensure support on any upcoming device that was not released, except SamsungS9 that was announced to be supported

In other word, only SamsungS9 will be supported 100%. Other unreleased is still no promised

[inio]

@jituijiaqiezi: @Thaina is correct. The S9 is the only upcoming device we have confirmed support for.

[jituijiaqiezi]

@inio I just bought s9.Hope arcore can support s9 asap!Thanks for your efforts.

[sillikk]

Hello @inio , any ETA on support for S9 and S9+ ?

[inio]

@jituijiaqiezi @Sillikk Per #250:

Support for the S9 and S9+ will be added in the next release, which should be released in the coming weeks.

[sillikk]

Great, thanks for the info!

[xRayDev]

Please add support for Honor 9

[yanosch1994]

Perhaps a very stupid suggestion, but with AR on the rise and google apparently having to do a shit-ton of work for every device how about tackling the IMU part of the problem by creating an open-source chip infrastructure and implementation process for device makers to adapt?

Granted, that still leaves the camera part, but might allow you to move way faster.
I'm talking about an AR-Core "core", a separate chip optimised for AR.

That shouldn't get the same pushback as tango, as implementing a chip like that would be way cheaper than the entire camera array that was tango.

[bbaker357]

Hi The Samsung S8 Active is not supported and that would appear to be a dead easy port since the S8 is already supported and they are virtually the same phone except for model number, the active has a bigger battery and tougher case/screen. Any idea when?

[Paullux]

Can you add the support of OnePlus 3T ?

[abuenovanadis]

Can you add the support of OnePlus 5T ?

[kelteseth]

Can you add the support for Samsung s6?

[geverk]

Hi, just release that the new samsung s8 that I bought to test arcore (SM-G9500) the hongkong model, where google play has no problems since is not ban has no support for the ARcore.

it would be sad that I need to sell my phone and order the china mainland model (SM-G9508) that has support even is supposed to not be as good as it has not the snapdragon chip...

Can this be solve for the next version?
thanks

[ez999]

Is there any plan to have calibration for sony xperia phones? I mean, there are XZ and XA1, which are older, than it would be strange if there will be support for XZ2 and XZ2c or newer devices and not for XZ1 and XZ1c.

[Thaina]

@inio Nokia 7 plus is launched. Is it support ARCore?

[inio]

@Thaina I don't believe we've committed to supporting any specific device from Nokia, but I could be wrong. Do you have a press release or news article that suggests a particular phone will be supported at launch?

That said, we're working to bring ARCore to as many of this year's flagship devices as we can.

[ikv007s]

any new news on onePlus 5T support?

[Thaina]

@inio I was really actually think that the ARCore supportive could be determined whenever the phone have full hardware spec, which is long before launching, and it could be announce supported as soon as it released for purchase, like GooglePixel that was promised to support and so people can buy GooglePixel on day 1 released with fully confident that they will be able to use ARCore in mind

I hope that as soon as any device released it should be announced that it was support ARCore or not immediately. What make it can't do? Why you need to made ARCore support for specific device when it should be determined by hardware capability?

Can you just tell us what is really the requirement for ARCore? Is it the double camera? Or gyrocope? Or accellerometer? Or speed of video recording? Or the speed of GPU and CPU? Why you need to check for specific device one by one and cannot measure before you could get your hand on it? What is the process to make it support?

Or is it just internal politics to select a support device and nokia must go beg you to support them like a slave?

[vincentfretin]

@Thaina there is some explanations by @inio on the calibration process there https://github.com/google-ar/arcore-android-sdk/issues/263#issuecomment-376231809

[Thaina]

@vincentfretin I have seen that explanation but it never be a problem for announce support or not support. Calibration means it can support but need calibration. It could never be cannot support because calibration, could it?

And actually if we should just get a usable runner while calibration can be just patched after. It could even be a git repo for calibration setting that we could also edit and make pull request instead of rely on one team to do it for each device

[bbaker357]

Hope you folks are going to support the Samsung S8 Active, since it is one of last years flagship devices. Should be a very easy calibration and port since it is basically the S8 Active, with a bigger battery, additional 600Mhz band (which shouldn't impact anything?) and tougher case/screen. It currently has Daydream support, so that should help with AR?

Oh yes forgot to mention, it just recently got Oreo 8.0 on it's TMO and AT&T versions, maybe sprint too.

[hoharald]

Will the Galaxy A3 2017 be supported?

[inio]

@CodingHarry @bbaker357 @ikv007s I just updated the top post to clarify:

Besides these devices, we cannot comment on supporting any specific devices in this forum.

[elblogbruno]

I need support for honor 8!
Great job!

[kyle18th]

Please support OnePlus 5T

[duncan088]

Support for moto g5 plus 2gb

[t1mman]

The Support for LG V30 has been removed lately, any plans to put it back? Any reasons why?

Thanks!

[inio]

@t1mman Similar to the S9, driver issues showed up on the V30 very late in the release process for 1.1. It will be re-added as soon as the driver issues are resolved or we can develop a workaround.

Good news on this one though: unlike the S9 driver issues the V30's problem is just a matter of one of a sensor using the wrong time base, so there's hope for an ARCore-side fix.

[sillikk]

Does it mean there is no hope for a fix on S9?

[inio]

@Sillikk There is more than hope - the S9 will support ARCore, but it will require a driver update. We don't have a specific timeline on this update but expect it soon.

[sillikk]

Ok, thanks !

[t1mman]

@inio Thanks for the follow up, can't wait to test the thing out!!

I was woundering, would the addition of Treble Project would have any effect on this sort of issue? Is it more an "android framework" dev or is this more of a "container" on the higher level?

[Thaina]

@inio What happen with Nokia 7 plus?

[inio]

@Thaina As I said before, I don't believe we've committed to supporting any specific device from Nokia. Do you have a press release or news article that suggests a particular phone will be supported?

[ikv007s]

actually, everyone has gone mad about device support. Everyone in here is excited about arcore and wants to get their hands on it. The problem is ARCore was announced back in sep last year and most of us still can't work on it, but we want to work on it so badly. I understand that it will take time to support more devices, but it's human desires for something you can't contain. RIP till it's out for more and more devices. Let's hope Google will announce something around Google I/O.

[Thaina]

@ikv007s The thing is I don't even ask that it must support right now. It's just the information for the core library to support which device should just available even it need to wait for calibration that's fine

Working process like this is not practical. Core supporting should just be able to checked by launch the basic test on that device and announce that it will eventually be calibrated and then released in the meantime. Just the fact that we could wait for update on that device is necessary for making decision to buy that device right now

Also we could expect that this calibration process between device is way too slow. It cannot keep up with releasing of new device. Google have boast that they was

partnering with many manufacturers to enable their upcoming devices this year, including Samsung, Huawei, LGE, Motorola, ASUS, Xiaomi, HMD/Nokia, ZTE, Sony Mobile, and Vivo.

And then what happen now? What is partnering process that was making ARCore cannot be available on upcoming devices this year as they said? What is the partnering actually did?

In fact. When I heard the question asking

press release or news article that suggests a particular phone will be supported

I was really disappointed because in the google's blog post above have boast

to enable their upcoming devices this year

Make me expect without saying that it must include every possible device that would released this year. Which is include Nokia 7 plus that just release this month

[belko-vasiliy]

Arcore apk v1.0 support samsung s7e sm-g935fd, but v1.1 doesn't. Can you fix this please.

[inio]

@belko-vasiliy Dual-sim devices (FD) are identical to single-sim devices (F) as far as our calibration goes, and are supported. I've asked the docs team to update the supported device list to include dual-sim devices.

[belko-vasiliy]

@inio
I thought so. Maybe my problem is in another things. I use arcore plugin in unreal engine 4. I used your quickstart guide for it. And when I was using arcore v1.0 in ue4.18, it was OK with everithing, but when I tried arcore v1.1 in ue4.19, it wasn't. So I don't know why arcore v1.1 in ue4.19 doesn't work on samsung s7e sm-g935fd.

[inio]

Could you try the Java HelloAR Project? If that fails as well, please open a new issue and post a logcat.

[skelder]

Is there any plans for official support for tablet devices(any model) in near future(like in few months)?

[sbidarkar]

Can we please get support for One Plus 5T? If it is a very small change/effort, please make it happen. Most of the people in my dev team currently use One Plus 5T and I am sure same is the case with most of the people around the world. One Plus 5 devices have become a bit scarce. I hope to hear from you.

[ttmagic]

Can you please support for LG G6? It just has an update to Oreo. Thanks in advance.

[water64]

I saw the Samsung Galaxy S6 edge+ referenced, but only for calibration and no S6 edge. Do you think it would be supported in the future?

[gabrielmartins]

Just installed ARCore v1.2 on my Galaxy S9 following the Google I/O announcement, confirming it is still incompatible (tested with WebARonARCore). Any ETA on the driver update and will it work with 1.2? Thanks!

[inio]

@gabrielmartins We're working on it. Calibrations for all variants are in 1.2 but we need to make sure a large enough portion of the device population is updated to be compatible before we can announce support.

[inio]

@datglowedesign Sorry, got crossed signals on that. The S6 is NOT supported yet.

@ttmagic Good news, the LG G6 is now supported with 1.2.

[t1mman]

When can we expect support for V30 to be added?

Thanks!

[inio]

@gabrielmartins Update: the S9 should be compatible with 1.2, but won't work with the Play Store until later this week. What's the specific type of incompatibility you're seeing?

[inio]

@t1mman I have an extremely unsatisfying answer for that: "Soon™". We're waiting for driver issues to be fixed and those fixes to reach a large enough portion of the device base that we can comfortably call it supported. You can try side-loading 1.2, but there's a decent chance it won't work.

[gabrielmartins]

@inio Thanks so much for the confirmation! I sideloaded Just a Line 1.1 and can now confirm support on the S9!
WebARonARCore was my initial test app but I'm guessing it's checking for compability the same way Play Store does so I'll check on it again once the device is officially registered as compatible. Are there any other apks you'd like for me to test?

[t1mman]

Thanks for the update!
Do you know if the driver issues are fix by you (or the AR Dev team) or by LG themselves, with a futur update?

By sideload, you mean by getting the APK and installing it this way?
If so, I'm willing to test it if you want!

[inio]

@gabrielmartins Glad to hear it works. If JustALine works well it should work across all apps.

@t1mman I'm not familiar with the details, but these kind of things usually require a bug fix from the device manufacturer, usually bundled with a regular security update.

[t1mman]

Oh! Well, knowing how LG updates (or don't update) their devices, we might never see it :/

Thanks!

[bbaker357]

Hi Ian Muldoon sorry I posted my comment before I finished it. It's been stated by Google that they intend to support last year's flagships. The S8 active is one of those I would like to know if Google is working on it for arcore. there seems to be responses to all kinds of weird ancient models but not to a current flagship. Is arcore going to be supported on the Samsung S8 active?

[inio]

@bbaker357 The calibration group says that enhanced-durability devices are unlikely to see support as they generally put the camera module on an additional shock dampener, as it is a particularly sensitive component due to the moving lens for focus. This decoupling of the camera from the frame of the device (and thus the circuit board carrying the accelerometer and gyro) makes calibrating these devices impossible.

[Thaina]

@inio What about Nokia 7 plus?

[vincentfretin]

@gabrielmartins WebARonARCore only supports S8 and Pixel on Android 7 because it still uses arcore-preview.apk (which is labeled as Tango Core in Parameters/Applications), not ARCore from Play Store.

[t1mman]

I've tried side loading the APK then loading ARuler and it seems to work, do you know if I could help in any way to make this "official" for the V30?

[inio]

@t1mman Well, go ahead and start developing. We can't officially support that device until until we're confident that a large enough portion of users with it will have a similar experience. Right now that is not the case.

[Thaina]

@inio Is it possible that even if the device can actually run the ARCore but if you not satisfied with that "similar experience" standard it will never launch official support?

[JamesR48]

@inio is the Xiaomi Mi A1 going to be on your supported devices list anytime soon? (Soon=less than 1 month maybe)

[Paullux]

There is an error, OnePlus "A3000" is the "OnePlus 3" not the "OnePlus 3T", which is "A3003".

[ikv007s]

So they are supporting oneplus3t but not 5t even after being the current flagship device. I can't get more frustrated than this. onePlus is playing with us lol. Google said oneplus will get android p beta and guess what it's for oneplus 6. what can i do with my 5t?

[inio]

We're working on supporting as many users as we can. Devices with a larger install base (or larger anticipated install base) generally will get enabled sooner.

[Svoka]

Hi, guys!
Since announcing of ImageTracking and SceneFrame do you have any plans to releasing this parts for everyone? Because it's seem like this super useful features don't need this camera calibration process.

[Aritzherrero4]

Can we expect oneplus 5T support? Since 3T and 5 are supported

[alerm-sml]

Xiaomi Mi 6, Xiaomi Mi Mix 2
thanks

[ikv007s]

@inio sorry! well oneplus5T has a very large user base and it's a flagship but not getting support even after months is what frustrates us.

[Thaina]

Same for Nokia 7 plus. It is the only one 6 inch display flagship from Nokia

[oliverellmers]

Any chance at all of getting support for tablets within the coming weeks?

Have a project I have been working on in Vuforia, but after doing some tests with the Augmented Image capabilities - I would very much like to move the entire project over the ARCore!!!

Need to get it going on Samsung Galaxy Tab S3

[inio]

@ikv007s Thanks for the edit. @Aritzmuro4 I understand frustration over the 5T. It's a device we'd like to support but have had issues acquiring enough of them to build a good calibration.

@Svoka Sceneform is something we'd like to release more generally, but right now it's coupled to ARCore.

@oliverellmers So far it seems we're on roughly a 6-week release cadence, so there's not likely to be any changes to the supported device set besides the maybe the V30 (which we're just blocked on a driver bug on) in the next 6 weeks or so. I hear we have a bunch of devices we're hoping to enable in 1.3 but even if I had the list I couldn't share it.

[Aritzherrero4]

@inio thanks for the reply. Luckily you can resolve those issues and finally we get it. I believe you are still trying to address them.

[oliverellmers]

@inio Thanks for the update - bit of a shame as I would love to have this software running on tablets for a couple of exhibition style pieces I am currently working on, hopefully I can convince the others involved to be happy with smaller screens - I might just have to try my luck with ARKit as Vuforia's android based tracking capabilities are terrible compared (obviously unfortunately... I hate developing strictly apple stuff :( but I am sure we will survive) - excited to see what happens with the 1.4 release! thanks!

[sam1am]

FYI ARCore 1.2 installs from apkmirror and works on the V30 whereas 1.1 did not. So maybe the problem is already fixed and the manifest just needs to be updated to list the v30 as supported? I only tested Just A Line and the Amazon Store and both work.

[inio]

@sam1am ARCore works on a fair number of V30s, but not quite enough for us to enable it.

[rajasimon]

Bought the 1+5T recently and can't able to afford another new phone which supports ARCore. My question is weather 1+5T support ARCore in the future ? Or Do I need to switch ? Any hack around in this ?

[Thaina]

So sad that google have boast "Work with manufacturer to enable ARCore" but cannot promise anything and grant anxiety to everyone who need to buy new phone (and also neglect people they cannot make argument to)

[inio]

@rajasimon: The 1+ 5T is one of the devices we're been looking at supporting for quite a while, but a string of bad luck has prevented us from confirming that it can be supported. (nothing to do with the device itself, stuff like shipping issues, calibration system failures, etc.)

@Thaina: I understand the frustration that this causes. Unfortunately, we're very reluctant to announce support for a device before we've fully confirmed that it works. We've already had several devices where we calibrated and validated prerelease versions, but then changes to the software leading up to release resulted in the shipping versions being incompatible.

[Thaina]

@inio From the start what we really want to know is, will the device in concern could use ARCore eventually

There could be level of support information

• Fully support
• In the calibration process <<< Will be fully supported soon <<< And should be able to run ARCore APK
• In the verification process <<< Will be supported eventually <<< This would be my acceptable to purchase device
• Hardware compatible <<< Have some hope but might not be able to support
• Hardware incompatible <<< Hopeless

This list should be map with android device from last year and available publicly. I don't ask you to have ETA or roadmap for anything but if my phone would dead tomorrow I know I could buy the best device available in market that can support ARCore eventually. And I think this is what many people here would like to know for decide to purchase device they interested in

But what you have done so far is spreading seed of anxiety to every new device in the market. Make everyone hesitate on every week have passed

I was asking you

Is it possible that even if the device can actually run the ARCore but if you not satisfied with that "similar experience" standard it will never launch official support?

And you just ignore this question. So what would you want me to think if it not that google are making ARCore be Tango2, unreliable and would drop support eventually again, and again, and again

Anyone here know the destiny of Tango I think

Your calibration process are currently making ARCore worse than Tango

[romanvfp]

Are you ever planning to add support to devices running Android 6? Some of
Android 6 phones have good hardware being definitely capable of running
ARCore, e.g. Lenovo Phab 2 Pro.
I love Google and hope that you will not be forcing people to buy new phone
just to have newer Android OS. This would be a bad trick, not talking about
harm to environment, because many people would buy new phones just to have
ARCore and will dispose good working phones. Google officially cares about
environment. Hope that it will also be shown in actions.

2018-05-12 18:03 GMT+02:00 Thaina Yu [e-mail]:

@inio https://github.com/inio From the start what we really want to
know is, will the device in concern could use ARCore eventually

There could be level of support information

• Fully support
• In the calibration process <<< Will be fully supported soon <<< And
  should be able to run ARCore APK
• In the verification process <<< Will be supported eventually <<<
  This would be my acceptable to purchase device
• Hardware compatible <<< Have some hope but might not be able to
  support
• Hardware incompatible <<< Hopeless

This list should be map with android device from last year and available
publicly. I don't ask you to have ETA or roadmap for anything but if my
phone would dead tomorrow I know I could buy the best device available in
market that can support ARCore eventually. And I think this is what many
people here would like to know for decide to purchase device they
interested in

But what you have done so far is spreading seed of anxiety to every new
device in the market. Make everyone hesitate on every week have passed

I was asking you

Is it possible that even if the device can actually run the ARCore but if
you not satisfied with that "similar experience" standard it will never
launch official support?

And you just ignore this question. So what would you want me to think if
it not that google are making ARCore be Tango2, unreliable and would
drop support eventually again, and again, and again

Anyone here know the destiny of Tango I think

Your calibration process are currently making ARCore worse than Tango

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/google-ar/arcore-android-sdk/issues/89#issuecomment-388564898,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXTvpMAfNJ5A9Wj-O9pdK7xoRSarDmi5ks5txwfFgaJpZM4REE1a
.

[inio]

@romanvfp At the moment, supporting API levels prior to 24 is not feasible. Internally, ARCore is dependent on the NDK camera API as well as the SurfaceTexture Java API. Using these two components together requires API 24 (you cannot convert a java Surface to an ANativeWindow until API 24).

[inio]

@Thaina While that seems like a good idea, it actually ends up being nearly useless. Until we are confident we're going to support a device (usually a few weeks before a new version of ARCore is released) there is zero guarantee it will actually ever be supported. We've probably put 150+ unique devices into the calibration station at this point, and somewhere between initial calibration and final certification we decided that the device wouldn't work with the current state of our software.

Further, naming devices we have deemed incompatible right now won't help anyone. We're constantly improving our accommodations for previously incompatible devices, so this state isn't permanent.

One small thing I think we could do is announce early (at least by a few weeks) some of the devices that are going to be supported, after we've made that decision. This is no worse than the current situation with the LG V30 and previous state of the Samsung Galaxy S9, and probably better because we can give an approximate timeline. I'll talk to our device enablement and product groups to see if I can get support for at least this.

[Thaina]

@inio

Until we are confident we're going to support a device

The point here is it should be known that you are going to support a device from the first day the device was in your hand. Even the device was difference every device hardware has a set of characteristic that should be able to predicted how likely it was passed like the similar device

At least when you have run initial calibration it should passed the ARCore APK launching already right? That was I think it satisfied enough and it very assured that at least developer could buy and try the current APK with that thing and could hope for the better next version

The situation you talk about somehow very unlikely

The possibility is there would be a device able to run ARCore APK and then need a calibration for "similar experience" but then it was not get certificate. And then there would be another device that cannot even run ARCore APK from the start because it was incompatible

But then sometimes later ARCore would be updated. Suddenly the device that cannot run ARCore in old version are able to run the new version and work perfectly. But the device that can actually run ARCore in the old version still couldn't get certified anyway

This is the situation that you argue as the reason that you could not give both incompatible category and calibrating category which as I say it very unlikely that both could happen. And if it happen then I could say the reliability of ARCore was worse than Tango. So at least one category should be able to announced

And even if it was really happen I think it still fine because to make a device that incompatible suddenly become workable was a major change in ARCore versioning and technology

Also I just realize that if there was a calibration and certified process, there should be the list of device that was already going through the process that failed in each version isn't it?

So until there would be updated version of ARCore that list should still be valid incompatible that we should avoid until the next version of ARCore. This would also be a useful information too

[inio]

@Thaina writes:

The point here is it should be known that you are going to support a device from the first day the device was in your hand.

This is false. I can't go into the details, but ensuring ARCore works well enough on a specific device model for us to support it requires is a long and complicated process that often includes iteration and sometimes developing device-specific solutions requiring code changes throughout the ARCore software stack.

[Thaina]

@inio The point is, in my opinion; and I assume the same for all developer here, _ARCore works_ is enough, don't need to be _well enough_

My current device is Motorola Nexus 6. It's quite sure that it impossible to run ARCore. It cannot open any version of ARCore APK I had download from arcore for all. But still I would like to have official announcement that it would be impossible so I need to buy some new device. But still I have my own preference and finance to I had to buy cheapest and favorest one. And for me is Nokia 7 plus

In the same sense. Many device could open ARCore APK (from ARCore for all) even it not officially supported. It can work somehow and developer can start working with it by device in their hand

At last. This is spec of Nokia 7 plus vs Nokia 6.1 (6.1 officially supported ARCore). Hardware of 7+ is better than 6.1 in almost all aspect but also a very same kind. If you cannot guaranteed ARCore to work on 7+ I think people would really be skeptic that it not about device capability anymore but about your own dictation policy and internal politics

[RegisAG]

Is support for Samsung J7 planned ? Thanks

[RegisAG]

Is support for Huawei P10 planned ? Thanks.

[sugartechnology]

Hi @inio
on the top of topic.Some of Note 8 Models seems in supported devices list.But I can not make it work on my devices with model number SM-N9500.Is this device is supported or any further plan to include supported devices ?

[RegisAG]

Strangely, I don't see anymore the Galaxy Note 8 in the list of supported devices https://developers.google.com/ar/discover/supported-devices . Has it been removed from the new version of ARCore ? If yes, do the Note 8 owners have access to the previous version of ARCore ? Thanks.

[sugartechnology]

Yes this is the exact question.All comments at blogs mentions that it was already supported but with 1.2 version at google play we face with incompatible version error.

[ikv007s]

People are going mad lol for ARCore i see

[inio]

@RegisAG We can't comment on plans, but I've noted those requests.

@abdurrahmanTurkeri All Samsung devices with models numbers like SM-*0 and SM-*8 are not currently supported.

@RegisAG That's weird, the Note 8 was definitely there before, even for 1.1. It looks like it missed the move between locations. I've asked internally what the story there is.

[JamesR48]

@inio I've an issue with a Moto G5s Plus also...a friend of mine was trying with that phone but he couldn't get it working...and that Moto G is on the supported devices list. He could download Just a Line, the Solar System app and stuff but when they asked for the latest ARCore and the device was redirected to the Store it said "device doesn't support this version" or something like that.

[t1mman]

I just saw that ARCore is supported on the Nexus 6P, is this new?

Funny because I was all happy seeing the "This app is compatible with some of your devices." on the google play, only to see that it's for my ol' Nexus 6P, not my current LB V30! :/

[inio]

@JamesR48 see #381

[inio]

@t1mman I believe we picked up the 6P and 5X with the 1.2 release.

[JamesR48]

Thanks for your response @inio but I got it working well on the Moto G5s Plus. The only problem is that we're not able to download it directly from the PlayStore, but it works well on the device

[rajasimon]

@JamesR48 @inio Is that right? If we can install ARCore app without installing from the Playstore it will help us to right ARCore app. It helps the development faster instead of waiting for the right mobile and support.

[JamesR48]

@rajasimon bro the thing is that the Moto G5s Plus was on the supported list but it has problems when trying to download the ARCore apk directly from the PlayStore. I just downloaded it from Aptoide and it worked because it was supposed to work since that specific device previously was on the supported list.

[inio]

@rajasimon @JamesR48 We hope to fix the Moto G5s soon. For the time being, we've fully disabled it to prevent users from downloading ARCore apps and then being unable to download ARCore itself. Please post further updates on this topic in #381.

[rataman098]

@inio will the Xiaomi Mi A1 recive support for ARCore? I have seen that XDA guys modded the app so it supports it, that can be installed with Magisk.

Here's the thread: https://forum.xda-developers.com/mi-a1/themes/magisk-arcore-modded-google-camera-t3720269

[celsourroz]

Hi guys ! Any news about the Xiaomi MI6 ? cheers

[widovanheemstra]

Please add support for Huawei mate 10 pro. Its silly that this is still not supported.

[Zhaituki]

Please add support for Nokia 8 models other than Sirocco, they have better specs than Nokia 6.1 for sure.

[MaxHellqvist]

Hi, are there any plans on adding support for the OnePlus 6?

[vadim0872]

Hello, When you will be support Tablets, for example samsung tab s2, tab s3?

[zacharyrs]

Any chance of support on the U11 and U11+?

[metalchronic]

Is there a possibility the s9 g9600 version will be supported anytime soon? Sucks to find out i can't use the recently released "measure" app by google llc :(

[MidnightTheory]

Requesting support for Samsung Galaxy Tab S3 (SM-T820)
It's ridiculous that these tablets aren't supported yet. Missing out on a HUGE market share for enterprise AR applications that require a larger screen.

[anybuy]

Requesting support for Samsung Galaxy Note 7 (Galaxy Note FE)

[inio]

@metalchronic ARCore 1.3 will now work for development purposes when sideloaded onto many previously unsupported Samsung "0" and "8" model numbers. We're currently exploring enabling installation on these devices through Play Store (only useful for users outside China obviously), but can't make any commitments yet.

[Thaina]

@inio Nokia 7 plus yet?

[rajasimon]

@inio Is ArCore 1.3 supports 1+5T ?

[lartx]

@rajasimon It works on mine, installation available from the Play Store.

[rajasimon]

@lartx yes it's available but the website still not mentioned about the 1+5T.

[snhsoul]

Requesting support for Samsung Galaxy Note FE(SM-N935).
Note FE Hardware is Very similar with Galaxy S7.

[alexandreMarie]

I saw that Ipad works now with ARCore (only cloud pin, no plane or image detection ? So we can't switch to Ipad)

We need for professionnal purposes an ARCore support on Galaxy Tab (S2, S3, A6 ...etc) Any tablet could fit.

Furthermore, our contract is in partnership with Samsung.

As it was said before, tablets are a HUGE market in AR enterprises applications. No one will pay for an app which runs only on smartphones.

[kpulka]

Any chance for Moto Z soon? It has Daydream but no Arcore yet :(

[Gheldar]

I would like to request support for Xiaomi Redmi Note 4. I know at least 5 people (apart from me) in my close circle (some of us being developers) owning this device, which well deserves support judging from it's hardware.

[Thaina]

My wishing device (Nokia 7 plus) was passed but I still would want to voice my opinion that the whole current process of ARCore is not practical. Many people stuck in the waiting line and good enough policy is not good for most people

[Mixermachine]

@Gheldar I second that.
Especially in India the Redmi Note 4 is a BIG hit. (top selling phone in 2017)
I use it with a LineageOS ROM as my daily driver.
Greetings from Munich.

[barwalker]

Hi, is there any chance of supporting for Samsung S8 Active? while other S8 phones are and share the same hardware.

[robertovanderlinden]

Sony XZ2

[inio]

@barwalker

From my previous comment in this thread:

The calibration group says that enhanced-durability devices are unlikely to see support as they generally put the camera module on an additional shock dampener, as it is a particularly sensitive component due to the moving lens for focus. This decoupling of the camera from the frame of the device (and thus the circuit board carrying the accelerometer and gyro) makes calibrating these devices impossible.

[ehong-tl]

Why does Oneplus 3 not supported, but Oneplus 3T does? Aren't they virtually the same phone with just a tiny hardwre upgrade on 3T?

[pinkysbrains]

Is there a brand specific problem to explain the absence of Arcore support for any HTC phones, U11, U11+, and now U12+? Is google punishing HTC for something, or is there actually a hardware incompatibility that can't be fixed? If not, could someone please give an estimated timeline for when these phones might be added:

[mjpwn]

Will we ever see Redmi 4A?

[baloo887]

@inio is there a reason why Xiaomi Mi A1 is still not supported? The chipset is the same of the motorola G5S Plus, It has even more ram of the moto.

[handikasputra]

I hope your team will add support Samsung Galaxy note fe device N935F/DF, the device hardware specifications simoiliar with s7 and has Oreo os. Thank you for your attention, I really appreciate your hard work and team
Your reply/confirmation realy useful or us :)

[dbaniel74]

Samsung S8active
Seriously, S8 and S8edge but not S8 ACTIVE??????? Wtf

[bbaker357]

hi I asked this question about 6 months ago and it appears that the S8 active cannot be calibrated for arcore because there is a rubber buffer or something like that around the camera lens that keeps it from being calibrated like the S8 can. I have an S8 active myself and it kind of bummed me out. If you look through the previous threads there should be an answer from the Arcore team

[bbaker357]

The rubber buffer apparently keeps the camera from being damaged if it's dropped

[leadenmoth]

Honor 9 support would be nice. Specs are very close to the already-supported Huawei P20 (dual-camera array has some feature differences (no laser focus and OIS) and GPU is Mail G71 vs G72, while the rest is more or less identical)

[Zetraux]

Please, add support for Zenfone 5. The whole zentalk forum on asus.com is mad. Many ppl ask to support arcore.

[vinod4dev]

Yes indeed Zenfone 5Z with the SD 845 is a prime candidate for arcore . I was trying to use the AR ruler app and was disappointed seeing that it doesn't support arcore .

[zaha]

Sadly the Sony Xperia XZ2 (Compact) ist not supported. Can you please add support for it? :)

[MaddestScience]

Sadly the Sony Xperia XZ2 (Compact) ist not supported. Can you please add support for it? :)

Would be nice indeed.

[vadim0872]

@inio Why you don't answer about tablets? When you support any android tablets? You support apple tablet, but don't android one ?

[inio]

@vadim0872: I can't discuss tablets for the same reason I can't discuss any other unannounced devices: they're unannounced.

I usually can't discuss support for any specific device for which support has not been formally announced. A very small number of devices we've stated cannot be supported at this time due to an inherent incompatibility (e.g. Phab Pro 2 doesn't run Nougat, various enhanced durability devices don't have consistent enough IMU<->Camera geometry), but for all remaining devices we do not publicly state intent or progress towards enabling.

A little more background:

For a device to be enabled for ARCore it needs to successfully go through the following steps:

1. Selection for consideration. This is usually based number of active devices running Nougat and Oreo, but other factors can apply.
2. Verification "on paper" that the device meets our requirements. Checking that it has the right sensors, has fast enough cores and enough RAM, etc.
3. Acquiring a sufficient sample size of devices for calibration and validation.
4. Verification of a consistent calibration result across the calibration sample.
5. Development of device-specific behavior to work around driver issues, device quirks, etc.
6. Validation of AR tracking quality on devices in the validation sample.

Devices can and do fail at every step. We're not going to say which step a device is stuck at. However, I will say that picking any one of the thousands of unique android devices at random, it probably is waiting to pass step 1.

[rataman098]

@inio so what about Mi A1? As I said on previous comment, it supports ARCore (XDA guys achieved it with a modded version, I've tested it myself).

[sarathsi]

I am trying to install ARCore from Google play store (released on 11 Dec 2017) on Huawei P20 lite- Android 8.0.0. But it shows "Your device isn't compatible with this version". What would be the correct ARCore version? Can we use latest version from https://github.com/google-ar/arcore-android-sdk/releases?

[inio]

@sarathsi The P20 lite is not supported. Only the P20 and P20 pro.

[rares45]

The list of Xiaomi devices which are compatible with ArCore is to short. What are the minimum specs to support arcore?

I asked that because ArCore support only 3 Xiaomi devices. Xiaomi Mi A1 is best bought Xiaomi phone in Europe and isn't supported by ArCore.

[MdYeasinSamadArnob]

XIAOMI MI A2 LITE has 41 sensors and also an android one programmed phone.so how long will it take to get the arcore support ?

[YoneChen]

Please, add support for OPPO Find X.

[cyberluke]

Reading this as software and hardware developer make me think AR Core is a dead technology already! It is nearly impossible to develop with ARCore and market for some meaningful number of devices. Even not all Samsung S8 are supported (SM-G950W is supported, but SM-G9500). I'm from EU, but wife is from Vietnam, we want to develop for EU & Asia. But after reading all these comments, I think it is a better business decision to support only ARKit and iPhone for AR applications. Do you know, it is very risky to develop ARCore app and then receive a lot of hate and bad ratings in App Store, because some users cannot use it on some S8 models for example. The hard work costs money and we don't believe it will return back. This framework should be supported by any gyro+camera device at least for planar detection. S6 should be also supported. Tablets should be also supported.

Maybe you could study some opensource quadcopter design and see how they calibrate gyro/acc/mag with individual motors and 4 motors together and solve vibration issues. Maybe you could create your own calibration hardware to allow change of position of camera and sensors on devboard. You are just using workarounds for workarounds and still have % of inacuraccy as you probably need to sample a lot of consumer devices. Big Data, machine learning will not work here. I think your approach is not a good one.

I was also thinking about buying Lenovo Phab 2 Pro, glad I didn't make this mistake. You support such devices only for 2 years, because of EU law. ARCore is developer's playground, quite expensive one. Not good for business. I think you need better CEO and CTO X_X

EDIT: Look up also your ARCore page on your Google Play Store. A lot of user comments, they have problems after your last update. All AR apps stopped working even on supported versions. This is a major loss of development costs for indie & commercials. People uninstalling apps, lost of trust in product. For example this Czech comment (I'm Czech also): "V zakoupeném telefonu nokia 7 plus to fungovalo ale po aktualizaci už ne a další apky pro AR už taky nejdou.". Next S7 and S8 users reporting after installation of ARCore, their camera stops working at all. After uninstalling ARCore, it starts to work again. Some S8 users report not working at all. After more than half a year they still don't have answer here. Please tell your management to support this official product more and answer people, you have the tools for it. Or it looks like it is normal to give support like this. ARCore is a no go even at current version.

[Thaina]

Totally agree. ARCore place too much requirement and could never be supported on enough device as it boast, not to mention the limitation and quality that does not much better than vuforia. You talk about acceptable quality and making a high wall but the quality of the real result is totally lower than expectation

Put it simply. With the quality of arcore system I had experienced, you should just stop every testing process and let every device that pass requirement on paper can use ARCore right now. Your process cause too much frustration to everyone and the result is not anything worth

ARCore is just Tango, dead together

[MdYeasinSamadArnob]

THE ONLY REASON GOOGLE HAS BECOME CARELESS AND LAZY OVER FEW YEARS IS BECAUSE THEY HAVE HIRE A BAD CEO.

[MdYeasinSamadArnob]

GOOGLE PROMISED TO BRING LATEST INNOVATIONS TO ANDROID ONE PHONES.SO I BROUGHT AN ANDROID ONE PHONE IT HAS STOCK ANDROID BUT NO ARCORE SUPPORT . THEN HOW HAD GOOGLE KEPT THE PROMISE ? THATS WHY I WOULD SAY THAT GOOGLE HAS TO REPLACE THE CEO OR ELSE IPHONE WILL BE THE WINNER IN EVERY THING.

[0x00x0]

@inio

Verification "on paper" that the device meets our requirements. Checking that it has the right sensors, has fast enough cores and enough RAM, etc.

1. May you share full device reuirements?
2. And to add device to compatible list, you need to contact with device manufacturer for support?

[oposop]

May I know why Vuforia is support Oneplus 5 but didnt support Oneplus 5T and 6?

[0x00x0]

@oposop,
above @inio mentioned steps to add new device to list of supported arcore devices.
As I right understand, they are doing those steps manually, so it will take much time for tests of each suitable android device.

[inio]

@oposop Um ... Vuforia? If you meant ARCore, then version 1.4 released a while back added support for the 5T and 6.

[handikasputra]

Add support for note fe like s7 series, Both have identical camera hardware, and I think the development is easier

[brainode]

What about HTC U11??It's like Google Pixel 2, the same firm(HTC), very similar hardware, but no support((

[RakeshRV1317]

ARCore not supported on Samsung A6+..
Please add support..

[ASHRAF1995]

mi a2 light not support ARcore

[zombiekitten]

Hi! While I'm waiting for ARCore support on my Mi Mix 2, I have a question:

The only supported phones so far from Xiaomi are from 2018. The same seems to be true for Huawei too, but not some other manufacturers. HTC phones aren't supported at all. Could it be that phone manufacturers can tell Google not to support ARCore on certain phones (so that they can make money on selling newer phones, for example)? Or is the decision to support or not support a phone purely based on technical stuff?

[Dandarawy]

Huawei Nova 3 should support ARCore, I've Nova 3 PAR-TL20 and doesn't support AR core, any help?!

[incognitorobito]

Essential Phone PH-1 should support ARCore. Most users should be running Oreo or Pie and there are at least 100k users. Does the device's IMU support ARCore?

[rares45]

I want to know if somebody from Google read this things.

[inio]

@rares45 Yes, someone does.

[incognitorobito]

@inio Any word on this? Essential has stated that the device is on the list but has not given any indication of a time frame. A timeline would be nice, but I'd just like to confirm that the device is slated to receive support from someone on Google's end.

[celsourroz]

Any news concerning Xiaomi Mi6 ?

[adelakinson]

@lvonasek @inio hi..is there some workaround that would help me get Arcore running on a samsung galaxy note 5...thanks

[inio]

To all those asking, as I say in the very first post, we cannot comment on supporting any specific devices in this forum.

[chinseng85]

@inio Can you please add HTC phones such as HTC U11 and U12 Plus in the list? Coming from OnePlus 6 to HTC U12+, really miss the ARCore apps.

[angelgod4]

So i know you said you cant comment on support for specific devices. But at least can you tell me if there even is a hope anymore for xiaomi mi 6 or its a dead no?

[angelgod4]

And also why dont you let people with unsupported devices to try at their own risk? It may or may not work but it would also be a good indication that with good calibration the device is ready to run as expected

[celsourroz]

@angelgod4, if you succeed to install a mod version or anything please let me know. I'm struggling as well ! I really want to use AR core on my mi6.

[inio]

@angelgod4 We're looking at ways for ambitious users to try ARCore on unsupported devices and maybe even help us refine and test calibrations for them, but this poses two problems:

1. We have no way to grant a specific user's device access to AR-Required apps, so this would likely be for development purposes only for the time being.
2. We don't have a way (yet) for users to help debug bad experiences with verbose logs or recordings or anything like that.

Until at least one of those two problems is fixed, providing a way for ARCore to run on uncertified devices is pretty low value both for us and users. Sorry 😞 .

[JesseyDeVaney]

I hope we get some sort of support for the Samsung Galaxy S7 active. I have tried a lot of different things to force it to work that I've read on reddit threads but it just freezes when it goes to load. I have heard of a way of making it work no matter what but that requires flashing the zip of the apk and renaming the what classifies your device as to trick it into working and there is a way to do this without rooting. But thats way to much effort. I just hope it becomes supported. I even downgraded to older version of AR Core that were to suppose to help with support for AR Core but still to no avail. Crossing fingers.

[smurfhunter]

Going to +1 #597. The oneplus 3 and 3T have the exact same rear camera and are otherwise almost identical. There's no real feasible reason to not also support the device

[mwvent]

@inio Re: We're looking at ways for ambitious users to try ARCore on unsupported devices.
At a glance it seems the current ARKit searches it's device_profile_2 folder for a file matching the device fingerprint. Could I suggest opening up device_profile_2_database to enthusiasts by adding a folder on the SD card to the search path.
This would allow me to create for example a device_profile_zeroflte_colon_7.textproto file for my Galaxy S6 and drop in calibration data from a similar model as a starting point.
I'd say high value for the community vs the size of such a change it also removes the temptation for end users to root their phones just to try this out ( so tempted myself but no must not )

[smurfhunter]

@mwvent I submitted #605 regarding that

[SekhmetOrb]

What about Xperia XZ? Why just Xperia XZ Premium? Please make it happen!

[jackssl]

Hi Developers ,
Please Support For ARCore For Asus Zenfone 5Z (ZS621KL/ ZS620
KL) This Is Latest Flagship Killer . Why You Are Not Supporting Asus Zenfone 5Z.. Please Give Support

[yasinjavaid]

Hi
I need support for Samsung Galaxy A7 2016 Model = SM-A710FD.
updated to Google 7.0

[yasinjavaid]

Hi Please add support for Samsung Galaxy A7 2016 Model = SM-A710FD.

[cyberluke]

Google has "the best in class" support for their products. Nobody reading
this, people. Go try to call Google HQ on the phone.

On Mon, Oct 22, 2018 at 7:34 AM yasinjavaid [e-mail]
wrote:

Hi Please add support for Samsung Galaxy A7 2016 Model = SM-A710FD.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/google-ar/arcore-android-sdk/issues/89#issuecomment-431742587,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABD1TyxQZDuzuK1dN25fn7bD8mZ5tLQSks5unVjQgaJpZM4REE1a
.

[Fernandoooooooo]

Tengo una duda, ¿por qué el modelo Samsung Galaxy a6+ 2018 no aplica para el uso de ARcore de Google si cumple con todos sus requisitos? Me intriga porque los modelos Samsung Galaxy a6 2018 y Samsung Galaxy a5 si están en su lista de aprobados, siendo el modelo que menciono de mayor calidad.

[DIGISHORT]

Hello, any possibility of support for the S7/S8 Active models in the next update or minor update? They do have very similar internals compared to their vanilla counterparts.

[Garuxa]

Can you add the support for Huawei Mate 9 (MHA-L29)?

[ExSport]

@inio And where we can ask for support? Huawei P20 Pro has official support but recently some change happened and Google Play shows device is not supported anymore. Using email contact for ArCore in GP is useless as it is no-reply mail redirecting to know-how page where it is not possible to create new issue?
Thanks

[TasukiFB]

Please add AR Core support for the HTC u12+ it's plenty well compatable and its a flagship phone not sure why it hasn't already been added yet.

[inio]

@ExSport and others asking about the P20:

A recent OS update for the Huawei P20 device family has resulted in some devices experiencing poor motion tracking performance. To minimize bad user experiences, we have temporarily disabled access to ARCore and AR-Required apps on the affected devices.

We are evaluating a workaround for this issue in ARCore V1.6, which should be released in the coming weeks. We hope to re-enable all affected devices at that time.

[ExSport]

@inio Many thanks for response.
Happy that future version will make it more compatible with P20 but is it a good path? Huawei should fix it by own or support for ArCore should be withdrawn. With your workaround there will not be any pressure on them to fix it :-(

[TasukiFB]

No reply to the HTC line of phones? Everything above the HTC 10 can run this software so what is Google's delay? Or are they delaying it or won't use it because of what they did to HTC?

[dementia2029]

Huawei p20 pro - "This device does not support AR"

[shendibrani]

Would be nice to add support for Xiaomi Mi A2, or at least give an explanation as to why it isn't supported. As it runs Android One, latest stock google android, and has hardware better than most supported phones on the list.

[nidss]

Any plans to support OPPO Find X?

[Margulka]

I would really like it if you released the ARCore for Samsung Galaxy A6+. ARCore is aviable for A6, but not for A6+.

[backpacker69]

Please support Samsung S8 Active

[inio]

@backpacker69 Many enhanced durability devices don't have consistent enough IMU<->Camera geometry due to the camera module being mounted on shock absorbers. I believe the S8 Active falls into this category.

[DIGISHORT]

@inio Is there any way we can privately test ARCore on the S8 Active and report how it performs using various AR Applications?

I have observed others placing ARCore on unsupported phones through third party means. S8 Active unfortunately cannot use such third parties due to firmware limitations of the S8 Line specifically so I can't say myself on how it performs. I am very much willing to help any way I could with bringing ARCore to S8 Acctive!

[ghost]

Support for Samsung Galaxy A6+?

[littleylv]

Any plans to support Cat S61?

[lam-hoang]

Any plans to support Galaxy Note Fan Edition?

[ZiadJ]

So A7(2017) is supported but A7(2018) isn't. Not sure I can make sense out of it or may someone else here can.

[romfeo]

What does it mean for Xiaomi's devices that there is "No support for CPU image access"?

[inio]

@romanvfp It means that the Frame.acquireCameraImage() API will always throw NotYetAvailableException.

Unfortunately on these devices, when an ImageReader and SurfaceTexture are connected to the camera, frames are delivered to the ImageReader as much as 100ms after being delivered to the SurfaceTexture. Our motion tracking can handle this (you just get 100ms more IMU integration), but it prevents us from providing synchronized textures and CPU images.

[brookmg]

I just saw J5 and J7 are supported. What about J6 (2018)?

[MrMuzzio]

As others have commented would it be great to have support for the Samsung A6+

[hcostelha]

Would it be possible to have the Epson BT-350 supported?

[moheydy]

please Add Samsung A7 2018 how this not working but honor 8x or nova3i supported, the new phone galaxy A like Galaxy A9 or a7 2018, or a6+ not working with Arcore

[gessel]

I'd argue for the active line or other rugged phones, though they tend to represent a smaller segment of the market, as one of the key applications of AR on mobile devices is field work: MRO, survey, military, construction, etc. Rugged devices are targeted to these field applications.

To date, one of the most compelling demonstrations I've ever seen of AR was an early 90s AR implementation of wiring route cards for aircraft specific 747 build and service support.

Compelling applications might include underground service maps, GIS overlays, field measurement and sighting, etc. All of these are well matched to rugged phones. Samsung's apparent end of support of the active line with the S8a is unfortunate, but other vendors continue to find the niche relevant. I would hope that the AR team would as well.

[agGitHub]

@inio
Would be great if it would not be possible for a user who does not have a compatible phone to be able to give a rating... As we can see on @ExSport screenshot. Very unfair for the developers!

[ExSport]

@agGitHub You are funny or you don't understand the conversation at all.

• where you see I gave any ratings?
• phone was compatible from date of market availability and one day it lost the compatibility, so I asked why
• if you will read other posts from inio, you will know why. Now it is supported again

Don't understand your post at all, sorry. Btw. will write it again, I still made no ratings at all for this app.

[agGitHub]

@ExSport You don't understand what I meant. I just see on your screenshot that it seems possible to give a rating to the ARCore app from a device that is not compatible with ARCore. I just wonder if it is also the case for the ARCore apps (using ARCore SDK). If it is the case (highly probable), it is not a convenient behaviour. It should not be possible as it may induce 1 star ratings like 'app not compatible with my device'.

[ExSport]

Ok, sorry, now understand your point :+1:

[Pavel401]

plz add support for A6+ samsung A6 is already supported

[Anirudh901]

Please Add Razer Phone 2 as a supported device? Razer phone 1 was supported in 1.5 and it should work fine if the device id verification is taken away ( camera is the same as the pixel 3 and it has a vanilla android with a light skin and has enough power to support it )

[HandaTakuya]

Please add Mi A2 to support ARCore By Google

[ryurinri]

Please please please add SAMSUNG GALAXY A9!
It's ridiculous that all the older models have this feature and the more powerful A9 doesn't! I know it came out recently but... I hope it'll be supported soon!!

[w1477olk]

Asus Zenfone 5Z(ZS620KL) please?
Thanks a lot :D

[baloo887]

Guys, I don't know how you decide which phone Is supported and which not, but I'm tired to wait for support of phones that should already have these features (like Xiaomi mi A1/ mi A2, lot of latest Samsung and so on). I'm really sorry to write this but I'm quitting android and move to iOS for AR...arkit Is already supported by all iPhone/iPad models and there i can develop and release application to a greather number of user.
I Hope that you're able to increase the number of supported devices so I can come back to Android and use Arcore

[dawids162]

Hi. Will Huawei mate 10 pro be supported?

[eljuko]

Would love to see A7(2018) support.

[0x00x0]

Please, add LG V20 (H990DS) and regional variants (if possible) support.
Thanks in advance!

[AlexInTheEcho]

What happens with xiaomi? Since months there are only 4-5 devices in the list and the newest smartphones are not supported, like Mi9, Blackshark 2, Redmi Note 7... And Google are ignoring the rest, the Mi A family, Redmi Note 5, Mi8 lite, and stuff. Because of hardware they are capables of running Arcore. What happens? They are gonna have support eventually?

[soroush-sarabi]

A7(2017) supported but A7(2018) not !! why???
What different between these two models?

[Garuxa]

Any updates on the Huawei Mate 9? The device has even already received official Android 9 and will receive another update

[bigbluewave]

I see the Samsung Galaxy J7 supported and wanted to request official support for the Samsung Galaxy J7 Refine (2018, Android 8.0, model SM-J737P).

[przemyslaw-latoch]

Any news about support for Xiaomi Mi 9?

[gut4]

Essential ph-1

[AlexInTheEcho]

I don't know if it's google fault or the other manufacturers, but I have to say that Arcore's support it's such a shame. It piss me off all that phones that are not in the list with similar hardware to other phones in the list are not supported because of yes. And the worst of the worst of this is the lack of information. Why are only flagships of Sony or Xiaomi supported and not their rest of their devices? I don't know. Why the Samsung Galaxy A7 of 2017 are supported, and the A7 of 2018 not? I don't know. And the Xiaomi Mi 9? And this keeps going on. This incoherences, the lack of information, all of this it's so frustrating, and this push users to do a stupid root

[SekhmetOrb]

I don't know if it's google fault or the other manufacturers, but I have to say that Arcore's support it's such a shame. It piss me off all that phones that are not in the list with similar hardware to other phones in the list are not supported because of yes. And the worst of the worst of this is the lack of information. Why are only flagships of Sony or Xiaomi supported and not their rest of their devices? I don't know. Why the Samsung Galaxy A7 of 2017 are supported, and the A7 of 2018 not? I don't know. And the Xiaomi Mi 9? And this keeps going on. This incoherences, the lack of information, all of this it's so frustrating, and this push users to do a stupid root

Exactly. Thank you @AlexInTheEcho . "Buy our new phones because you won't have ArCore even if your phone is better than ours :) hehehehe", stupid.

[PrincessW0lf]

Hi - would love to see support added for Samsung Galaxy A9 please!

Thanks

[AndroidLibrariesYoutube]

Support request for Xiomi Mi A1

[kmitchell6]

Please support Nokia 9. Thank you.

[AlexInTheEcho]

Support the rest of Xiaomi's devices please, Redmi Note 5, mi8 lite, redmi note 7, etc

[adirmd]

Request for Galaxy A9 2018

[sorosunrain]

Will Xiaomi mi 9 be supported?

[BPMOmega]

I'd also like to see Razer Phone 2 [cheryl2] added as a supported device. Seems the Razer Phone 1 [cheryl] was added back in v1.5, so it's strange to see its stronger successor isn't supported.

[dodofish]

Please add support of HTC U11, thank you!

[ginestopo]

Huawei Mate 10 please. It is capable of moving AR and advanced graphics. I need it before minecraft earth is released :(

[Tegzek]

Add HTC U11 support, it is more powerful than Mate 20 Lite, G6, Galaxy S7 but has no support ;// Also please add other HTC smartphones. U11 will receive android 9 soon.

[GenericBleach]

Essential PH-1 please

[andrewapperley]

Essential PH-1 and eventually the PH-2 ;)

[whymoo]

Essential ASAP please

[luxferro]

No ARcore support for Essential PH-1 after all this time.

No support for Wireless Android Auto for devices other than Pixels, even though Google said it would come to all phones on Android 9, and some on 8.

Using proprietary wireless changing on Pixel phones.

Google sucks...

[spargonaut]

yet another request to add support for the Essential PH-1.

[NvrBst]

Essential PH-1 Support for ARCore Please. The Essential team submitted a request OVER A YEAR AGO! Why has it not been approved and implemented? It is one of the few phones with Android Q updates... but still no ARCore?

[the-jose-sanchez]

Can you please add support to the Essential PH-1? It should be decently powerful has been out for 2 years... not having ARCore.

[AlexInTheEcho]

Seriously, can anyone of google explain all this requests? Explain WHY all this phones are not yet supported? People are mad at this because of this lack of information. This is frustrating. I'm still waiting for the support for Xiaomi's devices like Redmi Note 5, Mi8 lite, Redmi note 7 etc

[Thaina]

@AlexInTheEcho To be fair. They already explain above in some comment

The problem lied on implementation of ARCore system right now. Simply put, google try to use some hacky technique to enable AR on the phone. They use the shakiness of our hand to emulate dual camera

The upside of this technique is it possible to enable ARCore in many device without dual camera or depth camera
But the downside is, actual device in the world have difference hardware, some has spring around camera, some has sponge, some has nothing, there were many bits difference that could affect the input of shakiness image of each frame

And so the ARCore team need to take time in many months to get each device and calibrate each device manually just to have ARCore can be run in that device in acceptable quality

To be fair again. I understand them. But seriously, I don't agree that they choose this way to do their job, it not practical at all. They should rethink the whole process. It obviously that this process can't match up with the amount of new phone released in market

[horstle]

Thanks for adding the Mi 9.

[ManuelTS]

Please add Nokia 7 Plus support, right now its buggy as in #764 and as explained here:

I updated my Nokia 7 Plus Android 9 API 28 and the AR Core App to 1.10.0, it did not work with the 1.9.0 version of ARCore App neither. The Nokia 7 Plus Android 9 API 28 only works with the 1.8.0 ARCore app. I cannot develop on the newest version now.

When I try to deploy my app with Android Studio 3.4.1, it reports (just search for exception and shutdown):

I: [99] imb.run(3): Stats for Executor: BlockingExecutor ink@1ddfcc3[Running, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 19]
I: [99] imb.run(3): Stats for Executor: LightweightExecutor ink@5a3940[Running, pool size = 4, active threads = 0, queued tasks = 0, completed tasks = 61]
I: [99] imb.run(3): Stats for Executor: bgExecutor ink@b5c1079[Running, pool size = 4, active threads = 0, queued tasks = 0, completed tasks = 56]
I: [2] uwo.a(6): Verification requested, id = 23
E: [2] vhp.a(2): Package name null is not an installed package
I: [121] uxo.a(2): Single user settings service is not running, bind it now
I: [2] uxs.onServiceConnected(1): Single user settings service is connected
W: Setting install_non_market_apps has moved from android.provider.Settings.Global to android.provider.Settings.Secure, returning read-only value.

    --------- beginning of system
D: Processing new values: info={.chargerAcOnline = false, .chargerUsbOnline = true, .chargerWirelessOnline = false, .maxChargingCurrent = 500000, .maxChargingVoltage = 5000000, .batteryStatus = CHARGING, .batteryHealth = GOOD, .batteryPresent = true, .batteryLevel = 100, .batteryVoltage = 4396, .batteryTemperature = 290, .batteryCurrent = -121, .batteryCycleCount = 1, .batteryFullCharge = 3862000, .batteryChargeCounter = 3838748, .batteryTechnology = Li-ion}, mBatteryLevelCritical=false, mPlugType=2
I: shutdownIfLowCurrentLocked batteryLevel = 100 , hasChargingCurrent = true(isPowered=true,batteryCurrent=-121,hardware=qcom) , hitShutdownVoltage = true(batteryVoltage=4396,mBatteryMinVoltage=-1) , isSystemReady = true
D: Sending ACTION_BATTERY_CHANGED. scale:100, info:{.chargerAcOnline = false, .chargerUsbOnline = true, .chargerWirelessOnline = false, .maxChargingCurrent = 500000, .maxChargingVoltage = 5000000, .batteryStatus = CHARGING, .batteryHealth = GOOD, .batteryPresent = true, .batteryLevel = 100, .batteryVoltage = 4396, .batteryTemperature = 290, .batteryCurrent = -121, .batteryCycleCount = 1, .batteryFullCharge = 3862000, .batteryChargeCounter = 3838748, .batteryTechnology = Li-ion}, EXTRA_WIRELESS_CHARGER_DISABLE = false
D: mIsPowerLEDBehavior =false
D: mAmbientMode=false
D: resetWhenChargingLongTime resetTime=25200000 ,mchargingUPTime=5928338 , (resetTime-(uptime-mchargingUPTime))=23560798 ,onBattery=false
D: received broadcast android.intent.action.BATTERY_CHANGED
D: ACTION_BATTERY_CHANGED...maxChargingMicroAmp: 500000 maxChargingMicroVolt: 5000000 current: -121000 isDisableWireless: false
D: handleBatteryUpdate
D: mPluggedIn = true;mCharging =true; status=2; level=100
D: WARNING, no carrier configs on phone Id: 0
I: updateShowPercent showPercent: 0 mUseSmallBatteryLevel: false mAllowShowPercentage: true
I: isHideWaring mHideWaring: false
I: updateShowPercent showPercent: 0 mUseSmallBatteryLevel: false mAllowShowPercentage: true
I: isHideWaring mHideWaring: false
I: updateShowPercent showPercent: 0 mUseSmallBatteryLevel: false mAllowShowPercentage: true
I: isHideWaring mHideWaring: false
I: ACTION_BATTERY_CHANGED -> Temprature : 29.0
I: DetectBatteryService: MaxTempShutDown : false
I: DetectBatteryService: LowTempShutDown : false
I: IS_SUPPORT_DECREASE_CHARGING : true
D: getConfig() : srsId = F_REMOVE_LOW_BATTERY_NOTIFY result = false type = bool pkg = com.android.systemui
V: battery_level_update
V: [battery_level_update][931] [HC] =>> [HS]
V: [batteryLevelUpdate][777] [HS] <<<<= [HC]
V: Exit Result 0
D: layoutOwnerInfo true..1.0
W: Failure retrieving text 0x7f100032 in package at.mts.arnatomy
    android.content.res.Resources$NotFoundException: String resource ID #0x7f100032
        at android.content.res.Resources.getText(Resources.java:348)
        at android.app.ApplicationPackageManager.getText(ApplicationPackageManager.java:1709)
        at android.content.pm.PackageItemInfo.loadUnsafeLabel(PackageItemInfo.java:223)
        at android.content.pm.PackageItemInfo.loadLabel(PackageItemInfo.java:199)
        at vcd.f(SourceFile:35)
        at vcd.c(SourceFile:1)
        at vea.c(SourceFile:7)
        at vjl.run(Unknown Source:2)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
        at iml.run(Unknown Source:5)
        at java.lang.Thread.run(Thread.java:764)
I: [121] vhp.c(2): PSIC verification started with installer uid: 2000 package name: null, originating uid: -1
I: [2] vea.c(3): Verifying id=23, result=1
I: [2] vea.b(6): Verification complete: id=23, package_name=at.mts.arnatomy
I: Killing 15144:com.google.android.webview:webview_service/u0a157 (adj 906): empty for 1800s
W: kill(-15144, 9) failed: No such process
W: Unknown element under <manifest>: uses-sdk at /data/app/vmdl478945630.tmp/split_lib_resources_apk.apk Binary XML file line #7
I: isSignLostPlatformPKey:false
D: manageDisableList userId=0 what=0x0 pkg=Window{faf5da9 u0 StatusBar}
D: disableLocked net1 = 0; net2 = 0 pkg=Window{faf5da9 u0 StatusBar}
I: Process 15144 exited due to signal (9)
D: hiding the MENU button
W: kill(-15144, 9) failed: No such process
I: Successfully killed process cgroup uid 10157 pid 15144 in 38ms
I: Force stopping at.mts.arnatomy appid=10253 user=-1: installPackageLI
I: Update package at.mts.arnatomy code path from /data/app/at.mts.arnatomy-qR6O86ozgPSq5FmzDlCZZA== to /data/app/at.mts.arnatomy-K_dqM83Mx0pNmFLNP5Ii5A==; Retain data and using new
I: Update package at.mts.arnatomy resource path from /data/app/at.mts.arnatomy-qR6O86ozgPSq5FmzDlCZZA== to /data/app/at.mts.arnatomy-K_dqM83Mx0pNmFLNP5Ii5A==; Retain data and using new
D: collectAdvancedAppsInfo ...
D: at.mts.arnatomy -> resizable apps -> INSTALL
I: [SW3]StatsLog PKG_ADM__ADM__MODIFY, isSystemApp:false
W: not interested in atom 130605
D: log source 1000 is allowed for fih atoms
D: log source 1000 is allowed for fih atoms
W: not interested in atom 130602
D: log source 1000 is allowed for fih atoms
D: log source 1000 is allowed for fih atoms
I: Verifying IntentFilter. verificationId:9 scheme:"https" hosts:"mts.at" package:"at.mts.arnatomy".
E: *~*~*~ Channel {0} was not shutdown properly!!! ~*~*~*
        Make sure to call shutdown()/shutdownNow() and wait until awaitTermination() returns true.
    java.lang.RuntimeException: ManagedChannel allocation site
        at cclc.<init>(:com.google.android.gms@[email protected] (100400-248795830):1)
        at cckz.<init>(:com.google.android.gms@[email protected] (100400-248795830):2)
        at ccdo.b(:com.google.android.gms@[email protected] (100400-248795830):14)
        at rzc.a(:com.google.android.gms@[email protected] (100400-248795830):43)
        at rzc.a(:com.google.android.gms@[email protected] (100400-248795830):58)
        at atbl.a(:com.google.android.gms@[email protected] (100400-248795830):9)
        at atbl.a(:com.google.android.gms@[email protected] (100400-248795830):26)
        at qbi.run(:com.google.android.gms@[email protected] (100400-248795830):1)
        at sgs.b(:com.google.android.gms@[email protected] (100400-248795830):37)
        at sgs.run(:com.google.android.gms@[email protected] (100400-248795830):21)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
        at smq.run(Unknown Source:7)
        at java.lang.Thread.run(Thread.java:764)
W: [{0}] Failed to resolve name. status={1}
W: Error performing check: 
I: Explicit concurrent copying GC freed 198208(10MB) AllocSpace objects, 82(2MB) LOS objects, 42% free, 16MB/29MB, paused 788us total 351.729ms
E: Failed to delete /data/app/vmdl478945630.tmp: No such file or directory
I: Force stopping at.mts.arnatomy appid=10253 user=0: pkg removed
W: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REMOVED dat=package:at.mts.arnatomy flg=0x4000010 (has extras) } to com.android.musicfx/.Compatibility$Receiver
I: Reconfiguring input devices.  changes=0x00000010
I: action=android.intent.action.PACKAGE_REMOVED removing=false
D: handleSavePolicyFile
W: A resource failed to call release. 
W: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REMOVED dat=package:at.mts.arnatomy flg=0x4000010 (has extras) } to com.android.vending/com.google.android.finsky.packagemanager.impl.PackageMonitorReceiverImpl$RegisteredReceiver
W: A resource failed to call release. 
I: putStringForUser: This is only for showing who is modifying the [enabled_notification_listeners],value :com.android.launcher3/com.android.launcher3.notification.NotificationListener
    java.lang.RuntimeException
        at android.provider.Settings$NameValueCache.putStringForUser(Settings.java:2027)
        at android.provider.Settings$Secure.putStringForUser(Settings.java:5046)
        at android.provider.Settings$Secure.putStringForUser(Settings.java:5029)
        at com.android.server.notification.ManagedServices.writeXml(ManagedServices.java:325)
        at com.android.server.notification.NotificationManagerService.writePolicyXml(NotificationManagerService.java:662)
        at com.android.server.notification.NotificationManagerService.handleSavePolicyFile(NotificationManagerService.java:644)
        at com.android.server.notification.NotificationManagerService.access$8000(NotificationManagerService.java:259)
        at com.android.server.notification.NotificationManagerService$WorkerHandler.handleMessage(NotificationManagerService.java:5793)
        at android.os.Handler.dispatchMessage(Handler.java:107)
        at android.os.Looper.loop(Looper.java:198)
        at com.android.server.SystemServer.run(SystemServer.java:479)
        at com.android.server.SystemServer.main(SystemServer.java:307)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:838)
I: putStringForUser: This is only for showing who is modifying the [enabled_notification_assistant],value :com.google.android.ext.services/android.ext.services.notification.Assistant
    java.lang.RuntimeException
        at android.provider.Settings$NameValueCache.putStringForUser(Settings.java:2027)
        at android.provider.Settings$Secure.putStringForUser(Settings.java:5046)
        at android.provider.Settings$Secure.putStringForUser(Settings.java:5029)
        at com.android.server.notification.ManagedServices.writeXml(ManagedServices.java:325)
        at com.android.server.notification.NotificationManagerService.writePolicyXml(NotificationManagerService.java:663)
        at com.android.server.notification.NotificationManagerService.handleSavePolicyFile(NotificationManagerService.java:644)
        at com.android.server.notification.NotificationManagerService.access$8000(NotificationManagerService.java:259)
        at com.android.server.notification.NotificationManagerService$WorkerHandler.handleMessage(NotificationManagerService.java:5793)
        at android.os.Handler.dispatchMessage(Handler.java:107)
        at android.os.Looper.loop(Looper.java:198)
        at com.android.server.SystemServer.run(SystemServer.java:479)
        at com.android.server.SystemServer.main(SystemServer.java:307)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:838)
I: putStringForUser: This is only for showing who is modifying the [enabled_notification_policy_access_packages],value :com.android.camera2:com.hmdglobal.camera2
    java.lang.RuntimeException
        at android.provider.Settings$NameValueCache.putStringForUser(Settings.java:2027)
        at android.provider.Settings$Secure.putStringForUser(Settings.java:5046)
        at android.provider.Settings$Secure.putStringForUser(Settings.java:5029)
        at com.android.server.notification.ManagedServices.writeXml(ManagedServices.java:325)
        at com.android.server.notification.NotificationManagerService.writePolicyXml(NotificationManagerService.java:664)
        at com.android.server.notification.NotificationManagerService.handleSavePolicyFile(NotificationManagerService.java:644)
        at com.android.server.notification.NotificationManagerService.access$8000(NotificationManagerService.java:259)
        at com.android.server.notification.NotificationManagerService$WorkerHandler.handleMessage(NotificationManagerService.java:5793)
        at android.os.Handler.dispatchMessage(Handler.java:107)
        at android.os.Looper.loop(Looper.java:198)
        at com.android.server.SystemServer.run(SystemServer.java:479)
        at com.android.server.SystemServer.main(SystemServer.java:307)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:838)
I: onReceive():android.intent.action.PACKAGE_ADDED
W: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REMOVED dat=package:at.mts.arnatomy flg=0x4000010 (has extras) } to com.android.vending/com.google.android.finsky.instantapps.appmanagement.InstantAppRemoveMonitor
W: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REMOVED dat=package:at.mts.arnatomy flg=0x4000010 (has extras) } to com.evenwell.bboxsbox/com.fihtdc.bboxsbox.IntentReceiver
W: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REMOVED dat=package:at.mts.arnatomy flg=0x4000010 (has extras) } to com.google.android.gms/.games.chimera.GamesSystemBroadcastReceiverProxy
W: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REMOVED dat=package:at.mts.arnatomy flg=0x4000010 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
I: [2] com.google.android.finsky.packagemanager.impl.PackageMonitorReceiverImpl.a(4): PackageMonitor received: android.intent.action.PACKAGE_ADDED
W: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REMOVED dat=package:at.mts.arnatomy flg=0x4000010 (has extras) } to com.google.android.googlequicksearchbox/com.google.android.apps.gsa.googlequicksearchbox.GelStubAppWatcher
W: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:at.mts.arnatomy flg=0x4000010 (has extras) } to com.android.musicfx/.Compatibility$Receiver
I: onReceive():android.intent.action.PACKAGE_REPLACED
W: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:at.mts.arnatomy flg=0x4000010 (has extras) } to com.android.vending/com.google.android.finsky.packagemanager.impl.PackageMonitorReceiverImpl$RegisteredReceiver
W: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:at.mts.arnatomy flg=0x4000010 (has extras) } to com.evenwell.bboxsbox/com.fihtdc.bboxsbox.IntentReceiver
W: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:at.mts.arnatomy flg=0x4000010 (has extras) } to com.google.android.gms/.games.chimera.GamesSystemBroadcastReceiverProxy
W: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:at.mts.arnatomy flg=0x4000010 (has extras) } to com.google.android.gms/.gass.chimera.PackageChangeBroadcastReceiver
W: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:at.mts.arnatomy flg=0x4000010 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
W: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:at.mts.arnatomy flg=0x4000010 (has extras) } to com.google.android.googlequicksearchbox/com.google.android.apps.gsa.googlequicksearchbox.GelStubAppWatcher
W: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_ADDED dat=package:at.mts.arnatomy flg=0x4000010 (has extras) } to com.google.android.ims/.receivers.RcsAutoStartReceiver
I: [2] vxb.a(11): Do not start WearSupportService due to Wear service optimization
I: onReceive(package): no push data changed
I: Background concurrent copying GC freed 113440(6MB) AllocSpace objects, 22(952KB) LOS objects, 49% free, 12MB/24MB, paused 72us total 102.297ms
I: [2] nlv.b(2): Frosting ID looked up on UI thread. Caller should move to a background thread.
E: Reading a NULL string not supported here.
I: onReceive(package): no push data changed
D: uninstall packageName:at.mts.arnatomy
I: [2] com.google.android.finsky.packagemanager.impl.PackageMonitorReceiverImpl.a(4): PackageMonitor received: android.intent.action.PACKAGE_ADDED
I: [2] vxb.a(11): Do not start WearSupportService due to Wear service optimization
E: No package ID 7f found for ID 0x7f08006e.
E: No package ID 7f found for ID 0x7f100062.
E: No package ID 7f found for ID 0x7f100064.
E: No package ID 7f found for ID 0x7f100063.
I: Reconfiguring input devices.  changes=0x00000010
I: putStringForUser: This is only for showing who is modifying the [accessibility_enabled],value :0
    java.lang.RuntimeException
        at android.provider.Settings$NameValueCache.putStringForUser(Settings.java:2027)
        at android.provider.Settings$Secure.putStringForUser(Settings.java:5046)
        at android.provider.Settings$Secure.putStringForUser(Settings.java:5029)
        at android.provider.Settings$Secure.putIntForUser(Settings.java:5259)
        at com.android.server.accessibility.AccessibilityManagerService.updateAccessibilityEnabledSetting(AccessibilityManagerService.java:1932)
        at com.android.server.accessibility.AccessibilityManagerService.updateServicesLocked(AccessibilityManagerService.java:1600)
        at com.android.server.accessibility.AccessibilityManagerService.onUserStateChangedLocked(AccessibilityManagerService.java:1782)
        at com.android.server.accessibility.AccessibilityManagerService.access$600(AccessibilityManagerService.java:142)
        at com.android.server.accessibility.AccessibilityManagerService$1.onSomePackagesChanged(AccessibilityManagerService.java:344)
        at com.android.internal.content.PackageMonitor.onReceive(PackageMonitor.java:451)
        at android.app.LoadedApk$ReceiverDispatcher$Args.lambda$getRunnable$0(LoadedApk.java:1391)
        at android.app.-$$Lambda$LoadedApk$ReceiverDispatcher$Args$_BumDX2UKsnxLVrE6UJsJZkotuA.run(Unknown Source:2)
        at android.os.Handler.handleCallback(Handler.java:874)
        at android.os.Handler.dispatchMessage(Handler.java:100)
        at android.os.Looper.loop(Looper.java:198)
        at android.os.HandlerThread.run(HandlerThread.java:65)
I: putStringForUser: This is only for showing who is modifying the [accessibility_shortcut_target_service],value :null
    java.lang.RuntimeException
        at android.provider.Settings$NameValueCache.putStringForUser(Settings.java:2027)
        at android.provider.Settings$Secure.putStringForUser(Settings.java:5046)
        at android.provider.Settings$Secure.putStringForUser(Settings.java:5029)
        at com.android.server.accessibility.AccessibilityManagerService.updateAccessibilityShortcutLocked(AccessibilityManagerService.java:2124)
        at com.android.server.accessibility.AccessibilityManagerService.onUserStateChangedLocked(AccessibilityManagerService.java:1783)
        at com.android.server.accessibility.AccessibilityManagerService.access$600(AccessibilityManagerService.java:142)
        at com.android.server.accessibility.AccessibilityManagerService$1.onSomePackagesChanged(AccessibilityManagerService.java:344)
        at com.android.internal.content.PackageMonitor.onReceive(PackageMonitor.java:451)
        at android.app.LoadedApk$ReceiverDispatcher$Args.lambda$getRunnable$0(LoadedApk.java:1391)
        at android.app.-$$Lambda$LoadedApk$ReceiverDispatcher$Args$_BumDX2UKsnxLVrE6UJsJZkotuA.run(Unknown Source:2)
        at android.os.Handler.handleCallback(Handler.java:874)
        at android.os.Handler.dispatchMessage(Handler.java:100)
        at android.os.Looper.loop(Looper.java:198)
        at android.os.HandlerThread.run(HandlerThread.java:65)
I: putStringForUser: This is only for showing who is modifying the [accessibility_shortcut_enabled],value :0
    java.lang.RuntimeException
        at android.provider.Settings$NameValueCache.putStringForUser(Settings.java:2027)
        at android.provider.Settings$Secure.putStringForUser(Settings.java:5046)
        at android.provider.Settings$Secure.putStringForUser(Settings.java:5029)
        at android.provider.Settings$Secure.putIntForUser(Settings.java:5259)
        at com.android.server.accessibility.AccessibilityManagerService.updateAccessibilityShortcutLocked(AccessibilityManagerService.java:2128)
        at com.android.server.accessibility.AccessibilityManagerService.onUserStateChangedLocked(AccessibilityManagerService.java:1783)
        at com.android.server.accessibility.AccessibilityManagerService.access$600(AccessibilityManagerService.java:142)
        at com.android.server.accessibility.AccessibilityManagerService$1.onSomePackagesChanged(AccessibilityManagerService.java:344)
        at com.android.internal.content.PackageMonitor.onReceive(PackageMonitor.java:451)
        at android.app.LoadedApk$ReceiverDispatcher$Args.lambda$getRunnable$0(LoadedApk.java:1391)
        at android.app.-$$Lambda$LoadedApk$ReceiverDispatcher$Args$_BumDX2UKsnxLVrE6UJsJZkotuA.run(Unknown Source:2)
        at android.os.Handler.handleCallback(Handler.java:874)
        at android.os.Handler.dispatchMessage(Handler.java:100)
        at android.os.Looper.loop(Looper.java:198)
        at android.os.HandlerThread.run(HandlerThread.java:65)
I: Reconfiguring input devices.  changes=0x00000010
I: [2] nlv.b(2): Frosting ID looked up on UI thread. Caller should move to a background thread.
I: [2] com.google.android.finsky.packagemanager.impl.PackageMonitorReceiverImpl.a(4): PackageMonitor received: android.intent.action.PACKAGE_ADDED
I: Received intent with action android.intent.action.PACKAGE_REMOVED
I: [2] vxb.a(11): Do not start WearSupportService due to Wear service optimization
I: [2] nlv.b(2): Frosting ID looked up on UI thread. Caller should move to a background thread.
E: [PhoneIntfMgr] getCarrierPackageNamesForIntent: No UICC
D: No carrier app for: 0
I: [SupervisedAccountIntentOperation] onHandleIntent(): android.intent.action.PACKAGE_ADDED
I: [SupervisedAccountIntentOperation] This operation is disabled
E: [PhoneIntfMgr] getCarrierPackageNamesForIntent: No UICC
D: No carrier app for: 1
E: [PhoneIntfMgr] getCarrierPackageNamesForIntent: No UICC
D: No carrier app for: 0
E: [PhoneIntfMgr] getCarrierPackageNamesForIntent: No UICC
D: No carrier app for: 1
W: Slow dispatch took 107ms main h=com.android.server.notification.NotificationManagerService$WorkerHandler c=null m=3
I: [Sync,SyncIntentOperation] Handling the intent: Intent { act=android.intent.action.PACKAGE_ADDED dat=package:at.mts.arnatomy flg=0x4000010 cmp=com.google.android.gms/.chimera.GmsIntentOperationService (has extras) }.
W: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REPLACED dat=package:at.mts.arnatomy flg=0x4000010 (has extras) } to com.android.musicfx/.Compatibility$Receiver
W: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REPLACED dat=package:at.mts.arnatomy flg=0x4000010 (has extras) } to com.evenwell.CPClient/.CPReceiver
W: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REPLACED dat=package:at.mts.arnatomy flg=0x4000010 (has extras) } to com.evenwell.batteryprotect/.BatteryProtectOnReceiver
W: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REPLACED dat=package:at.mts.arnatomy flg=0x4000010 (has extras) } to com.google.android.gms/.gass.chimera.PackageChangeBroadcastReceiver
W: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REPLACED dat=package:at.mts.arnatomy flg=0x4000010 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
W: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REPLACED dat=package:at.mts.arnatomy flg=0x4000010 (has extras) } to com.google.android.googlequicksearchbox/com.google.android.apps.gsa.googlequicksearchbox.GelStubAppWatcher
W: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REPLACED dat=package:at.mts.arnatomy flg=0x4000010 (has extras) } to com.google.android.ims/.receivers.RcsAutoStartReceiver
E: cannot create TelephonyManager from ComponentInfo{com.android.phone/com.android.services.telephony.TelephonyConnectionService}, ***, UserHandle{0}
D: android.intent.action.PACKAGE_REPLACED , package name:at.mts.arnatomy
D: maybeAddedImsService, packageName: at.mts.arnatomy
D: mHandler: 9 phoneId: 0
I: Background concurrent copying GC freed 3173(401KB) AllocSpace objects, 3(60KB) LOS objects, 42% free, 18MB/31MB, paused 1.108ms total 192.062ms
D: Processing new values: info={.chargerAcOnline = false, .chargerUsbOnline = true, .chargerWirelessOnline = false, .maxChargingCurrent = 500000, .maxChargingVoltage = 5000000, .batteryStatus = CHARGING, .batteryHealth = GOOD, .batteryPresent = true, .batteryLevel = 100, .batteryVoltage = 4396, .batteryTemperature = 290, .batteryCurrent = -121, .batteryCycleCount = 1, .batteryFullCharge = 3862000, .batteryChargeCounter = 3838800, .batteryTechnology = Li-ion}, mBatteryLevelCritical=false, mPlugType=2
I: shutdownIfLowCurrentLocked batteryLevel = 100 , hasChargingCurrent = true(isPowered=true,batteryCurrent=-121,hardware=qcom) , hitShutdownVoltage = true(batteryVoltage=4396,mBatteryMinVoltage=-1) , isSystemReady = true
D: Sending ACTION_BATTERY_CHANGED. scale:100, info:{.chargerAcOnline = false, .chargerUsbOnline = true, .chargerWirelessOnline = false, .maxChargingCurrent = 500000, .maxChargingVoltage = 5000000, .batteryStatus = CHARGING, .batteryHealth = GOOD, .batteryPresent = true, .batteryLevel = 100, .batteryVoltage = 4396, .batteryTemperature = 290, .batteryCurrent = -121, .batteryCycleCount = 1, .batteryFullCharge = 3862000, .batteryChargeCounter = 3838800, .batteryTechnology = Li-ion}, EXTRA_WIRELESS_CHARGER_DISABLE = false
D: mIsPowerLEDBehavior =false
D: resetWhenChargingLongTime resetTime=25200000 ,mchargingUPTime=5928338 , (resetTime-(uptime-mchargingUPTime))=23559062 ,onBattery=false
D: mAmbientMode=false
I: Received intent with action android.intent.action.PACKAGE_REPLACED
I: action=android.intent.action.PACKAGE_ADDED removing=false
W: CP2 sync disabled by gservices.
D: topic sync succeeded
I: Received intent with action android.intent.action.PACKAGE_ADDED
I: DefaultDialerCache: Refreshing default dialer for user 0: now com.google.android.dialer: DDC.oR@ARg
I: onReceive : android.intent.action.PACKAGE_ADDED
V: getFullBackupIntervalMilliseconds(...) returns 86400000
D: handleSavePolicyFile
I: ACTION_BATTERY_CHANGED -> Temprature : 29.0
I: DetectBatteryService ACTION_BATTERY_CHANGED return !!
D: received broadcast android.intent.action.BATTERY_CHANGED
D: ACTION_BATTERY_CHANGED...maxChargingMicroAmp: 500000 maxChargingMicroVolt: 5000000 current: -121000 isDisableWireless: false
D: mPluggedIn = true;mCharging =true; status=2; level=100
I: updateShowPercent showPercent: 0 mUseSmallBatteryLevel: false mAllowShowPercentage: true
I: isHideWaring mHideWaring: false
V: battery_level_update
V: [battery_level_update][931] [HC] =>> [HS]
V: [batteryLevelUpdate][777] [HS] <<<<= [HC]
V: Exit Result 0
I: updateShowPercent showPercent: 0 mUseSmallBatteryLevel: false mAllowShowPercentage: true
I: isHideWaring mHideWaring: false
I: updateShowPercent showPercent: 0 mUseSmallBatteryLevel: false mAllowShowPercentage: true
I: isHideWaring mHideWaring: false
I: putStringForUser: This is only for showing who is modifying the [enabled_notification_listeners],value :com.android.launcher3/com.android.launcher3.notification.NotificationListener
    java.lang.RuntimeException
        at android.provider.Settings$NameValueCache.putStringForUser(Settings.java:2027)
        at android.provider.Settings$Secure.putStringForUser(Settings.java:5046)
        at android.provider.Settings$Secure.putStringForUser(Settings.java:5029)
        at com.android.server.notification.ManagedServices.writeXml(ManagedServices.java:325)
        at com.android.server.notification.NotificationManagerService.writePolicyXml(NotificationManagerService.java:662)
        at com.android.server.notification.NotificationManagerService.handleSavePolicyFile(NotificationManagerService.java:644)
        at com.android.server.notification.NotificationManagerService.access$8000(NotificationManagerService.java:259)
        at com.android.server.notification.NotificationManagerService$WorkerHandler.handleMessage(NotificationManagerService.java:5793)
        at android.os.Handler.dispatchMessage(Handler.java:107)
        at android.os.Looper.loop(Looper.java:198)
        at com.android.server.SystemServer.run(SystemServer.java:479)
        at com.android.server.SystemServer.main(SystemServer.java:307)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:838)
D: handleBatteryUpdate
I: putStringForUser: This is only for showing who is modifying the [enabled_notification_assistant],value :com.google.android.ext.services/android.ext.services.notification.Assistant
    java.lang.RuntimeException
        at android.provider.Settings$NameValueCache.putStringForUser(Settings.java:2027)
        at android.provider.Settings$Secure.putStringForUser(Settings.java:5046)
        at android.provider.Settings$Secure.putStringForUser(Settings.java:5029)
        at com.android.server.notification.ManagedServices.writeXml(ManagedServices.java:325)
        at com.android.server.notification.NotificationManagerService.writePolicyXml(NotificationManagerService.java:663)
        at com.android.server.notification.NotificationManagerService.handleSavePolicyFile(NotificationManagerService.java:644)
        at com.android.server.notification.NotificationManagerService.access$8000(NotificationManagerService.java:259)
        at com.android.server.notification.NotificationManagerService$WorkerHandler.handleMessage(NotificationManagerService.java:5793)
        at android.os.Handler.dispatchMessage(Handler.java:107)
        at android.os.Looper.loop(Looper.java:198)
        at com.android.server.SystemServer.run(SystemServer.java:479)
        at com.android.server.SystemServer.main(SystemServer.java:307)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:838)
I: putStringForUser: This is only for showing who is modifying the [enabled_notification_policy_access_packages],value :com.android.camera2:com.hmdglobal.camera2
    java.lang.RuntimeException
        at android.provider.Settings$NameValueCache.putStringForUser(Settings.java:2027)
        at android.provider.Settings$Secure.putStringForUser(Settings.java:5046)
        at android.provider.Settings$Secure.putStringForUser(Settings.java:5029)
        at com.android.server.notification.ManagedServices.writeXml(ManagedServices.java:325)
        at com.android.server.notification.NotificationManagerService.writePolicyXml(NotificationManagerService.java:664)
        at com.android.server.notification.NotificationManagerService.handleSavePolicyFile(NotificationManagerService.java:644)
        at com.android.server.notification.NotificationManagerService.access$8000(NotificationManagerService.java:259)
        at com.android.server.notification.NotificationManagerService$WorkerHandler.handleMessage(NotificationManagerService.java:5793)
        at android.os.Handler.dispatchMessage(Handler.java:107)
        at android.os.Looper.loop(Looper.java:198)
        at com.android.server.SystemServer.run(SystemServer.java:479)
        at com.android.server.SystemServer.main(SystemServer.java:307)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:838)
D: getConfig() : srsId = F_REMOVE_LOW_BATTERY_NOTIFY result = false type = bool pkg = com.android.systemui
D: WARNING, no carrier configs on phone Id: 0
D: [SW3]ServiceCached is the same, no need to write to file
D: Current default: ComponentInfo{com.google.android.gms/com.google.android.gms.tapandpay.hce.service.TpHceService}
D: Default payment service still ok.
D: onServicesUpdated
D: generateServiceMap component: ComponentInfo{com.google.android.gms/com.google.android.gms.tapandpay.hce.service.TpHceService}
D: Exact AID, resolving.
I: uid=1027(nfc) com.android.nfc identical 18 lines
D: Exact AID, resolving.
D: Not updating routing table because NFC is off.
D: layoutOwnerInfo true..1.0
D: Service unchanged, not updating
I: PackageUpdatedTask packages [at.mts.arnatomy] 2
W: com.qualcomm.location resolves service com.android.location.service.v3.NetworkLocationProvider, but has wrong signature, ignoring
W: com.google.android.gms resolves service com.android.location.service.v3.NetworkLocationProvider, but has wrong signature, ignoring
W: com.qualcomm.location resolves service com.android.location.service.v3.NetworkLocationProvider, but has wrong signature, ignoring
W: Odd, no component found for service com.android.location.service.v3.NetworkLocationProvider
I: [186] nlu.run(16): Wrote row to frosting DB: 1768
W: Slow dispatch took 112ms main h=com.android.server.notification.NotificationManagerService$WorkerHandler c=null m=3
I: IndexChimeraService.getServiceInterface callingPackage=com.google.android.gms componentName=AppsCorpus serviceId=SEARCH_CORPORA
I: IndexChimeraService.getServiceInterface callingPackage=com.google.android.gms componentName=AppsCorpus serviceId=SEARCH_QUERIES
D: Processing new values: info={.chargerAcOnline = false, .chargerUsbOnline = true, .chargerWirelessOnline = false, .maxChargingCurrent = 500000, .maxChargingVoltage = 5000000, .batteryStatus = CHARGING, .batteryHealth = GOOD, .batteryPresent = true, .batteryLevel = 100, .batteryVoltage = 4396, .batteryTemperature = 290, .batteryCurrent = -121, .batteryCycleCount = 1, .batteryFullCharge = 3862000, .batteryChargeCounter = 3838800, .batteryTechnology = Li-ion}, mBatteryLevelCritical=false, mPlugType=2
I: shutdownIfLowCurrentLocked batteryLevel = 100 , hasChargingCurrent = true(isPowered=true,batteryCurrent=-121,hardware=qcom) , hitShutdownVoltage = true(batteryVoltage=4396,mBatteryMinVoltage=-1) , isSystemReady = true
D: resetWhenChargingLongTime resetTime=25200000 ,mchargingUPTime=5928338 , (resetTime-(uptime-mchargingUPTime))=23558754 ,onBattery=false
I: [186] nlu.run(16): Wrote row to frosting DB: 1769
I: [186] nlu.run(16): Wrote row to frosting DB: 1770
I: Usage reports ok 3, Failed Usage reports 0, indexed 0, rejected 0
I: Usage reports ok 0, Failed Usage reports 0, indexed 0, rejected 0
I: IndexChimeraService.getServiceInterface callingPackage=com.google.android.gms componentName=AppsCorpus serviceId=SEARCH_CORPORA
I: IndexChimeraService.getServiceInterface callingPackage=com.google.android.gms componentName=AppsCorpus serviceId=SEARCH_QUERIES
W: [{0}] Failed to resolve name. status={1}
I: Usage reports ok 0, Failed Usage reports 0, indexed 0, rejected 0
I: Force stopping at.mts.arnatomy appid=10253 user=-1: set debug app
I: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10000000 cmp=at.mts.arnatomy/.activity.Main} from uid 2000
W: getTransport: Cannot find entry [email protected]::IIop/default in either framework or device manifest.
E: Iop tryGetService failed
I: Usage reports ok 0, Failed Usage reports 0, indexed 0, rejected 0
D: activityStartTrigger: Activity is Triggerred in full screen ApplicationInfo{bebcb77 at.mts.arnatomy}
E: activityStartTrigger: not whiteListedat.mts.arnatomy/at.mts.arnatomy.activity.Main/1
D: activityResumeTrigger: The activity in ApplicationInfo{bebcb77 at.mts.arnatomy} is now in focus and seems to be in full-screen mode
E: activityResumeTrigger: not whiteListedat.mts.arnatomy/at.mts.arnatomy.activity.Main/1
D: Package [at.mts.arnatomy] have process
D: manageDisableList userId=0 what=0x0 pkg=Window{faf5da9 u0 StatusBar}
D: disableLocked net1 = 0; net2 = 0 pkg=Window{faf5da9 u0 StatusBar}
D: setSystemUiVisibility vis=a008 mask=ffffffff oldVal=a018 newVal=a008 diff=10
D: hiding the MENU button
D: Package [at.mts.arnatomy] have process
I: Start proc 18162:at.mts.arnatomy/u0a253 for activity at.mts.arnatomy/.activity.Main
D: handleProcessStartedLocked mDoneFinishBooting && app.pid != 0 ---> notifyProcessStart, app.processName = at.mts.arnatomy, app.info = ApplicationInfo{bebcb77 at.mts.arnatomy}, app.hostingType = activity, getHostingName() = ComponentInfo{at.mts.arnatomy/at.mts.arnatomy.activity.Main}, getIntentFlag() = 0, getIsPackageRunning() = true, app = ProcessRecord{6e13e4 18162:at.mts.arnatomy/u0a253}, getExtraData() = Bundle[{ACTIVITY_TASK_AFFINITY=at.mts.arnatomy, ACTIVITY_INTENT=Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10000000 cmp=at.mts.arnatomy/.activity.Main }, CALLER_PACKAGE=null, ACTIVITY_INFO=ActivityInfo{f46204d at.mts.arnatomy.activity.Main}}]
I: Late-enabling -Xcheck:jni
D: manageDisableList userId=0 what=0x0 pkg=Window{faf5da9 u0 StatusBar}
D: disableLocked net1 = 0; net2 = 0 pkg=Window{faf5da9 u0 StatusBar}
D: hiding the MENU button
D: com.android.settings -> resizable apps -> USAGE 304925
W: not interested in atom 130605
D: log source 1000 is allowed for fih atoms
D: log source 1000 is allowed for fih atoms
D: manageDisableList userId=0 what=0x0 pkg=Window{faf5da9 u0 StatusBar}
D: disableLocked net1 = 0; net2 = 0 pkg=Window{faf5da9 u0 StatusBar}
D: hiding the MENU button
D: manageDisableList userId=0 what=0x0 pkg=Window{faf5da9 u0 StatusBar}
D: disableLocked net1 = 0; net2 = 0 pkg=Window{faf5da9 u0 StatusBar}
D: manageDisableList userId=0 what=0x0 pkg=Window{faf5da9 u0 StatusBar}
D: disableLocked net1 = 0; net2 = 0 pkg=Window{faf5da9 u0 StatusBar}
I: Reconfiguring input devices.  changes=0x00000004
W: not interested in atom 130601
D: log source 1000 is allowed for fih atoms
D: log source 1000 is allowed for fih atoms
D: ActivityTrigger activityPauseTrigger 
W: not interested in atom 130601
D: log source 1000 is allowed for fih atoms
D: log source 1000 is allowed for fih atoms
D: hiding the MENU button
W: ColorManagerService is not Existed
D: manageDisableList userId=0 what=0x0 pkg=Window{faf5da9 u0 StatusBar}
D: disableLocked net1 = 0; net2 = 0 pkg=Window{faf5da9 u0 StatusBar}
D: manageDisableList userId=0 what=0x0 pkg=Window{faf5da9 u0 StatusBar}
D: disableLocked net1 = 0; net2 = 0 pkg=Window{faf5da9 u0 StatusBar}
D: manageDisableList userId=0 what=0x0 pkg=Window{faf5da9 u0 StatusBar}
D: disableLocked net1 = 0; net2 = 0 pkg=Window{faf5da9 u0 StatusBar}
D: manageDisableList userId=0 what=0x0 pkg=Window{faf5da9 u0 StatusBar}
D: disableLocked net1 = 0; net2 = 0 pkg=Window{faf5da9 u0 StatusBar}
D: manageDisableList userId=0 what=0x0 pkg=Window{faf5da9 u0 StatusBar}
D: disableLocked net1 = 0; net2 = 0 pkg=Window{faf5da9 u0 StatusBar}
D: hiding the MENU button
W: Application at.mts.arnatomy is waiting for the debugger on port 8100...
I: Sending WAIT chunk
I: It non-support bigbang
I: isNeedChangeNaviBarColor taskInfo: [android.app.ActivityManager$RunningTaskInfo@8ea8a50] size: 1
I: isAPPNeedChange pkgName: at.mts.arnatomy needKeep: false
I: isNeedChangeNaviBarColor false
I: generateLayout mNavigationBarColor: ff000000
I: generateLayout isLightNavi false, Visibility: 0
D: manageDisableList userId=0 what=0x0 pkg=Window{faf5da9 u0 StatusBar}
D: disableLocked net1 = 0; net2 = 0 pkg=Window{faf5da9 u0 StatusBar}
D: hiding the MENU button
D: manageDisableList userId=0 what=0x0 pkg=Window{faf5da9 u0 StatusBar}
D: disableLocked net1 = 0; net2 = 0 pkg=Window{faf5da9 u0 StatusBar}
D: hiding the MENU button
D: manageDisableList userId=0 what=0x0 pkg=Window{faf5da9 u0 StatusBar}
D: disableLocked net1 = 0; net2 = 0 pkg=Window{faf5da9 u0 StatusBar}
D: hiding the MENU button
D: manageDisableList userId=0 what=0x0 pkg=Window{faf5da9 u0 StatusBar}
D: disableLocked net1 = 0; net2 = 0 pkg=Window{faf5da9 u0 StatusBar}
D: hiding the MENU button
D: manageDisableList userId=0 what=0x0 pkg=Window{faf5da9 u0 StatusBar}
D: disableLocked net1 = 0; net2 = 0 pkg=Window{faf5da9 u0 StatusBar}
D: hiding the MENU button
W: Activity pause timeout for ActivityRecord{ee26c38 u0 at.mts.arnatomy/.activity.Main t538}
D: manageDisableList userId=0 what=0x0 pkg=Window{faf5da9 u0 StatusBar}
D: disableLocked net1 = 0; net2 = 0 pkg=Window{faf5da9 u0 StatusBar}
D: hiding the MENU button
D: ActivityTrigger activityStopTrigger 
I: Indexing com.google.android.gms-apps from com.google.android.gms
I: Indexing com.google.android.gms-internal.3p:MobileApplication from com.google.android.gms
I: Indexing com.google.android.gms-internal.3p:DigitalDocument from com.google.android.gms
I: Indexing done com.google.android.gms-apps
I: Indexing com.google.android.gms-internal.3p:Message from com.google.android.gms
I: Indexing com.google.android.gms-internal.3p:Event from com.google.android.gms
I: Indexing done com.google.android.gms-internal.3p:MobileApplication
I: Indexing done com.google.android.gms-internal.3p:DigitalDocument
I: Indexing done com.google.android.gms-internal.3p:Message
I: Indexing done com.google.android.gms-internal.3p:Event
I: Indexing com.google.android.gms-apps from com.google.android.gms
I: Indexing done com.google.android.gms-apps
W: [{0}] Failed to resolve name. status={1}
V: getFullBackupRequiredNetworkType(...) returns 2
V: getFullBackupRequireCharging(...) returns true
W: App freeze timeout expired.
I: Debugger has connected
I: waiting for debugger to settle...
W: Error performing check: 
I: waiting for debugger to settle...
I: uid=10253(at.mts.arnatomy) identical 4 lines
I: waiting for debugger to settle...
W: [{0}] Failed to resolve name. status={1}
I: waiting for debugger to settle...
I: debugger has settled (1424)
D: manageDisableList userId=0 what=0x0 pkg=Window{faf5da9 u0 StatusBar}
D: disableLocked net1 = 0; net2 = 0 pkg=Window{faf5da9 u0 StatusBar}
D: hiding the MENU button
I: The ClassLoaderContext is a special shared library.
E: getDiskStats failed with result NOT_SUPPORTED and size 0
D: Mode change to WRITE_MODE!
W: JIT profile information will not be recorded: profile file does not exits.
I: uid=10253(at.mts.arnatomy) identical 10 lines
W: JIT profile information will not be recorded: profile file does not exits.
I: Connecting to perf service.
I: starting instant run server: is main process
I: Added user client for pid:18162 and userId:0
I: It non-support bigbang
I: isNeedChangeNaviBarColor taskInfo: [android.app.ActivityManager$RunningTaskInfo@d6f043d] size: 1
I: isAPPNeedChange pkgName: at.mts.arnatomy needKeep: false
I: isNeedChangeNaviBarColor false
I: generateLayout mNavigationBarColor: ff000000
I: generateLayout isLightNavi false, Visibility: 0
W: Accessing hidden method Landroid/view/View;->computeFitSystemWindows(Landroid/graphics/Rect;Landroid/graphics/Rect;)Z (light greylist, reflection)
W: Accessing hidden method Landroid/view/ViewGroup;->makeOptionalFitsSystemWindows()V (light greylist, reflection)
D: Skia GL Pipeline
I: QUALCOMM build                   : a4d39a0, I6fd668c4d3
    Build Date                       : 10/05/18
    OpenGL ES Shader Compiler Version: EV031.25.03.01
    Local Branch                     : 
    Remote Branch                    : refs/tags/AU_LINUX_ANDROID_LA.UM.7.2.R1.09.00.00.442.049
    Remote Branch                    : NONE
    Reconstruct Branch               : NOTHING
I: Build Config                     : S L 6.0.7 AArch64
I: PFP: 0x005ff112, ME: 0x005ff066
I: android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasWideColorDisplay retrieved: 0
I: android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasHDRDisplay retrieved: 0
I: FEngine (64 bits) created at 0x7edda00000 (threading is enabled)
D: Using ASurfaceTexture
D: FEngine resolved backend: OpenGL
I: Optional library com.google.ar.sceneform.animation not present. Sceneform animation disabled
W: Error performing check: 
W: Out of retries on: b <
      a: "at.mts.arnatomy"
      b: # bptg@eb35ea8a
      w: -1
    >
    w: -1
I: Verification 9 complete. Success:false. Failed hosts:mts.at.
I: Entering ArSession_createWithFeatures
I: ARCore Version: APK version code: 190603066
I: ARCore Version: SDK build name: 1.10
I: version_check.cc:23 ARCore Version: APK version:1.10.190603066
I: version_check.cc:24 ARCore Version: emulated SDK version:1.10.190519000
I: Dynamite load ok.
I: Attempting to load native library arcore_c from package com.google.ar.core
I: Dynamite::LoadNativeRemoteLibrary handle=8630142703875706433
I: session_create_implementation.cc:66 Entering createImplementationWithFeaturesAndSettings. ARCore SDK version: [1.10.190519000].
V: JniHelper: attached thread (Called from line 264).
I: device_profile_database_helpers.cc:433 Found nothing for jFkjgw
I: device_profile_database_helpers.cc:433 Found nothing for Onyx_00WW/B2N_sprout
I: device_profile_database_helpers.cc:418 Considering ZQZPO_:8
I: device_profile_database_helpers.cc:429 Device profile for Nokia/Onyx_00WW/B2N_sprout:9/PPR1.180610.011/00WW_3_53B:user/release-keys: ZQZPO_:8
W: helpers.cc:1988 Defaulting to persistent calibration file.
W: helpers.cc:1965 Property calibration_cad is not defined.
I: session_create_implementation_shared.cc:936 Using noop feature extractor
I: device_profile_conversions.cc:143 used_active_calibration: 2
I: device_profile_conversions.cc:143 used_active_calibration: 2
I: android_sensors.cc:80 Using uncalibrated accelerometer.
I: android_sensors.cc:116 Using uncalibrated magnetometer.
I: android_platform_checks.cc:190 IsZeroRotationLandscape = false
I: device_profile_conversions.cc:143 used_active_calibration: 2
W: Accessing hidden field Ljava/nio/Buffer;->address:J (light greylist, reflection)
W: The API key for use with the Google AR service could not be obtained!
D: No Network Security Config specified, using platform default
W: [{0}] Failed to resolve name. status={1}
I: android_camera.cc:1123 Initializing camera manager.
I: android_camera.cc:1147 Camera manager initialized successfully with 2 cameras.
I: Initialized TensorFlow Lite runtime.
I: session_create_implementation_shared.cc:1121 CPU Image enable frame delay to compensate delay: false
I: create_pursuit_tracker.cc:23 AugmentedRegion downsample mode from Phenotype: true
I: planar_target_tracking_manager.h:110 Config of PlanarTargetTrackingManager:
    -pose_refinement_with_detection_interval_ns: 0
    -min_interval_between_detections_ns: 500000000
    -filter_parallax: false
    -filter_result: true
    -multiple_targets: true
    -mini_detection: true
    -tracking_mode: 1
I: session_create_implementation.cc:241 createImplementationWithFeaturesAndSettings returning OK.
W: Accessing hidden method Landroid/media/Image;-><init>()V (light greylist, linking)
I: Loading AImage symbols
I: Loading ACameraMetadata symbols
W: Log Source: PJgQUl1CRhj8-rGlwtloKA==
I: session.cc:656 Entering Session::Resume.
I: android_camera.cc:540 Reset cleanly got to CLOSED state for camera 1
I: Connecting to camera service
W: [soar.cts] ignore the status update of camera: 2
W: [soar.cts] ignore the status update of camera: 3
W: ignore the torch status update of camera: 2
I: session.cc:1884 Update Frame Delay to 8 frames.
I: android_sensors.cc:139 Starting thread.
I: cameras.cc:599 Selected camera 1 stream 0 as feature extraction stream.
W: ignore the torch status update of camera: 3
I: android_sensors.cc:28 Gyro min delay 2.5ms requesting 5ms
D: Calling package is  :
I: CamSemaphore =1 PreCamAPPName=
I: ClientName :  count =(0)
D: WaitCloseDone::sem_init 
I: CameraService::connect call (PID -1 "", camera ID 1) for HAL version default and Camera API version 2
I: android_sensors.cc:28 Accel min delay 2.5ms requesting 5ms
W: Processing 1 accounts
E: Access Denial: can't use the camera from an idle UID pid=18162, uid=10253
E: openCamera: connect camera device failed: Status(-8): '6: validateClientPermissionsLocked:976: Caller "" (PID 10253, UID 18162) cannot open camera "1" from background'
E: android_camera.cc:545 Reset: Resetting camera 1 from an ERROR state, best effort clean-up commencing
W: session.cc:735 Session::Resume returning generic::unavailable: ACameraManager_openCamera.
E: status.cc:153 generic::unavailable: ACameraManager_openCamera
D: Shutting down VM


    --------- beginning of crash
E: FATAL EXCEPTION: main
    Process: at.mts.arnatomy, PID: 18162
    java.lang.RuntimeException: Unable to resume activity {at.mts.arnatomy/at.mts.arnatomy.activity.Main}: com.google.ar.core.exceptions.FatalException
        at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3811)
        at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3843)
        at android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:51)
        at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:145)
        at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:70)
        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1823)
        at android.os.Handler.dispatchMessage(Handler.java:107)
        at android.os.Looper.loop(Looper.java:198)
        at android.app.ActivityThread.main(ActivityThread.java:6729)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
     Caused by: com.google.ar.core.exceptions.FatalException
        at java.lang.reflect.Constructor.newInstance0(Native Method)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:343)
        at com.google.ar.core.Session.throwExceptionFromArStatus(Session.java:134)
        at com.google.ar.core.Session.nativeResume(Native Method)
        at com.google.ar.core.Session.resume(Session.java:70)
        at com.google.ar.sceneform.ArSceneView.resumeSession(SourceFile:48)
        at com.google.ar.sceneform.ArSceneView.resume(SourceFile:37)
        at com.google.ar.sceneform.ux.BaseArFragment.start(BaseArFragment.java:507)
        at com.google.ar.sceneform.ux.BaseArFragment.onResume(BaseArFragment.java:315)
        at android.support.v4.app.Fragment.performResume(Fragment.java:2390)
        at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1474)
        at android.support.v4.app.FragmentManagerImpl.moveFragmentToExpectedState(FragmentManager.java:1759)
        at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1827)
        at android.support.v4.app.FragmentManagerImpl.dispatchStateChange(FragmentManager.java:3244)
        at android.support.v4.app.FragmentManagerImpl.dispatchResume(FragmentManager.java:3212)
        at android.support.v4.app.FragmentController.dispatchResume(FragmentController.java:217)
        at android.support.v4.app.FragmentActivity.onResumeFragments(FragmentActivity.java:509)
        at android.support.v4.app.FragmentActivity.onPostResume(FragmentActivity.java:498)
        at android.support.v7.app.AppCompatActivity.onPostResume(AppCompatActivity.java:171)
        at android.app.Activity.performResume(Activity.java:7317)
        at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3803)
        at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3843) 
        at android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:51) 
        at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:145) 
        at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:70) 
        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1823) 
        at android.os.Handler.dispatchMessage(Handler.java:107) 
        at android.os.Looper.loop(Looper.java:198) 
        at android.app.ActivityThread.main(ActivityThread.java:6729) 
        at java.lang.reflect.Method.invoke(Native Method) 
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493) 
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858) 
W:   Force finishing activity at.mts.arnatomy/.activity.Main
D: manageDisableList userId=0 what=0x0 pkg=Window{faf5da9 u0 StatusBar}
D: disableLocked net1 = 0; net2 = 0 pkg=Window{faf5da9 u0 StatusBar}
D: hiding the MENU button
D: manageDisableList userId=0 what=0x0 pkg=Window{faf5da9 u0 StatusBar}
D: disableLocked net1 = 0; net2 = 0 pkg=Window{faf5da9 u0 StatusBar}
D: hiding the MENU button
I: Sending signal. PID: 18162 SIG: 9
I: Received action(android.intent.action.DROPBOX_ENTRY_ADDED)
I: Start BBoxsBoxService
E: dropboxTag:data_app_crash;dropboxTime:1561105660683
E: Service Started.. 
I: HwBinder: Starting thread pool for default::[email protected]::IBox
E: Box::BoxCMD sbuf_len=74
E: [APRReport] get APRReport from memory
I: [APRReport] addDropboxEntry() data_app_crash
I: [ParserUtility] /data/system/dropbox/[email protected]
I: [ParserUtility] key word : at.mts.arnatomy
I: [ParserUtility] VERSIONCODE : 1
I: [ParserUtility] VERSIONNAME : 1.0
I: [APRReport] exceptionItem  tag:data_app_crash packageName:at.mts.arnatomy versionCode:1 versionName:1.0
I: HwBinder: Starting thread pool for default::[email protected]::IBox
E: Box::BoxCMD sbuf_len=151
I: HwBinder: Starting thread pool for default::[email protected]::IBox
E: Box::BoxCMD sbuf_len=82
I: HwBinder: Starting thread pool for default::[email protected]::IBox
E: Box::BoxCMD sbuf_len=81
I: HwBinder: Starting thread pool for default::[email protected]::IBox
E: Box::BoxCMD sbuf_len=92
I: HwBinder: Starting thread pool for default::[email protected]::IBox
E: Box::BoxCMD sbuf_len=109
I: HwBinder: Starting thread pool for default::[email protected]::IBox
E: Box::BoxCMD sbuf_len=94
I: HwBinder: Starting thread pool for default::[email protected]::IBox
E: Box::BoxCMD sbuf_len=76
I: HwBinder: Starting thread pool for default::[email protected]::IBox
E: Box::BoxCMD sbuf_len=60
I: HwBinder: Starting thread pool for default::[email protected]::IBox
E: Box::BoxCMD sbuf_len=47
I: HwBinder: Starting thread pool for default::[email protected]::IBox
E: Box::BoxCMD sbuf_len=65
I: HwBinder: Starting thread pool for default::[email protected]::IBox
E: Box::BoxCMD sbuf_len=54
I: HwBinder: Starting thread pool for default::[email protected]::IBox
E: Box::BoxCMD sbuf_len=89
I: HwBinder: Starting thread pool for default::[email protected]::IBox
E: Box::BoxCMD sbuf_len=68
I: HwBinder: Starting thread pool for default::[email protected]::IBox
E: Box::BoxCMD sbuf_len=59
I: HwBinder: Starting thread pool for default::[email protected]::IBox
E: Box::BoxCMD sbuf_len=65
I: HwBinder: Starting thread pool for default::[email protected]::IBox
E: Box::BoxCMD sbuf_len=71
I: HwBinder: Starting thread pool for default::[email protected]::IBox
E: Box::BoxCMD sbuf_len=79
I: HwBinder: Starting thread pool for default::[email protected]::IBox
E: Box::BoxCMD sbuf_len=62
I: HwBinder: Starting thread pool for default::[email protected]::IBox
E: Box::BoxCMD sbuf_len=58
I: Process at.mts.arnatomy (pid 18162) has died: cch  CRE 
I: HwBinder: Starting thread pool for default::[email protected]::IBox
E: Box::BoxCMD sbuf_len=72
W: kill(-18162, 9) failed: No such process
I: HwBinder: Starting thread pool for default::[email protected]::IBox
I: Process 18162 exited due to signal (9)
E: Box::BoxCMD sbuf_len=65
I: HwBinder: Starting thread pool for default::[email protected]::IBox
E: Box::BoxCMD sbuf_len=80
W: Attempting to destroy on removed layer: AppWindowToken{f442976 token=Token{eb15411 ActivityRecord{ee26c38 u0 at.mts.arnatomy/.activity.Main t538}}}#0
I: HwBinder: Starting thread pool for default::[email protected]::IBox
E: Box::BoxCMD sbuf_len=83
I: HwBinder: Starting thread pool for default::[email protected]::IBox
E: Box::BoxCMD sbuf_len=73
I: HwBinder: Starting thread pool for default::[email protected]::IBox
E: Box::BoxCMD sbuf_len=89
I: HwBinder: Starting thread pool for default::[email protected]::IBox
E: Box::BoxCMD sbuf_len=105
I: HwBinder: Starting thread pool for default::[email protected]::IBox
E: Box::BoxCMD sbuf_len=89
D: manageDisableList userId=0 what=0x0 pkg=Window{faf5da9 u0 StatusBar}
D: disableLocked net1 = 0; net2 = 0 pkg=Window{faf5da9 u0 StatusBar}
D: manageDisableList userId=0 what=0x0 pkg=Window{faf5da9 u0 StatusBar}
D: disableLocked net1 = 0; net2 = 0 pkg=Window{faf5da9 u0 StatusBar}
D: manageDisableList userId=0 what=0x0 pkg=Window{faf5da9 u0 StatusBar}
D: disableLocked net1 = 0; net2 = 0 pkg=Window{faf5da9 u0 StatusBar}
I: HwBinder: Starting thread pool for default::[email protected]::IBox
E: Box::BoxCMD sbuf_len=97
D: manageDisableList userId=0 what=0x0 pkg=Window{faf5da9 u0 StatusBar}
D: disableLocked net1 = 0; net2 = 0 pkg=Window{faf5da9 u0 StatusBar}
D: setSystemUiVisibility vis=a018 mask=ffffffff oldVal=a008 newVal=a018 diff=10
I: HwBinder: Starting thread pool for default::[email protected]::IBox
D: hiding the MENU button
E: Box::BoxCMD sbuf_len=92
I: HwBinder: Starting thread pool for default::[email protected]::IBox
E: Box::BoxCMD sbuf_len=93
I: HwBinder: Starting thread pool for default::[email protected]::IBox
E: Box::BoxCMD sbuf_len=92
I: HwBinder: Starting thread pool for default::[email protected]::IBox
E: Box::BoxCMD sbuf_len=87
W: kill(-18162, 9) failed: No such process
I: Successfully killed process cgroup uid 10253 pid 18162 in 46ms
I: HwBinder: Starting thread pool for default::[email protected]::IBox
E: Box::BoxCMD sbuf_len=89
I: HwBinder: Starting thread pool for default::[email protected]::IBox
E: Box::BoxCMD sbuf_len=62
I: HwBinder: Starting thread pool for default::[email protected]::IBox
D: manageDisableList userId=0 what=0x0 pkg=Window{faf5da9 u0 StatusBar}
D: disableLocked net1 = 0; net2 = 0 pkg=Window{faf5da9 u0 StatusBar}
D: hiding the MENU button
E: Box::BoxCMD sbuf_len=82
E: send error message:data_app_crash;1561105660683(pkgName:at.mts.arnatomy;version:1.0;versionCode:1) to BBS for ANR/FC/TOMB_STONE...
I: HwBinder: Starting thread pool for default::[email protected]::IBox
D: [WIFI_DBG]: onStart: mremoteLockFeatureOn = false ,mremoteLocked = false
E: Service Destroyed.. 
E: Box::BoxCMD sbuf_len=16
W: Permission Denial: broadcasting Intent { act=android.net.conn.CONNECTIVITY_CHANGE flg=0x4200010 (has extras) } from null (pid=-1, uid=-1) requires android.permission.CHANGE_NETWORK_STATE due to registered receiver BroadcastFilter{c691ee6 u0 ReceiverList{983f941 16485 com.android.settings/1000/u0 remote:150a828}}
W: Permission Denial: broadcasting Intent { act=android.net.wifi.STATE_CHANGE flg=0x4000010 (has extras) } from null (pid=-1, uid=-1) requires android.permission.CHANGE_NETWORK_STATE due to registered receiver BroadcastFilter{c691ee6 u0 ReceiverList{983f941 16485 com.android.settings/1000/u0 remote:150a828}}
I: HwBinder: Starting thread pool for default::[email protected]::IBox
E: Box::BoxCMD sbuf_len=179
W: Permission Denial: broadcasting Intent { act=android.net.conn.CONNECTIVITY_CHANGE flg=0x4200010 (has extras) } from null (pid=-1, uid=-1) requires android.permission.CHANGE_NETWORK_STATE due to registered receiver BroadcastFilter{655e87d u0 ReceiverList{11c1ed4 16485 com.android.settings/1000/u0 remote:c106c27}}
W: Permission Denial: broadcasting Intent { act=android.net.wifi.STATE_CHANGE flg=0x4000010 (has extras) } from null (pid=-1, uid=-1) requires android.permission.CHANGE_NETWORK_STATE due to registered receiver BroadcastFilter{655e87d u0 ReceiverList{11c1ed4 16485 com.android.settings/1000/u0 remote:c106c27}}
D: manageDisableList userId=0 what=0x0 pkg=Window{faf5da9 u0 StatusBar}
D: disableLocked net1 = 0; net2 = 0 pkg=Window{faf5da9 u0 StatusBar}
D: hiding the MENU button
D: manageDisableList userId=0 what=0x0 pkg=Window{faf5da9 u0 StatusBar}
D: disableLocked net1 = 0; net2 = 0 pkg=Window{faf5da9 u0 StatusBar}
D: hiding the MENU button
D: manageDisableList userId=0 what=0x0 pkg=Window{faf5da9 u0 StatusBar}
D: disableLocked net1 = 0; net2 = 0 pkg=Window{faf5da9 u0 StatusBar}
D: hiding the MENU button
D: manageDisableList userId=0 what=0x0 pkg=Window{faf5da9 u0 StatusBar}
D: disableLocked net1 = 0; net2 = 0 pkg=Window{faf5da9 u0 StatusBar}
D: hiding the MENU button
D: manageDisableList userId=0 what=0x0 pkg=Window{faf5da9 u0 StatusBar}
D: disableLocked net1 = 0; net2 = 0 pkg=Window{faf5da9 u0 StatusBar}
D: hiding the MENU button
D: Mode change to WRITE_MODE!
W: [{0}] Failed to resolve name. status={1}
W: [{0}] Failed to resolve name. status={1}
I: Aggregate from 1561103714611 (log), 1561103714611 (data)
I: Received action(android.intent.action.DROPBOX_ENTRY_ADDED)
I: Start BBoxsBoxService
E: dropboxTag:event_data;dropboxTime:1561105684345
I: HwBinder: Starting thread pool for default::[email protected]::IBox
E: Box::BoxCMD sbuf_len=74
I: dumping service [account]
I: Received action(android.intent.action.DROPBOX_ENTRY_ADDED)
I: Start BBoxsBoxService
E: dropboxTag:dumpsys:account;dropboxTime:1561105684482
I: HwBinder: Starting thread pool for default::[email protected]::IBox
E: Box::BoxCMD sbuf_len=74
I: Killing 15457:com.hmdglobal.support/u0a100 (adj 904): empty for 1800s
I: Killing 15560:com.google.android.webview:sandboxed_process0/u0a100i0 (adj 904): empty for 1800s
W: kill(-15457, 9) failed: No such process
I: onStartJob(): PeriodicContextualMetrics.
I: call()
I: call() : Finished in 1 ms
I: Task: PeriodicContextualMetrics successes.
W: kill(-15457, 9) failed: No such process
W: Scheduling restart of crashed service com.hmdglobal.support/org.chromium.content.app.SandboxedProcessService0 in 1000ms
I: Process 15560 exited due to signal (9)
D: ConnectivityService NetworkRequestInfo binderDied(NetworkRequest [ TRACK_DEFAULT id=55, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Unwanted:  Uid: 10100] ], android.os.BinderProxy@e305793)
D: ConnectivityService NetworkRequestInfo binderDied(NetworkRequest [ LISTEN id=56, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Unwanted:  Uid: 10100] ], android.os.BinderProxy@3f643d0)
D: releasing NetworkRequest [ TRACK_DEFAULT id=55, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Unwanted:  Uid: 10100] ] (release request)
D: handleMessage what = 1
I: Process 15457 exited due to signal (9)
I: [0]invokeOemRilRequestRaw: serial=1102 length=24
I: [0]1102 > OEM_HOOK_RAW[514f454d484f4f4b27000800080000000000000000000000]
I: [0]sendOemMonitorMessage: eventId = 1, serial = 1102
I: [0]processOemHookResponse serial no: 1102 error: 0length=0
I: [0]removeMonitorMessage: eventId = 1, serial = 1102
I: [0][1102] < OEM_HOOK_RAW [[B@5a3940]
D: handleMessage what = 2
D: handleMessage what = 1
D: manageDisableList userId=0 what=0x0 pkg=Window{faf5da9 u0 StatusBar}
D: disableLocked net1 = 0; net2 = 0 pkg=Window{faf5da9 u0 StatusBar}
D: hiding the MENU button
I: [1]invokeOemRilRequestRaw: serial=1103 length=24
I: [1]1103 > OEM_HOOK_RAW[514f454d484f4f4b27000800080000000000000000000000]
I: [1]sendOemMonitorMessage: eventId = 1, serial = 1103
I: [0]processOemHookIndication length=28
I: [0]processOemHookIndication unsolId=1028
I: [1]processOemHookResponse serial no: 1103 error: 0length=0
I: [1]removeMonitorMessage: eventId = 1, serial = 1103
I: [1][1103] < OEM_HOOK_RAW [[B@9ce11be]
D: handleMessage what = 0
D: manageDisableList userId=0 what=0x0 pkg=Window{faf5da9 u0 StatusBar}
D: disableLocked net1 = 0; net2 = 0 pkg=Window{faf5da9 u0 StatusBar}
D: hiding the MENU button
D: handleMessage what = 2
W: kill(-15457, 9) failed: No such process
I: [1]processOemHookIndication length=28
I: Successfully killed process cgroup uid 10100 pid 15457 in 87ms
I: [1]processOemHookIndication unsolId=1028
W: Failed to open process cgroup uid 99000 pid 15560: No such file or directory
E: Error encountered killing process cgroup uid 99000 pid 15560: No such file or directory
D: handleMessage what = 0
W: Shifting events by PT-41.358S now
D: checkPermissionAndAppOp, com.google.android.apps.wellbeing want to check com.google.android.providers.gsf.permission.READ_GSERVICES(-1) was skipped. -1/-1
I: Killing 12317:com.evenwell.custmanager/1000 (adj 906): empty for 1800s
W: kill(-12317, 9) failed: No such process
D: manageDisableList userId=0 what=0x0 pkg=Window{faf5da9 u0 StatusBar}
D: disableLocked net1 = 0; net2 = 0 pkg=Window{faf5da9 u0 StatusBar}
D: hiding the MENU button
D: checkPermissionAndAppOp, com.google.android.apps.wellbeing want to check com.google.android.providers.gsf.permission.READ_GSERVICES(-1) was skipped. -1/-1
I: Process 12317 exited due to signal (9)
W: kill(-12317, 9) failed: No such process
I: Successfully killed process cgroup uid 1000 pid 12317 in 48ms
W: Can't send stop request because service was unbound.
W: [{0}] Failed to resolve name. status={1}
D: Processing new values: info={.chargerAcOnline = false, .chargerUsbOnline = true, .chargerWirelessOnline = false, .maxChargingCurrent = 500000, .maxChargingVoltage = 5000000, .batteryStatus = CHARGING, .batteryHealth = GOOD, .batteryPresent = true, .batteryLevel = 100, .batteryVoltage = 4396, .batteryTemperature = 290, .batteryCurrent = -119, .batteryCycleCount = 1, .batteryFullCharge = 3862000, .batteryChargeCounter = 3840172, .batteryTechnology = Li-ion}, mBatteryLevelCritical=false, mPlugType=2
I: shutdownIfLowCurrentLocked batteryLevel = 100 , hasChargingCurrent = true(isPowered=true,batteryCurrent=-119,hardware=qcom) , hitShutdownVoltage = true(batteryVoltage=4396,mBatteryMinVoltage=-1) , isSystemReady = true
D: Sending ACTION_BATTERY_CHANGED. scale:100, info:{.chargerAcOnline = false, .chargerUsbOnline = true, .chargerWirelessOnline = false, .maxChargingCurrent = 500000, .maxChargingVoltage = 5000000, .batteryStatus = CHARGING, .batteryHealth = GOOD, .batteryPresent = true, .batteryLevel = 100, .batteryVoltage = 4396, .batteryTemperature = 290, .batteryCurrent = -119, .batteryCycleCount = 1, .batteryFullCharge = 3862000, .batteryChargeCounter = 3840172, .batteryTechnology = Li-ion}, EXTRA_WIRELESS_CHARGER_DISABLE = false
D: resetWhenChargingLongTime resetTime=25200000 ,mchargingUPTime=5928338 , (resetTime-(uptime-mchargingUPTime))=23520014 ,onBattery=false
D: received broadcast android.intent.action.BATTERY_CHANGED
D: ACTION_BATTERY_CHANGED...maxChargingMicroAmp: 500000 maxChargingMicroVolt: 5000000 current: -119000 isDisableWireless: false
D: mIsPowerLEDBehavior =false
D: mPluggedIn = true;mCharging =true; status=2; level=100
D: mAmbientMode=false
D: WARNING, no carrier configs on phone Id: 0
V: battery_level_update
I: updateShowPercent showPercent: 0 mUseSmallBatteryLevel: false mAllowShowPercentage: true
I: isHideWaring mHideWaring: false
I: ACTION_BATTERY_CHANGED -> Temprature : 29.0
I: DetectBatteryService: MaxTempShutDown : false
I: DetectBatteryService: LowTempShutDown : false
I: updateShowPercent showPercent: 0 mUseSmallBatteryLevel: false mAllowShowPercentage: true
I: isHideWaring mHideWaring: false
I: updateShowPercent showPercent: 0 mUseSmallBatteryLevel: false mAllowShowPercentage: true
I: isHideWaring mHideWaring: false
V: [battery_level_update][931] [HC] =>> [HS]
V: [batteryLevelUpdate][777] [HS] <<<<= [HC]
V: Exit Result 0
D: getConfig() : srsId = F_REMOVE_LOW_BATTERY_NOTIFY result = false type = bool pkg = com.android.systemui
D: handleBatteryUpdate
I: IS_SUPPORT_DECREASE_CHARGING : true
D: layoutOwnerInfo true..1.0
W: [{0}] Failed to resolve name. status={1}
I: Killing 12604:com.google.android.gms.unstable/u0a88 (adj 906): empty for 1807s
W: kill(-12604, 9) failed: No such process
I: Process 12604 exited due to signal (9)
D: manageDisableList userId=0 what=0x0 pkg=Window{faf5da9 u0 StatusBar}
D: disableLocked net1 = 0; net2 = 0 pkg=Window{faf5da9 u0 StatusBar}
D: hiding the MENU button
W: kill(-12604, 9) failed: No such process
I: Successfully killed process cgroup uid 10088 pid 12604 in 47ms
D: <sendMessageSynchronously> dstMessenger = android.os.Messenger@557d66f sent message = 131133
E: no controller energy info supplied for wifi
E: no controller energy info supplied for bluetooth
I: Uploading list of 19 apps for 1 account(s)
E: Privacy bit setting explicitly disabled
D: type: WIFI mIsCharging: true diffBytes: 0 lastBytes: 322456205 currentBytes: 322456205
D: type: MOBILE mIsCharging: true diffBytes: 0 lastBytes: 0 currentBytes: 0
I: getAlarmDumpInfo()
I: writeToTable: 20190621102831,180,0.0,31.6,(0.0,46:1:3,75:0:1,83:2:0),0,0,-6.2,100,129.0,P0Q0,0:0,,,,(),-1,0,0,0,B0,1586,(),0,0,0,0
D: Mode change to WRITE_MODE!
I: fusedValue = true
D: Mode change to WRITE_MODE!
D: updateBatteryUsageRecord!!
D: processAppDataUsage!!
D: Mode change to WRITE_MODE!
D: Mode change to WRITE_MODE!
I: fusedValue = true
D: getWakelockUsageNew()!!
D: saveUsageMapToFile 
D: Mode change to WRITE_MODE!
D: saveUsageMapToFile 
D: Mode change to WRITE_MODE!
I: fusedValue = true
D: Mode change to WRITE_MODE!
D: topApCounter at.mts.arnatomy
D: topApCounter com.android.settings
D: Processing new values: info={.chargerAcOnline = false, .chargerUsbOnline = true, .chargerWirelessOnline = false, .maxChargingCurrent = 500000, .maxChargingVoltage = 5000000, .batteryStatus = CHARGING, .batteryHealth = GOOD, .batteryPresent = true, .batteryLevel = 100, .batteryVoltage = 4396, .batteryTemperature = 290, .batteryCurrent = -119, .batteryCycleCount = 1, .batteryFullCharge = 3862000, .batteryChargeCounter = 3840979, .batteryTechnology = Li-ion}, mBatteryLevelCritical=false, mPlugType=2
I: shutdownIfLowCurrentLocked batteryLevel = 100 , hasChargingCurrent = true(isPowered=true,batteryCurrent=-119,hardware=qcom) , hitShutdownVoltage = true(batteryVoltage=4396,mBatteryMinVoltage=-1) , isSystemReady = true
D: Sending ACTION_BATTERY_CHANGED. scale:100, info:{.chargerAcOnline = false, .chargerUsbOnline = true, .chargerWirelessOnline = false, .maxChargingCurrent = 500000, .maxChargingVoltage = 5000000, .batteryStatus = CHARGING, .batteryHealth = GOOD, .batteryPresent = true, .batteryLevel = 100, .batteryVoltage = 4396, .batteryTemperature = 290, .batteryCurrent = -119, .batteryCycleCount = 1, .batteryFullCharge = 3862000, .batteryChargeCounter = 3840979, .batteryTechnology = Li-ion}, EXTRA_WIRELESS_CHARGER_DISABLE = false
D: mIsPowerLEDBehavior =false
D: resetWhenChargingLongTime resetTime=25200000 ,mchargingUPTime=5928338 , (resetTime-(uptime-mchargingUPTime))=23495511 ,onBattery=false
D: mAmbientMode=false
V: battery_level_update
I: ACTION_BATTERY_CHANGED -> Temprature : 29.0
I: DetectBatteryService: MaxTempShutDown : false
I: DetectBatteryService: LowTempShutDown : false
D: received broadcast android.intent.action.BATTERY_CHANGED
D: ACTION_BATTERY_CHANGED...maxChargingMicroAmp: 500000 maxChargingMicroVolt: 5000000 current: -119000 isDisableWireless: false
D: mPluggedIn = true;mCharging =true; status=2; level=100
V: [battery_level_update][931] [HC] =>> [HS]
I: IS_SUPPORT_DECREASE_CHARGING : true
V: [batteryLevelUpdate][777] [HS] <<<<= [HC]
V: Exit Result 0
I: updateShowPercent showPercent: 0 mUseSmallBatteryLevel: false mAllowShowPercentage: true
I: isHideWaring mHideWaring: false
D: WARNING, no carrier configs on phone Id: 0
I: updateShowPercent showPercent: 0 mUseSmallBatteryLevel: false mAllowShowPercentage: true
I: isHideWaring mHideWaring: false
I: updateShowPercent showPercent: 0 mUseSmallBatteryLevel: false mAllowShowPercentage: true
I: isHideWaring mHideWaring: false
D: getConfig() : srsId = F_REMOVE_LOW_BATTERY_NOTIFY result = false type = bool pkg = com.android.systemui
D: handleBatteryUpdate
D: layoutOwnerInfo true..1.0
E: getDiskStats failed with result NOT_SUPPORTED and size 0
W: [{0}] Failed to resolve name. status={1}
I: Killing 15928:com.google.android.apps.messaging:rcs/u0a144 (adj 906): empty for 1805s
W: [{0}] Failed to resolve name. status={1}
W: kill(-15928, 9) failed: No such process
W: kill(-15928, 9) failed: No such process
I: Process 15928 exited due to signal (9)
D: manageDisableList userId=0 what=0x0 pkg=Window{faf5da9 u0 StatusBar}
D: disableLocked net1 = 0; net2 = 0 pkg=Window{faf5da9 u0 StatusBar}
D: hiding the MENU button
W: kill(-15928, 9) failed: No such process
I: Successfully killed process cgroup uid 10144 pid 15928 in 59ms

Does somebody know a workaground by any chance?

[shenlong]

Is Razer Phone 2 support coming up?
Developing apps for AR!!!

[Borneck81]

Moto G6 play (Android 9) is not supported for ARCore

[ghost]

Is Xiaomi Mi 8 Pro going to get support? It's almost the same device with Mi 8 but it doesn't have ArCore support.

[Tegzek]

Please add HTC devices, U11, U11+ and U12+

[bfjeje]

I would like you to add my Honor 8 Pro to the compatibility list please. It's a great phone, has Android Pie.... I don't see why it is not supported.

[kcomain]

Hello, i would like to see the device Samsung Galaxy A6+(SM-A6050) be added to the list. I have searched through the supported devices and can only see the model A6 on it. Thanks for reading and hope you have a nice day reviewing it :)

[rgembalik]

Would you, please, consider supporting HMDs Nokia 9 PureView? Any plans on this one?

[ryurinri]

Please support for samsung A9!!! I can't believe all other phones of the same line have it, but this doesn't!

[MizuyoruTW]

Please support ASUS ZenFone 5 and 5Z, thanks.

[Bereggood]

Hi.
Q. Can I count on support Moto G5S ?

[lvidal1]

Please, add support to HTC U11. This device completes the requirements for AR. It has been required on #820 #229 and this thread.

[NitroToxin2]

The latest version of ARCore works just fine with Xiaomi Mi 9T (Redmi K20), but the phone is not listed on the official Supported Devices page, and thus ARCore services and apps cannot be installed from Google Play. Can it be added to the official list?

[AlexInTheEcho]

Really Arcore works in the Mi 9T? You have to do anything special or it's just download the apk?

[NitroToxin2]

Really Arcore works in the Mi 9T? You have to do anything special or it's just download the apk?

Just download the apk (v1.11.0)

[jynn7]

Please support honor 8 pro for Ar Core

[dam7lc]

A6 has support already but why a6+ doesnt ?? it doesnt make any sense, please review the compatibility of the smartphone

[jynn7]

Honor8 pro pleaseee

[jynn7]

Please add support Honor 8 pro.

[kvxrun]

Please add support for Xiaomi Redmi Note 7 (lavender) and Xiaomi Redmi Note 7 Pro (violet) @inio

[AlexInTheEcho]

And support all the rest of Xiaomi's devices, Redmi Note 5/Pro, Mi 8 lite, Mi A family, etc

[SammCheese]

Please add support for Honor 9

[Raiigo]

Is it possible to add ARCore support for the Xiaomi MI A2 ?
And if no, why ?
I saw the specification of the MI A2 (SnapDragon 660) are ok for the support of this device.

[wesselbarten]

Please add support for EVERY device. I don't understand why we have this issue where everybody can request specific devices. I think that is it time for ARCore to keep up the pace. ARKit is already way ahead of ARCore and works 10 times better. Also Unity works even better than ARCore on my Samsung Galaxy S8, and Unity is supported on almost every device. When will ARCore be actually production ready??

[OldShaterhan]

I'm asking for introduce ARCore support for Xiaomi Mi 8 Lite and Mi 8 Pro, as Mi 8 SE and Mi 8 are supported.

Xiaomi Mi 8 and Mi 8 Pro shares much of their configuration, there are nearly no changes between them:
https://www.mgsm.pl/pl/porownanie/xiaomi-mi8pro-vs-xiaomi-mi8/

and Mi 8 Lite has a bit more differences to 8 SE, but still is a high-end model:
https://www.mgsm.pl/pl/porownanie/xiaomi-mi8se-vs-xiaomi-mi8lite/ (#903)

[chnouman]

ARCore is working for us good in Pixel 2 but when we test it with Samsung A series it gives us flying models and poor performance.

[tves4405]

Please, add support to HTC U12+

[chrystian-farias]

Are they still adding support for new devices? It looks like they are no longer looking at this forum.

I wonder if there are any document with minimum hardware and software requirements for a device to be certified.

[KL0nLutiy]

Please add support for ZTE Axon 10

[MarcProe]

Please add support for Xiaomi Redmi Note _8_ Pro.
(...as the Note _7_ Pro ist already supported...)

[sionide0278]

Please add support for mid 2018 flagship device Oppo Find X

[MadKingEzekeil]

Please add support for Razer Phone 2
Not having it really, really sucks :(

[mcfizzlestag]

Please add support for Razer Phone 2. Its pretty ridiculous that one of the top android gaming phones is not supported.

[jadapa]

Hello,
I would like to request support for XIAOMI MI A2 Lite. It is a 2018 phone with a great CPU. Why is the phone not supported yet?

[davidvilanova007]

This issue is to track/dedup requests for device support.

See the official Supported Devices page for the complete list of currently supported devices.

Device-specific details/issues:

• #183 Asus' ZenFone AR never starts tracking
• Samsung S8(+) and S9(+) devices with model numbers ending and 0 sold outside of China may be used for development by side-loading the ARCore APK.

Besides these devices, we cannot comment on supporting any specific devices in this forum.
I'd like to request support the Huawei P Smart 2019 (POT-LX1)

[davidvilanova007]

This issue is to track/dedup requests for device support.
See the official Supported Devices page for the complete list of currently supported devices.
Device-specific details/issues:

• #183 Asus' ZenFone AR never starts tracking
• Samsung S8(+) and S9(+) devices with model numbers ending and 0 sold outside of China may be used for development by side-loading the ARCore APK.

Besides these devices, we cannot comment on supporting any specific devices in this forum.

I'd like to request support to the Huawei P Smart 2019 (POT-LX1)

[nikoskon2003]

Support for Samsung Galaxy A20 and A20e

[lboeckmann]

Please add Honor Play.
Is there a schedule on which mobile phone is currently working?

[RinMerin]

Please add support for RedmiNote 8 thanks

[rickyayri]

There is a possibility to add support to Samsung Galaxy A10?

[DavidBurela]

Nokia 9 support please.
It has 5 cameras, and a Time of Flight sensor. Surely there is more than enough hardware there to support this.

[Coopsolo]

Support for Samsung Galaxy A20 and A20e

Yes, please add support for a20. Few of my friends and I have this device and would love to tinker with it.

[Thaina]

Nokia 9 support please.
It has 5 cameras, and a Time of Flight sensor. Surely there is more than enough hardware there to support this.

If any device equipped with ToF camera then it don't need to ARCore anymore. You could just access depth map and construct every pixel location directly. The main parts of ARCore that waste most of their times is the project about guessing location of pixel from normal camera

I think if, in the next year, most of the device would contain ToF then the current ARCore will be stopped progressing. It might be new library that just use ToF. And this repo would be just dead

[rgembalik]

Nokia 9 support please.
It has 5 cameras, and a Time of Flight sensor. Surely there is more than enough hardware there to support this.

If any device equipped with ToF camera then it don't need to ARCore anymore. You could just access depth map and construct every pixel location directly. The main parts of ARCore that waste most of their times is the project about guessing location of pixel from normal camera

I think if, in the next year, most of the device would contain ToF then the current ARCore will be stopped progressing. It might be new library that just use ToF. And this repo would be just dead

An interesting point, but I think that's only partially true. To achieve fast and performing, dedicated AR application - yeah, you don't need ARCore in such case (although ARCore does a little bit more than just depth detection).

The main reason to have ARCore supported is that there is a ton of applications already supporting ARCore. Official support will allow Nokia 9 users to use all those apps. Because currently, they can't. It would be awesome to see some targetted optimizations alongside it, so there is actual support for ToF etc, but it's not a priority since most of the ARCore apps won't launch AR mode anyway, which is by far much bigger issue.

[Thaina]

@rgembalik I think so but, unfortunately, the ARCore developer just only care about working on their _precious scholar project_ and preaching the sermons about _consistency_ to all device

Admittedly half of my words here are sarcasm in the hope that the ARCore developer might come read and realize that what are they currently doing right now is totally impractical for developer in the whole world. I too actually hope that they will just stop and focused on ToF camera and release new ARCore based on ToF and dual camera depth map, instead of wasting their time on the guesser calibration for single camera for each device

But as you can see. There was more than 3 months of silence from the ARCore developer team in this thread. No one actively care about device capability at all. I really skeptic that the ARCore team might be dissolved from google anytimes

Seriously, currently now I think ARCore is hopeless. It just being another tango

[Hugobilou]

Please add Honor Play support.

[dangoso]

Another voice for the Razer phone 2. Near identical stats to the note 9 so should't be to hard. i hope.

[BeesQ]

And another voice for Razer Phone 2
One of the Best Gaming Phones... still not supported :|

Razer Phone 1 has ARCore Support (but only to v1.5)

Asus ROG Phone is also Gaming Phone (and has ARCore Support) ¯_(ツ)_/¯

[tel33]

Definitely there has to be Support for the ZTE Axon 10!! Hardware is more than capable.

[spectre2121]

Another voice here for the Razer phone 2. Please and thank you.

[gendgee]

Please add Google Play Services for AR for Mongolian Store on Google Play, we are team developed real estate marketplace and ready to launch , unfortunately Google Play Services for AR still not available in our Region, demo : https://www.youtube.com/watch?v=tw7Y1yzeyfM , Best Regards Denn

[popit42]

I know there's a bunch of other devices to work on, but is there any chance us Razer Phone people could get a word on if progress is being made? (Sorry, but I'm really feeling that AR itch)

[syltria]

Yet another person asking for Razer Phone 2 support. From a hardware standpoint I see no reason it shouldn't be supported and clearly there are enough users to warrant it.

[Roshibomb]

Created an account specifically to post this. Please, please add Samsung Galaxy A20 support. Thank you for your time.

[AstraeaZero]

...again everyone have Xperia XZ in the *. Whyyy? What's wrong with this phone? Why all ignoring non-premium XZ support? We get latest 8.0 Android and this is all. This is a still Flagship phone...

[Sliicy]

Please add the RAZER PHONE 2!!! Yet another voice.

[rjahgons]

Been waiting for a long time for Support to Galaxy A9 (2018), hope it's being developed..

[jd0yle]

Support or feedback for the Razer Phone 2 would be fantastic.

[OMechanicum]

Would love some Samsung A9 support

[brunacama]

Thank you for your hard work :) Huawei P30 and P30 Pro are already supported, any chance for P30 Lite?

[wisockijunior]

Do It support higher precision ToF sensors?

On Sat, Dec 21, 2019, 11:42 brunacama [e-mail] wrote:

Thank you for your hard work :) Huawei P30 and P30 Pro are already
supported, any chance for P30 Lite?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google-ar/arcore-android-sdk/issues/89?email_source=notifications&email_token=ABELDAT4MCV3J5ZAUHTZPJTQZYTPFA5CNFSM4EIQJVNKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHO5IUY#issuecomment-568185939,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABELDAQUJAEED63ENPSA3XLQZYTPFANCNFSM4EIQJVNA
.

[JameRetief2005]

Also requesting support for the Razer Phone 2.

[javipsicoloco]

Hello, I'd like to please request support for Xiaomi Mi 8 Pro
I noticed the supported devices include Mi8, Mi 8 SE, Mi 9, Mi 9 SE. So maybe the configuration is similar for Mi 8 Pro.
Thanks for reading :)

[Nine3hundred]

The 5g model of the xiaomi mi mix 3 needs support, especially because it mentions AR gaming in its listing on the xiaomi site

[PranavVyas]

Please add support for RedmiNote 8 thanks

I think that now Redmi note 7 supports ARCore! It will be great if redmi note 8 also supports it!

[ehong-tl]

Please add support for Xiaomi Mi Note 10 / Xiaomi Mi Note 10 Pro :-)

[PikabobAlex]

ARCore support for Vivo V17 Pro please?

[fartboygh]

Samsung Galaxy A20 please. It has all the specs needed.

[abkoradiya]

Add support for Redmi 8.

[Zi7ar21]

Essential Products said something about there being an OEM waitlist for Google to verify and add official support for the Essential Products PH-1, can someone please tell us if AR Core has the ability to be officially be supported after all this time? If not, what happened? Thank you so much.

[taiebbh]

Honor 20 PRO please , the phone is powerfull enough to run all the AR games/apps

[sandrobl]

Please add support for Nokia 7.2

[jynn7]

Please support Honor 8 pro

[pdecostervgls]

Please add Razer Phone 2 support

[PikabobAlex]

Please support Vivo 1910

[RVYA]

I was about to start developing an AR app using ARCore in Flutter and I noticed Galaxy A10 isn't supported! My phone is good, it doesn't need to be a flagship. Will Google reconsider adding this device in compatible devices list?

[mann1996]

Add Support for redmi note 8

[TNFB]

I have a Xiaomi Redmi Note 8 and It's a good phone. I don't understand why is not supported.
So add support for Redmi Note 8

[Allgon]

pls redmi note 8 and the pro version both of them are good and cost effective phones so more people buy them maybe not much as apple or samsung but still a lot people buy them so its should be high up in the list for the next supported devices

[BPMOmega]

I've noticed that @sandyfriend has marked a lot of open issues with the Device Support label, as well as closing several of them. Is this an indication that support is coming soon for these devices? If so, when can we expect an update? Any info would be appreciated!

[Allgon]

I've noticed that @sandyfriend has marked a lot of open issues with the Device Support label, as well as closing several of them. Is this an indication that support is coming soon for these devices? If so, when can we expect an update? Any info would be appreciated!

As far i know they stopped answering questions when they gotten under Google as for your questions idont think they are closing them beacuse they are making them no they are closind them so it would be more organized

[PikabobAlex]

Vodafone Smart V8 please

[GrayHat12]

Redmi Note 8 pro please

[0x00x0]

@inio any news about support of LG V20(H990DS)? How can I help dev team to support this device? Please, contact me, if you need some assistance from device holder.

[NouhaBsn]

Redmi Note 8 pro please

https://www.apkmirror.com/apk/google-inc/arcore/arcore-1-16-20030204-release/google-play-services-for-ar-1-16-200302046-android-apk-download/
this works for me.

[orifinkelman]

Readme 8 note support. Please.

[GrayHat12]

Redmi Note 8 pro please

https://www.apkmirror.com/apk/google-inc/arcore/arcore-1-16-20030204-release/google-play-services-for-ar-1-16-200302046-android-apk-download/
this works for me.

Actually what I need to use is Displayland (https://play.google.com/store/apps/details?id=com.ubiquity6.displayar)
I tried your suggestion but that still doesn't show me Displayland app compatible on playstore

[call0fcode]

Redmi Note 8 pro please

https://www.apkmirror.com/apk/google-inc/arcore/arcore-1-16-20030204-release/google-play-services-for-ar-1-16-200302046-android-apk-download/
this works for me.

Actually what I need to use is Displayland (https://play.google.com/store/apps/details?id=com.ubiquity6.displayar)
I tried your suggestion but that still doesn't show me Displayland app compatible on playstore

AR is working on Redmi Note 8 Pro using the following APK from APKMirror as already said:

Google Play Services for AR 1.16.200302046 (arm64-v8a + arm-v7a) (Android 7.0+)

You'll probably not be able to download the app you mentioned (Displayland) from Google Play because the device is still not really recognized by Google as supported (it probably will be soon..).
Try to find the Displayland's APK and install it externally ;)

[HasinduLanka]

Come on, we want this magic to work on Xiaomi Redmi note 8. It is already in the pro version, why not this?

[call0fcode]

Come on, we want this magic to work on Xiaomi Redmi note 8. It is already in the pro version, why not this?

The Redmi Note 8 Pro isn't officially supported as far as I know, but ARCore works on it with the mentioned APK anyway.

If you search for "ARCore" in the Play Store on a Redmi Note 8 Pro it literally doesn't appear. Using the link https://play.google.com/store/apps/details?id=com.google.ar.core opens the Play Store but still shows "Device not supported".

[sandyfriend]

@call0fcode @orifinkelman
Xiaomi Redmi Note8, Note8 Pro, Note 8 T are official support now.
Please check the update Support list:
https://developers.google.com/ar/discover/supported-devices

[orifinkelman]

@sandyfriend
Indeed, it was automatically installed and works.
Thanks.

[BPMOmega]

@sandyfriend Will the Razer Phones get added as officially supported devices?

[yenkij]

Can you please support Lenovo Z6 Pro?
Thanks :)

[BeesQ]

@sandyfriend Please Support Razer Phone 2 :(

[MihalyPapp]

Still waiting for HONOR 20 PRO! #974

[DKFactotum]

I have Xiaomi Mi Mix 3 5G - all the specs are practically identical to the Mi Mix 3 if not superior. Could you please add it.

I am developing a tool for designers and digital fabricators and it is extremely inconvenient to test with other's devices, especially now.

[orbites]

please support Xiaomi Redmi Note 9S

[MSRKTRNM]

Please, add support for HONOR 20 PRO.
I'm awaiting for this moment. 😊

[boboboboliu]

Can ARCore support AR/XR Headsets? We use Qualcomm Sc660 and Android 9.0。But can not run the ARCore.

[Amr512]

Nova 5T please :(

[ghost]

Please add the support of HONOR 20 PRO. 📱

This flagship has established itself as a productive and powerful phone.

The phone supports Huawei AR, but Google’s AR Services are better.

Please add. 🙏 Many people are interested and waiting.

[karizune]

Please add the support to ZENFONE 5 X00QD, i think this device can run with this especifications of hardware :)
pleeaseeee

[eidgrand]

Please add the support of HONOR 9 lite please

[MSRKTRNM]

Please, add support for HONOR 20 PRO.
I'm awaiting for this moment. 😊

Apparently, there will be no feedback. Disappointed in Google.

[sismoon2013]

Support request for Samsung Tab A series (SM-T510/T515)<

Please send us an update about this issue. I am able to install AR games but when I try to play the game I get a message "Installing Google Play Services for AR" . Then I get a message " Your device isn't Compatible with this version." Is my device the issue or Google Play Services for AR?

See this thread too> Samsung Tab A 10.1 (2019) Support #912

[kintovt]

+1 for Xiaomi Mi Note 10

[pyngit]

please support Xiaomi Mi Note 10 Lite.

[BillyB2933]

What about support for Samsung Galaxy S8 Active? The device that has the same hardware as other standard S8 which is supported, but is in a more rugged casing. Why doesn't this phone have support? It's more than capable speaking from a hardware spec perspective.

[PikabobAlex]

I love the fact that Vivo, Realme, OnePlus and Oppo are from the same parent company. All the brands got supported by ARCore but Vivo, only 3 devices are supported.

Yeah, thanks for the hard-working. guess I'll get another phone rather than keep requesting.

[MSRKTRNM]

I love the fact that Vivo, Realme, OnePlus and Oppo are from the same parent company. All the brands got supported by ARCore but Vivo, only 3 devices are supported.

Yeah, thanks for the hard-working. guess I'll get another phone rather than keep requesting.

Or it’s easier to switch from Android to iOS, where AR is already supported. Since Google does not support users, it will lose consumers.

[BPMOmega]

I'd like some transparency in the device support process, please. It's been more than a year since support was requested for the Razer Phone 2 (including myself, there's been 13 people asking for this). The first comment requesting for it was on Feb 18, 2019. I had posted a comment about it on May 31, 2019.

Since then, there's been complete radio silence. Newer phones released afterwards have been supported. Older phones released before it have gained support, as well. No rhyme or reason, especially when it comes to "small" brands. It's been frustrating, since I know this phone is more than capable of running ARCore. On a rooted device, you could run a modded version of the APK with the supported device list added... I just don't feel like rooting my phone for something that should be capable without doing so.

Honestly, it's really silly that there's a supported device list at all. It should just be allowed to install on every phone, and then it works or not depending on if your phone has the right OS version and required hardware.

[HuntStarJonny]

What about Xiaomi Mi Note 10?

[pavelk0508]

And what about Xiaomi Mi Note 10 Lite?

[mckaysalisbury]

RazerPhone (2) ++

[MSRKTRNM]

Still waiting for Honor 20 Pro.

[granitzheg]

Still waiting for XIAOMI MI9 LITE

[SValyok]

will be support for Xiaomi Mi Note 10 Lite ?

[donalhunt]

Per Issue #912...

Samsung Galaxy Tab A 10.1 (2019)

https://www.gsmarena.com/samsung_galaxy_tab_a_10_1_(2019)-9582.php

CPU: Octa-core (2x1.8 GHz Cortex-A73 & 6x1.6 GHz Cortex-A53)
RAM: 3GB
GPU: Mali-G71 MP2

[icorreacm]

It be great to certificate Samsung A20. It has great hardware and Android 10 but google forget to enable in google play. Please!!!

[MihalyPapp]

974

[thiagocgp]

Why Samsung Galaxy A9 (2018) SM-A920F don't have support for ARCore??
All other inferior and older devices are supported (Galaxy A3 / A5 / A6 / A7 / A8 / J5 / J7 ... etc).
I don't understand

[SpLinD]

I have a OnePlus 5T, which used to be supported by ARCore and is now not supported anymore. Possibly because of the Update to Android 10? Could you give any insights into why it's not supported anymore and if that will be fixed?

[MSRKTRNM]

There's no answers from devs. It's time to switch from Android and Google services completely. Very disappointed.

[PavelZurek]

Please add support for Asus ROG Phone 3 #1100

[CalmarEnrumey]

Please add the support for the Razer Phone 2. It's an amazing smartphone that as amazing spec that are plenty enough for arcore.
Just search internet and you will see that hundred of peaple want badly to use with ARCore and Minecraft Earth for exemple. Please, it's really sad that some people are paying a bit less than a 1k dollars for aphone and are nt even capable of playing lastest ar games. Why a ton of requests are getting close without any reason and why we cannot enev get an answer for google!
Please I would really appreciate to play minecraft earth on my RP2.

[AkshaySudheer]

Waiting for OnePlus Nord support.

[livedtrid]

Please add support for Xiaomi Redmi Note 9 Pro.

[rdcdt1]

please add the realme x2 pro
thanks for all

[NoelBulga]

Could you please add support for Xiaomi Mi Note 10 Lite?

[boehm-e]

Will the Poco X3 NFC support ARCore / depth api? (specs should be way enough & there is a lot of users)
Thank you

[y2kbadbug]

Per request in #1136 I was hoping support for the Galaxy A21 would be added. The A20 is supported and the A21 isn't much different. The A21 is actually more powerful: https://www.phonearena.com/phones/compare/Samsung-Galaxy-A20,Samsung-Galaxy-A21/phones/11159,11399

[Bumki-Kim]

Is there a plan for Google Pixel 5 or Galaxy Note 20?

I checked that Pixel 4a is included, even if it is released together, how about Pixel 5?

[PikabobAlex]

Hi developers, thanks for adding a few more Vivo devices to the list, but regarding to the model V17 I think you missed out the V17 Pro. Thanks

[Zi7ar21]

I am willing to help get the Samsung Galaxy A71 5G working with the new depth API, there is a camera it seems dedicated for depth support. They call it a depth camera, but it's not ToF but hopefully would certainly help estimate accurate depth data.

[GabNet1975]

Please, add support to Galaxy A9. All the older models have compatibily. Is the hardware so different?

[DrSensor]

Rather than hardcode it, I wonder why not support all devices since ARCore now supports a single camera 🤔
If the problem is in GPU, then it can be detected by its framerate to decide the tier (similar to detect-gpu)

[brainode]

Why Samsung Galaxy S20 FE doen't support Depth API? Will it release in future?

[Zi7ar21]

Today I noticed the Samsung Galaxy A71 5G now supports the Depth API! It runs OK, I am just curious if the depth camera on the phone is used because the depth map looks poor quality and covering the depth camera doesn't seem to affect anything. Is it possible to use it for a higher quality experience? I have had issues using the other cameras on the phone myself, I don't think Samsung implemed it very well. Can this be solved with the HAL?

[Zi7ar21]

Also I wanna thank whoever worked on enabling it

[catness]

I have a question. The list currently includes Samsung Galaxy S20+ 5G and Samsung Galaxy S20. So why Samsung Galaxy S20+ without 5G is missing? Isn't it supposed to be better than Samsung Galaxy S20, which is included without mentioning 5G, and better than Galaxy S7-S10 which are all included?

Any idea if S20+ works with ARCore unofficially? (The model I'm specifically interested in is SM-G985F, Exynos.)

[Alien-Tretech]

Xiaomi Black shark 3 would be great. has depth camera and AI

[jpizarrom]

Please add support for Xiaomi Redmi 9A/Xiaomi dandelion

[BeesQ]

Please, do something... :'c

[BPMOmega]

Still waiting on Razer Phone 2 to be officially supported...

[Thuaanf]

Hi, everyone. I'm getting start with AR.

I'm trying to run hello_ar_java and i got the message :"This device does not support AR" with black screen

• My editor: Android Studio 4.2 Canary 13
• My emulator:
  
  
  
  • Google Pixel 2 (This device is in the list of supported devices)
  
  
  • API 28
  
  
  • Android 9.0 Pie(Google Play)
  
  
  • CPU/ABI: x86
  
  
  • Camera (Back): VirtualScene
  
  
  • I have logged into Google Play and installed lasted version of 'Google play services for AR'
  
  

---

I used Debug feature and i got the following:
```
12/16 21:49:16: Launching 'app' on Pixel 2 API 28.
App restart successful without requiring a re-install.
$ adb shell am start -n "com.google.ar.core.examples.java.helloar/com.google.ar.core.examples.java.helloar.HelloArActivity" -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -D
Waiting for application to come online: com.google.ar.core.examples.java.helloar | com.google.ar.core.examples.java.helloar.test
Waiting for application to come online: com.google.ar.core.examples.java.helloar | com.google.ar.core.examples.java.helloar.test
Waiting for application to come online: com.google.ar.core.examples.java.helloar | com.google.ar.core.examples.java.helloar.test
Waiting for application to come online: com.google.ar.core.examples.java.helloar | com.google.ar.core.examples.java.helloar.test
Waiting for application to come online: com.google.ar.core.examples.java.helloar | com.google.ar.core.examples.java.helloar.test
Waiting for application to come online: com.google.ar.core.examples.java.helloar | com.google.ar.core.examples.java.helloar.test
Waiting for application to come online: com.google.ar.core.examples.java.helloar | com.google.ar.core.examples.java.helloar.test
Waiting for application to come online: com.google.ar.core.examples.java.helloar | com.google.ar.core.examples.java.helloar.test
Connecting to com.google.ar.core.examples.java.helloar
Capturing and displaying logcat messages from application. This behavior can be disabled in the "Logcat output" section of the "Debugger" settings page.
I/es.java.helloa: Background concurrent copying GC freed 16289(7MB) AllocSpace objects, 0(0B) LOS objects, 60% free, 992KB/2MB, paused 784us total 256.130ms
W/ActivityThread: Application com.google.ar.core.examples.java.helloar is waiting for the debugger on port 8100...
I/System.out: Sending WAIT chunk
I/System.out: Debugger has connected
waiting for debugger to settle...
I/System.out: waiting for debugger to settle...
I/System.out: waiting for debugger to settle...
I/chatty: uid=10087(com.google.ar.core.examples.java.helloar) identical 3 lines
I/System.out: waiting for debugger to settle...
I/System.out: debugger has settled (1362)
W/es.java.helloa: Accessing hidden method Landroid/graphics/drawable/Drawable;->getOpticalInsets()Landroid/graphics/Insets; (light greylist, linking)
Accessing hidden field Landroid/graphics/Insets;->left:I (light greylist, linking)
Accessing hidden field Landroid/graphics/Insets;->right:I (light greylist, linking)
W/es.java.helloa: Accessing hidden field Landroid/graphics/Insets;->top:I (light greylist, linking)
Accessing hidden field Landroid/graphics/Insets;->bottom:I (light greylist, linking)
W/es.java.helloa: Accessing hidden method Landroid/view/View;->computeFitSystemWindows(Landroid/graphics/Rect;Landroid/graphics/Rect;)Z (light greylist, reflection)
Accessing hidden method Landroid/view/ViewGroup;->makeOptionalFitsSystemWindows()V (light greylist, reflection)
D/OpenGLRenderer: Skia GL Pipeline
I/ARCore-ArCoreApk: Starting setup activity
D/HostConnection: HostConnection::get() New Host Connection established 0xe2a98460, tid 17843
D/HostConnection: HostComposition ext ANDROID_EMU_CHECKSUM_HELPER_v1 ANDROID_EMU_dma_v1 ANDROID_EMU_YUV420_888_to_NV21 ANDROID_EMU_YUV_Cache ANDROID_EMU_async_unmap_buffer GL_OES_EGL_image_external_essl3 GL_OES_vertex_array_object GL_KHR_texture_compression_astc_ldr ANDROID_EMU_host_side_tracing ANDROID_EMU_gles_max_version_3_0
I/ConfigStore: android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasWideColorDisplay retrieved: 0
android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasHDRDisplay retrieved: 0
I/OpenGLRenderer: Initialized EGL, version 1.4
D/OpenGLRenderer: Swap behavior 1
W/OpenGLRenderer: Failed to choose config with EGL_SWAP_BEHAVIOR_PRESERVED, retrying without...
D/OpenGLRenderer: Swap behavior 0
D/eglCodecCommon: setVertexArrayObject: set vao to 0 (0) 0 0
D/EGL_emulation: eglCreateContext: 0xe8dda1e0: maj 3 min 0 rcv 3
D/EGL_emulation: eglMakeCurrent: 0xe8dda1e0: ver 3 0 (tinfo 0xe2aa4230)
D/HostConnection: HostConnection::get() New Host Connection established 0xd0487ec0, tid 17840
D/HostConnection: HostComposition ext ANDROID_EMU_CHECKSUM_HELPER_v1 ANDROID_EMU_dma_v1 ANDROID_EMU_YUV420_888_to_NV21 ANDROID_EMU_YUV_Cache ANDROID_EMU_async_unmap_buffer GL_OES_EGL_image_external_essl3 GL_OES_vertex_array_object GL_KHR_texture_compression_astc_ldr ANDROID_EMU_host_side_tracing ANDROID_EMU_gles_max_version_3_0
D/eglCodecCommon: setVertexArrayObject: set vao to 0 (0) 0 0
D/EGL_emulation: eglCreateContext: 0xd04d9140: maj 3 min 0 rcv 3
D/HostConnection: createUnique: call
D/HostConnection: HostConnection::get() New Host Connection established 0xe2a99d60, tid 17843
D/HostConnection: HostComposition ext ANDROID_EMU_CHECKSUM_HELPER_v1 ANDROID_EMU_dma_v1 ANDROID_EMU_YUV420_888_to_NV21 ANDROID_EMU_YUV_Cache ANDROID_EMU_async_unmap_buffer GL_OES_EGL_image_external_essl3 GL_OES_vertex_array_object GL_KHR_texture_compression_astc_ldr ANDROID_EMU_host_side_tracing ANDROID_EMU_gles_max_version_3_0
E/eglCodecCommon: GoldfishAddressSpaceHostMemoryAllocator: ioctl_ping failed for device_type=5, ret=-1
D/EGL_emulation: eglMakeCurrent: 0xe8dda1e0: ver 3 0 (tinfo 0xe2aa4230)
D/EGL_emulation: eglMakeCurrent: 0xd04d9140: ver 3 0 (tinfo 0xe2a03290)
D/eglCodecCommon: setVertexArrayObject: set vao to 0 (0) 3 2
I/OpenGLRenderer: Davey! duration=703ms; Flags=1, IntendedVsync=3083221064235, Vsync=3083637730885, OldestInputEvent=9223372036854775807, NewestInputEvent=0, HandleInputStart=3083649770900, AnimationStart=3083649916800, PerformTraversalsStart=3083650041500, DrawStart=3083739081600, SyncQueued=3083754987900, SyncStart=3083825450800, IssueDrawCommandsStart=3083833396900, SwapBuffers=3083923188800, FrameCompleted=3083995386800, DequeueBufferDuration=33672000, QueueBufferDuration=2910000,
D/EGL_emulation: eglMakeCurrent: 0xe8dda1e0: ver 3 0 (tinfo 0xe2aa4230)
I/es.java.helloa: Background concurrent copying GC freed 3194(633KB) AllocSpace objects, 1(1028KB) LOS objects, 51% free, 1421KB/2MB, paused 22.628ms total 119.922ms
D/eglCodecCommon: setVertexArrayObject: set vao to 0 (0) 0 0
D/eglCodecCommon: setVertexArrayObject: set vao to 0 (0) 0 1
D/eglCodecCommon: setVertexArrayObject: set vao to 1 (1) 2 0
D/eglCodecCommon: setVertexArrayObject: set vao to 0 (0) 2 1
D/eglCodecCommon: setVertexArrayObject: set vao to 0 (0) 3 1
D/eglCodecCommon: setVertexArrayObject: set vao to 0 (0) 4 1
D/eglCodecCommon: setVertexArrayObject: set vao to 2 (2) 5 0
D/eglCodecCommon: setVertexArrayObject: set vao to 0 (0) 5 1
D/eglCodecCommon: setVertexArrayObject: set vao to 3 (3) 6 0
D/eglCodecCommon: setVertexArrayObject: set vao to 0 (0) 6 1
D/eglCodecCommon: setVertexArrayObject: set vao to 4 (4) 7 0
D/eglCodecCommon: setVertexArrayObject: set vao to 0 (0) 7 1
D/eglCodecCommon: setVertexArrayObject: set vao to 0 (0) 8 1
D/eglCodecCommon: setVertexArrayObject: set vao to 0 (0) 9 1
D/eglCodecCommon: setVertexArrayObject: set vao to 0 (0) 10 1
D/eglCodecCommon: setVertexArrayObject: set vao to 5 (5) 10 0
I/ARCore-ArCoreApk: Starting setup activity
I/Choreographer: Skipped 124 frames! The application may be doing too much work on its main thread.
D/EGL_emulation: eglMakeCurrent: 0xd04d9140: ver 3 0 (tinfo 0xe2a03290)
D/EGL_emulation: eglMakeCurrent: 0xd04d9140: ver 3 0 (tinfo 0xe2a03290)
D/EGL_emulation: eglMakeCurrent: 0xe8dda1e0: ver 3 0 (tinfo 0xe2aa4230)
I/OpenGLRenderer: Davey! duration=1069ms; Flags=1, IntendedVsync=3086287590682, Vsync=3086304257348, OldestInputEvent=9223372036854775807, NewestInputEvent=0, HandleInputStart=3086304637800, AnimationStart=3086304776000, PerformTraversalsStart=3086304824100, DrawStart=3086615425400, SyncQueued=3086621099300, SyncStart=3086852824300, IssueDrawCommandsStart=3086900241500, SwapBuffers=3087339599500, FrameCompleted=3087588418700, DequeueBufferDuration=36094000, QueueBufferDuration=503000,
I/Choreographer: Skipped 81 frames! The application may be doing too much work on its main thread.
D/EGL_emulation: eglMakeCurrent: 0xd04d9140: ver 3 0 (tinfo 0xe2a03290)
I/OpenGLRenderer: Davey! duration=1698ms; Flags=0, IntendedVsync=3086305423692, Vsync=3087655423638, OldestInputEvent=9223372036854775807, NewestInputEvent=0, HandleInputStart=3087658539200, AnimationStart=3087658835600, PerformTraversalsStart=3087661398600, DrawStart=3087910356800, SyncQueued=3087922238400, SyncStart=3087932545800, IssueDrawCommandsStart=3087944925100, SwapBuffers=3087947626300, FrameCompleted=3088014401000, DequeueBufferDuration=18565000, QueueBufferDuration=3940000,
I/ARCore-ArCoreApk: Starting setup activity
D/EGL_emulation: eglMakeCurrent: 0xe8dda1e0: ver 3 0 (tinfo 0xe2aa4230)
Connected to the target VM, address: 'localhost:55306', transport: 'socket'
D/EGL_emulation: eglMakeCurrent: 0xd04d9140: ver 3 0 (tinfo 0xe2a03290)
D/EGL_emulation: eglMakeCurrent: 0xd04d9140: ver 3 0 (tinfo 0xe2a03290)
I/third_party/arcore/ar/core/android/sdk/session_create.cc: Entering ArSession_createWithFeatures
ARCore Version: SDK build name: 1.22
I/third_party/arcore/ar/core/android/sdk/session_create.cc: ARCore Version: APK version code: 203220533
I/third_party/arcore/ar/core/android/sdk/session_create.cc: Dynamite load ok.
I/third_party/arcore/java/com/google/vr/dynamite/client/native/dynamite_client.cc: Attempting to load native library arcore_c from package com.google.ar.core
I/third_party/arcore/java/com/google/vr/dynamite/client/native/dynamite_client.cc: Dynamite::LoadNativeRemoteLibrary handle=2038953293
I/third_party/arcore/ar/core/android/sdk/session_create.cc: ARCore SDK: dynamite number_of_symbols_loaded=226
I/native: session_create_implementation.cc:206 Entering createImplementationWithFeaturesAndSettings. ARCore SDK version: [1.22.202940000].
V/third_party/redwood/infrastructure/jni_common/jni_helper.cc: JniHelper: attached thread (Called from line 364).
E/native: session_create_implementation_shared.cc:1954 Unable to obtain device profile from the content provider: NOT_FOUND: Device is not supported.
session_create_implementation_shared.cc:2268 Failed to create calibration config and device profile.
W/native: session_create_implementation_shared.cc:2269 CreateDeviceProfileDirectDependencies returning NOT_FOUND:
ARCoreError: third_party/arcore/ar/core/android/implementation/session_create_implementation_shared.cc:1958
[type.googleapis.com/util.ErrorSpacePayload='ArStatusErrorSpace::AR_UNAVAILABLE_DEVICE_NOT_COMPATIBLE'].
V/third_party/redwood/infrastructure/jni_common/jni_helper.cc: ~JniHelper: about to detach thread (Called from line 364).
~JniHelper: detached thread (Called from line 364).
E/native: error_policy_util.cc:263
################ ARCore Native Error ##################
BUILD_CHANGELIST:344925174
BUILD_BASELINE_CHANGELIST:342918918
################### Stack Trace Begin ################
ARCoreError: third_party/arcore/ar/core/android/implementation/session_create_implementation_shared.cc:1958 https://cs.corp.google.com/piper///depot/google3/third_party/arcore/ar/core/android/implementation/session_create_implementation_shared.cc?g=0&l=1958
ARCoreError: third_party/arcore/ar/core/android/implementation/session_create_implementation.cc:315 https://cs.corp.google.com/piper///depot/google3/third_party/arcore/ar/core/android/implementation/session_create_implementation.cc?g=0&l=315
ARCoreError: third_party/arcore/ar/core/android/implementation/session_create_implementation.cc:411 https://cs.corp.google.com/piper///depot/google3/third_party/arcore/ar/core/android/implementation/session_create_implementation.cc?g=0&l=411
################### Stack Trace End #################

################### Undecorated Trace Begin  #################
NOT_FOUND: 
ARCoreError: third_party/arcore/ar/core/android/implementation/session_create_implementation.cc:315

ARCoreError: third_party/arcore/ar/core/android/implementation/session_create_implementation_shared.cc:1958
 [type.googleapis.com/util.ErrorSpacePayload='ArStatusErrorSpace::AR_UNAVAILABLE_DEVICE_NOT_COMPATIBLE']
################### Undecorated Trace End  #################

W/es.java.helloa: Accessing hidden method Landroid/widget/TextView;->getTextDirectionHeuristic()Landroid/text/TextDirectionHeuristic; (light greylist, linking)
E/HelloArActivity: Exception creating session
com.google.ar.core.exceptions.UnavailableDeviceNotCompatibleException
at java.lang.reflect.Constructor.newInstance0(Native Method)
at java.lang.reflect.Constructor.newInstance(Constructor.java:343)
at com.google.ar.core.Session.throwExceptionFromArStatus(Session.java:16)
at com.google.ar.core.Session.nativeCreateSessionAndWrapperWithFeatures(Native Method)
at com.google.ar.core.Session.(Session.java:11)
at com.google.ar.core.Session.(Session.java:4)
at com.google.ar.core.examples.java.helloar.HelloArActivity.onResume(HelloArActivity.java:256)
at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1412)
at android.app.Activity.performResume(Activity.java:7292)
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3776)
at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3816)
at android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:51)
at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:145)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:70)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1808)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:193)
at android.app.ActivityThread.main(ActivityThread.java:6669)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
D/EGL_emulation: eglMakeCurrent: 0xe8dda1e0: ver 3 0 (tinfo 0xe2aa4230)
D/EGL_emulation: eglMakeCurrent: 0xe8dda1e0: ver 3 0 (tinfo 0xe2aa4230)
Disconnected from the target VM, address: 'localhost:55306', transport: 'socket'

```

Edit:

I tried to install "Google_Play_Services_for_AR_1.22.0_x86_for_emulator.apk"(from git: https://github.com/google-ar/arcore-android-sdk/releases) and used SDK 29. And it worked.
But i don't understand why it's not work:
-- When i try to use SDK 29 with Google_Play_Services_for_AR in Google Play Store
-- When i try to use SDK 27,28, 30 with install "Google_Play_Services_for_AR_1.22.0_x86_for_emulator.apk" from Git

[sandyfriend]

@Thuaanf
in the error log, it showed the device can not find the right device profile.
I can not reproduce the issue with Pixel 2
could you provide the build fingerprint with full logcat?
Update:
If you use emulator，
Google_Play_Services_for_AR in Google Play Store will not work, those device profile
target for physical devices.
Please refer:
https://developers.google.com/ar/discover/supported-devices#emulators
for SDK versions are not working, Do you run it with Windows?

[sabatminas]

@inio
Hello sir,
I'm recently working on my university graduation project about AR tech. Completed all of the Unity side, but having trouble with the ARCore side. Because it turns out my device is not supported..
Are there any significant hardware issues with _Samsung Galaxy A6+ (SM-A605FN) / Android10?_ I want to learn that because the devices below (A5, A6, A7) are officially supported, but why not A6+ ?

• Samsung | Galaxy A5 (2017) | Supports multiple GPU texture resolutions - 1440x1080, 960x720, 480p
• Samsung | Galaxy A6 (2018) |  
• Samsung | Galaxy A7 (2017) | Some models only support OpenGL ES 3.0 and earlier

Tried all of the unofficial methods all week to make it run, but no results.. Could you do us a favor and please add Samsung A6+ to supported device list if its possible and if hardware specs are valid?

Thank you
Best regards

[x2k13]

Please add Support for Samsung Galaxy Tab A 10.5:
SM-T590NZKADBT, WiFi version & SM-T595NZKADBT, LTE version

Galaxy Tab A 10.5 (SM-T590NZKADBT)

- OS: Android 10
- Chipset: Qualcomm SDM450 Snapdragon 450 (14 nm)
- CPU: Octa-core 1.8 GHz Cortex-A53
- GPU: Adreno 506
- Storage (internal): 32GB
- RAM: 3GB

- Main Camera: 
- Single: 8 MP, f/1.9, AF
- Features: LED flash, panorama
- Video: 1080p@30fps

Thank you!

[lantuin]

Hello,

would the redmi k20 Pro / Mi 9T Pro support Arcore depth API?
At the moment it is listed only for ARCore supported devices but not for DEPTH API.