Database Develop

Problem with Notification Bar.

I recently ran into an odd problem. I updated my phone from 2.1 to 2.2 Froyo Test 4, then to RC1. I use overclocker app, launcher pro, and advance task killer mainly.
My problem is: When I use my phone, sometimes the screen will not allow me to touch icons, unlock it, ..etc. All it does it move the notification bar up and down like I am touching the top of the screen. If I keep trying to "turn screen off, back on, off, back on"...eventually, I will be able to use the phone for a couple of minutes before it happens again. I tried disabling/reducing overlock settings, uninstalling launcher pro, downgrading 2.2 to 2.1 (ICERoM 2.8). None of this helps.
Any ideas?
Note: Sorry if this was explained elsewhere. I tried searching my best.
Kernal Version: 2.6.29-Godmode-oc-bfs (toast)

Where do you live? I live in florida, and this happens to me when I'm outside for an extended period on a really humid day. Once I take it in to the ac for a few, it's all ok.
Sent from my HTC Hero CDMA using XDA App

Louisiana. Doesn't seem like that would be it though. My wife has the same phone and has never experienced this problem (she has OEM 1.6 version). I am leaning towards software issue.

mar122999 said:
I recently ran into an odd problem. I updated my phone from 2.1 to 2.2 Froyo Test 4, then to RC1. I use overclocker app, launcher pro, and advance task killer mainly.
My problem is: When I use my phone, sometimes the screen will not allow me to touch icons, unlock it, ..etc. All it does it move the notification bar up and down like I am touching the top of the screen. If I keep trying to "turn screen off, back on, off, back on"...eventually, I will be able to use the phone for a couple of minutes before it happens again. I tried disabling/reducing overlock settings, uninstalling launcher pro, downgrading 2.2 to 2.1 (ICERoM 2.8). None of this helps.
Any ideas?
Note: Sorry if this was explained elsewhere. I tried searching my best.
Kernal Version: 2.6.29-Godmode-oc-bfs (toast)
Click to expand...
Click to collapse
You posted this in the wrong forum
Anyway, it could be a hardware problem, but it sounds more like a software issue. Sometimes this happens to me when the phone slows down. Are you low on RAM when this happens?

Nope. Ram is ok. 70+ Mb. Seems like it all started when I upgraded to 2.2. At times, the phone is unusable. Right now, it has been working perfect for a couple of hours. I downgraded to 2.1 thinking that 2.2 was the problem, but 5 hours ago, I encountered the same problem with 2.1. So that can't be it. Screen protector maybe?

mar122999 said:
Nope. Ram is ok. 70+ Mb. Seems like it all started when I upgraded to 2.2. At times, the phone is unusable. Right now, it has been working perfect for a couple of hours. I downgraded to 2.1 thinking that 2.2 was the problem, but 5 hours ago, I encountered the same problem with 2.1. So that can't be it. Screen protector maybe?
Click to expand...
Click to collapse
Yeah, could definitely be the screen protector is changing roms doesn't help. Could also be a bad touchscreen, but most likely screen protector.

derekwilkinson said:
Yeah, could definitely be the screen protector is changing roms doesn't help. Could also be a bad touchscreen, but most likely screen protector.
Click to expand...
Click to collapse
+1
when i had one on my phone it would do this. i think its static tricking the touchscreen.

CM7 Root Issue - Screen Flashing When Turned On

Hi There,
Noob here. I did a CM7 (update-cm-7.0.3-encore-signed) root and everything seemed to go fine except when I turn on the unit, the screen flashes a white color. This is not the entire screen. It does it for a spit second then loads.
I thought maybe I screwed up the device, so I did a factory reset using CWR which did as was supposed to. Once factory reset, it didnt do the screen flash.
I then went and reinstalled CM7 with the same issue occurring.
Any thoughts?
Thanks,
Herschel

That's normal, nothing to worry about. It does that when it switches boot screens.
Sent from my CM7 Nook

Is normal mine dose the same thing , it will do it also when you unlook the screen
Sent from my NookColor using Tapatalk

its configurable. Check in your settings for screen on/off animations.
menu>>>>settings>>>>cyanogenmod settings>>>>display

TainT said:
its configurable. Check in your settings for screen on/off animations.
menu>>>>settings>>>>cyanogenmod settings>>>>display
Click to expand...
Click to collapse
That will do nothing for the OP.

Is there a fix for that, it doesn't look good to eyes, when the screen suddenly flashes in full bright white, after the screen starts again after a timeout.
Sent from my NookColor

TainT said:
its configurable. Check in your settings for screen on/off animations.
menu>>>>settings>>>>cyanogenmod settings>>>>display
Click to expand...
Click to collapse
priyank_bolia said:
Is there a fix for that, it doesn't look good to eyes, when the screen suddenly flashes in full bright white, after the screen starts again after a timeout.
Click to expand...
Click to collapse
You two are talking about a totally different issue than the OP, but TainT's post should answer your question, pb. If screen-on animations are not your issue, you'll have to clarify.
Also, as a PSA: installing CM7 is not rooting. You may have rooted (unnecessarily) in the process of installing CM7, but not any and every modification to an Android device is a "root." Rooting is the process of gaining Super-User access to an Android OS on which you were previously denied it. When you install CM7, you are running a completely different operating system in which you already have root access.

For me the screen on/off animations are disabled, still when the screen timeout or when I press the power button, the screen flashes very brightly for a brief time. It looks very ugly and painful at night when the screen flashes.
This is not a device issue as this happens with CM7 only.
I hope that I am clear in explaining the issue now.
Sent from my NookColor

Sorry, I don't get anything like that--if I wake the NC with either power or 'n' it just comes on at normal brightness. I still get the flash horizontally across the screen when powering on the NC, if it was actually powered down (what the OP was talking about). Otherwise, no bright white lights.
What CM7 are you running? 7.0.3? The beta 7.1? A nightly? SD or eMMC?

7.0.3 from emmc.
Sent from my NookColor

Well, you could try grabbing a nightly, or the original 7.1 beta. I know I don't get any weird flashes with those, but I don't really remember if I did with 7.0.3.
Or you can wait--there should be a stable build with the new kernel before too long. I ran the 7.1 beta for over a week, OCed with dal's 5/23 kernel, and it was rock solid stable.

[Q] NC Keyboard disappears

Just updated to v1.2.0 and re-rooted, but now I have a strange problem. I tried searching these forums, and The Google, but couldn't find anything helpful.
When you click in a text field (e.g., the search box, or the address bar of the browser), the keyboard will pop-up for about 1/2 second, and then minimize again. You can do this repeatedly with the same result - the keyboard just won't stay open.
I've tried rebooting, and even installing a different keyboard (can't get them to appear as an option in NCTools).
Has anyone else run into this? Were you able to fix it?

This used to happen to me when I used a Archos 28 "tablet". It was because there wasn't enough RAM most of the time, so it would close the keyboard to make more.
I doubt that's the case for the Nook Color, though. I've never had a problem with memory on these things.

I've had that happen as well but strangely only when the nook is at an angle like when I'm laying on my back in bed with the screen above me angled downward, tilting the screen so that it is facing up solves it for me, like I said, strange.
Sent from my NookColor using XDA Premium App

ninpo said:
I've had that happen as well but strangely only when the nook is at an angle like when I'm laying on my back in bed with the screen above me angled downward, tilting the screen so that it is facing up solves it for me, like I said, strange.
Sent from my NookColor using XDA Premium App
Click to expand...
Click to collapse
Did you do anything to resolve it, or just live with it?

I just live with it, simply changing the angle seems to solve it, that's a simple enough fix for me.
Sent from my NookColor using XDA Premium App

FYI for anyone that runs into this thread later:
There must have been some glitch in the rooting process that screwed up the keyboard. I ended up doing the whole process over again by restoring back to stock 1.1, updating to 1.2, and re-rooting. Everything works like a charm now.
Incidentally, the stock/update/root process is a lot easier the second time you do it.

Hi, I have the exact issue, anyone knows where I can download 1.1 rom or 1.01 rom? I tried all 1.2, 1.3, 1.4.1, they all have the same issue. Thanks.

Every time before install new ROM, I formatted system, data, and cache, but seems still not totally formatted, cause 1, the keyboard part still mess up, now even cm7 on emmc has the issue. 2, the wifi connection still saved because it auto connects to my network every time flashed. Any idea? Thanks.

[Q] Touchscreen issue

Hi everyone,
I was up to ICS Rom yesterday, but everytime i unlock screen, i cant touch in the bottom of the screen, cant typing with h, g, j and somewhere around it, but on the right, left or top screen i can still use normal. Does anyone know what happen and how to fix it?
When im in CM7 Rom is was fine and has no problem
PS: Sr for my bad english i really not good in grammar.

Same problem but different area
I have the same issue.
On Apex i had no issues but when i upgraded to SlimICS 3.2. The right side of the screen ocasionally becomes unresponsive.
That is, on any keyboard from approximately the 'i' to backspace horizontally, and from enter to the top of the screen.
This whole zone randomly decides not to work. the only fix is to turn the screen off and then turn the screen on again, or backing out of the application and reloading it. The application can be anything, chrome browser, swiftkey, messages, whatsapp.
Does anyone know what the issue could be?
I'm running slimics3.2 with semaphore ics 1.0

I'm also running slim 3.2 and had the same issue with the sephamore kernal. I just reflashec the essentials and everything worked perfectly for me.
Sent from my SGH-I897 using XDA

I used the essentials kernel first and experienced the issue, i thought it was a kernel issue so I flashed semaphore afterwards. But I still have the issue...

arse87zx said:
I'm also running slim 3.2 and had the same issue with the sephamore kernal. I just reflashec the essentials and everything worked perfectly for me.
Sent from my SGH-I897 using XDA
Click to expand...
Click to collapse
I tryed AOKP 3.0 and didn't modify anything, also some another ROM but it still have a problem with the touchscreen

KunNuK said:
Hi everyone,
I was up to ICS Rom yesterday, but everytime i unlock screen, i cant touch in the bottom of the screen, cant typing with h, g, j and somewhere around it, but on the right, left or top screen i can still use normal. Does anyone know what happen and how to fix it?
When im in CM7 Rom is was fine and has no problem
PS: Sr for my bad english i really not good in grammar.
Click to expand...
Click to collapse
I hate to say this, but its probably the fact the phone does not like ICS, it is more than likely some sort of hardware incompatibility issue.
I went through this exact same thing, it was on a 1009 or so build number captivate, no matter what flavor of ICS, none of them would work properly with the touchscreen hardware, there was always a spot of the screen, at the lower center 1/4 portion of the screen, that was unresponsive. Flashing a Froyo or Gingerbread rom, the touchscreen was perfect.
So.. I sold that Captivate, purchaced a refurb Captivate off Ebay, and touchscreen is perfect with ICS (CM9 is what I run).
Wish I had something more helpful, but that's my experience. Good luck with it.

[Q] Touchscreen sensitivity issues in CM9/CM10 (but not webOS)... any advice?

Hello, I am having some touchscreen problems with CM9 and 10, but not with webOS. Namely, I think that the tablet is detecting double or even triple taps when none are present.
In CM9, when I execute a longpress (to move an app for example), the tablet just kind of... spazzes out, and in general nothing happens. In CM10 it also does this, and almost everytime, it starts whatever app I was pressing on.
Also, when I try to type in the CM10 keyboard, 2-4 characters are being entered at a time, unless I touch incredibly lightly, and even then, I will often get two.
There are other symptoms along these lines, like trying to pull up the notifications, etc. This does not appear to be isolated to any one portion of the screen, it is happening everywhere I could check it.
This CM9 versions I have tried are the nightly 0715, and whatever the latest nightly was about a week ago. The CM10 version I am using is jcsullins' 12/16.
As stated, I have zero issues in webOS.
Is there any way to change the touch sensitivity? Am I a moron and doing something wrong?
Thank you for your help/advice.

To clarify, I think this might be two separate issues...
I'm not as concerned with the CM9 issue, as it is only a mild annoyance and everything else is outstanding. CM10 is virtually unusable, however, so I'm hoping someone can help me out there.

thatdumbguy said:
Hello, I am having some touchscreen problems with CM9 and 10, but not with webOS. Namely, I think that the tablet is detecting double or even triple taps when none are present.
In CM9, when I execute a longpress (to move an app for example), the tablet just kind of... spazzes out, and in general nothing happens. In CM10 it also does this, and almost everytime, it starts whatever app I was pressing on.
Also, when I try to type in the CM10 keyboard, 2-4 characters are being entered at a time, unless I touch incredibly lightly, and even then, I will often get two.
There are other symptoms along these lines, like trying to pull up the notifications, etc. This does not appear to be isolated to any one portion of the screen, it is happening everywhere I could check it.
This CM9 versions I have tried are the nightly 0715, and whatever the latest nightly was about a week ago. The CM10 version I am using is jcsullins' 12/16.
As stated, I have zero issues in webOS.
Is there any way to change the touch sensitivity? Am I a moron and doing something wrong?
Thank you for your help/advice.
Click to expand...
Click to collapse
I've not had this issue, but this might help. Go here : http://goo.im/devs/jcsullins/cmtouchpad/testing
Download the touch pressure utility (should be the last one) and flash it. Hope it helps.
Good luck.

As an update, after shelving the touchpad for a few months, I have revisited it, and, after doing a clean install of jcsullins' CM10.1 w/BT Fix (20130808), the same issues as above still persist. I've done the following, although I didn't really expect most of them to work:
Switching to stylus mode (no difference)
Changing the accessibility settings for touch & hold delay
Even went so far as to install another launcher (nova) to ensure it wasn't trebuchet (not that I think it was)
Same for the keyboard
This has never been an issue I've seen in webOS... additionally, I don't remember ever having any issues in CM7 either. I did play with webOS for some time today to make sure it wasn't some kind of hardware failure between now and the last time I used it frequently, but I failed to reproduce the problem there.
Is there any light someone can shed on the subject? Thanks!

Thanks for that Chicle_11... I don't know why I failed to mention it, but I did also try the patches with CM9, but it is to my understanding that they were rolled into cm9 nightlies at some point?
I wonder if I could be having a minor hardware issue that just isn't severe enough to display in webOS, because I can't seem to find anything else about this, especially the keyboard problem with CM10. Its bizaar for sure.

Started experiencing the same issues after upgrading from cm9
I recently upgraded from cm9 to cm10.2 and immediately noticed this issue. There were no such issues with cm9. When swyping on the keyboard (any - Google, Swype, etc.), the system registers that I lifted my finger, and so garbage gets typed - you can also see the effect in the trace. When typing instead, letters sometimes double-up for a single press. When playing games like PvZ2, dragging a plant results in a release of the plant before I've lifted my finger, and sometimes the plant gets planted across the screen from where my finger is pressing.