My friend just got this update. Can anyone confirm what it does?
Matej101 said:
My friend just got this update. Can anyone confirm what it does?
Click to expand...
Click to collapse
Security update
It appears to be only the security patch of June 1, 2018. I have not noticed any other changes.
I deodexed framework for signature spoof / microg. If interested, let me know, and I can post. Self-check in microg shows no nlp support, but location services working fine. Going to look into it more... Nanodroid Magisk module required for patching, (at least I couldn't do it any other way - maybe Haystack, if you're advanced. Tingle didn't work, and I don't think kernel will enable diy patching from venkat kamesh).
levone1 said:
I deodexed framework for signature spoof / microg. If interested, let me know, and I can post. Self-check in microg shows no nlp support, but location services working fine. Going to look into it more... Nanodroid Magisk module required for patching, (at least I couldn't do it any other way - maybe Haystack, if you're advanced. Tingle didn't work, and I don't think kernel will enable diy patching from venkat kamesh).
Click to expand...
Click to collapse
Hey I just wanted to let you know that the location services are working fine because com.qualcomm.location package is still currently hitting the google location servers. The com.qualcomm.location package is still the main location provider because the framework-res.apk specifies com.qualcomm.location as the location provider.
Your post prompted me to look into this a little further and I found that through an overlay "hack" we can adjust the framework-res values to allow Location Services for UnifiedNlp (built into MicroG now).
Additionally, after deodexing the framework (using Haystack) and applying the patch to framework-res-overlay, I built a magisk module to apply the necessary adjustments to framework-res, services.jar, framework.jar, ext.jar to support the Signature Spoofing & Location Services.
p.s. disable the com.qualcom.location package and see if your location services still work.
p.p.s i will open a new thread for the magisk module for stock version 34.4.A.2.85 Sig Spoof & Location Services Update
*edit: https://forum.xda-developers.com/x-...dule-signature-spoof-update-location-t3808521
JenItols said:
Hey I just wanted to let you know that the location services are working fine because com.qualcomm.location package is still currently hitting the google location servers. The com.qualcomm.location package is still the main location provider because the framework-res.apk specifies com.qualcomm.location as the location provider.
Your post prompted me to look into this a little further and I found that through an overlay "hack" we can adjust the framework-res values to allow Location Services for UnifiedNlp (built into MicroG now).
Additionally, after deodexing the framework (using Haystack) and applying the patch to framework-res-overlay, I built a magisk module to apply the necessary adjustments to framework-res, services.jar, framework.jar, ext.jar to support the Signature Spoofing & Location Services.
p.s. disable the com.qualcom.location package and see if your location services still work.
p.p.s i will open a new thread for the magisk module for stock version 34.4.A.2.85 Sig Spoof & Location Services Update
*edit: https://forum.xda-developers.com/x-...dule-signature-spoof-update-location-t3808521
Click to expand...
Click to collapse
Nice , thanks ... I already found out about location from microg devs, but wasn't sure what to do about it, except wait for Xposed.
levone1 said:
Nice , thanks ... I already found out about location from microg devs, but wasn't sure what to do about it, except wait for Xposed.
Click to expand...
Click to collapse
No problem. If you got signature spoofing then the only other relevant change is the change to framework-res resource values.
config_fusedLocationProviderPackageName
config_networkLocationProviderPackageName
config_comboNetworkLocationProvider
You can download the Magisk zip file and extract the ./system/vendor/overlay/framework-res-overlay.apk and push it to your device location /system/vendor/overlay. This will correct that issue for you since you have already added signature spoofing via a boot time Magisk module.
Of course you don't have to but I expect Xposed will take a while to get back up and running so this may be the only option till then.
I'm on CE1 firmware, which no longer seems to be receiving updates. Does anyone happen to know what the next best firmware to flash would be? US phone on TMobile.
RSakai said:
I'm on CE1 firmware, which no longer seems to be receiving updates. Does anyone happen to know what the next best firmware to flash would be? US phone on TMobile.
Click to expand...
Click to collapse
Customized US has latest...
RSakai said:
I'm on CE1 firmware, which no longer seems to be receiving updates. Does anyone happen to know what the next best firmware to flash would be? US phone on TMobile.
Click to expand...
Click to collapse
Depends whether you use the fingerprint sensor. If so, then don't switch to US firmware, where the sensor is deactivated. Perhaps try Customized UK or Customized DE, both on the latest version, ...85. The only thing I've noticed about not using the US firmware (on AT&T) is that certain kinds of group text messaging, and messaging with attached images, aren't available. May not apply to T-Mobile anyway.
levone1 said:
Customized US has latest...
Click to expand...
Click to collapse
pseudonym58 said:
Depends whether you use the fingerprint sensor. If so, then don't switch to US firmware, where the sensor is deactivated. Perhaps try Customized UK or Customized DE, both on the latest version, ...85. The only thing I've noticed about not using the US firmware (on AT&T) is that certain kinds of group text messaging, and messaging with attached images, aren't available. May not apply to T-Mobile anyway.
Click to expand...
Click to collapse
Thanks all, yep, moved to ce1 shortly after I got this thing almost two years ago for the fingerprint scanner, it's always been great (Outside of the general issues introduced with android 8). I figure after two updates appear to have fully rolled out, and other devices having received their ce1 updates, it's time to move to something current. DE seems to be a common recommendation, so I'll try rolling to that this weekend. Thanks again.
RSakai said:
Thanks all, yep, moved to ce1 shortly after I got this thing almost two years ago for the fingerprint scanner, it's always been great (Outside of the general issues introduced with android 8). I figure after two updates appear to have fully rolled out, and other devices having received their ce1 updates, it's time to move to something current. DE seems to be a common recommendation, so I'll try rolling to that this weekend. Thanks again.
Click to expand...
Click to collapse
Let me know how that goes. I am in the same boat as you with CE1. Was on UK but went to CE1 for "LTE", instead of "4G". Cosmetic, I know. Let me know how the DE goes and whether the data icon shows as "LTE", if you will.
Cheers.
delvirtud said:
Let me know how that goes. I am in the same boat as you with CE1. Was on UK but went to CE1 for "LTE", instead of "4G". Cosmetic, I know. Let me know how the DE goes and whether the data icon shows as "LTE", if you will.
Cheers.
Click to expand...
Click to collapse
DE shows LTE
ondrejvaroscak said:
DE shows LTE
Click to expand...
Click to collapse
Thanks. Just to confirm, this is the "Customized DE", correct?
delvirtud said:
Thanks. Just to confirm, this is the "Customized DE", correct?
Click to expand...
Click to collapse
Yes
Just thought I'd mention that many XC firmware variants have been updated to 34.4.A.2.97 (July 1, 2018 security patch).
https://xpericheck.com/device/F5321
Related
So I've made vendor blobs and gapps for shamu using 6.0.0(MRA58K) files. I'm posting them here incase anyone wants to help or make them work for your builds. I figure collaboration is always better than none.
vendor_motorola_shamu - GitHub
Google Apps (nodpi) - files.oceighty.co (WORKS)
There they are. Feel free to use them how you want to. I just ask you spread them around so we can get this going!
@xanaxdroid I've had success with the ROM booting up with these binaries but have had the issue where the SIM card isn't being recognized. Is the same problem happening to you as well?
JJD does apologizes, but he has to be that "guy". Please use the button to show your thanks to the OP, vice posting. Now if you have input into development, please do post........
Thread Cleaned.
zephiK said:
@xanaxdroid I've had success with the ROM booting up with these binaries but have had the issue where the SIM card isn't being recognized. Is the same problem happening to you as well?
Click to expand...
Click to collapse
There seems to be an issue no matter what blobs are used @zephiK
We pulled the binaries directly from Google and same thing happened. I tried using @xanaxdroid's blobs which btw don't match up with what Google put out and came up empty as well
Mazda said:
There seems to be an issue no matter what blobs are used @zephiK
We pulled the binaries directly from Google and same thing happened. I tried using @xanaxdroid's blobs which btw don't match up with what Google put out and came up empty as well
Click to expand...
Click to collapse
These are the binaries Google put out with the rest pulled from the shamu system image.
xanaxdroid said:
These are the binaries Google put out with the rest pulled from the shamu system image.
Click to expand...
Click to collapse
Gotcha, guess I'm just used to pulling them from Google not the actual image.
Anyways, going to troubleshoot this data/signal issue and see what I come up with
Let me know if you guys come up with anything, really don't care who fixes it as long as the result is the same
zephiK said:
@xanaxdroid I've had success with the ROM booting up with these binaries but have had the issue where the SIM card isn't being recognized. Is the same problem happening to you as well?
Click to expand...
Click to collapse
Same is happening to me as well.
Team Octos -Nexus 6
zephiK said:
@xanaxdroid I've had success with the ROM booting up with these binaries but have had the issue where the SIM card isn't being recognized. Is the same problem happening to you as well?
Click to expand...
Click to collapse
Yeah same thing. I pushed an update. Getting ready to try it again now.
I couldn't post on your g+ post @Mazda so came here, I haven't yet compiled(doing now) but I did notice that the blobs @zephiK & @xanaxdroid are using don't have alot of the radio related files, no wfc, and misc radio stack ones that I had figured out during 5.1.1 those helped immensely for fi and sprint, etc along with a number of radio related functions. Maybe those need to be used this go around?(Google doesn't supply these on their released blobs btw) I will let you guys know how it goes on my end when build finishes. Fingers crossed
Sent from my Nexus 6 using Tapatalk
BeansTown106 said:
I couldn't post on your g+ post @Mazda so came here, I haven't yet compiled(doing now) but I did notice that the blobs @zephiK & @xanaxdroid are using don't have alot of the radio related files, no wfc, and misc radio stack ones that I had figured out during 5.1.1 those helped immensely for fi and sprint, etc along with a number of radio related functions. Maybe those need to be used this go around?(Google doesn't supply these on their released blobs btw) I will let you guys know how it goes on my end when build finishes. Fingers crossed
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Just for clarification, the ones I used are the same ones from xanax so they're exactly identical as his.
zephiK said:
Just for clarification, the ones I used are the same ones from xanax so they're exactly identical as his.
Click to expand...
Click to collapse
I know, that's why I included you both in my comment. But you are missing all the wfc blobs, same with Google they only have really given us the "mandatory" blobs since the device was released. Not really sure why.. We had to source the ims and wfc ones ourselves previously from the factory images.
Edit: didn't something similar to this happen when volte was first introduced?
BeansTown106 said:
I know, that's why I included you both in my comment. But you are missing all the wfc blobs, same with Google they only have really given us the "mandatory" blobs since the device was released. Not really sure why.. We had to source the ims and wfc ones ourselves previously from the factory images.
Edit: didn't something similar to this happen when volte was first introduced?
Click to expand...
Click to collapse
Before they had different releases for different carriers. I used the binaries from Google and the system image to try and match the L release ones plus with newer files and files that had been removed. I don't remember about the VoLTE and WFC, but I just posted these as a starting point just in case someone knows what's missing they could post theirs and we can get on rolling and pushing out these builds.
BeansTown106 said:
I know, that's why I included you both in my comment. But you are missing all the wfc blobs, same with Google they only have really given us the "mandatory" blobs since the device was released. Not really sure why.. We had to source the ims and wfc ones ourselves previously from the factory images.
Edit: didn't something similar to this happen when volte was first introduced?
Click to expand...
Click to collapse
Currently, the baseband isn't being recognized. If I remembered correctly, when 5.1 came out the baseband was already recognized the only thing that didn't work was VoLTE which made the phone drop down to HSPA during a phone call. So on 5.1 blobs provided by Google, you could still have mobile/cellular data but on 6.0.x it doesn't.
Me and Sykopompos worked on this for quite awhile to get VoLTE working. I remembered in one of the batch of blobs we used, we had a SIM card problem and it was resolved by swapping several files from factory image.
I've also asked the question on the Android building Google group, if this is a flub or a new policy. I hope we'll get an answer soon.
Y'all remembered this commit right? https://github.com/CyanogenMod/andr...mmit/7b51319cb06ac99386ceba84d5aaee5a1c905937
jamieg71 said:
Y'all remembered this commit right? https://github.com/CyanogenMod/andr...mmit/7b51319cb06ac99386ceba84d5aaee5a1c905937
Click to expand...
Click to collapse
Yeah that was part of the initial bring up for a few of us
@xanaxdroid assuming the reason you removed SetupWizard from your 10/07 gapps was because of SetupWizard FCs reported on several devices, have you tried keeping setupwizard, and also adding GoogleTTS and libs to system/app to see if the FCs are gone? from logs i've seen, it looks like SetupWizard is crashing because of missing TTS. http://pastebin.com/nkdtkd7y
BeansTown106 said:
I know, that's why I included you both in my comment. But you are missing all the wfc blobs, same with Google they only have really given us the "mandatory" blobs since the device was released. Not really sure why.. We had to source the ims and wfc ones ourselves previously from the factory images.
Edit: didn't something similar to this happen when volte was first introduced?
Click to expand...
Click to collapse
How did your build work out Beans? Any luck?
Team Octos -Nexus 6
dankoman said:
@xanaxdroid assuming the reason you removed SetupWizard from your 10/07 gapps was because of SetupWizard FCs reported on several devices, have you tried keeping setupwizard, and also adding GoogleTTS and libs to system/app to see if the FCs are gone? from logs i've seen, it looks like SetupWizard is crashing because of missing TTS. http://pastebin.com/nkdtkd7y
Click to expand...
Click to collapse
That was the reason. I'll give it another go today using Google TTS. Thanks
Radio logs are crying for a libxml2.so, which is apparently related to RILD. Pull libxml2.so and push to system/lib and pray for results
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!
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.
Hi all,
I just modified the module from @snowwolf725 to have a newer template so it can run on oreo rom
If you need to use nfc-sim on oneplus 3/3t you could try this module.
[Install]
1. Get Magisk
2. In the download area search for "OnePlus 3/t NFC Sim Enabler"
3. Reboot
4. If your manage app require permission you can give it at settings-apps-app permissions-additional permissions, toggle smartcardservice for it
I only test it on OOS Oreo ROM, it may not work on custom rom due to different framework built in.
You can report here so I'll check what other MOD have to add to make other ROM work.
the smartcardservice is modified from SEEK for Android by Johnzweng
Repo link
crazymika said:
Hi all,
I just modified the module from @snowwolf725 to have a newer template so it can run on oreo rom
If you need to use nfc-sim on oneplus 3/3t you could try this module.
[Install]
1. Get Magisk
2. In the download area search for "OnePlus 3/t NFC Sim Enabler"
3. Reboot
4. If your manage app require permission you can give it at settings-apps-app permissions-additional permissions, toggle smartcardservice for it
I only test it on OOS Oreo ROM, it may not work on custom rom due to different framework built in.
You can report here so I'll check what other MOD have to add to make other ROM work.
the smartcardservice is modified from SEEK for Android by Johnzweng
Repo link
Click to expand...
Click to collapse
Any chance that this mod used on htc m9 with aicp 13.1, rooted with magisk?
tombbb said:
Any chance that this mod used on htc m9 with aicp 13.1, rooted with magisk?
Click to expand...
Click to collapse
I don't think so, it's NFC chip specified so if you have a different device it's xml config would be different.
For m9 you could look through it's stock rom to adjust configuration, I believe the M9 stock ROM support NFC-SIM card.
What does nfc sim means?
prasant737 said:
What does nfc sim means?
Click to expand...
Click to collapse
In some places we have our payment/transportation card integrated in SIM card.
so we can use our phone to pay/take public transportation.
hi sir able to update it for oneplus 6t android pie?
laocheebye said:
hi sir able to update it for oneplus 6t android pie?
Click to expand...
Click to collapse
according your ID I assume you are Taiwanese, there is modification for oneplus 6 on mobile01, i think that will also work for 6t
I didn't have 6t so I can't test on it.
crazymika said:
according your ID I assume you are Taiwanese, there is modification for oneplus 6 on mobile01, i think that will also work for 6t
I didn't have 6t so I can't test on it.
Click to expand...
Click to collapse
i am singaporean actually. can u link me the thread? i can read chinese so its fine. thank you deep deep.
---------- Post added at 02:27 PM ---------- Previous post was at 02:12 PM ----------
i found the thread and the download link if anyone is interested to try for oneplus 6 or 6t.
forum link in chinese
flashable zip
i havent tried cos there is no decrypt twrp for 6t yet so at your own risk people.
I had asked about it to the author directly on github since since my test are not successful. No update since then...
https://github.com/Magisk-Modules-Repo/oneplus3simnfc/issues/2
NoobZik said:
I had asked about it to the author directly on github since since my test are not successful. No update since then...
https://github.com/Magisk-Modules-Repo/oneplus3simnfc/issues/2
Click to expand...
Click to collapse
I'll update this to pie compatible when oos pie released
crazymika said:
I'll update this to pie compatible when oos pie released
Click to expand...
Click to collapse
Hello, any news ?
Hi, just tried the latest v1.2.1, but it seems HamiPay detects root even MagiskHide enabled for it. Would you please share how to prevent HamiPay from detecting root? Thank you.
jekyll530 said:
Hi, just tried the latest v1.2.1, but it seems HamiPay detects root even MagiskHide enabled for it. Would you please share how to prevent HamiPay from detecting root? Thank you.
Click to expand...
Click to collapse
I think they changed the root detection, now it's can only use with iPASS, EasyCard or icash.
Creditcard function have been lock with rooted devices.
crazymika said:
I think they changed the root detection, now it's can only use with iPASS, EasyCard or icash.
Creditcard function have been lock with rooted devices.
Click to expand...
Click to collapse
Thank you for replying. The above seems work fine. Can this module be ported for OP5/T, 6/T (OOS 9.0) or even 7/Pro?
Cuvillier said:
Hello, any news ?
Click to expand...
Click to collapse
I've update to Pie rom, and confirm that we still can use sim NFC at it, just need some path adjustments, use the attached zip file replace your system/vendor/etc/libnfc-nxp.conf, put the SmartcardService folder in system/priv-app folder
add this line "persist.nfc.smartcard.config=SIM1,eSE1" in system/build.prop file, and should work as before.
I forgot how to make it into proper Magisk Module~the module i made tonight can't not be installed.... so strange. I'll update once i get it to work.
P.S.
I tried custom ROMs, they have many differences about NFC config, I can not get it to work even replace the framework and permission file, tried everything I know but still failed, maybe they missed something at more lower level.
updated for OOS Pie
I just found what's wrong.
Here's the updated Module for OOS Pie.
Later i'll update to Modules-Repo
jekyll530 said:
Thank you for replying. The above seems work fine. Can this module be ported for OP5/T, 6/T (OOS 9.0) or even 7/Pro?
Click to expand...
Click to collapse
@snowwolf725 have created the OP5 module, 6/6t have other method to make it working,but I need check some of it's file to make sure, op7 should work in theory, but it still depend on some rom configuration. I only have a op3t, do don't know how other models work.
Currently OOS have proper components (driver, config, frameworks...) installed, so it easier to enable them, for custom rom or future builds(which OP3 won't have)
I believe that require more adjustments to have this feature working.
crazymika said:
@snowwolf725 have created the OP5 module, 6/6t have other method to make it working,but I need check some of it's file to make sure, op7 should work in theory, but it still depend on some rom configuration. I only have a op3t, do don't know how other models work.
Currently OOS have proper components (driver, config, frameworks...) installed, so it easier to enable them, for custom rom or future builds(which OP3 won't have)
I believe that require more adjustments to have this feature working.
Click to expand...
Click to collapse
The OP5/T module is not available via Magisk download now. I'm currently using OP5 and will buy a 7 Pro. If you need, I can help testing.
crazymika said:
@snowwolf725 have created the OP5 module, 6/6t have other method to make it working,but I need check some of it's file to make sure, op7 should work in theory, but it still depend on some rom configuration. I only have a op3t, do don't know how other models work.
Currently OOS have proper components (driver, config, frameworks...) installed, so it easier to enable them, for custom rom or future builds(which OP3 won't have)
I believe that require more adjustments to have this feature working.
Click to expand...
Click to collapse
thanks but it doesn't work on lineage os 16. in logcat i get keymaster operation failed and unsupported digest on km1 hal issue. i hope you can fix it
regards
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