Thanks to the devs, now we Zenfone 5 users can finally use Android N.
***************************************************************************************
Please dont blame me if you mess up, in following the instructions properly.
This method has been tested thoroughly and I'm not responsible if something happens to your phone.
If you point your finger at me, I'll laugh at your face.
//Always wanted to do this.
***************************************************************************************
Requirements:
Android 7.1+
Rooted Device
BuildProp Editor
Please follow the following steps :
Step 1 : Download BuildProp Editor and the latest version of Google App from PlayStore(or you can directly flash Nano Gapps or any higher variant).
Step 2 : Append the following line,
Code:
ro.opa.eligible_device=true
Step 3: After this save the edited file(BuildProp Editor will ask for Root Permissions).
Step 4 : Reboot the Device.
Step 5 : Clear all data of the Google App(Optional, you can skip this.If it doesnt work try it nonetheless).
Step 6 : Assign Assist App as Google App in Settings(Optional, if you have flashed Nano Gapps or any higher variant).
Step 7 : Enjoy !! :good: :victory:
Profit!!
DroidNoob123 said:
Thanks to the devs, now we Zenfone 5 users can finally use Android N.
***************************************************************************************
Please dont blame me if you mess up, in following the instructions properly.
This method has been tested thoroughly and I'm not responsible if something happens to your phone.
If you point your finger at me, I'll laugh at your face.
//Always wanted to do this.
***************************************************************************************
Requirements:
Android 7.1+
Rooted Device
BuildProp Editor
Please follow the following steps :
Step 1 : Download BuildProp Editor and the latest version of Google App from PlayStore.
Step 2 : Open BuildProp Editor and change the following lines,
ro.product.brand=asus --> ro.product.brand=Google
ro.product.model=T00F/T00J --> ro.product.model=Pixel
Step 3 : Append the following lines,
ro.opa.eligible_device=true
ro.build.system_root_image=true
Step 4 : After this save the edited file(BuildProp Editor will ask for Root Permissions).
Step 5 : Reboot the Device.
Step 6 : Clear all data of the Google App.
Step 7 : Assign Assist App as Google App in Settings.
Step 8 : Enjoy !! :good: :victory:
Click to expand...
Click to collapse
Well if you just add the below lines in build.prop
Code:
ro.product.model=Pixel XL
ro.opa.eligible_device=true
It does the work . tested on all nougat roms for zenfone 5 toof.
also replacing the model and device may have conflict with audio and video .
Just remember to push Google app as system app first then do the changes .
Boomshiva said:
Well if you just add the below lines in build.prop
Code:
ro.product.model=Pixel XL
ro.opa.eligible_device=true/CODE]
It does the work . tested on all nougat roms for zenfone 5 toof.
also replacing the model and device may have conflict with audio and video .
Just remember to push Google app as system app first then do the changes .[/QUOTE]
Yes, however the only bugs that I faced is that PixelMaster Camera doesnt work, but no problems with Google Camera.
Click to expand...
Click to collapse
Boomshiva said:
Well if you just add the below lines in build.prop
Code:
ro.product.model=Pixel XL
ro.opa.eligible_device=true
It does the work . tested on all nougat roms for zenfone 5 toof.
also replacing the model and device may have conflict with audio and video .
Just remember to push Google app as system app first then do the changes .
Click to expand...
Click to collapse
i tried this, my model is T00J nd apparently for some reason this doesnt work.Assistant doesnt take any input.
shd i try changing all the aforesaid line ?
Awesome111 said:
i tried this, my model is T00J nd apparently for some reason this doesnt work.Assistant doesnt take any input.
shd i try changing all the aforesaid line ?
Click to expand...
Click to collapse
Yes.
That method has been tested for T00F devices.
Hence, the need of a new thread.
DroidNoob123 said:
Yes.
That method has been tested for T00F devices.
Hence, the need of a new thread.
Click to expand...
Click to collapse
Thanks, man.
Awesome111 said:
Thanks, man.
Click to expand...
Click to collapse
If you are using my method then configure first google app then add the lines to build prop . download chop assistant from play store enable it from accessibility settings that's it you are good to go .
tank4k said:
Shortcut - just flash nano gapps. Thank me later
Click to expand...
Click to collapse
You mean, if you flash nano gapps, it already contains google assistant or still need to edit build.prop??
I just did as you told,then I find the microphone dosen't work.:crying:upset
24kptjo said:
I just did as you told,then I find the microphone dosen't work.:crying:upset
Click to expand...
Click to collapse
same here
24kptjo said:
I just did as you told,then I find the microphone dosen't work.:crying:upset
Click to expand...
Click to collapse
What microphone not working . so you saying by using the op method microphone got damaged ? I don't understand .
Try the method suggested by me.
1: revert all changes first .
2: download google app and make it system app ( or you can flash nano gapps ) set ur preference.
3: edit build prop . just add the below lines
Code:
ro.opa.eligible_device=true
4: reboot to recovery , wipe cache and dalvik cache . reboot
Boomshiva said:
What microphone not working . so you saying by using the op method microphone got damaged ? I don't understand .
Try the method suggested by me.
1: revert all changes first .
2: download google app and make it system app ( or you can flash nano gapps ) set ur preference.
3: edit build prop . just add the below lines
4: reboot to recovery , wipe cache and dalvik cache . reboot
Click to expand...
Click to collapse
Without change ro.product.brand and ro.product.model?
24kptjo said:
Without change ro.product.brand and ro.product.model?
Click to expand...
Click to collapse
Yes don't change anything just add the above mentioned line at the end of build prop .
See the attached image .
Boomshiva said:
Yes don't change anything just add the above mentioned line at the end of build prop .
See the attached image .
Click to expand...
Click to collapse
That works perfectly!:victory: thank you
killar_aka_arabu said:
same here
Click to expand...
Click to collapse
24kptjo said:
I just did as you told,then I find the microphone dosen't work.:crying:upset
Click to expand...
Click to collapse
Guys, I'm really sorry for dropping the ball on this thread and no excuse of mine can uphold my incompetence.
However, huge thanks to Boomshiva and tank4k for talking care of this thread in my absence.
In light of recent events, Google has now removed the restriction, that a device needs to be Pixel to use Google Assistant.
So you can essentially skip the steps for changing Device Model and Brand.
Now just append(add to the end) the following line to the end of build.prop :-
Code:
ro.opa.eligible_device=true
after doing this Reboot you phone. Profit !!
The confusion of flashing whether nano or any lower variant:
Nano Variant of Gapps automatically flashes Google app as a System app, whereas lower variants dont.
If you are going to flash a lower sized variant, u have to make Google as a System app.
DroidNoob123 said:
Guys, I'm really sorry for dropping the ball on this thread and no excuse of mine can uphold my incompetence.
However, huge thanks to Boomshiva and tank4k for talking care of this thread in my absence.
In light of recent events, Google has now removed the restriction, that a device needs to be Pixel to use Google Assistant.
So you can essentially skip the steps for changing Device Model and Brand.
Now just append(add to the end) the following line to the end of build.prop :-
after doing this Reboot you phone. Profit !!
The confusion of flashing whether nano or any lower variant:
Nano Variant of Gapps automatically flashes Google app as a System app, whereas lower variants dont.
If you are going to flash a lower sized variant, u have to make Google as a System app.
Click to expand...
Click to collapse
Cool , bro
can I use google assistant in portuguese? Its work just in english
Related
HOW TO UPDATE GOOGLE MAPS:
I saw many pp ask about this and now I will type the guide here:
- Remove old version of Map
- Go to your /data/system
- Take the file "packages.xml" and copy to somewhere (sdcard, pc..etc)
- Open it wit NOtepad++ (on PC - recommend) and search then delete the line: <shared-user name="com.google.android.apps.maps".....>
- Copy the file back to its place and set permission rw-r-r
- Install this new signed version below as normal apk
- Done & Test
Download:
Version 6.12 http://www.mediafire.com/?17l0ayhlyx0fdxo
Version 6.11: https://www.dropbox.com/s/0ufwl1bfo6zqx2i/Maps6.11.1_Mod.apk
FAQ:
Q: Why I dont make a patch/update via updater?
A: Becoz it depends on your packages.xml and UserID
Q: Is there any other easy way?
A: I dont know Just found this way and it works for me. If u can find other easy way, pm me and I will update the guide.
Nice Guide DK
Put this on the myth updater app .
Sent from my GT-S5830 using Tapatalk 2
dredremon said:
Put this on the myth updater app .
Sent from my GT-S5830 using Tapatalk 2
Click to expand...
Click to collapse
Dont u read 1st post?
Updated version 6.12
devilsking said:
Updated version 6.12
Click to expand...
Click to collapse
I don't have the line you showed. I only have this one;
<shared-user name="android.uid.shared" userId="10007">
Should I delete this one instead?
When installing from market, it says this
"Incompatible with other applications using same shared user ID"
Working great....thanks Leo !!!
SuperAce609 said:
I don't have the line you showed. I only have this one;
<shared-user name="android.uid.shared" userId="10007">
Should I delete this one instead?
When installing from market, it says this
"Incompatible with other applications using same shared user ID"
Click to expand...
Click to collapse
I think u should find: com.google.android.apps.maps =.=
Some users tested and it works so It's weird if it doesnt appear in your phone
what apps did you use to move the xml file?
also what app is use for changing chmod?
hey guys,
this might be a more broader android question, but either way: is there a way to change the hardware device name of a device?
i.e. my issue is the following - i use the "good for work" application for my work emails. My company basically has every manufacturer added to their approved list (HTC, Samsung, even Nexus devices work no problem). Now that I have my sweet OP3, I get the below error message (pic attached)
"the device hardware version is 'oneplus a3000 android 6.0.1' and is not permitted. Install the application on a permitted device."
now - before you tell me to go to my network admins and have the device added - I can't do that for reasons I won't go into here. Basically i want to understand if there's a way to change certain files on the phone that will make this application think it's a nexus device and clear it.
I tried editing the build.prop file (using twrp and adb - since I don't have root) to remove all mention of oneplus, etc. and replacing with "nexus" or something else (used the build.prop file from my 5x for reference). But the app still does not work and the OP3 still shows the model as One Plus 3 in the "about phone" section. This is really fascinating to me. What is driving this device's identity?
Appreciate any thoughts/suggestions you might have.
Try xposed mods... I think it is possible
Wrong forum.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
wrong section.
post this in Q&A
@piotrus22, If you correctly modified your build prop then it's almost impossible to come as Oneplus name in about section of setting.
as far as I know the name in about section is read from build prop.
can you provide link to your modified build.prop file so i can see what's a problem.
Have you applied correct permissions (rw-r--r-- or 0644) to build prop after side loading
Go to your Bluetooth settings, select the menu, and Rename this device.
JumboMan said:
@piotrus22, If you correctly modified your build prop then it's almost impossible to come as Oneplus name in about section of setting.
as far as I know the name in about section is read from build prop.
can you provide link to your modified build.prop file so i can see what's a problem.
Have you applied correct permissions (rw-r--r-- or 0644) to build prop after side loading
Click to expand...
Click to collapse
thanks @JumboMan. attached are both build.props (edited and non-edited). I ran the command "adb shell chmod 644 /system/build.prop" after I pushed the file onto the phone. I believe it worked because I added the line about LCD density (ro.sf.lcd_density=420) and the density did indeed change. Also - I am able to view the updated build.prop in a file browser when I open the phone with the changes I've made.
...still confused...
piotrus22 said:
thanks @JumboMan. attached are both build.props (edited and non-edited). I ran the command "adb shell chmod 644 /system/build.prop" after I pushed the file onto the phone. I believe it worked because I added the line about LCD density (ro.sf.lcd_density=420) and the density did indeed change. Also - I am able to view the updated build.prop in a file browser when I open the phone with the changes I've made.
...still confused...
Click to expand...
Click to collapse
I have carefully inspected build.prop file and i found that build.prop doesn't have "ro.product.model" line . That's why you are not able to change device name.
So if you have to change device name you have to manually add above line with whatever device name you want and push file to phone and apply proper permissions
e.g ro.product.model=device name you want
In your case above line will look like ro.product.model=Nexus 5x
Though not required,change lines containing OnePlus to your custom device name
JumboMan said:
I have carefully inspected build.prop file and i found that build.prop doesn't have "ro.product.model" line . That's why you are not able to change device name.
So if you have to change device name you have to manually add above line with whatever device name you want and push file to phone and apply proper permissions
e.g ro.product.model=device name you want
In your case above line will look like ro.product.model=Nexus 5x
Though not required,change lines containing OnePlus to your custom device name
Click to expand...
Click to collapse
ok - making progress here. the model name now shows up as Nexus 5x, but when the computer recognizes the phone it still shows up as ONEPLUS A3000... and what about the build? I've tweaked everything I can think of but still can't change the build number from "ONEPLUS A3000_16_0705"
any ideas?
piotrus22 said:
ok - making progress here. the model name now shows up as Nexus 5x, but when the computer recognizes the phone it still shows up as ONEPLUS A3000... and what about the build? I've tweaked everything I can think of but still can't change the build number from "ONEPLUS A3000_16_0705"
any ideas?
Click to expand...
Click to collapse
now I think I'm going out of ideas.
I think you have to ask some experienced dev
JumboMan said:
now I think I'm going out of ideas.
I think you have to ask some experienced dev
Click to expand...
Click to collapse
how do I do that? just hope one of them sees this post? LOL
piotrus22 said:
how do I do that? just hope one of them sees this post? LOL
Click to expand...
Click to collapse
Yesterday I researched a lot about your question but I only found half answer.
Now Today I'm back with more build prop lines that will 100% solve your question.
This time I tested myself first before posting to confirm the changes
So here is a Trick
=====
1.To change Model Number
ro.product.model=Nexus 5x
2.To Change Build Number
ro.build.display.id=Nexus 5x
ro.build.display.full_id=Nexus 5x
ro.build.id.hardware=Nexus 5x
=====
Note - value "Nexus 5x" is used just as an example.
You change this value to anything you want.
JumboMan said:
Yesterday I researched a lot about your question but I only found half answer.
Now Today I'm back with more build prop lines that will 100% solve your question.
This time I tested myself first before posting to confirm the changes
So here is a Trick
=====
1.To change Model Number
ro.product.model=Nexus 5x
2.To Change Build Number
ro.build.display.id=Nexus 5x
ro.build.display.full_id=Nexus 5x
ro.build.id.hardware=Nexus 5x
=====
Note - value "Nexus 5x" is used just as an example.
You change this value to anything you want.
Click to expand...
Click to collapse
you sir are amazing. just tried it and it worked. will test it out to see if it causes other issues. may I buy you a beer?
piotrus22 said:
may I buy you a beer?
Click to expand...
Click to collapse
For me Thanks=Beer, so thanks are sufficient
JumboMan said:
For me Thanks=Beer, so thanks are sufficient
Click to expand...
Click to collapse
Ok @JumboMan, so now my phone won't save video. Basically when I try to take a video with the camera app, it hangs up on the "saving" section. Then the only way to get the camera running again is to reboot. I can't believe this is related to what I did in the build.prop files right?
The driver names will ever be the real device name. So...
:thumbup:
Sent from my XT320 using xda premium
piotrus22 said:
Ok @JumboMan, so now my phone won't save video. Basically when I try to take a video with the camera app, it hangs up on the "saving" section. Then the only way to get the camera running again is to reboot. I can't believe this is related to what I did in the build.prop files right?
Click to expand...
Click to collapse
It may be due to build prop changes but I'm not sure. can you use 3rd party camera app check for your problem. or it only occurs with stock camera.
JumboMan said:
It may be due to build prop changes but I'm not sure. can you use 3rd party camera app check for your problem. or it only occurs with stock camera.
Click to expand...
Click to collapse
Third party camera app has the same problem. Will revert to original build prop and see if that fixes the issue. Will report back.
JumboMan said:
For me Thanks=Beer, so thanks are sufficient
Click to expand...
Click to collapse
Dethfull said:
The driver names will ever be the real device name. So...
:thumbup:
Sent from my XT320 using xda premium
Click to expand...
Click to collapse
@Dethfull do you know which items in the build prop coordinate to the drivers for the camera?
ok so I think I fixed it. I played around with the build.prop file and it appears changing the ro.product.manufacturer =OnePlus back from Nexus5 did the trick. Camera seems to be much faster than before and videos can save now, and the Good app still works.
Will update if things change but hopefully not!
If you don't care about OTA and can make changes to system then this guide is for you
So Google has dropped support for Phone App for our Mi A1 and can no more find it in Playstore even if you find somehow by searching on Chrome you will see the message saying This App is Not Compatible
Make following changes to your Build Prop file and Restart device. After restart Phone App will appear in Playstore and compatible with Mi A1 now
Before Making changes to Build Prop file take a backup of it incase you can to restore it later
Changes To Be Made:
ro.product.model=Pixel 2
ro.product.brand=google
ro.product.name=walleye
ro.product.device=walleye
ro.product.manufacturer=Google
Note:
After making these changes my phone got stuck on boot screen but i forced restarted it by Long Press and Hold Power Button and Both Volume Buttons all together for few seconds and it booted fine
It is not better to download Google Phone from ApkMirror and install?
bruceas said:
It is not better to download Google Phone from ApkMirror and install?
Click to expand...
Click to collapse
Nope cuz install process will fail due to incompatible phone...
I have installed Version: 17.0.184919600 (2334720) without problem.
bruceas said:
I have installed Version: 17.0.184919600 (2334720) without problem.
Click to expand...
Click to collapse
Me too
Is Systemless?
I can't install it. I have tried both version.
bruceas said:
It is not better to download Google Phone from ApkMirror and install?
Click to expand...
Click to collapse
No because you may get this popup as i got after changing rom
lukikow said:
I can't install it. I have tried both version.
Click to expand...
Click to collapse
What issue are you facing and what have you tried?
Ni9e. said:
What issue are you facing and what have you tried?
Click to expand...
Click to collapse
Check attachment.
Ni9e. said:
If you don't care about OTA and can make changes to system then this guide is for you
So Google has dropped support for Phone App for our Mi A1 and can no more find it in Playstore even if you find somehow by searching on Chrome you will see the message saying This App is Not Compatible
Make following changes to your Build Prop file and Restart device. After restart Phone App will appear in Playstore and compatible with Mi A1 now
Before Making changes to Build Prop file take a backup of it incase you can to restore it later
Changes To Be Made:
ro.product.model=Pixel 2
ro.product.brand=google
ro.product.name=walleye
ro.product.device=walleye
ro.product.manufacturer=Google
Note:
After making these changes my phone got stuck on boot screen but i forced restarted it by Long Press and Hold Power Button and Both Volume Buttons all together for few seconds and it booted fine
Click to expand...
Click to collapse
Just coz users are facing problem on google phone app they dropped support instead of fixing it? What does google hire bunch of noobs I suppose :facepalm:
Sent from my Mi A1 using Tapatalk
---------- Post added at 11:13 PM ---------- Previous post was at 11:11 PM ----------
MarkezG said:
Is Systemless?
Click to expand...
Click to collapse
No dude op clearly mentioned in first line i.e "If you don't care about OTA and can make changes to system then this guide is for you"
Sent from my Mi A1 using Tapatalk
lukikow said:
Check attachment.
Click to expand...
Click to collapse
I think no one else is facing this installing issue except you. You might have modded version of phone app installed in your phone thats why you cant install official version. Uninstall updates of phone app from application manager then try to install official apk
Got New update today 27 February ?
Ni9e. said:
Got New update today 27 February
Click to expand...
Click to collapse
Man could you please upload the file somewhere in cloud. I tried this version from apkmirror "Version: 17.0.184919600 (2334720)" but failed.
alshanu said:
Man could you please upload the file somewhere in cloud. I tried this version from apkmirror "Version: 17.0.184919600 (2334720)" but failed.
Click to expand...
Click to collapse
Bro i edited build prop file to Pixel XL 2 properties now i get all Phone.apk updates through playstore and no errors
Ni9e. said:
Bro i edited build prop file to Pixel XL 2 properties now i get all Phone.apk updates through playstore and no errors
Click to expand...
Click to collapse
When I was on stock rom that's is MIUI I was unable to install it but when I installed lineage os I got option to install google dialer without altering the build prop.
Hello, google duo icon in dialer didn't work. If someone has this problem?
!!ATTENTION!!
As Google recently changed how the device_profile files are located, these steps below do NOT work anymore. There are only two options you can choose from which you can follow and read about here
#I'll not be responsible for anything that happens to your device when you follow these steps#
If you don't know what ARCore is read this https://en.m.wikipedia.org/wiki/ARCore
After you understand what ARCore is for then continue reading.
@Arnova8G2 has made a flashable zip with support for our device.
AR Stickers download https://drive.google.com/open?id=1Uvspxje-myBIKIeDHfgMpZ4Uv_o5ZFYL
Installation steps:
1. Install original arcore linked below
2. Reboot to TWRP
3. Install twrp-Patch-ARcore-for-all-device.zip
4. Reboot to system
Zip download here. This method is still under testing, so the original method is still shown below.
Step 1. Download ARCore from here https://www.apkmirror.com/apk/googl...se/arcore-1-4-180716096-android-apk-download/
Step 2. Install an app that use ARCore. If you're lazy, you can use this https://www.apkmirror.com/apk/google-creative-lab/just-a-line-draw-anywhere-with-ar/
Step 3. Open the app you installed in step 2 and let it crash. This will make the folders and files that we're going to use later on.
Step 4. Download the file named device_profile_vince.textproto.txt at the end of this post and rename the file to device_profile_vince.textproto
Step 5. Using root explorer, copy the file you just renamed to /data/data/com.google.ar.core/files/device_profile_database2 and change SE context by selecting the file you just copied and press the three dots. Then select Restore default context and then press OK.
Step 6. Now you can use any apps that require ARCore!:victory:
NOTE: If you updated ARCore repeat step 3 to step 5
Tested on my vince running AEX and havoc os with omnivision sensor
Not really necessary anymore as we've Arnova8G2's flashable zip but I'll keep it here anyways
During the steps above, you probably saw a bunch of files in /data/data/com.google.ar.core/files/device_profile_database. One file is for one device or another variant of the same device. These files come from the manufacturers or Google themselves for the devices that officially ARCore.
Unfortunately, vince, like a lot of other devices, don't officially support ARCore, so some of these files maybe more compatible with vince but I don't have time to test them all. So if anybody have extra time, you can help me find out which one of these files is best suited for our device. You just have to rename the file you want to test to device_profile_vince_.textproto(the _ is to make sure you don't accidentally replace the original device_profile_vince.textproto file) and rename the original device_profile_vince.textproto to device_profile_vince.textproto.bak
If you believe you've found a file that's better than the one on the OP, then please tag me and post the file name in this thread and I'll test it to see if it's better before adding it to the OP
CHANGELOGS;
Code:
3.9.18:Updated links in OP and ARstickers link
5.7.18:Updated OP and Arstickers link
3.7.18:Updated OP
27.06.18:Updated OP
23.06.18:Updated ARCore link
16.06.18:Updated device_profile_vince file
31.05.18:Updated ARCore link
23.05.18: Updated ARStickers link
21.05.18: Initial post
FAQ:
Q:Why (insert app name) can't detect surface?
A:Find a surface that's not shiny or white color. Surfaces that are textured and have sufficient lighting can help. Sometimes a reboot can help too
Q:Why can't I install all apps that use ARCore in play store?
A:They're supposed to be only for devices that officially support ARCore. If you want to use them on vince, download using apkmirror
Q:Why ARCore still isn't working on MIUI even after I followed all the steps?
A:This could be because that MIUI is heavily modified from stock Android so a lot of things aren't working on it.
Q:Why isn't AR Stickers working?
A:Use this version Download, (MIRROR). Thanks to @Arnova8G2 for this
Reserved
Hi.
Thank you for your hard work.
Can I know if potentially all arcore's app can work on Vince?
I am asking this because I'm fully stock and I would like to know for root it.
Sent from my Redmi 5 Plus using Tapatalk
vespino75 said:
Hi.
Thank you for your hard work.
Can I know if potentially all arcore's app can work on Vince?
I am asking this because I'm fully stock and I would like to know for root it.
Sent from my Redmi 5 Plus using Tapatalk
Click to expand...
Click to collapse
All apps that use ARCore should work except for ARStickers, which you've to use the one linked in the FAQ. It's the only app so far I tested that needs to be modded to work.
Deer developer tried every step describe by you on miui costum rom wash n dish by Jerome-X but not worked any AR core based software always it is saying that device is not supported check the screen shots.
irfan.shikarpuri said:
Deer developer tried every step describe by you on miui costum rom wash n dish by Jerome-X but not worked any AR core based software always it is saying that device is not supported check the screen shots.
Click to expand...
Click to collapse
I wish Venice could support the AR core
Really good work done by you to enable this feature.
May be I am getting error due to miui
Mhhh... Weird.
I must wait 110 hours until unlock my bootloader... Damn.
Anyway.
I developed some app with Google tango.
And yes, the problem can be the Android version also.
Arcore works on few models with Android nougat. If you use a smooth vanilla 8.0 it can works (maybe).
If someone wants to try, please, try this app (now I can't because the bootloader),
Sent from my Redmi 5 Plus using Tapatalk
Now I got it that I have android 7.0 and AR core works good on android 8.0
Does not work with dotos.... why?
i followed exactly the guide...
irfan.shikarpuri said:
Now I got it that I have android 7.0 and AR core works good on android 8.0
Click to expand...
Click to collapse
Hmm, that's weird, it should work for nougat ROMs too. Maybe because MIUi is heavily modified
vespino75 said:
Does not work with dotos.... why?
i followed exactly the guide...
Click to expand...
Click to collapse
Are you sure you followed all the steps exactly? And how does it not work?
Yes I followed the instructions, and all the app (I tested 3 app) does not work (included the area stickers and yours in the guide).
I did also the last modify with root explorer... But I have the same problem of irfan
vespino75 said:
Yes I followed the instructions, and all the app (I tested 3 app) does not work (included the area stickers and yours in the guide).
I did also the last modify with root explorer... But I have the same problem of irfan
Click to expand...
Click to collapse
How does it not work? Did the app just crash or something else?
Stampyron said:
How does it not work? Did the app just crash or something else?
Click to expand...
Click to collapse
The app says "your device is not compatible with AR"
Sent from my Redmi 5 Plus using Tapatalk
vespino75 said:
The app says "your device is not compatible with AR"
Sent from my Redmi 5 Plus using Tapatalk
Click to expand...
Click to collapse
Then either you didn't rename the file correctly or you didn't restore SE context
Stampyron said:
Then either you didn't rename the file correctly or you didn't restore SE context
Click to expand...
Click to collapse
I did it. Both.
There is some problem... Can I do something?
I tried also to use the extension .proto instead .textproto, with the first extension the app crash.
Sent from my Redmi 5 Plus using Tapatalk
vespino75 said:
I did it. Both.
There is some problem... Can I do something?View attachment 4512944View attachment 4512945
I tried also to use the extension .proto instead .textproto, with the first extension the app crash.
Sent from my Redmi 5 Plus using Tapatalk
Click to expand...
Click to collapse
Try put permission to rw and reboot
1) Install File Explorer Root Browser
2) Go to System folder
3) Scroll all the way down and opet build.prop file
4) Add these 2 lines at the end of the file:
Code:
ro.lge.proximity.delay = 150
mot.proximity.delay = 150
5) Save the file
6) Reboot
is this a permanent fix or what?
and how did u figure it out?
thx by the way
It should be permanent. Waiting to see will it stay fixed after rom update tho.
I did a lot of research, tried some apps but it did not work, and finally found this fix on some chinese forum.
mr_techno said:
1) Install File Explorer Root Browser
2) Go to System folder
3) Scroll all the way down and opet build.prop file
4) Add these 2 lines at the end of the file:
5) Save the file
6) Reboot
Click to expand...
Click to collapse
Delay is already set at 200 in build.prop. I doubt just changing the delay fixes much.
Keep us posted on the fix…ya never know
fox_xda2 said:
Delay is already set at 200 in build.prop. I doubt just changing the delay fixes much.
Keep us posted on the fix…ya never know
Click to expand...
Click to collapse
Well I did not have delay in my build.prop (using pixel experience plus rom) and so far, no more issues with the sensor. Maybe try and change it to 150? What rom are you using?
mr_techno said:
Well I did not have delay in my build.prop (using pixel experience plus rom) and so far, no more issues with the sensor. Maybe try and change it to 150? What rom are you using?
Click to expand...
Click to collapse
PE 10.
AFAIK the instable proximity sensor issue is due to a poor driver released in a Xiaomi firmware, nothing so easy to solve.
Just registered to say my formerly non-operational proximity sensor now works perfectly (Pixel Experience)! Thanks very much.
Sentox6 said:
Just registered to say my formerly non-operational proximity sensor now works perfectly (Pixel Experience)! Thanks very much.
Click to expand...
Click to collapse
Mine too following the OP instructions ?
fox_xda2 said:
Delay is already set at 200 in build.prop. I doubt just changing the delay fixes much.
Keep us posted on the fix…ya never know
Click to expand...
Click to collapse
Worked with OP instructions.
Sent from my Redmi Note 7 using XDA Labs
Thanks, it worked perectly on PE 9!
Thanks a lot! Worked wonderfully on PE 9!
if this fix doesnt work and youve tried all kinds of "fixes" you may want to check out this if you have previously changed the screen or frame or had any hardware repair done to your xiaomi redmi note 7, there may be small peices you forgot to install. https://forum.xda-developers.com/redmi-note-7/how-to/fix-xiaomi-redmi-note-7-proximity-t4008965
Did it, seems that solved my problem to hear whatsapp audios outside in the sun. Ty
For now works like a charm in MIUI 11.0.3.0 Global, thanks.
:good:
Just want to say thanks for this fix. Works with PE10 with latest Delta update. For those who don't want root can uninstall magisk after editing build prop no problem at all
CR Droid 6.2 12JAN release. Nothing has changed unfortunately with this trick :crying:
Thanks. I am on Havoc 3.1 and the it fixed it.
Well, this can be included for sure, if y'all can let me know this actually works, I'd add the prop to the device tree. Thanks!