question, i've got a 6515 and it keeps powering itself on. when i turn it off (with the on switch), it automatically powers on after a few minutes. this drains my battery within 18 hours since the pda function is activated (back light and screen comes on). it keeps powering on automatically every time i turn it off. i disabled all connectivity (no sim present, bluetooth of. so both are disabled). i disabled the gps download applet, so it cannot automatically download. i disabled the active sync setting (After setting it to manually and unchecked all the peaktime settings). i also tried to reflash my current rom (the latest), but it keeps powering on? i also took out all the memory cards and there are no third party applications installed (just did a hard reset). any help is appreciated, or else i will throw the thing out of the window (then i know for sure it will never turn on again)!
mine did the same thing for a while and it was related to activesync and blutooth ativesync. no idea what fixed it tho. sorry
Disable Hardware Buttons
Have you tried to disable the hardware buttons to see if it maybe a button that is getting pressed. To disable them hit Start, goto Settings, tap Buttons, tap the Lock tab, then put a check in the "Disable all buttons except power button" box.
I used the flashlight last night by pressing the volume up button momentarily. I then turned off the flashlight by pressing the volume down button.
This morning I woke up and noticed in BBS that the device never sleep (it was not connected to power).
In "Kernel Wakelock" it shows PowerManagerService was rubbing ask the time.
In "Partial Wakelock", it shows PhoneWindowManager.mTorchLightWakelock was running ALL the time.
It's this a bug in the implementation of using hardware key for using the flashlight?
lanwarrior said:
I used the flashlight last night by pressing the volume up button momentarily. I then turned off the flashlight by pressing the volume down button.
This morning I woke up and noticed in BBS that the device never sleep (it was not connected to power).
In "Kernel Wakelock" it shows PowerManagerService was rubbing ask the time.
In "Partial Wakelock", it shows PhoneWindowManager.mTorchLightWakelock was running ALL the time.
It's this a bug in the implementation of using hardware key for using the flashlight?
Click to expand...
Click to collapse
It seems to be a bug, yes, same thing happened to me when I activated the flashlight function and tried it out once. I had to de-activate the ability to turn on the flashlight, and then reboot, to make it go away. I downloaded a third party flashlight app instead, can't recall which one, and put a shortcut on my lockscreen instead.
any idea how to set up Tasker to turn on airplane mode at a specific time and turn it off at a specific time? The idea is to have airplane mode turned on at say 1am and turned off at 7am. Anyone?
Only with ROOT.
Do you have ROOT?
jonathansmith said:
any idea how to set up Tasker to turn on airplane mode at a specific time and turn it off at a specific time? The idea is to have airplane mode turned on at say 1am and turned off at 7am. Anyone?
Click to expand...
Click to collapse
New profile ---> Time ---> From 1:00 to 6:59
Task: Plugin ---> Secure Settings --> Configuration ---> Root Actions ---> Airplane Mode ---> On
Exit Task: Plugin ---> Secure Settings --> Configuration ---> Root Actions ---> Airplane Mode ---> Off
This requires you to have th Secure Settings plugin for Tasker and Root access.
Yep, I have root access. @alray ... thanks mate ... will give it a go and will report! Thanks to both of you
Worked as @alray explained ... but the only problem is that I set the time from ... to ... but but when the time frame has expired I would expect Tasker to turn off airplane mode (that's the whole point), but at the moment it doesn't. What am I missing here? Had to keep my eyes open and select 'Enable Tasker'. For a first time user, that switch could easily be skipped.
PS - I couldn't find anywhere in the settings where to remove the Tasker icon from the notification bar. I do want it to run in the background but i don't need it in my notification bar and also when i pull-down the notification screen. Any idea how to remove it?
OK, got the answer to the Notification area question (It was the Run in foreground tick). Furthermore, I tried both Root Actions ---> Airplane Mode ---> On and Root Actions ---> Airplane Mode ---> Toggle ... but with both options Tasker forgets to turn off Airplane Mode at the set end time for the profile ... When I was in the Configuration of the Airplane Mode and selected Toggle instead of On, I hit the 'Test action' setting and I ran that a few times. It correctly toggled on and off Airplane mode. So that seemed to work well, but not when I left Tasker do it. The problem occurs both with 'Run in foreground' ticked and un-ticked. Weird!
jonathansmith said:
Worked as @alray explained ... but the only problem is that I set the time from ... to ... but but when the time frame has expired I would expect Tasker to turn off airplane mode (that's the whole point), but at the moment it doesn't. What am I missing here? Had to keep my eyes open and select 'Enable Tasker'. For a first time user, that switch could easily be skipped.
Click to expand...
Click to collapse
jonathansmith said:
I tried both Root Actions ---> Airplane Mode ---> On and Root Actions ---> Airplane Mode ---> Toggle ... but with both options Tasker forgets to turn off Airplane Mode ... strange ...
Click to expand...
Click to collapse
Add an exit task turning back airplane mode off:
Create a new task: plugin --> Secure Settings --> Root Action ---> Airplane mode ---> Off.
Go back to your profile page, tap and hold the linked task and select "add an exit task" and link your "airplane mode OFF" task.
Btw If you set your task from 1:00 to 7:00 then the exit task will start at 7:01 (or if you prefer the task will end at 7:01)
Btw If you set your task from 1:00 to 7:00 then the exit task will start at 7:01
Yep .. thought about that, tested and FAIL
And now will give a try to your last suggestion. That ought to work
jonathansmith said:
Btw If you set your task from 1:00 to 7:00 then the exit task will start at 7:01
Yep .. thought about that, tested and FAIL
And now will give a try to your last suggestion. That ought to work
Click to expand...
Click to collapse
You have to use an exit task, that wasn't a suggestion
And the exist task (airplane mode off) will be triggered 1 minute after the desired time frame. So better to select from 1:00 to 6:59
alray said:
Add an exit task turning back airplane mode off:
Create a new task: plugin --> Secure Settings --> Root Action ---> Airplane mode ---> Off.
Go back to your profile page, tap and hold the linked task and select "add an exit task" and link your "airplane mode OFF" task.
Btw If you set your task from 1:00 to 7:00 then the exit task will start at 7:01 (or if you prefer the task will end at 7:01)
Click to expand...
Click to collapse
That now worked LIKE A BOSS !!! Thanks, man!
jonathansmith said:
That now worked LIKE A BOSS !!! Thanks, man!
Click to expand...
Click to collapse
Youre welcome, post #3 edited accordingly.
Just one last comment - it seems that it won't work unless you leave it run in the foreground. Turning it on DID happen last night while I had Tasker running in BACKGROUND, but turning it off did NOT. Might have something to do with the low memory killer settings or with the app Recently that I use, but since both of these 2 are needed in my case, I guess the only solution is to have tasker forced to run in foreground. Nice at least that I can hide the icon in the notif. bar when it is folded, but annoying when I unfold it and see that huge tasker thing taking all that screen real estate, but ... gotta live with it
And here comes the solution to my previous post. Now I can say the issue is finally resolved! (SEE screenshot)
@alray or @ anyone who's good at figuring out Tasker; how do I set up the following rule - I manually enter Air Plane mode when charging my phone. Can Tasker be automated to turn off the Air Plane mode upon removing the charger? Sometimes I forget to do that and it costs me ... I charge with Air plane mode ON cos it's just A BIT faster. And for my 10% tapping charges a small boost in time is desirable.
jonathansmith said:
@alray or @ anyone who's good at figuring out Tasker; how do I set up the following rule - I manually enter Air Plane mode when charging my phone. Can Tasker be automated to turn off the Air Plane mode upon removing the charger? Sometimes I forget to do that and it costs me ... I charge with Air plane mode ON cos it's just A BIT faster. And for my 10% tapping charges a small boost in time is desirable.
Click to expand...
Click to collapse
You'll need root + Tasker + Secure Settings. Create a new profile based on state: AC plugged in. Task: plugin, secure settings, root action, airplane mode, ON. Then add an exit task: plugins, secure settings, root action, airplane mode: OFF.
Sent from my HTC One using XDA Labs
10x man! You should have said that I first have to start with the Task(s) and then when creating the profile I add the Task(s). Now, your suggestion is good, but a bit different from what I asked. As far as I understand your suggestion would enable Airplane mode while on AC and will disable it as soon as I unplug from AC. Fair nuff, fair nuff. However, I was asking only for an action to disable Airplane mode in the event that I actually did enable it in the first place. I say that cos I don't ALWAYS enable airplane mode while charging. I do most of the time but not always. Sometimes I need longer charges and I really don't want airplane mode to be enable during them. I need the airplane mode only for short-term charges and therefore my idea is that I should be the one to decide whether or not I enable Airplane mode. What Tasker should do is only to disable Airplane mode upon unplugging from AC ONLY in case airplane mode was enabled in the first place. This way I can decide whether or not I want to charge with Airplane mode enabled and in case I did charge with Airplane mode enabled Tasker will do its thing and will turn it off when needed. I'm sure that whatever I decide Tasker will attempt to turn off Airplane mode. In case I didn't enable airplane mode then Tasker will attempt to disable it but it will be in vain cos I didnt enable it in the first place .. so all good with that situation too.
So I modified your idea a bit and this is what I did. In Tasks I have a task called 'Airplane mode OFF' and it consists of exactly what you said - plugin, secure settings, root action, airplane mode, here I only chose OFF and then the Save icon. So .. that's all there is to it about the Task. Now over to the Profiles. Hit +, State, Power, and here comes my different approach - I choose Battery Level (cos I know that I always charge up to about 90%) so I select a range from 90 to 100... basically anything above 90 would do cos that's the whole point. Reaching over 90 would trigger the action. Of course this approach only applies in case you do what I do, i.e. charge up ALWAYS to a certain %. [ofc I have apps alarming me when this % is off indicating to me that I have to unplug]. So, having done this now I have my range from say 90 to 100 and that then becomes my new Profile and it asks me to add a task and I ONLY add the task to turn off Airplane Mode. I add no exit task at all. Tested it and it works.
By mistake or sth I enabled the setting called 'Enable System+Module'. Is it actually better this way or should I disable it?
jonathansmith said:
What Tasker should do is only to disable Airplane mode upon unplugging from AC ONLY in case airplane mode was enabled in the first place. This way I can decide whether or not I want to charge with Airplane mode
Click to expand...
Click to collapse
OK got it. You could try the same thing but once the profile and tasks are created, delete the entry task so you only have an exit task. This way Tasker will only run a task (airplane mode off) when disconnecting your charger. It won't do anything if airplane mode is already off but it will switch it back off if you turned it on.
Sent from my HTC One using XDA Labs
Correct! Just remember that when you do what you suggest you should restart the app. I closed it and cleared the recents and reopened the app in order to apply the changes. They wouldn't take effect prior to doing that. So ... all things being equal you are absolutely right. Your way is much better, cos it guarantees that in case I want to charge with Airplane mode on, the Airplane mode will be disabled after a charge from ... say 60 to 70% ... in case I'm in a hurry and can only tap 10%. The approach I suggested only works in case you always reach up to the specified 90-ish% and that's not always doable as is the case with the example I gave of a quick charge from 60 to 70%!
Thank you big time for the support!
oh @alray ... as I said - By mistake I enabled the setting called 'Enable System+Module'. Is it actually better this way or should I disable it ... is it a problem?
Is it possible to have airplane mode on when the signal is really low ? and quit after a while ? If so how ?
Hey guys,
I have a Note 8 running on Android 9 for 4 years and I have been using the phone just fine until this morning when I woke up and noticed the phone having nothing on the main screen but a message (in native language, temporary translated as "Phone is booting/starting..."). I thought it was my child messing something up so I left it alone and 2 hours later it still displayed the same message. When I clicked on the Bixbly button, it said that the function was unable in Emergency mode. I also tried restarting, force restarting and restarting in Download mode, but nothing works. The volume button, navigation bar are still working properly; I can still access settings via navigation bar, and I can answer phone calls though I could not make phone calls with it.
Any suggestions on fixing this issue?
sakibaraki said:
Hey guys,
I have a Note 8 running on Android 9 for 4 years and I have been using the phone just fine until this morning when I woke up and noticed the phone having nothing on the main screen but a message (in native language, temporary translated as "Phone is booting/starting..."). I thought it was my child messing something up so I left it alone and 2 hours later it still displayed the same message. When I clicked on the Bixbly button, it said that the function was unable in Emergency mode. I also tried restarting, force restarting and restarting in Download mode, but nothing works. The volume button, navigation bar are still working properly; I can still access settings via navigation bar, and I can answer phone calls though I could not make phone calls with it.
Any suggestions on fixing this issue?
Click to expand...
Click to collapse
From sammobile - To turn off the Emergency mode, just tap on the overflow menu (the three-dot icon) in the top right corner and tap on the relevant option. You can also manage your emergency contacts by tapping the Manage emergency contacts option in the overflow menu.
ultramag69 said:
From sammobile - To turn off the Emergency mode, just tap on the overflow menu (the three-dot icon) in the top right corner and tap on the relevant option. You can also manage your emergency contacts by tapping the Manage emergency contacts option in the overflow menu.
Click to expand...
Click to collapse
Hey ultramaq69,
Thanks for your response. Though the suggestion sounds very general, I found out how to turn it off via power option menu, and it is now working properly again, thanks!
I recently tried activating and deactivating airplane mode on my Galaxy S10 5G to reset my data connection, which was having issues. When I did, the phone's screen timeout somehow set itself to a setting that normally doesn't exist (see attached screen shot). This causes the screen to go black almost immediately when there's no activity. Since happening the first time, my phone keeps defaulting to this setting, usually when charging it overnight. The setting disappears of I select another option and exit the menu, but keeps showing up again whenever it defaults back or I activate airplane mode again. Does anyone have any clue what's happening here?
Welcome to XDA.
Try clearing the system cache first.