Database Develop

Backlight turns on, then after delay, message or call arrives

Hi everyone,
I've searched the forums through Google extensively trying to find out if anyone else is having the same problem that I am, but haven't been able to find any related threads.
I'm using the ATT Tilt with Dutty's WM6 ROM and the .17 radio -- I've noticed that when a text message arrives and my phone is in standby with the screen off, the backlight will turn on and then about 3-5 seconds later, the actual text message will show up on the screen or the call will show up...
I'm not sure if others are experiencing this and if anyone has a solution to it -- its not the end of the world if I have to live with it, was just hoping maybe someone else experienced the same thing and had found a solution...
Thank you very much!

Gas Addict said:
Hi everyone,
I've searched the forums through Google extensively trying to find out if anyone else is having the same problem that I am, but haven't been able to find any related threads.
I'm using the ATT Tilt with Dutty's WM6 ROM and the .17 radio -- I've noticed that when a text message arrives and my phone is in standby with the screen off, the backlight will turn on and then about 3-5 seconds later, the actual text message will show up on the screen or the call will show up...
I'm not sure if others are experiencing this and if anyone has a solution to it -- its not the end of the world if I have to live with it, was just hoping maybe someone else experienced the same thing and had found a solution...
Thank you very much!
Click to expand...
Click to collapse
I have this too....I don't really mind though. I see it light up on my desk, look down, and watch my email/message appear.
I'm on Dutty's v4 and .11

Same experience here.
As long as this isn't the case with telephone calls, I can live with it
Having a 5 second delay on answering a phone call could make you miss the call...

dont really se the problem tbh, the phne wakes up when it starts receiving the message and then notifies you when its arrived - the lag you observe must be simply he time it takes to download the message?

Happens to me every time. I see my phone light up, and know I'm getting a message. When I get a call it lights up and instantly shows who's calling.

I agree this isn't so much a problem. I see it as FAD (Functioning As Designed).
See what happens is the Tower Sends a signal to the Phone saying (Incoming Call/Message Heading your way). It Wakes Up checks its Registry for What you set your Ringtone as. Tower passes the Call and It Rings. You Hit the Green Phone and You are connected YAY!
Now Messages are a tad different. The Phone wakes up looks for what your Message Alert Tone is. Tower Passes the Message. The Phone saves it, makes it into a readable format (If you have Threaded SMS adds it to the proper thread) and Notifies you that all is ready.

Same here, I like it. I can pick up the phone before it makes sound and have the phone already in my hand when the msg is showing up.

no different than when my non-3g phones would start chattering with the pc speakers a few seconds before an incoming call or message.

same here
i see no problem in this

snathanb said:
no different than when my non-3g phones would start chattering with the pc speakers a few seconds before an incoming call or message.
Click to expand...
Click to collapse
I loved that!
Ducka-Duck-Ducka-Duck-
Ducka-Duck-Ducka-Duck-
Ducka-Duck-Ducka-Duck-
Ducka-Duck-Ducka-Duck-
RIIIIIIIIIIIINNNNNGGGGGG

OT but... iPhone users are suing apple over that btw b/c it's blowing out their expensive home theater speakers. (no shielding due to thin design = DUCKA-DUCK-DUCKA-DUCK instead of ducka-duck-ducka-duck)

Sleuth255 said:
OT but... iPhone users are suing apple over that btw b/c it's blowing out their expensive home theater speakers. (no shielding due to thin design = DUCKA-DUCK-DUCKA-DUCK instead of ducka-duck-ducka-duck)
Click to expand...
Click to collapse
Nuh uh. Lol, when I had my iPhone I had no chattering at all, only on crappy speakers.

Sleuth255 said:
OT but... iPhone users are suing apple over that btw b/c it's blowing out their expensive home theater speakers. (no shielding due to thin design = DUCKA-DUCK-DUCKA-DUCK instead of ducka-duck-ducka-duck)
Click to expand...
Click to collapse
Yes I had a friend who went to the dark side and had a iPhone It was indeed LOUD. Never thought of suing Apple for it.
~~Tito~~ said:
Nuh uh. Lol, when I had my iPhone I had no chattering at all, only on crappy speakers.
Click to expand...
Click to collapse
Well Think about that statement how many iPhone users are smart? Most are trend followers and don't know much about speakers probably got sold to them by some "winner" at Big Buy.

I have the same problem.

on mine too, but only for messaging.

Same problem for messaging and calls. I pretty think this glich is for all HTC phones. Seen this on HTC touch too.

I've had many different PDA phones over the last five years and used many different cooked ROMS (starting off with the original WM2003) and this has always been the normal behavior. Must be by design.

Hmm, I dunno if its about being by design as much as it has to do with the fact that from wakeup to showing the message it takes much longer on a complex PDA than it does on a simple phone with no complicated programs or settings in it.
IMHO it seems that because of all the bulk of software running on a PDA with an OS and all, it just isn't as efficient at doing simple small tasks as a regular non-PDA phone is....which I guess is the price we pay for carrying little computers in our pockets rather than a simple phone.

Gas Addict said:
Hmm, I dunno if its about being by design as much as it has to do with the fact that from wakeup to showing the message it takes much longer on a complex PDA than it does on a simple phone with no complicated programs or settings in it.
IMHO it seems that because of all the bulk of software running on a PDA with an OS and all, it just isn't as efficient at doing simple small tasks as a regular non-PDA phone is....which I guess is the price we pay for carrying little computers in our pockets rather than a simple phone.
Click to expand...
Click to collapse
I would agree with that statement. My wife's razr lights up and rings instantaneously...but has the functionality of my big toe.

Alright Lets Put an End to this. this ISN'T a PROBLEM. Its how Phones Work If they are "asleep" or not in "Full Operation Mode" then it must "Wake" to fully operate the processes that are needed to do what it is asked. Start a Call, Receive a message, etc etc.
And just FYI, My Old V3 Razr would Turn on The Front screen a couple seconds before I received a message or a call.

Capacitive Button Responsiveness?

Recently, I've been considering getting a Nexus One, however, most of the reviews I read say that the N1's capacitive buttons are a little unresponsive. You must tap the upper half of the button as opposed to the bottom half of the button.
I've also read that some of the cyanogen roms have fixed this problem. Can anyone give me more insight on this issue?

I've never had a problem with mine.
I saw a review saying that they got in the way when typing w/ the onscreen keyboard, but I haven't even had that, and I'd like to think that I have pretty normal-sized fingers.

Some people have problems, others don't i personally haven't. I wouldn't consider it to be something important enough to sway me from a sale though.

Stock Rom had this issue. If you unlock your bootloader, all the kernels (and mods) available now have a fix for this, as well as a few other things.
Im sure when 2.2 update comes out this fix will be passed on to the stock version too (at least as far as im aware it hasnt already!?). So tbh this isnt an issue for you not to get a nexus one...also, there's no point getting a nexus one if ur too scared to unlock the bootloader!!

adam18488 said:
Stock Rom had this issue. If you unlock your bootloader, all the kernels (and mods) available now have a fix for this, as well as a few other things.
Im sure when 2.2 update comes out this fix will be passed on to the stock version too (at least as far as im aware it hasnt already!?). So tbh this isnt an issue for you not to get a nexus one...also, there's no point getting a nexus one if ur too scared to unlock the bootloader!!
Click to expand...
Click to collapse
Definitely! That's one of the biggest reasons why I want an N1. It has a good root and dev community and gets android updates first.
I just thought it'd be annoying to have to use a phone with crappy capacitive buttons, but I'm glad to hear that the problem has been fixed.
The only other thing I'm worried about is the dualtouch but it's most definitely going to get fixed in the next update.
Thanks to everyone for their input. I'll definitely be picking up an N1 soon

I have rooted and custom roms etc and I still hate the capacitive buttons with a passion. They are not nearly enough to topple the overall awesome that is the N1 but man I hate those things.

I only hate those buttons, when Nex is in my car mount!

adam18488 said:
Stock Rom had this issue. If you unlock your bootloader, all the kernels (and mods) available now have a fix for this, as well as a few other things.
Click to expand...
Click to collapse
Is this true? I've tried plenty of ROMs and kernels and I don't remember any of them changing the button sensitivity.
The best way to show off how frustrating the buttons can be is to give the phone to someone that's never played with it before and watch as they struggle to register touches on the buttons. The people that use the phone daily have recognized that the touchpad is above the button and never think about it any more.
It's very apparent as soon as you rotate the phone into a different position though.

PrawnPoBoy said:
Is this true? I've tried plenty of ROMs and kernels and I don't remember any of them changing the button sensitivity.
The best way to show off how frustrating the buttons can be is to give the phone to someone that's never played with it before and watch as they struggle to register touches on the buttons. The people that use the phone daily have recognized that the touchpad is above the button and never think about it any more.
It's very apparent as soon as you rotate the phone into a different position though.
Click to expand...
Click to collapse
I also haven't noticed any change in the sensitivity with different ROMs or kernels. For me though, sometimes if I hit right on top of the button it won't register. I am used to just tapping it a little above and it works everytime.
As others have said, this is definitely not a deal breaker for me or shouldn't be for any person IMO. This phone's pros far outweigh the cons.

The best way to show off how frustrating the buttons can be is to give the phone to someone that's never played with it before and watch as they struggle to register touches on the buttons. The people that use the phone daily have recognized that the touchpad is above the button and never think about it any more.
Click to expand...
Click to collapse
When someone is doing that you should just say that it has Finger print authentication technology

absolutely true and this was my discovery today (day 4 with n1). the buttons work fine if you cheat towards the top of the button area and overlap into the screen area.
that solved it for me.
resolved for me for now...

xboomer55 said:
absolutely true and this was my discovery today (day 4 with n1). the buttons work fine if you cheat towards the top of the button area and overlap into the screen area.
that solved it for me.
resolved for me for now...
Click to expand...
Click to collapse
Did you just buy your N1 from Google brand new?

Those buttons are a pain in the bum, but you get used to them, the bigger problem is if the phone gets too cold it starts mis-registering the touchscreen necessitating a reboot or a bunch of mucking around to fix it. This is the biggest annoyance with the phone for me, hopefully they fix the screen calibration in 2.2!
Almost swapped mine for a Desire, thinking less of doing so now, unless anyone can offer a good reason

I got my N1 straight from Google on day one, and I'm currently running CM 5.06
I find the capacitive buttons to be _awful_ if I tap directly on them it takes 2-5 attempts to get it to register.
However, I have found that if I swipe from the button down off the bottom of the button it registers ever single time.
I'm pretty convinced that the problem isn't the digitiser itself but in the driver that splits that section of the digitiser off. I believe it checks to see if there is upward movement before registering a button tap and if it does detect upward motion it cancels the tap event and forwards the event as a touch screen event. I also thing that because I have pretty big fingers any time I press the flattening of my finger registers as a slight upward motion.
If I could find the button "sub"-driver I'd be hacking at it right now.
Still, I wouldn't give up my N1.

SilentMobius said:
I got my N1 straight from Google on day one, and I'm currently running CM 5.06
I find the capacitive buttons to be _awful_ if I tap directly on them it takes 2-5 attempts to get it to register.
However, I have found that if I swipe from the button down off the bottom of the button it registers ever single time.
I'm pretty convinced that the problem isn't the digitiser itself but in the driver that splits that section of the digitiser off. I believe it checks to see if there is upward movement before registering a button tap and if it does detect upward motion it cancels the tap event and forwards the event as a touch screen event. I also thing that because I have pretty big fingers any time I press the flattening of my finger registers as a slight upward motion.
If I could find the button "sub"-driver I'd be hacking at it right now.
Still, I wouldn't give up my N1.
Click to expand...
Click to collapse
Just realized that!!
It does not get the upward movement
It gets: right, left & down
So this means, one could set different options for different directions...

hacker01 said:
Recently, I've been considering getting a Nexus One, however, most of the reviews I read say that the N1's capacitive buttons are a little unresponsive. You must tap the upper half of the button as opposed to the bottom half of the button.
I've also read that some of the cyanogen roms have fixed this problem. Can anyone give me more insight on this issue?
Click to expand...
Click to collapse
I have noticed no issues when holding the phone in my hands but the responsiveness is not that great if the phone is flat on a desk or a similar surface. I wonder what if anything the accelerometer may play a factor.

PrawnPoBoy said:
Is this true? I've tried plenty of ROMs and kernels and I don't remember any of them changing the button sensitivity.
The best way to show off how frustrating the buttons can be is to give the phone to someone that's never played with it before and watch as they struggle to register touches on the buttons. The people that use the phone daily have recognized that the touchpad is above the button and never think about it any more.
It's very apparent as soon as you rotate the phone into a different position though.
Click to expand...
Click to collapse
I dunna man, my 3-year-old daughter figured it out within a minute of getting my phone. I set her up in a game and she decided she wanted something else, so she messed with the capacitive buttons until she got out of the game. Once she had it once or twice (~5-10 seconds for her to figure out each time) it was pretty much instant after that. If a 3-yo can figure it out, I'm pretty sure it's not THAT difficult. Annoying, sure....but not difficult.

hacker01 said:
Did you just buy your N1 from Google brand new?
Click to expand...
Click to collapse
Yes. Direct from Google.

Wow there's definitely a good mix of answers. I thought that the newer batches of N1's fixed the capacitive button problem, but apparently not.
I guess there's not a definite answer. It seems the only conclusion you can make is that some N1's may still have the problem, some may not. Some can be fixed with custom roms and unlocking the bootloader and some cannot. Your results may very.
EDIT: After rereading some of the previous posts (more carefully. excuse my sleep deprived state lol), the capacitive button issue might actually be more of a feature than an issue. I've read similar posts about the capacitive buttons having that sort of "motion detection" thing to prevent accident presses. Hopefully for anyone still having the problem, you can reread some of the posts on this page and give their methods a try

I haven't had a problem with mine but I haven't had the problems most people say they have with the phone so I would recommend this phone to anyone that wants an android phone
-------------------------------------
Sent from my Nexus One

HTC One vibration sound

Picked up this phone just today and my god I love this phone to death but every phone comes with complaints. Most things arent big and will just take time to get used to but this one I cannot ignore. I love having the vibrate on keypress option selected and the HTC One when it vibrates makes this very unpleasant loose spring like sound whenever it vibrates. Am I the only one thats noticed this or is this every device?
Sent from my HTC One using xda app-developers app

many people do have this ... me too.... thats my second device and both of them got this crappy vibration sound...
i replaced it because of that .... but because of that i disabled every vibration functions on this phone to get rit of it ....
so i guess you have to live with it ... try to replace it and hope you get one with a good vibration motor or disable all vibrations

B-Man2005 said:
many people do have this ... me too.... thats my second device and both of them got this crappy vibration sound...
i replaced it because of that .... but because of that i disabled every vibration functions on this phone to get rit of it ....
so i guess you have to live with it ... try to replace it and hope you get one with a good vibration motor or disable all vibrations
Click to expand...
Click to collapse
Isnt that due to the OIS? Not sure about but all of my 4 Ones had that. The One of a friend also sounds like that. I´m ok with it.

shox22 said:
Isnt that due to the OIS? Not sure about but all of my 4 Ones had that. The One of a friend also sounds like that. I´m ok with it.
Click to expand...
Click to collapse
It's something you have to live with

shox22 said:
Isnt that due to the OIS? Not sure about but all of my 4 Ones had that. The One of a friend also sounds like that. I´m ok with it.
Click to expand...
Click to collapse
I'm sure there will be soon an option in custom roms to control vibration intensity, and put it to the value you like! it's only a matter of time, I'm sure!

[I'm sure there will I am currently facing the same issue with my replacement and thinking about replacing it again but hesitant because every device comes with its own minor defects, u only notice the alight clicking in a very quite environment and only on short vibrates such as when typing, but to be honest this is as perfect as it can get, everything seems to work with this device with no problems except this, and I might apply for a replacement and end up with a worst unit and another major issue, I have emailed HTC complaining about their quality control, cuz my first device had gaps and a tiny hair under the screen, my second device had a touchscreen problem and now this one which has a minor vibration sound.
The problem is I am too picky when it comes to this kind of stuff and a little ocd about them so I am positive that other people won't even notice the issue and even the repair tech might claim it's normal and in all devices. So yeah
my device is work related so giving it to them for 2 full days is kind of troublesome for me

add me to the list
I have had my HTC One for 2 days now. I too noticed this on mine. I just chalked it up to the phone being all aluminum case vs my old EVO was plastic/metal. I have a few other complaints too lol.
Ok the rants!
1. Why did you have to move all the buttons all over the place? Seems like every button is opposite to other android phones? Especially moving the power button to the far left? Who designed this? Must of been a left handed person. Come on at least compromise and put in the middle! Stupid!
2. Why limit to only 3 buttons at the bottom of the HTC one and in all actuality...you never enabled the "HTC" to be a button so we are stuck with 2! Most phones have at least 3! Again Stupid!
3. The Home button and back buttons. Ok maybe the person designed this drives on the wrong side of the road or goes in the exit door or something? The buttons need to be flipped in my humble opinion. Home first (left side) or at least in the middle, back button to the left or right sides. OH and bring back the quick access button!
4. Ok speaking of the "HTC" logo/button at the bottom. Why put in circuitry for it to be a button and then not enable it? Stupid #3!
5. The widgets for "Bluetooth", Wireless", "Mobile", and "GPS". Why light blue for the "on notification". Seems like a **** poor color choice. At least a green or red would be fairly noticeable considering the widget itself is blue? Hello.....great designing there.
6. The power button. More recessed then ever before making it difficult to push down or even find. No step up here.
7. Lock screen can only have 1 widget on it? Really? Wow...couple steps back here.
8. Full animated weather locking screen gone/no longer available because HTC forces you to use their one and ONLY ONE version their crappy line art weather on the lock screen. I don't mind the plain jane weather for showing up in the app list but placing it on the bottom of the lock screen with nothing else is horrible. I want my weather back to the lock screen. I know I have mentioned it a lot...sorry pet peeve, have it it so long on all my other phones.
9. I won't mention Blinkfeed. I have that pushed off the side and hear that sense 5.5 is around the corner which will allow you to finally turn the damn thing off.

Hey guys, I wanted to point out that you can reduce the vibration intensity, therefore getting rid of the "springy" feeling! Just download FauxClock. (Yes you need root of course). Gratefully this app doesn't require you to flash anything, it just needs BusyBox. The only downside to reducing the intensity is after so far you basically lose haptic feedback. (I wanted to reduce notification buzz.) And this is where I went with plan B.
Plan B (NO ROOT!): This method, you guys, will make you feel real dumb for not thinking of. Personally I did this to get rid of notification buzz but keep haptic feedback, but you can also just turn off buzz on certain apps. Simply open up App-ops on Android 4.3, go through all your apps, and untick the "Vibration" permission! That's it guys! Feel dumb now?
Note: to open App-ops is an activity, you can download App-ops launchers from Play Store or, in my case, I used a Tasker task.
--
<<< Say thanks if I was of help! :good:

[Q] Z3c screen response very poor

Hi guys! All new to this site. I just got a z3c and everything is really great, but for 2 things:
The screen response is so poor, that if it can't be fixed, I'm returning it. Deal breaker.
Whenever I tap something, the screen responses in about 1 second. That is too long. Way too long.
Any of you tried the "Don't tap the white tile" app? (it's a game, where you have to be fast on your fingers) If you have (or you think, that your phone is NOT slow, please give it a go)
The swiping seems to be ok, it's the tapping that's delayed!
I'm hoping that it's just my phone and it can be replaced, 'cause otherwise I will have no choice, but to find another one.
Also is it not possible for me, to decide wether or not an app can have acces to internet? On iPhones you can manually dissable every app from using the internet, both wifi and regular. This can also prove to be a deal breaker for me.
I hope you can help me to find out if I should keep this, apart from that stuff, really wonderful phone or if I have to go back to iPhone, which I don't want to actually.
Regards Kokinos, Denmark

"Whenever I tap something, the screen responses in about 1 second." - that is definitely not normal. I am playing Wordz and screen response is instant.
There are many apps to control permission (e.g. Internet) for individual apps, but it requires root - APP OPS is the best. But you might try this, which works without root: https://play.google.com/store/apps/details?id=com.netspark.firewall&hl=en or this: https://play.google.com/store/apps/details?id=com.gmail.permissionmanager&hl=en

davebugyi said:
"Whenever I tap something, the screen responses in about 1 second." - that is definitely not normal. I am playing Wordz and screen response is instant.
There are many apps to control permission (e.g. Internet) for individual apps, but it requires root - APP OPS is the best. But you might try this, which works without root:
Click to expand...
Click to collapse
Thanks a lot, Dave! I'm so pleased to hear that, I will take it to the store and ask for a replacement then
-funny thing is, if I tap really hard, as in so hard the pixels round my finger turn black and I'm holding on to the phone with the other hand so tight, that it's on the verge of breaking, it IS possible to get the phone to react a, almost, once.
But swipe seems to work alright. I can't understand that. I actually thougt it was a software flaw and not a hardware one. But maybe I'm wrong.
I'll read into your links. My boyfriend might be able to understand a little more of it, so he'll help me

Nobody, that have noticed a delay on tapping, but not swiping?
Anybody I can convince to try the "Don't tap the white tile" game? It's free. I can play it fine on a iPhone, but on my Z3c the screen doesn't react fast enough. Unless I tap so hard, the pixels around my finger turn black and that can't be healthy for the phone.
It's not, that this game is important, it's just, that it shows very accurate, wether your sceen has delay or not.

That white tile game is the piano kind of game from Cheetah game studios? In case I just tried it and no issues with the screen response while tapping. It's more likely that you have a faulty device :/

davebugyi said:
That white tile game is the piano kind of game from Cheetah game studios? In case I just tried it and no issues with the screen response while tapping. It's more likely that you have a faulty device :/
Click to expand...
Click to collapse
Yes it is, and thank you SO much, Dave, you have been so helpfull :victory:
Yay, I'm so glad I don't have to find another phone, I will go and have this replaced :victory:
Thank you!

Kokinos said:
Thanks a lot, Dave! I'm so pleased to hear that, I will take it to the store and ask for a replacement then
-funny thing is, if I tap really hard, as in so hard the pixels round my finger turn black and I'm holding on to the phone with the other hand so tight, that it's on the verge of breaking, it IS possible to get the phone to react a, almost, once.
Click to expand...
Click to collapse
I cant imagine why your phone isnt working properly , cross your fingers the store you are trying to return it to doesnt read this forum.

jarayn said:
I cant imagine why your phone isnt working properly , cross your fingers the store you are trying to return it to doesnt read this forum.
Click to expand...
Click to collapse
Thanks for your not so helpfull comment. I would certainly NOT have pressed that hard, if it weren't for the fact, that I either would return it or have a replacement. Luckily I'm located in Denmark. We have excellent consumer rights. Otherwise I would be stupid to have done so.

[Q] Anyone else having a hard time with phone calls on their N6?

For the life of me I cannot use my N6 no-handed, even for just a moment. The 5-10 seconds I need to hold my phone up between my shoulder and my face to free both hands.......it never fails that I cause an issue with a live phone call. Obviously the larger screen (larger touch-sensitive area) and the screen being on for some reason during the call.......I always either put the phone call on hold, or even put the current call on hold and manage to dial one of my starred contacts. It is driving me up the damn wall. I am not a huge fan of the L phone interface (the starred favorites especially), I much prefer the KK layout.
Anyone else having as hard of a time as me? I'm wondering if the screen being off during the call would cure this. I guess I could manually cut it off when going to no-hands.......but figured it should do it on its own. Anyone care to either give me some suggestions, or even punch me for my ignorance and tell me what I am doing wrong?
Love everything about the phone, and also loving LiquidSmooth.......just hoping the development gets into high gear soon.

The screen is suppose to be off during calls, that's what the proximity sensor is for. Are you sure you are not hitting the power button while in call, i find it to be sensitive??If its not turning itself off when you put it up to your face, flash back to full stock. Still not working, then its probably a hardware issue???
Sent from my Nexus 6 using XDA Free mobile app

holeindalip said:
The screen is suppose to be off during calls, that's what the proximity sensor is for. Are you sure you are not hitting the power button while in call, i find it to be sensitive??If its not turning itself off when you put it up to your face, flash back to full stock. Still not working, then its probably a hardware issue???
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I forgot to reply I had this issue while stock as well. I wasn't looking to 'fix' this issue with a different ROM either, I just like the capabilities and development done in the ROM's themselves. Can't say I didn't hope something would change though.....

I only experience this with my left hand, LOL. Right handed, no issues with the screen turning off.

wilson289 said:
I only experience this with my left hand, LOL. Right handed, no issues with the screen turning off.
Click to expand...
Click to collapse
Well that is certainly odd lol.....
Anyone else? Surely I'm not the only one....... :silly: