Database Develop

TyTN II waking randomly

Hey everyone
Has anyone else noticed that their TyTN II wakes from standby when switching between GPRS and 3G. At least I think this is why mine appears to wake up randomly! It will be sat on my desk in standby mode and then the screen will switch on and the signal strength bars will move.
I've checked to make sure nothing is running in the background and performed a soft reboot.
Any ideas?

Hi
The Kaiser does turn on at least once every hour (some house keeping tasks), and will turn on if the mobile signal is lost. However these on's are in unattended mode which means the device appears off to the owner so the screen will not come on.
If you have some software that likes to do work or updates the today page for example, that software may be detecting the device has turned on and in order to get your attention or just through bad programming, issues a power announcement to say turn on proper, hence the display lights up!
Regards
Phil

Thanks for the info, I'll have a look what I have on there and try and isolate what is causing the power ups.
Cheers for the help.

If you have sprite backup installed with the auto backup on low power option that causes occasional power ups to enable the power check.

I may have solved this issue. After uninstalling enAlarm the phone, no longer appears to be waking. I'm still monitoring it though

i have the same problem when im signed on to AIM. Once i sign off it stops waking up, but if its on it'll wake up every 5 minutes or so, and it is in fact annoying. Havent found out the solution for it yet so i just dont really use it that often

nando223 said:
i have the same problem when im signed on to AIM. Once i sign off it stops waking up, but if its on it'll wake up every 5 minutes or so, and it is in fact annoying. Havent found out the solution for it yet so i just dont really use it that often
Click to expand...
Click to collapse
it's when a friend log's in or out of AIM.. it's a paint, rediculious and ATT refuses to get rid of OZ messanger and use a real one.
here's the kicker. it supposed to use TEXT , but when a friend logs in or out, the message is sent to your phone, and then DATA brings up the list..
STUPID and ignorant of ATT but,. big companies do what they want!

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 Tilt):
http://forum.xda-developers.com/showthread.php?t=335433

While on Call: Face keeps hitting Mute, etc.. HELP

I thought the screen shuts off when you're in the middle of a call (proximity sensor?). On the iPhone, when you're in the middle of the call, it shuts the screen off when its by your face just so you don't hit anything like mute, etc...
Any way to get around this? Thanks

Legaleye3000 said:
I thought the screen shuts off when you're in the middle of a call (proximity sensor?). On the iPhone, when you're in the middle of the call, it shuts the screen off when its by your face just so you don't hit anything like mute, etc...
Any way to get around this? Thanks
Click to expand...
Click to collapse
Mine shuts off the screen when your face is close to it.
Settings -> Call Settings, do you have Keep screen awake checked?

I don't see that option. Settings, then call settings... I see voicemail, call forwarding... That's pretty much it. Running Stock 2.1

Mine has done this a couple times now,i'll be talking to someone and all of a sudden start hearing beeps as if hitting the numbers on the keypad. First time it happened I thought it was the person on the other end but it happened again last night and I looked at the phone after I got off the call and it had #2* or something like that in the dialer so something is definitely weird here.

bluehaze said:
Mine has done this a couple times now,i'll be talking to someone and all of a sudden start hearing beeps as if hitting the numbers on the keypad. First time it happened I thought it was the person on the other end but it happened again last night and I looked at the phone after I got off the call and it had #2* or something like that in the dialer so something is definitely weird here.
Click to expand...
Click to collapse
are you using a screen protector/skin/case ... anything?
mine has never given a problem.
so far.

Maybe you have a really skinny head that's not passing the sensor?

nmesisca said:
are you using a screen protector/skin/case ... anything?
mine has never given a problem.
so far.
Click to expand...
Click to collapse
Nope, I imagine this will happen to everyone at some point though. It doesn't happen very often, it just out of the blue will happen one day. I guess the more you talk on the phone the more likely you will be to eventually experience it Maybe it has something to do with enabling the keypad? As that is what I did last night to punch in an extension.

This problem happened with my gf, when she had a droid. For some reason while she was talking on the phone the screen wouldn't always stay off and she would bump the on screen buttons with her cheek and end up usually trying to add a new caller to the call, thus muting whom she was talking to. She also had a lot of problems with the Capacitive touch screens, it wouldn't register half the time where she touched.
I've never had this happen to me, I doubt it actually will. It must be something related to how we hold our phones, and where it lines up to peoples differently shaped heads.

bofslime said:
This problem happened with my gf, when she had a droid. For some reason while she was talking on the phone the screen wouldn't always stay off and she would bump the on screen buttons with her cheek and end up usually trying to add a new caller to the call, thus muting whom she was talking to. She also had a lot of problems with the Capacitive touch screens, it wouldn't register half the time where she touched.
I've never had this happen to me, I doubt it actually will. It must be something related to how we hold our phones, and where it lines up to peoples differently shaped heads.
Click to expand...
Click to collapse
Never happened to me in 2-3 years with the Iphone. To act like it is happening because we are holding the phone wrong is a bit absurd, I mean it's not exactly a complicated process I will try and figure out what's happening, haven't paid much attention to it yet because I figured it was a fluke but it happened twice now and is happening to other people.
One thing I noticed last night was the phone screen was still blacked out while the beeps happened so it's not a sensor thing the screen is actually blacking out it's just being activated again by something that happens after it's off I assume.

I'm not using a case or anything. It NEVER happened to me with the iPhone, but it happens quite often with the Nexus One. VERY annoying... It should be like the iPhone, where when its by your face, it shuts off the screen AND disable the touch buttons below the screen.
I think its the touch buttons causing the problem... Because my screen does turn off when its by my face.

Legaleye3000 said:
I'm not using a case or anything. It NEVER happened to me with the iPhone, but it happens quite often with the Nexus One. VERY annoying... It should be like the iPhone, where when its by your face, it shuts off the screen AND disable the touch buttons below the screen.
I think its the touch buttons causing the problem... Because my screen does turn off when its by my face.
Click to expand...
Click to collapse
This is the behavior I experience with my nexus one (stock and custom roms). As soon as I place it near my face the proximity sensor turns off the screen.
The capacitive buttons below the screen are disabled when the screen turns off for me as well. I just called in to voice mail and hit every one while the screen was off due to the proximity sensor, not a single response from any button or the screen and no change in call status when I moved the phone away and the screen came back on.

krohnjw said:
This is the behavior I experience with my nexus one (stock and custom roms). As soon as I place it near my face the proximity sensor turns off the screen.
The capacitive buttons below the screen are disabled when the screen turns off for me as well. I just called in to voice mail and hit every one while the screen was off due to the proximity sensor, not a single response from any button or the screen and no change in call status when I moved the phone away and the screen came back on.
Click to expand...
Click to collapse
Yea it's some kind of fluke, It happens so randomly I am thinking it might be something to do with the internet connection like checking mail or maybe the GPS doing something that wakes up the buttons while the proximity sensor keeps the screen off because everything will be fine then all of a sudden it happens while the screen is still blacked out.

Sounds like a factory reset might fix this issue... definitely not normal behavior.

I think this is happening to a bunch of people. I don't think a factory reset would help. I think its a bug...

uansari1 said:
Sounds like a factory reset might fix this issue... definitely not normal behavior.
Click to expand...
Click to collapse
No it's not a normal behaviour you are correct however it's not anything a factory reset is going to fix either. It's some kind of software bug that once enough people experience it will get sorted, just a matter of time before enough people start complaining to bring it to attention of Google or HTC.

bluehaze said:
Never happened to me in 2-3 years with the Iphone. To act like it is happening because we are holding the phone wrong is a bit absurd, I mean it's not exactly a complicated process I will try and figure out what's happening, haven't paid much attention to it yet because I figured it was a fluke but it happened twice now and is happening to other people.
One thing I noticed last night was the phone screen was still blacked out while the beeps happened so it's not a sensor thing the screen is actually blacking out it's just being activated again by something that happens after it's off I assume.
Click to expand...
Click to collapse
Are you accidentally hitting the volume buttons on the side of the phone? It sounds like you might be turning the in call volume down, thus leading to it being muted.

^^ No... My face actually hits the mute button. I then have to click the mute button with my finger once i realize the person can't hear me and then they start hearing me again after I click it.
It happens with other buttons on the screen too.

Legaleye3000 said:
^^ No... My face actually hits the mute button. I then have to click the mute button with my finger once i realize the person can't hear me and then they start hearing me again after I click it.
It happens with other buttons on the screen too.
Click to expand...
Click to collapse
Figured I would ask... I sell cell phones, and I get about 1 person a day in that has muted their in call volum by accidently hitting the volume toggle button without knowing it... all different phones (BB's are the worst!).
Anyways, my proxy sensor works perfect! I even just tested it a bit, and it senses a single finger tip starting about 1" away from the screen anywhere along the top of the screen... worked on both the left and right side and everywhere in between just fine.
I use my phone a lot at work in call (calling in to CS, calling the manager, etc) and have not had a single proxy sensor issue in the week I have had my phone.

bluehaze said:
No it's not a normal behaviour you are correct however it's not anything a factory reset is going to fix either. It's some kind of software bug that once enough people experience it will get sorted, just a matter of time before enough people start complaining to bring it to attention of Google or HTC.
Click to expand...
Click to collapse
May not be normal, but its not a bug that seems to be effecting all phones. Same thing that not everyone is experiencing random touch events, 2g/3g toggling, or dust/dogfooding. To say every phone has this problem because you do is simply short sighted.

bofslime said:
May not be normal, but its not a bug that seems to be effecting all phones. Same thing that not everyone is experiencing random touch events, 2g/3g toggling, or dust/dogfooding. To say every phone has this problem because you do is simply short sighted.
Click to expand...
Click to collapse
LOL shortsighted eh? It's a bug it will happen to more and more people eventually and you will see, i'm sure it will happen to you eventually as well. Only thing shortsighted is your reply.
Good day to you sir.

[Q] Active Display turns on when phone is moved.

This might seem like a dumb question but whenever I set my phone down and it is moved even in the slightest the Active Display lockscreen turns on. Is there anyway possible to disable that?

That's the cool thing about this phone. Don't worry about it

Chronos300 said:
This might seem like a dumb question but whenever I set my phone down and it is moved even in the slightest the Active Display lockscreen turns on. Is there anyway possible to disable that?
Click to expand...
Click to collapse
You will get used to it and come to love it. the great thing is that it doesn't adversely effect your battery, it uses the special built in processors. I thought it was weird at first but now I just tap my phone or bump the table to see my notifications.

I love it because I never have to push the power button to turn my device on. This is a great way to save wear and tear on your power button. A lot of devices that rely on one button all the time (power button) end up with that button not working anymore. If I didn't have this option I would be using my volume rocker to power up my phone.
Sent from my XT1060 using Tapatalk

This is easily my favorite feature about the Moto X. All I gotta do is pick up my phone and it automagically shows me any notifications and is ready to be unlocked. Power button? What's that?
Sent from my Nexus 5 using XDA Premium 4 mobile app

I like this feature. I usually tap my finger on the screen or press off to one side so the phone rocks slightly on the curved back to get the display to come on. As someone else said, it saves a lot of wear on the power button. I can't tell you how often I clicked my Razr Maxx on just to see what time it was, and clicked it off again immediately. The button never wore out, but it's nice not having to do it at all.
I do have a question though. I got the phone on Wednesday and didn't notice this at all until this morning, and I don't know if it's normal or not. While getting ready for work this morning I noticed the Active Display fire on and off a few times in a row. I thought since it was right at 7am that I may have gotten a few emails close together or something, and didn't worry about it.
When I got to work I set my phone on my desk and was reading emails and such and I noticed the display puling on and off about every 5-6 seconds. It fades in, holds for maybe 1 second and fades out. It only had one notification, for Plume (Twitter), which only polls every 15 minutes in the background, so I knew it wasn't getting new notifications repeatedly.
I can't remember if this was happening yesterday and I just opened it up right away to see what it was for, or if something actually changed. I disabled Plume from the Active Display list, which didn't change anything, I got the same result for email (Maildroid) and Snapchat.
I guess it kind of makes sense that it repeats, as there is no LED on the phone, but it seems a little excessive. I don't know how much power is saved by using white on black in the small area of the screen, but it's bugging me a little because I don't remember it doing this before.
Thanks for any input anyone has on this...

fury683 said:
I guess it kind of makes sense that it repeats, as there is no LED on the phone, but it seems a little excessive. I don't know how much power is saved by using white on black in the small area of the screen, but it's bugging me a little because I don't remember it doing this before.
Click to expand...
Click to collapse
It's normal. When you have a notification, the screen pulses instead of having a notification LED.
I haven't measured it, but it's my impression that it slows down the pulsing if the phone sits quietly for a while after the notification happens (I seem to notice that, if I ignore the notification, I don't see it as much). It really uses almost no battery, though, so don't worry about it.

Does the phone always light up when driving? I don't remember it happening on my old X but it's lights up at every bump on my new X.
Thinking I've frozen something I shouldn't have. Did not use assist on either phone.

binary visions said:
It's normal. When you have a notification, the screen pulses instead of having a notification LED.
I haven't measured it, but it's my impression that it slows down the pulsing if the phone sits quietly for a while after the notification happens (I seem to notice that, if I ignore the notification, I don't see it as much). It really uses almost no battery, though, so don't worry about it.
Click to expand...
Click to collapse
Thanks for the quick reply. I'm guessing yesterday I either cleared them quickly, or they were present long enough to go slower and I didn't notice the repetition.
I will have to play around with what I actually want notifications for. Plume (Twitter) is the worst, followed by email. I wish I could turn on different channels for Plume so that Mentions/DMs could go to Active Display, but regular tweets didn't, but still have it do all in the notification shade. I might have to just settle for not getting a notification for all new tweets. Or increase my poll time...
Email might get shut off too. I get too much spam to care, and rarely get any emails that are urgent enough to warrant it.

Yes, mine lights up when driving Lol. The second I press on the gas it lights up, tripped me out the first few days owning the device, but I'm used to it now.
Sent from my XT1058 using xda app-developers app

[Q] Screen on

Hey Z3c owners,
After an upgrade to LP-5.0.2, my screen acts weird. When phone is locked time to time screen comes on and does not turns off automatically, despite that my screen timeout is set to 30 seconds.
I have no idea what is causing that, thought that I could be triggered by notifications but after few test this idea felt.
Anyone has similar issue? Or any thoughts how to find whats triggers that screen on, and does not allows it to turn off?
Thanks

Info
Exris said:
Hey Z3c owners,
After an upgrade to LP-5.0.2, my screen acts weird. When phone is locked time to time screen comes on and does not turns off automatically, despite that my screen timeout is set to 30 seconds.
I have no idea what is causing that, thought that I could be triggered by notifications but after few test this idea felt.
Anyone has similar issue? Or any thoughts how to find whats triggers that screen on, and does not allows it to turn off?
Thanks
Click to expand...
Click to collapse
have u test factory reset? OR Repairing fimrware by PC Companion?
IF not do it and write the result
:good:

Geeks Empire said:
have u test factory reset? OR Repairing fimrware by PC Companion?
IF not do it and write the result
:good:
Click to expand...
Click to collapse
It's will be last what to do, if wont find any other solution.
For now I will be disabling downloaded apps one by one, may be one the apps is triggering screen.

Notification sound cut off, now screen won't turn on

Since updating to marshmallow, my longer notification sounds, especially Calendar Snooze, are cut off.
I read somewhere about an app setting to allow it to turn the screen on as a fix. I did that but now I can't remember what app I made the change in or where I read that suggestion. I thought it might have been Light Flow, but I can't find it in there.
Now my power button fails to wake up the screen the majority of the time. Sometimes the lock screen will flash for a fraction of a second and go black again. Usually it takes 6-10 tries before the screen finally stays on so I can use my phone.
Since the wake up problem started when I tried to fix the notification sound, I'm pretty sure they're related. Any ideas?
Sent from my Nexus 6 using Tapatalk

JimSmith94 said:
Since updating to marshmallow, my longer notification sounds, especially Calendar Snooze, are cut off.
I read somewhere about an app setting to allow it to turn the screen on as a fix. I did that but now I can't remember what app I made the change in or where I read that suggestion. I thought it might have been Light Flow, but I can't find it in there.
Now my power button fails to wake up the screen the majority of the time. Sometimes the lock screen will flash for a fraction of a second and go black again. Usually it takes 6-10 tries before the screen finally stays on so I can use my phone.
Since the wake up problem started when I tried to fix the notification sound, I'm pretty sure they're related. Any ideas?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
if youre using lightflow id suggest wiping the data in it and resetting your notification settings. it does tend to override the system so i can see that screwing with the duration of the notification, and starting fresh usually solves most problems
i have mine set to wake the screen for SMS but not MMS. it creates similar problems with the screen

Thanks for the info. I tried just toggling the screen on settings on and back off for all of the Light Flow apps, and it seems to have fixed my screen turn on problem, at least for now.
Sent from my Nexus 6 using Tapatalk

I'm having the same notification sound cut short problem, I have a nexus 7 wifi 2013 model running Mohamed rom v2.1
Whenever anyone calls me on google hangouts, the ring only lasts for a second before its cut off, this doesn't happen if the front cover is open, it happens only when its closed.
I didn't have this problem on kitkat, but on MM this problem started from day 1.
I don't see any light flow option anywhere.
Any suggestions to fix this will be very appreciated.
Thanks.

A.Ahmed79 said:
I'm having the same notification sound cut short problem, I have a nexus 7 wifi 2013 model running Mohamed rom v2.1
Whenever anyone calls me on google hangouts, the ring only lasts for a second before its cut off, this doesn't happen if the front cover is open, it happens only when its closed.
I didn't have this problem on kitkat, but on MM this problem started from day 1.
I don't see any light flow option anywhere.
Any suggestions to fix this will be very appreciated.
Thanks.
Click to expand...
Click to collapse
LightFlow fixed my screen problems, but it was just a coincidence that I installed Marshmallow and my sounds got cut off around the same time. I'm still looking for a solution to that issue. Similar to you, if my screen is on, the notification sounds work correctly. If the screen is off, they get cut off.