Related
Hi all.
i've a rooted nook touch with an old version of TouchNooter .
Now, google updated the marketplace (now play store) and since that time i can't install anything else on the device. Said so, i would like to upgrade the touchnootler version to a new one (hoping that it has the play store).
what should i do? do everything from scratch or is there another procedure?
Is there any "better" rooting?
PS: don't know if it's a rooting problem, but in the library, for the last book i was reading ("last reading" or smt like that), i've the screen saying 1 of 1 (pages) and when i open it it starts from the begining instead of the page where i left the book.
ciao.
esseti said:
Hi all.
i've a rooted nook touch with an old version of TouchNooter .
Now, google updated the marketplace (now play store) and since that time i can't install anything else on the device. Said so, i would like to upgrade the touchnootler version to a new one (hoping that it has the play store).
what should i do? do everything from scratch or is there another procedure?
Is there any "better" rooting?
PS: don't know if it's a rooting problem, but in the library, for the last book i was reading ("last reading" or smt like that), i've the screen saying 1 of 1 (pages) and when i open it it starts from the begining instead of the page where i left the book.
ciao.
Click to expand...
Click to collapse
anyone that can help?
When you say you can't install anything else, what do you mean specifically? Inability to search in Market is a known issue. If you mean you can't search, you need to install SearchMarket to search for things. The NST runs an old (2.1 Eclair) version of Android, which is NOT compatible with the new Play Store, so we're stuck with the old Market. Everything works, but searching.
Use the latest version of TouchNooter for your device. It won't be able to fix the searching problem.
bobstro said:
When you say you can't install anything else, what do you mean specifically? Inability to search in Market is a known issue. If you mean you can't search, you need to install [*URL="https://play.google.com/store/apps/details?id=youten.redo.searchmarket&feature=search_result#?t=W251bGwsMSwxLDEsInlvdXRlbi5yZWRvLnNlYXJjaG1hcmtldCJd"]SearchMarket[/URL] to search for things. The NST runs an old (2.1 Eclair) version of Android, which is NOT compatible with the new Play Store, so we're stuck with the old Market. Everything works, but searching.
Use the latest version of TouchNooter for your device. It won't be able to fix the searching problem.
Click to expand...
Click to collapse
if i click on the market icon nothing happens. even going to the play store and install it via pc does not work. i cannot install anything. ideas?
I believe you can download the latest TouchNooter and run it with no harm. Read through the TouchNooter thread to be sure.
Market should launch, even if you can't search. Installing via the web page should work. Sounds like something is broken on the system.
As far as the page numbering -- that's a known B&N bug. I quit using B&N's reader or library.
bobstro said:
I believe you can download the latest TouchNooter and run it with no harm. Read through the TouchNooter thread to be sure.
Market should launch, even if you can't search. Installing via the web page should work. Sounds like something is broken on the system.
As far as the page numbering -- that's a known B&N bug. I quit using B&N's reader or library.
Click to expand...
Click to collapse
well, upgrading to last touchnootler i'll have to do all the procedure back again (if i follow the one one the first page that i assume to be the correct one).
since it's basically like doing everything from scratch, is this the actual best mod for the touch? or is there anything better?
What do you use instead of the B&N library?
"Better" is a subjective term. TouchNooter installs the basic tools you're likely to want (Market, NOOK Touch Tools, etc.) MinimalTouch lets you have complete control over the process, but requires more work on your part.
I have used TN a half-dozen times with no problems if I follow the instructions carefully, so it's my preferred method of rooting. That doesn't mean it's the "better" approach. I do modify TN to add a file manager that works before I root with it. SuperManager that Gabrial includes has never worked for me, and I don't like waiting 24 hours to install software via the Market.
I use Mantano Reader Premium to replace the B&N Library and Reader completely. I never see the B&N Home screen, Reader or Launcher.
bobstro said:
"Better" is a subjective term. TouchNooter installs the basic tools you're likely to want (Market, NOOK Touch Tools, etc.) MinimalTouch lets you have complete control over the process, but requires more work on your part.
I have used TN a half-dozen times with no problems if I follow the instructions carefully, so it's my preferred method of rooting. That doesn't mean it's the "better" approach. I do modify TN to add a file manager that works before I root with it. SuperManager that Gabrial includes has never worked for me, and I don't like waiting 24 hours to install software via the Market.
I use Mantano Reader Premium to replace the B&N Library and Reader completely. I never see the B&N Home screen, Reader or Launcher.
Click to expand...
Click to collapse
ok thx.
i'm right now upgrading the firmware (1.1.2) since the first upgrade of the touchnootler didn't work out well.
quite interested in understanding how did you manage to rip off the B&N library and put the one you have.
esseti said:
ok thx.
i'm right now upgrading the firmware (1.1.2) since the first upgrade of the touchnootler didn't work out well.
quite interested in understanding how did you manage to rip off the B&N library and put the one you have.
Click to expand...
Click to collapse
i don't know. i had some problems while rooting but right now i booted the nook and the market is working. good. how can i know which version of the touchnootler is installed?
esseti said:
i don't know. i had some problems while rooting but right now i booted the nook and the market is working. good. how can i know which version of the touchnootler is installed?
Click to expand...
Click to collapse
Which one did you download and run? That'll be the one. TN doesn't put any sort of "About..." box anywhere that I'm aware of.
Remember that you may have to wait 24 hours to be able to search, even with SearchMarket.
---------- Post added at 07:27 PM ---------- Previous post was at 07:22 PM ----------
esseti said:
ok thx.
i'm right now upgrading the firmware (1.1.2) since the first upgrade of the touchnootler didn't work out well.
quite interested in understanding how did you manage to rip off the B&N library and put the one you have.
Click to expand...
Click to collapse
I didn't rip them out. I just don't run them. I can get to them if I ever need them. I use the Mantano equivalent screens. I changed the "Library" button on the QuickMenu to run Mantano Reader using NOOK Touch Tools. That takes me to Mantano's Library screen. From there, I select books and it opens the Mantano Reader screen.
Every morning, I have Dropsync download my newspaper and magazine content created by Calibre and hit the Import button in Mantano. It's quite a nice replacement for the B&N software, especially with the improved pdf reading features.
bobstro said:
Which one did you download and run? That'll be the one. TN doesn't put any sort of "About..." box anywhere that I'm aware of.
Remember that you may have to wait 24 hours to be able to search, even with SearchMarket.
---------- Post added at 07:27 PM ---------- Previous post was at 07:22 PM ----------
I didn't rip them out. I just don't run them. I can get to them if I ever need them. I use the Mantano equivalent screens. I changed the "Library" button on the QuickMenu to run Mantano Reader using NOOK Touch Tools. That takes me to Mantano's Library screen. From there, I select books and it opens the Mantano Reader screen.
Every morning, I have Dropsync download my newspaper and magazine content created by Calibre and hit the Import button in Mantano. It's quite a nice replacement for the B&N software, especially with the improved pdf reading features.
Click to expand...
Click to collapse
the fact is: when i flashed the new version of TN i had the black screen (as it should be) but it automatically restarted. So i tried to flash it again but nothing happened. I reboot the devices and i had everything working, i needed only to accept the market agreement and nothing else. For this reason i'm not sure to have the lastest version, but, as long as it works i don't care much.
what are the diffrences between the 1.11 and the last version of TN? just that the last works and the old one shouldn't?
esseti said:
the fact is: when i flashed the new version of TN i had the black screen (as it should be) but it automatically restarted. So i tried to flash it again but nothing happened. I reboot the devices and i had everything working, i needed only to accept the market agreement and nothing else.
Click to expand...
Click to collapse
Did you follow the rest of the procedure to register with YouTube to enable the Market? You'll still probably have to wait 24 hours for the Market to work, and you'll still have to use SearchMarket to find things on your device, but it should work if you've followed the full procedure. From what you've written, it sounds as if you stopped part way through.
For this reason i'm not sure to have the lastest version, but, as long as it works i don't care much.
what are the diffrences between the 1.11 and the last version of TN? just that the last works and the old one shouldn't?
Click to expand...
Click to collapse
The old one *might* but it would take you all of two minutes to be sure you've downloaded the latest (2.1.31 as of this writing) and carefully followed the procedure that GabrialDestruir has so generously provided. Follow the entire procedure. You will spend more time trying to fix things than you will doing it by the procedure the first time.
bobstro said:
Did you follow the rest of the procedure to register with YouTube to enable the Market? You'll still probably have to wait 24 hours for the Market to work, and you'll still have to use SearchMarket to find things on your device, but it should work if you've followed the full procedure. From what you've written, it sounds as if you stopped part way through.The old one *might* but it would take you all of two minutes to be sure you've downloaded the latest (2.1.31 as of this writing) and carefully followed the procedure that GabrialDestruir has so generously provided. Follow the entire procedure. You will spend more time trying to fix things than you will doing it by the procedure the first time.
Click to expand...
Click to collapse
wait. when i turned on after the flashing the nook was already ready to go as before flashing it. so with android and all the software/books i had. no android welcome or other stuff, no registration and so on. only to accept the market ToS.
Btw:i did the 8 reboot stuff for flashing to factory. after the flash the andorid mood was still there. is this normal?
after that i upgraded it to 1.12. right now i've the 1.1.0 (that was probably the flash of TN 2.1.31 doing this).
esseti said:
wait. when i turned on after the flashing the nook was already ready to go as before flashing it. so with android and all the software/books i had. no android welcome or other stuff, no registration and so on. only to accept the market ToS.
Click to expand...
Click to collapse
Hmm. That doesn't sound right. I just rebuilt my NST, so let me summarize the steps. This is from memory, so I might get it wrong, but I did it twice recently, so hopefully my memory is good:
I did a factory wipe of user data (Settings->Erase and Deregister Device).
I did an 8 failed boot reload of the original firmware. This put me at 1.0.0, IIRC.
I re-registered with B&N.
I copied the 1.1.2 update to uSD and let it update and rebooted to confirm it was a 1.1.2.
I rebooted with my TouchNooter 2.1.31 uSD card inserted and let it run until the screen went black (10-30 seconds).
I removed the TN uSD card and put my blank 8 GB card back in.
I powered up the NST. It gave me that perverted "Touch the Android to begin" screen. I touched the little bugger.
I skipped the Google sign in per Gabrial's instructions.
I accepted the location management options.
It dropped me to the ADW screen.
I launched YouTube and signed in using my existing google account, per Gabrial's instructions.
At this point, it was working and rooted. Unfortunately, the SuperManager used in TN has never worked for me, nor has Opera Mini, so you can be stuck waiting 24 hours for the Market to activate at this point. I have worked around this by adding a few select tools to my TN bootable uSD card in /data/app (ES File Explorer to load files saved to Dropbox, Root Explorer, SearchMarket).
As usual, YMMV.
It sounds like you're not seeing the initial Android setup screen. Is that correct? What are you doing differently from my steps, if anything?
bobstro said:
Hmm. That doesn't sound right. I just rebuilt my NST, so let me summarize the steps. This is from memory, so I might get it wrong, but I did it twice recently, so hopefully my memory is good:
I did a factory wipe of user data (Settings->Erase and Deregister Device).
I did an 8 failed boot reload of the original firmware. This put me at 1.0.0, IIRC.
I re-registered with B&N.
I copied the 1.1.2 update to uSD and let it update and rebooted to confirm it was a 1.1.2.
I rebooted with my TouchNooter 2.1.31 uSD card inserted and let it run until the screen went black (10-30 seconds).
I removed the TN uSD card and put my blank 8 GB card back in.
I powered up the NST. It gave me that perverted "Touch the Android to begin" screen. I touched the little bugger.
I skipped the Google sign in per Gabrial's instructions.
I accepted the location management options.
It dropped me to the ADW screen.
I launched YouTube and signed in using my existing google account, per Gabrial's instructions.
At this point, it was working and rooted. Unfortunately, the SuperManager used in TN has never worked for me, nor has Opera Mini, so you can be stuck waiting 24 hours for the Market to activate at this point. I have worked around this by adding a few select tools to my TN bootable uSD card in /data/app (ES File Explorer to load files saved to Dropbox, Root Explorer, SearchMarket).
As usual, YMMV.
It sounds like you're not seeing the initial Android setup screen. Is that correct? What are you doing differently from my steps, if anything?
Click to expand...
Click to collapse
i wasn't doing any reset. now i'm doing what you did. let's see.
esseti said:
i wasn't doing any reset. now i'm doing what you did. let's see.
Click to expand...
Click to collapse
You should not have to, but if you're not worried about losing any data, it's nice to know exactly what state your device is in.
bobstro said:
You should not have to, but if you're not worried about losing any data, it's nice to know exactly what state your device is in.
Click to expand...
Click to collapse
did it and everything worked. right now i'm waiting for the market.
I have been using a Nook Classic for years, and finally, the light on my case gave up and it was time for something new.. So, I got me one of those fancy Simple Touches with GlowLights..
When I originally rooted my Nook Classic, I used the info from NookDev.com and everything went smoothly. I actually went back to stock because there wasn't much rooting of that device did for me. When looking at that site, it seems like they only talk about software 1.1 for the Simple Touch. Upon Googling, it seems like because of my new software, 1.2.1, everything gets pointed towards the NookManager (http://forum.xda-developers.com/showthread.php?t=2086582).
Because of how old the Simple Touch model is, all the different software versions, and all that good stuff, a lot of the articles on the web have the Nook Manager and Nooter ways of rooting.. I guess for Nooter, I would need to downgrade software first. Which is the best/most current method that will give me the best options of apps. Technically, all I want for an extra app is something that will allow me to sync my reading progress (I use mostly library books or PDFs). I would prefer Google Books, but would settle for Kindle.. I assume that the Nook Manager is the way to go, but figured it couldn't hurt to ask..
Thanks
Ok, so I got an old Nook Simple Touch. In part because they can be had for such a cheap price on eBay these days and in part because they're among the few eInk based devices that run on Android and can actually be unlocked and more done with them than the manufacturers intended (I've used an old Kindle and man I hate how locked down and generally useless they are.) Actually, I was hoping I could do some neat stuff like setup daydream with weather info and a clock and all on it while the screen was "off" but I guess I forgot that this is a relatively new thing and it looks like it's based on a really really old Android version? Either way, I'm so used to CyanogenMod and its relatively near to AOSP nature that this thing is feeling horribly limiting and unpleasant to use for me.
Anyway, I've been searching around for various guides and such. I've found tools for rooting and putting the Google Market (yeesh, I forgot they used to call it "Market" ages ago.) It seems I needed to update the system to 1.1 for this (I had bootloops until I did, so clearly you have to have the right system version.) It seems there is a newer version or two beyond this though, but I didn't see root tools (I'm still hoping I can do more with this that might require root access to actually do.) Should I be updating beyond that? Namely, are there tools to actually root and all if I do?
Also, in the meantime, I'm running into troubles with the plain and simple fact that neither Google Market nor Amazon's app store installed by these tools work which may not be fixable. The thread on here says to add an account through Youtube first, then go to gmail and manually refresh over and over until it eventually crashes. After probably 15 minutes of this my hands were too tired to continue though. I just don't think it's supposed to take 15 minutes though. When I start the market it doesn't crash like that guide mentions either. Is there any other way to fix this? Is there any point? Obviously the market app is quite old, so perhaps it's simply never going to work? Is there some alternative way to find stuff that actually works on the NST? I thought to do F-Droid, but even it requires a newer SDK version apparently (I'm getting kind of curious what version of Android its base corresponds to. Does it predate 2.2? If so I may be in trouble since I don't think any of the stuff I was hoping I could put on there will go lower than 2.2.)
For this matter, is there a better way I can do stuff like loading apps? I was hoping to at least have a file manager to be able to use do stuff, but they didn't include one. I'll probably have to track down an apk. For now I'm having to actually use the network adb (I installed the version of the tools that was supposed to do adb over USB, but it doesn't even show up as an adb device at all for me to even so much as install a driver, so I guess it's not doing adb over USB as it should. The network method seems to work, though I'm not a big fan of leaving it wide open like that on principle really, yet remembering to manually change it on and off is a pain too.)
I realize this is a really old device and probably it is very limited what I can really do with it, but I was hoping I could at least squeeze a bit of use out of it. In particular, I'm going to need a much better reading app even if I use it for its intended purpose only. When I looked it up I had thought it was a close enough to stock Android that I'd be able to load up most apps I guess and I didn't think it would be so hard to even get anything on it.
Whew!
OK, let's start with basics. You didn't say how you rooted it but if you're working from 1.1 you probably are not getting the best out of the device. 1.21 is the final stock version. If you can get your NST back to stock, I would recommend doing so. Considering what you seem to have done already probably the easiest way to go is to use the NookManager route. Go here. Follow the instructions. There is info there for adding a Gapps package after rooting. But first get yourself back to 1.21 stock. Once that's done you can either use the Search Market tool from the Gapps package, or find apps on your computer and have them show up on the NST via the PlayStore, or side-load apps from the SD card or via ADB (default on that is WiFi with NookManager--you can install the ADB Konnect app and it works fine). There are plenty of alternate readers that run on the NST. I happen to like the stock reader very much, but to each his/her own.
When all that's done, everything depends on what your expectations are and what you want from your NST. There are a variety of kernals out there as well as USB host/audio mods. Although the Android system is old and the display limits what you can do, there are many apps that run well on the device and I personally get a lot of use out of mine, even more now that I have audio. Check out what I've done (second post) and look at what others have done (in the same thread).
There's a lot of good info in this forum on modifications, apps that run well (and don't) and many tips and tricks.
I think I have most of what I need with that actually, yes. I didn't realize from the guides I initially found that you could root or install third party components with a > 1.1 system version. With that stuff I do have a semi-working Google Market now and can actually install a lot more stuff than I thought. I see also my favorite reader app not only works, but apparently knows I'm running it on a device with an eInk screen and defaults to having eInk adaptations turned on.
Is there any way it can do anything like what I had sort of envisioned before btw? Eg on the screen "off" mode have some sort of thing that shows weather or news or something that updates every so often? (Nevermind the clock thing, that's probably a bad idea. I was just wondering about dedicating it to being sort of something like a clock with it plugged in all the time. Now I think maybe I can stop using my tablet for reading and use this instead.)
Nazo said:
Is there any way it can do anything like what I had sort of envisioned before btw? Eg on the screen "off" mode have some sort of thing that shows weather or news or something that updates every so often? (Nevermind the clock thing, that's probably a bad idea. I was just wondering about dedicating it to being sort of something like a clock with it plugged in all the time. Now I think maybe I can stop using my tablet for reading and use this instead.)
Click to expand...
Click to collapse
Sounds like you are having CM lockscreen widget withdrawal
Actually that seems like a job for Tasker. But it would be potentially messy. You'd need to:
1. Clear image in custom screensaver folder
2. Turn on wi-fi
3. Open weather/whatever app to update info
4. Take screenshot and save to custom screensaver folder
5. Close app
6. Turn off wi-fi
At that point when the Nook goes to sleep the info will be displayed on the lock screen. The question is whether Tasker can wake up the Nook and repeat this at desired intervals when you're not using it.
Also, have a look here for something along the same lines. Maybe you'll get an idea.
Ironically on my phone and tablet I keep it really simple. It's just that the eInk screen of the Nook can essentially be "always on" so to speak without draining the battery like mad (since it would only actually need to wake up every half hour or so for a frequent update schedule.)
But, all that said, it just doesn't sound like this is really worth all the effort. I guess I'm actually more used to newer versions of Android mostly rather than CyanogenMod specifically as they just have more power in what these things can do. With the Nook -- even unlocked and opened up -- it really sounds like the amount of time and effort required to even remotely approach such a thing is orders of magnitude higher. Well, that's fine. I had initially thought that I might maybe just use it as some sort of really neat "smart clock" type thing (at $35-ish on eBay you won't find many clocks that could come close to doing what an Android device could theoretically do) but in the end I don't think this is really all that realistic and definitely not worth the effort. On the other hand, now that I'm able to get more stuff actually running on it and open up its capabilities more I'm thinking I could maybe use this thing for something more akin to its original intended purpose: reading. From time to time I want my tablet to be able to do a bit more and I think this can do pretty well everything I care about beyond the basic reading stuff, so maybe I can stop carrying my tablet around all the time. (And for stuff like music I have a dedicated multimedia phone courtesy of eBay that's much better off really.)
Hi folks,
I haven't been using my NST for a very long time. I was expecting a decline of interest for my old love but i thought i would figure out a solution to use my NST like i used to. But i couldnt. Because I haven't tried any sort of hacking stuff that involved rooting, installing customs roms etc. for the past 3-4 years ,i almost forgot everything about these matters. So i am an absolute noob right now :/ Memory is a b*tch and mine is weak
I really really want to release my Nook Simple Touch from Barnes&Noble's ugly stock chains. I checked some topics and i saw that most of them are dead. My question is; Is it still possible to do these things to my nook
1- root it
2-sign in to google and install a working playstore apk
3- find a working "read it later" like application which suits NST
4- find a good pdf,epub reader app
Can you please guide me through these steps, your help will be greatly appreciated. I may figure out a way to do these and don't bother with these silly questions but i can't look at led/lcd screens for long periods of time because i have a problem with my eyes. :/
Best wishes,
Baran
Here are some suggestions & pointers to get you started:
Factory-reset your NST for a clean-start base using Nook Manager (http://forum.xda-developers.com/showthread.php?t=2040351).
Update to BN ROM to v1.2.1 (if your NST has an older ROM version)
Root using using Nook Manager.
Install ReLaunch Launcher (http://forum.xda-developers.com/nook-touch/general/relaunch-best-nst-launcher-version-1-4-t3060782) and essential Google apps (e.g., Market, SearchMarket, Gmail, etc.) using NTGAppsAttack (http://forum.xda-developers.com/showthread.php?t=2086582).
Backup early and often. NookManager makes it easy to do this, so although it takes a bit of time, it's a good idea. However, NM only stores the most recent backup. You can keep "snapshots" of major hurdles by connecting your NST to your computer while NookManager is loaded up. You will see the Backup section on the SD card. Copy the two files in the folder onto your computer. I like to store them in dated folders also containing a small text file that describes the major changes. Then you can drag them back onto the SD card when NookManager has loaded to restore a specific backup--if the need arises.
I keep three or four of these backups while I am making changes. It's a whole lot better than starting from scratch if thing go south later in the game.
For pdf reading I can recommend ezpdf, if you can find an old version. It stopped working reasonably on the NST from about version 2.5 (e.g. you couldn't see text in the menu, probably because the font colour wasn't available on the eink screen, or the font type not installed - either way, really annoying if you want to change settings by guessing), but I remember I used to run it fine with some slightly older version.
Hay The Best Reader for NST is Renate's Temblast Reader
http://forum.xda-developers.com/showpost.php?p=54201382&postcount=94
It is not perfect but very viable for Nook.
I hope Renate will continue the development.
Still Nook STR is the best ereader out there. It is sad that it is no longer available officially.
Good luck with your project
Gosh!
I'm still working on the reader, it's had a lot of improvement.
I just have to find the time to get it out.
Here's a preview on my Nook Glow Plus.
(I use the same app on my NST, LG phone and Nexus 7 tablet.)
I am not hijacking this thread.
Renate love to hear about the improvement.
Renate Could you please add text selection & a Dictionary.English is my second language so I like a build in Dic like in Nook reader.
Thank Keep up the great work genius
(Sorry I didn't ment to hijack this thread)
I got a Like New NST, reset it, unregistered it, and rooted it. I haven't replaced the kernel yet. But I have noticed that (even before I rooted it) the battery consumption is unacceptable. I've seen some old threads about this (for example https://forum.xda-developers.com/showthread.php?t=1475070) , and some suggested removing some APKs like Phone.apk and TelephonyProvider.apk, while others suggested removing or disabling some B&N-related APKs.
The thing is that some other threads seem to imply these solutions are bogus and that they don't really help. There is a lot of conflicting information spread around on this topic.
Does anybody know if there is a solution to this issue? I'm really loving the NST, it's an amazing reader in all ways except for this glaring issue.
Thanks!
Winston S. said:
I got a Like New NST, reset it, unregistered it, and rooted it. I haven't replaced the kernel yet. But I have noticed that (even before I rooted it) the battery consumption is unacceptable. I've seen some old threads about this (for example https://forum.xda-developers.com/showthread.php?t=1475070) , and some suggested removing some APKs like Phone.apk and TelephonyProvider.apk, while others suggested removing or disabling some B&N-related APKs.
The thing is that some other threads seem to imply these solutions are bogus and that they don't really help. There is a lot of conflicting information spread around on this topic.
Does anybody know if there is a solution to this issue? I'm really loving the NST, it's an amazing reader in all ways except for this glaring issue.
Thanks!
Click to expand...
Click to collapse
I sympathize and don't want to add to the conflicting information. Read what I wrote here: https://forum.xda-developers.com/showpost.php?p=78287581&postcount=2 under "Decrapify system/app". I can tell you definitively that Phone.apk has little or nothing to do with your battery drain. I did a major study on that issue a long time ago: https://forum.xda-developers.com/nook-touch/general/battery-usage-phone-apk-t3341370
nmyshkin said:
I sympathize and don't want to add to the conflicting information. Read what I wrote here: https://forum.xda-developers.com/showpost.php?p=78287581&postcount=2 under "Decrapify system/app". I can tell you definitively that Phone.apk has little or nothing to do with your battery drain. I did a major study on that issue a long time ago: https://forum.xda-developers.com/nook-touch/general/battery-usage-phone-apk-t3341370
Click to expand...
Click to collapse
Thank you for all your work, you are very methodic and logical, and I appreciate your generosity sharing all your knowledge about the NST (I have been reading up on different things here before I decided to buy one.) :good:
So, to condense all this, it looks as if neither deleting Phone.apk nor disabling B&N apps helps with battery consumption. Also, am I correct in concluding that having an unregistered Nook (or a Nook which is offline, even if registered) will invariably result in poor battery life? That's quite unfortunate, as I was planning to use my NST as a fully offline device.
Winston S. said:
So, to condense all this, it looks as if neither deleting Phone.apk nor disabling B&N apps helps with battery consumption. Also, am I correct in concluding that having an unregistered Nook (or a Nook which is offline, even if registered) will invariably result in poor battery life? That's quite unfortunate, as I was planning to use my NST as a fully offline device.
Click to expand...
Click to collapse
Almost, but fortunately not quite right. Although B&N did some questionable stuff when they cobbled together the NST/G system, I don't think they expected the devices to spend a lot of time online. If the system detects that there is no WiFi, it just slaps a post-it on its internal "refrigerator" to remind it to try a check-in later. All of that happens pretty quickly and in the grand scheme of things Android where stuff is not always killed outright even when you've finished with it, it's not a Big Deal.
So register and forget. It's the easiest path to device stability and the intended power consumption pattern.
nmyshkin said:
Almost, but fortunately not quite right. Although B&N did some questionable stuff when they cobbled together the NST/G system, I don't think they expected the devices to spend a lot of time online. If the system detects that there is no WiFi, it just slaps a post-it on its internal "refrigerator" to remind it to try a check-in later. All of that happens pretty quickly and in the grand scheme of things Android where stuff is not always killed outright even when you've finished with it, it's not a Big Deal.
So register and forget. It's the easiest path to device stability and the intended power consumption pattern.
Click to expand...
Click to collapse
Thank you again, I suppose if that's the case then I will register my NST. A couple questions: So if I register the device and never again connect to Wireless that "refrigerator post-it" won't expire?
And, most importantly, if I register with B&N will they push the 1.2.2 update on my device, or can I prevent that without any ill effect? I'd really like to stick to 1.2.1.
EDIT: I read your previous OP about the 1.2.2 OTA update, and your link for how to block it here: https://forum.xda-developers.com/showpost.php?p=34433959&postcount=3
Renate NST also suggested deleting /system/app/DeviceManager.apk, but I don't know if this would be problematic with the B&N registration issue I'm trying to fix to begin with.
Is there a preferred way to do this and still keep the device registered and battery life unscathed?
I appreciate your help!
Winston S. said:
Thank you again, I suppose if that's the case then I will register my NST. A couple questions: So if I register the device and never again connect to Wireless that "refrigerator post-it" won't expire?
And, most importantly, if I register with B&N will they push the 1.2.2 update on my device, or can I prevent that without any ill effect? I'd really like to stick to 1.2.1.
EDIT: I read your previous OP about the 1.2.2 OTA update, and your link for how to block it here: https://forum.xda-developers.com/showpost.php?p=34433959&postcount=3
Renate NST also suggested deleting /system/app/DeviceManager.apk, but I don't know if this would be problematic with the B&N registration issue I'm trying to fix to begin with.
Is there a preferred way to do this and still keep the device registered and battery life unscathed?
I appreciate your help!
Click to expand...
Click to collapse
I think since you are just starting out working with the device and don't have work to lose by updating and re-rooting, registering and then updating (you can do it manually by downloading the file yourself) is your best bet. The device keeps a "last date contacted" and "next date to try contact" in settings.db. If there is no WiFi, it will just keep changing the dates. That's all.
OTOH, if you do not update but NEVER connect to WiFi, there will probably be no issue. The method to block updates "works", as I found, but it did not prevent the occasional reboot when I was connected to WiFi, so I finally just threw in the towel and updated my devices, starting over from scratch. I'm happy with the many changes I've made since, so it worked out for me. Not sure why you want to stay with 1.2.1. It is virtually identical to 1.2.2 and I don't believe there is anything on-site here that worked with 1.2.1 which doesn't also work with 1.2.2. All B&N did was patch contacts with their servers for TLS 1.2 compliance.
Deleting/disabling DeviceManager will give your NST Alzheimers as far as your registration is concerned and it will just begin wondering why it can't remember who it is and how/when to phone home--wherever that is. One of the problems with disabling B&N apps is that there are also jar files which don't get disabled and the system still tries to fool with those. You can delete/disable those as well but the more you niggle at the system architecture the more unstable the device becomes and the more things fail to work properly (like the Reader and Library).
Like I said before, it's better AND easier to just treat the device the way it was designed as far as updating or registering. You don't have to use a credit card, you don't even have to use a real e-mail address, I suppose. Then when all that is out of the way you can just install your own launcher and set the "n" button to Home. Voila! You'll never see or hear from the B&N stuff again and your battery will last a good long time.
nmyshkin said:
I think since you are just starting out working with the device and don't have work to lose by updating and re-rooting, registering and then updating (you can do it manually by downloading the file yourself) is your best bet. The device keeps a "last date contacted" and "next date to try contact" in settings.db. If there is no WiFi, it will just keep changing the dates. That's all.
OTOH, if you do not update but NEVER connect to WiFi, there will probably be no issue. The method to block updates "works", as I found, but it did not prevent the occasional reboot when I was connected to WiFi, so I finally just threw in the towel and updated my devices, starting over from scratch. I'm happy with the many changes I've made since, so it worked out for me. Not sure why you want to stay with 1.2.1. It is virtually identical to 1.2.2 and I don't believe there is anything on-site here that worked with 1.2.1 which doesn't also work with 1.2.2. All B&N did was patch contacts with their servers for TLS 1.2 compliance.
Deleting/disabling DeviceManager will give your NST Alzheimers as far as your registration is concerned and it will just begin wondering why it can't remember who it is and how/when to phone home--wherever that is. One of the problems with disabling B&N apps is that there are also jar files which don't get disabled and the system still tries to fool with those. You can delete/disable those as well but the more you niggle at the system architecture the more unstable the device becomes and the more things fail to work properly (like the Reader and Library).
Like I said before, it's better AND easier to just treat the device the way it was designed as far as updating or registering. You don't have to use a credit card, you don't even have to use a real e-mail address, I suppose. Then when all that is out of the way you can just install your own launcher and set the "n" button to Home. Voila! You'll never see or hear from the B&N stuff again and your battery will last a good long time.
Click to expand...
Click to collapse
The main reason I want to avoid 1.2.2 is because I tend to value stability overall, and since most of the stuff here was created by the era of 1.2.1 or before, I am leery of doing something that will make things less compatible. Plus I am distrustful of B&N changes on a device this old. I also thought I had read you explaining some changes that needed to be done after a 1.2.2 update to make something work (NM, maybe? I forget.)
So my question was more along the lines of whether, when I register the device, it will be flagged immediately for update and cause some trouble if I don't, or even if the update will be downloaded in the background without me being able to do anything about it. I suppose I could always patch the sqlite file to disable OTA updates and then register. That would be the safest way to go. And you need to use ADB for this to work, right? There is no way to edit the file onboard the NST itself?
I can't wait for the battery consumption to be normal, because I am really enjoying my NST with its great ergonomy and the ability to install different readers. Mine is going to be a dedicated offline ebook reader, but a great one. And much of the reason it is so amazing is thanks to folks like you and Renate who have contributed so much. :good:
Winston S. said:
The main reason I want to avoid 1.2.2 is because I tend to value stability overall, and since most of the stuff here was created by the era of 1.2.1 or before, I am leery of doing something that will make things less compatible. Plus I am distrustful of B&N changes on a device this old. I also thought I had read you explaining some changes that needed to be done after a 1.2.2 update to make something work (NM, maybe? I forget.)
So my question was more along the lines of whether, when I register the device, it will be flagged immediately for update and cause some trouble if I don't, or even if the update will be downloaded in the background without me being able to do anything about it. I suppose I could always patch the sqlite file to disable OTA updates and then register. That would be the safest way to go. And you need to use ADB for this to work, right? There is no way to edit the file onboard the NST itself?
Click to expand...
Click to collapse
There's really no reason to be concerned about the 1.2.2 update. It's all fine. B&N would not go to the trouble on an old device like this only to somehow wreck it. It's just a TLS security update and involves connection to their servers. Since you do not intend to use the device online, the only minor issue (resigning Opera Mobile browser-- which I've already provided elsewhere) is moot for you.
As for changing the OTA flag, you can do it via ADB if you install sqlite3. This is probably best since moving settings.db back onto the device after editing can be tricky. But you could eliminate the entire tango by just updating to 1.2.2 and going on with your life
nmyshkin said:
There's really no reason to be concerned about the 1.2.2 update. It's all fine. B&N would not go to the trouble on an old device like this only to somehow wreck it. It's just a TLS security update and involves connection to their servers. Since you do not intend to use the device online, the only minor issue (resigning Opera Mobile browser-- which I've already provided elsewhere) is moot for you.
As for changing the OTA flag, you can do it via ADB if you install sqlite3. This is probably best since moving settings.db back onto the device after editing can be tricky. But you could eliminate the entire tango by just updating to 1.2.2 and going on with your life
Click to expand...
Click to collapse
Thank you for clarifying that, I think I have had an overdose of information from reading too many threads in a short span of time and somehow I got the idea NookManager had some sort of issue after the 1.2.2 update that required some tinkering. The fact that the update is limited to the TLS update means it doesn't affect me, so things would be OK. On the other hand, not installing the update also seems like wouldn't be an issue and I really wanted to get ADB going anyway to install things wirelessly, so the most logical path seems to go through the minimal effort required to change that setting anyway. It turns out I already have sqlite3 installed (I am running an Ubuntu system,) so even more reason to do this!
I'll be reading up on the way to get ADB working.
BTW, I know you have proposed probably changing NookManager to address different issues you have encountered. Let me know if I can be of any help. I have no experience building Android components and limited experience compiling, but I would be happy to learn a new skill.
Thanks! :good:
@nmyshkin I easily managed to change the OTA setting through USB ADB. (I'm keeping track of all this process so when I have everything set up I will create a thread for posterity to help anyone else with the same questions.)
Now, the problem I wasn't anticipating is that I didn't foresee the battery problems, so I used that procedure to avoid the Register prompt on startup (Bypass OOBE procedure.) But of course now I don't know how to register the Nook. Do I need to reset to Factory using NookManager, root, disable OTA, and then register? It would be nice if there is a way to avoid this?
EDIT: Searching through another thread I saw your suggestions (almost 3 years old) to use the DeviceRegistrator, so after creating a B&N account I did and it said that the registration was successful, but in Settings the Account is showing up as unavailable, so I restarted the NST, and still I am getting Account Unavailable under Settings. Does the Device Registrator not work anymore? Or have B&N stop registering NST devices?
So I checked by logging into the B&N account and as expected there are no NSTs linked to my account. The DeviceRegistrator app has a few options (Register Device, Authenticate Device, Register User, and Authenticate User.) I didn't touch the User options so I guess that is to create a new account. I just used the "Register Device" option. Do I need to Authenticate Device too, or is this just not working anymore?
I read somewhere that there is also another app called OOBE Reg or something like that that basically runs the default registration procedure, but I haven't found that app in my NST.
I actually went down a similar rabbit hole myself at one point when I was investigating selective disabling of B&N apps, etc. Yes, you need to authenticate. That may or may not have the desired effect. Right now DeviceRegistrator is your only option. It may or may not be possible to authenticate a rooted device by this method.
Having said that, maybe it's time to take a step back and ask yourself whether all this angst is worth the end result when the path of least resistance will yield an equally functional result. The answer to that depends, in part, on how much other stuff you have already done. But before you do more things don't forget that the basic device needs to be in optimum working condition (like not eating battery) first.
nmyshkin said:
I actually went down a similar rabbit hole myself at one point when I was investigating selective disabling of B&N apps, etc. Yes, you need to authenticate. That may or may not have the desired effect. Right now DeviceRegistrator is your only option. It may or may not be possible to authenticate a rooted device by this method.
Having said that, maybe it's time to take a step back and ask yourself whether all this angst is worth the end result when the path of least resistance will yield an equally functional result. The answer to that depends, in part, on how much other stuff you have already done. But before you do more things don't forget that the basic device needs to be in optimum working condition (like not eating battery) first.
Click to expand...
Click to collapse
I will Authenticate using DeviceRegistrator and see if it works. The Catch 22 is that if I revert to Factory and then register the device I might have a problem with the 1.2.2 update I want to avoid (but yes, I realize at this point my aversion to 1.2.2 is basically irrational.) So I will try this approach first and report back. I will double check to see if the Nook Device shows up in my B&N account too, and I'll report again.
I agree 100% about putting the device in a sound baseline state before installing a lot into it. I'm documenting all that I do, and when I reach that state I'll create a thread about it. Hopefully it can be of use to someone down the road, because I do see new NST units being bought still every week in eBay.
I was relieved that ADB over USB was already enabled by installing NookManager and that I only needed to create a couple of files in my Ubuntu machine for it to work.
Winston S. said:
I was relieved that ADB over USB was already enabled by installing NookManager and that I only needed to create a couple of files in my Ubuntu machine for it to work.
Click to expand...
Click to collapse
That's actually news to me. I had thought the flag for WiFi ADB was set. I've never tried USB.
nmyshkin said:
That's actually news to me. I had thought the flag for WiFi ADB was set. I've never tried USB.
Click to expand...
Click to collapse
Yes, apparently ADB Konnect is set up so that if you start ADB Wireless it sets the flag, and then unsets it. I just tried ADB through Wireless and it also works.
To update on the DeviceRegistrator, I tried to Authenticate the Device and it didn't work (I got a banner saying that the operation is no longer supported.) So it looks like I will need to restore to Factory, register, and then root (which defeats the purpose of disabling OTA updates, as I can't do that until I root.)
@nmyshkin, is resetting the Nook to factory by using "Erase & Deregister Device" option in the stock Nook Settings the same as resetting to factory.zip from NookManager or holding the two Page Back hardware buttons on startup?
I reset mine using the "Erase & Deregister Device" menu option, and then registered and rooted it again, but still I am having problems with CoolReader (I am using the cr3_0_49_13.apk posted in the relevant thread.) Basically, there are no options to set the refresh interval where they should be, and the Options interface is black. Somebody mentioned this as well but they fixed it by restoring to factory, so I'm wondering what the deal is. Is this the only version of CoolReader people use with the NST?
Winston S. said:
@nmyshkin, is resetting the Nook to factory by using "Erase & Deregister Device" option in the stock Nook Settings the same as resetting to factory.zip from NookManager or holding the two Page Back hardware buttons on startup?
I reset mine using the "Erase & Deregister Device" menu option, and then registered and rooted it again, but still I am having problems with CoolReader (I am using the cr3_0_49_13.apk posted in the relevant thread.) Basically, there are no options to set the refresh interval where they should be, and the Options interface is black. Somebody mentioned this as well but they fixed it by restoring to factory, so I'm wondering what the deal is. Is this the only version of CoolReader people use with the NST?
Click to expand...
Click to collapse
No, erase and deregister does just that. It removes your account info and settings. The factory reset is an actual reimaging of the device from the protected onboard image. This can be done with the two button technique, NookManager or eight failed boot attempts.
I'm afraid I can't help much with CoolReader. I once had a version installed but found it had way too many settings for me. I ended up using only the screensaver/book cover option but that was pretty silly and I eventually got rid of and wrote my own app for that.
I located the version for the other fellow, but that's the extent of my knowledge. I'll try it in a bit and see what you're talking about.
nmyshkin said:
No, erase and deregister does just that. It removes your account info and settings. The factory reset is an actual reimaging of the device from the protected onboard image. This can be done with the two button technique, NookManager or eight failed boot attempts.
I'm afraid I can't help much with CoolReader. I once had a version installed but found it had way too many settings for me. I ended up using only the screensaver/book cover option but that was pretty silly and I eventually got rid of and wrote my own app for that.
I located the version for the other fellow, but that's the extent of my knowledge. I'll try it in a bit and see what you're talking about.
Click to expand...
Click to collapse
Please, don't waste any time with CoolReader. As usual, you saved the day. I'll reimage the device using the correct procedure, as I mistakenly believed this is what the Erase and Deregister option did. I think this will take care of the CoolReader weirdness, and if not I have found that NoRefresh works remarkably well with it anyway. Thank you!
Winston S. said:
Please, don't waste any time with CoolReader. As usual, you saved the day. I'll reimage the device using the correct procedure, as I mistakenly believed this is what the Erase and Deregister option did. I think this will take care of the CoolReader weirdness, and if not I have found that NoRefresh works remarkably well with it anyway. Thank you!
Click to expand...
Click to collapse
Mmm.....I see nothing in that version of CoolReader thats looks anything like it was adapted for the NST. I got that version from a e-book blog post link so shame on me for passing along bogus stuff. It's definitely NOT the version I once had installed (whatever that was...). The current market version is incompatible and the "new" CoolReader GL installs but does not run. I took a look at the CR home at SourceForge and there are many versions available there but it would be trial-and-error with them--and maybe there is no magic bullet. If you search for "CoolReader" on the forum you will find a variety of references. In some lists of "working" apps there are version numbers. Tracking down one of those might be a start.
nmyshkin said:
Mmm.....I see nothing in that version of CoolReader thats looks anything like it was adapted for the NST. I got that version from a e-book blog post link so shame on me for passing along bogus stuff. It's definitely NOT the version I once had installed (whatever that was...). The current market version is incompatible and the "new" CoolReader GL installs but does not run. I took a look at the CR home at SourceForge and there are many versions available there but it would be trial-and-error with them--and maybe there is no magic bullet. If you search for "CoolReader" on the forum you will find a variety of references. In some lists of "working" apps there are version numbers. Tracking down one of those might be a start.
Click to expand...
Click to collapse
Thank you for looking at this. I am a little confused, because you helped @ALinkToTao who was having problems with it, and he seems to imply that the version linked here which you referred him to ended up working for him..
So I'm just going to write that off to him being confused about the version he ended up installing. I will see if I find something that works, thanks again.
Winston S. said:
Thank you for looking at this. I am a little confused, because you helped @ALinkToTao who was having problems with it, and he seems to imply that the version linked here which you referred him to ended up working for him..
So I'm just going to write that off to him being confused about the version he ended up installing. I will see if I find something that works, thanks again.
Click to expand...
Click to collapse
Yeah, so I need to redeem myself there. In my lame defense, I was just going with what was posted here: https://blog.the-ebook-reader.com/2...artial-refresh-and-page-button-support-video/
Clearly that is bogus. So I checked out @wozhere's listed working version, or something close.
I think the place to start is with the 3.1.2 series from the SourceForge home of CoolReader. The attached version looks a lot more like what I remember and has screen refresh options (only visible as settings while viewing a book).
There were many more options on the version I once had, so this one is a starting point only.