Database Develop

The Moto G5S now supports ARCore!

According to the newly updated supported devices page for ARCore, the Moto G5(S) Plus supports ARCore
(https://developers.google.com/ar/discover/supported-devices),
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

ARCore only works on 64-bit devices. It's possible that they're going to be releasing a 32-bit version, but some part of me wants to hope that this means the G5S Plus will be updated to 64-bit with the Oreo update.

Already Supporting....
Moto G (5S) Plus supports ARCore in Nougat. Just download ARCore APK from APKMirror and Install it. And Download AR Apps From Play Store and Start Using AR Apps.

sensi277 said:
ARCore only works on 64-bit devices. It's possible that they're going to be releasing a 32-bit version, but some part of me wants to hope that this means the G5S Plus will be updated to 64-bit with the Oreo update.
Click to expand...
Click to collapse
There is no such requirement for ARCore, all that is required is the ARCore app from the play store, after which any ARCore based apps will run.
Tested on Stock Nougat.
Besides though, I think it's highly unlikely that an official stock version of 64bit oreo will be released since an upgrade to a 64bit device requires a complete wipe, which 95%+ of the user base for this phone simply would never agree to
If they do invest into find a workaround to somehow do this, I doubt they would take such an effort on a non flagship device

amithkk said:
There is no such requirement for ARCore, all that is required is the ARCore app from the play store, after which any ARCore based apps will run.
Tested on Stock Nougat.
Besides though, I think it's highly unlikely that an official stock version of 64bit oreo will be released since an upgrade to a 64bit device requires a complete wipe, which 95%+ of the user base for this phone simply would never agree to
If they do invest into find a workaround to somehow do this, I doubt they would take such an effort on a non flagship device
Click to expand...
Click to collapse
Yeah, they're telling as if they're working hard to build 32-64bits converted OS update just to fool customers.
As the companies like Moto&lenovo have plenty of product in line, it's really hard to concentrate on one particular product and conduct developments. You can take the examples of Samsung ( not in 2018). They had many models in their line, if they want to provide updates, they need to employ nearly 15-20 engineers only for software development and testing. But they'll not worry about this, and stay back by doing so just to save money. Because they can invest that money on new devices. Launching pros, plus and special varients?.
Whereas Companies like Oneplus have very few devices and can concentrate on product developments. So, we should take blame on ourselves for choosing this brand!
It's really very unlikely to get(even to expect) 64Bit varient

sensi277 said:
ARCore only works on 64-bit devices. It's possible that they're going to be releasing a 32-bit version, but some part of me wants to hope that this means the G5S Plus will be updated to 64-bit with the Oreo update.
Click to expand...
Click to collapse
Custom rom lol bro

(Requesting Help) Trouble with architecture

I decided one day that id try using custom roms from this site and its been nice, I mean ive tried almost all the roms in this section. The reason for creating this thread and requesting help started when I decided to change from OctexGold (just wanted a change), misread and downloaded a rom for another device (woops). I dont remember the rom and for what device.
The problem :
My architecture is detected as ARM, the 32 bit version.
This is holding me back on plenty of stuff I want to try out, since ARM64 is what ive found most developers seek to support.
I realized the architecture had changed from ARM64, when I installed a proper rom after the mistake, and the GApps ARM64 version was no longer working and I has to use the 32 version.
If anyone could tell me how to fix this, itd mean alot to me, since I just cant seem to find anything.
Idk, just felt to include this screenshot from the Droid Info app
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

To clarify, ive only ever browsed on this site, and this the first account I just created before this post so I apologize if theres anything im doing wrong.

So, if you're phone is G610X (J7Prime). The correct and Default architecture is ARM for ROM / Firmware, and our CPU as far as i know must be support ARM64 but there is no ARM64 Source / Firmware.
Conclusion :
- The Correct one is ARM Instead of ARM64
- Currently there is no ARM64 Based ROM so far
Solution :
For anything to be Fixed / Back To Normal please Reflash Original Firmware:fingers-crossed:
And to be clear can you Send me the link about your False ROM installation? Maybe i can inspect why this is happened because in common the ROM will not flash by Giving ERROR saying Device not Compatible or Something.:silly:
I Guess that's it, Sorry for some bad language.

Cruxter321 said:
So, if you're phone is G610X (J7Prime). The correct and Default architecture is ARM for ROM / Firmware, and our CPU as far as i know must be support ARM64 but there is no ARM64 Source / Firmware.
Conclusion :
- The Correct one is ARM Instead of ARM64
- Currently there is no ARM64 Based ROM so far
Solution :
For anything to be Fixed / Back To Normal please Reflash Original Firmware:fingers-crossed:
And to be clear can you Send me the link about your False ROM installation? Maybe i can inspect why this is happened because in common the ROM will not flash by Giving ERROR saying Device not Compatible or Something.:silly:
I Guess that's it, Sorry for some bad language.
Click to expand...
Click to collapse
Thanks, I appreciate the reply. :good:
If I find the ROM, I'll send it.

data.mistat.intl.Xiaomi.com

I have used https://github.com/Szaki/XiaomiADBFastbootTools to uninstall all Xiaomi bloatware but I'm still seeing the mistat contacting its server every minute, maybe because I blocked it and it keeps on retrying. I wonder which Xiaomi bloatware I have to disable to turn this off?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Mi 9T Pro using Tapatalk

Tom
I have the same problem, it appears to be draining battery, as it was the phone very often.

Its find device service, You can't get rid of it.

tollboy said:
Its find device service, You can't get rid of it.
Click to expand...
Click to collapse
Find Device can't be debloated by ADB and if you remove/hide its apk (systemlessly or not), you get bootloop:
/system/priv-app/FindDevice/FindDevice.apk
The best you can do is to logout from the stock Find Device - from time to time it will complain that using Find Device would be safer
Edit:
Btw, not sure if/how data.mistat intl.xiaomi is related to FindDevice (com.xiaomi.finddevice)

zgfg said:
Find Device can't be debloated by ADB and if you remove/hide its apk (systemlessly or not), you get bootloop:
/system/priv-app/FindDevice/FindDevice.apk
The best you can do is to logout from the stock Find Device - from time to time it will complain that using Find Device would be safer
Edit:
Btw, not sure if/how data.mistat intl.xiaomi is related to FindDevice (com.xiaomi.finddevice)
Click to expand...
Click to collapse
It's related to Xiaomi Service Framework. Freezing or removing it (which I don't think is possible, at least not via the Debloat tool) will result in a bootloop.

Catsonvi said:
It's related to Xiaomi Service Framework. Freezing or removing it (which I don't think is possible, at least not via the Debloat tool) will result in a bootloop.
Click to expand...
Click to collapse
Service framework can be debloated

IoIam said:
Service framework can be debloated
Click to expand...
Click to collapse
Ever managed to boot into MIUI after doing so? In my case China beta, China stable, Global stable and xiaomi.eu bootloop. XSF is like GSM, except that a lot of OS components rely on it in order to work properly. Also (ironically) every connection to Alibaba servers is done through XSF.

Catsonvi said:
Ever managed to boot into MIUI after doing so? In my case China beta, China stable, Global stable and xiaomi.eu bootloop. XSF is like GSM, except that a lot of OS components rely on it in order to work properly. Also (ironically) every connection to Alibaba servers is done through XSF.
Click to expand...
Click to collapse
I removed it with adb commands through termux in Xiaomi.eu

Porting TWRP to the Note 10 Lite

Hey everyone,
As nobody has been willing to port TWRP to the Note 10 Lite and due to the unfortunate circumstances of OTA Updates bricking my own phone every time I have more or less been forced to get TWRP running on my device to even have a chance of recovering at least some data from it.
I will keep everyone posted on my progress but keep in mind that this is the first time I attempt to port TWRP or any other android component to a phone so progress might not go very smoothly at first.
I'm currently in the progress of getting a working build environment set up based on TWRP for the Galaxy S9 as it seems to share the same SoC as the Note 10 Lite which should at least provide a better base than starting from scratch. I hope to get something working before the end of the week as it's fairly critical for me to get it working asap.
If anybody who at least knows some stuff about porting TWRP to samsung devices wants to help me out I'd really appreciate it. Every nudge in the right direction is very nice to have so feel free to respond here or pass me a message
Current issue:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

FFS2309 said:
Hey everyone,
As nobody has been willing to port TWRP to the Note 10 Lite and due to the unfortunate circumstances of OTA Updates bricking my own phone every time I have more or less been forced to get TWRP running on my device to even have a chance of recovering at least some data from it.
I will keep everyone posted on my progress but keep in mind that this is the first time I attempt to port TWRP or any other android component to a phone so progress might not go very smoothly at first.
I'm currently in the progress of getting a working build environment set up based on TWRP for the Galaxy S9 as it seems to share the same SoC as the Note 10 Lite which should at least provide a better base than starting from scratch. I hope to get something working before the end of the week as it's fairly critical for me to get it working asap.
If anybody who at least knows some stuff about porting TWRP to samsung devices wants to help me out I'd really appreciate it. Every nudge in the right direction is very nice to have so feel free to respond here or pass me a message
Current issue:
View attachment 5201069
Click to expand...
Click to collapse
I have already made TWRP for Note10 Lite, And one more dev also made TWRP for N10Lite..
TWRP is ready but vbmeta check not allowing to flash any custom recovery in partition.
Yes we have flashed vbmeta disabled file but even phone says vbemta disabled value set still it gives while flashing twrp or any custom recovery error vbmeta verification failed.
This might be due to vbmeta in BL cross checking vbmeta of AP.
This same problem is present on other many samsung phones too.. and was present on s20 before but samsung fixed it with OTA update.
Unless samsung fixes that or give us private keys to sign twrp to use partition without that you cant flash anything into partition.
I haven't tried on one ui 3/ Android 11 firmware but I have seen vbmeta file of it, its the same as one ui 2.5.
I have posted all of this info here on XDA but got deleted cause I deleted my account. Will post again.
You can PM me if you want any help.

Unable to pass ctsProfile

Hello All,
My device was brick when I dirty flash the Lineage OS 20211003 to 20211110.
So the flash it back to stock Android 11 (Nov 2021 update) via fastboot, then flash Lineage OS 20211110 again.
And this time everything is fine except I can get the ctsProfile pass at 20211003, but failed this time.
I have try though the process at https://forum.xda-developers.com/t/tutorial-unlock-bootloader-get-root-and-valid-safetynet.4178673/
but no luck.
Magisk version is 23.0
Spoiler
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And the modules I currently installed, tried riru - LSposed but it is not helping so I removed.
Spoiler
Any ideas I can fix the ctsProfile issue?
{Mod edit: Spoiler added for better reading & scrolling experience}

Is that build of LOS using a certified device fingerprint out of the box? Otherwise you need to apply one to pass CTS.

Didgeridoohan said:
Is that build of LOS using a certified device fingerprint out of the box? Otherwise you need to apply one to pass CTS.
Click to expand...
Click to collapse
Humm ... I'm not sure, may I ask how to check?
Ok, I installed MagiskHide Props Config, and got a string as following:
google/redfin/redfin:11/RQ3A.211001.001/7641976:user/release-keys
but I'm not sure it is certified or not

Arlik said:
Humm ... I'm not sure, may I ask how to check?
Ok, I installed MagiskHide Props Config, and got a string as following:
google/redfin/redfin:11/RQ3A.211001.001/7641976:user/release-keys
but I'm not sure it is certified or not
Click to expand...
Click to collapse
You mean that's the reported used fingerprint? Looks ok, but it's also possible that the ROM has a security patch date that doesn't match the print. Try applying a Pixel 5 print from the module and see if that helps.

Try to apply Pixel 5, 5a, 3a Android 11's fingerprint by pressing
f - Pick a certified fingerprint
After reboot, it still show
google/redfin/redfin:11/RQ3A.211001.001/7641976:user/release-keys
Did I do something wrong?

Just an update.
The issue should be relay to the November update of LOS
now I redo all my process with LOS 20211020 version, safetyNet has passed.

Arlik said:
Just an update.
The issue should be relay to the November update of LOS
now I redo all my process with LOS 20211020 version, safetyNet has passed.
Click to expand...
Click to collapse
All of a sudden, my SafetyNet is failing. I've tried these tricks posted online like Riru, Universal Safety Fix, etc. None of them work! I am on LOS 20211229. If the 20211020 version would work, I don't mind going back. Where can I download it? The official LOS site now has only the Dec 2021 version. I tried to Google for this older version but can't find it. Thank you