Hello everyone (first post).
Have been using the HD for a week now, no serious issues, but one thing does bug me.
I cannot get any option to permanently stick as a default input (during power off or soft reset), apart from the plain vanilla builtin keyboard. I tried with Resco, SPB, no luck.
Furthermore, even if I select say SPB keyboard in the "Input" of settings, it gets ignored - I can only change options in the soft-keys row (where the keyboard icon is). Even disabling the default keyboard in the registry (IsSIPdefault or something alike) doesn't prevent it from being selected as a default after power on. Grrr.
Any ideas / suggestions would be very welcome. Thanks.
Cheers,
Rok
Doesn't seem to be an easy answer. I have been having the same issue with TouchPal and so put SipChange into my startup menu. It does the job and changes the SIP but throws an error on every reboot, even when I have set the interval in SipChange settings to the maximum possible.
So try SipChange but be prepared for an error...still works though
Two questions about gyrator:
1. Can you configure it to disable completely while the keyboard is open? If so, how?
2. How do you add applications (the list is fixed and the .ini file does not include paths)? I have several games (Experiment 13 for example) that get hosed up if you repeatedly rotate the screen.
hi, if you want to disable any app, just go to the event panel add a new one and then:
>Name it the way you want
>Select the app (Learn Class/Title, pull the stylus out, lauch your app and put the stylus back)
>Select the orientation you want it to be fixed in
>Don't check any stylus options
>Check Rotate screen on the actions panel
>Don't bother with the last panel
Apply and then check "Orientation" for the event (it'll be marked as 1 on the right)
Apply, you're done.
I never tried to disable the keyboard rotation.
Thank you SSh_Shama.
I wasn't concerned about the keyboard, but I wanted to disable other programs (mainly the dialer) from rotating. Gyrator is an excellent application, but I just couldn't understand how to get the events to work. Your explaination made more sense to me. Thanks again.
I've seen miscellaneous info around on the common task of repurposing the "n" button. I'd like to see a concise rundown of ways to hack it.
The "n" button is a scancode 102 that normally gets mapped to keycode 3 with /system/usr/keylayout/gpio-keys.kl
Keycode 3 in intercepted by the interceptKeyTi method of PhoneWindowManager in /system/framework/android.policy.jar
Keycode 3 is handled directly without using any intents.
It's not easy to hack a key to give an intent. You have CALL_BUTTTON, CAMERA_BUTTON & MEDIA_BUTTON. I haven't managed to catch them. The easy one to hack is SEARCH_LONG_PRESS.
You can easily change gpio-keys.kl to key 102 SEARCH
A normal press will bring up the default Nook search. A long press will generate an intent. All you have to do is insert another intent filter in your favorite app.
Code:
<intent-filter>
<action android:name="android.intent.action.SEARCH_LONG_PRESS" />
<category android:name="android.intent.category.DEFAULT" />
</intent-filter>
I have this running on my ADW Launcher and I uninstalled Button Savior.
Personally, I prefer hacking to installing yet another app just to do one thing. I would like to come up with a solution for a dedicated action for the "n" key.
Any thoughts?
If you use NookTouchTools this allows you to remap the buttons/quicknav etc without all the hassle.
GabrialDestruir said:
... without all the hassle.
Click to expand...
Click to collapse
Well, I'd really like to learn things, not just load another app.
So how exactly do the Tools work? Do they need to have another process just to listen for a keycode and translate it to an intent?
Renate NST said:
Well, I'd really like to learn things, not just load another app.
So how exactly do the Tools work? Do they need to have another process just to listen for a keycode and translate it to an intent?
Click to expand...
Click to collapse
It uses modification of various .jar files
XorZone said:
* Patched android.policy.jar:
*** Injected home button code from AOSP, with configuration check between goto home and b&n quicknav toggle
*** Fixed recent apps dialog with configuration check to launch recent apps dialog or configured app launch
* Patched services.jar
*** "Reading now" button check for configured launch value (possible values: Home, Back, Menu, Search, Long Search, Custom App, B&N default)
*** All quicknav buttons configurable and will load icons (once, onCreate) possible values same as above.
* ActivityPicker - B&N removed default activity (usually in Settings.apk) to serve ACTION_PICK_ACTIVITY requests, so I added it back to the app and now able to add shortcuts/edit doc shortcuts in Launcher Pro...
* Configuration - All above configurable values stored in Settings.System so both system jars and Conf app can access it.
* Clear dalvik-cache button
Click to expand...
Click to collapse
Thanks, Gabrial. I had read through this entire thread before and it had left me confused. 10 pages of talking about changing the UI and not a single screenshot? I'm still not sure how an activity picker or a recent apps dialog looks like. Heck, I'm not even sure what additional things you get in Settings. Is there even a tree list of what people should have?
Yes, I do have a penchant for doing things the hard way. I like things lean and mean. If I knew how to inject code into jars I would just have fixed android.policy.jar and left it at that. My main need was a way to globally get back to my launcher desktop without onscreen controls (like Button Savior).
Renate NST said:
Thanks, Gabrial. I had read through this entire thread before and it had left me confused. 10 pages of talking about changing the UI and not a single screenshot? I'm still not sure how an activity picker or a recent apps dialog looks like. Heck, I'm not even sure what additional things you get in Settings. Is there even a tree list of what people should have?
Yes, I do have a penchant for doing things the hard way. I like things lean and mean. If I knew how to inject code into jars I would just have fixed android.policy.jar and left it at that. My main need was a way to globally get back to my launcher desktop without onscreen controls (like Button Savior).
Click to expand...
Click to collapse
Well said
I'd try to ask Nook Color forums too...
Well, I finally learned how to hack compiled Java code.
Now, I've got a simple press the "n" and it goes directly to your desktop.
It required just a bit of editing of android.policy.jar
Why would anyone want "QuickNav"?
It's not part of Android anywhere, it's just something B&N put in.
Sometimes I use library...
brendan10211 said:
Sometimes I use library...
Click to expand...
Click to collapse
You can drag the stock Library icon onto your desktop.
You can even put the stock Home or Shop there also.
I also use it to force refresh, but XorZone just made that soo
Renate NST said:
Well, I finally learned how to hack compiled Java code.
Now, I've got a simple press the "n" and it goes directly to your desktop.
It required just a bit of editing of android.policy.jar
Why would anyone want "QuickNav"?
It's not part of Android anywhere, it's just something B&N put in.
Click to expand...
Click to collapse
Hi,
I, same as you, like to modify my Nook as little as possible. In case of a future software upgrade, I would like to know what to change back before applying it.
Of course, I know I can just save the partitions (internal disk) and restore it as needed, but I would like to not need to do this.
Right now, I modified the gpio file for Search and created my own Launcher (base on Home Sample code in Android SDK).
Still, I don't like the need for Long Press on Search.
Could you please post the links which shows how to hack the android.policy.jar?
Maybe, if I don't ask too much, your edits to it?
Thanks!
Renate NST said:
[...] Why would anyone want "QuickNav"?
It's not part of Android anywhere, it's just something B&N put in.
Click to expand...
Click to collapse
Mainly because I don't like every device looking like an iPhone wannabe with a grid of icons. I like the reader focus with apps secondary. I do wish the QuickNav could be fully customized, including icons, easily.
bobstro said:
Mainly because I don't like every device looking like an iPhone wannabe with a grid of icons.
Click to expand...
Click to collapse
Mmm, Ok. Still, I don't like having to do three taps to do a non-book activity.
"n", then [launcher select] gets me anywhere.
The "currently reading" icon gets me back to my book.
I'm not fond of icons at all and have considered a list-oriented launcher,
but the fact remains that visually locking onto an icon is quicker.
That's why the QuickNav has icons on it.
Renate NST said:
Mmm, Ok. Still, I don't like having to do three taps to do a non-book activity.
Click to expand...
Click to collapse
There are only a few apps I use regularly on the NST, so I've just remapped the QuickNav buttons using Xor's NookTouch Tools to launch them directly: Library, maildroid, astrid tasks, calendar pad and dropsync. I find it quicker than pulling up a full launcher.
It's definitely a personal preference thing. I rather like that the NST isn't trying to be an iDevice. There's a minimalist 'Zen' to it I like.
I know you don't like additional software, but you can take it a step further using Folder Organizer. I set it to show items in the Notification menu, then show the "Starred items" and "Applications" menus in the Notification menu. You can launch apps and submenus this way, and also shortcuts, which can be handy to have 2 clicks away.
"n", then [launcher select] gets me anywhere.
The "currently reading" icon gets me back to my book.
Click to expand...
Click to collapse
For me, it's:
"n" then run my top 5 most often used apps directly from QuickNav (2 taps)
or tap Notification->app for regularly used (still 2 taps)
or at worst, Notification->Menu->app for stuff I don't use regularly (3 taps)
This give me progressively more focused listof apps. At no point do I have to go through a launcher, thus avoiding the dreaded iPhone-wannabe look. I never use a launcher except for maintenance tasks.
I'm not fond of icons at all and have considered a list-oriented launcher, but the fact remains that visually locking onto an icon is quicker. That's why the QuickNav has icons on it.
Click to expand...
Click to collapse
Folder Organizer does essentially what you've described. You can change the folder display to show:
icons with text
icons only
list with icon and text
list with text only.
I don't recall which features are available in the free version, but I like to toss a few bucks to developers when I can, so happily paid the few bucks for the full version.
Unfortunately, NookTouch Tools only allows you to set the 'n' key to show QuickNav or not. If it allowed setting it to launch a shortcut, you could pull up a nice targeted list of apps directly, thus bypassing the 5 item limit of QuickNav.
bobstro said:
Unfortunately, NookTouch Tools only allows you to set the 'n' key to show QuickNav or not.
Click to expand...
Click to collapse
Although I have no experience with any of the Tools, I presume that they
(like my mod) just generate an android.intent.category.HOME/android.intent.action.MAIN
Most "home-based" apps should already have this as a filtered intent.
You should be able to easily select one of them as the default.
Using specific "shortcuts" defeats the purpose of the Android intents system.
Renate NST said:
[...] Using specific "shortcuts" defeats the purpose of the Android intents system.
Click to expand...
Click to collapse
Does it have to be one or the other exclusively? For a basic launcher, pulling up the main app is sufficient. Other programs, such as Folder Organizer, provide shortcuts to user-defined categories, so I could have a subset of all available apps appear rather than a full launcher. Various readers provide shortcuts to books, and so on. Sometimes you don't want/need the full program.
Looks like they have the new Nook 1.1.5 OSS released: http://images.barnesandnoble.com/PResources/download/Nook/source-code/nook2_1-1-5.tgz
The "n" button is used turn the light on and off I think with long presses.
I pre-ordered mine already so will see when it arrives how it works.
I'm running Fattire's ICS, been running it for months and months now without problems. Today, Swiftkey updated itself and now I get this message non-stop about an Asian app having stopped. I'm pretty sure it's one of the Asian language apps because there are several shown in the Settings > Language & Input control panel. I uninstalled SwiftKey and rebooted, but that didn't fix the problem.
When I am in the Language & Input settings menu, I have the following:
- Android Keyboard (Checked and grayed out)
- Japanese IME (Checked and grayed out)
- [Asian characters I can't type here] (Checked and grayed out)
How do I fix this?! Can I use Root Explorer to remove whatever apk is having the issue? I don't need any asian languages, can I remove them with Root Explorer?
911jason said:
I'm running Fattire's ICS, been running it for months and months now without problems. Today, Swiftkey updated itself and now I get this message non-stop about an Asian app having stopped. I'm pretty sure it's one of the Asian language apps because there are several shown in the Settings > Language & Input control panel. I uninstalled SwiftKey and rebooted, but that didn't fix the problem.
When I am in the Language & Input settings menu, I have the following:
- Android Keyboard (Checked and grayed out)
- Japanese IME (Checked and grayed out)
- [Asian characters I can't type here] (Checked and grayed out)
How do I fix this?! Can I use Root Explorer to remove whatever apk is having the issue? I don't need any asian languages, can I remove them with Root Explorer?
Click to expand...
Click to collapse
It is best to just disable them in settings. Go to settings, apps, all, and look for them. One has the Asian characters and I don't remember the other one. Just open in settings and chose disable. You can always re-enable them later if you want.
Edit: the second Japanese app is OpenWnn.
Sent from my Nook Color running ICS and Tapatalk
See following post for workaround
I tracked down an old version of the app (2.6.2--extracted from one of the nooter project file zips) and installed it on my NST, hoping to create a simple date-day widget.
I must be daft. I cannot get a widget to display! I can go through the entire creation and customization process. I can "see" the preview result while in the settings section. But nothing appears on the home screen
I tried installing the same app on my little KitKat device and had no issues with the widget appearing on the home screen. This version of the app was surely known to work with the NST or else it would not have been included in the nooter package.
Does anyone have any experience with Minimalistic Test on the NST? I must be missing something. I have no problem adding other widgets.
Workaround
Whew! It's too bad there wasn't any chatter on the forum about working with this app. Maybe something in the newer NST firmwares just makes it mad, but whatever may be the case, here's what I did:
The last version for Eclair is 2.6.3. You can get it straight from the developer here: http://devmil.de/MT/MinimalisticText_2_6_3.apk
I did this on a system running FW 1.2.2 but I'm pretty sure this will apply to 1.2.1 also. Installation goes OK but apparently the file minimaltextprefs*.xml in /data/data/de.devmil.minimalitext/shared_pref is malformed in some way. Things just don't behave the way they should. While I floundered about I ended up installing the app on my little KitKat media player and then copied the minimaltextprefs*.xml file from that device and used it to replace the one on the NST. Voila! There is a number at the end of the file name and you can make the replacement file the same as the original file, but the number does change as you use the app. I have attached a zipped copy of the file I used below.
For me the best use of the widgets is with black text and no background. Unfortunately the opening settings screen of the app is black.... So if you use black text (the default is white) you will see nothing except a box for your widget. However, within the customization section there is a preview pane which lets you see what you've got.
One last--and the most important--thing. Supposedly when you've made changes the "back" button saves these. Not on the NST. Instead, while in the settings section (anywhere except the customization preview pane) if you tap the "menu" button one of the options that pops up at the bottom of the screen is "OK". That is how you save your changes. Using the "save" command at the end of the settings just places things in a file for later reference.
All this for a date-month-day text widget...... But you can do a lot more with the app, so maybe someday.
I want to thank @Devmil for providing the direct link to v. 2.6.3 and also for having patience with me while I tried to figure all this out.