[Q] Hopefully simple Nook Touch question...

MildBill · Apr 13, 2014

I have a Nook Simple Touch, BNRV300, and I have successfully modified uRamdisk to gain root shell access with ADB over USB (Thanks Renate!). I am currently on firmware version 1.2.1.
I know this may seem like heresy to some here, but I really do not want or need to root my NST and add a number of apps I won't use anyway. I have a fully rooted Nexus 7 for that sort of thing.
All I would like to be able to do is turn off the need to swipe to unlock when returning from sleep, and modify the text on the screensaver overlay.
I have discovered, by the way, that sqlite3 does not seem to be available on this NST, as when trying to use it via ADB shell, it says "sqlite3: not found".
SO, there we are... I would greatly appreciate any assistance offered.

MildBill

P.S. I have tried Nook Manager, and while it did what I wanted, there were many things added that I just have no need for. And, battery drain seemed to double.So, it had to go.

Renate · Apr 14, 2014

Regarding SQLite3.
Since the guts of it (libsqlite.so) is already in the Nook, you only need the command line executable (sqlite3).
It's here: http://xdaforums.com/showthread.php?p=50958855#post50958855
Unzip it, stick it in /system/bin, chmod 755 it.

MildBill · Apr 14, 2014

Renate NST said:
Regarding SQLite3.
Since the guts of it (libsqlite.so) is already in the Nook, you only need the command line executable (sqlite3).
It's here: http://xdaforums.com/showthread.php?p=50958855#post50958855
Unzip it, stick it in /system/bin, chmod 755 it.

Ahh, once again, thank you Renate. Now if I can get some idea on my main questions...

Renate · Apr 14, 2014

There are no simple questions here. Even the answers are complicated.
Many people have created solutions and packed them into these "manager" things.

I finally got around to doing my own minimal one.
It's packaged up in nook121patch.zip (in the signature).

Code:

C:\>adb pull /system/framework/android.policy.jar
C:\>apktool d android.policy.jar \AP
C:\>mergesmali /v C:\AP\smali C:\Nook121Patch\KeyguardViewMediator.smali
C:\>apktool b C:\AP android.policy.jar
C:\>adb shell stop
C:\>adb mount -o rw,remount /dev/block/mmcblk0p5 /system
C:\>adb push android.policy.jar /system/framework/
C:\>adb shell chmod 644 /system/framework/android.policy.jar
C:\>adb shell reboot

MildBill · Apr 14, 2014

Renate NST said:
There are no simple questions here. Even the answers are complicated.
Many people have created solutions and packed them into these "manager" things.

I finally got around to doing my own minimal one.
It's packaged up in nook121patch.zip (in the signature).

Well Renate, I hate to complicate your answer any more than necessary, but...

On the Temblast page that clicking on your signature takes me to, I do see mergesmali, one of the two tools I will need based on the instructions you gave. I do not see nook121patch.zip, nor apktool, however. Where can I find these?

Also, can you tell me something about what this will do for me?

I hate to be such a noob, I have just enough knowledge to be dangerous.

Thanks again for all your help, sorry I have to keep asking for more.

MildBill

Renate · Apr 15, 2014

Well, I wasn't that clear.

mergesmali is in the signature, nook121patch.zip is on the mergesmali project page too.
Apktool is detailed and linked here: http://xdaforums.com/wiki/Apktool

There are many patches in the nook121patch.zip
You can apply them selectively.

.jar is easy, they don't need signing.
.apk is trickier they must be signed.
System .apk is even trickier, they must be signed with the system signature.

The KeyguardViewMediator.smali will make that your Nook just opens with a push of the power button and no swipe.

MildBill · Apr 15, 2014

Renate NST said:
Well, I wasn't that clear.

mergesmali is in the signature, nook121patch.zip is on the mergesmali project page too.
Apktool is detailed and linked here: http://xdaforums.com/wiki/Apktool

Ahh! Well, my bad, I should have tried harder. And, yet again, thanks. Nook users owe you much, Renate!

MildBill

MildBill · May 11, 2014

Renate NST said:
Code:

C:\>adb pull /system/framework/android.policy.jar

OK so far, and (I think) I have apktool properly installed, then realized I also needed to install the Java Development Kit as well to use it, which I managed to do. But, when I try to do

Code:

C:\>apktool d android.policy.jar \AP

I get

Code:

 Input file (\AP) was not found or was not readable.

as a response.
So, I guess I need to return to the magic well of your knowledge for further assistance and/or instruction.
To which I can only add...

HELP!

EDIT: By the way, I am using an adb.exe implementation from another root kit I have installed, not the standard installation from the SDK. Is this perhaps part of my problem?

Renate · May 11, 2014

Well, something goofy is going on there.
Type just apktool and get the usage and version.
\AP in this case is the destination directory.
It should not already exist or else you get a warning.
Maybe the input file (the jar) can't be found, but the error message is wrong?

Code:

C:\>apktool
Apktool v1.5.2 - a tool for reengineering Android apk files
Copyright 2010 Ryszard Wi?niewski <brut.alll@gmail.com>
with smali v1.4.1, and baksmali v1.4.1

Code:

C:\>apktool d C:\nook121\system\framework\android.policy.jar \AP
I: Baksmaling...
I: Copying assets and libs...

Code:

C:\>apktool d C:\boguspath \BogusDir
Input file (C:\boguspath) was not found or was not readable.

MildBill · May 12, 2014

Renate NST said:
Well, something goofy is going on there.
Type just apktool and get the usage and version.

Well, there ya go... I got apktool v2.0.0b9.

I can get 1.5.2, but will it work with Java 7? Oh well, live and learn I guess...

MildBill

Renate · May 12, 2014

Oh, well, then the 2.0 probably uses different args.
"apktool" by itself will tell you the order of arguments.

To run anything on the desktop the Java 7 runtime environment is fine.
To compile an Android application you have to use Java 6.0 SDK.

MildBill · May 12, 2014

Renate NST said:
Oh, well, then the 2.0 probably uses different args.
"apktool" by itself will tell you the order of arguments.

To run anything on the desktop the Java 7 runtime environment is fine.
To compile an Android application you have to use Java 6.0 SDK.

Well then, since it appears from the changes that 2.0 requires the Java 7 SDK, I guess I'll uninstall it all and get 1.5.2 and Java 6.

Renate · May 12, 2014

I'm running desktop applications:

Code:

C:\>java.exe -version
java version "1.7.0"
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Java HotSpot(TM) Client VM (build 21.0-b17, mixed mode, sharing)

I'm compiling Android applications with:

Code:

C:\>javac.exe -version
javac 1.6.0_38-ea

apktool runs under the JRE, version 1.7 is fine.

MildBill · May 13, 2014

OK, finally got around to completing the instructions as posted, and except for having to add the command 'shell' to the mount statement, everything worked fine. And, it accomplishes exactly what I was after.

Next I may look into trying your library and reader apps.

Thanks again!

MildBill

P.S. You might consider rewriting the readme file included in nook121patch.zip to better describe what each patch does.

Renate · May 13, 2014

The readme is admittedly very old.
That's because I forgot that it's even there!

Each of the individual smali files has comments at the head saying what it does.
I'll make something to compile the individual comments into a single readme.

MildBill · May 14, 2014

I can also report, at this point, that unlike an other method I have tried to accomplish this simple task, this one does NOT run thru battery life like it was going out of style.

The next most popular option, NookManager, which uses the NookModManager to do this fix, uses an average of 10% battery life every day, even when in in sleep mode the whole time. Turning the option off (I.E. reinstating the swipe to unlock) again reduces battery drain to a more normal point.

But, the fix by Renate seems to use nomorebattery than the stock reader, whether reading, sleeping, with WiFi on or off. I like it!

Once again, Renate, thank you very much for this, and for all you have done for the Nook community.

MildBill

Topics

Topics

[Q] Hopefully simple Nook Touch question...

MildBill

Member

Renate

Recognized Contributor / Inactive Recognized Dev

MildBill

Member

Renate

Recognized Contributor / Inactive Recognized Dev

MildBill

Member

Renate

Recognized Contributor / Inactive Recognized Dev

MildBill

Member

MildBill

Member

Renate

Recognized Contributor / Inactive Recognized Dev

MildBill

Member

Renate

Recognized Contributor / Inactive Recognized Dev

MildBill

Member

Renate

Recognized Contributor / Inactive Recognized Dev

MildBill

Member

Renate

Recognized Contributor / Inactive Recognized Dev

MildBill

Member

Similar threads

New posts