Help Issues with CyanogenMod

Master_W · Sep 3, 2015

I recently acquired a Nook Tablet and installed CyanogenMod 11 stable on it. I'm not sure if this site supports CM, but the official CM forums are inactive, and my threads have gone unanswered at XDA.

Anyway, everything has been going pretty well on it, except for this very strange issue I'm having...
When the battery reaches about 30%, the screen will start doing things on its own (opening apps, opening the notification bar, etc.) for a few minutes and will then shut off. Right before it turns off, the battery percentage will show 1-3%. If I press the power button, it will begin to boot up but will shut down again before its done.

It works fine when the battery is charged up, this only happens when it gets to 30% or so... I know some people might just say to reflash it, but I don't want to have to go through all that again if not necessary.

Update: I pressed the power button to try it again, then when I looked back over to it it was doing a factory reset, it then proceeded to shut off in the middle of it, and now when I press the power button it just shows the Nook logo for a second then shuts off...

It's midnight and I'm typing this on my phone, I'm new to all this Android stuff and it's about to make me pull my hair out...

Any help would be appreciated.

mikedt · Sep 3, 2015

Gives trouble, goes unstable and shuts down when battery is <30%. Did you aquire new or second hand, if it's an older device, could be a sign the battery is worn out and needs replacing.

Master_W · Sep 3, 2015

mikedt said:
Only gives trouble when battery is <30%. Did you aquire new or second hand, if it's an older device, could be a sign the battery is worn out and needs replacing.

It was second hand, but these problems weren't occurring with the stock Barnes and Noble software.

mikedt · Sep 3, 2015

Don't really know then. I've used CM on a few devices myself, never had problems like that. This forum covers CM and other ROMs running on a few devices. If the CM forums for Nook are deserted, it sounds like interest in CM on this device might have passed, they might no longer be interested in supporting the Nook.

Master_W · Sep 3, 2015

Plugged it up to the charger and it went on with the restore. The B&N startup animation loaded, then it turned off and now the screen won't turn on no matter what I do. I've tried holding down the button(s) for 30 seconds, reconnect disconnect charger, etc.

I'm afraid it's bricked :/

Master_W · Sep 3, 2015

mikedt said:
Don't really know then. I've used CM on a few devices myself, never had problems like that. This forum covers CM and other ROMs running on a few devices. If the CM forums for Nook are deserted, it sounds like interest in CM on this device might have passed, they might no longer be interested in supporting the Nook.

I believe they still support it, they released CM 12 stables for it just yesterday.
Thanks for the replies. Maybe someone else will chime in, all this is really frustrating me...

Master_W · Sep 3, 2015

Well I left it plugged in for awhile and when I came back it was booted into the stock OS. It's running now, but does that mean all the CM/CWM stuff has been wiped? Or do I need to wipe and reflash with CWM? I just don't want any leftover files on it before I give CM another try.

Anyone?

Master_W · Sep 4, 2015

After reflashing, this issue is somewhat better. It doesn't start to die until it gets down near 5%, but it will still start doing things on its own before turning itself off.

Anyone? Anyone at all?

Hadron · Sep 4, 2015

Never heard of this before. But even weirder to me is that it sounds like it spontaneously reverted to the stock software, which should be impossible since a custom ROM overwrites the factory ROM completely. Factory resets are irrelevant to this, since all they do is wipe user data and don't touch the ROM at all.

So either there's something very different about this device, or you installed CM in an unusual way (one of these multi-ROM setups? I've never used them, but it's the only way I can imagine what I think you are saying happening). Can you tell us exactly how you installed the ROM? If there's something odd in your setup it might be that other odd behaviour is somehow related.

Master_W · Sep 4, 2015

Hadron said:
Never heard of this before. But even weirder to me is that it sounds like it spontaneously reverted to the stock software, which should be impossible since a custom ROM overwrites the factory ROM completely. Factory resets are irrelevant to this, since all they do is wipe user data and don't touch the ROM at all.

So either there's something very different about this device, or you installed CM in an unusual way (one of these multi-ROM setups? I've never used them, but it's the only way I can imagine what I think you are saying happening). Can you tell us exactly how you installed the ROM? If there's something odd in your setup it might be that other odd behaviour is somehow related.

I mostly followed the CM Wiki instructions for "acclaim", which is the Nook Tablet code name. I created a bootable SD of CWM 6 with Gparted on Ubuntu, and copied the latest stable CM 11 .zip to it. Booted up, wiped data, cache, and dalvik, installed the .zip from the SD card and rebooted. I went back into CWM, wiped cache and dalvik, and flashed GApps.

As to it restoring to the stock software, I think that because I didn't flash CWM directly to the device, the stock recovery partition remained in tact. I also found out that if the boot is interrupted more than 8 times on the Nook Tablet, it will automatically restore.

Hadron · Sep 4, 2015

I'm going to have to look into this when I have time. The procedure sounds like it should permanently install CM - you flashed the ROM, and that should be that. I've never met a device that can revert to stock because that requires keeping a separate copy of the stock ROM that can be used to reflash back to stock, and I've never met a manufacturer who wastes a gig or two of storage doing that.

I agree that it's hard to imagine this happening if you'd replaced the stock recovery. But even so it's pretty unique behaviour!

Unfortunately if the device really has that feature then this doesn't provide any clue as to why it misbehaves when the battery level falls low under CM.

Master_W · Sep 4, 2015

Hadron said:
I'm going to have to look into this when I have time. The procedure sounds like it should permanently install CM - you flashed the ROM, and that should be that. I've never met a device that can revert to stock because that requires keeping a separate copy of the stock ROM that can be used to reflash back to stock, and I've never met a manufacturer who wastes a gig or two of storage doing that.

I agree that it's hard to imagine this happening if you'd replaced the stock recovery. But even so it's pretty unique behaviour!

Unfortunately if the device really has that feature then this doesn't provide any clue as to why it misbehaves when the battery level falls low under CM.

Well I guess for now I'll just have to turn it off before it gets that low. Thanks for looking into it.

Master_W · Sep 5, 2015

I flashed CM 12 and this issue appears to be gone. I really liked CM 11 better, oh well.

Master_W · Sep 8, 2015

I couldn't stand CM 12, so I decided to give CM 11 another try. I restored to stock, then flashed CM 11 again without GApps or anything else. The low battery issue STILL occurs on a clean CM 11 install.
This is maddening... Surely someone else has had this same problem? It's not a hardware issue, because this never happens on the stock NT software or even CM 12.
Anyone?

Help Issues with CyanogenMod

Newbie

你好

Newbie

你好

Newbie

Newbie

Newbie

Newbie

Spacecorp test pilot

Newbie

Spacecorp test pilot

Newbie

Newbie

Newbie

BEST TECH IN 2023

Smartphones

Best Android Phones

Upcoming

Best iPhones

Upcoming

Tablets

Best Tablets

Upcoming

Laptops

Best Laptops

Upcoming

Televisions

Best TVs

Upcoming

Game Consoles

Best Game Consoles

Upcoming

Wearables

Best Wearables

Upcoming

Smart Home

Smart Home Tech

Upcoming

Similar threads