FORUMS

I/O Summary: How Android M Handles Power And Charging

In the spirit of improving the core Android experience, Google is changing Android … more

I/O Summary: Google Photos App

At I/O 2015, Google tackled the information problem in mobile once more, this time through … more

I/O Summary: Development, Play Store, The Next Billion

VP of Engineering Jen Fitzpatrick began talking about what Google is doing to … more

I/O Summary: Google Now on Tap

Google is all about organizing the world’s information to make it universally useful, and these … more

[Q] Hopefully simple Nook Touch question...

Thanks Meter: 3
 
By MildBill, Junior Member on 13th April 2014, 06:10 AM
Post Reply Subscribe to Thread Email Thread
12th May 2014, 07:18 PM |#11  
Renate NST's Avatar
Recognized Contributor / Recognized Developer
Boston
Thanks Meter: 860
 
More
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.
 
 
12th May 2014, 11:01 PM |#12  
OP Junior Member
Thanks Meter: 3
 
More
Quote:
Originally Posted by Renate NST

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.
12th May 2014, 11:12 PM |#13  
Renate NST's Avatar
Recognized Contributor / Recognized Developer
Boston
Thanks Meter: 860
 
More
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.
13th May 2014, 06:53 PM |#14  
OP Junior Member
Thanks Meter: 3
 
More
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.
Last edited by MildBill; 13th May 2014 at 06:55 PM.
13th May 2014, 07:15 PM |#15  
Renate NST's Avatar
Recognized Contributor / Recognized Developer
Boston
Thanks Meter: 860
 
More
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.
14th May 2014, 07:07 AM |#16  
OP Junior Member
Thanks Meter: 3
 
More
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
Last edited by MildBill; 14th May 2014 at 07:13 AM.
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Top Threads in Nook Touch General by ThreadRank