I notice there's always a system process called ADCP running, I think it stood for Amazon Device Control Program. Anyone investigated what it does and what happens if you disable it? I'm wondering if it's involved in any way with the OTA updates, and also what ramification disabling it has, like will the various Amazon programs not work right? I've not been adventurous enough to experiment with, in fact I've got my wifi off for now until it's clear whether the OTA update can be blocked by the methods discussed here.
jb0ne said:
I notice there's always a system process called ADCP running, I think it stood for Amazon Device Control Program. Anyone investigated what it does and what happens if you disable it? I'm wondering if it's involved in any way with the OTA updates, and also what ramification disabling it has, like will the various Amazon programs not work right? I've not been adventurous enough to experiment with, in fact I've got my wifi off for now until it's clear whether the OTA update can be blocked by the methods discussed here.
Click to expand...
Click to collapse
check this out
http://forum.xda-developers.com/showpost.php?p=20166149&postcount=1
essentially it connects the amazon apps to the kindle registration
I'm suspicious, I suspect it does more, and is the thing responsible for the OTA updates everyone is getting no matter what they do....
I really want to try and freeze it, but too afraid that it might actually be necessary...
Well I installed Droidwall and didn't give permissions to ADCP and so far my device is still registered and I can watch videos and use my books, can use the Amazon App Store (I gave it permissions, I don't think it's the program responsible). I've effectively disabled ADCP by not allowing it to connect to the internet, but it's still running in case it does, say, DRM services or something. All good and still on 6.2 (and I did do the other suggestions previously).
jb0ne said:
Well I installed Droidwall and didn't give permissions to ADCP and so far my device is still registered and I can watch videos and use my books, can use the Amazon App Store (I gave it permissions, I don't think it's the program responsible). I've effectively disabled ADCP by not allowing it to connect to the internet, but it's still running in case it does, say, DRM services or something. All good and still on 6.2 (and I did do the other suggestions previously).
Click to expand...
Click to collapse
Glad it worked for someone else too. I am not sure which process is actually responsible for downloading and installing the update though.
EDIT: Oh, I didn't post about DroidWall in this forum. I figured out DroidWall last night and we posted on Gizmodo about it.
An important element I overlooked, even after adding apps to the whitelist, you have to go back to Menu and enable firewall. It's NOT enabled by default even if you change whitelist apps. Even though I had it not running firewall until 10 minutes ago, I hadn't received update. Maybe moving otacerts.zip stopped it....
jb0ne said:
I'm suspicious, I suspect it does more, and is the thing responsible for the OTA updates everyone is getting no matter what they do....
Click to expand...
Click to collapse
I installed ADCP on CM7 when I was trying to find a way to get amazon video working. It brings up the page to register your kindle, but it never seemed to work right on CM7. There's a different apk for the OTA update, if I remember correctly.
You could put /system/etc/security/otacerts.zip back in and see if ADCP then lets your register your kindle.
Related
I've been collecting free apps from Amazon on my rooted NC for awhile now. At the time I got each of these apps, they were listed as "compatible" with my device.
Now suddenly a lot of them are not, and I am unable to go back and re-install the ones that I had removed.
Even worse, pretty much everything I've tried so far today to grab has come up as incompatible. Even really simple stuff that should have no problem running.
Oddly, at some point early on, Amazon listed my device as simply "Nook Color". Most of the apps are still showing as compatible with that device. Unfortunately, that's not what Amazon thinks my NC is anymore! I now have a second device on my list called "BarnesAndNoble NOOKcolor", which almost nothing is compatible with.
So then I wanted to check to see if Amazon was behind this, maybe to screw B&N fans. But nope! The Android Marketplace lists every game I've checked so far today as incompatible with my NC!!!
That's certainly news to me, considering some of the games I checked are currently installed on my NC and work perfectly.
I'm not sure what's going on here, but it's sort of scaring me. Who's locking down my rooted NC? If the official android marketplace says everything is incompatible... there aren't a lot of options for getting apps.
Do search with "Market" keyword, you will see about 10 threads with many responses and instructions how to fix this.
votinh said:
Do search with "Market" keyword, you will see about 10 threads with many responses and instructions how to fix this.
Click to expand...
Click to collapse
There are quite a few threads found that way, but none of the ones I read helped. I did the "stop/restart Framework/Google and reload" and nothing changed. Most of the others seem to be related to problems with the new market, which was working perfectly for me up until today, or problems run into right after rooting. I've been rooted for about 5 months with no market problems of any kind, and I haven't changed anything on my NC for over a month.
I also tried clearing the settings for the Amazon market and also deregistered the device from my amazon account, forcing it to re-register. Still no luck.
Anyone else seeing this, or have another suggestion?
My old market and new market were working fine too, just like yours, until a few days ago. If you try the 160 dpi/reboot/clear-data-from-market procedure below and that doesn't work, then you may have a totally unique problem that just happens to have the same variety of symptoms everyone else is having. (I'm doubtful.) This procedure seems to be fixing the problem for almost everyone else. Did you try it? It fixed mine.
1) set dpi to 160 in build.prop
2) reboot
3) clear market app data (force close first may help?)
4) restart market, accept terms, let it rebuild data at 160 dpi
5) profit
the above we all seem to agree on now. Next steps are more speculative
6) set dpi back to 161 (or whatever you had)
7) reboot
8) profit indefinitely (unknown how long this lasts; I rebooted >5 times including flashing a nightly w/o issue)
9) do NOT clear data again as this rebuilds data at the wrong dpi again.
Click to expand...
Click to collapse
Thanks, I had tried the first half, but not the second. I used manual nooter, so my dpi entries originally looked like:
ro.sf.lcd_density.xdpi=169.3333
ro.sf.lcd_density.ydpi=169.3333
I don't know if that makes a difference.
Anyway, I just tried the second half of the above process but I'm still showing as incompatible. I wonder if I need to re-noot.
Everyone trying to be helpful here seems to miss the poster's dilemma. He is talking about the Amazon Market, not the Android Market. Hopefully someone familiar with the workings of the Amazon Market will chime in with some suggestions.
My original problem was with Amazon's market, but it looks like that's just a symptom of the bigger problem that I noticed first because I use it every day, as opposed to much less frequent use of the android market.
But the Android market suffers the same problem and from what I've read online it sounds like the problem was started with changes by Google that Amazon also adopted.
Interestingly I noticed this for the first time last night on the Android market and this morning with the Amazon market. Ebook downloads presently are unaffected to my rooted NC. Amazon recognizes my device as an Android but when I tried to make an app purchase this morning it suddenly tried to download it to a BN Nook. Amazon emailed me this morning saying that unless I have their market preloaded by the manufacturer they do not support it. Collusion?
I got the "not compatible" message after installing the most recent update from the Amazon App Store. Fortunately, I have the very first app store apk. I uninstalled the updated app store, then installed the old apk, logged in and then updated it and for some reason that worked for me. You might try not updating also to see if that works. I am not using CM7 though and I'm not manualnootered. I'm minirooted meaning I can side load apps and have superuser access, but no Android Market access and some other things.
I have attached the apk I used. I hope it works for you.
unibroker said:
Interestingly I noticed this for the first time last night on the Android market and this morning with the Amazon market. Ebook downloads presently are unaffected to my rooted NC. Amazon recognizes my device as an Android but when I tried to make an app purchase this morning it suddenly tried to download it to a BN Nook. Amazon emailed me this morning saying that unless I have their market preloaded by the manufacturer they do not support it. Collusion?
Click to expand...
Click to collapse
A better question would be is Amazon trying to bork the Nook Color with their app?
Anyone else have a suggestion for getting the Android Market working again for me?
thanks for the APK, I'll try it when I have a chance... But since the Android market from Google doesn't work either I'm hoping for a fix to that.
If you make the change in your build.prop “ro.product.manufacturer=BarnesAndNoble” to “ro.product.manufacturer=samsung” then reboot the device. This seems to fix most of the device compatibility problems in the Amazon appstore. I went down the top 100 paid and free app list, and the only apps that came up with the compatibility problems after doing this are,
Soundhound
Peggle
Thumb keyboard
Trainz simulator THD
Chuzzle
Talking Tom Cat
flexT9
GrooVe IP
Ultra Voice Changer
TV.com
Compass
Also attached is the amazon appstore v.1.14, it has the double click buying fix, but does not give all the compatibility issues. With installing this version does fix the compatibility problem, but you will be constantly hounded with the update reminder.
I don't use Facebook, but I was able to find, install and open the Facebook app with the new market. Do the density change using 240. Its more stable than 160 for whatever reason.
GMPOWER said:
If you make the change in your build.prop “ro.product.manufacturer=BarnesAndNoble” to “ro.product.manufacturer=samsung” then reboot the device. This seems to fix most of the device compatibility problems in the Amazon appstore.
Click to expand...
Click to collapse
Thanks for the suggestion. Unfortunately it had no effect. The first four apps i tried not on your list all came up incompatible, as did stuff on the google market.
I'll try your attachment to see if it helps. Thx!
kayak and tripit does not install
Running MN4.5 on NC. Kayak and Tripit are visible in Market and downloads - but I get a window that just says "error".
Any suggestions?
GMPOWER said:
Also attached is the amazon appstore v.1.14, it has the double click buying fix, but does not give all the compatibility issues. With installing this version does fix the compatibility problem, but you will be constantly hounded with the update reminder.
Click to expand...
Click to collapse
The old version of the market is working! I was able to install a number of apps that didn't previously work.
Now if I could just get the Google market to work!
Thanks for that link!
I was having the same problem with the AMAZON appstore (but not the android marketplace, for some reason) but I couldn't find the old amazon appstore apk. Going back to it totally fixed the problem. But you're right, the constant reminders to update the apk are a pain in the whatsus.
Also try going into application management and goto market and tap uninstall updates. Also use titanium backup or similar program to freeze market updater.
By what I read, I bet amazon is trying to block the competition because they are fixing to come out with their own tablets and by horning something like the nook you might be enticed to buy their tablet.
I voided my warranty and your mum.
My markets all seem to do whatever the f*ck they want the moment i need an application that was perfectly available minutes before. What i've done to get around the issue if neither the market or the amazon store have what i'm looking for is: (i know its tedious but hey it works)
1) install astro
2) using your android phone assuming you have one, download the applications you want regardless of them being compatible with the nook color according to the android market.
3) once your files are installed on your phone use astro to create a backup of the .apk files you want (open astro > menu > tools > application manager/backup)
4) i then take my sd card out of my phone and pop it into my nook color and install my apps through w.e file manager it is i have on the nook color
all the games that i cant normally download onto my nook through the official methods i've been able to install and play through the method i've been using. not ALL apps will allow you to back them up though =/
Posted this on Gizmodo last night - not sure if people would still find it useful.
http://gizmodo.com/5870339/how-to-keep-your-kindle-fire-rooted-and-update+free
Bascially: just install DroidWall and whitelist the applications you want to give access to. Even though I would rather do this for now, TWRP + 6.2.1 w/built in su does seem tempting though.
this has already been posted to the XDA forums....
http://forum.xda-developers.com/showpost.php?p=20599145&postcount=13
krelvinaz said:
this has already been posted to the XDA forums....
http://forum.xda-developers.com/showpost.php?p=20599145&postcount=13
Click to expand...
Click to collapse
I was the first one to post about it.
http://forum.xda-developers.com/showpost.php?p=20569169&postcount=221
My post count was too small to create a standalone post or insert URLs.
And actually, zirooo just copied and pasted my Gizmodo article, although he did include a helpful image.
You would have to block all amazon services including video, store, etc.
It might be easier to turn off the wifi.
LukeQr said:
You would have to block all amazon services including video, store, etc.
It might be easier to turn off the wifi.
Click to expand...
Click to collapse
Actually, you can selectively choose Video and Appstore. Enabling those did not cause the update to download.
The only way to know for sure would be to use the device for a couple days as many suggested blocks didn't show them selves to be ineffectual until a number of days went by.
Well here is why I think this one works for real:
Before installing DroidWall, the instant my Kindle would connect to Wi-fi, my bandwidth would spike to 600kbps (as per my Tomato router). There were no other applications that would be running, so I attributed that to the update. After installing DroidWall, the massive spike ceased.
Hopefully I'm posting in the correct section. Found this and wanted to share it. A simple tool to block bloatware of many phones, with and without root. Check out the following forum :
http://forum.xda-developers.com/and...er-remove-carrier-bloat-t2998294#post58069093
Just a note for anyone who doesn't want to use a tool for this (or is on a non-Windows platform). Everything that tool does can be accomplished without root via the ADB command interface described in this topic in our own forum
Nice cross link nonetheless, have a thanks
Ironically, I used the method that you're talking about on my z3c.
I thought this tool makes the process simpler as a frontend with some descriptions too.
It works works on my z3c without root because of kitkat. Other roms do require root.
And you're right, windows only application, good call
Essentially it just freezes the app, which without root is a very good thing, should you need to enable it again.
Thanks, though does anyone know how to block the Enterprise Service? It unblocks itself as soon as I try to block it.
Edit: never mind I got it, had to revoke its device admin rights before blocking it. Annoyingly a bunch of previously disabled apps got enabled again. smh.
degraaff said:
Annoyingly a bunch of previously disabled apps got enabled again. smh.
Click to expand...
Click to collapse
Yeah, I had the same thing here, I froze some with Titanium Backup (root) and they unfroze themselves....
I have access to an unlocked and a locked device, the same thing happened when I tried to disable apps @ the one with the locked BL. The thing that helped me was clearing the data/cache for the apps that I were about to disable. (aka before disabling them.)
Try that.
Sent from my D5803
degraaff said:
Thanks, though does anyone know how to block the Enterprise Service? It unblocks itself as soon as I try to block it.
Edit: never mind I got it, had to revoke its device admin rights before blocking it. Annoyingly a bunch of previously disabled apps got enabled again. smh.
Click to expand...
Click to collapse
Correct, we had that (a longer time) before: you have to disable it in settings -> security -> administrators before you block it. Don't confuse disabling with blocking. Disabled Apps may get enabled again after disabling device admins, blocked ones shouldn't.
Just for the sake of completion, here is the complete adb tutorial+ a nice list of processes which can be disabled so you dont have to look them all up
https://www.reddit.com/r/SonyXperia...battery_life_is_out_of_this_world_bye/cnmj0vn
2mal16 said:
Just for the sake of completion, here is the complete adb tutorial+ a nice list of processes which can be disabled so you dont have to look them all up
https://www.reddit.com/r/SonyXperia...battery_life_is_out_of_this_world_bye/cnmj0vn
Click to expand...
Click to collapse
Why does he list Small Apps as one of the main bloatwares to block? I'd think small apps is actually quite a useful addition to many.
degraaff said:
Why does he list Small Apps as one of the main bloatwares to block? I'd think small apps is actually quite a useful addition to many.
Click to expand...
Click to collapse
I agree but he states "You could leave the small app launcher/widget if you like it." . Apparently some ppl just dont like it .
Sorry to bother you guys, I would really like to kill/freeze some apps from this great device, in the easiest way possible and WITHOUT connecting the device to the computer. Is it possible to enter all those commands in a Terminal Emulator on the phone itself? Would it be great if we can do like a script or a batch that disable all the apps we dont need/want so, as soon as we reset the phone, it will disable/kill them in an easy way, not 1 by 1 going into the applications list.
Sorry again if this was a stupid question, but this is chinese for me.
Thanks in advance.
Alx
Wow... Great info i really like it...
Nice App!! Would be nice making a list of secure app to be block, without making any damage to the phone Like com.sony.touchscreen, Device Usage, User Data Logging and Crash Monitor what does each one?
I tried to use a Terminal Emulator and kill the What's New using PM BLOCK blah blah blah......it says "killed" but the app is still working.......what is wrong? *in english, please
Thanks in advance.
I recently discovered the joys of package disabling, using this XDA article as a guide and it has been 99% amazing. My battery life went up significantly and the bixby button is disabled without having to use some third party app.
However, the 1% that isn't amazing is the fact that google play seems to no longer be able to automatically update my apps. I can go in and manually update them, and it still shows a big list of which apps are available to update, and auto update is still turned on... but I suspect something I disabled may be not allowing google play to actually run the updates. Any thoughts?
I was reading another thread about which things people have disabled, and someone mentioned the settings menu loads slower... another person knew right away that it was two services that you had to re-enable, so I figured maybe someone just kinda knew what to do without having to go through each service/package and guess...
jigielnik said:
I recently discovered the joys of package disabling, using this XDA article as a guide and it has been 99% amazing. My battery life went up significantly and the bixby button is disabled without having to use some third party app.
However, the 1% that isn't amazing is the fact that google play seems to no longer be able to automatically update my apps. I can go in and manually update them, and it still shows a big list of which apps are available to update, and auto update is still turned on... but I suspect something I disabled may be not allowing google play to actually run the updates. Any thoughts?
I was reading another thread about which things people have disabled, and someone mentioned the settings menu loads slower... another person knew right away that it was two services that you had to re-enable, so I figured maybe someone just kinda knew what to do without having to go through each service/package and guess...
Click to expand...
Click to collapse
I ran basically the same huge long list that guy exported in the thread about disabling Bixby / etc.. and I didn't experience this issue. You may have to play the 50/50 game until you isolate which service is responsible
Bump!
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.