Database Info

[Q] Letters on keyboard stop working?

Anybody had this issue? all of a sudden keys stop working (or parts of the screen) - Default keyboard in the default and Handsent SMS the K and L have stopped working...

GiZiM said:
Anybody had this issue? all of a sudden keys stop working (or parts of the screen) - Default keyboard in the default and Handsent SMS the K and L have stopped working...
Click to expand...
Click to collapse
My touch screen stop working when I turn the phone upside down.. Not sure if this is the same problem.

Haven't had this happen. I've only had the auto rotate stop working.
Sent from my HTC Inspire 4G using XDA app

RayYung said:
My touch screen stop working when I turn the phone upside down.. Not sure if this is the same problem.
Click to expand...
Click to collapse
Honestly that's a really great idea if it was a feature. Think about it no more accidental answer/deny when pulling it out of your pocket if you put it in upside down. And how often if ever is the phone used upside down. I'm calling for a patent on this one!

I have this issue.
I have this issue and it goes far beyond the keyboard. I will be playing fruit ninja and half the screen will be unresponsive. Its happening quite a bit and I am thinking about exchanging my phone.

Same here
I've been having the same problems but I think it has only happened to me when I use custom ROMs such as Cyanogenmod or Coredroid. When I went back to stock I don't remember it happening.
I was running Coredroid V8.1 a few weeks ago and didn't like it because the font looked terrible but I think the keyboard didn't give that problem, it was with an older version of CD. Right now I am using Cyanogenmod 7.0 and it happens a lot and gets annoying. I now for a fact that is not hardware since the keyboard will work normally on landscape and other stuff will respond to the touchscreen.
Still trying to see if there is some sort of fix or to use a new keyboard. Installed GO keyboard and same thing happened, now using Swiftkey X and it happened also but now I took the protective case to see if that has something to do with it LOL.

edit: disregard.

ive had this problem also for awhile. i dont remember having it on the factory rom, but that was awhile back also. ive had it on every custom rom that i can think of. i used coredroid and cm7 for awhile. right now im using miui. ive tried 3-4 different keyboard at least, and had this problem with all of them. the keyboards accuracy also seems to decline. when switching to a new keyboard the problem initially goes away, but it eventually starts doing it again with the different keyboard.

I would try come non CM based roms as I have seen this come up a few times and the omr thing most have in common is that it shows up on CM based roms like MIUI. I have never had this issue on any sense based rom so that would lead me to think like wifi and Bluetooth that it is due to the non OEM drivers CM uses.

Coreddroid is a sense rom, and I had it back then. I've been using absolution, which is cm7 based, and have not since had the problem. The problem has also been reported to occur on non rooted, stock phones.
Sent from my Inspire 4G using XDA App

Nevermind that, I still have it.

Temporary Touchscreen "dead" spots

I recently rooted my Inspire (2 days ago) and just today ive noticed that im getting dead spots on my touch screen. Its most noticeable when im typing something and one of the keys will hardly register. I will have to push multiple times, harder than I would normally have to for it to register. Rebooting the phone fixes the dead spot for a while, and then a new spot will have the same issue a little later. If anyone has any suggestions or and ideas on what could possibly be causing this I would really appreciate it.

What rom/kernel are you using? A lot of people were having that problem, including myself, and to my understanding it had something to do with the drivers. I believe Lee's latest kernel addresses this problem.
Sent from my Desire HD using XDA App

I've noticed this while using the CoreDroid ROM and the Gingerbread keyboard. I switched back to the HTC keyboard and deadspot is gone. So my guess is, its something with the GB keyboard.

Well I am using LeeDroid Rom. Does the regular rom itself not update the Kernel aswell?? Sorry if this is a dumb question, this was my first time rooting.

It's a well documented bug. It's hardware problems with inspires
Sent from my Inspire 4G using XDA Premium App

same here, using Coredroid V7(even before v7) and Lee Kernel 3.1.7 BFS.

same here.. its always the A and the O with almost every rom..

@OP:
This is a known touch screen drivers issue. Only way out is to press power for screen off, and then press again for screen on. I don't think any of our devs here can do anything about it (atleast I assume so, with no doubts about the abilities of our devs).

diablo009 said:
@OP:
This is a known touch screen drivers issue. Only way out is to press power for screen off, and then press again for screen on. I don't think any of our devs here can do anything about it (atleast I assume so, with no doubts about the abilities of our devs).
Click to expand...
Click to collapse
I have found that doing a screen rotation works too

chicobrown726 said:
I have found that doing a screen rotation works too
Click to expand...
Click to collapse
Great! I generally (close to 95%) have my screen rotation turned off, so didn't notice it. Thanks for the idea though.

[Q][Solved] Problems on Nexus S i9023

As the title suggests, I have a Nexus S i9023 (no root, perfectly clean) and the major problem is that i've upgrade the phone to ICS manually and now there are some things that don't work (recovery, light sensor, etc.). I know that there are a lot of threads like this, i know that the problem of the recovery is a problem of brightness, but i wanna know which ROM i've to flash. I'm using the build IML74K.
Another problem is that sometimes the keyboard freezes. Is it caused by the wrong build?

Which rom did you flash?
Try lastest version of ics

I'm using ICS 4.0.3, build IML74K, flashed manually.
Sent from my Nexus S using XDA App

alfax21 said:
I'm using ICS 4.0.3, build IML74K, flashed manually.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I am using the same on my i9023 with no issues, only difference is I am rooted and have clockwork recovery. I suggest a re flash.

I'll try to re-flash the same ROM. If it won't work i'll root the phone and i'll flash CM9.
Anyway, how can i solve the problem of the keyboard? I don't think it's a problem of the build.

I've flashed the ROM for Nexus S i9023 two times but the problems still remain. Any suggestion?

alfax21 said:
I've flashed the ROM for Nexus S i9023 two times but the problems still remain. Any suggestion?
Click to expand...
Click to collapse
Only thing I can suggest is installing clockwork recovery, rooting etc and flashing another rom to see if the problem persists, if so then it probably a hardware issue.
Also where did you get the rom your flashing? There is a thread in the general section with the full rom package I used. Its on the first page at the mo.

Ok maybe there's no solution (i'm new in this forum so i can't post link as the one below):
code.google.com/p/android/issues/detail?id=23065&can=1&q=ics%20nexus%20s%20i9023%20recovery&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars
So I think it will be fixed in the next release. I ask confirmation if someone knows something.

CONTACTMC said:
Also where did you get the rom your flashing? There is a thread in the general section with the full rom package I used. Its on the first page at the mo.
Click to expand...
Click to collapse
Yeah, i've seen it. This one, right?
forum.xda-developers.com/showthread.php?t=1445635

alfax21 said:
Yeah, i've seen it. This one, right?
forum.xda-developers.com/showthread.php?t=1445635
Click to expand...
Click to collapse
Yeah that's the one, flash the full rom package. You may just have a corrupt .zip.

Alredy done two times, but the problem remains. Mmmh i don't think it's a corruption problem, i mean, i've tried to put the update in the phone from two PC.
Sent from my Nexus S using XDA App

Recovery: Known problem. Backlight stays off. Nothing you can do without unlocking your bootloader or rooting. Angle + lamp will show you what is on the screen.
Light Sensor: It's still buggy. With the phone locked, cover your hand over the light sensor (left of the ear piece while facing the phone). Hand still covering, unlock the phone. After a few seconds, remove your hand and face it under a light source. What i've noticed is it'll get brighter initially but refuse to darken again. Of course, you need to have Automatic brightness adjustment (just in case it isn't set to auto).
Unsure about your keyboard problem though, but it does like to stay open for longer than i'd like after going back to the home screen.

Harbb said:
Unsure about your keyboard problem though, but it does like to stay open for longer than i'd like after going back to the home screen.
Click to expand...
Click to collapse
Yeah, it remains open also after going back to the home screen, and it doesn't work. The only way is to crash it by going to the setting of the keyboard in the notifications.

alfax21 said:
Yeah, it remains open also after going back to the home screen, and it doesn't work. The only way is to crash it by going to the setting of the keyboard in the notifications.
Click to expand...
Click to collapse
Mine doesn't remain open though,. It just stays for say half a second, then animates away. Would be much more perfected if it went away while animating the previous window away, not a second later. I've not experienced the keyboard causing those kind of problems.
Might be wise to try SwiftKey or some other kind of keyboard alternative? That is easily enough to sway me away from stock.

Harbb said:
That is easily enough to sway me away from stock.
Click to expand...
Click to collapse
I agree. I'll wait for an Experimental Mod of CM9, then i'll root the phone.

Ok i'll make the thread as solved. I want to thanks Harbb for his help, i quote his post for those who will read this thread.
Harbb said:
Recovery: Known problem. Backlight stays off. Nothing you can do without unlocking your bootloader or rooting. Angle + lamp will show you what is on the screen.
Light Sensor: It's still buggy. With the phone locked, cover your hand over the light sensor (left of the ear piece while facing the phone). Hand still covering, unlock the phone. After a few seconds, remove your hand and face it under a light source. What i've noticed is it'll get brighter initially but refuse to darken again. Of course, you need to have Automatic brightness adjustment (just in case it isn't set to auto).
Click to expand...
Click to collapse
If you have problems (like the recovery one and the light sensor) with ICS 4.0.3, build IML74K, on your Nexus S i9023 there's nothing you can do, probably Google will fix it on his next update 4.0.5.

I'll just add that many custom ROMs allow light sensor manipulation. I hear there are great, working settings, its just the stock calibration that sucks. I've not tried this myself, but should be available in cm9, cna, etc.

..

Election Day said:
This is how I have my i9023 set up. These settings work very well, so feel free to use them.
Click to expand...
Click to collapse
Are these settings of the stock ROM?

..

Screen Flicker Galaxy S III-Fixed?

I've search high and low but it seems like any thread related to this was closed when the forums were split up. In any case, please report any screen flicker issues here and what keyboard you might be using and whether or not you're rooted. I bought this phone new and had a screen flicker before I rooted it. I figured it might be software related so I rooted and installed another ROM. I still notice it from time to time when typing. I don't think this flicker will ever go away. I'm now on CM10 and still notice the problem. I've been using Swiftkey from the start but I'm not sure yet if that's what causing it.
Thanks to TechSavvy2, I think this problem has been fixed.
Originally Posted by TechSavvy2
Go to settings - developer options - and check the box disable hw overlays. It should drastically fix flicker or at least help till the fix is merged (who knows when)
Click to expand...
Click to collapse
Known problems when selecting this option.
-Swiftkey FC's. (link to vote to fix problem - http://support.swiftkey.net/forums/116693-2-swiftkey-bugs-/suggestions/3143605-disabled-hw-overlays-due-to-screen-flicker-galaxy-

I have experienced it too on my s3

AndroidGraphix said:
I've search high and low but it seems like any thread related to this was closed when the forums were split up. In any case, please report any screen flicker issues here and what keyboard you might be using and whether or not you're rooted. I bought this phone new and had a screen flicker before I rooted it. I figured it might be software related so I rooted and installed another ROM. I still notice it from time to time when typing. I don't think this flicker will ever go away. I'm now on CM10 and still notice the problem. I've been using Swiftkey from the start but I'm not sure yet if that's what causing it.
Click to expand...
Click to collapse
Aren't you on CM10??? Go to settings - developer options - and check the box disable hw overlays. It should drastically fix flicker or at least help till the fix is merged (who knows when)
Sent from my Galaxy S3 using Tapatalk 2

TechSavvy2 said:
Aren't you on CM10??? Go to settings - developer options - and check the box disable hw overlays. It should drastically fix flicker or at least help till the fix is merged (who knows when)
Sent from my Galaxy S3 using Tapatalk 2
Click to expand...
Click to collapse
I'm pretty sure this has fixed the screen flicker problem for the galaxy s3. Thanks a million. What exactly does this option do
Sent from my SCH-I535 using xda premium

AndroidGraphix said:
I'm pretty sure this has fixed the screen flicker problem for the galaxy s3. Thanks a million. What exactly does this option do
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Not sure what it does, but you will need to tick the same option every time you reboot if you're on CM10 official at least(I can't speak for the other AOSP ROMs.)
You got a screen flicker BEFORE you did anything to your phone tho? That's the first I've heard of the flicker anywhere except an AOSP ROM. Hmmm. And was/is it only when you used Swiftkey? If so, gotta be some conflict between Swiftkey and our phones. (I really don't care for swiftkey since it doesn't have any kind of swipe option. I use Touchpal, which is pretty good on the autocorrect/predictions especially for a freebie)

I've also had the screen flicker on my phone since I activated it. I am on stock touchwiz and the thing that kepts it from occuring every time i opened the keyboard was installing thumb keyboard. I really wish Samsung would send a fix sometime in the near future. I am hoping this is just a software issue and not hardware.

shangrila500 said:
I've also had the screen flicker on my phone since I activated it. I am on stock touchwiz and the thing that kepts it from occuring every time i opened the keyboard was installing thumb keyboard. I really wish Samsung would send a fix sometime in the near future. I am hoping this is just a software issue and not hardware.
Click to expand...
Click to collapse
Ya, I know for a fact, I had the flicker before I rooted or even changed the bootloader. I've tried every rom out there and still have a real bad flicker every now and then. It does go away when I turn hw overlays off but by turning it off I can't use SwiftKey which really bites. Isn't this an indication its software related?
And I'm not sure if it's just SwiftKey related. I guess, I'll experiment with the other keyboard to test.
By any chance could it be kernel related?
Sent from my SCH-I535 using xda premium

It happened to my GF's S3, lets call this S3 A, screen fickers and with series of lines vertically, phone freezes, had to do hard boot, then the battery dropped to 3% instantly. We think it's the battery, lucky us, we have another S3, we'll call this S3 B, in which has no flickering issue, and we exchange the battery and the flickering did not happen on S3 A anymore but it did happen to S3 B in which has no flickering issues at all from the start.
And we noticed the S3 A battery is beginning to bloat (it is getting fatter than the battery of S3 B) maybe due to wear and tear or over charging.
So our conclusion, the battery is culprit, we've replaced it and we'll observe for about a week.

I can also experience flickering and very crappy battery life. Guess I need to buy a new batter then? I don't want to waste money if changing batter doesn't work so please tell me if I should buy or not.

[Q] Phone Jitters

has any noticed "jitters" with there phone screens becuase ive notived lately that my phone "jitters" ( kinda like a reception issue i guess ) were the screen flickers on an off and im needing help in regards to fixing this issue ( IF IT CAN BE FIXED ) or do i need to send my phone into samsung to get replaced please let me know

I would get a replacement.. sounds like hardware failure
Sent from my SGH-T769 using xda app-developers app

That happened to me and I had to get a replacement. Started off being a sporadic issue and progressively got worse, to the point where o could not use my phone when it happened. The phone would flicker a charcoal grey color, this would cover the entire screen except the notification bar. It hasn't happened with the replacement.
Sent from my SGH-T769 using Tapatalk 2

soldier1184 said:
has any noticed "jitters" with there phone screens becuase ive notived lately that my phone "jitters" ( kinda like a reception issue i guess ) were the screen flickers on an off and im needing help in regards to fixing this issue ( IF IT CAN BE FIXED ) or do i need to send my phone into samsung to get replaced please let me know
Click to expand...
Click to collapse
Are you running stock rom or have you rooted and run custom roms? could be a rom issue... if running stock possibly hardware issue..

found the issue
Racing19969 said:
Are you running stock rom or have you rooted and run custom roms? could be a rom issue... if running stock possibly hardware issue..
Click to expand...
Click to collapse
i found the issue it wasn't hardware failure or rom is was actually using the TWRP 2.4 recovery i tested it with 3 of the roms i normally run as dailies ( tweaked 2.2 slim 3.1.0 Struck and PAC 4.1.2 and it jittered the screens like bad ( kinda like a computer that when it gets popped with a magnet / or older tv having f|_|cked up reception so i changed the recoveries and viola no more jitters so apparently the TWRP doesn't like blaze owners ( at least me lol ) but if there's anyone else experiencing these issues narrow down first before you consult a replacement