Database Users

Signing apps help needed!

I got my app ready to go, 99% positive I did everything right so...
I used the jarsigner to sign my app as suggested by google and I get the jar verified message but when I try to upload it to the market it says its not properly signed?!
I googled n read n google n read and cannot find the problem or a solution, I've seen people saying its just a bug, restart, reinstall, try again. Or ppl saying its something wrong with the editing of the manifest and even a icon in the apk causing the error...
I've tried everything n I just can't seem to figure it out so I ask for someone familiar with this issue to please help cus my brain is fried!
I also wanna add that zipalign doesn't work for me either, I use a bat file that someone created on here that does it automatically cus when I try n use command prompt it keeps giving a cannot open .zip or can't find error?!
Again, I would really appreciate the help! I got my app, payed my fee n I'm ready to go, I just need help gettin past this. Thx!
Sent from my SPH-D700 using XDA App

Are you using eclipse to write the app? If so, just use Eclipse's "Export" (File->Export) function to do all the work for you.

I used the app inventor and used all the tutorials that are floatin around everywhere. I have eclipse but dont know how to use it cus its more code based and I havent reached that point yet. Even if there was a way to import the apk to Eclipse just do sign it would be great but I dont think it can be done. Its weird cus now I cant even get me apk to recompile after editing the xml file either! I've tried everything manually and fount programs that do it for you with one click and nothing... Its just one headache after another and I cannot figure it out nomatter how much googlin and searching on here I do! Im also starting to think it has something to do with the way the xml file is edited, I've read the tutorials and watched the videos and it seems to be right so if thats the case then I just done know... Im gonna post my xml file so anybody with this knowledge can take a look at it...
I also wanted to add that I am self taught in all this, besides getting help from others to learn so when editing a xml file I just copy, paste, backspace n enter which is what Im guessing Im suppose to do, I match up everything as others have it but Im not sure if iIm suppose to be using different commands or with xml editing things work different... So if thats the case please "school" me on that lol. Thanks!

This is what my .xml looks like...
This is how it comes up on Internet Explorer, when Im in notepad editing it doesnt show the - symbols though, maybe thats my mess up, I dont know cus it doesnt show them in notepad lol. HEADACHES! lol.
<?xml version="1.0" encoding="UTF-8" ?>
- <manifest xmlns:android="http://schemas.android.com/apk/res/android">
package="appinventor.ai_djykcor1.LOTF" android:versionCode="1" android:versionName="1.0">
<uses-sdk android:minSdkVersion="3" />
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.VIBRATE" />
<uses-sdk android:minSdkVersion="3" />
- <application android:label="LOTF" android:icon="@drawable/ya">
- <activity android:label="LOTF" android:name=".Screen1">
- <intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
<activity android:name="com.google.devtools.simple.runtime.components.android.ListPickerActivity" android:configChanges="keyboardHidden|orientation" />
- <activity android:name="com.google.devtools.simple.runtime.components.android.WebViewActivity" android:configChanges="keyboardHidden|orientation">
- <intent-filter>
<action android:name="android.intent.action.MAIN" />
</intent-filter>
</activity>
</application>
</manifest>

I've never used app-inventor so I can't help you with this. I always just export from eclipse.

Well when I try to import it to Eclipse it gives a error and the xml file cant be read properly or somethin, It has a icon on it that seems to make it look as a error...
com.android.ide.eclipse.adt.internal.project.AndroidManifestHelper] Unable to read C:\android-sdk-windows\AndroidManifest.xml: java.io.FileNotFoundException: C:\android-sdk-windows\AndroidManifest.xml (The system cannot find the file specified)

As a long time programmer, I'll use anything that helps me develop code quickly and easily. And, IMO, Eclipse is the tool.
Creating, testing and deploying your app in Eclipse is great. Signing an app via Export (as mentioned above) takes about 30 seconds.
Google for Android Eclipse Hello World app and it will walk you through doing an app in Eclipse.
Then you can create a new project and copy your code and xml into the project.

I have been learning in eclipse now and I finally got things to go except I keep getting force closes now with my app and Im lost from here... I anybody can help id really appreciate it!

Learn how to log messages, put them in your code to trace its logic and then use logcat to see where the program is abending (old COBOL term for force stopped LOL).

ykman1 said:
I got my app ready to go, 99% positive I did everything right so...
I used the jarsigner to sign my app as suggested by google and I get the jar verified message but when I try to upload it to the market it says its not properly signed?!
I googled n read n google n read and cannot find the problem or a solution, I've seen people saying its just a bug, restart, reinstall, try again. Or ppl saying its something wrong with the editing of the manifest and even a icon in the apk causing the error...
I've tried everything n I just can't seem to figure it out so I ask for someone familiar with this issue to please help cus my brain is fried!
I also wanna add that zipalign doesn't work for me either, I use a bat file that someone created on here that does it automatically cus when I try n use command prompt it keeps giving a cannot open .zip or can't find error?!
Again, I would really appreciate the help! I got my app, payed my fee n I'm ready to go, I just need help gettin past this. Thx!
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
There's Two Apps Available On The Market That Sign Apk's, Zip's, & Jar's
"Zipsigner", & "Signapktic"! I Personally Like "Signapktic", But Both Work!!!
Sent from my HERO200 using XDA App

Well now I got everything good to go but now Im getting force closes so it seems to be a debugging issue that Im tryin to figure out... If any of you can help I'd greatly appreciate it. Shoot me a PM with your # or email, I'm completely lost from here and its SSOOO frustrating cus Im right at the end of the process...

ykman1 said:
Well now I got everything good to go but now Im getting force closes so it seems to be a debugging issue that Im tryin to figure out... If any of you can help I'd greatly appreciate it. Shoot me a PM with your # or email, I'm completely lost from here and its SSOOO frustrating cus Im right at the end of the process...
Click to expand...
Click to collapse
What's the app exactly? I might be able to help.

Debugging can be one of the most frustrating or satisfying jobs as a programmer.
As I said earlier, put Log.v or Toast messages before and after every line of code if you have to. Check the logcat. Comment-out chunks of code until it runs. Un-comment one line at a time till it blows up and you should find your problem and be able to fix it.

Rootstonian said:
Debugging can be one of the most frustrating or satisfying jobs as a programmer.
As I said earlier, put Log.v or Toast messages before and after every line of code if you have to. Check the logcat. Comment-out chunks of code until it runs. Un-comment one line at a time till it blows up and you should find your problem and be able to fix it.
Click to expand...
Click to collapse
Programmers life in a nutshell lol.

Yeah buddy, been there, done that. In college, while taking COBOL, learning to debug an ABEND was a nightmare; no help whatsoever to where it was bombing unless you let it print the 500 green bar pages of the dump . Off topic but...
We had this one room for the advanced class...crappy old IBM terminals, but we had our OWN line printer...which meant we didn't have to go and wait at computer center for our output. This printer was on a table in front of the room and when it fired up, it was soooo loud and actually shook all the tables in the room.
We were all intent on our coding, but sometimes, in the back of our heads, we noticed the printer NOT stopping. Once one of us realized it wasn't a lot of back to back job prints, we knew someone had sent a dump to the printer! The pour soul was summoned to go up and cancel the job, head hung in shame ROFL!!

I appreciate the replies everyone, not sure if I said this before but I'm self taught in all this, learning one step at a time so now that it seems to be a debugging thing ima find the logcat n post it when I get to the lab. Thanks!
Sent from my SPH-D700 using XDA App

Newklearx3 said:
What's the app exactly? I might be able to help.
Click to expand...
Click to collapse
The process is I am making the app in app inventor then importing it to eclipse to edit and make any changes, I am not as advanced to work stricly with code so I use the AI as a base to start the project and I'm learning one step at a time when editing or generating code. Ima be taking a class on this soon once I figure out the best thing to go for... thanks
Sent from my SPH-D700 using XDA App

[Q] HELP with stupid errors in main.xml!

I am at my wits end with this and cannot figure out what is wrong.
Its a plain screen with imagebuttons and a BG - any idea why this is giving me error at the top?

what exactly is the error message saying?

Can you highlight the error and screenshot it again so we can see what it says?
Sometimes Eclipse can mess up give you an error for no reason. Go to the 'error' dialog at the bottom, right click the error and delete it. If it reappears then there's problem with your code.

That "error" can still be there even if your XML is ok. Make sure you save the file and then do a "Clean Project". Should fix it.

Hyperbyte,Meltus - sorry i dun goofed - attached is new screen cap - for some reason nothings coming from the error log though
Rootstonian - Thanks for your advice, but after saving and cleaning nothing has changed.
For record I am on latest release as of yesterday of eclipse and Android SDK

Yeah... the error tracking in xml files is less than helpful in eclipse. I think you probably have a typo somewhere. Just cut out tablerows until the error goes away, then youll find it

Lakers16 said:
Yeah... the error tracking in xml files is less than helpful in eclipse. I think you probably have a typo somewhere. Just cut out tablerows until the error goes away, then youll find it
Click to expand...
Click to collapse
I shall let you know how i do - my boss wouldnt let me take my workstation tower home for the weekend seeing i did 30 hours straight on it doin android plus 3DS Max ****. they found me asleep on one of our AVID edit suites this morning....considering i develop personal safety initiatives for Ozzie mining industry you woulda thought i would hav not done over double the national regulated work hours....(im quitting - someone give me a job lol)

I cant see anything wrong with that XML either, these sorts of problems are very annoying. Have you tried copying & pasting the XML into another tool & see it it highlights where it isnt well formed ???

gungh0 said:
I cant see anything wrong with that XML either, these sorts of problems are very annoying. Have you tried copying & pasting the XML into another tool & see it it highlights where it isnt well formed ???
Click to expand...
Click to collapse
Ill have to try it on monday (dont have that computer on me). I haven't pasted into another tool yet, but pasting it into a different xml layout page it doesnt error until i delete the main.xml and rename second xml to main

Yeah, that one's a real PITA. I still say no error is there LOL
Usually the red "X" is AT or NEAR the point of the error from my experience.
I would just copy the whole lot to a text file, then shift-command-down delete what's there and save the empty main.xml. Then copy lines back one by one and see what happens.
I remember a time working on a mainframe COBOL program...wasn't compiling. Worked on it for days! I gave up and just recreated the whole program...it was like some hidden character was in the original code.

ive had some errors like this pop up in eclipse when i copy and paste xml in to eclipse.
i would delete the whole thing and retype each line manually (i know it sucks)
this is the only way i have found to get rid of this error.

Have you tried physically deleting the error message from the error log at the bottom?
It sounds stupid but it can sometimes work.
Eclipse is buggy as hell!
Sent from my Nexus One using XDA App

Two things to try (after I had a quick look at a main.xml which I know works)
Code:
<?xml version="1.0" encoding="utf-8"?>
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
android:id="@+id/root"
1- add the xmlns:android="http://schemas.android.com/apk/res/android" to your first <TableLayout ........./> block. See if that fixes anything.
If not, then go to a .java file so the main.xml re-examines itself in Eclipse, maybe delete the error, maybe fix the project and then see if it all works then.
2- Try deleting the space between the <?xml ...?> and the <Layout> block; sounds stupid, but might actually work
Also, always be in a .java file tab (don't have eclipse show the .xml; go to the .java tab) when you compile. For some strange reason my Eclipse always screws around, pops out errors and does other wierd stuff when I compile if I'm in a .xml tab.

[Q] Last read confusion

I'm using the stock nook reader and renate's Library.apk. How can you make sure the last read icon on the top bar corresponds to the last read file in the library?
I am not sure where this icon gets its link. It doesn't seem to always open the last read file.

I've been thinking about asking this question (although I am using the stock reader AND library apps). My "reading now" button is getting really cranky of late. It often just goes to the first page (cover) or sometimes it goes to the first page AND displays a two-option message about the different current reading positions in two Nook readers (!) and which one do I want (generally neither is correct). Right now the only sure way to get to the correct page is to go to the Library screen and select the book from there. So the Nook does remember, but the Reading Now button is not functioning properly.
For a time I had a number of B&N apps disabled (renamed ".bak") and gradually discovered the imponderable connections that seemed to render little things inoperable. I've had to restore quite a few of the apps to running to keep everything functioning except Nook Community (because the constant "nagifications" drove me crazy) but this button behavior has me baffled (as does the reference to two Nook readers!)
I wonder, are you using any sort of "cleaning" app? I am using Clean Master and find it helpful in freeing up memory but I'm beginning to think that some of the data it is throwing out might just contain the info that the button needs to function properly. It certainly messes with Tasker.

The "Last Read" icon on the status bar sends out the intent com.bn.nook.launch.LAST_BOOK
This would normally be handled by Home.apk
If you deleted Home.apk and are using my Library.apk it has its own receiver for that.
Depending on which version Nook software you have it will query
content://com.bn.nook.reader.providers.lastreadingpointprovider/
content://com.bn.nook.reader.common.providers.lastreadingpointprovider/
The LRP database is maintained by the Reader(RMSDK).apk.
Checking for the latest modification gives you the last book read.
My Library.apk sends an intent out to open that book.
Currently Library.apk does not update the order of books displayed in "Last read" unless the refresh button is hit.
Two things to look for if you are having problems:
If you let the battery die and the WiFi is always off the clock time will be wrong.
If you crash or shutdown improperly Reader(RMSDK).apk will not get a chance to update the LRP.
P.S. I just noticed a possible anomaly if you read PDF's in the reader too.

Oh! It just occurred to me one thing.
I remember opening a book that you have been reading already and it opens at page 1.
This was tied to opening the book in different ways.
There are different ways to open a book:
Through the "Last Read" icon and stock Home.apk
Through the stock Library.apk
Through my Library.apk
Through a file manager application
The LRP database is /data/data/com.bn.nook.reader.activities/databases/lastreadingpoint.db
Code:
CREATE TABLE lastreadingpoint
(_id integer primary key autoincrement,
ean text, // file URI
luid text,
offsetrmsdk text, // subfile path fragment
lastupdated long, // Unix milliseconds last read
bookdna int, // always 1?
sync_status int // always 1?
);
ean (which normally might stand for European Article Number, i.e. "UPC") is a URI, not a path.
Code:
sqlite> select ean from lastreadingpoint;
file:///sdcard/Books/aboveall.epub
...
There may be cases where a single book gets different ean's.
If you could look at LRP and see if this is so?

I actually managed to locate that db file on my own (!) and what seemed to be a companion with related information (readerlocal.db). They seemed to be full of junk info (books that had since been removed, etc.) although there were no duplicate entries, which is what I had suspected.
Anyway, I got a little "brave" (i.e., foolhardy) and decided to clean up both files in a parallel way. Then I pushed them back, reset the permissions and rebooted.
Yikes. My Nook is set to go to the B&N Home screen only on reboot. That screen flickered and flashed, never filling in any of the images. I could still use the "N" button to access other parts of the system and they were working fine, but any return to the Home screen via the Back button showed it was still in distress.
So....restore from backup...again.
It seems OK for now. I have noticed that the little "refresh" button in the Library does sometimes seem to go on and on and on without any accomplishment. I have suspected the issue was how I accessed the book-in-progress as you described. Since I sometimes read more than one book at a time, I'm all over the place with how I do things (including a Library icon in my App home screen). I'm going to try being more disciplined for a while and see how it behaves.

nmyshkin said:
I actually managed to locate that db file on my own (!) and what seemed to be a companion with related information (readerlocal.db). They seemed to be full of junk info (books that had since been removed, etc.) although there were no duplicate entries, which is what I had suspected.
Anyway, I got a little "brave" (i.e., foolhardy) and decided to clean up both files in a parallel way. Then I pushed them back, reset the permissions and rebooted.
Yikes. My Nook is set to go to the B&N Home screen only on reboot. That screen flickered and flashed, never filling in any of the images. I could still use the "N" button to access other parts of the system and they were working fine, but any return to the Home screen via the Back button showed it was still in distress.
So....restore from backup...again.
It seems OK for now. I have noticed that the little "refresh" button in the Library does sometimes seem to go on and on and on without any accomplishment. I have suspected the issue was how I accessed the book-in-progress as you described. Since I sometimes read more than one book at a time, I'm all over the place with how I do things (including a Library icon in my App home screen). I'm going to try being more disciplined for a while and see how it behaves.
Click to expand...
Click to collapse
Would it be possible to write an app that simulates opening the last read book from only one of the Library apps and then map that to the last read icon to simplify this whole system?

mergen3107 said:
Guys, if you are concerned about why sometimes the last read option goes to the 1st page, then it was already fixed by our forum users somewhere here. (I could hardly remember and trace where it all started but finally it was successfully solved)
Just install a file this package (internal.db deep in the 'data' folder. You could delete 'system' folder - this is hyphenations dictionary for Russian) through cwm or replace it manually (the zip contains detailed path) and here you go.
Click to expand...
Click to collapse
Now that was an interesting trip! Once I had Google do some translating there were a number of really interesting posts that were (mostly) intelligible. I'd want to compare that modified internal.db file with what's already on my Nook before I did any replacing. A lot of the work from that site is "russified" (not surprisingly) and there may be other changes there not really needed/wanted, but it's a good start.
I noticed in another posting there that someone said there is a related issue with in what state the Nook is connected via USB. Apparently the hypothesis is that if you don't connect while in the Library you stand a good chance of scrambling the "reading now" database entry. I've certainly been hooking up with my Nook in all kinds of states, so if that's correct, no wonder my database file was so messed up!

Installation of the internal.db file from the Russian source will not work. I've tried a side-by-side comparison of the file with the one from my Nook (FW 1.21) and there are differences (beyond the region identifier, which is easily changed). It's not at all clear what changes have been made or from what firmware the modified file came. In any case, it causes havoc when exchanged for the native internal.db
The Russian discussion points to this thread on XDA which approaches (and apparently solves) the problem another way. I'm going to give it a try.

nmyshkin said:
Installation of the internal.db file from the Russian source will not work. I've tried a side-by-side comparison of the file with the one from my Nook (FW 1.21) and there are differences (beyond the region identifier, which is easily changed). It's not at all clear what changes have been made or from what firmware the modified file came. In any case, it causes havoc when exchanged for the native internal.db
The Russian discussion points to this thread on XDA which approaches (and apparently solves) the problem another way. I'm going to give it a try.
Click to expand...
Click to collapse
Do I read this correctly, http://bit.ly/Q7MytN from that thread there should be no problem if renates Library.apk is used exclusively and the stock Library.apk has the bug?

My rooted unregistered Nook Simple Touch chews battery like crazy

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.

NST library files

Anyone knows where the files/databases are for the library to use, e.g., sorting files for recent, author and title, as well as for shelves. It seems the library module from time to time doesn't sort correctly, after adding new books. Sometimes, a book from search is not placed in the 1st in the library ( for most recent order ). So I guess there must be something wrong in related files. Any tips are appreciated.

smjohn1 said:
Anyone knows where the files/databases are for the library to use, e.g., sorting files for recent, author and title, as well as for shelves. It seems the library module from time to time doesn't sort correctly, after adding new books. Sometimes, a book from search is not placed in the 1st in the library ( for most recent order ). So I guess there must be something wrong in related files. Any tips are appreciated.
Click to expand...
Click to collapse
AFAIK there is nothing specifically for the Library app other than an xml file (/data/data/com.bn.nook.library/shared_prefs.xml) which I imagine is supposed to control how the various library options display when the library is accessed. I've never had any luck with changing the settings (which are obfuscated anyway) as I would like the library to open a certain way but it insists on reverting to something else no matter how many times I set it.
As for databases, there are two associated with the Reader app (/data/data/com.bn.nook.reader.activites/databases/lastreadingpoint.db and /readerlocal.db). Historically there have been issues with the databases becoming garbled and there are a couple of postings somewhere in the forum with sqlite sequences for clearing out the dross and starting over. I'll see if I can scare those up but you should search also. And you'll need a sqlite database viewer if you want to examine the databases on your PC to see what's there.
Edit: This is the main thread I was remembering: https://forum.xda-developers.com/t/solved-on-the-problem-of-broken-bookmarks.1467429/

nmyshkin said:
AFAIK there is nothing specifically for the Library app other than an xml file (/data/data/com.bn.nook.library/shared_prefs.xml) which I imagine is supposed to control how the various library options display when the library is accessed. I've never had any luck with changing the settings (which are obfuscated anyway) as I would like the library to open a certain way but it insists on reverting to something else no matter how many times I set it.
As for databases, there are two associated with the Reader app (/data/data/com.bn.nook.reader.activites/databases/lastreadingpoint.db and /readerlocal.db). Historically there have been issues with the databases becoming garbled and there are a couple of postings somewhere in the forum with sqlite sequences for clearing out the dross and starting over. I'll see if I can scare those up but you should search also. And you'll need a sqlite database viewer if you want to examine the databases on your PC to see what's there.
Edit: This is the main thread I was remembering: https://forum.xda-developers.com/t/solved-on-the-problem-of-broken-bookmarks.1467429/
Click to expand...
Click to collapse
Thx, I will dig a bit. Strange thing is just read books from search don't appear in library's beginning at all. On the other hand, books read from library do change order in the library. Besides database, any other possible modules that would such problems?

smjohn1 said:
Thx, I will dig a bit. Strange thing is just read books from search don't appear in library's beginning at all. On the other hand, books read from library do change order in the library. Besides database, any other possible modules that would such problems?
Click to expand...
Click to collapse
I've come up empty. From examining the two Reader databases it is clear that they do not contain any information that would create placement in the Library such as shelves. That information must be somewhere but I have not been able to find it. There is another database, home.db, which is part of the bn.home app. There is minimal data there about books, but nothing helpful.
What is distressing (besides not being able to track down where this information is stored) is that there seems to be no mechanism to flush out the databases. Looking over mine I see (sideloaded) books that I have deleted a long time ago. No wonder things act funny after awhile.
Edit: Never say never. This post: https://forum.xda-developers.com/t/automating-shelving.1378510/ reveals the whereabouts of the information for the Library. I never would have guessed B&N would use stock Android for that!

Yeah, there used to be problems with the MediaScanner on the NST.
I got used to not relying on it.
Even now, my Library app has a fixed number of locations for books and you just hit Refresh once in a while.
The AdbSync script (makefile actually) that I use just pokes a refresh after syncing the Books directory.

nmyshkin said:
I've come up empty. From examining the two Reader databases it is clear that they do not contain any information that would create placement in the Library such as shelves. That information must be somewhere but I have not been able to find it. There is another database, home.db, which is part of the bn.home app. There is minimal data there about books, but nothing helpful.
What is distressing (besides not being able to track down where this information is stored) is that there seems to be no mechanism to flush out the databases. Looking over mine I see (sideloaded) books that I have deleted a long time ago. No wonder things act funny after awhile.
Edit: Never say never. This post: https://forum.xda-developers.com/t/automating-shelving.1378510/ reveals the whereabouts of the information for the Library. I never would have guessed B&N would use stock Android for that!
Click to expand...
Click to collapse
Wow! Thx. I need to learn sqlites to see all the contents.

Renate said:
Yeah, there used to be problems with the MediaScanner on the NST.
I got used to not relying on it.
Even now, my Library app has a fixed number of locations for books and you just hit Refresh once in a while.
The AdbSync script (makefile actually) that I use just pokes a refresh after syncing the Books directory.
Click to expand...
Click to collapse
how tro refresh? Is there adb code for that? Thx again.

smjohn1 said:
Wow! Thx. I need to learn sqlites to see all the contents.
Click to expand...
Click to collapse
You can do sqlite manipulations via ADB is you have sqlite3 installed on the NST, but for a better overall view you really need to copy the database file to a PC use a tool like this.

smjohn1 said:
How to refresh? Is there adb code for that?
Click to expand...
Click to collapse
Not really.
There are ways to make the MediaScanner scan a single file.
There is no simple way to tell it to just rescan everything.
I was talking about my Library.apk which does a simple foreground scan when you:
Code:
adb shell am start -a com.temblast.library.REFRESH