Hey everyone,
I know, there are a lot of similar threads, but most of them are device specific.
I'm looking for a way to read NFC tags when the screen of my phone is off. I tried the Xposed module called "NFC LockScreenOff Enabler" on my OnePlus 3T running LineageOS 16 with Magisk, Riru Core and EdXposed, but it's somewhat unstable. Sometimes, the phone reads NFC tags while the screen is off, sometimes it doesn't. Moreover, my phone becomes unresponsive after a short time. Apps take ages to start, even the settings won't show for minutes... My brother tried the module on his Samsung Galaxy S4 Mini (GT-I9195I) running LineageOS 14.1 with the original Xposed-Framework by Rovo89. His phone doesn't read the tags at all while the screen is off (and yes, both of us changed the settings of the module to read tags with screen off), although, his phone doesn't become unresponsive.
Since the modules last update was 2014 and I guess it's not compatible with newer Android versions, I wanted to ask if anyone has an idea how to keep NFC alive even when the phone screen is off?
There are tutorials on how to mod the NfcNci.apk, but they are all for Android versions 5 or 6 :/
Hi,
I am using cards emulator (playstore), which needs root and xposed.
Having this app enabled in xposed allows to activate "enable nfc when screen is off" option.
This app is designed to emulate cards, but that option to enable nfc while screen is off might work for you, just try it out.
I am using the paid version of this app as i need it, works well on my pixel 3 xl on latest android 9.
Related
Hello,
Can "Scheduled Power OFF/ON" feature be added into the future builds(LineageOS 14.1)?
I would be happy if Lineage builds get this awesome feature!
There are some third party apps (like automate) which are only capable of switching OFF the device, not capable of turning it back ON......so I request LineageOS team to work on this feature.:good:
Thanks in advance!
Eagerly waiting for this feature...
Sent from my Asus Zenfone 2( Z00A) running Official lineageOS 14.1 builds.
The thing is that this was removed from devices after it was found not to really turn the device off completely. Which makes complete sense as if it is completely off then there is no way to turn it back on.
zelendel said:
The thing is that this was removed from devices after it was found not to really turn the device off completely. Which makes complete sense as if it is completely off then there is no way to turn it back on.
Click to expand...
Click to collapse
On older removable battery Chinese phones when this feature was there, the scheduled power on/off times and dates were the same when the battery was replaced, whether immediately or later (not sure about how much later).
But miui has this feature and it works great on MIUI
Zelendel, kindly point to the commit that was removing the feature.
I would like to try restoring it back for myself.
And what is the programmatic method the app was working? Are you saying that was just enabling airplane mode and switching screen off?
Pretty much that is all it was doing. It was leaving the internet hardware on.
As for the commit. You may not find it. It is not part of the open source android. It is closed sourced and not even really seen anymore on major devices. Most Chinese devices use it as a way to send data back to China when the user doesn't think anything is happening.
i am waiting for solution too.
I think you can make your phone life longer by keeping it off 8 hours a day.
I think that some phones have that hardware ability and some don't. PCs have this ability too.
I own a Xiaomi Redmi Note 7 running on unofficial Lineage OS 17. This feature is partially implemented now.
I set on an alarm.
I power off my phone.
The phone powers up when the alarm goes off. This works only if the alarm is set 5 or more minutes ahead from the time you power off.
As this works flawlessly, it should be pretty easy to add an "Automatic/Scheduled turn On/Off" in the phone settings.
I'm using crontab to automatically turning the phone off at 1 am. The problem is that if I'm still awake and using the phone at that time, it does not warn me. It just turns off. A feature in the phone settings would allow me to abort right before turning of.
If anybody is interested to know the graceful poweroff command, this is my cron tab line
Code:
00 1 * * * am start -a com.android.internal.intent.action.REQUEST_SHUTDOWN
Hi Guys,
I've been having a real hard time with this phone, I am sitting on the MIUI 10 stable global rom at the moment and I was wondering if you guys turn off MIUI optimization at all (in the developer settings) I'm not entirely sure what it does, but toggling it wipes out alot of permissions.
I've got 2 big issues with this phone. the Video Chat mic bug (Which I have seemed to get around by using WhatsApp for video chats)
The other being Android Auto not connecting all the time. I was wondering if maybe because this MIUI optimization is like a task killer that keeps killing stuff in the background?
When I need Android Auto to work, all I have to do is toggle USB Debugging and it fires up right away. Very strange, but it works for now.
Side Note for Xiaomi, Why do you need to lock down the phones like this? Android memory management works great, please don't mess with it. I just don't understand why we have these extra layers of security and permissions. It really messes with any third party apps, what an ordeal it is to get notifications working for example on any third part texting app. I have to go into like 3 different areas and then only sometimes it works. Please leave android alone, it works fine the way it is
I just turned them off. I guess we'll see how it goes.
Running lineageOS 17 on a xiaomi mi 9 lite, loving it, but i made a mistake.
I have my phone rooted and have been messing around with edxposed and magisk and i was trying to see if i could enable some sort of face unlock feature through a mod. found one called hidden settings and i started poking around, and i tried to change the value of this one called "lockscreen.options=enable_facelock" through the terminal, hoping it would enable a face recognition header in the settings somewhere, but instead, it had a very strange effect. first, that string no longer exists in android secure settings on my phone, and second, now my phone will not lock through normal means. using the power button, waiting for timeout, nothing, as soon as i wake the screen, the padlock icon is already open and the screen swipes itself up and goes to my unlocked home screen as though it had recognized my face and unlocked itself...only it didn't, because even trying this with my thumb over the camera has the same result.
anyway, i don't know what to do, but i need my phone to lock. so far the only thing ive tried that works is to use the lockdown mode button in my power menu, but that's a hassle. anyway, any help would be appreciated, my goal is to avoid a factory reset as well.
thanks in advance
Sorry, unofficial lineageOS 17 and magisk and edexposed. That is a highly experimental setup. You should be aware, there you have to start from scratch at some point. Be happy, if it's enough to wipe system and data. Others flash stock ROM to fix things.
kurtn said:
Sorry, unofficial lineageOS 17 and magisk and edexposed. That is a highly experimental setup. You should be aware, there you have to start from scratch at some point. Be happy, if it's enough to wipe system and data. Others flash stock ROM to fix things.
Click to expand...
Click to collapse
actually it was simpler than I thought...turns out nothing was broken at all. in fact one element was functioning better than i expected it to. a while back i was messing around on my previous phone, a rooted oneplus 5 running resurrection remix, and i started fiddling with tasker...anyway, at some point i had issues with the native smart lock features so i set a profile in tasker to unlock the phone when the screen turns on as long as i am connected to my home wifi network. apparently when i restored all my apps to the new phone through my google account it saved a ghost of that profile...i didn't catch it because it wasn't listed in the tasker interface, so i assumed none of my old automations had transferred. i figured it out when other old profiles started to activate, and eventually i remembered that i hadn't set any of that stuff up on this phone yet :victory::laugh:
in any case, thank you for the input...to be honest i would rather have a less experimental setup, but the mi 9 lite doesn't have much development yet so i'm choosing the best from what is available.
Hi!, I really need help with this:
I have 4 xiaomi phones, redmi note 3, 6 pro, 7, and 8... The xiaomi redmi note 8 have a problem, while Im spoofing and let the spoofing app, all the others phones, with almost the same setup (twrp, magisk, gps josytick, SmaliPatcher),they work fine with my go-tcha (is like a fitness divice to track walk, but is made for the game pokemon go), every phone have one go-tcha. The phones work fine with the screen off, the game pokemon go auto walk fine, adding steps to my phone and some other functions. Redmi Note 8, stop autowlaking with the screen off, and I tried MIUI rom and now HavocOs, and is the same, screen off and bye, no more auto walk. Why this happend? why is not working like my other 3 phones? I use this for 4 months and the redmi note 8, I bought it 1 week ago, I cant find a way to make it work with the screen off. Most off ppl use the device gotcha with the screen off and spoofing app to work while we are bussy or to not waste the battery by keeping the screen on (it work with the game opened or not, it keep working in the home screen with the game in the background), so why it dont work with the screen off?.
The game seems to keep working in the place, not moving, like auto walk stopped by I dont know what, and doing things with out lossing the signal of the fake gps / spoofing.
After talking with the maker of gps joystick, he said:
"Unfortunately I don't know either, my best guess is that the manufacturer of that phone may have implemented more stricter battery saving mode, which turns off GPS when screen is off or something like that"
Hi all,
Just asking a big favour really, as nothing else comes close to the specs I want I'd like to purchase a poco f5 again once these three issues are fixed:
Pocket mode not working
Memory management closing apps after a little while (despite being locked, set not to close, no power restrictions etc). Even play music app was being killed and Chromecast controls constantly...
Notifications delayed massively again despite the same changes as above point. 15-20+ minute delays.
Ps. I tried debloating and changing every setting I could find. I believe issue is due to MIUI powerkeeper dameon but removing that removes ability to set battery saving on apps at all.
Many thanks in advance.
LaurenceGough said:
Hi all,
Just asking a big favour really, as nothing else comes close to the specs I want I'd like to purchase a poco f5 again once these three issues are fixed:
Pocket mode not working
Memory management closing apps after a little while (despite being locked, set not to close, no power restrictions etc). Even play music app was being killed and Chromecast controls constantly...
Notifications delayed massively again despite the same changes as above point. 15-20+ minute delays.
Ps. I tried debloating and changing every setting I could find. I believe issue is due to MIUI powerkeeper dameon but removing that removes ability to set battery saving on apps at all.
Many thanks in advance.
Click to expand...
Click to collapse
And where did you experience all of those?
1. Pocket mode in recent Xiaomi devices are might not correctly working because of virtual proximity sensor I believe, cmiiw.
2. If you tried to keep a lot of apps running, of course some might have to be killed or put in a sleep state. You can't keep all the apps keep running in background.
3. This is the direct result from point above. Do note, apps use various method of receiving notifications, some rely on google service (mostly google apps, I believe this is most battery friendly way) while some manage the notifications themselves (this requires the app to be kept running in background, or occasionally given a queue by OS+kernel to be awaken periodically to receive the notifications)
tl;dr: if you want every apps to be as responsive as possible, you have to have a bigger ram and non stop power supply (not running in a battery)
x3r0.13urn said:
And where did you experience all of those?
1. Pocket mode in recent Xiaomi devices are might not correctly working because of virtual proximity sensor I believe, cmiiw.
2. If you tried to keep a lot of apps running, of course some might have to be killed or put in a sleep state. You can't keep all the apps keep running in background.
3. This is the direct result from point above. Do note, apps use various method of receiving notifications, some rely on google service (mostly google apps, I believe this is most battery friendly way) while some manage the notifications themselves (this requires the app to be kept running in background, or occasionally given a queue by OS+kernel to be awaken periodically to receive the notifications)
tl;dr: if you want every apps to be as responsive as possible, you have to have a bigger ram and non stop power supply (not running in a battery)
Click to expand...
Click to collapse
I appreciate your help but this phone does have a proper proximity sensor, it's just not used in the software correctly for some reason. HW tests pass ok . I wouldn't have purchased this phone otherwise, I've had the misfortune of owning devices with the virtual one... Ugh... Never again.
Understood but the 12GB is not being fully used. If you remove power restrictions from these apps they should remain in memory and running in the cached / background state. Xiaomi powerkeeper which is in addition to the stock Android ROM appears to be closing apps regardless. All xiaomi cleaning or clearing options are disabled.
Indeed the applications in question are using Google's cloud messaging notification systems and it isn't an issue on aosp based ROMs on other phones even others in the house at the same time on the same network (doze active or not), but these custom ROMs aren't available for this phone yet.
I'd have probably kept it if the pocket mode worked but I draw the line at my phone dialing emergency numbers when locked in my pocket which happened within two days of ownership. In testing pocket mode didn't work correctly at all, seems others have the same problem.
Thanks though
LaurenceGough said:
I appreciate your help but this phone does have a proper proximity sensor, it's just not used in the software correctly for some reason. HW tests pass ok . I wouldn't have purchased this phone otherwise, I've had the misfortune of owning devices with the virtual one... Ugh... Never again.
Understood but the 12GB is not being fully used. If you remove power restrictions from these apps they should remain in memory and running in the cached / background state. Xiaomi powerkeeper which is in addition to the stock Android ROM appears to be closing apps regardless. All xiaomi cleaning or clearing options are disabled.
Indeed the applications in question are using Google's cloud messaging notification systems and it isn't an issue on aosp based ROMs on other phones even others in the house at the same time on the same network (doze active or not), but these custom ROMs aren't available for this phone yet.
I'd have probably kept it if the pocket mode worked but I draw the line at my phone dialing emergency numbers when locked in my pocket which happened within two days of ownership. In testing pocket mode didn't work correctly at all, seems others have the same problem.
Thanks though
Click to expand...
Click to collapse
Regarding about the proximity sensor, I need a confirmation from any owner of this device because it's failed to be mentioned by any reviews. Though elliptic labs didn't mention any Poco F5 and GSMArena might not properly mentioned it (their site mentioned Poco F4 not having a virtual one, while it does use one). Elliptic labs isn't the only one that supply such technology too. Please take a look in an app such "device info hw", see if it's reported as elliptic labs or Xiaomi sensor.
You could try Xiaomi.eu rom if you have already unlocked, though doubtful it will resolve the issue. Or you could try turning off MIUI optimization to see if that can turn off the aggressive doze on google service.
x3r0.13urn said:
Regarding about the proximity sensor, I need a confirmation from any owner of this device because it's failed to be mentioned by any reviews. Though elliptic labs didn't mention any Poco F5 and GSMArena might not properly mentioned it (their site mentioned Poco F4 not having a virtual one, while it does use one). Elliptic labs isn't the only one that supply such technology too. Please take a look in an app such "device info hw", see if it's reported as elliptic labs or Xiaomi sensor.
You could try Xiaomi.eu rom if you have already unlocked, though doubtful it will resolve the issue. Or you could try turning off MIUI optimization to see if that can turn off the aggressive doze on google service.
Click to expand...
Click to collapse
The phone got real proximity sensor. Verified by waving hands over the sensor and placing the phone stationary. The position of the sensor is in top right corner where the signals are shown in ui.
ThanveerAliSayed said:
The phone got real proximity sensor. Verified by waving hands over the sensor and placing the phone stationary. The position of the sensor is in top right corner where the signals are shown in ui.
Click to expand...
Click to collapse
An easier way to check for the future is just to use another camera to check for emitted IR light when the screen is turned on.
LaurenceGough said:
Hi all,
Just asking a big favour really, as nothing else comes close to the specs I want I'd like to purchase a poco f5 again once these three issues are fixed:
Pocket mode not working
Memory management closing apps after a little while (despite being locked, set not to close, no power restrictions etc). Even play music app was being killed and Chromecast controls constantly...
Notifications delayed massively again despite the same changes as above point. 15-20+ minute delays.
Ps. I tried debloating and changing every setting I could find. I believe issue is due to MIUI powerkeeper dameon but removing that removes ability to set battery saving on apps at all.
Many thanks in advance.
Click to expand...
Click to collapse
I have the chines' model .
for notification : just disable com.miui.powerkeeper by typing the below in CMD command ( plz search for method)
pm disable-user --user 0 com.miui.powerkeeper
and you will receive the notification instantly for all apps .
Note: make sure to unoptimized the apps from battery optimization
LaurenceGough said:
An easier way to check for the future is just to use another camera to check for emitted IR light when the screen is turned on.
Click to expand...
Click to collapse
I wonder if the Note 12 Turbo has the same problem. That had been out for quite a few months before this phone... I see the Note 12 Turbo Chinese firmware just had an update today.
fal4fal said:
I have the chines' model .
for notification : just disable com.miui.powerkeeper by typing the below in CMD command ( plz search for method)
pm disable-user --user 0 com.miui.powerkeeper
and you will receive the notification instantly for all apps .
Note: make sure to unoptimized the apps from battery optimization
Click to expand...
Click to collapse
Indeed I think this is the problem, I did pop this in my first post " I believe issue is due to MIUI powerkeeper daemon but removing that removes ability to set battery saving on apps at all.".
So yeah, it prevents you from using battery saving modes at all on the apps you don't use often .
Thanks though.