Within the last couple days I noticed that my power/standby button doesn't always work. From time to time I will try pressing it and I will try holding it, and randomly I will hear the camera shutter sound and it will take a screenshot! Weird... I just flashed SC 2.8 today and the problem was still there. Anybody have this happen/have suggestions on how to fix it?
I know when you take a screen shot with 2.8 you hold the back button and hit the power button.
Just try to flash 2.8 again.
The screen shot thing is part of Android 2.2 I believe, but I've been having the same issue and I'm on stock/deodexed/debloated EB01. I can never tell if I just don't press the button enough or if the button truly isn't working. I agree with k rock though, clear cache, wipe dalvik and try to reflash it.
This is good news....I was looking for the answer to this....I knew it was possible but wasn't sure how to accomplish.
Happens to me too.
i haven't updated to 2.8 yet, but i know making the power button take pics in camera mode was added as a feature in one of the earlier sc versions. i'm on 2.4, and i haven't had any issues with the button not working, though.
i want to disable it ...its annoying...can someone pls tell us how?
xlinth said:
i want to disable it ...its annoying...can someone pls tell us how?
Click to expand...
Click to collapse
It might be possible for you to use root explorer to just kill the app, ScreenCaptureService.apk, I don't think this will break anything else since its just a system app. Worst case you have to reflash 2.8. Maybe just try moving it first so you can put it back if you want.
wideopn11 said:
It might be possible for you to use root explorer to just kill the app, ScreenCaptureService.apk, I don't think this will break anything else since its just a system app. Worst case you have to reflash 2.8. Maybe just try moving it first so you can put it back if you want.
Click to expand...
Click to collapse
I believe this to be true. I read somewhere you could do that but never tried because I imagined somewhere, sometime I'd want to use it. The screen capture has been available since DL30 (you're supposed to hold down the Back button while then pressing power, this always works for me as long as you wait just a bit before pressing power button), but based on what has been posted here and my own experience, it seems to be buggy (i.e., taking screenshots when you don't want it to/have not even pressed the back button - for me, I couldn't get the power button to do anything after having taken a picture accidentally until I tapped the Back button once)
I haven't had the bug since moving to SC2.8 though (a couple days ago, I'd normally get a couple unintended screenshots a day).
Its been my experience that sometimes the soft keys at the bottom of the device have a mind of their own sometimes. On many an occasion my back button specifically will activate two or three times all on its own
Samsung Fascinate
Super Frankenclean 2.8
EB16 Voodoo Kernel
tyler1234567's TransblueHC theme
Sent from XDa App Premium
Yes, this has happened to me. I am guilty of not wiping between SC2.6 and SC2.8, though. There has been just enough goofy behavior that I think I will do a wipe later today and re-Odin the SC2.8 tar file on to my phone.
Sent from my SCH-I500 using XDA App
Question:
What locking feature are you using? pin, pattern, password, glass slide?
Voodoo or non
I have a theory.
Related
There is this problem that i seem to be having that i cannot find any information on at all, i mean i have seached the forums several times and no one seems to be having the same problem as me
Basicly every now and again when i hit the power key to bring the phone screen back on it will sort of glitch and turn into a sort of negative look, you know the kind of effect you can set the camera to do, it looks like that and i cant remove it without a reboot and its getting a bit annoying, i just thought maby someone could help me
I am using the new shubcraft 1.4c and maxsenseui energy rom for WM. And i might as well ask if there has been any solution to the screen not coming on straight away when i press the key to wake it up, it doesnt ever sod but it does not come on straight away and sometimes i have to hit the power key several times to get it on but thats no show stopper whereas my main problem is pretty annoying. Thanks for any help in advanced and thanks to all of you guys that made android on HD2 possible
Cheers Dane.
xpstyle36 said:
There is this problem that i seem to be having that i cannot find any information on at all, i mean i have seached the forums several times and no one seems to be having the same problem as me
Basicly every now and again when i hit the power key to bring the phone screen back on it will sort of glitch and turn into a sort of negative look, you know the kind of effect you can set the camera to do, it looks like that and i cant remove it without a reboot and its getting a bit annoying, i just thought maby someone could help me
I am using the new shubcraft 1.4c and maxsenseui energy rom for WM. And i might as well ask if there has been any solution to the screen not coming on straight away when i press the key to wake it up, it doesnt ever sod but it does not come on straight away and sometimes i have to hit the power key several times to get it on but thats no show stopper whereas my main problem is pretty annoying. Thanks for any help in advanced and thanks to all of you guys that made android on HD2 possible
Cheers Dane.
Click to expand...
Click to collapse
I think the 'slow' wakeup is a known issue... I think
As for the negative efect, I got the same thing a few times, but it all seemed to stop after I started using mskip's bootloader....coincidence, maybe but its worth a try.
Lock estimate: 11:33 AM GMT
thesweeney said:
I think the 'slow' wakeup is a known issue... I think
As for the negative efect, I got the same thing a few times, but it all seemed to stop after I started using mskip's bootloader....coincidence, maybe but its worth a try.
Lock estimate: 11:33 AM GMT
Click to expand...
Click to collapse
Ah ok, i will try that now and thanks for the rapid response, didn't expect one that quick heh.
Dane.
xpstyle36 said:
Ah ok, i will try that now and thanks for the rapid response, didn't expect one that quick heh.
Dane.
Click to expand...
Click to collapse
No worries,... as i said, the bootloader may not have been what fixed it for me, it may have just been coincidence... but I know I have had far less problems and not a single WSOD since using the bootloader....
Good luck
thesweeney said:
No worries,... as i said, the bootloader may not have been what fixed it for me, it may have just been coincidence... but I know I have had far less problems and not a single WSOD since using the bootloader....
Good luck
Click to expand...
Click to collapse
Thanks alot Ah i love XDA such a nice bunch of people, would never get that level of tech support in a 3 shop lol !
I have this happening randomly at times, but very rare at think twice
now in a span of 2 weeks. It happened even after I stopped using
Android loaders (ie., mskip) (every time I make a fresh test, I HR winmo, format my sd card then start a fresh) as i said it is very rare
and occurrence is difficult to attribute to anything in particular
Before my actual WinMob ROM I had this effects a few times, now I haven't had it for about a week... Chuckys ROM has a "build-in" Android-loader, works fine for me...
This happened to me yesterday
I pressed the power button a few times in quick succession with a press of the home button thrown in somewhere for good measure.
I should learn to be more patient and let the screen come on
Im also using Mskips loader so can confirm this doesnt stop the issue
it happened to me once when i was using old kernals it also happened on windows mobile , but with new kernals it works fine
solved with frantic key presses
Mr_Erratic said:
This happened to me yesterday
I pressed the power button a few times in quick succession with a press of the home button thrown in somewhere for good measure.
I should learn to be more patient and let the screen come on
Im also using Mskips loader so can confirm this doesnt stop the issue
Click to expand...
Click to collapse
same thing happened to me and I got out of it using the ur frantic power button press solution []
thanks.
Hi,
Imilka reported on this saying it was only a glitch. Just reboot and don't worry about it.
Its happened to me a few times, mainly when I disconnect my charger.
Flashed from my fingers to your face
Anyone having a issue with the screen not coming back on and staying blank? I get this happening from time to time and the only way to fix it is to do a battery pull or do volume up + camera + power button to reboot. When it happens I can hit the power button to wake up the screen but it stays blank and just the keys on the bottom light up and respond to be touched but don't do anything.
Rooted with stock EB13, it did this on rooted DI18 also.
I've done a lot of reading on the Epic forums (General and Development) and I haven't heard of this issue before. What method did you use to update to EB13? If you didn't already do it, you might want to consider a full wipe/reflash of EB13 using Odin/Heimdall/Samsung installer. I'm not guaranteeing anything, but to me it sounds kinda like you have a bad upgrade/flash.
If wiping your caches and doing a full reflash doesn't fix it then it's probably a hardware issue.
DISCLAIMER: I'm nowhere near as experienced as some of these dudes on XDA. If anyone else thinks I'm wrong, please say so and explain why so that I don't give any more bad info! However, I try not to talk out of my ass, so I feel fairly confident in what I've said.
AmericanJedi001 said:
I've done a lot of reading on the Epic forums (General and Development) and I haven't heard of this issue before. What method did you use to update to EB13? If you didn't already do it, you might want to consider a full wipe/reflash of EB13 using Odin/Heimdall/Samsung installer. I'm not guaranteeing anything, but to me it sounds kinda like you have a bad upgrade/flash.
If wiping your caches and doing a full reflash doesn't fix it then it's probably a hardware issue.
DISCLAIMER: I'm nowhere near as experienced as some of these dudes on XDA. If anyone else thinks I'm wrong, please say so and explain why so that I don't give any more bad info! However, I try not to talk out of my ass, so I feel fairly confident in what I've said.
Click to expand...
Click to collapse
I used the Samsung installer.
Same thing has happened to me thrice today (since the upgrade last night, which came from ODINed DI18 usind update.zip).
And that's with no apps installed/running.
I've had this coming up couple times a week on DK28 ROMs, sometimes it's able to recover (like some sort of soft-reboot), most times I need to pull the battery.
I need to replace my Epic badly.. if the replacement behaves the same way, it will join a pile of junk WM6 phones in my basement.
No one else has had this?
Yes. It happened to me twice earlier today. Disturbing. I can't think of anything specific when it happened...once on Dolphin and once after using the camera i think. Have used those a lot since, and it hasn't happened again.
Stock, not rooted. I manually updated via placing the install.zip file on my SD card.
I can confirm this behavior.
Sent from my SPH-D700 using XDA App
Hi dude?!! I dont know if you ever experiences random reboot.
I got my phone not responding (when touch power or menu button) and i could see the Samsung logo hazy. But always resolve by reboot (hold the power button for 8 seconds)
I didnt root or apply lag fix. Is this probably cause by certain app ??? i use some of optimizer or tweaking app.
Usually this happen when i didnt touch my phone over 2 hours. This is very annoying to me. How could i resolve this problems. Does anyone know? please share!!!
Me too
Hello, I have the same issue.
My phone is rooted and i'm using the rom: I9003XXKB1 from Movistar ( spanish operator ).
Compilation number: FROYO.BGKB3
Kernel: 2.6.32.9
The phone freezes randomly and i need to force a reboot holding the power button.
Sometimes it directly reboots alone.
Greetings.
The phone freezes randomly and i need to force a reboot holding the power button.
Click to expand...
Click to collapse
Funny ****, got the same issue on my i9000 on 2.3.4 JVP with CF-Root... also had it on Froyo 2.2.1... this sucks big time, any input or hints appreciated.
Try a new fw first and post the results. Dont add anything else then observe. If all else fails, take it to where you bought it from and get a new 1.
Sent from my GT-I9003 using XDA App
konx777 said:
Hi dude?!! I dont know if you ever experiences random reboot.
I got my phone not responding (when touch power or menu button) and i could see the Samsung logo hazy. But always resolve by reboot (hold the power button for 8 seconds)
I didnt root or apply lag fix. Is this probably cause by certain app ??? i use some of optimizer or tweaking app.
Usually this happen when i didnt touch my phone over 2 hours. This is very annoying to me. How could i resolve this problems. Does anyone know? please share!!!
Click to expand...
Click to collapse
I occasionally have a random reboot as well though I haven't had any again after disabling the live wallpaper i had running from GO Weather.
Mine is a GT-9000 / 2.3.3 stock /I9000XXJVO/GINGERBREAD.XWJVH/ stock kernel at the moment
Didn't have the reboots/freezes before the last standard KIES update though.
You said "i use some of optimizer or tweaking app."
I'd say start by disabling/uninstalling all stuff that you don't really need.
Check if there are apps configured to run in the background and disable those as well
eriamel said:
I'd say start by disabling/uninstalling all stuff that you don't really need.
Check if there are apps configured to run in the background and disable those as well
Click to expand...
Click to collapse
I ever think that maybe cause by bad memory management in Froyo, thats why i use that kind of tools.
But, i'll try to get rid of it, and lets see.
*Sent from my GT-I9003 using XDA App*
Everybody seem concern to latest Gingerbread that actualy still trial ROM
Buts every feedback really needed for I9003 sake.
I have upgrade to 2.3.4 and getting worst after 10min idle. But with some trick from this forum getting better and now still evaluate.
Try this
Select all animations from display menu
go to Settings>Display>Animations>All animations
utkarshshrivastava1 said:
Select all animations from display menu
go to Settings>Display>Animations>All animations
Click to expand...
Click to collapse
Hi utkarshshrivastava, i did it. But still no hope
is it related to battery calibration or something like that ???
Now, iam back to xxkb3 an experienced with this reboot issue again
just rooted and use some apps like TitaniumBackup, Go Launcher Ex, Go Weather.
hmm...just dunno how to figure this out, not only with latona, the other device in other brand also experienced it.
I found that every so often my screen will either start to move on its own or will no longer accept my finger press's. I can fix it by hitting the power button and then turn it back on and it will read again. is there a way to fix this so I don't have to press the power over and over again?
I've had this same problem with my Nook Color (which is about a year old). I solved it by installing a newer version of the ROM I was using. If you still using the stock software that came with the device try doing a factory reset as this problem seems to have evolved and wasn't inherent to the device. Good luck!
spr8dogg said:
I've had this same problem with my Nook Color (which is about a year old). I solved it by installing a newer version of the ROM I was using. If you still using the stock software that came with the device try doing a factory reset as this problem seems to have evolved and wasn't inherent to the device. Good luck!
Click to expand...
Click to collapse
marcusja2002 said:
I found that every so often my screen will either start to move on its own or will no longer accept my finger press's. I can fix it by hitting the power button and then turn it back on and it will read again. is there a way to fix this so I don't have to press the power over and over again?
Click to expand...
Click to collapse
I'm pretty sure your nooks are possessed. I would consult a Catholic Priest or call Ghostbusters.
Sorry couldn't resist.
Sent from my NookColor using Tapatalk
Well odd thing I was messing around with Themes this weekend and the problem disappeared. it doesn't move like it was, but now I find that some of the more intensive games seem to slow down a bit now. Doesn't happen often but enough. Hopefully all this completely disappears once ICS is stable
I'm sure most know this on here but it seemed to be a new idea over at rootz.
Whenever the dinc freezes and locks up, instead of waiting for it to reboot on its own, hold power, volume down and then press the trackball. That should knock off those annoying wait times if you have a rom that like to randomly freeze.
Yep, the "Three Finger Salute". It's been around for a while.
Thanks bobAbooE. Learn something new everyday - even after power-using my Dinc for 2 years. I could never understand why the Dinc, a god of a phone, couldn't reboot without a battery pull or got that stupid Low Memory error. Well, I found the EXT4ALL memory solution a month or so ago, and now I find the 3 Finger Salute. It's a good universe we live in...
Sent from my ADR6300 using Tapatalk 2
I have owned this phone since day 1 and never knew this lol. Thanks.
I know this technique has been around for a while, 'cause I've seen references to the "3 fingered salute" before, but I never saw what it actually meant. Now that I'm getting into custom ROMs and have experienced a couple of random lockups, I'm glad to know this trick. Thanks for posting!
Wow, after two years of rooting my dinc this is the first time I have heard of this this reboot option.
First time I've run across this method of rebooting, useful info.
This is a great tip. Especially, if you have a Seido multipart case!
Good tip, I use this one all the time.
thought I knew everything about the Inc, but apparently not!! thanks!
Great tip. Never knew that you could reboot the incredible this way. Thx.
BTW, I briefly ran with the Touch of Blue GB ROM over the weekend, and it did not support this "3-fingered-salute" reboot method. (I also couldn't get it to boot into the Bootloader via the Vol-down+Power buttons, which I thought was a ROM-independent feature, but I tried it multiple times without success, so I dunno what was going on there.)
Now that I'm on Tiny's CM10.1, the buttons are back to working as expected both for reboots and boots.
MysticCobra said:
BTW, I briefly ran with the Touch of Blue GB ROM over the weekend, and it did not support this "3-fingered-salute" reboot method. (I also couldn't get it to boot into the Bootloader via the Vol-down+Power buttons, which I thought was a ROM-independent feature, but I tried it multiple times without success, so I dunno what was going on there.)
Now that I'm on Tiny's CM10.1, the buttons are back to working as expected both for reboots and boots.
Click to expand...
Click to collapse
It was fast boot mode on sense that caused this.
To expand upon this discussion, fast boot is also a feature in Sense starting with GB -- on by default -- that when enabled, allows the phone to boot up faster. Details unknown but with it on, the phone doesn't truly shut down so you can't access bootloader from an off position. It is likely what prevented you from doing the 3-finger-salute.