Is it supposed to continuously flash even when there is nothing to report? My phone will flash an active notification so long as it is face up (then gain I can't tell when it is face down) even if there is nothing to report. It will just flash the key/lock pad.
I think it does that when it sense some sort of vibration and thinks the phone has been moved slightly. I noticed it when it was in my generic car dock while driving.
I think it's meant to do that in order to act as a sort of notification led. I personally like how it turns on occasionally so I can glance at it while it's sitting on a desk and see any notifications
Sent from my XT1053 using xda app-developers app
FSXv13 said:
Is it supposed to continuously flash even when there is nothing to report? My phone will flash an active notification so long as it is face up (then gain I can't tell when it is face down) even if there is nothing to report. It will just flash the key/lock pad.
Click to expand...
Click to collapse
Mine does that, although I think it has to be activated. It seems really sensitive to being moved at all (not a problem IMO since it doesn't use much battery). I don't think it is supposed to do that without it sensing some sort of movement though. I also find it helpful to just be able to glance over and see if I have a text.
mikeosu said:
Mine does that, although I think it has to be activated. It seems really sensitive to being moved at all (not a problem IMO since it doesn't use much battery). I don't think it is supposed to do that without it sensing some sort of movement though. I also find it helpful to just be able to glance over and see if I have a text.
Click to expand...
Click to collapse
Well if you have a text it should start flashing cause you have a text...
This is flashing even though there isn't anything to report. That's why I find it odd. There is nothing to report, so why is it flashing?
FSXv13 said:
Well if you have a text it should start flashing cause you have a text...
This is flashing even though there isn't anything to report. That's why I find it odd. There is nothing to report, so why is it flashing?
Click to expand...
Click to collapse
Because you bumped the phone and the accelerometer detected movement, and it thinks you may want to unlock the phone.
This is the feature that enables you to pick the phone up off the table and unlock it without pressing any physical buttons.
glitch003 said:
Because you bumped the phone and the accelerometer detected movement, and it thinks you may want to unlock the phone.
This is the feature that enables you to pick the phone up off the table and unlock it without pressing any physical buttons.
Click to expand...
Click to collapse
I did not bump the phone when it is lying face up on the marble counter or when it is on the corner of my desk well away from my keyboard and mouse.
Related
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
hi there. i bought this phone yesterday and it's great. i love it. best phone i've ever owned.
however i have a few niggling questions;
i find the touch buttons to be very difficult to see in sunlight. is there a way to brighten them? or are all the phones like this. my mother has a galaxy s and i feel her touch buttons are brighter.
is the power button meant to be so slim to the phone? i can find it hard to press sometimes.
secondly, how come my LED notification light only stays on for a short time when i receive a text? i would have thought it stayed on until the text was read, but when i get a text and don't notice for half an hour to an hour the LED isn't flashing. if i receive a text (and i'm there to notice it) the LED flashes. again, is this just my phone or everyones?
also, how safe is it to install the swype beta on your phone? and how safe is it downloading pdf's (accidentally, opened a link on a reputable train website) on to my phone over the 3G network?
and finally, not as important, but the standard version of angry birds seems to always lag/crash at startup. i don't know whether it's due to the ads, but i have to hit home before i am able to click 'start', and then the same again when the level loads up before i can move the birds. i've played rio and that seems fine.
OH, and one more thing. if i go from an area with good 3g reception to an area with poor 3g, and then back again, my phone takes a while to catch up, so i have to turn off mobile networks and then back on again to get 3g back. normal?
sorry for all the questions.
thanks. peace.
Hi there martyfly1990,
Congratulations on your purchase and I hope you'll enjoy your phone as much as everyone here!
I won't be able to answer all of your questions but I'll try to help you out the best I can:
i find the touch buttons to be very difficult to see in sunlight. is there a way to brighten them? or are all the phones like this. my mother has a galaxy s and i feel her touch buttons are brighter.
Click to expand...
Click to collapse
The Incredible S's capacitive buttons have a unique feature compared to other devices, they get to turn when you put your phone in landscape mode (only in one direction). In order to achieve this, they use a different method of illumination. What you may also notice is a kind of ghost of the buttons secondary positions beneath what is displayed in a round border if looked at at the right angle. However, it also gives the possibility to have nothing at all showing up when the lights are off giving it a cool look (I find ). Compared to other phones I've seen, I'd say that it's normal for the IS to have slightly less bright touch buttons.
is the power button meant to be so slim to the phone? i can find it hard to press sometimes.
Click to expand...
Click to collapse
The IS was given what some people call a very industrial look. Aside from the back cover, the phone is very minimal in the sense that nothing extrudes from it. The power as well as the volume rocker buttons are even the same colour as the body. All to give it that slab look. The volume rocker sticks close to the body too, and I'm sure your phone is perfectly fine. You'll get used to it
and how safe is it downloading pdf's (accidentally, opened a link on a reputable train website) on to my phone over the 3G network?
Click to expand...
Click to collapse
If you trust the source (and are sure that the file is indeed a pdf, there is no problem at all.
and finally, not as important, but the standard version of angry birds seems to always lag/crash at startup. i don't know whether it's due to the ads, but i have to hit home before i am able to click 'start', and then the same again when the level loads up before i can move the birds. i've played rio and that seems fine.
Click to expand...
Click to collapse
I will presume that your phone is still stock? I haven't had that problem with Angry Birds, but did you try uninstalling it and installing it back on? Worth giving a try.
OH, and one more thing. if i go from an area with good 3g reception to an area with poor 3g, and then back again, my phone takes a while to catch up, so i have to turn off mobile networks and then back on again to get 3g back. normal?
Click to expand...
Click to collapse
The reaction time not being immediate is normal, but how long do mean by "a while"? 10 seconds or 10minutes? I could only think of a radio problem if it's really bad. Could you share what version of android and what's your baseband version on your phone?
martyfly1990 said:
secondly, how come my LED notification light only stays on for a short time when i receive a text? i would have thought it stayed on until the text was read, but when i get a text and don't notice for half an hour to an hour the LED isn't flashing. if i receive a text (and i'm there to notice it) the LED flashes. again, is this just my phone or everyones?
Click to expand...
Click to collapse
I think that other question has been answered so i will skip it.
LED notification i will only last for 5 minutes, so far i haven found out any ways to stretch up the time until we read the message or any other notification.
I think they set it to only 5 minutes properly of the battery drain?
Hope its help.
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:
So, I've noticed a weird problem my RP2 has. I carry it in my hip pocket, and at times (happens frequently enough to be annoying) when I pull it out to use it, the screen doesn't respond to a normal touch. I have to really push down hard on the screen to get it to register. If I let it sit for a few seconds/minutes the touch responsiveness fixes itself and it can be used normally. Not sure if it could be a physical problem with the digitizer/connection or if something is going on when it is "asleep" in my pocket. Just weird that it fixes itself. Anybody else see anything like this or have a suggestion as to what it could be? The phone is totally usable, and even when it messes up it still works I just have to push super hard to get it to do anything. Sometimes i'm afraid I'm going to snap the glass, although I don't really think that is likely to happen. Thanks for any ideas.
Just to weigh in I also have this issue not very often but enough to notice it. Especially since the last update also when I zoom with the stock camera it just freezes.
I'm having similar issues, camera fixes if i reboot but thats annoying if your trying to get a moving shot, also noticed it sometimes freezes switching to portrait mode.
For the screen freeze I have found if i use my finger print to unlock when the screen isnt responding its starts to work. but i didnt have the problem until i put on a crappy glass screen protector.
I just got the phone and im using arters r2 kernel with f2fs on data, as well as magisk and xposed so i wasn't sure if it was something i did but since others are seeing it ill assume its something with the phone and see if theres any fixes or decide if i should return it.
godsfilth said:
I just got the phone and im using arters r2 kernel with f2fs on data, as well as magisk and xposed so i wasn't sure if it was something i did but since others are seeing it ill assume its something with the phone and see if theres any fixes or decide if i should return it.
Click to expand...
Click to collapse
Mine does that too, but I'm not on the new kernel. Maybe it has something to do with the ambient display being turned on.
jonchance_84 said:
Mine does that too, but I'm not on the new kernel. Maybe it has something to do with the ambient display being turned on.
Click to expand...
Click to collapse
hmm maybe, i only had show new notifications turned on but ill try turning it off and see how it goes over the next couple days
Ok so since turning off my ambient display, no issues so far.
karlkarloff said:
So, I've noticed a weird problem my RP2 has. I carry it in my hip pocket, and at times (happens frequently enough to be annoying) when I pull it out to use it, the screen doesn't respond to a normal touch. I have to really push down hard on the screen to get it to register. If I let it sit for a few seconds/minutes the touch responsiveness fixes itself and it can be used normally. Not sure if it could be a physical problem with the digitizer/connection or if something is going on when it is "asleep" in my pocket. Just weird that it fixes itself. Anybody else see anything like this or have a suggestion as to what it could be? The phone is totally usable, and even when it messes up it still works I just have to push super hard to get it to do anything. Sometimes i'm afraid I'm going to snap the glass, although I don't really think that is likely to happen. Thanks for any ideas.
Click to expand...
Click to collapse
I use Ambient Display and sometimes the screen behaves as you've described where it won't reach to touch, but I've always just given it time/pressed the power button repeatedly until the screen came on (or continued to tap the screen lightly)... never tried pressing down very hard.
Not to Necro a thread but I've experienced this aswell, infact it's happening right now as I type this.
In addition to "Do Not Disturb" when flipping the phone over, facing down. Is there a way to also immediately lock the phone?
You can hold the power down and select "Lockdown" (this has to be enabled in display settings first).
I need it to be automated when flipping the phone over. I often leave my phone at my desk and I don't want it to be immediately accessible.
garyHal said:
I need it to be automated when flipping the phone over. I often leave my phone at my desk and I don't want it to be immediately accessible.
Click to expand...
Click to collapse
What do you mean lock the phone? After a set amount of seconds it auto locks, face up or face down.
You are correct, the phone auto locks. I have it set to 15 seconds. I need the phone to lock immediately, regardless of the auto lock time.
garyHal said:
You are correct, the phone auto locks. I have it set to 15 seconds. I need the phone to lock immediately, regardless of the auto lock time.
Click to expand...
Click to collapse
Tap the power button and off it goes. If you are in a work environment where if you walk away for 5 seconds and your phone is at risk of being compromised either you need to find another job (lol) or never leave the phone on the desk. That's some serious personal insecurity right there.
The easy answer is something like Tasker to look at the gyro, ambient brightness and the proximity sensor but I don't know offhand if that requires root to lock your screen.
raynan said:
The easy answer is something like Tasker to look at the gyro, ambient brightness and the proximity sensor but I don't know offhand if that requires root to lock your screen.
Click to expand...
Click to collapse
Lol. That's easy? Easier than hitting the power button? This whole thread is silly.
bobby janow said:
Lol. That's easy? Easier than hitting the power button? This whole thread is silly.
Click to expand...
Click to collapse
If you're looking for a once-and-done solution, yes. But I am an automation freak
raynan said:
If you're looking for a once-and-done solution, yes. But I am an automation freak
Click to expand...
Click to collapse
Oh.. lol. I can't help you with that. I'm a practical guy. Physical as it were. Push the button. Make it happen.
bobby janow said:
Oh.. lol. I can't help you with that. I'm a practical guy. Physical as it were. Push the button. Make it happen.
Click to expand...
Click to collapse
That probably is the EASIEST answer, but if you can flip your phone to make it turn off sound, lock, and maybe launch the sound recorder (for example), you have a discrete, potentially automatic meeting transcriber that's pretty much thoughtless.
raynan said:
That probably is the EASIEST answer, but if you can flip your phone to make it turn off sound, lock, and maybe launch the sound recorder (for example), you have a discrete, potentially automatic meeting transcriber that's pretty much thoughtless.
Click to expand...
Click to collapse
Food for thought. But perhaps you might want to think of another device to do those things. Why would you even want a phone for those functions? A little recorder would do that with no compromise of your personal data. Pull it out of your pocket, put it on the table like a phone and you got your spy device. Phone locked away in your pocket.
Or a shortcut to the sound recorder, lock the phone, face down on the table. Unless you're an agent of some sort then you need to talk with your superiors and design something. Fun convo though.
bobby janow said:
Food for thought. But perhaps you might want to think of another device to do those things. Why would you even want a phone for those functions? A little recorder would do that with no compromise of your personal data. Pull it out of your pocket, put it on the table like a phone and you got your spy device. Phone locked away in your pocket.
Or a shortcut to the sound recorder, lock the phone, face down on the table. Unless you're an agent of some sort then you need to talk with your superiors and design something. Fun convo though.
Click to expand...
Click to collapse
It's fun hearing others' points of view!
But I'm thinking convenience; you've already got a phone and, with the Pixel 4's live transcription and text search, it could make for a powerful tool in this circumstance, as niche as it might be.
raynan said:
It's fun hearing others' points of view!
But I'm thinking convenience; you've already got a phone and, with the Pixel 4's live transcription and text search, it could make for a powerful tool in this circumstance, as niche as it might be.
Click to expand...
Click to collapse
Yes it would. But now you're talking about automating a few different actions one of which is disabling sounds and another locking the screen. Then starting a task of recording and then turning off if the storage gets full without deleting previous recordings. All without user input. I'm not sure a phone was designed to do that. At least not these.
I suspect there are devices that can do that but that might be clandestine type stuff we are not privy to. But maybe a Tasker procedure could handle that? I don't know.
You would want a device that would start recording once voices are heard, and stop after a few minutes of silence.
I do work in an area that contains sensitive information. People entering have to leave their phones at the front desk with the phone muted. I just want to ensure that when I hand over the phone, face down, that it is immediately and automatically locked from anyone else. Simplifying that process would be great!
Please don't question the logic or rationale of my work area.
garyHal said:
I do work in an area that contains sensitive information. People entering have to leave their phones at the front desk with the phone muted. I just want to ensure that when I hand over the phone, face down, that it is immediately and automatically locked from anyone else. Simplifying that process would be great!
Please don't question the logic or rationale of my work area.
Click to expand...
Click to collapse
The XML here can be imported to Tasker to do what you're describing. You may find that you'll need to tweak it to better fit your usage/device, but the skeleton here should be a good starting point.
Edit: XDA didn't like my XML; here's a Google Drive link https://drive.google.com/file/d/11zxgUTwJA37Haf9rV2TbzHWaD1XJeQwx/view?usp=drivesdk