Hi,
I am unable to use NFC on my smartphone since I installed LineageOS 15.1 on it. Although My smartphone supports NFC (I used it when I had the official ROM).
Can somebody help me activate NFC?
I have a Samsung J5 SM-J500FN with LineageOS 15.1. (latest currently).
There is no com.android.nfc on my phone. There used to be one before I installed LineageOS, but now it is not there.
I installed Google Apps Mini which includes "Google Tags (replaces stock/AOSP NFC Tags)"
Shell command service call nfc does not work, because nfc service does not exist
"svc nfc enable" responds "Got a null NfcAdapter, is the system running?"
I don't have any NFC toggle button in the status bar, nor in Settings.
This person says that NFC isn't supported on some phones for LineageOS 14.1, but there is no list of supported devices.
On the contrary, this page says that LineageOS 15.1 supports NFC (NFC is listed in the features - though it could be not implemented in all models, I have no details).
So, basically, if NFC is supported for my smartphone, I'd like to know how to enable the feature. If not, I'd like to see why - as the phone does have the hardware feature
Thanks!
Hey Im trying to figure out this too, I have the same Phone SM-J500FN which indeed does support NFC since I tried it and confirmed it when I installed Official ROM
Try looking on my Thread maybe you will learn some more about this LINK
Ok thanks! I've tried with LineageOS 16, and no NFC support either.
From your link, I understand you haven't been able to use NFC on your SM-J500FN with an custom ROM right?
Also see here: https://github.com/Galaxy-MSM8916/android_device_samsung_j5nlte/issues/1 - but no answer.
Related
I want to port/build IMS Manager for getting VoLTE feature on klte (LineageOS 14.1) but there is no guide on XDA, YouTube or even on google search... There are even VoLTE patches for Mi, Moto and Yu devices. Please help me to build it as I don't even know where to start after getting sources... Thanks in advance! ?
Update:
Found VoLTE rom for S5 (snapdragon variants) https://forum.xda-developers.com/galaxy-s5/development/rom-s7ux-pure-stock-t3505699
So you are aware IMS manager is that, a Manager, it doesn't effect your IMS functionality. Furthermore, LineageOS doesn't currently have native VoLTE functionality afaik. IMS manager is a samsung app for the samsung system, you'd better bug the Lineage Dev's for a tool for manipulating the IMS settings in LineageOS and more so bug them to implement VoLTE, however this comes at a risk as it can interfere with 911 Functionality and as such could pose libaility they wish to not deal with
Pls help him, I need VoLTE, too
If you need another similar to stock android 32 bit chip set ROM with ims manager, I could suggest you download wind7 ls 5016 firmware(snapdragon 210 with marshmallow). It might help you. Please try.
kvsjxd said:
I want to port/build IMS Manager for getting VoLTE feature on klte (LineageOS 14.1) but there is no guide on XDA, YouTube or even on google search... There are even VoLTE patches for Mi, Moto and Yu devices. Please help me to build it as I don't even know where to start after getting sources... Thanks in advance!
Click to expand...
Click to collapse
Bro you saw my above comment?
Have you made any progress on this? I've had a look at this in latest lineageos and on Galaxy s6. Though I think the basic idea is the same. The ImsManager is part of lineageos Rom. Though it needs a ims service. If that is not available even if you enable volte or WiFi calling over build.properties it will not work.
So to my (limited) knowledge, the first thing one would have to do is provide an implementation of that service. I think in Stock Galaxy s6 that is provided in imsservice.apk that comes in /system/priv-apps. I've attached the version of stock s6. Though I'm unable to use that since it's signature is not accepted and I'm neither able to decompile nor to resign /zipalign the package.
Any ideas? Or is this an all wrong way I'm following?
Br
Johannes
orgler said:
Have you made any progress on this? I've had a look at this in latest lineageos and on Galaxy s6. Though I think the basic idea is the same. The ImsManager is part of lineageos Rom. Though it needs a ims service. If that is not available even if you enable volte or WiFi calling over build.properties it will not work.
So to my (limited) knowledge, the first thing one would have to do is provide an implementation of that service. I think in Stock Galaxy s6 that is provided in imsservice.apk that comes in /system/priv-apps. I've attached the version of stock s6. Though I'm unable to use that since it's signature is not accepted and I'm neither able to decompile nor to resign /zipalign the package.
Any ideas? Or is this an all wrong way I'm following?
Br
Johannes
Click to expand...
Click to collapse
Some more ideas I've tested are described over there :
https://forum.xda-developers.com/galaxy-s6/orig-development/rom-lineageos-14-1-t3598775/post72465060
Found VoLTE rom for S5 (snapdragon variants) https://forum.xda-developers.com/galaxy-s5/development/rom-s7ux-pure-stock-t3505699
kvsjxd said:
Found VoLTE rom for S5 (snapdragon variants) https://forum.xda-developers.com/galaxy-s5/development/rom-s7ux-pure-stock-t3505699
Click to expand...
Click to collapse
Explain please.
西村大一 said:
Explain please.
Click to expand...
Click to collapse
I didn't had to port IMS Manager to lineageos or any rom. And instead I tested the above specified rom, it's for SM-G900F but I flashed it on SM-G900W8 and SM-G900T. After flashing and booting up for the first time, I got VoLTE running on both devices without even changing a setting. Keep in mind that the rom have 3 bugs, SystemUI crashes when you get a notification from WhatsApp, You cannot disable the lockscreen, If you change lockscreen from swipe to something else and lock the screen, you won't be able to unlock the device. Then you'll need to factory reset/flash the rom again or have to manually remove lock using TWRP. I am switching to a different operator next week, I am tired of the battle for VoLTE. Hope it helps.
@TheMadScientist Please close this thread.
Mod Edit
Thread closed at the request of the [OP]
malybru
Senior Moderator
Hello, everyone:
I have one problem for those AOSP ROM that I have flashed in Mi10Tpro - I can enable and disable NFC button in QuickSettings BUT NO FUNCTION AT ALL when phone close to bank card.( PE+/Evox/dotOS/Shapshift ... these ROM seems to have the common vendor - OSS vendor).
It looks like NFC is broken in OSS vendor because It works well when I returned Stock MIUI ROM.
Anyone has the same problem as mine ?
Well ... It's very interesting ... After I installing an app "easy NFC connect&Beam Send Files", it works ...
I can hear the sound and feel the vibration when making my phone close to a bank Card.
I have the same problem on newest pixel experience, I cant get it to work
Dear all LG G7 users, I would like to create this thread to discuss about ways of using LG G7 with all the basic features working and without Google Apps and Services.
I have a EU G7 with latest firmware and updates (Android 10) This is what I am looking for:
Working USB Tethering Hotspot and WiFi hotspot
Working Gcam
Working Bank Apps
Working microG
Good GPS signal
AOD - Always On Display (if possible)
DT2W - Double Tap to Wake (if possible)
I see there are a few ROMs like LineageOS 18.1, Dot 5, and others. But I am unsure of which one offers the stability I am looking for (not customization). It is ok to use Android 10.
I have downloaded the file from LG to unlock my bootloader, so I am ready my goal is to get rid of Google, and I am aware that with stock rom, even if I like it, it is not possible.
Thanks in advance for everyone who will join the discussion.
TheArt. said:
Dear all LG G7 users, I would like to create this thread to discuss about ways of using LG G7 with all the basic features working and without Google Apps and Services.
I have a EU G7 with latest firmware and updates (Android 10) This is what I am looking for:
Working USB Tethering Hotspot and WiFi hotspot
Working Gcam
Working Bank Apps
Working microG
Good GPS signal
AOD - Always On Display (if possible)
DT2W - Double Tap to Wake (if possible)
I see there are a few ROMs like LineageOS 18.1, Dot 5, and others. But I am unsure of which one offers the stability I am looking for (not customization). It is ok to use Android 10.
I have downloaded the file from LG to unlock my bootloader, so I am ready my goal is to get rid of Google, and I am aware that with stock rom, even if I like it, it is not possible.
Thanks in advance for everyone who will join the discussion.
Click to expand...
Click to collapse
dotos, also usb tethering won't work on any rom, unless you use pda net
EmanuelCN said:
dotos, also usb tethering won't work on any rom, unless you use pda net
Click to expand...
Click to collapse
I thought custom ROMs based on Android 11 did not have USB tethering. So not even Android 10 based custom ROMs have it? That's strange that a paid app like PDANET allows USB tethering
TheArt. said:
I thought custom ROMs based on Android 11 did not have USB tethering. So not even Android 10 based custom ROMs have it? That's strange that a paid app like PDANET allows USB tethering
Click to expand...
Click to collapse
Because the app itself allow it through their own method. its not using android's implementation. And no, not even android 10 roms have it working on g7
Hi there, I am still here, trying to find a way of minimizing the Google impact in the stock ROM.
Could someone please update me if a custom rom has USB tethering working? And if the answer is still a big NO, is there a way to debloat or degoogle the stock rom via unlocking bootloader and root? Ideally I would love to replace Play Services with microG, or at least remove Play Services while keeping the phone booting. Any advices are appreciated.
EDIT: seems like this is a viable option for me, anyone tried? : https://forum.xda-developers.com/t/guide-degoogle-any-device-and-install-microg.4058743/
For other searching here: I just installed AOSPK from Emanuel (telegram group) and it is Android 12 based. Here USB-Tethering works out of the box and the ROM does support signature spoofing so microg can be used right away.
As posted in other thread, i'm on latest crDroid (7.9) with Flamegapps full.
Pretty much everything working, except voice match "hey/ok google", whose activation is grayed out in google settings ("the function is not available on your device").
Searching the web, it seems that's a common problem for Android 11 custom roms, related to some file (hotword blobs) missing in the rom, device specific.
See this thread for example:
New Hotword blobs on Android 11 · Issue #19 · ShivamKumarJha/android_tools
Hotword functionality requires the following files on Android 11 system_ext/etc/permissions/com.android.hotwordenrollment.common.util.xml system_ext/framework/com.android.hotwordenrollment.common.u...
github.com
I'm no dev, so i don't really understand this stuff...but many people have my same problem here and on Telegram (the others simply doesn't use voice match, i guess), so i think it is good thing to report out this thing to developers, if this is the problem
thank you
I'm leaving this reply in case someone needs it in the future.
The solution is making Google a system app, you can use a magisk module called systemize.
This is the most recent version I found: https://github.com/xeddmc/terminal_systemizer
Cryn_058 said:
I'm leaving this reply in case someone needs it in the future.
The solution is making Google a system app, you can use a magisk module called systemize.
This is the most recent version I found: https://github.com/xeddmc/terminal_systemizer
Click to expand...
Click to collapse
Thank you very much for your replay.
That was the issue, and yours is a good solution.
For me, the issue has been solved with the next Flamegapps release, some time later.
i confirm on android 13 crdroid rom app 2023, nikgapps, Google must be installed as system app to google assistant working ( "and not be grayed out in google settings)
strachan said:
i confirm on android 13 crdroid rom app 2023, nikgapps, Google must be installed as system app to google assistant working ( "and not be grayed out in google settings)
Click to expand...
Click to collapse
System/app or system/priv-app??
Disclaimer
Your warranty will be void
Some carriers' Terms of Service prohibit device modifications
Modifying will trip Samsung Knox and SafetyNet, so be aware that some apps will cease to work
I AM NOT RESPONSIBLE FOR BRICKED DEVICES, FAILED ATTEMPTS AND OTHER CAUSES OF IMPROPER USAGE OF THIS GUIDE!Now that we got that out of the way, we can continue.
Unlocking the BootloaderUNLOCKING THE BOOTLOADER WILL ERASE ALL OF YOUR DATA!
Go into Settings > About Phone > Software Information
Find Build Number and quickly tap it 7 times. This will enable Developer Options
Find OEM Unlocking and USB Debugging options and enable them
Turn off the phone
Hold Volume Up and Volume Down while connecting your phone to a PC to boot into Download Mode
Read the Warning carefully to understand it and then if you want to continue press Volume Up
On the Unlock Bootloader screen, press and hold the Volume Up button one more time (This is the step that erases all of your data, if you don't want to do it, now is the time to turn back!)
After the automatic reboot, repeat steps 1. - 3. and make sure that OEM Unlocking is greyed out and enabled
Congratulations! You bootloader is now unlocked.
Flashing a Custom RecoveryCredit to @BlackMesa123 for this guide.
Rooting your Phone
Download the latest version of Magisk on your Computer
Follow the Official Installation Guide from Magisk developers
Flashing a GSI (Generic System Image)
Choose a GSI from this List
Power Off your phone and connect it to your Computer
Hold Volume Up and Power buttons, after the logo appears, release only the Power button, this will boot you into TWRP
Do a Wipe and transfer the GSI file from you Computer to your Phone
Click Install >Image Flashing, find your transferred GSI file and tap on it.
Toggle the System Image option and flash the file.
After flashing Format Data to be able to boot into your new System.
I know your Camera doesn't work, don't worry check out this Post to get it to work again.
Useful Resources
A52s bootloader/modem collection repository
OrangeFox Recovery
SafetyNet Fix for Magisk (Zygisk)
Custom ROMs: RayOS (One UI 4.1), NcX (One UI 5.0)
Mesa's Custom Kernel
Credit to @BlackMesa123 @Ryzen5950XT @ShaDisNX255 for the additional resources.
That's it! Thank you for following the guide and enjoy your unlocked Samsung.
This is very helpful thanks
Thank you for the guide. Here's some additional resources/changes that can be added in the post:
- A52s bootloader/modem collection repository
- OrangeFox Custom Recovery, same as TWRP but with a different UI
- SafetyNet and (some) Knox features can still work with the correct adjustments. See the SafetyNet fix for Magisk (Zygisk) or custom ROM's such as RayOS (One UI 4.1), NcX (One UI 5.0)
- Mesa's Custom Kernel, greatly improves device's performance
Hoping to see the list enhanced soon.
BlackMesa123 said:
Thank you for the guide. Here's some additional resources/changes that can be added in the post:
- A52s bootloader/modem collection repository
- OrangeFox Custom Recovery, same as TWRP but with a different UI
- SafetyNet and (some) Knox features can still work with the correct adjustments. See the SafetyNet fix for Magisk (Zygisk) or custom ROM's such as RayOS (One UI 4.1), NcX (One UI 5.0)
- Mesa's Custom Kernel, greatly improves device's performance
Hoping to see the list enhanced soon.
Click to expand...
Click to collapse
Thank you for the links, thread is now updated.
Quick question, with MCK, should I wipe everything before/after flashing and will it work with PE+ GSI?
kzyx said:
Thank you for the links, thread is now updated.
Quick question, with MCK, should I wipe everything before/after flashing and will it work with PE+ GSI?
Click to expand...
Click to collapse
You shouldn’t wipe anything when flashing the kernel. If the stock kernel works fine, I don’t see why mine shouldn’t
Everything is working perfectly, thanks for the guide. I installed the PixelExperience GSI but for some reason Fingerprint sensor is not working. The process is stuck on "Touch the sensor" and the sensor is not lighting up. Yes, I set the color of fingerprint sensor to White (and even tried all other colors).
I even have the following options checked
- Enable Extra Sensor
- Enable workaround for broken fingerprint sensor
- Enable workaround for white-ish screen
Any help will be appreciated, thanks.
Mian-786 said:
Everything is working perfectly, thanks for the guide. I installed the PixelExperience GSI but for some reason Fingerprint sensor is not working. The process is stuck on "Touch the sensor" and the sensor is not lighting up. Yes, I set the color of fingerprint sensor to White (and even tried all other colors).
I even have the following options checked
- Enable Extra Sensor
- Enable workaround for broken fingerprint sensor
- Enable workaround for white-ish screen
Any help will be appreciated, thanks.
Click to expand...
Click to collapse
I don't know what could be the issue, maybe try to google or try disabling and enabling the fingerprint lock again.
I have tried few GSI Roms. Here is my summary:
Android 13
- AOSP, Android 13, No image with GAPPs pre-installed and cannot seem to install it. Tried NikGAPPs, and LiteGAPPs, both didn't work
- Google GSI, Android 13, same issue
- Pixel Experience, Android 13, GAPPs pre-installed but Fingerprint sensor won't get detected.
Android 12
- AOSP, Android 12, GAPPs pre-installed, Fingerprint sensor detected (changing color to white). Will stick to it unless there is an issue detected.
Mian-786 said:
I have tried few GSI Roms. Here is my summary:
Android 13
- AOSP, Android 13, No image with GAPPs pre-installed and cannot seem to install it. Tried NikGAPPs, and LiteGAPPs, both didn't work
- Google GSI, Android 13, same issue
- Pixel Experience, Android 13, GAPPs pre-installed but Fingerprint sensor won't get detected.
Android 12
- AOSP, Android 12, GAPPs pre-installed, Fingerprint sensor detected (changing color to white). Will stick to it unless there is an issue detected.
Click to expand...
Click to collapse
Thanks for the feedback, have you tried any ROMs instead of GSIs?
You have links for them in this thread.
kzyx said:
Thanks for the feedback, have you tried any ROMs instead of GSIs?
You have links for them in this thread.
Click to expand...
Click to collapse
Nope, I tried to find a good custom rom for A52s but couldn't find any.
What about volte and hotspot on GSI pixel experience 13?
Mian-786 said:
I have tried few GSI Roms. Here is my summary:
Android 13
- AOSP, Android 13, No image with GAPPs pre-installed and cannot seem to install it. Tried NikGAPPs, and LiteGAPPs, both didn't work
- Google GSI, Android 13, same issue
- Pixel Experience, Android 13, GAPPs pre-installed but Fingerprint sensor won't get detected.
Android 12
- AOSP, Android 12, GAPPs pre-installed, Fingerprint sensor detected (changing color to white). Will stick to it unless there is an issue detected.
Click to expand...
Click to collapse
Thanks for your summary,
Is there any experience with MicroG on this device with AOSP 13?
7slaper said:
Thanks for your summary,
I'm on AOSP 13 now, but perhabs it's better to go back to 12. I'm very interested in the AOSP with the GAPPs pre-installed. Could you share a link to the file?
Click to expand...
Click to collapse
I got the image from AOSP under the official Android 12/12L section. You can find release here. The exact image I got is the system-squeak-arm64-ab-vndklite-gapps-secure.img.xz one since the standard gapps one came with an app called "superuser" which I couldn't seem to uninstall (I tried the scripts to remove supersu). This caused my banking apps to not run. That is why I installed the "secure" one and then installed Magisk and added my banking apps to the defylist.
Zhazhael said:
What about volte and hotspot on GSI pixel experience 13?
Click to expand...
Click to collapse
I think VoLTE was available as an option in one of the ROM I tested but I don't remember exactly. Currently AOSP 12 doesn't support it. Hotspot worked on every ROM just fine.
Mian-786 said:
I got the image from AOSP under the official Android 12/12L section. You can find release here. The exact image I got is the system-squeak-arm64-ab-vndklite-gapps-secure.img.xz one since the standard gapps one came with an app called "superuser" which I couldn't seem to uninstall (I tried the scripts to remove supersu). This caused my banking apps to not run. That is why I installed the "secure" one and then installed Magisk and added my banking apps to the defylist.
Click to expand...
Click to collapse
Hi Mian,
Thanks for your response. When I typed my question I realized that in the end I want to have and de-googled phone. So I changed my question in the direction of MicroG. I didn't expect you to be so quick with answering.
7slaper said:
Hi Mian,
Thanks for your response. When I typed my question I realized that in the end I want to have and de-googled phone. So I changed my question in the direction of MicroG. I didn't expect you to be so quick with answering.
Click to expand...
Click to collapse
I haven't tried MicroG in any of the ROM. I just to have as little Google apps as possible but if you do find a good guide, let me know, I will try to use a de-googled phone.
Thx, all worked.
Mian-786 said:
I haven't tried MicroG in any of the ROM. I just to have as little Google apps as possible but if you do find a good guide, let me know, I will try to use a de-googled phone.
Click to expand...
Click to collapse
I've installed MicroG. But it seems AOSP doen't allaw support system spoofs signature. Play services (GmsCore) is installed but without the spoofed signature it can't do much I guess...
I have been using AOSP Android 12 for the past week or so. Most of the things just plain works but somethings don't. Here is the list of things that are not working so you can decide if the hassle of installing GSI is worth it or not.
- Proximity Sensor is worse than it was in OneUI. Yes, it is a virtual sensor but on OneUI, it worked better. Now, it is worse. More often than not, it turns on the screen during the call. It would have been better if it simply didn't work.
- The viewport of default camera App in the AOSP displays picture in 4:3 but the camera hardware is giving out 16:9, so the viewport was squeezed. After installing GCam everything is good.
- Fingerprint Sensor simply doesn't work in-app like those in banking apps. It works on the lock screen but nowhere else.
- USB Audio Devices don't work. I have a USB-C to A OTG where I used to insert my headphones. On OneUI they used to work but here they don't. Storage devices work.
- 120 Hz felt smoother on OneUI.
Hello everyone
I managed to install LineageOS with working GApps and camera using this guide, so a big thanks to everyone who worked on flashing this phone
If anyone wants to install it, you need to:
Chose a bgN package (I installed this one : https://sourceforge.net/projects/an...UNOFFICIAL-arm64_bgN-vndklite.img.xz/download). It includes the GApps. You won't be able to install GApps after installing a vanilla (bvS / bvN) package. For some reasons, the /system partition is too small.
For unlocking camera and install magisk, just flash this kernel : https://forum.xda-developers.com/t/kernel-12-13-a528b-n-mesas-custom-kernel-r4.4490653/
I also installed magiskhide prop conf module, but I'm not sure it changed anything and the camera fix was probably already in the MCK. You can find it here anyway : https://forum.xda-developers.com/t/...safetynet-prop-edits-and-more-v6-1-2.3789228/