I know this is in the wrong forum but you never get an answer in general, so im asking for help here please.
basically im after a way to force GPS to turn off, through terminal with root permissions or somthing to that effect as i cannot for the life of me get GPS to turn off!! i untick gps in settings menu, it unticks, i back out that screen and go back in and its still ticked for gps on. and the power widget doesnt even do anything when i press to turn off gps.
i know that a factory reset will probably sort it but ill do that as a last resort, i just wondered if there is a way to force it to turn off.
but linux commands i have no idea about as i imagine it could be done through terminal??
any answers are greatly appreciated, as you can imagine my battery is dying pretty rapidly now with minimal use
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General
Have you tried using an app like the ones at https://market.android.com/details?id=com.dinop.GpsOnOff&feature=search_result or https://market.android.com/details?id=zwt.android.gpsonoff&feature=search_result or there are more available by searching the Android Market if the above do not help.
Dave
Related
I flashed Serendipity 6.2 on my Captivate yesterday and I've noticed a problem. The backlight on my buttons at the bottom of the screen stay on all the time, the settings, home, back and info buttons. I cannot find a setting to turn off the backlights on them or a setting to say how long they stay on until they go off. It's draining my battery faster because of it. Has anyone else noticed this problem with Serendipity 6.2, or am I missing a setting somewhere?
Thanks in advance,
That is a feature in the ROM/Kernel, not a defect. If can be turned off/on in the recovery menu, or controlled via an app.
https://market.android.com/details?id=neldar.bln.control.free&feature=search_result
KonaZXIII said:
That is a feature in the ROM/Kernel, not a defect. If can be turned off/on in the recovery menu, or controlled via an app.
https://market.android.com/details?id=neldar.bln.control.free&feature=search_result
Click to expand...
Click to collapse
BLN (black light notification) is not supposed to stay on permanently.
but try booting into clockwork recovery > find BLN settings and disable.
give that a try.
OR it could be a problem with "keep the lights on" or whatever patch/method that rom uses to keep the lights on while touching screen.
also you get more help posting Questions in the Questions and Answer section... or more specifically the Serendipity Q&A thread
For the millionth time:
It's BLN.
It's not a bug.
It's not a problem.
It's not draining battery.
RTFM.
Sent from my Captivate
Thanks for the help guys.
Trusello, I'll keep that in mind on the Q&A thread.
MikeyMike, I'm a relative newbie to android and just got into modding my phone. I'm also new to the forum here and the bulk of information can be overwhelming. I'm still learning my way around to forum so please be patient with a new android user.
Thanks again for all your help.
In the future, most of the ROMs in here have a dedicated sticky in the Q&A subforum where questions like this should go.
All of a sudden today, my screen turned off after like 4 seconds. I pressed power and it just flashed momentarily and turned off immediately. Every time I pressed power, it did the same thing.
I rebooted. The ASUS startup screen showed fine. Then as soon as it booted in, same thing.
I tried wiping all data, and then rebooted. Same problem.
Since it only does this when booted in, I'm thinking it's a software issue. But how the hell do I fix it if I can't get the screen to do anything more than flash on for less than 1 second?
When I'm plugged in, the screen works fine. I'm so confused...
UPDATE: For some reason, when I turn on automatic brightness, the problem goes away. But the second I turn off auto brightness, the screen immediately shuts off and the problem repeats. And auto brightness keeps the screen on a really low setting.
Urrghhh
Chief85 said:
All of a sudden today, my screen turned off after like 4 seconds. I pressed power and it just flashed momentarily and turned off immediately. Every time I pressed power, it did the same thing.
I rebooted. The ASUS startup screen showed fine. Then as soon as it booted in, same thing.
I tried wiping all data, and then rebooted. Same problem.
Since it only does this when booted in, I'm thinking it's a software issue. But how the hell do I fix it if I can't get the screen to do anything more than flash on for less than 1 second?
When I'm plugged in, the screen works fine. I'm so confused...
UPDATE: For some reason, when I turn on automatic brightness, the problem goes away. But the second I turn off auto brightness, the screen immediately shuts off and the problem repeats. And auto brightness keeps the screen on a really low setting.
Urrghhh
Click to expand...
Click to collapse
This is a well known and well documented issue that could have been easily found by searching. Your thread adds to the 3 or 4 that already exist regarding this issue.
Sent from my TF Decepticon
b1ackplague said:
This is a well known and well documented issue that could have been easily found by searching. Your thread adds to the 3 or 4 that already exist regarding this issue.
Sent from my TF Decepticon
Click to expand...
Click to collapse
I do recall reading similar reports earlier, but from my memory, there seemed to be some differences. If I'm wrong, I'm sorry for inconveniencing you for a whole 5 seconds
Side question: have you ever tried to get decent search results? It's extraordinarily difficult given that terms are used for multiple purposes, and not all the language is universal.
After going back, and reading a ton of threads through manual forum-browsing, it seems that I was correct about most other problems being distinction from this. Only really found one other mention of this (http://forum.xda-developers.com/showthread.php?t=1078331). So perhaps YOU should search before telling people they should search.
Anyone have thoughts?
Chief85 said:
After going back, and reading a ton of threads through manual forum-browsing, it seems that I was correct about most other problems being distinction from this. Only really found one other mention of this (http://forum.xda-developers.com/showthread.php?t=1078331). So perhaps YOU should search before telling people they should search.
Anyone have thoughts?
Click to expand...
Click to collapse
I do search and I am subscribed to other threads that I check daily regarding your same issue. Ill come back to this thread and post the links to those other forums so as to keep the TF general thread from being overpopulated. And even if your problem IS unique its still very closely related to others in the forum link you posted and would still be more appropriate to post there rather than creating another thread.
I have the same exact problem as you and I want it solved just as much as you but I would I also like the ability to easily navigate this forum and that's only possible by keeping related threads from happening.
Sent from my TF Decepticon
For now the only solution seems to be to keep hard resetting your device (hold power for 10+ seconds) several times and keeping a manual brightness. I had to hard reset my device 8 tines before the screwn would stay on. The reason that your backlight is shutting off when you turn AB off is because of where your manual brightness is set and chances are it's set too high which seems to be the common cause. Keep hard resetting your device until manual brightness is allowed then set MB to a lower level. This issue happens on AB as well when in a bright area and it sets the brightness to high on its own.
Sent from my TF Decepticon
I wonder if it can be fixed if you use the dock's brightness adjustment keys?
b1ackplague said:
I do search and I am subscribed to other threads that I check daily regarding your same issue. Ill come back to this thread and post the links to those other forums so as to keep the TF general thread from being overpopulated. And even if your problem IS unique its still very closely related to others in the forum link you posted and would still be more appropriate to post there rather than creating another thread.
I have the same exact problem as you and I want it solved just as much as you but I would I also like the ability to easily navigate this forum and that's only possible by keeping related threads from happening.
Sent from my TF Decepticon
Click to expand...
Click to collapse
Hate to jump in you but do you see the inherent contradiction in that statement? If the search tools are adequate then the number of similar threads should not matter as they can sorted by relevance. If they are not, as your desire for single threads suggest, then asking a new person to use them to find an answer is not appropriate as it isn't going to be successful. I've found that the bulk of the posts aren't technical so a search for the appropriate terms is pointless and a simple question is more likely to get results. For example, when calling on webcore, lcd brightness is being set to 0. This is in the logcat I took when testing and I get nothing when searching for it. If I search for 'black screen', I get something.
Let's remember we're here to help each other. Being inclusive and welcoming to newcomers is a much more positive way for us to find results.
Cheers,
Todd.
frosty5689 said:
I wonder if it can be fixed if you use the dock's brightness adjustment keys?
Click to expand...
Click to collapse
I have this problem and the dock is the only way I can get the screen back on. I have to press the auto brightness button then press the power button to get the screen on.
If I manually increase the brightness from 0 in steps I can get to half way but then the screen goes off. Similarly I can reproduce this by using the slider to increase the brightness. I am trying other ROMs to see if I can get rid of this issue but so far it happens on Stock & Paul O'Brian's with full resets on both. sigh.
After endless reviews of the logcat files, resets and roms, seems I can't find a solution. Going to rma it unfortunately!
Sent from my HTC Desire using XDA App
So RMA is the answer?
Yes I rmaed mine to Asus. Only took them a a few days to fix and ship it back to me.
Thanks. I better unroot mine and get it sent.
Having this problem.
Latest distro of RG2X MIUI installed... I can't seem to find any way to adjust or disable the LED notification when an Email/SMS/Call is received/missed. Anyone have any insight?
I like the LED notification, however it seems to destroy my battery life if I don't clear the notification in a reasonable amount of time. I wouldn't think it to be the problem, however if I go without getting notifications, my battery life is great.
TIA
searched the thread came up with this, courtesy of psychoace
Go to the home screen
Hit the search button
Hit menu
Go to search settings
Turn on settings search
Back out
Hit search again and type either trackball or led
You now have control of your capacitive button lights
and maybe next time search the thread or ask in there before making a whole new thread when you don't have to... that is an old solution and MIUI has been updated since so I don't know if it'll work or not... post your results if it worked.
mt3g said:
searched the thread came up with this, courtesy of psychoace
Go to the home screen
Hit the search button
Hit menu
Go to search settings
Turn on settings search
Back out
Hit search again and type either trackball or led
You now have control of your capacitive button lights
and maybe next time search the thread or ask in there before making a whole new thread when you don't have to... that is an old solution and MIUI has been updated since so I don't know if it'll work or not... post your results if it worked.
Click to expand...
Click to collapse
While I should have mentioned in my original post that I DID SEARCH for a solution, I don't see the necessity for the contempt.
I did try the method mentioned, PRIOR to posting this thread. Neither LED or Trackball shows up in the search after enabling the settings search.
In summary, the proposed solution does not work for RG2X MIUI 2.3.24
hmmm I didn't think it would, I don't know what to tell you hopefully someone can help out.
Ok, an update for anyone who may have a similar problem.
I could not get the above mentioned solution to work, at first. After getting a bit frustrated with the matter, I performed a completely clean flash of the ROM again, re downloaded, etc... and now the above solution does work.
Another inexplicable and random quark I suppose.
Thanks for the help, mt3g.
Interesting but glad it worked out
Sent from my LG-P999 using xda premium
First of all, sorry for my English, I'm Spanish and I'm still learning your language, so be patient with my spelling
I want to announce that I have searched the internet looking for a solution and have not found it, so I'm asking here as there is much expert with mobiles and the android operating system.
The problem I have is that I push notifications are late, I tried using programs like "Advance Wifi Lock and Fix My WiFi" and the problem persists. Currently use "Baked Blackbean r6" with the stock kernel of this rom.
Is there any solution to this problem?
I also know that this is not the right place to post this problem, but since I have only 6 posts, I can not post in the developer forum and do not want to fill the absurd message board to increase my number of posts.
Thanks in advance.
At this point it only seems that advanced wifi lock should be the best cure. Nothing better invented yet.
You can try just to turn screen brightness to minimum and put screen timeout on "never"
If what you say just do not want to imagine the battery drain that implies.
I guess the only solution is known, it will be a general failure in the use of "custom roms"
If anyone knows any alternative, I'm all ears
Also, if you use "advanced wifi lock", the device never goes into "sleep mode" and that's a drawback for battery drain...
EDIT:
SORRY: Searching on this forum i found this: http://forum.xda-developers.com/showthread.php?t=2025708
good morning all,
i am hoping someone can help my stupid self.
i finally got a root to work on my phone, for the main purpose of removing mcafee. i start getting rid of the programs i don't need and can't find mcafee anywhere. turns out is in the "cannot remove" list.
so, i find a couple of tasks without any info and turned one off hoping that might be it:angel:.
turns out i turned off my input for the lockscreen. to make it even more fun, it is encrypted. i cannot get it to be recognized on my pc. i can get it to start in safe mode, and i can get it to start in the download mode.
it won't install the mtp drivers, but the rest are there.
so, i was hoping one or more of you wonderful, intelligent and, dare i say, beautiful people would know of a way to get around either the encryption or some way to turn the task back on so that i can enter my code.
thank you for not laughingtoo hard at my pain