Related
No matter what I do and however many times I flash cm7, I seem to have erratic touchscreen behavior.
The nook is BRAND NEW (two days) and I flashed it with cm7 7.0.2 stable (after phiremod's 6.0 & 6.1) and flashed it about four times now.
I have tried it with the OC and without.
It's not the SD - it doesn't matter if it's in or not.
Not the wifi, since I didn't even set it up the third and fourth time - it was too erratic to even try.
Plugged in or not... still the same problem. Doesn't seem similar to the other forums topics about touchscreen issues WHILE charging.
Screen is near spotless... no smudges.
It is important to note, that it waits until I have done a few things to start going crazy. I restart it and it's fine, until I do some cpu intensive stuff - live wallpaper is the simplest activity that causes it.
Any ideas?
I have also tried NSR (screen re calibrator) to no avail.
Would love a quick fix rather than re-installing stock and returning it and convincing them to replace it. I am not sure if it does it with stock... didn't wait long enough to find out before flashing it.
have you tried a screen protector? my screen wasnt the best for precise touches but since i put a screen protector on and clean the screen regularly it has since changed my problems to almost non existant.
Sent from my NookColor using Tapatalk
Others may be able to help you more than I can with exactly when the CM7 may be doing this, but returning to stock to find out is actually not hard at all.
In the development thread there is a post that has the 1.2 stock zips (one keeps CW in place, the other returns it completely to stock). Which ever one you pick it's still just as easy to return to stock as to reflash CM7 again. This is especially true if you used a SD card with CW to flash (which is what I do), since when you want to go back to CM7 you won't have to worry about flashing CW to emmc again.
angelic.pariah said:
No matter what I do and however many times I flash cm7, I seem to have erratic touchscreen behavior.
The nook is BRAND NEW (two days) and I flashed it with cm7 7.0.2 stable (after phiremod's 6.0 & 6.1) and flashed it about four times now.
I have tried it with the OC and without.
It's not the SD - it doesn't matter if it's in or not.
Not the wifi, since I didn't even set it up the third and fourth time - it was too erratic to even try.
Plugged in or not... still the same problem. Doesn't seem similar to the other forums topics about touchscreen issues WHILE charging.
Screen is near spotless... no smudges.
It is important to note, that it waits until I have done a few things to start going crazy. I restart it and it's fine, until I do some cpu intensive stuff - live wallpaper is the simplest activity that causes it.
Any ideas?
I have also tried NSR (screen re calibrator) to no avail.
Would love a quick fix rather than re-installing stock and returning it and convincing them to replace it. I am not sure if it does it with stock... didn't wait long enough to find out before flashing it.
Click to expand...
Click to collapse
Hate to say it but it sounds like it might turn out to be a hardware issue. This is not a CM7 issues that I've seen from anybody.
Can you describe the behavior in more detail?
dalingrin said:
Hate to say it but it sounds like it might turn out to be a hardware issue. This is not a CM7 issues that I've seen from anybody.
Can you describe the behavior in more detail?
Click to expand...
Click to collapse
It seems to start selecting things on its own after I have been using it for a while. It's difficult to describe except that there isn't really a pattern... it selects something different and keeps at it. At one point I almost purchased an app from the market before I had to power down.
I will return it to 1.2 stock and report back. I was mainly wanting to know if these was a commonly reported issue or not. I guess it's not. Thanks for the help everyone!
angelic.pariah said:
It seems to start selecting things on its own after I have been using it for a while. It's difficult to describe except that there isn't really a pattern... it selects something different and keeps at it.
Click to expand...
Click to collapse
So my NC started to do the same thing last night. I have been running CM7 (at 7.0.2 now, but nightlies before then with dal's OC kernal) for quite a while now with no problems. Only thing I did last night was to delete about 1GB of ebooks off of my NC and reload them through Calibre.
I left it alone last night after it started doing it and then this morning it started doing crazy touches again. I was in Aldiko and it was selecting books and turning pages at random. Rebooted and it seems to be fine for now. Little odd though considering it has been running perfect for a few months.
bucketheadmn said:
So my NC started to do the same thing last night. I have been running CM7 (at 7.0.2 now, but nightlies before then with dal's OC kernal) for quite a while now with no problems. Only thing I did last night was to delete about 1GB of ebooks off of my NC and reload them through Calibre.
I left it alone last night after it started doing it and then this morning it started doing crazy touches again. I was in Aldiko and it was selecting books and turning pages at random. Rebooted and it seems to be fine for now. Little odd though considering it has been running perfect for a few months.
Click to expand...
Click to collapse
So now I have installed nook stock 1.2 and NO PROBLEMS. I have run everything trying to get something to happen, and nothing.
Is it possible that I installed something the wrong way with cm7? Could I have used the wrong CWM version (3.0.0.6)?
Should I try cm7 7.0.2 or something else again?
I would try and return it, but I can't recreate the problem... if I could, I would be in their face right now.
Thanks for the help so far.
I think I solved it!
The newest nooks (in the last week or so) have 1.1.0 factory stock. Apparently there is a glitch that has been reported a lot recently about handling the touchscreen AND the SD card. These were fixed in the 1.2 upgrade. SO...
1. I flashed factory stock back on (in this case I went back to 1.0.1)
2. Then turned it off and "restored factory" settings using "Power+N" to turn it on. Repeated that a second time to get B&N's factory reset screen to come up.
3. Pressed N twice to accept restore prompts.
4. Upgraded to 1.2 (no glitches already by this point with touch or SD)
5. Booted CWM 3.0.0.6+
6. Formatted /system & /data
7. Flashed phiremod 6.1
8. OC'd to 1.1Ghz
...and DONE. No problems so far. I still see the "Read Forever" opening screen, but it still works wonders. WAY better than before.
I am still having issues with Wifi, but I can deal with that.
Now to attempt dalingrin's OC to 1.3!
Thanks guys... hope this helps others.
I think they call it "Touchscreen goshting". It started happening to me when I rooted the nook and the keyboard would go crazy. Now in CM7 7.0.2 with latest kernel, it happens more frequently. About 5 minutes in from boot, fast random touches occur. Most of the times this gets fixed by pressing the power button to turn the screen off (sleep), and on again. I guess it could be a hardware issue where some devices are affected. I haven't tried any recalibration apps to try to fix it yet, its kind of annoying when it happens in fast intervals.
I had weird touchscreen issues when using the interactive cpu governor. I later found only performance is supported. Using performance setting, everything works much better.
queseyo said:
I think they call it "Touchscreen goshting". It started happening to me when I rooted the nook and the keyboard would go crazy. Now in CM7 7.0.2 with latest kernel, it happens more frequently. About 5 minutes in from boot, fast random touches occur. Most of the times this gets fixed by pressing the power button to turn the screen off (sleep), and on again. I guess it could be a hardware issue where some devices are affected. I haven't tried any recalibration apps to try to fix it yet, its kind of annoying when it happens in fast intervals.
Click to expand...
Click to collapse
I had the same issue. I exchanged it the other night and now my new one does not have the problem. It probably a hardware issue...i hope you are still under warranty!
Not sure what is going on. I experienced it on stock rom, and I'm also experiencing it on Android Revolution HD Rom.
It seems like whenever the phone is tasked by an app opening or closing, I experience a random reboot.
Anyone know whats causing it?
Yeap me too, but only after closing final fantasy IV.. Dunno what's the deal here
°° no rest for the wiCKed °°
anyone?
S_Dot said:
anyone?
Click to expand...
Click to collapse
Me, too, but I didn't catch any regularity, yet.
I am on stock ROM.
One time a had a crash report from htc, but most times I only realize it, because I have to re-enter my pin.
Today I realised, that long-pressing the power-button does restart the phone without any other input.
Maybe it's that?
I'm using developer edition and have been suffered from heavily random reboot.
The phone rarely rebooted (2 or 3 times) while I was using it but just kept rebooting if I left it idle (5 reboots in 20 mins). I cannot reproduce the reboot because it was so random. One day, it just kept me annoying by rebooting itself more than a dozen time. The other day it just went super smooth and stable. This reboot has been happening on both completely stock and custom (Rom, kernel).
Anyone got a clue?
If you know a certain action is causing the reboot get a logcat, there's an app called catlog on the play store. Press record, repeat the action, after it reboots get the logcat and post it here
Sent from my Tricked out HTC One
Same issue here! I'm using TrickDroid though. Has anyone tried this with 4.2.2 to see if it still happens?
Sylpher said:
Same issue here! I'm using TrickDroid though. Has anyone tried this with 4.2.2 to see if it still happens?
Click to expand...
Click to collapse
I'm using Android Revolution ROM on 4.2.2., same thing. It happens once in a blue moon, and it's only on wake when I hit the power button. The whole phone freezes and reboots.
Is everyone here on the Developer's Edition?
I'm having the same issue, dev edition stock except recovery, and root. Some days it reboots, other days its fine. Not exactly sure whats up w/ that
Sent from my HTC One
I'm gonna go ahead and bump this, seeing as I'm facing the same issue on my 2 day old device.
At first I thought it was a problem with 4.1.2, but even after upgrading to 4.2.2 the issue is still there.
ViperOne 2.1.0 the same trouble
Hello,
I confirm the same problem on ViperOne ROM. I have tried out ElementalX 3.4 and Bulletproof kernels. But it seems to be kernel independent.
I attached the log, my configuration is as described in my signature except that I use Bulletproof kernel right now.
It is quite frustrating cause I just wanted to play a movie on my TV using Hama MHL cable, but everytime I connect my phone to the adapter the phone reboots, then it gets stuck on HTC logo, then I have to reboot it manually holding power button. I am also experiencing a reboot right after phone boots up.
This is such a serious issue that I am thinking of going back to stock kernel, but I am not sure if it will help
Any hints?
EDIT: I just installed stock kernel, but still the same, really does not seem to be a problem of the kernel
EDIT2: still trying to find the out whats the problem, I did a clean reinstallation of everything, even w/o using Titanium Backup, well, MHL still causes reboots
OmniROM
Lollipop - Android 5.x
A new "unified" Galaxy Tab 2 section was added to our forum because we don't make a difference between p31xx an p51xx specific roms.
Please use the Thread here for Omni 5 related questions and feedback
Reserved
Downloads:
Unofficial Builds by me
ROM Downloads for all supported devices can be found here
SuperSU http://download.chainfire.eu/supersu
GApps:
by @Deltadroid http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
or http://forum.xda-developers.com/android/software/gapps-google-apps-minimal-edition-t2943330
Can't wait to try this out. Loved omnirom ROM 4.4.4 on my tab until I tried your recent SlimLP ROM on it
Sent from my Nexus 5 using Tapatalk
New builds late this evening
Send from OnePlus One using Tapatalk
Android-Andi said:
New builds late this evening
Click to expand...
Click to collapse
Will definitely try this out - Omni 4.4.4 was perfect - I expect nothing less here (over time of course). Thanks Andi.
Builds are up
Send from OnePlus One using Tapatalk
FYI... Cant get it to boot! First tried with dirty flash from SlimLP then a clean... But no luck. Get stuck on bootscreen...
cheeseous said:
FYI... Cant get it to boot! First tried with dirty flash from SlimLP then a clean... But no luck. Get stuck on bootscreen...
Click to expand...
Click to collapse
Likewise with a P5113 here, booted first time after clean flash with pico Gapps and supersu 2.40... but after first reboot and 2 force reboots... still hanging on boot screen with a blank faced android blinking and wondering. Black to SlimLP for now. Thanks again Andi.
Lolli!
I installed the latest build and its working great in my P5110
I didn't even had any major bug yet (Only clock app not working)
Android-Andi said:
Builds are up
Click to expand...
Click to collapse
Reporting: Did an update from last years version.
Wiped C + DC
Flashed Rom + SuperSU
Rebooting .... took approx. 7 minutes ... done
Settings done,
Reboot,
Stuck at boot logo ... left for about 15 minutes
Wiped C + DC again,
Rebooted successfully this time.
Used for an hour or two, than reboot again, stucked at boot logo again...
After wiped C + DC again without no apparent reason: Booting successfully.
Restoring SlimLP with TWRP. Will test next build Andy when available.
@Gregzi thx for testing. I'll run new builds tonight...
Send from OnePlus One using Tapatalk
Testing Build 20150107
Testing latest build:
- Clean flash Rom + Gapps + Supersu 2.40
- Boot time reduced to 3 minutes
- Setting everything
- Noticed that SuperSU is this time correctly pushed into the system (in previous builds I had two:
one in Launcher and one in Settings ==> sometimes problems with root - TBackup)
- Shutting down the tablet
- Booting - again stuck at Omni boot animation (left it for about 10 minutes)
- Force reboot to TWRP (with two button combo)
- Reboot into the system from TWRP without cleaning anything
- Booting normally in 1 minute
When OC the frame rate is now 32,8 fps (Nenamark2), so better than previous builds, so certain progress is done.
The tablet feels smoother - especially noticeable when opening app drawer.
BR
installed over omni 4.4.4 without wipe.
first boot took about 40 mins, updating 173 apps.
some bugs:
firefox beta won't run
home button does not work
still collecting experience, but it doesn' t look too bad ?
Cheers and thanks alot, s.
sent over omni
sebastel23 said:
installed over omni 4.4.4 without wipe.
first boot took about 40 mins, updating 173 apps.
some bugs:
firefox beta won't run
home button does not work
still collecting experience, but it doesn' t look too bad
Cheers and thanks alot, s.
sent over omni
Click to expand...
Click to collapse
Home button gets fixed by flashing Gapps!
DarKnighT916 said:
Home button gets fixed by flashing Gapps!
Click to expand...
Click to collapse
thanks, but actually i had flashed Gapps (pico) already just after the ROM.
however, i'll try again later. :fingers-crossed:
in the meantime, i re-flashed gapps, with no change in behaviour.
for the time being, i'm back to 4.4.4.
bt issues
cannot connect bt headset. other features working fine, any toughts
only a question
I have a p5110 and runs pretty well but I've a problem with the minimum brightness it's very dark I can't see anything. any solution?
I loaded the 1/29 build last night on a clean install (with the latest Nano PA Gapps and SuperSU install zip, all on Andi's latest TWRP build). So far so good, here's a few observations:
-The first boot took a pretty long time but from what I've read this is normal. I didn't reboot again until the next day but for the second boot, the bootanimation never loaded, it just went straight from the brand logo to the launcher, long black wait in between. After that, all fine. Later I loaded the stock lollipop bootanimation I had been using previously (I do like the omni one a lot, though), and it used to lag a bit at the end on 4.4.4 but now it runs smooth all the way through, so that's encouraging.
-Turning the screen off (or letting it time out) is usually buggy, the screen flickers on/off for a second instead of any type of animation (I believe Lollipop is supposed to do a monochrome fadeout?) Edit: On closer inspection I see it is doing the monochrome fade, but then the screen flashes at the end of the animation.
-Re-installing apps was painfully slow and seemed to hang if I let the screen turn off (I'd find it sitting on the same install several minutes later). Downloading seemed a lot slower than KitKat ever was, too. I looked at the stats in settings->apps->running at on point in the process and the Play Store was listed as Restarting, perhaps this indicates poor memory management? Running the app in the foreground didn't seem to help at all, though.
-The material updates to the stock browser app are pretty swanky, I'm a fan. (I saw that in the gerrit and got excited. Not done yet but looks great.)
-Cast screen doesn't seem functional, doesn't find my chromecast. I've tested both Netflix and Localcast to connect just fine, LocalCast was a bit finicky the first time I tried but I think that may have been a network issue.
-I was testing a video call in in Hangouts and tried to mute the sound (was testing with my phone in hand and there was audio feedback loops because of that), but couldn't. Using the volume buttons, it wouldn't go all the way down, and if I dragged the bar the rest of the way it just wouldn't stick. Not sure exactly which volume control that was (lollipop's sound settings still confuse me in general), but I think it must be a bug of some sort that it wouldn't go down to mute.
-I had only just got around to trying to use my tablet's IR blaster (P5113) for TV control a few days earlier, and I found that the top several smart remote apps in the store don't work at all. Peel actually forces a soft reboot when it gets to the "push this button to test turning the device on" step, consistently. I did get one app working, which only includes remote IR support as a secondary function, TV Guide by Mini Group. Unfortunately the app isn't quite polished enough to be useful to me, but it was notable that it just worked where the others all get nothing. I didn't re-test all of the apps on lollipop but the ones I did(both of the ones linked here and a couple of the others that didn't work) behaved the same way.
-Visual performance generally seems a bit laggy but overall performance is fine (i.e. animations may freeze or lag but the tasks they're covering up don't suffer). Maybe all the animations in lolipop are just a bit rough on older hardware? I find them a bit overdone now that I've played around with things a bit more, personally (not that this reflects on the ROM). I don't really like stuff like shadows bouncing around as I scroll menus, though some of them are a nice subtle touch.
Overall I was happy with KitKat, but I think I'll let lollipop grow on me, these quirks are all minor. Idle battery life seems a bit worse but it's hard to make that call, I've been fiddling with the tablet more than usual to test things anyway.
Edit: Actually after letting it sit overnight unplugged, the idle battery is better than I was ever getting on KitKat. Granted, I made a point of closing all apps before and I think on KitKat I was having issue with casting apps holding wakelocks overnight and that's yet to be tested, but 1% over 12 hours is a pretty damn good baseline. Not sure what caused that wifi drop towards the end, after holding the connection (it gets a good strong signal) for about 11 hours, though.
Hey together!
Seems like we have some faulty eMMC chips, some reports of broken devices appeared.
I pushed a commit to address the issue and prevent other devices from damage.
I will recompile latest Lollipop roms and recoveries within 1 week.
For more information please read http://forum.xda-developers.com/showthread.php?t=3016879
Follow the instructions please to check your eMMC information.
Best regards and wishes!
Andi
Send from OnePlus One using Tapatalk
Internet sharing (mobile hotspot) doesn't work
Okay. . .so here's a little background on my issue. So, I have been running CM13 nightlies for almost a year without issue. The phone is encrypted (by choice) and I went to install the latest nightly (072216) and the install went great. As it boots up, it requests a password to be entered before it will boot. (Normal behavior, so far). But when I go to enter the password now, the keyboard is all messed up. Certain keys can be pressed and others cannot. Instead, when I press certain keys, it is as if the notification bar tries to come down. . .again, the phone is still encrypted and NOT booted up at this point. It only happens on the last 2 nightlies. . . .(072216 and 072316). Because the keyboard is acting strangely, I am unable to log in. The only way to boot it is to boot into recovery, reinstall the previous version and then all is well.
Any thoughts?
Don't use the newest nightlies until it's fixed? Or even better, drop cm and use a better ROM?
Kreateablaze said:
Don't use the newest nightlies until it's fixed? Or even better, drop cm and use a better ROM?
Click to expand...
Click to collapse
Ha! Actually, rather enjoy using the standard CM13 Rom. That said, I noticed something else. It isn't the keyboard that is the issue, but the lock screen icon is actually covering up the bottom line of the keyboard and not letting me get to it.
That's why you should use another ROM. The Cyanogenmod crew simply don't test the things they throw into the ROM anymore, leading to incidents like this one.
Help[emoji21] So my problem is when I use a single finger(eg. Right Thumb) the touch doesn't work on my phone[emoji22](Nothing so unusual....right? But wait for it). However when I hold down a finger(eg. Left Thumb) on the screen and then use another finger(eg. Right Thumb) the touch works absolutely fine(Note that even though I've 2 of fingers on the screen, its getting registered as a single touch....not two). Now that is weird[emoji44]...
Now back to the case where a single finger is on the screen... As I said, the touch doesn't work...right? But it does work.... to a certain extent(I don't know how to put this[emoji28]...but I'll try anyway). Certain highlightable options(those in settings app, notification panel, etc) gets highlighted upon touching by a single finger... But I'm not able to scroll, open app, or anything touch related except highlighting(with a single finger). 'Show Touches' under Developer Options doesn't show this touch.
I'm on Lineage OS and I'm pretty much sure this wasn't supposed to be a ROM feature(As I faced similar issues on Resurrection Remix). Also, sometimes when I reboot, the problem gets resolved until next reboot. I had recently replaced the digitizer(by myself). So I'm not sure whats causing it..... If only someone could help[emoji25]
Sent from my Cloud_Cube using XDA-Developers Legacy app
Have u tried Mokee ROM? It's pretty good! My issues same as yours got mostly fixed by switching to this ROM.
lamtrinhan1503 said:
Have u tried Mokee ROM? It's pretty good! My issues same as yours got mostly fixed by switching to this ROM.
Click to expand...
Click to collapse
thnx for the reply I really appreciate it... I will surely try Mokee ROM and hope that fixes it
Is the problem solved? Cause I have a same issue with my xperia. First I used Stryflex Marshmallow then changed to Stryflex Lollipop and now I am using CM 14.1 But the problem still there :crying:
Brah ! Just flash doom lord kernel using flash tool and fastboot
Then boot sequence is
1when your phone turned on and you can see sony logo then continuously press vol down button after that you have to wipe/factory reset your phone and then wipe cache partition then wioe dalvik cache in advanced tab then install/flash the zip(ROM) you want.