Database Develop

Rooted NC is possessed, need exorcism.

Looking to find anyone with the same issues I am having. My NC is rooted using Auto-nooter for 101. Everything went smoothly no issues at all. A day later my NC has been possessed. When reading a book NC would start to skip pages sometimes as much and 5 pages in fast progression, I would then have to swipe back to my page. Then there are times when the quick nave bar of the NC would start flashing multiple times then click a random book from the home screen or from the daily shelf and open it, when I close it it would do it again this would happen about 3 or 4 times till the screen freezes for about 7 minutes. But its not over, then the NC would automatically go into settings then back to home screen then back to settings again really fast, then again freeze. The only way (and this does work) is to "light boot" it by holding down the power button for 5 seconds (the option to shut down will pop up) then let go then press the power button once quickly on then off. The home screen will come back and the "possession" will have stopped, for awhile. This is getting really annoying, especially the reader skipping multiple pages forward on its own as I do like reading with my NC. So has anyone else have this happening? Any ideas as to what this could be? Thanks for any help or ideas. I have read the forums but it seems I am the only "lucky" one to have this issue. Again thanks.

yes, this happened to me. I went and bought a screen cover and cloth. Cleaned the screen VERY thoroughly and applied to cover. Has not happened since.

Phyllip J FRy said:
yes, this happened to me. I went and bought a screen cover and cloth. Cleaned the screen VERY thoroughly and applied to cover. Has not happened since.
Click to expand...
Click to collapse
Do you mean like an anti glare/non scratch screen protector? I have a great gadget cloth that I use all the time.

brie987 said:
Looking to find anyone with the same issues I am having. My NC is rooted using Auto-nooter for 101. Everything went smoothly no issues at all. A day later my NC has been possessed. When reading a book NC would start to skip pages sometimes as much and 5 pages in fast progression, I would then have to swipe back to my page. Then there are times when the quick nave bar of the NC would start flashing multiple times then click a random book from the home screen or from the daily shelf and open it, when I close it it would do it again this would happen about 3 or 4 times till the screen freezes for about 7 minutes. But its not over, then the NC would automatically go into settings then back to home screen then back to settings again really fast, then again freeze. The only way (and this does work) is to "light boot" it by holding down the power button for 5 seconds (the option to shut down will pop up) then let go then press the power button once quickly on then off. The home screen will come back and the "possession" will have stopped, for awhile. This is getting really annoying, especially the reader skipping multiple pages forward on its own as I do like reading with my NC. So has anyone else have this happening? Any ideas as to what this could be? Thanks for any help or ideas. I have read the forums but it seems I am the only "lucky" one to have this issue. Again thanks.
Click to expand...
Click to collapse
No, you're by far not the only one, seems to be related to bad chargers, bad cables, or bad luck... I've had it happen one time while plugged in, but some people have said they couldn't use their NC at all while plugged in.
There are several threads here already on this subject...

I had some eratic stuff going on...buttons clicking, menus popping up, etc. Cleared up after i cleaned the screen really well and stopped breating so heavily (have a cold and coughing & breath was making the screen moist).

something similar happened to me early on... My K key kept pressing itself, and random key strokes while trying to enter a password... here I think.
Is your screen dirty? I happened to be using mine with sweaty hands right then, lots of finger cheese on the screen was causing false contacts. cleaned it and was good to go.

I have had the "dirty screen" issues as well. But there was one time about a week ago when this was happening even after I cleaned the screen. I completely powered off and rebooted and all has been well since. . .

Thanks for the replies I never thought that my greasy marks would make false positive clicks on my screen. come to think of it it does happen when I am reading for a bit before it starts and eating chips while reading just conjures up those spirits, thanks.
EDIT: Alright I am now convinced that this issue is technical. Its happening again now and my screen is clean and I just reboot it. NC was just sitting and charging I started it to read and it just started jumping to settings again and the Nav bar keeps flashing on and off. This time I just let it go and it went on for 5 min even after the screen turned off. I did the old "soft boot" (check first post) and it stoped. HHHHHHHHMMMMMMMMMM. I think I have a conflict with an app. I did the "save battery by changing the phone.apk and telephony.apk, has anyone also changed this and have this problem?

I had the problem before I did the cell standby battery thing.
In another thread people were solving it by recalibrating the screen. I tried it and it worked for a while before they phantom presses started again, though I might have done it wrong to begin with.
*can't post the link but its in the nookdev wiki.

Sunrisemix said:
I had the problem before I did the cell standby battery thing.
In another thread people were solving it by recalibrating the screen. I tried it and it worked for a while before they phantom presses started again, though I might have done it wrong to begin with.
*can't post the link but its in the nookdev wiki.
Click to expand...
Click to collapse
Thank you so much for this, I did not even know of this site, happy I do now. To anyone that needs this the link is here. Again thanks.
http://nookdevs.com/Recalibrate_the_NookColor_touch_screen

Happened to me when i first got my NC while charging it. Has not happened since.

brie987 said:
Looking to find anyone with the same issues I am having. My NC is rooted using Auto-nooter for 101. Everything went smoothly no issues at all. A day later my NC has been possessed. When reading a book NC would start to skip pages sometimes as much and 5 pages in fast progression, I would then have to swipe back to my page. Then there are times when the quick nave bar of the NC would start flashing multiple times then click a random book from the home screen or from the daily shelf and open it, when I close it it would do it again this would happen about 3 or 4 times till the screen freezes for about 7 minutes. But its not over, then the NC would automatically go into settings then back to home screen then back to settings again really fast, then again freeze. The only way (and this does work) is to "light boot" it by holding down the power button for 5 seconds (the option to shut down will pop up) then let go then press the power button once quickly on then off. The home screen will come back and the "possession" will have stopped, for awhile. This is getting really annoying, especially the reader skipping multiple pages forward on its own as I do like reading with my NC. So has anyone else have this happening? Any ideas as to what this could be? Thanks for any help or ideas. I have read the forums but it seems I am the only "lucky" one to have this issue. Again thanks.
Click to expand...
Click to collapse
I had it happen one time recently while the NC was charging. I was attempting to type a FB reply and the keyboard went all wacky. For every character I hit it entered 3-4 random characters. I switched to Gmail and it did the same thing. I unplugged the NC to plug into the computer to calibrate the screen and immediately after unplugging (before calibrating) it worked perfectly. No problems since.

My God! I thought I was the only one this was happening to. It drives me CRAZY. It happens all the time.
I have hands that sweat almost nonstop, and I think they're what causes this for me. Funny thing is, I never noticed it till I rooted. Does AutoNooter install a custom kernel? That may explain it. Also, it mostly seems to happen when plugged in, which makes me think it may be an issue like on the Evo in it's early days where the screen isn't properly grounded. It was fixed by a sensitivity tweak in a software update, and that should be possible here, I'll look into it.
Someone said a screen protector helps, and I just ordered one to try it. They've helped on past devices, and may here too.

While I have not personally had these problems on either of the NCs in the family it seems pretty conclusive that two things contribute to the problem ... a) 'dirty screen' .. getting a screen protector helps ... b) using while charging .. the #1 'quality' problem reported in the forums seems to be the port/plug on the NC and circumstantial evidence points to the cable .. I don't use the NC while it's charging so don't see the behavior and do use it connected to the PC rarely and do not use the B&N cable to connect so those with the problem may want to try another cable/charger. One of my cables works fine, the other is problematic.

Nook will turn on by it self after 5 minutes or so

First I thought that I'm crazy but now I can confirm that my NC will boot on it's own after about 5 minutes after power OFF. I have to shut down 2nd time and than it will stay OFF. Any idea what's wrong ?
Thanks
(Yes I did confirm after first shut down that it's actually OFF since no buttons will respond)

Any weather Apps running? Many of them have an option to wakeup in order to update. Check your mail, twitter and facebook apps. It has to be something you installed, I have run every update, tried all the froyo images and both Honeycomb releases and I have not seen that.

To expand on what gedster wrote, it seems kind of crazy and out there but what about any devices on your network that might send Wake on Lan requests? What if something on your network had located your NOOKcolor. I don't even know why a eReader Tablet would have a function for Wake on Lan but it's just another crazy avenue to jog down.

I do have weather app installed but I find it hard to believe that it can wake up OS that is not in standby but completely off. WIFI is also not enabled before shutdown.

Looks like the problem is there only if I used market, if market is not used it will shut down fine and it will not boot on its own.

lifeisfun said:
Looks like the problem is there only if I used market, if market is not used it will shut down fine and it will not boot on its own.
Click to expand...
Click to collapse
Seems that's unlikely if you're the only one having the issue, I'd keep digging if I were you.

Looks like you're right I can't replicate the problem every time
The timing when it will boot also varies 5, 15 and even 35 minutes.
Don't know what to do, it's hard to imagine how it can boot on it's own from
complete power off state

I can't believe I'm the only one with this problem

lifeisfun said:
I can't believe I'm the only one with this problem
Click to expand...
Click to collapse
I just posted a thread about this issue for me less than an hour ago! Funny, no one replied to mine: http://forum.xda-developers.com/showthread.php?t=940713. It was pretty long...guess I should've added a TL;DR.
It happens to me on any (or no) power source. Timing varies like yours as well. I'm going to pull my weather app based on the above recommendation, and I will try your Market theory out. Knowing someone else has this issue makes me hopeful that we can find something that we have in common as the culprit.
I did download the newest Honeycomb image yesterday and I'm going to put that SD card in and see if I can get it to turn itself back on on a Market-less, user App-less build. If successful I'll Titanium my 1.1 apps and remove everything non-system, then slowly add until I get this figured out. Keep me posted if you figure something out, I'll be sure to do the same!
In case it matters I bought mine about a week ago and the serial number starts with 20046.
EDIT: Testing with Honeycomb SD now so if that's the case here it should just stay off. I booted into Honeycomb at 9CST and turned it off at 9:01. I'll give it a couple of hours.

I used to have this same problem. I would randomly find my 1.0.1 auto-nootered 950mhz rom nook on, when I knew I had turned it off. interesting part is, this problem completely solved itself after I flashed my emmc with the custom nookie 5.9 img. so it must be an eclair issue and not a hardware issue

woot1524 said:
I used to have this same problem. I would randomly find my 1.0.1 auto-nootered 950mhz rom nook on, when I knew I had turned it off. interesting part is, this problem completely solved itself after I flashed my emmc with the custom nookie 5.9 img. so it must be an eclair issue and not a hardware issue
Click to expand...
Click to collapse
Really? I've been putting that off because I don't like the idea of not having Clockwork Recovery. I understand there are ways to do the same things using IOMonster's things but I'd really rather just have Clockwork Recovery working. Unless there's a way to get it going that I missed?

Yup, I've been having this issue as well. I really want to flash NF but I want hardware video acceleration.

oscillot said:
Really? I've been putting that off because I don't like the idea of not having Clockwork Recovery. I understand there are ways to do the same things using IOMonster's things but I'd really rather just have Clockwork Recovery working. Unless there's a way to get it going that I missed?
Click to expand...
Click to collapse
you are correct that clockwork does not work with froyo. however the bootable sd card that you would burn automatically starts up clockwork first. you can run a backup and restore, as far as i know, without having to reflash froyo. on a personal note, froyo still has some issues but overall I'm exteremly pleased so far. i really just wanted to get rid of all of the b&n stuff (mainly the status bar) along with any possible way of them pushing an update to break root. I would recommend it, but CM 7 with gingerbread will probably be out sooner rather than later.

woot1524 said:
you are correct that clockwork does not work with froyo. however the bootable sd card that you would burn automatically starts up clockwork first. you can run a backup and restore, as far as i know, without having to reflash froyo. on a personal note, froyo still has some issues but overall I'm exteremly pleased so far. i really just wanted to get rid of all of the b&n stuff (mainly the status bar) along with any possible way of them pushing an update to break root. I would recommend it, but CM 7 with gingerbread will probably be out sooner rather than later.
Click to expand...
Click to collapse
Which I guess brings us back to, why is Eclair doing this, and why does it seem to be limited to lifeisfun and myself?

I'm glad I'm no longer special
My serial # is 200503 .....
Removing all application that I have installed didn't help.
Only 100% way to shut down is to let it boot and immediately shut down.

unknown.soul said:
Yup, I've been having this issue as well. I really want to flash NF but I want hardware video acceleration.
Click to expand...
Click to collapse
Now that I understand the power of this things SD slot and that CWR can be run off of an SD, I can totally live with that. Hardware Video isn't a must for me yet, so I may take the plunge tonight after work...BTW, what are people's favorite video apps? I have been playing with VLC stream and convert, which works somewhat with my media server's samba shares. I have the share mounted to a directory on the sdcard since many apps look there exclusively.
More on topic, I couldn't get SD Honeycomb to start itself on its own. I tried booting then shutting down. 2 hrs of nothing 15mins light activity then shutting down. 2 more hours of nothing. About an hour of heavy use, seeing what could be installed, sideloading, testing, editing things like build.prop and rebooting often and trying to get swype working (don't think it's supposed to, but that's "heavy use" for me.) Powered down. Went to bed. Still not on this morning. This looks indeed to be an issue with the B&N stock Eclair.

Mine doesn't turn itself on with no interaction at all, but will turn on every time when you plug in the charger or cable hooked to USB port in computer.
I can turn it off once it is already plugged in and it will stay off, but remove and replug the charger and it is on again.
Strange.

Well, strange that only two or three of us noticed this strange problem.

Yeah, started for me after 1.1 update. Turned it off last night, tonight it was on with 40% battery! I think its 1.1 related, this didn't happen with 1.0.1 ...

I'm sure there's a condition that's causing or exasperating this issue, something common to us all. But at this point since I don't use the Nook as a video player (I actually bought it to read books, but I use Aldiko and the open epub format) I will likely flash Nookie to the eMMC and call it a day. Honestly can't wait to get a clean notification bar on this thing anyway.

[Q/Problem] Seems to happen with Every Rom.

I would like to keep this short and sweet so...
Basically heres the low down: I got a G1 almost a year ago, got into Rooting/flashing 7 months ago. I noticed in the beginning almost every rom was giving me a problem, Freezing up, hanging for long periods of time, etc. I eventually found a very nice, stable rom thats been lasting me for about 6 months but as of late was being horrible. Force Closing everytime I got a text message, REALLY Hanging for long periods of time, freezing up. Etc.
So I finally got FED UP, and decide it was time for a change, so I grabbed MLIGN 3.3v having seen so many good reviews and what not, thinking it would be the remedy to my poison. I cried. So in short, here is whats going on:
1. It seems to only wanna cooperate when Plugged into the USB, which, isn't too practical.
2. When not plugged in, it is NOT sluggish, but when loading into apps I've noticed it will hang for quiet awhile or completely lock up to the point only popping out the battery will work.
3. I haven't noticed it yet, but on the old ROM it would randomly shut off during phone calls; which leads me too....
4. When ever I shut the screen off (by pushing endcall) it seems to freeze and lock up and eventually either SHUTOFF or REBOOT into a SHUTOFF of the phone and refuse to turn back on until it has been plugged into the USB, or enough time has passed for it to 'forgive me' and by that, I mean randomly work again.
5: Various other things I cant think of right now.
So, basically thats almost everything. Whenever its plugged into USB though, it works like a charm (for the most part).
Would a problem with my Battery be the case? Which, would be awkward but a possibility.
Or did I just do something wrong?
I made sure to factory wipe the phone twice, even 3 times on the last go, I updated the ENG.SPL and Radio every time I tried to reflash just to make sure.
I partitioned my SD Card for 32MB Swap; 512EXT2 (and 7xxEXT2 I forget what it was) and I also upgraded it to EXT3, which showed some improvement... I believe.
So, I just would like to have my phone working, in a peaceful, obedient manner xD.
Forgive me for the block of text, and all help will be appreciated. Thank you guys... I await sound advice

Try different ROM? See which one works best.
Like me, I found that SuperAosp is best suit for me (see my sig for DEV Site and Download, if you want to try it). It had been running fast and I had no issue, what so ever. Occasionally when I loaded apps that hogged the power usage it gets lags, but still good. FCs are at minimal to none (that's just because of the way I handle the apps). Once in a while I noticed that it reboot, when I tried to use the apps that hogged the memory (maybe that was the apps issue).
Only other thing I recommed is to download a different launcher, because the build-in ADW Launcher does not work too well in my opinion.
Another thing, if you wish to keep the ROM you had. I would suggest to change the partition size. (IE: Catch [128MB]/Ext 2 or EXT 3 [1024MB]/ FAT32[the rest]) Now I know other people might say that it's overkill, but to me my G1 performance it great.

I've tried multiple roms as of late, and the one I like the most does happen to be MLIGNs... everything seems to be working correctly for the most part with the exception of what I listed above... Now on the like, 23rd reboot most of the sluggishness that was there before is gone, and everything is pretty much being cooperative, with the exception of like the weather, which isn't updating properly but I can live with that. What I cant live with is the fact that this ROM when not plugged in, will freeze up when in the lock screen, a few minutes after it has darkened and gone black and wont respond at all. Or I'll unplug it and just do a test, swipe left, right for a good minute or two, go into apps and It'll just SHUT OFF. Maybe it really is the battery? I'm unsure. When I look at the battery it does look quiet bloated... I am unsure...
I'm gonna try to set it to what you recommended, and see if that works...

I don't think it's the battery.
Have you tried reformat/partion your SD card (be sure to backup your data first). See my last comment on sizes recommendation for each partition.
Also check on the swappiness setting.

Mhm... so I went back and followed everything you told me to do, including repartitioning to the exact file sizes you told me. (Also I'm guessing Cache meant Swap) So I set everything up and its really blazing fast and stable.... until I remove the USB cord. Then it shuts off, freezes at lock screen when the screen is dimmed to black, and will just randomly shut off while doing things (especially when trying to get into messages)
Also if it helps, I have a Class 2 8Gig SD card, and my Recovery is Ra 1.5.x(I forget.) I'm completely confused... I dunno what to do... I would really like this to just work and stop being a hassle D:

Hmmm, Try reading this thread, http://forum.xda-developers.com/showthread.php?t=1010932
See if it helps.

Nothing :/ Its okay... I'm gonna go play around with other roms, completely re do my phone, make sure everything is updated etc. Then go from there.
Thank you anyways, you were a big help, reguardless of my phones triumphing retardism

everything is Force Closing since yesterday

hey guys, I don't know what's going on with my S7 but yesterday was working fine and out of nowhere everything started to FC! From twitter to "Google Services Framwork", Gmail, browser, tweetdeck, calendar, voice, I can't pretty much use it anymore, I haven't done any new app installations so i don't know what's wrong! is it just me, or anyone else having this problem??
Any help will be much appreciated!
Thanks

That has happened to me 4 or 5 times. It's like half of the device gets erased but the apps are there. Everything force closes. I end up having to erase the device and re-install everything. Reboot into recovery if you can't figure it out and format the system and data. For some reason when i do that, i keep root. Not entirely sure how that happens, but one less step for me. I think root is power and one of the volume buttons.

djdanska said:
That has happened to me 4 or 5 times. It's like half of the device gets erased but the apps are there. Everything force closes. I end up having to erase the device and re-install everything. Reboot into recovery if you can't figure it out and format the system and data. For some reason when i do that, i keep root. Not entirely sure how that happens, but one less step for me. I think root is power and one of the volume buttons.
Click to expand...
Click to collapse
ha! i remember I already did that. After the Update we had, and I exchanged mine for a new one I decided to stay with no root (i don't know why! lol) so I guess I'll reset everything and go back to root I figured at the end I was gonna do that, but I was trying to see if it was just me or there was a fix
thanks man!

ok, so since yesterday I've been trying to factory reset the DS, and when it boots back on, everything stays the same!
I'm a little confused now, if I take a picture and I turn the tablet off, when I turn it back on, the picture disappears. Same thing happens if I move widgets, delete or create new ones on the screen, they go back to as the configuration was on friday night! GV not working, and the last message that shows there, same thing, shows the last one on friday. I don't know what can I do.... should I call dell??

duck tape and dynomite
stupid thing started crashing yesterday FC this and FC that ....cant restore it as i no longer have write access to the internal sd card
1) tried nv flash
2) tried restoring from clockwork
3) tried pushing files through adb
4) tried fastboot ....
if i didnt just dump money into this thing id blow it up ......
any help would be appreciated.......any tips to fix it or kill it completely so i can get another one
actually deleted all of the files on internal sd card and uninstalled every program on the device looked completly stock ....rebooted it and it went back to how it was yesterday ......theres gotta be a reason why other are having the same problem that started on the same day .....maybe dell pushed an OTA update and screwed us ......just a thought cause mine was fine till i went 4g yesterday so my sis could post facebook pics ....not sure but hope we can figure this out

Samething happened to me
Hi, did you ever find a solution? my streak 7 was ran out of battery, before it shut off, the screen started flickering and then it turned off. after it came back on, it looked like it was fine, everything looked normal, but then everything started force closing, haven't found a solution

jz83 said:
Hi, did you ever find a solution? my streak 7 was ran out of battery, before it shut off, the screen started flickering and then it turned off. after it came back on, it looked like it was fine, everything looked normal, but then everything started force closing, haven't found a solution
Click to expand...
Click to collapse
I'm running stock, and I discovered the hard way that you can't let the S7 battery run all the way down. The S7 will not power itself down in time. I had the same issue, and the only way around it was to do a complete factory reset, using the menu button from the main screen. I think the reset is in the "About" section, but I don't have my S7 with me now.
Being used to WM6, which powers the device down at 5%, I was not expecting the device to do this, but there it is.

dell streak 7
im not sure if I am the only one with this issue you but becareful with the streak 7 mine well both of mine wont charge properly and the newest one wont charge at all. i have to send it back to dell for them to fix it. Im not sure what cause this but my only advie is to never use a different charger for it only dell chargers. Im guessing that it messes up the battery callibration and then it gets really hot when charging

Sliding won't work anymore

Hey guys,
I could need a bit of help! It's now the third time I'm having this problem, don't ask me why. I've got the feeling that I read the whole forum here, but didn't find anything similiar.
The 1st time I didn't change anything (ok, rooted it, but nothing else)
The 2nd time I overclocked it slightly (~850-900 MHz)
Now I'm using MIUI.
But back to the problem:
I'm unable to use the keyboard, every time I'm sliding open the keyboard (even when it's turned off), it "crashes". The screen stops working or it freezes, the only way to turn it off is taking out the battery.
However, the bigger problem comes now: I'm barely able to restart it. It tries booting, but is restarting all the time or the screen is just turning on (in some angles you see that it is turned on but it's black). After many retries, it starts working, sometimes the bootloop is running 15min or i have to manually restart it 10 times or more. The strange thing is that the keyboard works fine, nevertheless I have to choose between using it opened (taking it with me becomes difficult ) or closed...
...the main problem now is flashing a new Rom, I'm currently trying it through the android sdk and adb, but using the power-button + x is easier
I don't think that I can solve the problem, I sent the device two times back (warranty till may 2012), but maybe someone here knows a bit more. My guess is that one of the sensors is broken, or some parts of the display that should manage the sliding process...
Anyway, thanks for your attention!
Web

If you already have Rom Manager, just click Reboot into Recovery..

inches0 said:
If you already have Rom Manager, just click Reboot into Recovery..
Click to expand...
Click to collapse
Tried to use one a time ago, but it wasn't working right....
However, now I'm not even able to boot it, the screen just flashes and turns off itself before trying to restart a few moments later....guess I lost my Milestone

Sbf back to stock?

taptaptouch said:
Sbf back to stock?
Click to expand...
Click to collapse
the computer isn't finding it anymore...I'll back up the data and try use my warranty... I hope that they don't complain about MIUI...
But I'm still not getting the point, why my mobile had these issues three times, although they "repaired" it twice...and nobody else is having the same problem