Is there a way?
I would like to know as well.
Can't find it in settings....maybe a ROM has it?
Dragonsla said:
I would like to know as well.
Can't find it in settings....maybe a ROM has it?
Click to expand...
Click to collapse
I find no such setting in stock or CM9...
It's in the framework or systemui (can't remember which). You need to decompile it change a settings in the xml recompile and push it back to your phone.
I am on my phone now so I can't find the link that I read it in, if I get a chance later I will see if I can find it.
I want it also however I haven't bothered to do it.
Sent from my Galaxy Nexus using xda premium
Hmm... not sure. But if you decompile framework-res.apk, and then navigate to res/values/bools.xml there's code that says "config_unplugTurnsOnScreen" set to true. You can set that to false, and it will not turn on when you unplug your phone, but I don't know if the same holds true if plugging your phone in. =/
I believe it's a kernel setting. On my DInc, same ROMs with different kernels some would screen on when plugging in and others would not.
I would also like to know how to keep the screen ON while plugged in....(and not go to sleep ;] )
Developer options keep screen awake. Or something like that
Sent from my Galaxy Nexus using xda premium
I, too, would like to know.
Stay awake while plugged in USB
Under developer options I found a setting to stay awake while charging.
Related
A quick search didn't turn up anything, so here goes..
Is there a way to prevent the phone from waking when you unplug it from charging? I know it will just time out or you can manually shut the screen back off, but I'd like to prevent it from turning the screen on at all on unplug.
Any ideas?
*I just realized this could be posted in the general Android q&a section since it shouldn't be device specific I think. If a mod would like to move it then great
Not exactly sure how its done, but i know that with CM7, it's disabled, so it has to be a feature of specific roms
Doesn't do it on MIUI either, so I think it's a Sense thing. Maybe something to do with the kernel?
Sent from my PC36100 using Tapatalk
ugh I would totally run CM if I could get MMS working on it with Cricket...it's the only thing stopping me.
If only they would transfer the Cricket APN settings built in the CM7 rom for the Huawei Ascend into other devices. It doesn't work properly when I try to manually program them in.
Hi Guys,
about 10 times a day or so, I hear my phone vibrate (phone is on vibrate at work).
When I unlock the screen, I have a "complete action using pop-up" with dropbox, gmail and skype as the options.
Another user did some investigation by clicking on gmail to see what exactly it's sending and it looks to be an error report to google.
Anyone else experienced this?
i've experienced this too, dont know the cause though
BUMP.
Anyone else getting this at all?
Running AOKP Build 26 4.0.3 and Franco Kernel.
Cheers
Yeah its data logging. Caused by holding both volume and power I think it is. You can turn it off in aokp in general UI settings
Sent from my Galaxy Nexus using xda premium
I got it too..I'm pretty sure it is not generated by holding both volume keys and power.
It appears random.What is that?It's a sort of issue log.
Any way to desactivate it?
I have the same issue running 4.0.4. I believe a program keeps automatically taken screen shots of my GN
This is happening to me... any solution?
Another victim.
Another one here.
I'm on Stock 4.0.4 and Franco's Kernel.
If I stop to think, I guess this started to happen since I started using MoDaCo leaked 4.0.4 that comes with Franco's Kernel.
So I guess it might be Kernel or 4.0.4 fault.
The bad thing is that the supposed error log have nothing interesting.
definitely 4.0.4... I'm running stock.
it happens if u press the volume button in between Up and Down (in the middle) and power at the same time for a second or so
try and u will see the report appearing after a minute or so
solution: when u want to unlock ur phone, just press the power button
Its ICS's bug mailer and is, to be honest, flawed. Its trying to send a bug report to Google. Use root explorer, mount as r/w and rename bugmailer.sh to bugmailer.sh.old, save and reboot. Should stop it hapenning anymore. Its more of an annoyance then anything useful IMO. I used to get 5-6 a day but never saw or come across any crashes or problems. Rename and enjoy the phone
Sent from my Galaxy Nexus using XDA
killyouridols said:
Its ICS's bug mailer and is, to be honest, flawed. Its trying to send a bug report to Google. Use root explorer, mount as r/w and rename bugmailer.sh to bugmailer.sh.old, save and reboot. Should stop it hapenning anymore. Its more of an annoyance then anything useful IMO. I used to get 5-6 a day but never saw or come across any crashes or problems. Rename and enjoy the phone
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
never happened to me..also it doesn't send reports to anyone, because u have to put the email address..its a developer feature to show u a lot of debug information
are u sure u are not pressing both volume (in the middle) and power when waking up the phone? thats the cause
andQlimax said:
never happened to me..also it doesn't send reports to anyone, because u have to put the email address..its a developer feature to show u a lot of debug information
are u sure u are not pressing both volume (in the middle) and power when waking up the phone? thats the cause
Click to expand...
Click to collapse
Granted, you don't have to send it to Google, but my point stands. It flares up, on occasions, all too often. If anyone has no desire to read it, disable it. It serves no purpose unless you actively wish to send it to anyone for any reason.
Sent from my Galaxy Nexus using XDA
andQlimax said:
it happens if u press the volume button in between Up and Down (in the middle) and power at the same time for a second or so
try and u will see the report appearing after a minute or so
solution: when u want to unlock ur phone, just press the power button
Click to expand...
Click to collapse
OMG! It did work!
I think that it might be due to the case!
I'll try killyouridols script renaming approach now.
I installed cm9 after using cm7 and cant get the four buttons on the phone to light up. They are accessible but not illuminated. has anyone else encountered this problem.
Also I was wondering if the Cm7 uses more battery than cm9
You have to use auto brightness.
cm9 illumination
If you mean display auto brightness ok but when I'm outside I can't see the screen...guess ibhave to toggle back and forth. I had switched back to cm7. In your opinion is 9 worth changing to. It seems like in 7 everything is working pretty well.
Thank you for the reply
pmpic said:
I installed cm9 after using cm7 and cant get the four buttons on the phone to light up. They are accessible but not illuminated. has anyone else encountered this problem.
Also I was wondering if the Cm7 uses more battery than cm9
Click to expand...
Click to collapse
Toggling auto brightness on and off solves it. Just tinker with it..
Sent from my Incredible 2 using xda premium
cm9 illumination
Thank you....I appreciate it
Menu keys...
Ive been using the dinc2 since last July and I got used to the buttons to the point that I noticed they didn't light up, but until I saw this post, I never considered it a "problem". Since I knew where they were and didn't need to see them to use them. If they ever do "fix" this issue I hope they allow for a settings option to keep them turned off. I actually enjoy them off, in my mind its just one more security feature. I know when my wife tries to use my phone she needs to see them, and since recently rooting to CM9 I don't want her bricking my phone. Because of the unlit buttons she has stopped using my phone (she uses some cheap AT&T phone, refuses to switch to Verizon). Just throwing my opinion in the mix. Thanks for the post as well I wasn't sure it was intentional or not.
atomwes said:
Ive been using the dinc2 since last July and I got used to the buttons to the point that I noticed they didn't light up, but until I saw this post, I never considered it a "problem". Since I knew where they were and didn't need to see them to use them. If they ever do "fix" this issue I hope they allow for a settings option to keep them turned off. I actually enjoy them off, in my mind its just one more security feature. I know when my wife tries to use my phone she needs to see them, and since recently rooting to CM9 I don't want her bricking my phone. Because of the unlit buttons she has stopped using my phone (she uses some cheap AT&T phone, refuses to switch to Verizon). Just throwing my opinion in the mix. Thanks for the post as well I wasn't sure it was intentional or not.
Click to expand...
Click to collapse
I believe in the advanced brightness settings under CMSettings you can do just that. Whenever I run a CM rom, I always go to the brightness settings under edit Other Levels and set all the softkey values on the far right column to 255 so they're always the same brightness and look nice. I like the sheen they have, but I can only see it when they're close to full brightness.
If you did the opposite, set all the values to 0 and then click Save and Apply Values at the top of that screen, they should, theoretically, never turn on.
Thank you ....as I am new to a rooted phone and this forum I didn't know those adjustments were available...learn something new everyday ......
Does cm9 drain the battery alot quicker or is it unnoticeable
pmpic said:
Thank you ....as I am new to a rooted phone and this forum I didn't know those adjustments were available...learn something new everyday ......
Does cm9 drain the battery alot quicker or is it unnoticeable
Click to expand...
Click to collapse
Unfortunately, I can't answer that question for you, as my phone doesn't like our ICS builds. Until we get a leaked official kernel and some source, I'm SOL.
RegnierD said:
I believe in the advanced brightness settings under CMSettings you can do just that. Whenever I run a CM rom, I always go to the brightness settings under edit Other Levels and set all the softkey values on the far right column to 255 so they're always the same brightness and look nice. I like the sheen they have, but I can only see it when they're close to full brightness.
If you did the opposite, set all the values to 0 and then click Save and Apply Values at the top of that screen, they should, theoretically, never turn on.
Click to expand...
Click to collapse
Where exactly are these settings? Running CM7 with the same problem as the OP and can't find it anywhere. Edit: found the settings and putting them all at 255 didn't do anything. Any other ideas?
Recently on a few roms I've seen my phone wake itself. Not entirely sure how.. And not to mention, it does this when I'm sleeping. So basically my phone will die within hours as my phone stays on and the screen burns in
Unfortunately I have a 30 second time out and it does not shut off my screen. It stays on entirely.
I need help to fix this issue, I have not recently installed anything I normally don't install things and haven't flashed any kernel or mod that should affect it. I did flash a Beats mod by rocko but I highly doubt that is causing the issue.
Sent from my ADR6300 using Tapatalk 2
withbloodskies said:
Recently on a few roms I've seen my phone wake itself. Not entirely sure how.. And not to mention, it does this when I'm sleeping. So basically my phone will die within hours as my phone stays on and the screen burns in
Unfortunately I have a 30 second time out and it does not shut off my screen. It stays on entirely.
I need help to fix this issue, I have not recently installed anything I normally don't install things and haven't flashed any kernel or mod that should affect it. I did flash a Beats mod by rocko but I highly doubt that is causing the issue.
Sent from my ADR6300 using Tapatalk 2
Click to expand...
Click to collapse
It sounds like some app is waking it up and then holding a wake lock. You will have to experiment and uninstall apps to see which app is doing it. Do you remember installing a certain app right before it starts doing it. More than likley it will be one of the apps on the running menu under manage applicarions.
cmlusco said:
It sounds like some app is waking it up and then holding a wake lock. You will have to experiment and uninstall apps to see which app is doing it. Do you remember installing a certain app right before it starts doing it. More than likley it will be one of the apps on the running menu under manage applicarions.
Click to expand...
Click to collapse
Exactly this, apparently Doubletwist was the culprit. Shame too.. its never done that to me before, I like using my phone as a media server to use on my xbox/surround sound system
Thanks though, appreciate it.
Sent from my ADR6300 using Tapatalk 2
I use better battery stats to find wakelocks. Sounds like yours was any easy find but some can be really sneaky.
I know Songbird has a ton of addons, maybe give it a look and see if it can do what doubletwist does.
In a related note....my screen timeout wouldn't work one day. No matter what I set it to, the phone would never timeout/display-off automatically. I just ran 'Fix Permissions' and issue fixed itself.
I'll have to try it, songbird is sick. I am in love with that audio player.
Sent from my ADR6300 using Tapatalk 2
Thanks.
cmlusco said:
It sounds like some app is waking it up and then holding a wake lock. You will have to experiment and uninstall apps to see which app is doing it. Do you remember installing a certain app right before it starts doing it. More than likley it will be one of the apps on the running menu under manage applicarions.
Click to expand...
Click to collapse
Precisely, in my case it was skype keeping my phone awake.
withbloodskies said:
Recently on a few roms I've seen my phone wake itself. Not entirely sure how.. And not to mention, it does this when I'm sleeping. So basically my phone will die within hours as my phone stays on and the screen burns in
Unfortunately I have a 30 second time out and it does not shut off my screen. It stays on entirely.
I need help to fix this issue, I have not recently installed anything I normally don't install things and haven't flashed any kernel or mod that should affect it. I did flash a Beats mod by rocko but I highly doubt that is causing the issue.
Sent from my ADR6300 using Tapatalk 2
Click to expand...
Click to collapse
You probably have an issue with Screen Wakelock(a.k.a FULL_WAKE_LOCK) , which is used by third-party apps to control the screen.
There is an app which is specially developed for solving "wakelock" issues, It is called "Wakelock detector" freely available at GooglePlay.
Or you can just type "Wakelock" at GooglePlay
Here is XDA thread; Xda Wakelock detector
Perhaps this can help as well.
http://forum.xda-developers.com/showthread.php?t=1878828
http://forum.xda-developers.com/showthread.php?t=1179809
Wow. Digging up an old post and the op has switched phones.
This information could still be useful to someone.
Sent from my Galaxy Nexus using Tapatalk 2
i'm a real idiot when it comes to creating a code... i can read and understand code, but not make it.
what i want is to change /sys/class/leds/jogball-backlight/brightness file...
this file controls the trackball light... i want it to be flashing (smoothly) constatly, even when asleep to know that my phone is alive...
so, default briightness value is 0 (as in OFF)... flashing smoothly is 7. so i just changed the file from 0 to 7... the trackball became flashing... so far so good.
i locked the phone and let it go to sleep... the trackball suddenly stopped.
i checked the file again, and it got replaced from 7 back to 0.
so what i want is a script that periodically sets the value to 7 to keep the trackball flashing.
any help?
———————————————————
i didn't mean to mock you or to offend you in any kind of way
Bump
———————————————————
i didn't mean to mock you or to offend you in any kind of way
This sounds like a bad idea that is going to ruin your trackball led and drain the hell out of your battery. Why would your phone ever not be "alive"? What is the point of this?
Sent from my HTC Vision using xda premium
blk_jack said:
This sounds like a bad idea that is going to ruin your trackball led and drain the hell out of your battery. Why would your phone ever not be "alive"? What is the point of this?
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
the point of this is because i use beta/test mods and ROMs, i sometimes see the phone "dead" as in i should boot it again and remove the beta mod to fix it... so i should at least know that the phone is alive only with looking at it
Riro Zizo said:
the point of this is because i use beta/test mods and ROMs, i sometimes see the phone "dead" as in i should boot it again and remove the beta mod to fix it... so i should at least know that the phone is alive only with looking at it
Click to expand...
Click to collapse
going in via adb shell seems like a less destructive way to know if your phone is "alive", since if you can't get in via adb, then the trackball led indicator is rather pointless even if it keeps looping.