Hello all,
I just got my AT&T Tilt and love it so far, except for one major annoyance. When I press the power button, the device will turn the screen back on after a few seconds to a few minutes. The problem is when it's in my pocket, it can accidentally call people. My 8125 and 8525 did not experience this issue.
Any suggestions?
Thanks!
Button lock
It sounds as though the phone isn't set to lock all buttons except the power button when it is in standby. This happened to me last time I re-flashed my Wizard, and I couldn't figure out for ages why my battery was draining so quickly as well!
Settings > Buttons > Lock
Hmm, not seeing any option under Buttons or Lock. I do remember this setting from WM5. It does appear, however, that the buttons are not turning the phone on, it's just waking up even if I leave it on a desk.
You can add lock to the home screen
first press and hold the hang-up button so that it locks. Then just push the power button once. This puts it in standby.
There is a idle timeout for going on standby mode, but I can't find a setting to auto-lock.
JBHorne said:
When I press the power button, the device will turn the screen back on after a few seconds to a few minutes.
Click to expand...
Click to collapse
Are you paired to a Bluetooth device? I see similar behavior in my 8525 when in my car - the BT car kit does stuff which "wakes" the 8525
Richard
Try this leaving Google Maps On the Screen
Hi Guys,
I get this behavior when I have Google Maps running. It will even cycle the screen on and off a couple times.
nope and nope. just sitting on the today screen.
JBHorne said:
When I press the power button, the device will turn the screen back on after a few seconds to a few minutes.
Click to expand...
Click to collapse
I have the very same problem.
However, my girlfriend whom I also bought a Tilt for, her's doesn't do it.
We've installed all the same software too, so I'm a little puzzled.
start>settings>system> key lock. set it to lock all buttons except power.
rzanology said:
start>settings>system> key lock. set it to lock all buttons except power.
Click to expand...
Click to collapse
Hmmm.. yeah, umm my key lock is already set to lock all buttons except power.
The problem isn't with when you press a button it comes on. The problem is the phone turns on by itself, sitting on a table, nothing being pressed, no new email, no new sms, just lights up and that's it.
JonRick said:
Hmmm.. yeah, umm my key lock is already set to lock all buttons except power.
The problem isn't with when you press a button it comes on. The problem is the phone turns on by itself, sitting on a table, nothing being pressed, no new email, no new sms, just lights up and that's it.
Click to expand...
Click to collapse
Any number of applications might be starting the device, from weather apps to calendar, diary, time sync etc etc. For example, HTCs weather app will do it depending on how often you have it set to another example I came across from someone was TREO ALERTS that contains a script "refresh.mscr" and it was set up refresh time 30 seconds (this was turning his TyTn II on by itself).
Mike
hard reset and try again.
i'm betting that none of these suggestions were helpful (except the one about some application generating a wakeup event without any other visual notifications).
i was having the same problem, but i just tried to narrow down which running program was causing the events. it's one of:
* wireless manager
* messaging
* IM
my guess is IM; i'm going to test that out in a second.
well, it's none of the above. still seems to wake up randomly anywhere from 15 seconds to several minutes.
seems to happen more frequently when it's just been turned off.
Even if you were to find what was turing the phone back on, this can still be a problem just from normal use... obviously, you WANT the phone to turn on for things like a call coming in. The solution for people like us who stick our phones in our pockets is to "lock" the phone. But for whatever reason, the Tilt doesn't lock the phone while holding down the end key. That means the only convenient way to lock it is to keep the lock function on the today screen, wasting space. Hopefully someone can find a way to allow the end key to lock the device on the Tilt just like the unbranded device.
dscline said:
Even if you were to find what was turing the phone back on, this can still be a problem just from normal use... obviously, you WANT the phone to turn on for things like a call coming in. The solution for people like us who stick our phones in our pockets is to "lock" the phone. But for whatever reason, the Tilt doesn't lock the phone while holding down the end key. That means the only convenient way to lock it is to keep the lock function on the today screen, wasting space. Hopefully someone can find a way to allow the end key to lock the device on the Tilt just like the unbranded device.
Click to expand...
Click to collapse
i'm fine with using the lock function, but it still turns on randomly, using battery, and eventually unnecessarily yellowing the screen from backlight aging. my next approach is to check out the notification queue, using a notification cleaner app.
So i am having a similar problem. When i press the power button, the phone's screen turns off but when the keyboard slides, it turns back on... is there a way to make it so the keyboard sliding does not turn on the device? I think the keyboard slides around a little when in my pocket and i hate pushing 3 buttons to unlock my phone... thanks
I was having the same problem.
This is an issue with the ATT rom. Flash over HTC rom and you will be all set.
I have been having the same problem as well. I just installed this DeviceLock program:
http://forum.xda-developers.com/showthread.php?t=305402
If you enable the "Lock on Wake" option, the device will be locked when it wakes up, so the backlight stays off and you won't call anyone by accidentally hitting buttons.
Also, I ran across this related thread you might want to check out (basically talking about the same thing, but for the TyTn II):
http://forum.xda-developers.com/showthread.php?t=341419
Does anyone have experience in configuring FakeCursor?
I've kind of got it to work so far, I've assigned a hardware button to launch FakeCursor via it's shortcut, however when I press the button again to turn FakeCursor off it always goes back to the Home screen, which is annoying.
What I'd like to be able to do is just have one button which turns the cursor on and the same button to turn it off? Any ideas how I could get that configured?
Cheers
try sphelper, this is i think better...
darksider said:
try sphelper, this is i think better...
Click to expand...
Click to collapse
SPHelper doesn't work with TomTom at all.
Mark Hewitt said:
Does anyone have experience in configuring FakeCursor?
I've kind of got it to work so far, I've assigned a hardware button to launch FakeCursor via it's shortcut, however when I press the button again to turn FakeCursor off it always goes back to the Home screen, which is annoying.
What I'd like to be able to do is just have one button which turns the cursor on and the same button to turn it off? Any ideas how I could get that configured?
Cheers
Click to expand...
Click to collapse
I have it mapped with Long_Home.lnk. The cross-hairs will appear for a second, then disappear and only reappear when you move it (with the directional pad).
Hold home to turn it on, hold home to turn it off (it will put you back on the home screen when it exits, this is a [poor] function of FakeCursor).
bigflavor said:
I have it mapped with Long_Home.lnk. The cross-hairs will appear for a second, then disappear and only reappear when you move it (with the directional pad).
Hold home to turn it on, hold home to turn it off (it will put you back on the home screen when it exits, this is a [poor] function of FakeCursor).
Click to expand...
Click to collapse
That's exactly how I have it configured . I was wondering if there was a way it wouldn't dump you back to the home screen, but it seems not?
Mark Hewitt said:
That's exactly how I have it configured . I was wondering if there was a way it wouldn't dump you back to the home screen, but it seems not?
Click to expand...
Click to collapse
I'm pretty sure that is a function of FakeCursor, not the mapping. It would be nice, but FakeCursor hasn't been updated for several years.
I had installed Doodle Jump on my Tilt, and it worked fine all day. Then I was with my girlfriend and wanted to show it off because she didn't believe me.. so I tap the screen.. it loads up.. i play for like 10 seconds to prove it to her, then i press the End key and exit out of it, then LONG-press the End key to lock it.
10 minutes later, press the power button to wake it up, try to tap Unlock..
and nothing???
took the battery out, soft reset, and still nothing.
finally figured out how to unlock it with the keyboard, then uninstall Doodle Jump, soft reset.. still no response.
[EDIT]
I was scrolling through the settings, about to Clear Storage and reset to default, and all of the sudden I tap the screen and it responds.. so it works now??
but I think it's a hardware issue, when I slide the keyboard out and tilt the screen, touchscreen doesn't work.
re-flash???
and i thought doodle jump required a G-Sensor or is is touch version if so can you post the link???
Hi guys, I just got my new replacement Bell Samsung galaxy S and have gotten things running on it again, but the damn thing keeps going into some weird screen capture.
What happens is that when I hit the "back" button it will go dark and the "menu" button will light up. repeatedly hitting the back button will do nothing, and hitting the menu button will do nothing. Pressing the center "home" button will take a picture of what I have displayed on the screen.
I go and check my running applications and it shows this "screen capture service" running. I stop it and then I continue on what I'm doing and it happens again, going back to the running apps and it is back.
The only way it seems I can use my "back" button is if i hit the "volume" button on the side and then both the "back" and "menu" buttons will light up, and then I have to wait until they both go dark before I can hit the "back" button and have it work. if I hit it will they are lit up it goes back into the screen capture "mode"
The phone came in the mail with I9000UGJL2, firmware 2.2.
Any advice on how to permanently kill that damn screen capture thing would be greatly appreciated because it is driving me nuts. I get a way with maybe 2 "back" button pushes where it works and then it goes into that mode
Same problem...
Samsung Galaxy S i9000 (Facinate)
It seems that by pressing the back button too quickly puts you in the Screen Capture mode...Back button dims but the Menu button stays lit. I found that if I push the Home button that take s the screen shot, then wait for both the Menu and Back button to come on and then lowlight, I can then hit the back button and continue on for a while?
Package name: com.sec.android.app.screencapture
Source: /system/app/ScreenCaptureService.apk
Please, I would like to find out more about this app in order to try and control it. It really slows moving back when you have to wait for the Menu and Back buttons to lowlight before you can hit the back button again!
Just after posting the above, I was able to Force Stop the package and I have not had a problem with the phone going into screen capture mode since.
Woohoo!
My i9100 built-in Screen Capture Service default output is png format. How can I change it to jpeg format?
I've been having an issue with my soft keys pressing themselves randomly and repeatedly. Menu options pop up and ill press menu to make em go away and seconds later they'll pop up again, and again. The one that blows me up most is when it presses home, *%#@! Anyone having the same issue, anyone have any advice, anything?
Now I'm so broke i can't even pay attention!