Database Develop

NFC

My XT will be here next week (hopefully) and I'm curious how NFC works. I understand the technology but how it works on the phone itself. It is another radio that you can turn on and off? If so does it have a noticeable impact on battery if left on, or can you leave it on all day and not worry about it?

schmidty86 said:
My XT will be here next week (hopefully) and I'm curious how NFC works. I understand the technology but how it works on the phone itself. It is another radio that you can turn on and off? If so does it have a noticeable impact on battery if left on, or can you leave it on all day and not worry about it?
Click to expand...
Click to collapse
Yes it's another radio with a toggle.
No it doesn't really have an impact on battery life.

papped said:
Yes it's another radio with a toggle.
No it doesn't really have an impact on battery life.
Click to expand...
Click to collapse
Pretty much sums it up. You will also notice that when sending a larger file (pictures for example) it will automatically switch on Bluetooth on both devices and send like that, then switch if off. I haven't really used it yet, which is a shame.
Sent from my LT30p using xda app-developers app

This pretty much sums it up from both a spec and uses point of view.
http://en.m.wikipedia.org/wiki/Near_field_communication
I bought some Smart Tags on a whim and have found them both useful and frustrating. Useful in that they can be used to perform several actions on the phone at the same time and frustrating because you have to unlock your phone before anything works (so I couldn't just jump in the car and swipe the phone by a tag to turn on Bluetooth and make sure my sound mode is set to normal!)
My thread has useful posts (by other members,mainly) about different types of tag and different apps to use with them.
http://forum.xda-developers.com/showthread.php?t=1930557

[Q] Lumia 920 low battery

Hey guys,
i got yesterday my Nokua Lumia 920 and i have some problems with my new baby.
The battery life is not really the best with normal usage for me (Music+Whatsapp and reading news) i got about 6-7h.
do u have some tips how i can save more energy ? I turna always my mobile data off and ofc my wifi and gps. Do u recommend the "Windiws Phone Power Safvr Mode"? Does it help ?
Thanks

I know NFC/wireless charging is a huge feature of the new Lumia, but everyone that I've seen complain about battery life says that turning NFC off saves a lot. You can always charge with the usb cable/adapter.

Fun With Drugs said:
I know NFC/wireless charging is a huge feature of the new Lumia, but everyone that I've seen complain about battery life says that turning NFC off saves a lot. You can always charge with the usb cable/adapter.
Click to expand...
Click to collapse
thanks mate, i´ll give a try. i turned the nfc off. lets see does it work.

NFC off helped mine. Since I don't need the NFC all the time I don't leave it on. No big deal if you ask me. Also check your background tasks.
Sent from my RM-820_nam_att_100 using Board Express

How is the performance on your new phone? What have you used before?
Sent from my X10i using xda app-developers app

[email protected] said:
How is the performance on your new phone? What have you used before?
Sent from my X10i using xda app-developers app
Click to expand...
Click to collapse
The performance is very good. Not simular to android, but great with the animations and without any lags. The worst thing is that wp8 closes automaticly your apps when u hit on the home button. So i always have to start whatsapp over and over again.
I´m coming from Samsung Galaxy S II with Android 4.1 CyanogenMOD 10 aka Siyah Kernel

LudoGris said:
NFC off helped mine. Since I don't need the NFC all the time I don't leave it on. No big deal if you ask me. Also check your background tasks.
Sent from my RM-820_nam_att_100 using Board Express
Click to expand...
Click to collapse
What do u mean with background tasks ? Push mail is on and WhatsApp.
I turned NFC off as well.

Windows Phone does *not* close apps when you press the Start button. Instead, it suspends them; they receive no CPU time*, so they don't drain the battery, but they can be resumed exactly where they were left whenever you want, instantly (although if the phone gets low on RAM, it will start to "tombstone" the apps to persistent storage and then remove them from RAM, which causes the resume to take a moment).
However, the general requirement for third-party apps on WP7 was that they must always launch clean when launched from the Start screen (including app list). The OS could either resume them or do a clean launch, and it was technically up to the app developer to choose, but MS would reject apps from the store that resumed instead of launching cleanly. In WP8, that restriction is removed (or so I've heard), but the apps need to be updated to take advantage of it.
To get back to a suspended app, you use the Back button. Either tap on it to go backward one level in the navigation history (for example, if you accidentally hit Start, you would hit Back to get back where you were), or press-and-hold it for a moment to open the task switcher, which allows you to jump into and resume any app that is resident in memory.
* Some apps are designed to continue running in the background, and will consume power. However, very much unlike Android where almost everything seems to enjoy sitting in the background gnawing on the battery, an app must be specially coded to do this, and for the store to approve it there must be a valid reason for the behavior.

auto closing high power usage apps bug?

Does anyone experience any problems with this setting on 4.1.3? On my phone if i switch it off it sometimes switches itself back on. It also seems to close down apps without notifying me. They are just greyed out and cannot be cleared or removed. (Podcast republic and swipe). Those two apps are also the reason i want it switched off as they stop functioning properly if on.
It seems to be linked to the power saving auto rotate switch-off bug as it tends to happen most of the time when the auto rotate isn't switched on again when i charge the phone. Anyone else experiencing this?
Phone is not rooted and run on stock rom

Lol everybody learning how to set up the new power savers that the development community has been using since the days of ics.
1st problem sounds like you ambient display enabled which will turn on your phone every time you receive some sort of notification. To fix this simply go into your settings, display and turn off ambient display and don't get it confused with adaptive brightness.
2nd problem to me sounds like you have aggressive doze mode active on all your apps or auto close high power apps. To fix this just go to settings, battery, click the 3 dots next to the refresh symbol near the top right corner, click aggressive doze..., if it's turned on make sure the slider is not enabled next to the apps you desire, hit the back button, click on the 3 dots top right corner again, click on high power usage apps, turn it off if it's on.
These battery savers in the Android os are basically hacked and slashed from development on xda. Greenify did most of these functions alone then if you were to mash greenify with power nap you basically got yourself aggressive doze with closing of high usage apps.
Sadly Google is still behind the curve as the power saver app on my Asus Zenfone 2 does a better job at saving power on lollipop because in addition to hibernating and closing apps it allowed you to turn off networks allowing only phone, sms, and alarm to work after the device is asleep and enabled upon waking or you could do super saving which did the same thing except the network stays disabled the whole time boosting standby time from 92 hrs to 105 hrs
Seriously though the best course of action here if this does not help you is to contact the developer of the app and tell them the issues your having, your device and a detailed log report and you will see better results faster because it's probably just an incompatibility​ due to the new os as apps always have issues with fresh out of the gate os systems and your might not be the only person with this issue but you just might be the only person to point it out for a long time.
Sent from my ONEPLUS A3000 using Tapatalk

i snort flour said:
Lol everybody learning how to set up the new power savers that the development community has been using since the days of ics.
1st problem sounds like you ambient display enabled which will turn on your phone every time you receive some sort of notification. To fix this simply go into your settings, display and turn off ambient display and don't get it confused with adaptive brightness.
2nd problem to me sounds like you have aggressive doze mode active on all your apps or auto close high power apps. To fix this just go to settings, battery, click the 3 dots next to the refresh symbol near the top right corner, click aggressive doze..., if it's turned on make sure the slider is not enabled next to the apps you desire, hit the back button, click on the 3 dots top right corner again, click on high power usage apps, turn it off if it's on.
These battery savers in the Android os are basically hacked and slashed from development on xda. Greenify did most of these functions alone then if you were to mash greenify with power nap you basically got yourself aggressive doze with closing of high usage apps.
Sadly Google is still behind the curve as the power saver app on my Asus Zenfone 2 does a better job at saving power on lollipop because in addition to hibernating and closing apps it allowed you to turn off networks allowing only phone, sms, and alarm to work after the device is asleep and enabled upon waking or you could do super saving which did the same thing except the network stays disabled the whole time boosting standby time from 92 hrs to 105 hrs
Seriously though the best course of action here if this does not help you is to contact the developer of the app and tell them the issues your having, your device and a detailed log report and you will see better results faster because it's probably just an incompatibility​ due to the new os as apps always have issues with fresh out of the gate os systems and your might not be the only person with this issue but you just might be the only person to point it out for a long time.
Click to expand...
Click to collapse
Thanks
A) ambient screen is off already
B) already done that but the apps work better if battery optimisation is on for them than off. They really misbehave if not optimised.
How do I produce the logs? Checking under the specific app under apps doesn't seem to have an app log option.

Eggstones said:
Thanks
A) ambient screen is off already
B) already done that but the apps work better if battery optimisation is on for them than off. They really misbehave if not optimised.
How do I produce the logs? Checking under the specific app under apps doesn't seem to have an app log option.
Click to expand...
Click to collapse
Grab a catlog off of the play store they are fairly simple to figure out and they are free. I can't remember for sure but I believe I liked logcat the best as it provided a better ui with a more detailed and easier to read log.
Sent from my ONEPLUS A3000 using Tapatalk
---------- Post added at 01:46 AM ---------- Previous post was at 01:35 AM ----------
Eggstones said:
Thanks
A) ambient screen is off already
B) already done that but the apps work better if battery optimisation is on for them than off. They really misbehave if not optimised.
How do I produce the logs? Checking under the specific app under apps doesn't seem to have an app log option.
Click to expand...
Click to collapse
That's weird that it keeps turning back on hopefully it's not a hardware issue. Most likely due to a rogue incompatible app. Also if you haven't already done so check for an update and make sure you have the latest version and if that don't work the last thing I could think of to try would be to download the latest update and put it on your phone somewhere you can remember, reboot into recovery and erase your cache and perform a factory reset followed by another cache wipe just to be sure. Then select install update from zip file, navigate to it's directory and open it, allow it install the update and after it completely has finished booting don't use it but keep the screen from turning off for about 2 minutes
Sent from my ONEPLUS A3000 using Tapatalk
---------- Post added at 02:07 AM ---------- Previous post was at 01:46 AM ----------
Sorry I can't be of more help to you but I just got my phone today and I'm on the oos 4.1.3 and mine is doing just fine so far but I don't sync mail, push notifications, or use any social media which drain your battery like a hooker with your bank account. So far I'm at 10+ hrs uptime with 4 hrs of sot sitting at 66% battery life with an estimated 20 hrs left.
hope you find your problem or at least know where you got take your issue to which will be discovered in your cat log so you will know if it's the apps, kernels, os or hardware that is to blame and be able to address it to the proper source.
Sent from my ONEPLUS A3000 using Tapatalk

Background processes killing. Is it problematic for you?

Reading this https://dontkillmyapp.com/oneplus I'm left wondering if some strange behaviour I'm seeing could be motivated by this.
For instance, I've been using for several years this app, Stay Alive: https://play.google.com/store/apps/details?id=com.synetics.stay.alive
It gives you the option of having the screen not turning itself off when charging. It's crucial in the car, where I have a dock mounted and use the phone for navigation, music playback, etc.
On my previous Nexus 6P the app worked flawlessly. With 6T sometimes the screen turns off and then it turn itself on once more, as if the process got killed and then restarted.
I have the "don't optimize" option activated for Stay Alive.
There are other strange behaviours I'm seeing, with Tasker for instance. And the nagging feeling that they might depend on background process handling at the OS level.
I recently did turn off Battery/Battery Optimisation/Advanced Optimisation/Deep Optimisation and Sleep standby optimisation, hoping to get better results. I still haven't reached a conclusion about it.
I have to say that it's pretty annoying to have the phone decide for you what should be happening for apps. For instance, I had Firefox in the "Don't optimize" category but it still had problems with opening new pages after a while. Turning off the above two options seems to have cured the problem but if that is needed I wonder what the heck "Don't optimise" mean for OnePlus.
I hope to get to the bottom of this as, quite frankly, not having the phone "act on his own" behind the scenes is exactly why I chose Android as my OS.

gorman42 said:
Reading this https://dontkillmyapp.com/oneplus I'm left wondering if some strange behaviour I'm seeing could be motivated by this.
For instance, I've been using for several years this app, Stay Alive: https://play.google.com/store/apps/details?id=com.synetics.stay.alive
It gives you the option of having the screen not turning itself off when charging. It's crucial in the car, where I have a dock mounted and use the phone for navigation, music playback, etc.
On my previous Nexus 6P the app worked flawlessly. With 6T sometimes the screen turns off and then it turn itself on once more, as if the process got killed and then restarted.
I have the "don't optimize" option activated for Stay Alive.
There are other strange behaviours I'm seeing, with Tasker for instance. And the nagging feeling that they might depend on background process handling at the OS level.
I recently did turn off Battery/Battery Optimisation/Advanced Optimisation/Deep Optimisation and Sleep standby optimisation, hoping to get better results. I still haven't reached a conclusion about it.
I have to say that it's pretty annoying to have the phone decides for you what should be happening for apps. For instance, I had Firefox in the "Don't optimize" category but it still had problems with opening new pages after a while. Turning off the above two options seems to have cured the problem but if that is needed I wonder what the heck "Don't optimise" mean for OnePlus.
I hope to get to the bottom of this as, quite frankly, not having the phone "act on his own" behind the scenes is exactly why I chose Android as my OS.
Click to expand...
Click to collapse
Thank you for this.
I've been feeling stupid having all these issues of pass getting killed in the background.
For me proper working phone is more important than battery life. I can easily get one whole day 6AM-11PM with around 30% battery left.
I would be ok if the apps won't get killed and I have say, 10% battery left at the end of the day.

I also don't understand this, it's what I really dislike about the OnePlus phones. In earlier Android versions it was always adviced not to use app killers because the Android OS knows best when to kill an app. Now OnePlus is doing exactly this, and then call it an optimization... [emoji848]
But @gorman42 are you aware of the option System - Developer Options - Stay Awake?

rmaathuis said:
I also don't understand this, it's what I really dislike about the OnePlus phones. In earlier Android versions it was always adviced not to use app killers because the Android OS knows best when to kill an app. Now OnePlus is doing exactly this, and then call it an optimization... [emoji848]
But @gorman42 are you aware of the option System - Developer Options - Stay Awake?
Click to expand...
Click to collapse
I want to say you're right but it's not only OnePlus that has too aggressive background killing. Google put optimization into Android a couple of years ago and they can't seem to hit a perfect medium between both. I'm sick of switching apps and then going back into an app a couple of minutes later to just have to start at the top of the feed again. It's annoying and it's happened with my 6t, Moto z, Droid turbo, lg g4, and my Galaxy s6 when they were all in their "prime". I think it boils down to Google ultimately

Turn off adaptive battery and on your apps you absolutely want untouched selectDon't optimize under battery > battery optimizations. After doing that I have what is consider a normal experience.

rmaathuis said:
But @gorman42 are you aware of the option System - Developer Options - Stay Awake?
Click to expand...
Click to collapse
Yes, I am. But the screen dims. It doesn't turn off but it dims. For in car navigation that is clearly undesired.
I wonder whether rooting would give me back the control I need through some third party modification...

Aridon said:
Turn off adaptive battery and on your apps you absolutely want untouched selectDon't optimize under battery > battery optimizations. After doing that I have what is consider a normal experience.
Click to expand...
Click to collapse
But if you read my post... I do have "Don't optimize" selected for relevant apps. It still doesn't seem to solve the problems I'm having.
Now I've turned off Adaptive Battery too. Let's see if it makes any difference.

Whats solitions.
İ open accebility settings for any app and closed automatical..
Whyy
I'm sorry for my bad english

gorman42 said:
But if you read my post... I do have "Don't optimize" selected for relevant apps. It still doesn't seem to solve the problems I'm having.
Now I've turned off Adaptive Battery too. Let's see if it makes any difference.
Click to expand...
Click to collapse
You find solitions ?
I'm sorry for my bad english

gorman42 said:
But if you read my post... I do have "Don't optimize" selected for relevant apps. It still doesn't seem to solve the problems I'm having.
Now I've turned off Adaptive Battery too. Let's see if it makes any difference.
Click to expand...
Click to collapse
What most of the times work for for me is open the app, then go to recent app management, click on the 3 dots in the upper right corner above the app and choose lock.
And thanks for the tip of this app, because of company policy "stay awake" was disabled on my device and this app overrides it (Earlier I tried 2 or 3 similar apps but they didn't work, this one does).

gorman42 said:
I wonder whether rooting would give me back the control I need through some third party modification...
Click to expand...
Click to collapse
You really shouldn't have to modify your phone to, by chance, fix what OnePlus did (same could be said about other OEMs too, but that's besides the point right now). OnePlus needs to fix this issue, which has been an ongoing thing in their ROMs for over two years.
It's a shame that it takes a few app devs getting bad reviews on their apps to come up with a website pointing out the offenders of aggressive app management, with OnePlus being number 2 on the list for this issue to pick up traction, despite numerous users reporting about it on their forum and via in-app feedback for so long.
I said it before, and I'll say it again: Compared to OxygenOS on the 3T, OxygenOS nowadays has become so nice to use on the 6T that I don't have a need to root anymore. It's just this issue that really hampers it.

I fell in love with OnePlus when I bought my very first OnePlus phone, the OnePlus 3T. I've since then owned the OnePlus 5T and 6T. Unfortunately I've been disappointed with both because of this specific issue. If they don't resolve this issue within the lifetime of my 6T I feel obligated to start looking for something other than a OnePlus phone next Such a shame, as I love everything else about OnePlus and OxygenOS.

While investigating this I stumbled upon a setting in Developer Options.
Here’s the description and explanation: https://www.techrepublic.com/article/how-to-use-android-pie-standby-apps/
Problem is, with 6T all apps are stuck to ACTIVE status, you can’t modify their status. I guess this could point to OnePlus messing with regular Android power management.

gorman42 said:
While investigating this I stumbled upon a setting in Developer Options.
Here’s the description and explanation: https://www.techrepublic.com/article/how-to-use-android-pie-standby-apps/
Problem is, with 6T all apps are stuck to ACTIVE status, you can’t modify their status. I guess this could point to OnePlus messing with regular Android power management.
Click to expand...
Click to collapse
Are you sure you can't modify the settings, I've tried it and let's me change as per the link you posted?
I agree with you guys the app management is pretty aggressive.

wilpang said:
Are you sure you can't modify the settings, I've tried it and let's me change as per the link you posted?
I agree with you guys the app management is pretty aggressive.
Click to expand...
Click to collapse
Yeah, I tried before writing here.
It happens when you disable Adaptive Battery. If Adaptive Battery is enabled, those settings are active.

I have the same issues with several apps (Tasker, Gravity Screen, Whatsapo (Web)...). The apps was running perfectly on my old lg g4 but on the OPO 6T they gets killed too often. Also disabled adaptive Battery and set those apps to dont optimize. But this doesnt helps....
In previous OOS on the 5T there was an setting for background apps count in developer options, this is sadly gone on our 6T. Is there a way to use this option also when removed from dev options?
(maybe editing some files).
Thx
Gesendet von meinem ONEPLUS A6013 mit Tapatalk

Yes this is very unfortunate.. sometimes I even miss calls and they straight to voicemail

gorman42 said:
Reading this I'm left wondering if some strange behaviour I'm seeing could be motivated by this.
[Snapped]
Click to expand...
Click to collapse
Yes, it is a problem for me. Never had a phone with such aggressive battery management. It even periodically kills my wifi for no reason.

There are 3 settings under Settings > Battery:
1. Battery Saver
2. Battery optimization
3. Adaptive Battery
I have been able to get a somewhat 'normal' experience after turning all 3 options off for Whatsapp, Tasker, etc... For some programs, it seems that it needs to be started, and left running without closing the program in 'Recentd's..
I am rooted and use Greenify to close programs that I want killed when in the background..

@gorman42
Why do you need this staying-alive app?
Google Maps and Waze already make the device's screen stay awake while navigating...

Question Always On Display turns off after an hour or so.

Hey All.
I have always used AOD as a night clock whilst its charging vertically.
But with this phone the AOD always goes off after about an hour.
Which sort of defeats the point of the feature really.
the setting is set to ALLDAY aswell.
is this a fault or is this how it is with phone.

stuatrb04 said:
Hey All.
I have always used AOD as a night clock whilst its charging vertically.
But with this phone the AOD always goes off after about an hour.
Which sort of defeats the point of the feature really.
the setting is set to ALLDAY aswell.
is this a fault or is this how it is with phone.
Click to expand...
Click to collapse
chinese version?

brunolongo said:
chinese version?
Click to expand...
Click to collapse
nah uk

Possibly power management of some type shutting it down?
I use to think always on AOD was a darling... now I only use tap on.
Lol, I sort of like how yours behaves; it waits for you to go to sleep.

blackhawk said:
Possibly power management of some type shutting it down?
I use to think always on AOD was a darling... now I only use tap on.
Lol, I sort of like how yours behaves; it waits for you to go to sleep.
Click to expand...
Click to collapse
pretty sure i have looked at most settings that could possibly effect this.
maybe its just the way it is.
it kinda bugs me at night when i wake up disorientated not knowing the time.
always something i have been used to with previous phones.

stuatrb04 said:
pretty sure i have looked at most settings that could possibly effect this.
maybe its just the way it is.
it kinda bugs me at night when i wake up disorientated not knowing the time.
always something i have been used to with previous phones.
Click to expand...
Click to collapse
I hear you. Best to ignore the phone and sleep.
Always being "connected" detrimental to your wellbeing. Quiet time is very underrated.
Lots of power management settings scattered throughout the phone, usually.
Check to see if global power management is running first: Developer options>standby apps, all buckets should show as active otherwise power management is active. It can't be disabled here though.
Check each apk being used for AOD. Make sure they have needed permissions and that battery saving isn't checked.
Disable any power management including Android, 3rd party, carrier or manufacturer ones.
Try in Safe mode.
Clear system cache and AOD data.
Make sure screen lock isn't interfering with AOD.
With a factory reset even if it works the issue will likely reoccur. Exception is if a 3rd party app altered user hidden settings, this can and does occasionally happen with poorly written apps. Sometimes only after you uninstall them
Play with it, find the root cause... fun isn't it?

blackhawk said:
I hear you. Best to ignore the phone and sleep.
Always being "connected" detrimental to your wellbeing. Quiet time is very underrated.
Lots of power management settings scattered throughout the phone, usually.
Check to see if global power management is running first: Developer options>standby apps, all buckets should show as active otherwise power management is active. It can't be disabled here though.
Check each apk being used for AOD. Make sure they have needed permissions and that battery saving isn't checked.
Disable any power management including Android, 3rd party, carrier or manufacturer ones.
Try in Safe mode.
Clear system cache and AOD data.
Make sure screen lock isn't interfering with AOD.
With a factory reset even if it works the issue will likely reoccur. Exception is if a 3rd party app altered user hidden settings, this can and does occasionally happen with poorly written apps. Sometimes only after you uninstall them
Play with it, find the root cause... fun isn't it?
Click to expand...
Click to collapse
ah some things there that i havent tried.
will play around and report back.
yea the joys of android!!!

stuatrb04 said:
ah some things there that i havent tried.
will play around and report back.
yea the joys of android!!!
Click to expand...
Click to collapse
Feels good when you track it down.
I've tracked (and caused, oops) a few bizarre ones down
Stock Androids are generally very robust platforms.

Lately I have had a Oneplus 9, Oneplus 9 Pro and a Oneplus 10 Pro. In all of them, from Android version 12 (it also happens in 13), what is said here happens (AOD turns off at night even if it is programmed so that it is always active).
From what I see here, either it is a bug that has been introduced since the Oneplus and Oppo software were unified, or it is a crap that Google has put in Android since version 12 that there is no way to fix Because I've been trying things for a long time and reading in forums and websites and no solution to this problem is found anywhere.
For those of us who use our mobile phones as a nightstand clock, it is a great disappointment.

dtvenom said:
Lately I have had a Oneplus 9, Oneplus 9 Pro and a Oneplus 10 Pro. In all of them, from Android version 12 (it also happens in 13), what is said here happens (AOD turns off at night even if it is programmed so that it is always active).
From what I see here, either it is a bug that has been introduced since the Oneplus and Oppo software were unified, or it is a crap that Google has put in Android since version 12 that there is no way to fix Because I've been trying things for a long time and reading in forums and websites and no solution to this problem is found anywhere.
For those of us who use our mobile phones as a nightstand clock, it is a great disappointment.
Click to expand...
Click to collapse
Welcome to XDA.
Tap on works fine for me and uses less battery. Constantly looking at the time when you should be sleeping is counterproductive and a bad habit to get into. For me the novelty wore off after about a year as I find it now annoying.

It's the same on OnePlus 8T, Oxygen OS 13. At least after midnight, maybe earlier, the screen turns black with AOD always on after roughly 25-30 minutes if non use. Double tap or more activates it again.
It's broken for people who is working nights and/or is awake and active after midnight.
There's gotta be a setting fixing this through root or adb shell.