Database Info

keyboard leds stay on after sliding back in

A couple of times I was shocked to notice that the keyboard leds on my TP weren't shut down with the keyboard slid in. Since there is a slight gap between the keyboard and the screen, in a dark environment, looking at the TP's right edge, white light was clearly visible just 1-1.5 cm's above the stylus (display and the hardware buttons were OFF, so no, no light "bleeding" effect).
After promptly sliding the keyboard out and back in, the lights went out; actually they went out right when I started to move the keyboard, possibly indicating that there might be a loose contact somewhere. Once, I actually waited for the light to go out by itself; it certainly stayed on after the regular "timeout" value...
So, I wonder: if the contact that is supposed to cut the power to the keyboard when you slide it back in sometimes doesn't work, but the device thinks it's locked and doesn't "timeout" the leds anymore, can this be the cause of mysterious battery drains reported so many times on this forum? Sure enough it's quite hard to spot, especially if you're using a case for the phone. It would most certainly explain why battery drain varied on my device rather wildly even though the usage pattern hardly changed from day to day.
I tried reproducing the effect but it's quite hard (I'd say for my device it would kill the lights correctly at least 9 out of 10 times) and I didn't want to stress the sliding mechanism too much...
Anyone notice this?

Just so noone thinks I'm seeing ghosts, today, just after unplugging it from my laptop, eventhough the keyboard hadn't even been opened, I saw the leds were on again. Just to be sure this wasn't a "feature" I waited about 5 minutes and they were still ON. So yes, this is most definitely a bug and a quite serious one at that.
I took a photo with a friends phone camera (sorry for the low quality). The bright, white, dots seen in the pic are the leds from the underlying keyboard (the phone had always been shut, keyboard fully slid in: display and hardware keys were completely off and no, there was no light from the D-pad either).
I can now easily understand how, occasionaly, the battery managed to run out so quickly... Has noone noticed this before? Am I the only one with a potentially defective unit/keyboard contact?

[Q] Possible hardware problem of the back button?

I just wanted to share this, since I was able to replicate this issue with three different phones, also asking if other people are having the same issue.
I am using my Samsung Nexus S for three days.
I noticed that the back button (the first capacitive button on the bottom left) appears to have an hardware problem.
Basically normally it works fine, I mean when I'm not using the phone for some hours.
Then if I start to use the phone, after a moderate use (example installing applications from the market, browsing etc) the button gets less and less sensitive.
After some minutes it gets really annoying.
To make it work it is necessary to use a really stronger pressure with the finger, and it is not even always working!
I am planning to return my device, but today talking with some people/colleagues I discovered that two of them have exactly the same problem.
I'm suspecting there is a batch of Nexus S phones with this glitch, I am curious to know how many people have the same problem.
Note:
At first I thought it was a general issue of the capacitive buttons. But I can't replicate the same problem with the other three buttons, they work very smoothly just lighltly skimming the finger over them, even after long usage.
Anyone with the same problem? What is your experience with this button after some usage?
Cheers

I want to say that I noticed something similar the other day, but it was short-lived, and I'm not 100% sure. It wasn't long enough or bad enough to make me think the phone is defective, but I'm a bit used to funky capacitive button responses from my N1 days.
I can't reproduce the issue right now, though. How much usage are you talking about needing to duplicate?
Does your phone get hot, or feel hotter than normal when this happens?
I'd see if there's some particular pattern or software that seems to trigger it if you're interested in trouble-shooting.

The problem goes away when I don't touch the phone for a while (it seems that 1 hour is enough to reset the problem).
It seems "recharging".
Then with normal usage, nothing in particular, just even browsing in the settings/maps/market/browser etc., in few minutes the problem appears. The button definitely loses his "power".
It's very annoying, and my friends confirmed the same behavior.
EDIT:
Forgot to sat that the phone is not getting hotter, everything else is really normal.
Cheers

Mine definitely can be used for much more than a few minutes without the problem you're describing appearing.
I'd take it back. Factory reset the phone to protect your private data before taking it back. After the factory reset, you might want to test the behavior again, if it went away, the phone's not defective, you just had some software glitch.
Reminder, factory reset erases everything on the phone, so if you do it as troubleshooting step, be prepared to have to set the phone up from scratch again...I'm sure you knew this, but just covering my butt in case you didn't. It's a good trouble shooting step no matter what if you don't mind the hassle of re-setting things up.

I have a similar experience with the back button. Not sure what to think yet.
Sent from my Nexus S using XDA App

I had a similar problem when I had the Vibrant. Just exchanged it and luckily I got a better one without any problems. I did find out though if you are using the screen protector that came with the phone, it can cause this type of problem.

No problem, I will try everything tomorrow. This is not my primary phone (still loving my rooted Nexus One with CyanogenMod 6.1.1 ;-) I can't renounce to the colored trackball for the different notifications), but just a "dev" phone for testing purposes.

michele72 said:
No problem, I will try everything tomorrow. This is not my primary phone (still loving my rooted Nexus One with CyanogenMod 6.1.1 ;-) I can't renounce to the colored trackball for the different notifications), but just a "dev" phone for testing purposes.
Click to expand...
Click to collapse
The app NOLED from the Market may interest you if you can't live without trackball style color notifications. Seems to work fine when I tested it.

distortedloop said:
The app NOLED from the Market may interest you if you can't live without trackball style color notifications. Seems to work fine when I tested it.
Click to expand...
Click to collapse
Thank you, giving it a try.
Anyway, today I factory-reset my telephone and the problem of the back button is still there. I am returning the device.

Back button non responsive
Hi,
I just got my new nexus S (about an hour ago) that I was really excited about and am faced with a problem with the back button too.
Its got factory settings, so it cannot be a downloaded software issue. Also, I have not yet charged the battery at all, its still running on the same battery power that it shipped with.
The other buttons at the bottom of the phone (home, menu and search) all respond fine, its only the back button that does not seem to work. After going through this thread, I tried long-pressing the button, hard-pressing it, pressing just above it, below it, etc. It just wont respond. I had removed the screen protector it shipped with, so that cannot be the issue either.
If this is a known hardware problem (i.e. others have faced it too), irrespective of whether it is acknowledged by Samsung / Google, I'll return the handset. I do not want to spend a fortune and be landed with a handset that does not work - forget working as desired, but it does not seem to be working as designed !
Thanks & Regards,
Rohan

Yep. Definitely a problem here with the back button. There's also two other threads here about it.

I'm having similar problems. I have to touch the button just right for it to work properly
Sent from my Nexus S using XDA App

I was experiencing the same thing with my Nexus S, wasn't sure if it was the case I was using! Took of case and still had problem. I eventually returned mine cause it seemed like it was getting worse! I have a new one worth no problems, definitely a hardware problem! Return it!
Sent from my Nexus S using XDA App

michele72 said:
I just wanted to share this, since I was able to replicate this issue with three different phones, also asking if other people are having the same issue.
I am using my Samsung Nexus S for three days.
I noticed that the back button (the first capacitive button on the bottom left) appears to have an hardware problem.
Basically normally it works fine, I mean when I'm not using the phone for some hours.
Then if I start to use the phone, after a moderate use (example installing applications from the market, browsing etc) the button gets less and less sensitive.
After some minutes it gets really annoying.
To make it work it is necessary to use a really stronger pressure with the finger, and it is not even always working!
I am planning to return my device, but today talking with some people/colleagues I discovered that two of them have exactly the same problem.
I'm suspecting there is a batch of Nexus S phones with this glitch, I am curious to know how many people have the same problem.
Note:
At first I thought it was a general issue of the capacitive buttons. But I can't replicate the same problem with the other three buttons, they work very smoothly just lighltly skimming the finger over them, even after long usage.
Anyone with the same problem? What is your experience with this button after some usage?
Cheers
Click to expand...
Click to collapse
those buttons work over the heat of your finger. thats why after use it doesnt get as responsive. its because the screen is also heated and the heat of the screen is effecting the buttons. thats why you need harder pressure for the phone to understand this is your finger.
same issue was with Nexus 1. less responsive buttons. thats why there is a bigger gap between the buttons and the screen for galaxy S phones. i dont know why they did such a thing again with the nexus S. its like samsung didnt learn from anything from HTCs mistake.

They work with capacitance, not heat. Hence it being called a capacitive screen with capacitive buttons.

I think this is true ...
I have an HTC Desire with AMOLED screen.
When I play a finger intensive game, like "SkyForce Reloaded", after some times, the touch is not registered.
Then I must stop for a while, or change finger
Try that, you will know what I meant.
But, I don't have issue with the back button on HTC Desire because it is a hardware button. I am just trying to explain about loosing touch registration because finger interaction on (s)amoled screen.
PS: SkyForce Reloaded is an old school shot'em up game where you control a little space ship with your finger, shooting enemies.
ll_l_x_l_ll said:
those buttons work over the heat of your finger. thats why after use it doesnt get as responsive. its because the screen is also heated and the heat of the screen is effecting the buttons. thats why you need harder pressure for the phone to understand this is your finger.
Click to expand...
Click to collapse

The Desire's digitizer is the same Clearpad 2000 which is used in the Nexus One (and quite a few others), the problem there is that it's pants.

Rusty! said:
They work with capacitance, not heat. Hence it being called a capacitive screen with capacitive buttons.
Click to expand...
Click to collapse
lol, isnt called like that because it registers the heat from your fingers. thats why if you try to use a pen, it wont register . and thus. the screen is NOT resistive type "where it will recognize anything since its being pushed by force ? "

Much more too it than that: http://en.wikipedia.org/wiki/Capacitive_touch_screen

Rusty! said:
Much more too it than that: http://en.wikipedia.org/wiki/Capacitive_touch_screen
Click to expand...
Click to collapse
from your link
"A capacitive touchscreen panel is one which consists of an insulator such as glass, coated with a transparent conductor such as indium tin oxide (ITO).[7][8] As the human body is also a conductor, touching the surface of the screen results in a distortion of the screen's electrostatic field, measurable as a change in capacitance. Different technologies may be used to determine the location of the touch. The location is then sent to the controller for processing.

[Q] xoom touchscreen issues?

I got my Xoom (WiFi) yesterday... already noticing some weird touchscreen behaviour.
It seems to me that whenever the Xoom is laid down flat, there's a chance that the device will stop responding to touch presses properly. Instead of being able to press-and-swipe, it acts like I tapped the screen (eg, pressed my finger on the screen and then lifted it straight back off) or worse, it causes a screen press in completely the wrong position. When it starts happening, it keeps on happening, but picking the Xoom up and holding it vertical seems to fix the problem.
Half the time it seems fine laid down though, so I'm not sure if it's just coincidence that it stops working at the same time I put it down flat or not, or that maybe picking it up means my hand is in contact with the back of the screen and this somehow changes some sort of electrical variable in my hands that affects the touchscreen operation.
Anyone else seen the same issue? I'm thinking I may need to take it back but want to see if anyone else has experienced anything similar.
Chris.

ok.. judging by the lack of response on this, I may either be on my own or it's just something that nobody is noticing. I've been testing it a bit more - I wrote an app which can show each touch point on the screen so I can see how the screen press/drag is working. This is what I've found.
Holding the tablet upright, screen presses and movements are fine, however I've noticed that if I hold my fingers in the same place for a while, the touch points will prematurely end.
If I put the Xoom down on the couch, there is a strong likelihood that the touchscreen will become incredibly unresponsive. I have had it regularly show up phantom presses where touching one point of the screen makes it appear as if I have also pressed another point of the screen. I also cannot drag my fingers across the screen - the touch points stay where they are until I take my fingers off the screen completely, or they just disappear right away as if I tapped the screen.
When this happens, if I touch the side of the case with either a free finger or my other hand, the touchscreen starts working perfectly! Seriously! I'm not kidding, I've been messing with this thing almost non-stop for the past coulpe of days and it is consistently doing this. So - couch + little finger on side of case = working touchscreen. couch but no contact with metal case = malfunctioning touchscreen.
If I have the Xoom in Motorola's case, it seems to work fine. If I put it on a table, it's a bit buggy but generally works better than on the couch. Any sort of material seems to send it regularly into crazy mode. The only time I've noticed it doesn't do this is if I'm in contact with the device immediately before putting it down and then remain in contact with the screen.
Could some sort of static charge cause this? Is it possible that me touching the back of the case is effectively allowing it to 'conduct' electricity properly on the touch screen? I'm not all that familiar with how capacitative screens work other than I assume they measure capacitance from your fingers. Maybe a static charge could throw it off. Or maybe I have weird fingers.
Anyway, I'm pretty close to taking the Xoom back now. Just trying to figure out if it's actually faulty or whether they're all like it by 'design'.

sorry
need to post to remove my limitations sorry again

This could be a loose touch controller cable. Someone had similar problems and posted a how to fix this, search for it.

It happens with me too, it's incredible annoying when you are developing and the tablet is on your table for debugging..
Did you find how to fix it?

I have a serious unresponsive issue on my Xoom when charging. I've tried several different chargers, (all from Motorola) with no luck. Unfortunately all the ones I tried where at my house so I'm not sure if its a wiring issue in my house.
I also have a similar problem on my Droid Razr so I'm starting to think its definitely the wiring.
Anyone know about this issue or have any recommendations?

kiroiv said:
I have a serious unresponsive issue on my Xoom when charging. I've tried several different chargers, (all from Motorola) with no luck. Unfortunately all the ones I tried where at my house so I'm not sure if its a wiring issue in my house.
I also have a similar problem on my Droid Razr so I'm starting to think its definitely the wiring.
Anyone know about this issue or have any recommendations?
Click to expand...
Click to collapse
Thats weird.. i owned xoom n droid razr too but i dun have any iissue

It could be a wiring issue (try another house, I guess), but a lot of devices are like that where the touch screen stops being as responsive when it's on a wall charger.

What does your TF do when closing the dock?

What does your TF do when closing the dock? Will it stay off and asleep?
I just got my B40 dock back after RMA (timeline and replaced parts number summarized here). I didn't really pay attention to how it was before I sent it because I only had it for a few days, except that it didn't sleep even when MobileDock Battery saving mode was set. Now after the RMA, it stays asleep correctly, but when I closed it in a darkened room, I noticed a light coming from the gap. It woke up!
In short, opening and closing the dock would behave like this:
1. While open, press the power button on the tablet (or the lock key on the dock). Table would go to deep SLEEP and would not wake up with a keyboard tap. However, as I close the dock and it approaches about 5 degree angle, the screen would turn ON and, worse, it stays on. Pressing the power button would not turn it off.
2. While ON and not asleep, close it. As it approaches 5 degree angle, the screen would turn OFF. It would turn ON as soon as the dock is opened again (regardless of how long I left it closed).
FWIW, the TF is B50 on Revolution ROM 2.1.0.
Edit: reluctant of another RMA, is there a microswitch inside the dock that detects the open/close position? If so, I might just disconnect it unless there is a software fix.

There is no switch. There's a magnet right beneath the - button that tells your TF to go to sleep when you close it and wake up when you open it. Don't put it to sleep before you close it. I have b60. When I press the power button before I close it, it would still stay asleep and wakes up when I open it. It's not a dock issue. It's a TF issue. May be the b50 is built differently. Don't know.

I uninstalled "No Lock" and now the screen stays off in scenario 1 above. But looking at CPU Spy, it wasn't deep-sleeping and instead it stayed at 216.
Not doubting you, but how did you know that your B60 was deep-sleeping for sure?

lost_ said:
I uninstalled "No Lock" and now the screen stays off in scenario 1 above. But looking at CPU Spy, it wasn't deep-sleeping and instead it stayed at 216.
Not doubting you, but how did you know that your B60 was deep-sleeping for sure?
Click to expand...
Click to collapse
I don't. All I know is that my battery lasts forever. Besides, if it doesn't go to deep sleep, then fine. I don't care. Like I said, as long as the battery lasts me the whole day without me worrying about charging, I'm good.
Why are people so anal about this sleep thing? Get an ipad if you want your device to deep sleep that badly.

I think there is a difference in being anal and trying to be sure about what our device is donig -- especially after one has just received it from RMA.
Being in XDA already makes us more attentive about our devices than the regular population, so can't blame someone for checking.

lost_ said:
I think there is a difference in being anal and trying to be sure about what our device is donig -- especially after one has just received it from RMA.
Being in XDA already makes us more attentive about our devices than the regular population, so can't blame someone for checking.
Click to expand...
Click to collapse
Actually, no. I think it's the opposite. If you're here in xda then chances are you are fine with some of the imperfections that come with our devices. That's why we mod.
It's the ipad users who expect things to be perfect. Myself and many others have pointed this out many times. iOS devices crash just as often as everything else. The only reason people think they don't is because when they do crash there's no error message. One moment you're in an app and the next you're on your home screen. iOS is built that way. It's like sweeping the dirt under the rug to give the impression that the place is spotless.

why are we even talking about iPad? Geez...

Question about screen dimming

hey guys got question for u all
i like so much the flip 4 but i sell it cause i had 1 major proble
i bought iphone 14 pro max but i really want my flip 4 again
my problem is any time im using the phone for facebook whatsapp and regular stuff with regular use (not even hard use at all)
the screen dimm to much cause the phone is warm
if i turn on the extra brightness its dimm alot faster with minimum use
so i i never used the extra brightness but always on the full brightness but i always use minimum use and the screen is dimm
any solution or its like that???? (the phone is ok i had 1 before and it was the same)
i have no case nothing i never pleyed games with my phone just regular use....any tips for what to do or this is how the phone act?
and just for you know im on android 13 latest thx for the help !!!

sounds like you have some sort battery saver turned on, have you checked in settings? this is not normal behaviour.

beanbean50 said:
sounds like you have some sort battery saver turned on, have you checked in settings? this is not normal behaviour.
Click to expand...
Click to collapse
sure man i never use battery saver always full brightness all the way up then the phone get hit very easy and dim the screen the temperature outside is around 25 c

nobody got this iisue? no way!!

It is clear that your mobile phone has a technical problem that needs maintenance, but try to return it to factory settings

amincom said:
It is clear that your mobile phone has a technical problem that needs maintenance, but try to return it to factory settings
Click to expand...
Click to collapse
ok but this my third phone loll, my sisters got the same iisue not just me, and we bought the phones in deffrent places :-(

nosferatu123 said:
ok but this my third phone loll, my sisters got the same iisue not just me, and we bought the phones in deffrent places :-(
Click to expand...
Click to collapse
maybe i use app that make the phone to hot the the screen dimm?
im using whatsapp facebook instagram and messanger maybe? anyone knows?

On the Flip 4 I use the Adaptive Brightness "on" setting, and Dark Mode. Your results may vary, but here's what I've seen.
In the summer, on a sunny day, I'll notice that the phone will automatically try to be as bright as possible, so the screen is readable. (I'm pretty sure when this happens the quick display panel's screen brightness slider color changes to orange. Maybe the color depends on the wallpaper/color palette.) And I never see the screen do this "extra bright" thing indoors. Only outside and only in direct sunshine.
So far so good. I think this is as everyone expects the phone to operate.
Given all this, sometimes I'll notice the screen brightness will vary, even though I'm still outside and still in the same brilliant sunshine. I've noticed this commonly when checking Google News, and for example, I'm reading a story and scrolling slowly through the article. In particular when the screen is mostly black text on a white background.
So, in this situation, that is, a largely bright background, in the bright sun, my phone will both:
Get warm to the touch, on the back-side of the phone, where the two batteries are, but not up where the cameras, CPU and memory are located. This makes sense because "scrolling text" isn't that demanding on the CPU, but I am driving the OLED screen hard.
Also the front of the phone (the OLED screen itself) can feel warm. Even in the screen's crease, away from the battery. Since the image is mostly white, all the OLED dots are "on" and give off heat. Then again, I'm in brilliant sunshine and almost any surface will get warm.
Further, I'll notice that the phone screen will automatically get dimmer after a bit of time (perhaps a minute or two of extra-bright before the dimming). This I attribute to the software doing one, or both of:
Dialing back the screen brightness, to prevent OLED burn-in.
Dialing down the power usage by the screen, to prolong battery life and/or limit the battery temperature.
What's more, after little more time, still in the same bright lighting conditions, perhaps reading the same story, the screen might be noticeably extra-bright again. It's as if the phone has given the display "a rest" and is willing to go "extra bright" again.
In short, I think the phone screen is trying hard to be brilliant in the brightest of sunshine. But there are limits in how hard you can drive an OLED screen, and how long the battery can power the screen.
All of this before we start to talk about what design limits come into effect when the CPU or graphics processing come into play, both or which compete for:
Power from the battery, and
The ability of the phone to keep itself cool.
This phone's form-factor is all about folding in half. A slab form-factor phone, I suspect, will be far more capable for heavy CPU, graphics, and provide a bigger battery and better heat disipation.