[Nook Touch Android Development] nmyshkin:
First, I checked the NookManager_Classic package (which it appears you used) to be sure I didn't leave out any apps or jars to disable the B&N system. That part is correct.

Second, phone.apk has nothing to do with your situation. That crazy "cell standby" artifact has caused more trouble than a basket of deplorables. I did a study of phone.apk here: https://xdaforums.com/t/battery-usage-and-phone-apk.3341370/ some time ago when it was discovered that it was needed to access the Android Media volume control for those using USB Audio. The short version is that the numbers you see as consuming battery on "cell standby" are meaningless.

Third, you have discovered one of the reasons I dislike Relaunch (X or otherwise). You can see phone.apk, but you can't touch it. You can't touch anything in the root directory with Relaunch. In this particular case it does not matter since that is not where the problem is.

Unfortunately I have no idea where the problem might be. It's typical for my devices to drop about 1% per day with "light" reading use (and WiFi off), and I have a

lot

of stuff going on. So if you're seeing a higher battery drain than that, there is clearly some issue.

My first suggestion would be to restore a registered backup of the functioning 1.2.2 B&N system (if you have one) and follow the battery drain for a few days (you can check the battery % in the Settings app). If you've still got an inordinate drain, it may be that your battery is simply getting old and is not holding a charge as long as it should. I've never seen this with my three devices, which surely must be quite old, but all batteries are different. So that's number one.

Number two, you could check the sequestered apks and jars to be sure there was not some kind of hiccup during the moving process. You should be able to see the files with Relaunch, just not interact with them. The directories and files you are looking for are:

/system/disabled-app

Accessories.apk

AccountAndSyncSettings.apk

AFfileDownloadService.apk

AirRuntime.apk

BnAuthenticationService.apk

BnCloudRequestSvc.apk

CloudService.apk

CryptoServer.apk

DemoMode.apk

DeviceManager.apk

DeviceRegistrator.apk

DownloadAdmin.apk

DownloadProvider.apk

DrmProvider.apk

GlobalSearch.apk

GoogleSearch.apk

Home.apk

Launcher.apk

Library.apk

MediaProvider.apk

NookCommunity.apk

NookHWTest.apk

Oobe.apk

QuickStartActivity.apk

Reader.apk

ReaderRMSDK.apk

ServiceOne.apk

Shop.apk

Social.apk

SysChecksum.apk

TelephonyProvider.apk

ThumbnailService.apk

WaveformDownloader.apk

/system/framework/disabled-jars

bncloudapi.jar

com.bn.app.crypto.jar

com.bn.app.deviceinfo.jar

com.bn.authentication.jar

com.bn.cloud.jar

com.bn.gpb.jar

com.bn.provider.utils.jar

com.bn.waveformdownloader.jar

Actually, I guess you should take a look at these first since that doesn't require restoring a backup, etc.

My NST with glowlight runs quite happily this way, with good battery life, so the concept is fine. Something has happened in the execution.

If none of this helps, the best thing to do is restore a registered 1.2.2 backup (which I hope you have) and try the rooting process again. That might sort out the unknowables.