I wrote this for myself but here it is in case anyone is also interested.
Google sets the wifi country code to whatever is in your sim card. If the country does not have a corresponding list of enabled 5GHz frequencies, then a lot of these frequencies get disabled. This mod simply sets the country code to US. There is no GUI or anything, just enable and restart and you're all set. Android marshmallow only. I tested it on my S7 edge and it's working fine.
Enjoy.
Edit: Added OREO 8.1 version. Testing working on Pixel 2 XL.
madmack said:
I wrote this for myself but here it is in case anyone is also interested.
Google sets the wifi country code to whatever is in your sim card. If the country does not have a corresponding list of enabled 5GHz frequencies, then a lot of these frequencies get disabled. This mod simply sets the country code to US. There is no GUI or anything, just enable and restart and you're all set. Android marshmallow only. I tested it on my S7 edge and it's working fine.
Enjoy.
Click to expand...
Click to collapse
android4.4 cannot open
madmack said:
I wrote this for myself but here it is in case anyone is also interested.
Google sets the wifi country code to whatever is in your sim card. If the country does not have a corresponding list of enabled 5GHz frequencies, then a lot of these frequencies get disabled. This mod simply sets the country code to US. There is no GUI or anything, just enable and restart and you're all set. Android marshmallow only. I tested it on my S7 edge and it's working fine.
Enjoy.
Click to expand...
Click to collapse
awesome thankx
我是一个卒 said:
android4.4 cannot open
Click to expand...
Click to collapse
did you read OP's post properly ?
There is no GUI or anything, just enable and restart and you're all set.
BytesReverser said:
did you read OP's post properly ?
There is no GUI or anything, just enable and restart and you're all set.
Click to expand...
Click to collapse
sorry,my english is poor
I've been trying to find a fix ever since i got this phone and your module fixed it with no hassle
Thank you very much
Can i have your permission to share this on Mi A1 forums and xiaomi subreddit?
berezker said:
I've been trying to find a fix ever since i got this phone and your module fixed it with no hassle
Thank you very much
Can i have your permission to share this on Mi A1 forums and xiaomi subreddit?
Click to expand...
Click to collapse
Sure thing. If I can ask you to please link to this post and not share the APK.
madmack said:
Sure thing. If I can ask you to please link to this post and not share the APK.
Click to expand...
Click to collapse
No problem
Thank you again so much
Hi!
Are you actively working on this still? and did you get around to testing it on a oneplus of any kind? I got the 5T, this does nothing on it sadly, and i'm desperate for a fix
thanks!
Amornik said:
Hi!
Are you actively working on this still? and did you get around to testing it on a oneplus of any kind? I got the 5T, this does nothing on it sadly, and i'm desperate for a fix
thanks!
Click to expand...
Click to collapse
I can't say I'm "working on it still" but whenever I have a need for it, I update it. I actually have the pixel 2 xl running latest oreo 8.1 and needed the added 5 GHz access points at work to have higher speeds (780 MBps beats 54 Mbps any day!)
Works fine here. Just make sure your xposed is working fine and that this module is loaded correctly. Reboot, profit. should work on all 8.1 ROMs given that I'm only modifying a simple framework method which should exist in all variants out there.
Hi,
thanks for the reply!
I have installed the latest Xposed, and your module (downloaded from there, not the file here) & rebooted. nothing happens. I do not see my 5GHZ when it's on the 148 and up band. When I switch it to the lower bands (38 and up) works just fine. this is driving me insane. Any chance you could help me out ?
In another post, someone offered me to replace a file, and that seemed to work for a bit, but now it has also stopped working
Link: https://forum.xda-developers.com/oneplus-5t/help/wifi-region-5ghz-question-5t-t3776003#post76220330
Thanks! appreciate any and all help.
Edit: Actually it would help to understand what it is exactly your addon is changing ? since the above file does have something that seems relevant. is this the same value being changed?
Amornik said:
Hi,
thanks for the reply!
I have installed the latest Xposed, and your module (downloaded from there, not the file here) & rebooted. nothing happens. I do not see my 5GHZ when it's on the 148 and up band. When I switch it to the lower bands (38 and up) works just fine. this is driving me insane. Any chance you could help me out ?
In another post, someone offered me to replace a file, and that seemed to work for a bit, but now it has also stopped working
Link: https://forum.xda-developers.com/oneplus-5t/help/wifi-region-5ghz-question-5t-t3776003#post76220330
Thanks! appreciate any and all help.
Edit: Actually it would help to understand what it is exactly your addon is changing ? since the above file does have something that seems relevant. is this the same value being changed?
Click to expand...
Click to collapse
Maybe use my file here instead? Not sure what's on the xposed modules repo.
madmack said:
Maybe use my file here instead? Not sure what's on the xposed modules repo.
Click to expand...
Click to collapse
Hi,
Thanks for the reply! I thought I had mentioned I already tried it, did not change anything.
Maybe if you told me which file this is editing and which value is being changed, I might be able to debug and see if it's actually changing the value it needs to.
Works fine on my xiaomi a1 !!! thx so much!!
madmack said:
I wrote this for myself but here it is in case anyone is also interested.
Google sets the wifi country code to whatever is in your sim card. If the country does not have a corresponding list of enabled 5GHz frequencies, then a lot of these frequencies get disabled. This mod simply sets the country code to US. There is no GUI or anything, just enable and restart and you're all set. Android marshmallow only. I tested it on my S7 edge and it's working fine.
Enjoy.
Edit: Added OREO 8.1 version. Testing working on Pixel 2 XL.
Click to expand...
Click to collapse
cleberjb said:
Works fine on my xiaomi a1 !!! thx so much!!
Click to expand...
Click to collapse
It would be great if you could specify which version of Android (8.0, 8.1) and which ROM (or stock).
thanks!
Amornik said:
It would be great if you could specify which version of Android (8.0, 8.1) and which ROM (or stock).
thanks!
Click to expand...
Click to collapse
Sorry my inconvenience. Works on Android 8.0 stock.
Amornik said:
Hi,
Thanks for the reply! I thought I had mentioned I already tried it, did not change anything.
Maybe if you told me which file this is editing and which value is being changed, I might be able to debug and see if it's actually changing the value it needs to.
Click to expand...
Click to collapse
Sure, editing method setCountryCode in com.android.server.wifi.WifiServiceImpl
Setting the parameter to US manually.
madmack said:
Sure, editing method setCountryCode in com.android.server.wifi.WifiServiceImpl
Setting the parameter to US manually.
Click to expand...
Click to collapse
Cool, thanks!
Just as a follow up..
1. is this com.android.server.wifi.wifiserviceimpl a file (.jar?)or db file?
2. where is it located?
3. does your fix change it every time on reboot? or is it a one time change? (meaning, does the phone update this from the SIM occasionally?)
thanks again!
Amornik said:
Cool, thanks!
Just as a follow up..
1. is this com.android.server.wifi.wifiserviceimpl a file (.jar?)or db file?
2. where is it located?
3. does your fix change it every time on reboot? or is it a one time change? (meaning, does the phone update this from the SIM occasionally?)
thanks again!
Click to expand...
Click to collapse
no man, it's a framework class that xposed can tap into and change the behavior. Take a look at the source code of Android AOSP for that class. it's not a simple file in /system that you modify. It is changed every time this method is invoked, it's how xposed works.
Lol, just goes to show how much I know about how rhis works, which is nothing
Its working with the update to 8.1 btw.
Thanks for all your work and patience!
Related
Hello,
I took the CM13 build from CN for the x720, removed all of the Chinese apps, and added the build.props to make it work correctly for the x727 version (single sim). Tested a bit and everything seems ok. Let me know if you find any issues or have any tweaks request.
Download: cm-13.0-20161219-UNOFFICIAL-lex727-zoid_003.zip
zoid_99 said:
Hello,
I took the CM13 build from CN for the x720, removed all of the Chinese apps, and added the build.props to make it work correctly for the x727 version (single sim). Tested a bit and everything seems ok. Let me know if you find any issues or have any tweaks request.
Download: cm-13.0-20161219-UNOFFICIAL-lex727-zoid_003.zip
Click to expand...
Click to collapse
Sweet I was having issues with build prop editing so I can try this tonight. Is the us modem corrected in here or do we still need to flash that seperately?
zmanfarlee said:
Sweet I was having issues with build prop editing so I can try this tonight. Is the us modem corrected in here or do we still need to flash that seperately?
Click to expand...
Click to collapse
The modem is not included in this package.
zoid_99 said:
The modem is not included in this package.
Click to expand...
Click to collapse
Thanks. Easy enough to flash anyways
I can't seem to get it to register a fingerprint. Is there something I did wrong? I installed the stock gapps, which replaces the some aosp apps with google ones.
robertzas said:
I can't seem to get it to register a fingerprint. Is there something I did wrong? I installed the stock gapps, which replaces the some aosp apps with google ones.
Click to expand...
Click to collapse
Yes it looks like I messed something up with the fingerprint scanner. I don't use the fingerprint scanner so I didn't test it. I'll see if the original CM13 fingerprint scanner and if so I should be able to fix it.
zoid_99 said:
Yes it looks like I messed something up with the fingerprint scanner. I don't use the fingerprint scanner so I didn't test it. I'll see if the original CM13 fingerprint scanner and if so I should be able to fix it.
Click to expand...
Click to collapse
Thanks! Otherwise been a great ROM so far, exactly what I've been looking for.
zoid_99 said:
Hello,
I took the CM13 build from CN for the x720, removed all of the Chinese apps, and added the build.props to make it work correctly for the x727 version (single sim). Tested a bit and everything seems ok. Let me know if you find any issues or have any tweaks request.
Download: cm-13.0-20161219-UNOFFICIAL-lex727-zoid_003.zip
Click to expand...
Click to collapse
great rom !! Can you build in the dual-APP, like the wechat avatar in the official ROM? Thanks!
One more suggestion: if it's not a big deal, you might as well allow the processor to get to its max speed for both big and little cores.
best post ever
zmanfarlee said:
Thanks. Easy enough to flash anyways
Click to expand...
Click to collapse
Can you tell me where I can find the modem zip file for band 12?
crookdbill said:
Can you tell me where I can find the modem zip file for band 12?
Click to expand...
Click to collapse
http://forum.xda-developers.com/le-pro3/how-to/flashing-guide-roundup-leeco-le-pro-3-t3511901
zmanfarlee said:
http://forum.xda-developers.com/le-pro3/how-to/flashing-guide-roundup-leeco-le-pro-3-t3511901
Click to expand...
Click to collapse
Thank you.
OK, so the fingerprint scanner is being a pain. I can't get the service to start on boot for some reason. I can get it to start after bootup and then it works ok. I'll keep toying with it.
Recently updated to build 137 on my BLA-L09, but now every time I take a picture and try open it in the gallery it constantly shows 'Loading...' with the actual picture dimmed out in the background.
Anyone facing the same issue?
Any solutions?
I also realised the picture doesn't actually save in the DCIM folder, however only the thumbnail saves in the DCIM>cache folder as a .tmp file.
wisemanwizz said:
Recently updated to build 137 on my BLA-L09, but now every time I take a picture and try open it in the gallery it constantly shows 'Loading...' with the actual picture dimmed out in the background.
Anyone facing the same issue?
Any solutions?
Click to expand...
Click to collapse
Are you using a custom kernel?
I am using the following custom kernel...
https://forum.xda-developers.com/mate-10/development/kernel-mate-10-mate-10-pro-stock-t3744501
wisemanwizz said:
Recently updated to build 137 on my BLA-L09, but now every time I take a picture and try open it in the gallery it constantly shows 'Loading...' with the actual picture dimmed out in the background.
Anyone facing the same issue?
Any solutions?
Click to expand...
Click to collapse
ante0 said:
Are you using a custom kernel?
Click to expand...
Click to collapse
wisemanwizz said:
I am using the following custom kernel...
https://forum.xda-developers.com/mate-10/development/kernel-mate-10-mate-10-pro-stock-t3744501
Click to expand...
Click to collapse
Mm. Huawei did something in B137. I will rebrand back to C432 and check later.
thanks man, i hope its fixable, it's actually quite annoying
ante0 said:
Mm. Huawei did something in B137. I will rebrand back to C432 and check later.
Click to expand...
Click to collapse
wisemanwizz said:
thanks man, i hope its fixable, it's actually quite annoying
Click to expand...
Click to collapse
Are you using B137 from 03-29 or 04-04?
It seems the latter is some test build, because it has the required files for Face Unlock (which probably is not enabled in Settings?).
I only did a diff so far on the 2 different B137 builds, but will have to flash to find out if it can be fixable.
I'm using the 04-04 version of the B137 update.
ante0 said:
Mm. Huawei did something in B137. I will rebrand back to C432 and check later.
Click to expand...
Click to collapse
ante0 said:
Are you using B137 from 03-29 or 04-04?
It seems the latter is some test build, because it has the required files for Face Unlock (which probably is not enabled in Settings?).
I only did a diff so far on the 2 different B137 builds, but will have to flash to find out if it can be fixable.
Click to expand...
Click to collapse
wisemanwizz said:
I'm using the 04-04 version of the B137 update.
Click to expand...
Click to collapse
I'm getting the same, one way to get camera back is simply to reflash but use B137 from 03.29. I have only had time to check what camera does briefly. It can't write to /sdcard/DCIM/ for some reason.
Face Unlock works btw, just need to set prop
ro.config.face_recognition=true
Can be done in build.prop or using a Magisk Module to set it at boot.
wisemanwizz said:
I'm using the 04-04 version of the B137 update.
Click to expand...
Click to collapse
It's fixed now. I will release a fix for this version in a couple of hours.
Huawei built kernel using different sources (V10 source it seems), where it uses a new/different vcodec for images.
I compared kernel configs from 4/4 B137 kernel to 3/29 B137 and it's different.
I first tried using the config from 4/4 but it wouldn't build with BLA source (Missing codec).
Then I checked 4/4 B137 config to Honor V10 sources config (It was a little different but codec was there), then built kernel and tested.
Wifi, BT and Camera works now.
That's great! Thank you so much! I look forward to testing it! :angel::angel::angel:
ante0 said:
It's fixed now. I will release a fix for this version in a couple of hours.
Huawei built kernel using different sources (V10 source it seems), where it uses a new/different vcodec for images.
I compared kernel configs from 4/4 B137 kernel to 3/29 B137 and it's different.
I first tried using the config from 4/4 but it wouldn't build with BLA source (Missing codec).
Then I checked 4/4 B137 config to Honor V10 sources config (It was a little different but codec was there), then built kernel and tested.
Wifi, BT and Camera works now.
Click to expand...
Click to collapse
wisemanwizz said:
That's great! Thank you so much! I look forward to testing it! :angel::angel::angel:
Click to expand...
Click to collapse
Here it is: https://mega.nz/#!ZD43wBxa!qPWTiOgcuafWUX1DzZd2RFVU-eZdSn71LFFlJR3Z7Ac
This will probably break camera on other builds (I've not tested).
If you want Face Unlock root is required, you can flash this Magisk module (if you use Magisk) https://mega.nz/#!5e4VSS4L!4vbZr0Pyzm39k2Ltcxi10gcFg_bcSlj7iLosK6SLKtM
Or add the prop manually to /product/etc/prop/local.prop
ro.config.face_recognition=true
The kernel works like a charm! Thanks!
For face unlock I tried to manually edit prop & then restart the phone, I am rooted but it is not working (I do not have Magisk) maybe I am doing something wrong.
Is there any specific place I have to put the "ro.config.face_recognition=true" within the prop file - i.e. should i just paste it right at the bottom of the prop file? And also where will the facial recognition option appear once it is enabled so I can confirm?
Sorry (I'm kind of a noob) I will probably try later. :angel::angel:
ante0 said:
Here it is: https://mega.nz/#!ZD43wBxa!qPWTiOgcuafWUX1DzZd2RFVU-eZdSn71LFFlJR3Z7Ac
This will probably break camera on other builds (I've not tested).
If you want Face Unlock root is required, you can flash this Magisk module (if you use Magisk) https://mega.nz/#!5e4VSS4L!4vbZr0Pyzm39k2Ltcxi10gcFg_bcSlj7iLosK6SLKtM
Or add the prop manually to /product/etc/prop/local.prop
ro.config.face_recognition=true
Click to expand...
Click to collapse
wisemanwizz said:
The kernel works like a charm! Thanks!
For face unlock I tried to manually edit prop & then restart the phone, I am rooted but it is not working (I do not have Magisk) maybe I am doing something wrong.
Is there any specific place I have to put the "ro.config.face_recognition=true" within the prop file - i.e. should i just paste it right at the bottom of the prop file? And also where will the facial recognition option appear once it is enabled so I can confirm?
Sorry (I'm kind of a noob) I will probably try later. :angel::angel:
Click to expand...
Click to collapse
After setting that prop, doesn't mater where so just place it at the bottom, reboot and then got to Settings - Security & Privacy, you should have the Face Unlock option. If you enroll your face you can unlock phone by using the power button and looking at screen. It unlocks instantly in most cases.
Also I noticed I failed at setting a custom string to kernel that would show in Settings - About - Kernel. But it just says Unavailable now. Don't worry about it if you were wondering.
Code:
If you encounter any errors during the installation process, feel free to report it to me.
Normally I test all the .zip Files before I upload them, so everything should work fine.
I Am Editing This File From 3 Weeks And Finally Created. I Created This Volte Module For Myself but after Hearing From Many Oneplus 3/3T Users Issues About Volte So I think To Share My Work.
Modified By Me: @jokerkill2r
Feel free to contact me on Telegram: @PurityNotHere
If You are Adding Or Sharing This Module Then Give Credit To Me And Share This Thread Link
Instructions:-
1. Flash The Custom ROM & Magisk
2. After Booting Open Magisk Manager
3. Flash The Fix File From Magisk
4. Enjoy!!! Check Your Volte Will Work
Code:
If You Like My Work Then Please Hit Thanks Button
Minor Information
ROM OS Version : 9.x Pie
Version Information
Status: Stable
Created : 2018-10-25
Download: Comment Down I will Give you the Module ( Admins/Mods Are Removing the link)
Hey bro great! can you please give me the link for module?
ssaikiran said:
Hey bro great! can you please give me the link for module?
Click to expand...
Click to collapse
https://www.mediafire.com/file/64mb...-OB_VoLTE-VoWiFi_Enabler_v1.0-signed.zip/file
This Is Not PPC LINK SO DON'T REMOVE IT
jokerkill2r said:
https://www.mediafire.com/file/64mb...-OB_VoLTE-VoWiFi_Enabler_v1.0-signed.zip/file
This Is Not PPC LINK SO DON'T REMOVE IT
Click to expand...
Click to collapse
1) Why don't you just upload to xda as an attachment?
2) Why do you use in thread name some sh*t letters instead of ASCII? With Google Product Sans font it does not render at all.
@jokerkill2r
Would this enable airtel/vodafone volte too or just jio volte ?
ayamstr said:
@jokerkill2r
Would this enable airtel/vodafone volte too or just jio volte ?
Click to expand...
Click to collapse
Try it ( 90% Chance's it will work)
I downloaded the file from the given link. But my Magisk isn't recognizing the file. Can you provide any alternative solutions? I'm using the latest version of Magisk 17.1
@jokerkill2r
If volte dosent works even after flashing this zip , how to revert back the to previous setup ?
ayamstr said:
@jokerkill2r
If volte dosent works even after flashing this zip , how to revert back the to previous setup ?
Click to expand...
Click to collapse
Just unchecked this module from magisk
Eeshan Bhave said:
I downloaded the file from the given link. But my Magisk isn't recognizing the file. Can you provide any alternative solutions? I'm using the latest version of Magisk 17.1
Click to expand...
Click to collapse
Try this one latest patched: https://www.mediafire.com/file/64mb...-OB_VoLTE-VoWiFi_Enabler_v1.0-signed.zip/file
przemcio510 said:
1) Why don't you just upload to xda as an attachment?
2) Why do you use in thread name some sh*t letters instead of ASCII? With Google Product Sans font it does not render at all.
Click to expand...
Click to collapse
Thanks for your advice I will keep it in mind
jokerkill2r said:
Try this one latest patched
Click to expand...
Click to collapse
This still doesn't work for me - also latest Magisk 17.1 and Magisk Manager. MM does not even see the file as something it can open.
EDIT: After renaming, everything worked without problem. Magisk Manager apparently expects naming convention like "<Name>-v<version>.zip". The zip by default has "-signed" at the end which seems to throw it off.
It is not working on my phone. I tried flashing latest firmware and build.prop code, both were a no-go.
Please help.
Thanks in advance.
Hey nice work
Can so please help me to get volte on op2
LucasBoy said:
This still doesn't work for me - also latest Magisk 17.1 and Magisk Manager. MM does not even see the file as something it can open.
EDIT: After renaming, everything worked without problem. Magisk Manager apparently expects naming convention like "<Name>-v<version>.zip". The zip by default has "-signed" at the end which seems to throw it off.
Click to expand...
Click to collapse
How do we rename it? In my file manager it's detected as a file not a zip file. i tried renaming it but no use.any ideas please...
[Edit]it installed fine after I removed the "-signed" part and changed its dir
But can anyone please say how to enable Airtel volte in my flydrqgon os
Can you try making one for OnePlus 2 too...
I flashed this on my OnePlus 3t an hour back, wondering if it would bring VoWifi, I cant confirm if VoWifi is working, As haven't noticed any VoWiFi or wifi calling while calling a few people, Though I have it enabled in settings.
But I can certainly say I am getting 4G+ on my phone, Which alteast i haven't ever noticed. I am testing for Speed on fast.com since then on irregular intervals, result is never noticed high speeds! I got 45, 29, 43, 46. 49, 26, 36, 39, 44 Mbps.
Will update again in a day, but this mod is worth it till now.
Thank You.
First of all READ THE WHOLE OP, PLEASE. Also pay attention to the "PS" at the bottom of this post.
(This post is still a work in progress)
WE NEED MORE TESTERS. Anybody with an A2017G and stock oreo(and the cam2 api patch below). Also more A2017U users on stock oreo need to help and test this.
Please report back if it works or not.
Requirements:
Selinux set to permissive (idk why but with enforced, ARcore doesn't work)
Camera 2 api is required. A2017G users need to flash this patch by @raystef66 https://androidfilehost.com/?fid=11410932744536993784
This won't be any simplified how to guide from me (more on that later).
Instead im gonna link 2 github issue posts which anyone with a little know-how about adb, sideloading/restore, root etc can follow to get ARcore working (reminder that it's also possible for non-rooted users).
First the main post
https://github.com/tomthecarrot/arcore-for-all/issues/139
IMPORTANT QUOTE and reason for not making a personal simple tutorial by myself (PAY ATTENTION TO THE LAST 2 SENTENCES PLEASE):
"Finally, we really only intended this mechanism for internal development use. We're mentioning it here because we see users super excited about running ARCore on additional devices, and agree that having to root your phone to do that is dumb. That said, we really only want to expose this to users already familiar with adb, side-loading, rooting, and the instability and wackyness that can arise from those things. Don't go out of your way to make it easy for novice users run ARCore on unsupported devices, and don't ask for support through official channels. If either of those start happening, we may have to cripple or remove this capability, and I think that's a loss for everyone involved."
What i think they are trying to prevent is "novice" users which don't know much about the matter in general, from flooding/spamming the official channels seeking for help. Also don't treat github as a forum. Don't ask the official devs for help. This is an UNSUPPORTED gift from the devs after all.
INSTEAD ask your questions here on this very xda thread and respect the official ARcore devs and the ARcore-for-all project. Thank you
I recommend reading through the whole github post as it's very informative on the matter and you might learn a thing or two.
Second post with instructions for rooted devices:
https://github.com/tomthecarrot/arcore-for-all/issues/139#issuecomment-466587565
For non-rooted users, please read through the github post. You need to know how to operate ADB restore properly.
Again, if you have any questions, ask here.
ARcore isn't working perfectly as of now since the calibration file we will be using isn't property tweaked yet (as the file itself was created for max compatibility for as many devices as possible). So let's work together, experiment with the values inside the calibration file (if you know how and what each value does, unlike me lol) and maybe, one day, we will have a proper, stable and smooth ARcore experience for our device.
Here is an example gif of me trying it out
https://thumbs.gfycat.com/GleefulShortBordercollie.webp (cant use IMG BB code to embed it into the post since its not in an actual gif format)
PS: i made this post on the phone and it's still a work in progress (especially now since xda labs messed up and only posted half of the OP for some reason). I plan to edit it later on pc for more clarity to make it visually easier and more appealing to read (currently sick, but i was so excited that i got ARcore working and really wanted to share it with you guys).
Since xda labs messed up with the post, some sentences are written differently than i originally intended. So i tried to fix it by re-writing the missing parts from memory and copy-pasting the whole text and posting it through the browser version of xda. So sorry if it is a little messy. All the more reason to edit it on pc later on xD.
Did everything the second post says to do for rooted users. Still a no go for me. When I load arcore measure it just flashes "acore keeps stopping"
Then it says ArCore is not able to run on this device.
What did you edit in your custom device profile?
Thanks bud
kountry83 said:
Did everything the second post says to do for rooted users. Still a no go for me. When I load arcore measure it just flashes "acore keeps stopping"
Then it says ArCore is not able to run on this device.
What did you edit in your custom device profile?
Thanks bud
Click to expand...
Click to collapse
I didn't edit anything yet since i have no idea what these values accomplish.
Do you have installed the camera2 api patch by @raystef66 ? Its needed, otherwise ARcore can't work. I edited OP and put the link to it at the top. (Totally forgot to add that this is the requirement)
Have you followed the steps exactly as they say? Quote: "Install the "arcore-modified-preview.apk" from*the "service-mod" branch*(it's linked in the README)"
See attached screenshot.
Download latest Arcore (from apmirror for example) and install that.
It doesn't have to be 1.7. You can just download the latest up to date version.
Follow the steps until he asks you to open the ARcore apk. What he now means by that is use any zip file viewer (i used rar for example) and with it open the official ARcore apk you downloaded (not the modified preview) and extract the textproto file from there.
Other than that i don't see any confusion coming from the rest of the instructions (renaming the file, putting it in the right folder etc)
GodOfPsychos said:
I didn't edit anything yet since i have no idea what these values accomplish.
Do you have the camera2 api patch installed by raystef66? This is necessary since it won't work without camera 2 api.
Have you followed the steps exactly as they say? Quote: "Install the "arcore-modified-preview.apk" from
Click to expand...
Click to collapse
I haven't installed raysteff66's camera2api patch but I have level_3 camera2 API and I went by the instructions you linked for rooted devices. I installed and modified everything it tells me to do.
P.s. I am using a ZTE Axon 7 A2017U on Oreo stock.
kountry83 said:
I haven't installed raysteff66's camera2api patch but I have level_3 camera2 API and I went by the instructions you linked for rooted devices. I installed and modified everything it tells me to do.
P.s. I am using a ZTE Axon 7 A2017U on Oreo stock.
Click to expand...
Click to collapse
Im sorry read my reply again, xda labs doesn't post my full replies for some odd reason so i used the browser version.
Also don't worry about the camera2 patch since you have an A2017U device. Its already camera2 api enabled
Added link of a demonstration gif to the OP
I'm running stock B20 Oreo and followed the instructions accurately. Do I need to clear the cache? I don't understand why it's crashing. I posted the screenshots of what I have.
kountry83 said:
I'm running stock B20 Oreo and followed the instructions accurately. Do I need to clear the cache? I don't understand why it's crashing. I posted the screenshots of what I have.
Click to expand...
Click to collapse
Hmm. Did you also set the permissions from the "files" folder as same as the others?
I didn't need to clear the cache and it worked for me.
@kountry83 if the "files" folder have the right permission and it still doesnt work. Could you maybe try a different camera ID?
Open the textproto file inside the files folder and edit the line camera_id: and change the 0 to 1.
Maybe this will do it.
See screenshot below
Maybe 0 is the front and 1 could be the back on the A2017U
GodOfPsychos said:
Hmm. Did you also set the permissions from the "files" folder as same as the others?
I didn't need to clear the cache and it worked for me.
Click to expand...
Click to collapse
/data/data/com.google.ar.core/files
My files folder is set to 2771 and the custom_device_profile.textproto file in the files folder is set to 644 permission.
kountry83 said:
/data/data/com.google.ar.core/files
My files folder is set to 2771 and the custom_device_profile.textproto file in the files folder is set to 644 permission.
Click to expand...
Click to collapse
My textproto file is set to 0666
We need more A2017G and U users with stock oreo to test ARcore. Please if any of you have already tested it and it works or not, please just say so in a reply and mention which device you used (G or U).
Edited OP as well to mention this
GodOfPsychos said:
We need more A2017G and U users with stock oreo to test this. Please if yoh have already tested it and it works or not, please just say so in a reply and mention which device you used (G or U)
Click to expand...
Click to collapse
Set the file to 0666. Still crashes with arcore measurement app. Even restarted and still crashes. What is your files folder permission?
Do you think you could make a flashible please with set permissions?
kountry83 said:
Set the file to 0666. Still crashes with arcore measurement app. Even restarted and still crashes. What is your files folder permission?
Do you think you could make a flashible please with set permissions?
Click to expand...
Click to collapse
My folder permission is the same as yours, 2771
Did you try changing camera ID as i mentioned in a previous post?
I tested the root method and it doesn't work as well. Probably need to tweak the custom_device_profile.textproto file
mickey36736 said:
I tested the root method and it doesn't work as well. Probably need to tweak the custom_device_profile.textproto file
Click to expand...
Click to collapse
Which device are you using? And which rom?
Also by "doesn't work as well" do you mean it doesn't work (crash) or its twitchy?
GodOfPsychos said:
Which device are you using? And which rom?
Also by "doesn't work as well" do you mean it doesn't work (crash) or its twitchy?
Click to expand...
Click to collapse
A2017G stock B01 with patch. I get with device not supportin mesure app.
Pokemon go also freeze the app when turn on ar+.
@GodOfPsychos changed camera ID to 1.
Same error, ArCore keeps stopping.
mickey36736 said:
A2017G stock B01 with patch. I get with device not supportin mesure app.
Pokemon go also freeze the app when turn on ar+.
Click to expand...
Click to collapse
Maybe its because you are still on the oreo beta. Im on b02
thank to derfelot he's a cool guy he help me a lot :good:
because of the nfc chip were different this cause kernel to wake or even random reboot
all you need to do is go to turn off nfc setting first [rooted need] go to
/vendor/lib/modules
and delete or rename file call pn553.ko
restart done
nfc will not work :good:
picture of cpu spy https://ibb.co/PjV135Z
Thanks for sharing! Previously i did try remove everything related nfc in /system which didn't work out for me, Now my SOV36 finally go deep sleep!
tq so much bro, its weird when phone run hotter
Does this also solves the random reboots?
yes nfc also cause reboot
my phone can't unlock bootloader . i cant't root
Been using this fix for 2 weeks on my SOV36 running Bliss ROM and I'm glad to say this resolved the random reboots.
I'm curious now, so in the original JP roms in the same /vendor/lib/modules, there are some files that got the same name as in any global and custom roms, but there's one file that's got "NFC" in the name, also has the .ko extension too. I wonder if we name that .ko file from the JP ROM to pn553.ko and put it in the global/custom roms, would NFC work? I haven't try it for myself lmao
you can't deferlot from xda said that chipset is different the only way is to build new kernel from source
ah that's a shame, but at least the random reboots are gone lmao thanks for the follow up!
Wangan_Beginner said:
ah that's a shame, but at least the random reboots are gone lmao thanks for the follow up!
Click to expand...
Click to collapse
I can have a crack at making a build for the Japanese variant with the correct kernel driver, but I don't know yet when I will have the time.
i7u
derf elot said:
I can have a crack at making a build for the Japanese variant with the correct kernel driver, but I don't know yet when I will have the time.
Click to expand...
Click to collapse
Damn it's the legend him/herself?? for real tho i personally rarely use the NFC (like, probably only twice a year, not that many place to use it in my country anyway lol) so I definitely not gonna push you to make it work, but I won't restrain you either lmao
derf elot said:
I can have a crack at making a build for the Japanese variant with the correct kernel driver, but I don't know yet when I will have the time.
Click to expand...
Click to collapse
how about if i debloat app NFC on /system/app/NfcNci/NfcNci.apk?
because i have ubl No, so i can't root my phone
is it solve a deep sleep problem?
charly.novianto said:
how about if i debloat app NFC on /system/app/NfcNci/NfcNci.apk?
because i have ubl No, so i can't root my phone
is it solve a deep sleep problem?
Click to expand...
Click to collapse
you can with temp root by j4nn
Hi everyone,
I've bought the same phone (SOV36 from AU), and I have the problem of reboots. I can't afford now a new phone, and I would like to know how to fix it... But I'm not expert. Would you be kind enough to explain me what I have to do exactly?
I've this build number (I don't know if it could be useful) : 47.2.A.11.228
Thank you so much in advantage.
Inviato dal mio G8341 utilizzando Tapatalk
TEK023 said:
thank to derfelot he's a cool guy he help me a lot :good:
because of the nfc chip were different this cause kernel to wake or even random reboot
all you need to do is go to turn off nfc setting first [rooted need] go to
/vendor/lib/modules
and delete or rename file call pn553.ko
restart done
nfc will not work :good:
picture of cpu spy https://ibb.co/PjV135Z
Click to expand...
Click to collapse
Can you please tell me how to root xperia Xz1
This file was not found in the modules directory of Android 11 system
jackeyloveno1 said:
This file was not found in the modules directory of Android 11 system
Click to expand...
Click to collapse
just flash this done :
(Shared) Updated POP-KERNEL (4.4.267) For G8431/2 and XZ1 AU
download (.267) 1 May 2021 **SOV36-AU NO NFC support download (.267) 1 may 2021 ***G431-G432 Download (.261) pixel 2 (kernel fork) 21 april 2021 Device still have heating ? : completely get rid of nfc files relate in vendor folder in root...
forum.xda-developers.com
Can I just replace all files related to the NFC?