[Q] Screen not timing out - Nook Color General

Since last night, my screen stopped timing out. I've been playing around with trying to get wallpaper to look right, and have installed Wallpaper Set & Save (didn't make it look right) and WallpaperCASA (can't figure out how to use custom wallpaper). Not sure if installing them is related, but a few hours after, my screen no longer times out. Eating battery charge. I can't find a setting in either one of them that has anything to do with this. And the screen was timing out fine immediately after installing them.
Timeout settings are set to 2 minutes. Does anyone know of another setting that controls this?

loribuono said:
Since last night, my screen stopped timing out. I've been playing around with trying to get wallpaper to look right, and have installed Wallpaper Set & Save (didn't make it look right) and WallpaperCASA (can't figure out how to use custom wallpaper). Not sure if installing them is related, but a few hours after, my screen no longer times out. Eating battery charge. I can't find a setting in either one of them that has anything to do with this. And the screen was timing out fine immediately after installing them.
Timeout settings are set to 2 minutes. Does anyone know of another setting that controls this?
Click to expand...
Click to collapse
Just ran into this myself....anyone, anyone?
I wasnt messing with wallpapers just screen timeout stopped working.

Got the same issue (no screen timeout) but with some odd thing. When I try to setup the screen timeout choosing "screen" on setup menu... I´ve got an error... the setup process ends unexpectly. I´m using N114, lastest OC Kernel from Dalingrin.

Related

Any hack to stop phone from returning to today screen after power-on????

Is there a way to stop WM6 from going to Today screen when I turn it on? I want it to just return wherever I was when I turned it off. Thanks.
I believe it only happens if you have the PIN setup, at least on my Tilt.
Nope, it happens all the time. I'm in messaging, I turn the screen off and then on and it returns to the today screen. It is incredibly annoying.
Mine does not do that.
Must be a setting somewhere because I know other people have the exact same problem.
I also own the tilt and have the same problem. It's very annoying.
It is a setting issue..
On my Tilt this works: To stop the screen from returning to the Today screen, just go to settings > Personal >Today > Items and choose the Today timeout period from the drop down list.
No dice for me. It was one of the first things I tried before anyway. Its especially annoying when I'm using PocketPlayer and I turn off the screen to save juice and when I turn it back on again PocketPlayer flickers for an instant, then it goes back to the Today screen then I have to retap PocketPlayer, then it has to redraw. Ugh!!!
Yeah,i have this same problem with my TyTn...but it does not happen on a fresh ROM...which leads me to say that it has to be a program installed that is causing it...i have a Kaiser (that is awaiting warranty replacement) on the stock ATT ROM, and it does not do it, considering, i have no apps installed...
pocketplayer has an option to stop this: disable switching to home screen
Even in PocketPlayer toggling that option has no effect on my problem. I am convinced it is a simple registry setting but I don't know what it is.
Anyone have a solution to this?
Just got a Kaiser and I agree, this is extremely annoying. I was hoping there was a registry hack to stop this.
TSoma said:
Anyone have a solution to this?
Click to expand...
Click to collapse
Sure you can
Start->Settings->Today->Items->Today Timeout (Diable it).
This determaine after how much time it will display the today.
Disable it.
Enjoy,
Nadavi
Nadavi said:
Sure you can
Start->Settings->Today->Items->Today Timeout (Diable it).
This determaine after how much time it will display the today.
Disable it.
Click to expand...
Click to collapse
Nope. Checking or unchecking seems to have no effect. Even when checked, turning the device off and on will immediately show the today screen, not in the 4 hrs (or whatever you have it set for) in the dialog box.
Have you tried removing the PIN Lock feature under Settings>Lock?
Aha! the pinlock was set to 0 minutes for some reason. disabling it has sorted the problem for me.
Uberlad
Happy to Help
Mine is set to 60 minutes. If that truly is the fix, it isn't an acceptable one. Thanks for the info, but HTC should fix this.
its definitely not the fix. Mine was set to 15min and that's what I want it at in case I lose it. I am 99% sure its a registry setting and I am also 99% sure that I saw the fix in some forum on another site once but can't remember where or find it again.

Buggy damned Tilt official 6.1...

I've flashed my 8925 twice and hard reset it once, I've tried with and without having allowed the ATT customizations, and still there's a bunch of stupid little crap that is driving me nuts. Please note: these bugs are with no additional software installed.
Can't keep the backlight from timing out. I've always disliked the default of having the screen auto dim: if the screen is on I'm probably *looking* at it, otherwise I'd have turned it off... I've tried everything, setting no backlight time out, leaving it checked but matched to the screen shutoff, it shows the right thing in the control panel and stays on after I leave that screen, but usually within minutes or especially after I've used the phone it'll start dimming at 10 seconds again--even though turn off backlight is still unchecked in the backlight control panel.
Missed calls / call log badly broken: I'll get the missed call notification but when I try to see the caller it shows the log as empty, and when I go into the log manually from the phone app it also shows empty--doesn't even have my outgoing calls.
Voicemail notification got stuck on. I can probably call ATT and have them fix this on their end in minutes but it's bloody annoying that my phone's been notifying me of a long deleted voicemail message for days.
Anybody else having any of these problems?
Anybody know a fix for any of them?
I've already tried advanced_configuration, no great help there.
What's the latest/best cooked ROM? I like that the official has stuff like Voice Command and Sprite Backup, would like to keep them...
I haven't noticed any of those problems. I have however had problems with the phone being really sluggish at times. Still testing with no apps installed. I don't have the backlight problem. I have just used the settings in Kaiser Tweak and everything is working. Not sure that I will keep using it though. I will probably go back to Hyperdragon's newest ROM's. Those always seem to work really well for me.
No issues with the official AT&T ROM either.
wmg76 said:
I have however had problems with the phone being really sluggish at times.
Click to expand...
Click to collapse
Are you using the right SPL?
I did not try the rom. But I heard cleartype w/ landscape problem still exist w/ this rom (like the official HTC 6.1 rom). It could be fix by replacing the ddi.dll but will probably break Opera mini 9.5.
Problems??? Pull up a chair! First I installed the ROM and none of my would work. I couldn't connect to the internet. I downloaded the ROM again and reflashed it. This time icons started disappearing on my phone. I did a soft reset. Nothing. Did a hard reset. Nothing. I reflashed. Loaded my apps, they actually worked. I set up my email, and I could connect to the internet. Great! Finally! One hour later, I got a phone call, but my phone didn't ring. Huh?Anyway, answered it, when the other party spoken it came out the speakerphone. I checked my device and there was no sound: ringtones,music games,alarms. Soft reset...Startup sound played..loaded up and no sound. Call ATT for a help, they decided to send me a replacement. Bad device, I guess. So I redownloaded the ROM and tried a different phone( i know, i know), can't get email to work, can't get MMetrics work. I quit!I will be going to custom ROM! I have a lot of reading to do.
Been using the new AT&T Rom since it was released and not having any issues. The only minor problem I have is that I'm seeing some compatibility issues with the version of S2U2 that I am using. Otherwise, good to go.
I don't get how people are having problems with this. Everything works flawlessly with me.
Except threaded messaging sucks, but with Kaiser Tweak, I turned it off.
I have had only 3 major issues with this rom.
1: Camera works, but doesn't show anything on the screen. I have a black screen, press the capture button, and I get a picture, but I can't tell what I am looking at until I take the picture. Working on this issue now. [Update] I just installed HTC Camera v5.04 b29195.00 http://rapidshare.com/files/99227062/HTC_Camera_v5.04_b29195.00__PPC_.CAB . Works Perfect now!
2. Battery life was HORRID! After 10 minutes I was down to 90%, while it sat on the desk, screen off, nothing running. After switching from 1.65.21.18 to 1.65.21.14, life was peachy. 8 hours with normal usage and only down to 80%.
3. Blue Tooth drops erratically. I connected my bt headset to the phone, made a call, after 10 or 15 minutes, it dropped the headset. BT stayed turn on, but headset couldn't be found. Turned off headset, turned back on, magically found. Haven't figured out what is causing this, but am researching that as well. OK, So I got on HTC's website to see if there was an update. There is no update for BT for the Tilt WM6.1. However, there is a fix for TYTN II WM6.0. http://www.htc.com/europe/SupportDownload.aspx?p_id=13&cat=0&dl_id=60. I decided to try this fix, installed thinking I would get the whole "this program was built for a previous version" garbage, but I didn't get that. Anyway, I am going to try this tomorrow when I make my calls. I will update if I notice it fixes my issues.
Otherwise, it's fast, good signal, good sound quality, etc. Overall I am pretty happy. Will be happier when I finally get the BT to stop dropping, as I travel a lot and it's illegal to talk on the phone w/o a hands free on any military installation.... Sorry if I didn't answer any problems others are having on this actual forum, but maybe someone else will be having the same issue and see my posts for my fixes. Thanks!
zip, zero, nada.......UI is faster, apps are faster, threaded SMS is really nice to have, MSVC works as advertised with my JB2.
Different Alarm Sounds!!
I have a small WAV file that I use as an alarm sound but now can't get the sound listing in the alarm setup. I use to put it in application data/sounds. It now doesn't show up if I put it there or anywhere else (/windows, /my documents/my ringtones). Anyone else have this problem?
eltrebor said:
I have a small WAV file that I use as an alarm sound but now can't get the sound listing in the alarm setup. I use to put it in application data/sounds. It now doesn't show up if I put it there or anywhere else (/windows, /my documents/my ringtones). Anyone else have this problem?
Click to expand...
Click to collapse
All my WAV and MIDI files in the root of Windows show up fine. How small is the file? 600kb is the size limit for sounds on AT&T ROMs unless you modify the registry key that restricts it. 600k may be large for an mp3 file, but that's only mere seconds of a WAV file.
I upgraded as soon as it was available and am seriously considering going back to the old WM6.0 ROM, which worked well. I have had several lockups and had to soft-reset. I have also had problems with calls. Once, it rang and shoed me the call, but wouldn't let me pick it up. Other times I have had echos. GPS lock time is also much longer. Oh, yes, the equalizer in TCPMP creates terrible distortion. It worked great in 6.0. And I am using the recompiled version.
It is great to get results of satisfaction with the new ROM, but I personally would like to know, for those who have been having problems and those, answers to some questions:
1 Which SPL
2 Which radio
3 Activesync or POP for email
4 Bloatware installed or not
5 PIE or other browser
I am sure that there are others, but those are what come to mind for the moment.
No Problems Here
FWIW, I think my Tilt is running much better with the new ROM. I've only had it (the new ROM) for a couple of days, but TT7 and Google Maps seem to run faster, and It seems to detect WIFI networks MUCH faster than with the old ROM. I'm a happy camper, at least for now.
I've noticed that its been alot slower and I don't like having a button devoted to the ringtone volume. The other HTC Tab I was using that was supposed to be an official use had Music allowing me to access Windows Media very easily now I can't. I also noticed my dialing pad is different and not the same as it was. I also don't like the threaded SMS on Windows Mobile it doesn't suit it. It makes it look very confusing and also I've noticed it has problems moving the screen upwards so that I can see what is being written in the space. Another thing I notice is randomly the HTC Home screen cuts itself off cutting off portions of the tab information. Its something to get used to but I don't see it happening cause I can't figure out what happened to some items on the phone like my GPS doesn't work, I am experiencing worse internet problems than before, Wifi dies frequently, and the dialer doesn't seem to work like it used to. Its a disappointment.
NotATreoFan said:
All my WAV and MIDI files in the root of Windows show up fine. How small is the file? 600kb is the size limit for sounds on AT&T ROMs unless you modify the registry key that restricts it. 600k may be large for an mp3 file, but that's only mere seconds of a WAV file.
Click to expand...
Click to collapse
Which key? I have been hunting... and no luck so far.
Backlight timeout linked to lock??
When I re-downloaded the software and re-flashed a *third* time things seemed to work better. The only thing I did differently was skip the 'setup a password' that last time I flashed.
The phone worked pretty well all weekend, and then this morning I finally put in owner info and set a pin password.
And I just noticed the backlight has started dimming after 10 seconds (or less) again. Restart didn't correct it, nor did changing the setting in advanced config so the screen doesn't dim for unlock screen.
For now I turned off lock and went into the backlight tab and it's stopped doing it. BLOODY ANNOYING. I've seen mention of the backlight timeout bug in other forums too...
Even while the phone was working well over the weekend I noticed that fairly often the first attempt to bring it out of standby flashes the screen on then it goes back off, comes on and stays on when I press power the second time.
I ran into the idiotic bug where text is white on white when in landscape mode, know I saw something about that being a cleartype bug or something and there being a fix, but why the hell would it be released like that?
Also, I can NOT get the 'message sent' notification to disable... does 'advanced config' not actually work?
Buggy is an understatement!
Having been unable to bear/ignore the bugs I reverted back to 6.0
Here's what I along with you guys have issues with.
1)Ringtones revert back to it's default tone whenever I open: Settings>Phone
2) Back-light reverts back to 10 seconds at random and often.
3) Google maps will not display letters when searching for places, but it'll invisibly type
4) Typical freezes on pages and things of that nature
5) Bloatware..
SeekerJBP said:
Which key? I have been hunting... and no luck so far.
Click to expand...
Click to collapse
I'll help you out here
Go into HKEY_CurrentUser --> ControlPanel --> Sounds --> FileSizeLimit ( it's a DWORD value)
Just delete the DWORD value, and bam, enjoy .
EDIT : wow, just realized this is my first post. I've been browsing the site since the Tilt came out, but I guess I've never found it necessary to post. haha!
TheCritic said:
Can't keep the backlight from timing out. I've always disliked the default of having the screen auto dim: if the screen is on I'm probably *looking* at it, otherwise I'd have turned it off... I've tried everything, setting no backlight time out, leaving it checked but matched to the screen shutoff, it shows the right thing in the control panel and stays on after I leave that screen, but usually within minutes or especially after I've used the phone it'll start dimming at 10 seconds again--even though turn off backlight is still unchecked in the backlight control panel.
Click to expand...
Click to collapse
I have the exact same problem with my 8925. My work buddy across the hall does not have this problem with his 8925. Running WM6.0 my screen has ALWAYS dimmed at boot, as well as after a call ended; his has never done so. Now, after we've both upgraded to WM6.1, I have all my same problems, as well as the additional 10 second auto dimming that I did not encounter with WM6.0, he still has none.
No matter what settings I change, no matter if connected to power, USB, or none, my screen dims after 10 seconds. I can get it to temporarily revert back to the setting of my choice, by going into the settings and then back out, but if I manually dim the phone, get a call, or pretty much anything, it defaults back to the automatic 10 second dimming. I'm so pissed off about this. S2U2 also automatically kicks in on every screen dim, so I can't use it while the dim prob is going on. Certainly someone within this HUGE base of geniuses has a definitive answer for this.
Lots of little bugs in this release.
Google maps doesn't like it.
Can't get TCPMP to work.
Gets sluggish.
MSVC doesn't notify.
Other things I can't think of now.
Pretty irritating to say the least.

Clock Issue with Energy rom

The issue im speaking of is the actual home screen clock. Every morning I have to re set it because it ends up becoming off by a few hours. I searched this forum and couldnt find anything. I had also posted the question in the Energy rom thread, but it kept getting swamped out by random question. Im running a tilt 2 FYI.
Any help appreciated, thanx
uncleswoop said:
The issue im speaking of is the actual home screen clock. Every morning I have to re set it because it ends up becoming off by a few hours. I searched this forum and couldnt find anything. I had also posted the question in the Energy rom thread, but it kept getting swamped out by random question. Im running a tilt 2 FYI.
Any help appreciated, thanx
Click to expand...
Click to collapse
Did you set your time zone? Did you turn on or off internet time sync? Did you uncheck get time from network under phone settings? Any of these could be the cause of your problems...
Im feeling really dumb this morning...My alarm didnt go off this morning because of this same problem. And I cant for the life of me figure out hwo to make sure the clock is auto updating to the network.
Im running Energy Cookie Reference. I have seen the settings before...but cant locate them today.
Time synchronization?
Hi.
Do you have the automatic time synchronization on? Try to disable it.
Settings -> Personal -> Phone ->
or
Sense settings tab -> data services -> internet time sync ->
Hey thanks for the response...my settings are different though. I found the setting in BSB Tweaks and turned it off...only time will tell if it helps though...we will see if my phone fails to wake me up again tomorrow...
Left Energy yet again because of this issue...I dont know a whole lot about the technicalities but it seemed to me that the phone is 'going to sleep' and actually losing track of the time thus keeping my alarm from sounding in the mornings.
When I hit the power button to wake the screen up in the mornings it would be displaying a time that was hours behind and seemingly random (what lead me to believe the phone was in a deeper sleep than normal). Possibly a really stupid theory...but like I said I dont know a whole lot. I just know it was way unacceptable in my case.
I will still monitor his threads like always and try the latest and greatest ROMS.
Clock Issue with Energy romArrow
I think the problem you are having is the windows alarm bug. I used to get this all the time until i started using g-alarm. it fixes the issue when you first install it. (note that its a paid app.) but here is the description and the registry edit that you need to change to fix the problem.
can't post the link soo you will need to copy and paste the url below if you want to view the webpage.
ageye.de/index.php?s=galarm/support/manual/limitations
Windows alarm bug
Windows Mobile has on some devices a strange behaviour: Although an alarm is successfully added to the WM notification queue (it's like a scheduler) it doesn't go off.
Searching the web gave me following information:
At midnight WM rebuilds the notification queue, therefore it wakes up for about 15 seconds. If the notification queue is too big or the device too slow WM goes to sleep again before it could finish building the queue for the next day.
If you force WM too stay awake for a longer time, it should successfully build the queue on at least more devices.
If you start G-Alarm and it complains about the Windows alarm bug, you've got the default WM settings (15 seconds WakeUpTime). If you press "Yes" G-Alarm changes it to 120 seconds which should be enough.
Here are the registry values G-Alarm changes:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Power\Timeouts\ACResumingSuspendTimeout
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Power\Timeouts\BattResumingSuspendTimeout
Click to expand...
Click to collapse

[Q] nc randomly reboots

Hey guys, my nookcolor has been randomly rebooting since i rooted it. Never while i was using it, i just sometimes hear the bootup sound, and look to find that my book is now on.
Im just concerned this will affect my battery, and i also don't want it rebooting while im using it.
I noticed it doing this one time, but right after i powered it off. In use, it has never rebooted on me (yet)..
This is why we so desperately need a custom ROM. Remove the B&N bloat, and start with a clean 2.2 (or even 2.3 now) base, and really open her up..
Divine_Madcat said:
I noticed it doing this one time, but right after i powered it off. In use, it has never rebooted on me (yet)..
This is why we so desperately need a custom ROM. Remove the B&N bloat, and start with a clean 2.2 (or even 2.3 now) base, and really open her up..
Click to expand...
Click to collapse
I still want to use the B&N stuff. Any rom that emits them, I will not be installing.
I think it likely that there are NC users in both camps-
Those who want the B&N stuff and those who don't.
I am one of those who don't; the Nook for Android software does better for reading ePub, imo and I am rarely near a B&N store.
Right now we have root and Market plus B&N and I would guess (could easily be wrong) that the first custom roms will be pure Android with no B&N.
We will probably end up with an option to set while flashing: retain B&N customizations or straight Android.
I base this guess on what I have seen in the other roms for various devices (mainly Droid) I have looked at.
Same here. If I want to read B&N books, I could still use their Android app on a custom ROM.
After switching to Cyanogen on my phone, it's been quite relaxing to not have to worry about provider updates bricking the thing or otherwise screwing up the rooted customizations (or just randomly resetting the thing back to factory defaults because I started up one of their apps and it got confused). Not to mention that the CM team does a far better job supporting the device than the manufacturer and my service provider does.
And yes, like other Android devices, there will probably be ROMs in both categories: completely built from scratch with no B&N portions at all, and improvements on the B&N system to add more functionality.
Fair enough for those that are interested in the reader portions - i have to admit, i bought this as a tablet, with literally 0% in it as an e-reader; i already have a Sony 505 for that. I may use it on occasion, but only as an afterthought.
However, this topic is really drifting - perhaps we should just bring it back to the rebooting issue?
Yeah, I installed the Uptime Widget on my NC today and picked it up a few ago and its uptime was 1:30; max 15h (from before it rebooted 90 minutes ago). I'll keep running it.
What we need to do is get a logcat when it happens.. So maybe overnight I'll leave it running or something. It just rebooted on me and I was semi-watching it, didn't even notice but Uptime Widget was reset to 7m up, 15:30 max..
I have started up a logcat and I'm going to leave it running while I get ready to go out for the day.. Although I just installed and fiddled with Google Earth, which failed badly, so I wonder if it caused some problem. Also saw it happen after playing with Google Maps, so I wonder about Location stuff maybe doing it.. Dunno. I just launched Maps a few ago and it's been up since. Hopefully a logcat will capture some info.
I have noticed that I've seen some crashes that don't show the Crash dialog.... TweetDeck is particularly bad about crashing viewing some Facebook posts, and in this case it just goes black for half a second then back to the list of posts. A logcat shows it crashed. But I don't know the two are related (not having the crash dialog stuff and the reboots that is).
I had it reboot on me twice last night, one time I didn't know about it until I picked it up later and noticed the uptime widget was down to some 30 minutes, and another time right before bed I hit the power button and about 10s later I saw the boot up text and a reboot happen.
Still haven't caught it on logcat.
My doesn't reboot spontaneously, but it does "lock up" and won't turn on with the power button from standby occasionally. If I remember to use the Nook Button to wake from standby, I don't seem to have this issue. If I use the power button, and it won't wake, I need to hold it down for ~15 seconds and it reboots.
AFIAK, it has done this since I purchased it (I rooted after about 1 hour with the NC in my hands).
Mine has never reboot WHILE I'm using it, it's sneaky about it. But I suppose I'd much prefer it reboot while I'm not using it than while I'm using it; I have yet to have it do a full reboot while using it.
Trying to set up a Delicious account.. yeah, that rebooted the Java VM. But only time I've made it reboot at all.
Hahah, damnit, it just rebooted after it went to sleep. I seriously think it has something to do with going to sleep. I've been sleeping it and waking it repeatedly on adb logcat and it won't crash. Figures.
I had this same issue a while ago. I don't have the logcat from it, but from what I could tell is was some sort of error coming from the system dimming the brightness before turning the screen off. I had Extended Controls installed and was using the widget to adjust my brightness. Whenever the screen would dim before turning off I would get a reboot. I have since uninstalled it and have had no issues with reboots. I'm not sure if this is the issue youre facing but thats my story.
isolated_epidemic said:
I had this same issue a while ago. I don't have the logcat from it, but from what I could tell is was some sort of error coming from the system dimming the brightness before turning the screen off. I had Extended Controls installed and was using the widget to adjust my brightness. Whenever the screen would dim before turning off I would get a reboot. I have since uninstalled it and have had no issues with reboots. I'm not sure if this is the issue youre facing but thats my story.
Click to expand...
Click to collapse
Actually not using any of those on mine.. I have Beautiful Widgets in ADW and Beautiful Widgets + Note Widget in WidgetLocker.. Not adjusting the backlight at all either, in fact I don't think I have at all since getting it now that I think about it.
I have the same issue: rooted Nook Color reboots occasionally and it does seem to do it whenever I put it to sleep or it goes to sleep by itself (when the screen dims). It hasn't rebooted while in use, but it does reboot occasionally when left alone. Have no idea why.
From apps that control dimming I have Advanced Task Killer installed besides the stock app that controls dimming... Could it be the issue? I will uninstall Advanced Task Killer and see if that help.
Otherwise I love my rooted NC. It's fast, beautiful and works great as an E-reader and an Android tablet.
to summarize: Do you think it's the hardware issue or software. I've heard of people who have non-rooted (stock) Nook Color having the same rebooting problem, but apparently it doesn't have to do with rooting. Do you think it will adversely affect the Nook?
If anyone finds a solution please post here. It would be tremendously appreciated.
Thanks and have great holidays.
mastroiani said:
I have the same issue: rooted Nook Color reboots occasionally and it does seem to do it whenever I put it to sleep or it goes to sleep by itself (when the screen dims). It hasn't rebooted while in use, but it does reboot occasionally when left alone. Have no idea why.
From apps that control dimming I have Advanced Task Killer installed besides the stock app that controls dimming... Could it be the issue? I will uninstall Advanced Task Killer and see if that help.
Otherwise I love my rooted NC. It's fast, beautiful and works great as an E-reader and an Android tablet.
to summarize: Do you think it's the hardware issue or software. I've heard of people who have non-rooted (stock) Nook Color having the same rebooting problem, but apparently it doesn't have to do with rooting. Do you think it will adversely affect the Nook?
If anyone finds a solution please post here. It would be tremendously appreciated.
Thanks and have great holidays.
Click to expand...
Click to collapse
I suspect it's a software thing, as it doesn't randomly reboot in use, it ONLY seems to happen going into standby, and I have YET to make it happen connected USB for adb.
You know actually, I think alogcat can log automatically now, maybe I should try that.. but it'd have to run for a day or so, as I only see this happen like twice a day at most.
Do you have setcpu installed? I was getting random reboots when I had it on conservative. Switched to ondemand for all profiles, and no more reboots!
wvcachi said:
Do you have setcpu installed? I was getting random reboots when I had it on conservative. Switched to ondemand for all profiles, and no more reboots!
Click to expand...
Click to collapse
I myself had not played with SetCPU at all. So had you in the past and set it to conservative, and switched it back, or you switched it from its defaults? Reminds me, per my observation that it never has rebooted while on AC or USB, was there a default profile when plugged in that it's set to ondemand vs conservative? This could start making some weird kind of sense. I'll try it, but using something called CPU Tuner since it's free..
EDIT: I looked on USB and on Battery, both times was conservative, so looks like that's the default... Does the Nook have an automatic switching utility like cpuspeed in it? Hmm.. /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor is the file if anyone else wants to look.
BTW, has anyone on 1.0.1 auto-nooted etc not seen these random sneaky ninja power-off reboots? I swear mine waits until I'm not looking and reboots. I've only SEEN it do it once or twice, but in the last 5 or so days it's rebooted at least 10 times while powered off. Again NEVER while I'm using it, so I'm at least thankful for that. If it were rebooting while using it that would not be acceptable.
I have the Uptime Widget, kinda wished I had an uptime graph to see if there is a pattern.. I'm about 99% sure it never happens when plugged in AC or USB.
EDIT2: IT IS CLEARLY MOCKING ME. It just rebooted after I peeked at the governor files and let it idle to sleep.
I have the same random reboot problem since I upgraded to 1.0.1 and used auto-nooter. I only see it when it goes to sleep...or so I thought. This morning I heard it reboot and i hadn't touched it since last night. FYI, it was not plugged in when it happened. Thankfully it never reboots while in use.
Oh...ad i havent used any CPU clocking tools. Also...never saw this on 1.0. So weird but I am sure someone smarter than I will figure it out.
UPDATE- Just got out of the shower and while getting dresses...heard the Book reboot twice within a minute or two.
Wondering if its an app that is causing a fatal crash when it tries to update.
Sent from my Nooxus One using Tapatalk
I haven't had a random reboot in 3.5 hours and i have used the Nook on and off. I did remove my email account from the Google email app (not gmail) and its been good for awhile now. I will update if this changes but I am feeling confident this fixed the random reboot.
Sent from my Nooxus One using Tapatalk
rckymtnrfc said:
I haven't had a random reboot in 3.5 hours and i have used the Nook on and off. I did remove my email account from the Google email app (not gmail) and its been good for awhile now. I will update if this changes but I am feeling confident this fixed the random reboot.
Sent from my Nooxus One using Tapatalk
Click to expand...
Click to collapse
I've had one unexpected reboot today that I know of, I think this has helped, although I keep finding my Wifi turned off, even though this program I installed is only set to turn it off when the battery is extremely low. So I changed that profile and it hasn't turned itself off since, so seems to me maybe the battery reporting is a little wonky sometimes.
I've been watching, and I'll keep an eye out, but I think wvcachi is onto something.
BTW, the Nook has been primarily idle for the last 5 hours, just popped it on a few times to read an email, check on something, or see if it reboots so I haven't used it a bunch but it's lost a whopping 2% battery in that time. I also disabled the Phone stuff too, per this thread:
http://forum.xda-developers.com/showthread.php?t=883908
I am at 6.5 hours now....no rebooting so far.
Sent from my Nooxus One using Tapatalk

[Q] Priority notification mode turning off on its own, even on "Indefinitely"?

[Q] Priority notification mode turning off on its own, even on "Indefinitely"?
The last few nights I've noticed that when I wake up, my phone is no longer in priority notification mode. At night, I set it to priority only and choose "indefinitely"...even verifying that it's on that setting by going back to it...and when I wake up, it's in normal mode.
I have no "Down Time" hours set and see no other settings that seem to imply turning it off automatically...
Anyone else have this issue?
Thanks!
jeffreii said:
The last few nights I've noticed that when I wake up, my phone is no longer in priority notification mode. At night, I set it to priority only and choose "indefinitely"...even verifying that it's on that setting by going back to it...and when I wake up, it's in normal mode.
I have no "Down Time" hours set and see no other settings that seem to imply turning it off automatically...
Anyone else have this issue?
Thanks!
Click to expand...
Click to collapse
Yes I'm having the same issue as you described. Noticed it 2 nights ago and thought I was disabling it in my sleep, lol.
Any work arounds? I'm thinking of doing a factory reset but not until I've exhausted all possible solutions. Hope this is an actual issue and not just 1 or 2 stray scenarios
Yaqoub_H said:
Yes I'm having the same issue as you described. Noticed it 2 nights ago and thought I was disabling it in my sleep, lol.
Any work arounds? I'm thinking of doing a factory reset but not until I've exhausted all possible solutions. Hope this is an actual issue and not just 1 or 2 stray scenarios
Click to expand...
Click to collapse
I never figured it out. Switched back to using Light Flow for notifications...
jeffreii said:
I never figured it out. Switched back to using Light Flow for notifications...
Click to expand...
Click to collapse
Okay last night I uninstalled Light Flow which seemed to have been the problem causing this behavior. It seems to automatically want to disable priority mode but I don't know what exactly is triggering it, but uninstalling Light Flow seemed to have retained priority mode all night long with no issues upon waking up.
I also updated my review on the Play Store to address the issue, hoping for a fix soon. Hopefully you figure out your problem, mine was caused by a notifications app from what I've tested so far. Will see if it holds up tonight as well.
jeffreii said:
The last few nights I've noticed that when I wake up, my phone is no longer in priority notification mode. At night, I set it to priority only and choose "indefinitely"...even verifying that it's on that setting by going back to it...and when I wake up, it's in normal mode.
I have no "Down Time" hours set and see no other settings that seem to imply turning it off automatically...
Anyone else have this issue?
Thanks!
Click to expand...
Click to collapse
Having same issue, no additional notification apps installed. Stock android on nexus 6 no root or anything yet. Thought I was loosing my mind thinking I never set it. Happens almost every night. Seems like a bug.
I'm having the opposite. On boot, priority mode is enabled even though it was off on shutdown. I turn it off then throughout the day I notice it come on again. I haven't been able to track anything down yet. I don't use lightflow.
Are there any logs that I can see that might tell me what is turning it on? There are no Downtime schedules.
Pure 3.95 / Franco r7
Yaqoub_H said:
Okay last night I uninstalled Light Flow which seemed to have been the problem causing this behavior. It seems to automatically want to disable priority mode but I don't know what exactly is triggering it, but uninstalling Light Flow seemed to have retained priority mode all night long with no issues upon waking up.
I also updated my review on the Play Store to address the issue, hoping for a fix soon. Hopefully you figure out your problem, mine was caused by a notifications app from what I've tested so far. Will see if it holds up tonight as well.
Click to expand...
Click to collapse
So I finally got tired of Light Blow being buggy on the Nexus 6 and uninstalled it a few days ago...two nights in a row I set priority to "indefinitely" and when I woke up I found it had been turned off...so I don't think it's Light Flow causing the problem.

Categories

Resources