Related
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.
I've tried searching other threads/posts but I don't see any solutions at all. I want to first rule out the problem being with the software before I send my Nexus One to a mobile phone technician for hardware repair.
Here's the situation. I got my Nexus One used, at very cheap price but with slight defect that the seller kindly informed me about. The brightness control is not working. He said that it started happening after installing CyanogenMod7 from stock rom.
I still purchased it from him and now it's my problem. I tried looking for solutions. Here's what I did so far:
reset the phone, including formatting the sdcard
installing 3rd party brightness controllers
reinstalling CyanogenMod7 and even used CM6, I've also used nightly and RC CM7
trying other roms (those that do not require modifying hboot [blackrose])
Having said the last item, that is something I have yet to try and really giving it a good thought before finally trying because of some cautions regarding Nexus One having SLCD as indicated by MICROP 0c15.
One thing to consider as well, whenever I run the stock clock app and press the brightness icon, the backlight does get dim so I'm thinking that the brightness can still be controlled.
Any ideas, guys?
Btw, as you can see, this is my first post. Apparently, I cannot find the solution myself so I had to ask.
Thank you in advance.
I have the same issue on both stock rom and the great CM7, Im hoping there is a fix for this.
It seems that only very few experienced this problem and the fact that there aren't any helpful reply means that there is no solution for this issue yet.
I really don't want to believe that this is a hardware failure, though.
dojavanese said:
It seems that only very few experienced this problem and the fact that there aren't any helpful reply means that there is no solution for this issue yet.
I really don't want to believe that this is a hardware failure, though.
Click to expand...
Click to collapse
try screen filter app from play store ..
I've tried using screen filter app and it was able to control the brightness but only to lower it.
Compared to other android phones, the brightness on my nexus one is definitely not on it's highest setting even if the screen filter app says it's on 100%.
It's like it's on 50% brightness.
Could the hboot have something to with this? I'm using 0.35.0017.
Having SLCD on it prevents me from fooling around with hboot flashing.
Any other ideas, guys?
Same problem
i on slim rom 4.3.1 on my LG P990, before the hard reset evrything was fine..n after that brightness controll dailed..
i guess ill have to Hard Reset again
but i dont wnat to..
so i guess lets just stick with it..
Normally I don't have a problem locating this kind of info, but for TP CM9 it eludes me. I found the link with the tech speak generated list. But I need the info to be a bit more plain english. And couldn't find a known issues list. I would like to check this info to see if I would like to try it out on my TP.
Thanks much.
StoneRyno said:
Normally I don't have a problem locating this kind of info, but for TP CM9 it eludes me. I found the link with the tech speak generated list. But I need the info to be a bit more plain english. And couldn't find a known issues list. I would like to check this info to see if I would like to try it out on my TP.
Thanks much.
Click to expand...
Click to collapse
Known issues are basically the camera and mic don't work, some folks have wifi issues and some don't... and some have issues with the audio acting up when waking from sleep... I myself am happy to say I don't have wifi or audio issues... but camera and mic are driver issues that may never get to work. All in all very stable though
Sent from my cm_tenderloin using Tapatalk 2
If camera and mic are the only problems then I see no reason not to give it a shot. I don't know if I would ever use them.I was concerned that it was missing core functionality making it something one wouldn't use as a daily OS and only switch over to it for test scenarios and then switch back. I have cm9 on my Samsung epic (the one with hw kb). Would the current latest nightly be the one to go with?
Just curious, why are the camera and mic drivers so difficult? I would have thought having them running on WebOS was at least some of the work. I guess porting said work to Android is a completely different ballgame.
I wonder if the wifi/audio issues are still being worked on tho? Or are those of us with those stuck with em forever?
The big thing for me was hardware video decoding. Alpha 1 fixed that for YouTube, and alpha 2 finished the fix for Netflix and others.
If you haven't already, check out the thread at rootzwiki.
I was using webOS by choice until CM9 came out. I switched to CM9, and have been using it as my daily driver since the very first Alpha. I never video chat, but if I wanted to I know I can just boot webOS.
Don't let people here tell you CM9 (or the Kangs thereof) are unstable. Some people continue to spew that we don't have a stable version of android purely because its called an alpha. I don't think it will graduate past alpha without camera/mic support, and that may never happen. Right now, without trying, I am sitting at 587 hours of up time on my TouchPad. I can't think of a better word to use than "stable."
Sent from my Galaxy S II (i777)
Known Issues that I can think of. I know some were mentioned above, but all in one place is good.
Broken, NO FIX:
1) No Microphone
2) No Camera
Partial Workarounds:
1) Audio gets noisy with screen off. Kinda workaround: Turn volume down, only happens at higher volume levels. Or set screen timeout longer/always on while playing audio. No complete fix.
2) Wi-Fi dies or doesn't reconnect. Some people never have a problem, others do. Workarounds: First, set WiFi to always on so it doesn't turn off with the screen. Second, try changing the channel on your router, or if you have 2.4ghz/5ghz switchable, try using the other. If Wi-Fi still dies, toggle it off and back on.
3) Some people report that if the TouchPad fully discharges to 0% they have trouble getting Android to charge properly. Others report that if you reboot the device with it plugged in, sometimes it won't charge. I've experienced neither problem, but the best advice is, charge before the device shuts off fully, and unplug the charger/usb while booting.
Broken, but Completely Fixable:
1) Random crashes. Install CPU Master and raise minimum CPU speed to 384 or 416 depending on which works for you, and crashes go away. Also, don't overclock too much.
Setup Issues:
1) DPI is at 160dpi stock. This works for most things, except a few tablet apps and games will not work properly. Setting DPI to 120dpi fixes everything, but the display quality is not ideal. 132dpi is ideal, but breaks the market after a day or two. Most people use 160dpi or 120dpi.
2) The default launcher, Trebuchet, is NOT compatible with the 4:3 aspect ratio of the TouchPad's screen if you use any DPI other than 160. Why something so easily fixable has not been fixed escapes me, but you will quickly find you need a new launcher. Go Launcher HD is one of a few that are very friendly to the TouchPad.
App Issues (not really issues but you probably want to know)
1) A few apps really, really, really are picky about the screen size and just won't scale right. (see Trebuchet notes above). One example is Politico HD - it forces 16:9 aspect ratio and thus gets cut off. Some apps simply refuse to run. Contacting the developers rarely works. This is probably less than 1% of the apps on the market, however.
2) Some developers simply are too strict on app compatibility on the market, and whitelist only select devices. Getting compatibility from these guys is a longshot. Best option is to install on another device, grab the APK or use Titanium Backup to move the app to the TouchPad.
3) Some games (notably Gameloft is the worst) enforce device compatibility checks within the program itself and it will refuse to run unless you masquerade as an approved device by hacking your build.prop... which is not normally recommended.
Did I miss anything anyone?
It seems that my Accelerometer isn't functioning correctly, it doesn't give me proper readouts unless the app in question has a calibration tool inside of it, and even then it doesn't fix it on other apps. I've tried the calibration tools in various apps to no success, I'm forced to use another app simply to change orientation while doing regular things like web and youtube.
When I have The Night Sky open it seems to be stuck looking down, and moving my phone just makes it turn left and right randomly.
Anyone have any ideas to help?
Flashing different ROMs and Kernels doesn't help.
Only thing I haven't tried is possibly flashing a GB rom and calibrating with that...
I am opening this thread for people to discuss issues with the CM10.1 and share solution and fixes that they have found to solve these issues.
I have noted that the auto brightness does not work for me. I do not notice any change in brightness in different light settings and it seems to be frozen. Does HD+ comes with a light sensor and is it supported by CM10.1.
Another thing I wanted to ask. Can we use MHL adapters to connect a Nook to a tv through HDMI. I was looking for an alternative to Nook branded adapter.
Thanks
excalibar001 said:
I am opening this thread for people to discuss issues with the CM10.1 and share solution and fixes that they have found to solve these issues.
I have noted that the auto brightness does not work for me. I do not notice any change in brightness in different light settings and it seems to be frozen. Does HD+ comes with a light sensor and is it supported by CM10.1.
Another thing I wanted to ask. Can we use MHL adapters to connect a Nook to a tv through HDMI. I was looking for an alternative to Nook branded adapter.
Thanks
Click to expand...
Click to collapse
I'm pretty sure there is no light sensor on a tablet that has no camera.
Overall CM 10.1 is a whole lot better than stock 2.1. Some games do not work that did with stock (Buggy Blitz, Moonshiners and NBA 2013), but all the Zen Pinball Star Wars games work (they did not with 2.1).
With CM 10.1, you can not get any more less intrusive with Android, especially compared to stock on the Nook HD+. The good news is there is no more stutter with apps and a lot of apps load faster. The bad news is some apps still load slow and there is intermittent lag when pressing to start apps or navigate. Tapatalk is an example. There can sometimes be a 5 to 10 second delay from the time the app is activated to the time there is an action. Same with navigating and with other apps as far as lag such as browsers and games. The weird thing is when games play, there is no lag or signs of touch response problems. Games play well and so do virtual pads for game emulators. The issue is not touch sensitivity, since the press registers, but sometimes takes a while before an action happens.
For whatever reason, the Nook HD+ has an intermittent lag problem that also existed with stock 2.1, though the app stutter has thankfully gone away. The lag really stands out when comparing to my S3 and Excite 7.7. Those both are stock, but respond instantly when activating and navigating apps and only have slight issues if updating apps in the background.
My Razr had a 4430 and was not laggy. The higher display res should not be a factor for such dramatic lag issue with the HD+. The lag seems to happen about 30% of the time, if I were to guess. For what I want it for, the lag is not a big issue, but seems to make no sense. Both HD+ I have used have the issue, but was hoping CM 10.1 would be the answer to fix it.
Bad memory management, perhaps? Added: Nope, if so, games in action would be laggy as well.
channeledbymodem said:
I'm pretty sure there is no light sensor on a tablet that has no camera.
Click to expand...
Click to collapse
You are right, there is no light sensor so autobrightness does not work.
Sent from my Nook HD+ running CM10.1 on emmc.
rushless said:
My Razr had a 4430 and was not laggy. The higher display res should not be a factor for such dramatic lag issue with the HD+. The lag seems to happen about 30% of the time, if I were to guess. For what I want it for, the lag is not a big issue, but seems to make no sense. Both HD+ I have used have the issue, but was hoping CM 10.1 would be the answer to fix it.
Click to expand...
Click to collapse
I need precise steps to see the lag, then I can profile it and if stars align right - fix.
Hashccode encountered some bad lag on KFireHD on (what he thinks) is some bad unnecessary waiting in kernel.
I do not see any of it, though, so cannot do anything about it.
verygreen said:
I need precise steps to see the lag, then I can profile it and if stars align right - fix.
Hashccode encountered some bad lag on KFireHD on (what he thinks) is some bad unnecessary waiting in kernel.
I do not see any of it, though, so cannot do anything about it.
Click to expand...
Click to collapse
Tapatalk seems to be a poster child app for the issue. It does seem like a wait state issue. Added: That said, it does not do it all the time, so probably not app specific. I just use Taptalk a lot. The lag seems to happen with most apps, but not all the time. 30% of the time seems about right. The good news is the stutter issue that was them main problem IMO with stock 2.1 is gone. No sign yet, in spite of the intermittent app start and navigation lag.
What app can I install to log the issue?
Thanks
rushless said:
What app can I install to log the issue?
Click to expand...
Click to collapse
I don't think there is a good one for logging.
I just need to be able to reproduce myself so I can poke at it from multiple angles.
It does seem to be an app start/stop and navigation lag. No lag when using touch or virtual controls in games.
Not having the stutter in the GTA games is nice. It was GTA Stutter City with stock 2.1. as in many other games. Smooth now, while playing a game.
channeledbymodem said:
I'm pretty sure there is no light sensor on a tablet that has no camera.
Click to expand...
Click to collapse
While I agree that HD+ may not have a light sensors, however, a light sensor has nothing to do with camera and primarily used to control the screen brightness. A camera can detect brightness through its image sensors which is separate from a light sensor.
Does stock firmware have auto brightness setting? Can not remember, but I thought it did.... I tend to not use it.
verygreen said:
I need precise steps to see the lag, then I can profile it and if stars align right - fix.
Hashccode encountered some bad lag on KFireHD on (what he thinks) is some bad unnecessary waiting in kernel.
I do not see any of it, though, so cannot do anything about it.
Click to expand...
Click to collapse
I would like to thank you first verygreen for your efforts. You have made the HD+ such a useful tablet.
I have noticed that sometimes my screen would turn off momentarily for no reason. This happen more frequently when I am using and charging he tablet at the same time. I believe that it is due to the magnetic cover flap sensors which goes awry for some reason. Is there a way to turn this sensor off for those of us who are not using a cover with magnetic flap?
rushless said:
Does stock firmware have auto brightness setting? Can not remember, but I thought it did.... I tend to not use it.
Click to expand...
Click to collapse
No, as many have said here, including me, there is NO hardware sensor, so auto brightness cannot work.
Sent from my Nook HD+ running CM10.1 on emmc.
As mentioned, I do not use it, but would not be the first time for a phantom setting. Look at stock 2.1 and the slow app loading, stuttering state that it is. Not exactly a model for strict user experience QA.
Getting about 4 or 5 random reboots per day but everything else seems fine. Using greenify to hibernate apps
Sent from my BN NookHD+ using Tapatalk 4 Beta
Not had a random reboot yet.
Must be some misbehaving apps since I have never had random reboots. However, my screen flicker once in a while if I charge and use it at the same time.
mrpunk2u said:
Getting about 4 or 5 random reboots per day but everything else seems fine. Using greenify to hibernate apps
Sent from my BN NookHD+ using Tapatalk 4 Beta
Click to expand...
Click to collapse
You might want to check to see if you have GPS checked in location services. If you have that checked and an app like Google Maps runs in the background, that sometimes causes reboots.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
You might want to check to see if you have GPS checked in location services. If you have that checked and an app like Google Maps runs in the background, that sometimes causes reboots.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
GPS is off - not sure what's causing it - Also, i keep getting Google Sign in errors and asks for my password at least 2x daily
Intermittent lag aside, I use the Nook now more than the iPad 4. Same nice display clarity and not locked down.
Wild how an OS mod can change perspective on a device so much.
My biggest problem has been with touch, it's not that responsive sometimes and sometimes I have my finger hovering over a button and it clicks it (is that phantom clicking?).. Overall it's MUCH better than stock and mad props to all the developers. My girlfriends tablet has been getting random reboots as well, i'll check to see if GPS is on.