Database Develop

Are there any available STK.apk for Nexus One?

I need Sim Tookit to manager my SIM card, but Nexus One doesn't have one.
I've seen thread 618491(I can't post links), the STK_2.1.apk in which can't be installed(INSTALL_FAILED_UPDATE_INCOMPATIBLE).
Are there any Solutions now?

I was looking for that too...did not find anything useable, only thing I read is that an update for Nexus One will fix this soon

I've done.
I've solved it.
Download STK.zip, unzip it. Put Stk.apk into /system/app/ of one ROM package, and then SIGN it, then flash it. After reboot you will see SIM Tookit in your menu of Nexus One.
I've tried it with CM 5.0 beta3 and it works well.
------
I'm sorry for my poor English...

li129667 said:
I've solved it.
Download STK.zip, unzip it. Put Stk.apk into /system/app/ of one ROM package, and then SIGN it, then flash it. After reboot you will see SIM Tookit in your menu of Nexus One.
I've tried it with CM 5.0 beta3 and it works well.
------
I'm sorry for my poor English...
Click to expand...
Click to collapse
Cant you just adb push it?

setzer715 said:
Cant you just adb push it?
Click to expand...
Click to collapse
It does work by adb pushing it. Just tried.

li129667 said:
I've solved it.
Download STK.zip, unzip it. Put Stk.apk into /system/app/ of one ROM package, and then SIGN it, then flash it. After reboot you will see SIM Tookit in your menu of Nexus One.
I've tried it with CM 5.0 beta3 and it works well.
------
I'm sorry for my poor English...
Click to expand...
Click to collapse
how to sign stk.apk?

Sim toolkit for android 2.1 might not be ready yet? The install seems fine, and the icon is there in the launcher, but when I receive a sim message it fails:
Code:
I/ActivityManager( 89): Starting activity: Intent { flg=0x58840000 cmp=com.android.stk/.StkDialogActivity (has extras) }
I/ActivityManager( 89): Displayed activity com.android.stk/.StkDialogActivity: 379 ms (total 379 ms)
I/ActivityManager( 89): Starting activity: Intent { act=android.intent.action.VIEW flg=0x10040000 cmp=com.android.stk/.StkInputActivity (has extras)
}
D/dalvikvm( 145): DexOpt: couldn't find field Lcom/android/internal/telephony/gsm/stk/Input;.iconSelfExplanatory
W/dalvikvm( 145): VFY: unable to resolve instance field 32
D/dalvikvm( 145): VFY: replacing opcode 0x55 at 0x004d
D/dalvikvm( 145): Making a copy of Lcom/android/stk/StkInputActivity;.configInputDisplay code (456 bytes)
D/AndroidRuntime( 145): Shutting down VM
W/dalvikvm( 145): threadid=3: thread exiting with uncaught exception (group=0x4001b170)
E/AndroidRuntime( 145): Uncaught handler: thread main exiting due to uncaught exception
E/AndroidRuntime( 145): java.lang.NoSuchFieldError: com.android.internal.telephony.gsm.stk.Input.iconSelfExplanatory
E/AndroidRuntime( 145): at com.android.stk.StkInputActivity.configInputDisplay(StkInputActivity.java:291)
E/AndroidRuntime( 145): at com.android.stk.StkInputActivity.onCreate(StkInputActivity.java:148)
E/AndroidRuntime( 145): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047)
E/AndroidRuntime( 145): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2459)
E/AndroidRuntime( 145): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2512)
E/AndroidRuntime( 145): at android.app.ActivityThread.access$2200(ActivityThread.java:119)
E/AndroidRuntime( 145): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1863)
E/AndroidRuntime( 145): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 145): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 145): at android.app.ActivityThread.main(ActivityThread.java:4363)
E/AndroidRuntime( 145): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 145): at java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime( 145): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
E/AndroidRuntime( 145): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
E/AndroidRuntime( 145): at dalvik.system.NativeStart.main(Native Method)
I/Process ( 89): Sending signal. PID: 145 SIG: 3
I/dalvikvm( 145): threadid=7: reacting to signal 3

It's working fine for me,
However, I do get some odd carrier specific popups every once in a while welcoming me back although I wasn't roaming
I can access the menu and check my credit and billing stuff

install Zip to nexus one
Hello li129667
I'm not familiar with the install process of this zip, can u further eloborate on it? Am I just dragging the whole thing into /system/app/ and click on stk.apk file?
--------------------
Originally Posted by li129667
I've solved it.
Download STK.zip, unzip it. Put Stk.apk into /system/app/ of one ROM package, and then SIGN it, then flash it. After reboot you will see SIM Tookit in your menu of Nexus One.
I've tried it with CM 5.0 beta3 and it works well.
------
I'm sorry for my poor English...

I need STk(Sim Tookit) to manager my SIM card.
Anyone can help?

Hello!!!
How can install this stk in my nexus one?
I'm newbie in android.
Thanks in advance

I tried to push it to /system/app and restarted, it doesn't show up in the apps drawer.
I went to Astro file manager and found it in /system/app and i tapped it and chose install but it fails and says application not installed... what am I doing wrong?

To adb push it you would go to the folder you downloaded it, right click the folder and select open command prompt here. Assuming you have set up adb already. In command prompt you would type.
Adb remount
Adb push STK.apk /system/app
Then you would use andexplorer or filemanager of your choice to navigate to the /system/app folder and find the STK.apk there and click it, install, done.
If you dont know if you can use adb then you can't. You can read more about adb by searching or on googles d.android.com

I did that, but it wont install.
C:\android-sdk-windows\root & rom\nexus one>adb install Stk.apk
771 KB/s (67151 bytes in 0.085s)
pkg: /data/local/tmp/Stk.apk
Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE]
Click to expand...
Click to collapse

Same issue with me, with latest (Update1) of 2.1 sofware. I tried stk21.apk , but still claims uncompatibility.

adb push STK.apk /system/app

did it
installed
but were can I get to the sim menu ?

How do you access the toolkit after installation

I've made an update.zip to install STK.apk. Works fine on Cyan's roms.

Any way to make this work with Enom's The Official 1.7.1 ROM?
Thanks in advance.

Wireless AP from other rom

Well,
I tried to grab the APK. which i will include here.
When i tried to install i did a logcat.
I/ActivityManager( 2265): Displayed activity com.android.packageinstaller/.InstallAppProgress: 317 ms (total 317 ms)
D/PackageParser( 2265): Scanning package: /data/app/vmdl48205.tmp
E/PackageManager( 2265): Package com.sec.android.app.mobileap requires unavailable shared library mobileap; failing!
W/PackageManager( 2265): Package couldn't be installed in /data/app/com.sec.android.app.mobileap.apk
D/dalvikvm( 2265): GC freed 10672 objects / 640424 bytes in 80ms
W/PowerManagerService( 2265): Timer 0x7->0x3|0x0
I/PowerManagerService( 2265): ULight 7->3 f0
I/AudioHardwareALSA( 2207): Output standby called!!. Turn off PCM device.
D/dalvikvm( 2726): GC freed 1324 objects / 89824 bytes in 106ms
D/Cursor ( 2726):
D/Cursor ( 2726): Database path: /data/data/com.noshufou.android.su/databases/permissions.sqlite
D/Cursor ( 2726):
D/Cursor ( 2726): Table name : permissions
D/Cursor ( 2726):
D/Cursor ( 2726): SQL : SQLiteQuery: SELECT _id, allow FROM permissions WHERE from_uid=? AND exec_uid=? AND exec_command=?
I/dalvikvm( 2726): Uncaught exception thrown by finalizer (will be discarded):
I/dalvikvm( 2726): Ljava/lang/IllegalStateException;: Finalizing cursor [email protected] on permissions that has not been deactivated or closed
I/dalvikvm( 2726): at android.database.sqlite.SQLiteCursor.finalize(SQLiteCursor.java:610)
I/dalvikvm( 2726): at dalvik.system.NativeStart.run(Native Method)
D/Cursor ( 2726):
D/Cursor ( 2726): Database path: /data/data/com.noshufou.android.su/databases/permissions.sqlite
D/Cursor ( 2726):
D/Cursor ( 2726): Table name : permissions
D/Cursor ( 2726):
D/Cursor ( 2726): SQL : SQLiteQuery: SELECT _id, allow FROM permissions WHERE from_uid=? AND exec_uid=? AND exec_command=?
I/dalvikvm( 2726): Uncaught exception thrown by finalizer (will be discarded):
I/dalvikvm( 2726): Ljava/lang/IllegalStateException;: Finalizing cursor [email protected] on permissions that has not been deactivated or closed
I/dalvikvm( 2726): at android.database.sqlite.SQLiteCursor.finalize(SQLiteCursor.java:610)
I/dalvikvm( 2726): at dalvik.system.NativeStart.run(Native Method)
E/Database( 2726): Leak found
E/Database( 2726): java.lang.IllegalStateException: /data/data/com.noshufou.android.su/databases/permissions.sqlite SQLiteDatabase created and never closed
E/Database( 2726): at android.database.sqlite.SQLiteDatabase.<init>(SQLiteDatabase.java:1705)
E/Database( 2726): at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:739)
E/Database( 2726): at android.database.sqlite.SQLiteDatabase.openOrCreateDatabase(SQLiteDatabase.java:771)
E/Database( 2726): at android.database.sqlite.SQLiteDatabase.openOrCreateDatabase(SQLiteDatabase.java:764)
E/Database( 2726): at android.app.ApplicationContext.openOrCreateDatabase(ApplicationContext.java:535)
E/Database( 2726): at android.content.ContextWrapper.openOrCreateDatabase(ContextWrapper.java:193)
E/Database( 2726): at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:98)
E/Database( 2726): at com.noshufou.android.su.DBHelper.<init>(DBHelper.java:28)
E/Database( 2726): at com.noshufou.android.su.SuRequest.onCreate(SuRequest.java:48)
E/Database( 2726): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047)
E/Database( 2726): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2459)
E/Database( 2726): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2512)
E/Database( 2726): at android.app.ActivityThread.access$2200(ActivityThread.java:119)
E/Database( 2726): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1863)
E/Database( 2726): at android.os.Handler.dispatchMessage(Handler.java:99)
E/Database( 2726): at android.os.Looper.loop(Looper.java:123)
E/Database( 2726): at android.app.ActivityThread.main(ActivityThread.java:4363)
E/Database( 2726): at java.lang.reflect.Method.invokeNative(Native Method)
E/Database( 2726): at java.lang.reflect.Method.invoke(Method.java:521)
E/Database( 2726): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:862)
E/Database( 2726): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:620)
E/Database( 2726): at dalvik.system.NativeStart.main(Native Method)
I/DumpStateReceiver( 2265): Added state dump to 1 crashes
D/PowerManagerService( 2265): lightSensorChangedLocked 5000

More info:
D/PackageParser( 2265): Scanning package: /data/app/vmdl48206.tmp
E/PackageManager( 2265): Package com.sec.android.app.mobileap requires unavailable shared library mobileap; failing!
W/PackageManager( 2265): Package couldn't be installed in /data/app/com.sec.android.app.mobileap.apk

Bump. You guys are all crying. and here is the app. If someone wants to get it to work.

stupid question, is this already deodexed?

Arr MiHardies said:
stupid question, is this already deodexed?
Click to expand...
Click to collapse
Sadly no. I really hope that somebody can deodex this and that it will work. This would be a major step forward for Vibrant...

I just need the data section of an intl galaxy and i can try
Sent from my SGH-T959 using XDA App

marsupial99 said:
Sadly no. I really hope that somebody can deodex this and that it will work. This would be a major step forward for Vibrant...
Click to expand...
Click to collapse
just download the modaco custom rom r2, all the apps are deodexed including Mobile AP

rhcp0112345 said:
More info:
D/PackageParser( 2265): Scanning package: /data/app/vmdl48206.tmp
E/PackageManager( 2265): Package com.sec.android.app.mobileap requires unavailable shared library mobileap; failing!
W/PackageManager( 2265): Package couldn't be installed in /data/app/com.sec.android.app.mobileap.apk
Click to expand...
Click to collapse
Okay, I downloaded the modaco rom and pulled out the MobileAP.apk from it. I've attached it. Supposedly this is deodexed - notice the size differences as compared to the original. I also found libmobileap.jar in /system/framework and I attached it too - had to append .zip extension so that I could attach it (.jar are not allowed on xda) so just strip it. Maybe that is the missing shared library referred to in the error you posted above. I suspect it would have to be copied to /system/framework before installing MobileAP.apk although I don't really have an understanding how this works. Anybody...?

marsupial99 said:
Okay, I downloaded the modaco rom and pulled out the MobileAP.apk from it. I've attached it. Supposedly this is deodexed - notice the size differences as compared to the original. I also found libmobileap.jar in /system/framework and I attached it too - had to append .zip extension so that I could attach it (.jar are not allowed on xda) so just strip it. Maybe that is the missing shared library referred to in the error you posted above. I suspect it would have to be copied to /system/framework before installing MobileAP.apk although I don't really have an understanding how this works. Anybody...?
Click to expand...
Click to collapse
If anybody can shed some clear light on this, I'd be happy to be a Vibrant Guinea Pig today.
I'll be online all day trolling the forums as usual.
Thanks XDA peeps!

Going to give it a try now.

Sadly, it does not work. I get application not installed. Haven't tried installing it through adb though, though I doubt it will make any difference.
Perhaps the apk needs to be resigned?
Can you check the libs directory and make sure we don't need anything in there as well?
Sent from my SGH-T959 using XDA App

Code:
Failure INSTALL_PARSE_FAILED_NO_CERTIFICATES
Logcat says
Code:
Package.com.sec.android.app.mobleap has no certificates at entry classes.dex; ignoring!

Looks like a signing issue... I'll try signing it in a few.
Sent from my SGH-T959 using XDA App

Arr MiHardies said:
Looks like a signing issue... I'll try signing it in a few.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
It's complaining about the jar, right?
I know absolutely nothing about java code signing.

Just tried resigning it... now the error I'm getting when doing adb install is
Failure [INSTALL_PARSE_FAILED_UNEXPECTED_EXCEPTION]
...
Im going to check the permissions

Just tried resigning it... now the error I'm getting when doing adb install is
Failure [INSTALL_PARSE_FAILED_UNEXPECTED_EXCEPTION]
...
Im going to check the permissions.....
Nope.. correcting the permissions did not help any....

I am signing them now
Though i was trying to go the stock route by not using other peoples roms. I have a feeling we will run into the same error.
Needing that /data/ file. But lets see.
rhcps-macbookpro41-2ther rhcp$ java -Xmx999m -jar signapk.jar -w testkey.x509.pem testkey.pk8 MobileAP.apk
java.lang.ArrayIndexOutOfBoundsException: 4
at com.android.signapk.SignApk.main(SignApk.java:480)
rhcps-macbookpro41-2ther rhcp$ java -Xmx999m -jar signapk.jar -w testkey.x509.pem testkey.pk8 libmobileap.jar
java.lang.ArrayIndexOutOfBoundsException: 4
at com.android.signapk.SignApk.main(SignApk.java:480)
Got errors on signing. But you may test.

For some reason,i cannot download that apk directly to my phone. Never had that problem before....
I didn't get any errors when I tried signing the file earlier though.
Sent from my SGH-T959 using XDA App

Arr MiHardies said:
For some reason,i cannot download that apk directly to my phone. Never had that problem before....
I didn't get any errors when I tried signing the file earlier though.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Post the signed files here.
You just adb push them. then install it with astro or some other file manager.

No, I was trying to download from my vibrants browser. something I havent had an issue with before.
The attached zip contains a both the signed apk and signed jar

[Q] Little help with launcher

Hi to all! I'm writing here now because i have a problem with a launcher that i would to replace with the stock... Let me explain.
I'm editing a ROM and i would to replace the twlauncher with MX Home so i have delete tw from system/app and i have insert here the new launcher. And here the problem. At first boot after the flash of the ROM it has a force close! How can I fix?
Thx

many applications do this "trick" if put in system/app... I am also looking for a solution but I think it's necessary to recompile the app for it to work on our Galaxy S.
However I'm interested too

sgsever said:
Hi to all! I'm writing here now because i have a problem with a launcher that i would to replace with the stock... Let me explain.
I'm editing a ROM and i would to replace the twlauncher with MX Home so i have delete tw from system/app and i have insert here the new launcher. And here the problem. At first boot after the flash of the ROM it has a force close! How can I fix?
Thx
Click to expand...
Click to collapse
Instead of just guessing what the problem might be, look at the logs. It may help you more.

And where is the log? Because when I boot up the phone is stuck at the force close because the "stock launcher" don't work... Help me

Can you get a shell into the phone using adb shell?

xxbeanxx said:
Can you get a shell into the phone using adb shell?
Click to expand...
Click to collapse
Perhaps yes but I have Linux... But I've come up with an idea. I don't know if it will work. If I boot up the phone, wait the FC and after I will go in recovery and mounting the internal SD i take the log? It is a good idea?

sgsever said:
Perhaps yes but I have Linux... But I've come up with an idea. I don't know if it will work. If I boot up the phone, wait the FC and after I will go in recovery and mounting the internal SD i take the log? It is a good idea?
Click to expand...
Click to collapse
The log file is not stored on the internal SD. Also I don't think it persists a reboot (I may be wrong about this).
What does having Linux have to do with anything? There is a Linux SDK available from Google.

xxbeanxx said:
The log file is not stored on the internal SD. Also I don't think it persists a reboot (I may be wrong about this).
What does having Linux have to do with anything? There is a Linux SDK available from Google.
Click to expand...
Click to collapse
Perhaps I have the log:
Code:
W/dalvikvm( 8000): Exception Ljava/lang/UnsatisfiedLinkError; thrown while initializing Lcom/neomtel/mxhome/SmaxInterface;
D/AndroidRuntime( 8000): Shutting down VM
W/dalvikvm( 8000): threadid=1: thread exiting with uncaught exception (group=0x40015578)
E/AndroidRuntime( 8000): FATAL EXCEPTION: main
E/AndroidRuntime( 8000): java.lang.ExceptionInInitializerError
E/AndroidRuntime( 8000): at com.neomtel.mxhome.SmaxView.init(SmaxView.java:169)
E/AndroidRuntime( 8000): at com.neomtel.mxhome.SmaxView.<init>(SmaxView.java:88)
E/AndroidRuntime( 8000): at com.neomtel.mxhome.Launcher.setupViews(Launcher.java:1559)
E/AndroidRuntime( 8000): at com.neomtel.mxhome.Launcher.onCreate(Launcher.java:379)
E/AndroidRuntime( 8000): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047)
E/AndroidRuntime( 8000): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1615)
E/AndroidRuntime( 8000): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1667)
E/AndroidRuntime( 8000): at android.app.ActivityThread.access$1500(ActivityThread.java:117)
E/AndroidRuntime( 8000): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:935)
E/AndroidRuntime( 8000): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 8000): at android.os.Looper.loop(Looper.java:130)
E/AndroidRuntime( 8000): at android.app.ActivityThread.main(ActivityThread.java:3687)
E/AndroidRuntime( 8000): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 8000): at java.lang.reflect.Method.invoke(Method.java:507)
E/AndroidRuntime( 8000): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:842)
E/AndroidRuntime( 8000): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:600)
E/AndroidRuntime( 8000): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 8000): Caused by: java.lang.UnsatisfiedLinkError: Couldn't load SmaxEngine: findLibrary returned null
E/AndroidRuntime( 8000): at java.lang.Runtime.loadLibrary(Runtime.java:429)
E/AndroidRuntime( 8000): at java.lang.System.loadLibrary(System.java:554)
E/AndroidRuntime( 8000): at com.neomtel.mxhome.SmaxInterface.<clinit>(SmaxInterface.java:99)
E/AndroidRuntime( 8000): ... 17 more
W/ActivityManager( 2736): Force finishing activity com.neomtel.mxhome/.Launcher
E/ ( 2736): Dumpstate > /data/log/dumpstate_app_error
I/dumpstate( 8009): begin
D/PowerManagerService( 2736): onSensorChanged: light value: 1000
W/ActivityManager( 2736): Activity pause timeout for HistoryRecord{40882a00 com.neomtel.mxhome/.Launcher}
W/su ( 8027): request rejected (0->0 /system/bin/sh)
W/PowerManagerService( 2736): Timer 0x7->0x3|0x0
I/PowerManagerService( 2736): Ulight 7->3|0
D/LightsService( 2736): BUTTON : 0
D/VoldCmdListener( 85): asec list
I/dumpstate( 8009): done
D/UsbStorageActivity( 4556): onResume !!!
Let me know... and thx for your patience!

I believe the error stems from the incompatibility between the launcher and the framework...

And nobody know how to fix this?

sgsever said:
And nobody know how to fix this?
Click to expand...
Click to collapse
I don't have a solution but here's what I would try.. Without having the app you are talking about to look at I'm only guessing from the log.
A Java UnsatisfiedLinkError occurs when the VM is trying to load a libary that isn't available. It would seem that perhaps the apk contains some libraries that get extracted by the Android installer when you first install the app.
Try using a tool like 'apktool' to decode the apk into a format that you can actually look at, then see if there are such libraries inside. If so you would want to extract these and put them somewhere that Dalvik can read them, for instance /system/lib.
I may be way off the mark here, like I said this is just a guess. Maybe later if I get some time I'll grab the apk and try to do exactly what you're doing. I'll post back if I do.

Okay so I downloaded the launcher and had a look in the apk using root explorer and sure enough, found lib/armeabi/libSmaxEngine.so.
Try extracting that file and putting it in /system/lib. Root explorer gives me the option to extract the file, and I tried it on an xml file and got back a readable file, so that may be the easiest option for you. I think apktool would do it too but it's been a while since I used that.
If that doesn't work I'm sure there is a way to do it. I've never had this problem before so it's new to me.

Okay so I copied the apk to /system/app and copied the extracted .so to /system/lib (extracted it with root explorer).
I then uninstalled the downloaded version of mxhome and rebooted. It worked fine. No FCs.
Looks like that's your solution.

Problem changing resolution to 240dpi on VengeaneNote2 - RC Build 1.0 - MIUI 2.9.14

Hi
I'm posting this question here because I'm not allowed to post to the development thread (yet)
I installed the last version of VengeaneNote2 (RC Build 1.0 - MIUI 2.9.14) but after I changed the screen resolution to 240dpi, I started getting this exception when opening the dialer:
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.contacts/com.android.contacts.activities.TwelveKeyDialer}: android.view.InflateException: Binary XML file line #174: Error inflating class <unknown>
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2070)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2095)
at android.app.ActivityThread.access$600(ActivityThread.java:133)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1198)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4758)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:786)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
at dalvik.system.NativeStart.main(Native Method)
Caused by: android.view.InflateException: Binary XML file line #174: Error inflating class <unknown>
at android.view.LayoutInflater.createView(LayoutInflater.java:613)
at com.android.internal.policy.impl.PhoneLayoutInflater.onCreateView(PhoneLayoutInflater.java:56)
at android.view.LayoutInflater.onCreateView(LayoutInflater.java:660)
at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:685)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:746)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:749)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:749)
at android.view.LayoutInflater.inflate(LayoutInflater.java:489)
at android.view.LayoutInflater.inflate(LayoutInflater.java:396)
at android.view.LayoutInflater.inflate(LayoutInflater.java:352)
at com.android.internal.policy.impl.PhoneWindow.setContentView(PhoneWindow.java:258)
at android.app.Activity.setContentView(Activity.java:1873)
at com.android.contacts.activities.TwelveKeyDialer.onCreate(TwelveKeyDialer.java:528)
at android.app.Activity.performCreate(Activity.java:5014)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1079)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2034)
... 11 more
Caused by: java.lang.reflect.InvocationTargetException
at java.lang.reflect.Constructor.constructNative(Native Method)
at java.lang.reflect.Constructor.newInstance(Constructor.java:417)
at android.view.LayoutInflater.createView(LayoutInflater.java:587)
... 26 more
Caused by: android.content.res.Resources$NotFoundException: File res/drawable-hdpi/dialer_buttons.9.png from drawable resource ID #0x7f020046
at android.content.res.Resources.loadDrawable(Resources.java:1944)
at android.content.res.TypedArray.getDrawable(TypedArray.java:601)
at android.view.View.<init>(View.java:3339)
at android.view.View.<init>(View.java:3275)
... 29 more
Caused by: java.io.FileNotFoundException: res/drawable-hdpi/dialer_buttons.9.png
at android.content.res.AssetManager.openNonAssetNative(Native Method)
at android.content.res.AssetManager.openNonAsset(AssetManager.java:413)
at android.content.res.Resources.loadDrawable(Resources.java:1936)
... 32 more
I did it many times (full wipe and format /system between each), but still having the same problem.
This only new in this version. I was able to switch to 240dpi in all previous versions without problem.
Any help on this?
Thanks

update
yelkarama said:
Hi
I'm posting this question here because I'm not allowed to post to the development thread (yet)
I installed the last version of VengeaneNote2 (RC Build 1.0 - MIUI 2.9.14) but after I changed the screen resolution to 240dpi, I started getting this exception when opening the dialer:
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.contacts/com.android.contacts.activities.TwelveKeyDialer}: android.view.InflateException: Binary XML file line #174: Error inflating class <unknown>
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2070)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2095)
at android.app.ActivityThread.access$600(ActivityThread.java:133)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1198)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4758)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:786)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
at dalvik.system.NativeStart.main(Native Method)
Caused by: android.view.InflateException: Binary XML file line #174: Error inflating class <unknown>
at android.view.LayoutInflater.createView(LayoutInflater.java:613)
at com.android.internal.policy.impl.PhoneLayoutInflater.onCreateView(PhoneLayoutInflater.java:56)
at android.view.LayoutInflater.onCreateView(LayoutInflater.java:660)
at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:685)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:746)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:749)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:749)
at android.view.LayoutInflater.inflate(LayoutInflater.java:489)
at android.view.LayoutInflater.inflate(LayoutInflater.java:396)
at android.view.LayoutInflater.inflate(LayoutInflater.java:352)
at com.android.internal.policy.impl.PhoneWindow.setContentView(PhoneWindow.java:258)
at android.app.Activity.setContentView(Activity.java:1873)
at com.android.contacts.activities.TwelveKeyDialer.onCreate(TwelveKeyDialer.java:528)
at android.app.Activity.performCreate(Activity.java:5014)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1079)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2034)
... 11 more
Caused by: java.lang.reflect.InvocationTargetException
at java.lang.reflect.Constructor.constructNative(Native Method)
at java.lang.reflect.Constructor.newInstance(Constructor.java:417)
at android.view.LayoutInflater.createView(LayoutInflater.java:587)
... 26 more
Caused by: android.content.res.Resources$NotFoundException: File res/drawable-hdpi/dialer_buttons.9.png from drawable resource ID #0x7f020046
at android.content.res.Resources.loadDrawable(Resources.java:1944)
at android.content.res.TypedArray.getDrawable(TypedArray.java:601)
at android.view.View.<init>(View.java:3339)
at android.view.View.<init>(View.java:3275)
... 29 more
Caused by: java.io.FileNotFoundException: res/drawable-hdpi/dialer_buttons.9.png
at android.content.res.AssetManager.openNonAssetNative(Native Method)
at android.content.res.AssetManager.openNonAsset(AssetManager.java:413)
at android.content.res.Resources.loadDrawable(Resources.java:1936)
... 32 more
I did it many times (full wipe and format /system between each), but still having the same problem.
This only new in this version. I was able to switch to 240dpi in all previous versions without problem.
Any help on this?
Thanks
Click to expand...
Click to collapse
I changed the dpi to 280 and it's working!

update 2
yelkarama said:
Hi
I'm posting this question here because I'm not allowed to post to the development thread (yet)
I installed the last version of VengeaneNote2 (RC Build 1.0 - MIUI 2.9.14) but after I changed the screen resolution to 240dpi, I started getting this exception when opening the dialer:
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.contacts/com.android.contacts.activities.TwelveKeyDialer}: android.view.InflateException: Binary XML file line #174: Error inflating class <unknown>
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2070)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2095)
at android.app.ActivityThread.access$600(ActivityThread.java:133)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1198)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4758)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:786)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
at dalvik.system.NativeStart.main(Native Method)
Caused by: android.view.InflateException: Binary XML file line #174: Error inflating class <unknown>
at android.view.LayoutInflater.createView(LayoutInflater.java:613)
at com.android.internal.policy.impl.PhoneLayoutInflater.onCreateView(PhoneLayoutInflater.java:56)
at android.view.LayoutInflater.onCreateView(LayoutInflater.java:660)
at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:685)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:746)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:749)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:749)
at android.view.LayoutInflater.inflate(LayoutInflater.java:489)
at android.view.LayoutInflater.inflate(LayoutInflater.java:396)
at android.view.LayoutInflater.inflate(LayoutInflater.java:352)
at com.android.internal.policy.impl.PhoneWindow.setContentView(PhoneWindow.java:258)
at android.app.Activity.setContentView(Activity.java:1873)
at com.android.contacts.activities.TwelveKeyDialer.onCreate(TwelveKeyDialer.java:528)
at android.app.Activity.performCreate(Activity.java:5014)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1079)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2034)
... 11 more
Caused by: java.lang.reflect.InvocationTargetException
at java.lang.reflect.Constructor.constructNative(Native Method)
at java.lang.reflect.Constructor.newInstance(Constructor.java:417)
at android.view.LayoutInflater.createView(LayoutInflater.java:587)
... 26 more
Caused by: android.content.res.Resources$NotFoundException: File res/drawable-hdpi/dialer_buttons.9.png from drawable resource ID #0x7f020046
at android.content.res.Resources.loadDrawable(Resources.java:1944)
at android.content.res.TypedArray.getDrawable(TypedArray.java:601)
at android.view.View.<init>(View.java:3339)
at android.view.View.<init>(View.java:3275)
... 29 more
Caused by: java.io.FileNotFoundException: res/drawable-hdpi/dialer_buttons.9.png
at android.content.res.AssetManager.openNonAssetNative(Native Method)
at android.content.res.AssetManager.openNonAsset(AssetManager.java:413)
at android.content.res.Resources.loadDrawable(Resources.java:1936)
... 32 more
I did it many times (full wipe and format /system between each), but still having the same problem.
This only new in this version. I was able to switch to 240dpi in all previous versions without problem.
Any help on this?
Thanks
Click to expand...
Click to collapse
So I tried many resolutions. Each time I modify the line ro.sf.lcd_density= in /system/build.prop and I reboot.
Conclusion: The phone dialer works correctly for resolution more than 270. if I go beyondm it start FCing with the excption above.

[APP][NST/G] Nook Settings

Version for no-BN account devices in post #5
This version of the app is for fully registered devices.
5-14-22: Updated to v1.5. Uninstall any previous version to insure all variables clear.
--removed Google accounts section
--removed Network Location setting (relied on Google accounts).
Over the years a few new "Settings" apps have been cobbled together from the ruins of what B&N left on the device. Starting with the original listing by @Renate NST which revealed the scope of what was hidden on the NST/G, people have rejiggered the app in a number of ways. Each of those attempts relied on actually changing the app or the framework and had limitations as to the type of installation they would run on and things that needed to be added, deleted, disabled, etc.
The Nook Settings app is my effort to create a utility that would encompass all the good ideas and none of the less good. But as I am no Java programmer, that meant Tasker (surprise). The result is a frankenapp, using screens from the B&N Settings app (you can't delete it!) as well as completely original pages I assembled from screen images and many, many invisible overlays to hijack the Back button and the return arrow throughout the app. My goal was to eliminate anything that did not work (USB debugging in the Development section, for example), try to fix what I could (USB debugging, for example!), and add in features that just should be there, mundane things like wallpaper and keyboard changes. I also wanted to re-organize the app in a more traditional way. A few representative screenshots below.
Disclaimers
1. Transitions are sometimes a little scrappy. It all depends on what the device is doing in the background and how difficult the item is to access.
2. Rather than introduce a lot of forking with many permutations, I elected to only separate the NST from the NSTG at first run. As far as accounts go, I included everything from B&N: Shop, Social). There is error trapping, so there should be no issues.
3. My number one goal in herding all these electric sheep was to keep what happens in the Settings app within the Settings app. This proved to be impossible in a few cases (keyboard swap is one) because of the way the native Android system was handling the main window. Those cases are clearly indicated in the app menus as "Exits Settings".
4. This app cannot be totally localized. That is, if you have a different display language (say, German), the parts of the app that are actually parts of the B&N Settings app will be localized, i.e., the phrases will be changed to the language you have selected. However, the custom pages I created are just images with invisible touch overlays so.... If anyone is seriously interested in localizing the app for themselves, they should contact me and we can discuss creating a custom set of images which I will then compile into a custom app.
5. I'm sorry to say that the App Manager was one of most difficult nuts to crack. It is part of the B&N Settings app but has an activity that cannot be opened via shell commands. Somehow ADW Launcher does it, but I was never able to come up with a method. Luckily, Tasker has a generic call to the App Manager and it actually works. Still, it is sluggish on the Back arrow where it must be tested against which screen is being displayed. Just not a happy camper. Be sure not to tap the Back arrow more than once or you'll end up who knows where. Consider it a free lesson in patience
6. This app is only for Portrait orientation. Oh, you can rotate your screen, but all the touch coordinates will be off and images distorted. This is not a priority for me, but I may look at it someday. It requires a redesign and right now, I'm sorta sick of working on this :silly:
Requirements
1. This is a Tasker app and has a dependency on two library files which are part of a GApps installation. If you don't have GApps or one of my other Tasker apps already, you need to copy the two files in the zip as below:
/system/etc/permissions/com.google.android.maps.xml
/system/framework/com.google.android.maps.jar
Set permissions for both files to rw-r--r-- and reboot. Without these files resident, the app will not install.
2. Root/SU. Right off the bat. Many, many shell commands, settings.db, accounts.db, etc. manipulations.
3. Sqlite3 (for the database manipulations), provided in the zip below. If you don't already have it, move the file to /system/bin and set the permissions to rwx r-x r-x.
4. Busybox. If you rooted with NookManager, you already have Busybox installed. A few other special packages probably include it. If you have it, you will find it in /system/xbin. If it's not there, copy the file from the zip to that location and set permissions to rwx-rwx-rwx
5. The original B&N Settings app installed
Edit: 6. I've discovered while working on a no-B&N variant that a kernal enabling multi-touch is needed for some of the "sendevent" sequences to execute. Lacking multi-touch does not mean the app will not function or that you will not be able to access some settings.
Installation
The easy part. This is not a system app, but a user app. Just install as normal. You don't have to disable or remove or change anything. If you don't like it, just uninstall.
On first run the app:
1. determines if you have an NSTG and adjusts the menus accordingly.
2. sets ADB debugging via TCP (for WiFi apps like ADB Konnect); This is the default state for rooting with NookManager. You can change to USB in Developer options.
Just to be clear, in every case in which there is a "return" arrow as part of a Settings screen, its function is identical to the Back button in the status bar (i.e., both have been hijacked).
Problems
If you have some issue and end up crashing the app or exiting unexpectedly (has not happened to me, but.....), there may still be invisible overlays present that will impair the function of your device. The easiest way to deal with these is to repeatedly press the Back button until the main Settings menu appears and then disappears. If there is still an issue, force stopping the app via the App Manager will clear all overlays. A power cycle is the last resort.
Acknowledgement
Wow, this was tough... I'm indebted to the generous folk who hang out at the Google Tasker group. I'm sure they all think I'm daft spending so much time on an Eclair device with an ancient version of Tasker, but they have nonetheless been helpful when I've been stuck.

Wow, @nmyshkin that looks like a bit of work.
On a different theme, I have an Android (Linux) executable for doing settings.
It's handy if you want to set a bunch of devices all the same (and you have root).
Settings are stored in different tables for global, system and secure.
Even worse, individual setting moved among these three categories for different versions of Android.
Even worse, they used to be stored in an SQLite database, then they moved to separate XML files.
Fortunately, if there is a setting "klaatu_barada_nikto" it is unique even though it might be in system or secure depending on Android version.
The executable takes an input file of settings.
Here is an example (just what I had at hand, I'm not saying that these settings are the right one for you (or even me)).
Code:
adb_enabled 1
airplane_mode_on 0
auto_time_zone 0
bluetooth_on 0
development_settings_enabled 1
dim_screen 0
heads_up_notification_enabled 0
immersive_mode_confirmations confirmed
install_non_market_apps 0
lockscreen.disabled 1
mock_location 1
package_verifier_enable 0
screen_auto_brightness_adj -1
screen_brightness 5
screen_brightness_mode 0
screen_off_timeout 1800000
skip_first_use_hints 1
stay_on_while_plugged_in 3
transition_animation_scale 1.0
usb_mass_storage_enabled 0
user_setup_complete 1
verifier_verify_adb_installs 0
window_animation_scale 1.0
wifi_frequency_band 0
If the setting exists, it will be set.
Notice, that you don't have to specify category (global, system, secure) since it can figure that out itself.
(No, I didn't attach the executable. I have to double check it.)

Renate NST said:
Wow, @nmyshkin that looks like a bit of work.
Click to expand...
Click to collapse
Yeah, this is another example of why humans are not allowed to know the future. If they did, they would shy away from attempting many things!
I'd be interested in the executable. From my work on this app I can imagine what it must involve to ferret out the appropriate entries. On the NST, at least, values in settings.db for some things appear to be artifacts only and don't actually seem to have any effect. It just made things more interesting...

nmyshkin said:
I'd be interested in the executable.
Click to expand...
Click to collapse
Well, here it is (in the signature).
Park "setvalues" in an executable directory (like /data or /data/local/tmp), chmod 755 it.
It takes the name of the values file as the only argument.
It's verbose in telling you what was and any changes done.
This also should run on any version of Android and any device.

Custom version for those without B&N account and/or apps
5-11-22: updated to 1.5. Uninstall any previous version to insure all variables clear.
--removed Google Accounts section
--removed Network Location setting (relied on Google Accounts)
This version is only for devices which either bypassed OOBE and then removed all B&N stuff or went through registration and then removed all B&N stuff
I've been playing around with a third (my last one, I swear) device and have finally hit upon the method for removing B&N apps without causing a constant drumbeat of protest in the system. More on that in a future post.
No B&N apps means no B&N account, whether you start with a registered device or skip OOBE, so my Nook Settings app had a lot of fluff in it for such devices. Also, the "About" stuff did not work so there was no information such as serial number, MAC address, etc.
This special version of the app addresses these issues. References to B&N stuff are removed and there is a custom "About" section which includes an editing option for those items the app could not dig up on its own (like your name, if you didn't register). See screenshot below.
Hint: if you skip OOBE, you will need to jot down the serial number, model number, and MAC address for entry into the "About" page. You can find these values on the screen where you elect to skip OOBE. Failing that, they are contained in text files in /rom/devconf
The zip below includes all the stuff from the zip in the OP with an updated custom app. Follow the installation instructions in post #1. If you are updating, you only need to uninstall the previous version and install the new one.

Great job!
The app dosen't install on my rooted NST fw ver.1.2.1 but at least I removed all unnecessary B&N apps. Thanks

kodovoimeji said:
Great job!
The app dosen't install on my rooted NST fw ver.1.2.1 but at least I removed all unnecessary B&N apps. Thanks
Click to expand...
Click to collapse
It should install and run on 1.2.1 without any problems. Did you remember to copy the two maps files? It won't install without those present. Also be sure the permissions for each file are set correctly. If not the installer may register them as MIA and refuse to run.
I'm not sure if the same level of dependency is present at installation for sqlite or busybox, but you do need both (with correct permissions) for some parts of the app to function.
Edit: I can confirm that the app installs and runs with FW 1.2.1, following the directions in the first post.

Hey, I find myself unable to put the com.google.android.maps.jar and com.google.android.maps.xml files in the required locations via ADB push due to the filesystem being readonly, and I'm not sure the safest way to remount readwrite on this device, please could you advise?

alexhorner said:
Hey, I find myself unable to put the com.google.android.maps.jar and com.google.android.maps.xml files in the required locations via ADB push due to the filesystem being readonly, and I'm not sure the safest way to remount readwrite on this device, please could you advise?
Click to expand...
Click to collapse
Did you choose one of the NookManager options with ES File Explorer? If so, you can mount /system as RW from within its Settings and just transfer the files to either your sdcard or /media (the "Nook" drive) and then move them with the file manager from there. You can even set the permissions (long-press on file and select "Properties").
Otherwise...hmm....let me see if I have that bookmarked...
Code:
adb shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
I think that's it. Then for permissions:
Code:
adb shell chmod 644 /system/wherever/whatever.xml
(I'm not suggesting it's 644--you'll have to check that.
ES File Explorer is by far the easier method.

nmyshkin said:
Did you choose one of the NookManager options with ES File Explorer? If so, you can mount /system as RW from within its Settings and just transfer the files to either your sdcard or /media (the "Nook" drive) and then move them with the file manager from there. You can even set the permissions (long-press on file and select "Properties").
Otherwise...hmm....let me see if I have that bookmarked...
Code:
adb shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
I think that's it. The for permissions:
Code:
adb shell chmod 644 /system/wherever/whatever.xml
(I'm not suggesting it's 644--you'll have to check that.
ES File Explorer is by far the easier method.
Click to expand...
Click to collapse
I went for the classic so no ES here! Just ReLaunchX. The mount command worked, and I can confirm 644 is the correct numeric for the required permissions. Busybox already existed from the root, and I installed sqlite3 with correct permissions, 755.
Copied those 2 google files over, set permissions, rebooted then installed the APK fine.
Sorry for being such a noob here, but how do I now run the app as superuser? Running it without just refreshes the screen (I assume that means it crashed after trying to open?)
Opening the Superuser app shows no apps in list.

alexhorner said:
I went for the classic so no ES here! Just ReLaunchX. The mount command worked, and I can confirm 644 is the correct numeric for the required permissions. Busybox already existed from the root, and I installed sqlite3 with correct permissions, 755.
Copied those 2 google files over, set permissions, rebooted then installed the APK fine.
Sorry for being such a noob here, but how do I now run the app as superuser? Running it without just refreshes the screen (I assume that means it crashed after trying to open?)
Opening the Superuser app shows no apps in list.
Click to expand...
Click to collapse
Sometimes SU is slow to respond. I'd reboot and try again.

No luck waiting or rebooting unfortunately. Superuser has no app list and the screen refresh flashes when trying to launch still

alexhorner said:
No luck waiting or rebooting unfortunately. Superuser has no app list and the screen refresh flashes when trying to launch still
Click to expand...
Click to collapse
Grr...
Ok, I've shut down my PC for the day. Let me try a clean install of the app tomorrow and refresh my memory on exactly what happens. SU can really be a pain on this device sometimes.

alexhorner said:
No luck waiting or rebooting unfortunately. Superuser has no app list and the screen refresh flashes when trying to launch still
Click to expand...
Click to collapse
So instead of reading till I get drowsy I have downloaded the zip right on the device! I uninstalled the app and checked Superuser to be sure any entries were gone. Then I extracted the app from the zip and installed it. The moment (or nearly) I tapped the app icon I got the Superuser permission request.
I'm baffled.

nmyshkin said:
So instead of reading till I get drowsy I have downloaded the zip right on the device! I uninstalled the app and checked Superuser to be sure any entries were gone. Then I extracted the app from the zip and installed it. The moment (or nearly) I tapped the app icon I got the Superuser permission request.
I'm baffled.
Click to expand...
Click to collapse
Well...
I opened ADB connect, as I knew that asked for super user too. It did, I accepted and it launched fine. I went back to ReLaunchX and decided to look at Superuser now. It won't open at all.
Okay, fine, I'll reboot the device.
Nope, still won't open.
So I decided to open ADB Connect again. Well now that's broken too! It gives me a black screen, so I decided to tap back. Nope. Okay, I'm stuck now.
After a few seconds I get "Sorry! Activity ReLaunchX (in application ReLaunchX) is not responding. [Wait] [Force Close]
I have since forced closed, uninstalled the settings app and rebooted. Superuser still broken. ADB works once and then subsequent times black screens me.
Edit: Got a logcat of superuser:
Spoiler: Logcat Superuser
Code:
D/AndroidRuntime( 1529): Shutting down VM
W/dalvikvm( 1529): threadid=3: thread exiting with uncaught exception (group=0x4001b210)
E/AndroidRuntime( 1529): Uncaught handler: thread main exiting due to uncaught exception
E/AndroidRuntime( 1529): java.lang.NullPointerException
E/AndroidRuntime( 1529): at com.noshufou.android.su.PinnedHeaderListView.configureHeaderView(PinnedHeaderListView.java:153)
E/AndroidRuntime( 1529): at com.noshufou.android.su.AppListActivity$AppListAdapter.onScroll(AppListActivity.java:326)
E/AndroidRuntime( 1529): at android.widget.AbsListView.invokeOnItemScrollListener(AbsListView.java:741)
E/AndroidRuntime( 1529): at android.widget.AbsListView.handleDataChanged(AbsListView.java:3181)
E/AndroidRuntime( 1529): at android.widget.ListView.layoutChildren(ListView.java:1488)
E/AndroidRuntime( 1529): at android.widget.AbsListView.onLayout(AbsListView.java:1314)
E/AndroidRuntime( 1529): at com.noshufou.android.su.PinnedHeaderListView.onLayout(PinnedHeaderListView.java:123)
E/AndroidRuntime( 1529): at android.view.View.layout(View.java:6863)
E/AndroidRuntime( 1529): at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1119)
E/AndroidRuntime( 1529): at android.widget.LinearLayout.layoutVertical(LinearLayout.java:998)
E/AndroidRuntime( 1529): at android.widget.LinearLayout.onLayout(LinearLayout.java:918)
E/AndroidRuntime( 1529): at android.view.View.layout(View.java:6863)
E/AndroidRuntime( 1529): at android.widget.FrameLayout.onLayout(FrameLayout.java:333)
E/AndroidRuntime( 1529): at android.view.View.layout(View.java:6863)
E/AndroidRuntime( 1529): at android.widget.FrameLayout.onLayout(FrameLayout.java:333)
E/AndroidRuntime( 1529): at android.view.View.layout(View.java:6863)
E/AndroidRuntime( 1529): at android.widget.FrameLayout.onLayout(FrameLayout.java:333)
E/AndroidRuntime( 1529): at android.view.View.layout(View.java:6863)
E/AndroidRuntime( 1529): at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1119)
E/AndroidRuntime( 1529): at android.widget.LinearLayout.layoutVertical(LinearLayout.java:998)
E/AndroidRuntime( 1529): at android.widget.LinearLayout.onLayout(LinearLayout.java:918)
E/AndroidRuntime( 1529): at android.view.View.layout(View.java:6863)
E/AndroidRuntime( 1529): at android.widget.FrameLayout.onLayout(FrameLayout.java:333)
E/AndroidRuntime( 1529): at android.view.View.layout(View.java:6863)
E/AndroidRuntime( 1529): at android.widget.FrameLayout.onLayout(FrameLayout.java:333)
E/AndroidRuntime( 1529): at android.view.View.layout(View.java:6863)
E/AndroidRuntime( 1529): at android.widget.FrameLayout.onLayout(FrameLayout.java:333)
E/AndroidRuntime( 1529): at android.view.View.layout(View.java:6863)
E/AndroidRuntime( 1529): at android.view.ViewRoot.performTraversals(ViewRoot.java:996)
E/AndroidRuntime( 1529): at android.view.ViewRoot.handleMessage(ViewRoot.java:1633)
E/AndroidRuntime( 1529): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 1529): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 1529): at android.app.ActivityThread.main(ActivityThread.java:4363)
E/AndroidRuntime( 1529): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 1529): at java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime( 1529): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
E/AndroidRuntime( 1529): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
E/AndroidRuntime( 1529): at dalvik.system.NativeStart.main(Native Method)
I/ActivityManager( 790): Removing old ANR trace file from /data/anr/traces.txt
W/ActivityManager( 790): Send CRASH intent: true
I/Process ( 790): Sending signal. PID: 1529 SIG: 3
D/EPD#ActivityManager( 790): resetRegion 4
D/NATIVE-EPD( 790): epd_reset_region: 0x10
D/EPD#ActivityManager( 790): resetRegion 5
D/NATIVE-EPD( 790): epd_reset_region: 0x20
D/EPD#ActivityManager( 790): resetRegion 6
D/NATIVE-EPD( 790): epd_reset_region: 0x40
D/EPD#ActivityManager( 790): resetRegion 7
D/NATIVE-EPD( 790): epd_reset_region: 0x80
D/DeviceManagerBroadcastReceiver( 949): action (com.bn.devicemanager.ACTION_HANDLE_CRASH)
I/dalvikvm( 1529): threadid=7: reacting to signal 3
I/dalvikvm( 1529): Wrote stack trace to '/data/anr/traces.txt'
I/Process ( 1529): Sending signal. PID: 1529 SIG: 9
I/ActivityManager( 790): Process com.noshufou.android.su (pid 1529) has died.
I/WindowManager( 790): WIN DEATH: Window{4a0ebc98 com.noshufou.android.su/com.noshufou.android.su.Su paused=false}
I/UsageStats( 790): Unexpected resume of com.gacode.relaunchx while already resumed in com.noshufou.android.su
W/InputManagerService( 790): Window already focused, ignoring focus gain of: [email protected]
V/Activity( 1225): performResume()

Most disturbing, as Jeeves would say.
Here's where my lack of depth shows. I can see there is trouble in the logcat. The word "CRASH" being a clue. But as to the rest..not so much.
I would, at this point, uninstall and reinstall SU--you can get the apk from your NookManager card.
I've got a fairly busy day but my aim is to back up one of my devices, revert it to an unrooted, registered state, root with the "classic" package and try to reproduce your situation. That's one step short of converting to UK and going through the entire process. Which I hope not to do.

nmyshkin said:
Most disturbing, as Jeeves would say.
Here's where my lack of depth shows. I can see there is trouble in the logcat. The word "CRASH" being a clue. But as to the rest..not so much.
I would, at this point, uninstall and reinstall SU--you can get the apk from your NookManager card.
I've got a fairly busy day but my aim is to back up one of my devices, revert it to an unrooted, registered state, root with the "classic" package and try to reproduce your situation. That's one step short of converting to UK and going through the entire process. Which I hope not to do.
Click to expand...
Click to collapse
The reinstall has certainly fixed Superuser, however, no luck with NookSettings still even after another reinstall. I feel reverting to UK on your device wouldn't particularly help you, however going from stock to rooted might. I am wondering at this point if that might do me any good.

It clearly shows a lack of resilience of Superuser although the instigation lies elsewhere.
There is absolutely no reason that an app should bomb doing a layout.
Personally, I've never liked su. All I need in life (before the advent of system as root) is a rooted adbd.

alexhorner said:
The reinstall has certainly fixed Superuser, however, no luck with NookSettings still even after another reinstall. I feel reverting to UK on your device wouldn't particularly help you, however going from stock to rooted might. I am wondering at this point if that might do me any good.
Click to expand...
Click to collapse
I have just found a new APK for Superuser, 3.0.7 which I have attached in both the unextracted ZIP form and the extracted APK form. Source is https://forum.xda-developers.com/t/app-superuser-2-3-6-1-now-on-the-market-2010-09-05.682828/page-49
Not sure it will be of much help, but it certainly works with ADB Konnect perfectly fine.
Still no luck with NookSettings. I decided to logcat that too, here it is:
Spoiler: NookSettings Logcat
Code:
I/ActivityManager( 790): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x14000000 cmp=com.home.nmyshkin.settings/net.dinglisch.android.tasker.Kid }
I/ActivityManager( 790): Start proc com.home.nmyshkin.settings for activity com.home.nmyshkin.settings/net.dinglisch.android.tasker.Kid: pid=3357 uid=10019 gids={}
E/TC ( 1023): KPICollector: 1634321461142 platform process_start {"processName":"com.home.nmyshkin.settings"}
I/dalvikvm( 3357): Debugger thread not active, ignoring DDM send (t=0x41504e4d l=38)
E/TC ( 1023): KPICollector: 1634321461231 ActivityManager background {"component":"com.gacode.relaunchx/.AllApplications"}
E/TC ( 1023): KPICollector: 1634321461238 ActivityManager foreground {"component":"com.home.nmyshkin.settings/net.dinglisch.android.tasker.Kid"}
I/dalvikvm( 3357): Debugger thread not active, ignoring DDM send (t=0x41504e4d l=56)
D/dalvikvm( 3357): GC freed 10007 objects / 357744 bytes in 64ms
D/dalvikvm( 3357): GC freed 10130 objects / 380968 bytes in 61ms
D/dalvikvm( 3357): GC freed 11236 objects / 402944 bytes in 41ms
D/dalvikvm( 3357): GC freed 7376 objects / 183336 bytes in 57ms
I/global ( 3357): Default buffer size used in BufferedReader constructor. It would be better to be explicit if an 8k-char buffer is required.
D/dalvikvm( 3357): GC freed 10826 objects / 521112 bytes in 53ms
D/LocationManager( 3357): Constructor: service = [email protected]
D/dalvikvm( 3357): GC freed 1646 objects / 200792 bytes in 44ms
D/dalvikvm( 3357): GC freed 116 objects / 120272 bytes in 44ms
I/global ( 3357): Default buffer size used in BufferedReader constructor. It would be better to be explicit if an 8k-char buffer is required.
E/dalvikvm( 3357): Could not find class 'com.google.android.maps.GeoPoint', referenced from method net.dinglisch.android.tasker.hf.a
W/dalvikvm( 3357): VFY: unable to resolve new-instance 279 (Lcom/google/android/maps/GeoPoint;) in Lnet/dinglisch/android/tasker/hf;
D/dalvikvm( 3357): VFY: replacing opcode 0x22 at 0x0005
D/dalvikvm( 3357): Making a copy of Lnet/dinglisch/android/tasker/hf;.a code (52 bytes)
W/dalvikvm( 3357): VFY: unable to find class referenced in signature (Lcom/google/android/maps/GeoPoint;)
I/dalvikvm( 3357): Could not find method com.google.android.maps.GeoPoint.getLatitudeE6, referenced from method net.dinglisch.android.tasker.hf.a
W/dalvikvm( 3357): VFY: unable to resolve virtual method 1180: Lcom/google/android/maps/GeoPoint;.getLatitudeE6 ()I
D/dalvikvm( 3357): VFY: replacing opcode 0x6e at 0x000a
D/dalvikvm( 3357): Making a copy of Lnet/dinglisch/android/tasker/hf;.a code (116 bytes)
W/dalvikvm( 3357): VFY: unable to find class referenced in signature (Lcom/google/android/maps/GeoPoint;)
W/dalvikvm( 3357): VFY: unable to find class referenced in signature (Lcom/google/android/maps/GeoPoint;)
W/dalvikvm( 3357): VFY: unable to find class referenced in signature (Lcom/google/android/maps/GeoPoint;)
W/dalvikvm( 3357): VFY: unable to find class referenced in signature (Lcom/google/android/maps/GeoPoint;)
I/dalvikvm( 3357): Could not find method com.google.android.maps.GeoPoint.getLatitudeE6, referenced from method net.dinglisch.android.tasker.hf.b
W/dalvikvm( 3357): VFY: unable to resolve virtual method 1180: Lcom/google/android/maps/GeoPoint;.getLatitudeE6 ()I
D/dalvikvm( 3357): VFY: replacing opcode 0x6e at 0x0009
D/dalvikvm( 3357): Making a copy of Lnet/dinglisch/android/tasker/hf;.b code (72 bytes)
W/dalvikvm( 3357): Unable to resolve superclass of Lnet/dinglisch/android/tasker/MyMapView; (284)
W/dalvikvm( 3357): Link of class 'Lnet/dinglisch/android/tasker/MyMapView;' failed
W/dalvikvm( 3357): Unable to resolve superclass of Lnet/dinglisch/android/tasker/ht; (280)
W/dalvikvm( 3357): Link of class 'Lnet/dinglisch/android/tasker/ht;' failed
W/dalvikvm( 3357): Unable to resolve superclass of Lnet/dinglisch/android/tasker/ht; (280)
W/dalvikvm( 3357): Link of class 'Lnet/dinglisch/android/tasker/ht;' failed
W/dalvikvm( 3357): VFY: unable to find class referenced in signature (Lcom/google/android/maps/GeoPoint;)
W/dalvikvm( 3357): Unable to resolve superclass of Lnet/dinglisch/android/tasker/MyMapView; (284)
W/dalvikvm( 3357): Link of class 'Lnet/dinglisch/android/tasker/MyMapView;' failed
E/dalvikvm( 3357): Could not find class 'net.dinglisch.android.tasker.MyMapView', referenced from method net.dinglisch.android.tasker.ql.a
W/dalvikvm( 3357): VFY: unable to resolve check-cast 472 (Lnet/dinglisch/android/tasker/MyMapView;) in Lnet/dinglisch/android/tasker/ql;
D/dalvikvm( 3357): VFY: replacing opcode 0x1f at 0x000b
D/dalvikvm( 3357): Making a copy of Lnet/dinglisch/android/tasker/ql;.a code (264 bytes)
W/dalvikvm( 3357): Unable to resolve superclass of Lnet/dinglisch/android/tasker/MyMapView; (284)
W/dalvikvm( 3357): Link of class 'Lnet/dinglisch/android/tasker/MyMapView;' failed
W/dalvikvm( 3357): VFY: unable to find class referenced in signature (Lnet/dinglisch/android/tasker/MyMapView;)
W/dalvikvm( 3357): Unable to resolve superclass of Lnet/dinglisch/android/tasker/MyMapView; (284)
W/dalvikvm( 3357): Link of class 'Lnet/dinglisch/android/tasker/MyMapView;' failed
I/dalvikvm( 3357): Could not find method net.dinglisch.android.tasker.MyMapView.getContext, referenced from method net.dinglisch.android.tasker.ql.a
W/dalvikvm( 3357): VFY: unable to resolve virtual method 3189: Lnet/dinglisch/android/tasker/MyMapView;.getContext ()Landroid/content/Context;
D/dalvikvm( 3357): VFY: replacing opcode 0x6e at 0x0001
D/dalvikvm( 3357): Making a copy of Lnet/dinglisch/android/tasker/ql;.a code (117 bytes)
W/dalvikvm( 3357): Unable to resolve superclass of Lnet/dinglisch/android/tasker/MyMapView; (284)
W/dalvikvm( 3357): Link of class 'Lnet/dinglisch/android/tasker/MyMapView;' failed
W/dalvikvm( 3357): VFY: unable to find class referenced in signature (Lnet/dinglisch/android/tasker/MyMapView;)
W/dalvikvm( 3357): Unable to resolve superclass of Lnet/dinglisch/android/tasker/MyMapView; (284)
W/dalvikvm( 3357): Link of class 'Lnet/dinglisch/android/tasker/MyMapView;' failed
W/dalvikvm( 3357): VFY: unable to find class referenced in signature (Lnet/dinglisch/android/tasker/MyMapView;)
W/dalvikvm( 3357): Unable to resolve superclass of Lnet/dinglisch/android/tasker/MyMapView; (284)
W/dalvikvm( 3357): Link of class 'Lnet/dinglisch/android/tasker/MyMapView;' failed
W/dalvikvm( 3357): Unable to resolve superclass of Lnet/dinglisch/android/tasker/MyMapView; (284)
W/dalvikvm( 3357): Link of class 'Lnet/dinglisch/android/tasker/MyMapView;' failed
W/dalvikvm( 3357): Unable to resolve superclass of Lnet/dinglisch/android/tasker/MyMapView; (284)
W/dalvikvm( 3357): Link of class 'Lnet/dinglisch/android/tasker/MyMapView;' failed
E/dalvikvm( 3357): Could not find class 'net.dinglisch.android.tasker.MyMapView', referenced from method net.dinglisch.android.tasker.ql.a
W/dalvikvm( 3357): VFY: unable to resolve new-instance 472 (Lnet/dinglisch/android/tasker/MyMapView;) in Lnet/dinglisch/android/tasker/ql;
D/dalvikvm( 3357): VFY: replacing opcode 0x22 at 0x0013
D/dalvikvm( 3357): Making a copy of Lnet/dinglisch/android/tasker/ql;.a code (96 bytes)
W/dalvikvm( 3357): Unable to resolve superclass of Lnet/dinglisch/android/tasker/MyMapView; (284)
W/dalvikvm( 3357): Link of class 'Lnet/dinglisch/android/tasker/MyMapView;' failed
W/dalvikvm( 3357): VFY: returning Ljava/lang/Object; (cl=0x0), declared Landroid/view/View; (cl=0x0)
W/dalvikvm( 3357): VFY: rejecting opcode 0x11 at 0x001c
W/dalvikvm( 3357): VFY: rejected Lnet/dinglisch/android/tasker/ql;.a (Landroid/content/Context;I)Landroid/view/View;
W/dalvikvm( 3357): Verifier rejected class Lnet/dinglisch/android/tasker/ql;
W/dalvikvm( 3357): Exception Ljava/lang/VerifyError; thrown during Lnet/dinglisch/android/tasker/md;.<clinit>
D/AndroidRuntime( 3357): Shutting down VM
W/dalvikvm( 3357): threadid=3: thread exiting with uncaught exception (group=0x4001b210)
E/Settings( 3357): 13.11.02#MyUEH: error: exception in thread main: java.lang.ExceptionInInitializerError
E/Settings( 3357): 13.11.02#: error: Caused by:
E/Settings( 3357): 13.11.02#: error: net.dinglisch.android.tasker.md.<clinit>(Unknown Source)
E/Settings( 3357): 13.11.02#: error: net.dinglisch.android.tasker.vh.b(Unknown Source)
E/Settings( 3357): 13.11.02#: error: net.dinglisch.android.tasker.vh.a(Unknown Source)
E/Settings( 3357): 13.11.02#: error: net.dinglisch.android.tasker.vh.d(Unknown Source)
E/Settings( 3357): 13.11.02#: error: net.dinglisch.android.tasker.Kid.onCreate(Unknown Source)
E/Settings( 3357): 13.11.02#: error: android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047)
E/AndroidRuntime( 3357): Uncaught handler: thread main exiting due to uncaught exception
E/AndroidRuntime( 3357): java.lang.ExceptionInInitializerError
E/AndroidRuntime( 3357): at net.dinglisch.android.tasker.vh.b(Unknown Source)
E/AndroidRuntime( 3357): at net.dinglisch.android.tasker.vh.a(Unknown Source)
E/AndroidRuntime( 3357): at net.dinglisch.android.tasker.vh.d(Unknown Source)
E/AndroidRuntime( 3357): at net.dinglisch.android.tasker.Kid.onCreate(Unknown Source)
E/AndroidRuntime( 3357): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047)
E/AndroidRuntime( 3357): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2459)
E/AndroidRuntime( 3357): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2512)
E/AndroidRuntime( 3357): at android.app.ActivityThread.access$2200(ActivityThread.java:119)
E/AndroidRuntime( 3357): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1863)
E/AndroidRuntime( 3357): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 3357): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 3357): at android.app.ActivityThread.main(ActivityThread.java:4363)
E/AndroidRuntime( 3357): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 3357): at java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime( 3357): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
E/AndroidRuntime( 3357): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
E/AndroidRuntime( 3357): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 3357): Caused by: java.lang.VerifyError: net.dinglisch.android.tasker.ql
E/AndroidRuntime( 3357): at net.dinglisch.android.tasker.md.<clinit>(Unknown Source)
E/AndroidRuntime( 3357): ... 17 more
I/ActivityManager( 790): Removing old ANR trace file from /data/anr/traces.txt
W/ActivityManager( 790): Send CRASH intent: true
I/Process ( 790): Sending signal. PID: 3357 SIG: 3
D/EPD#ActivityManager( 790): resetRegion 4
D/NATIVE-EPD( 790): epd_reset_region: 0x10
D/EPD#ActivityManager( 790): resetRegion 5
D/NATIVE-EPD( 790): epd_reset_region: 0x20
D/EPD#ActivityManager( 790): resetRegion 6
D/NATIVE-EPD( 790): epd_reset_region: 0x40
D/EPD#ActivityManager( 790): resetRegion 7
D/NATIVE-EPD( 790): epd_reset_region: 0x80
D/DeviceManagerBroadcastReceiver( 949): action (com.bn.devicemanager.ACTION_HANDLE_CRASH)
I/dalvikvm( 3357): threadid=7: reacting to signal 3
I/dalvikvm( 3357): Wrote stack trace to '/data/anr/traces.txt'
I/Process ( 3357): Sending signal. PID: 3357 SIG: 9
I/ActivityManager( 790): Process com.home.nmyshkin.settings (pid 3357) has died.
V/Activity( 1225): performResume()
D/EPD#ActivityResume( 790): resetRegion 4
D/NATIVE-EPD( 790): epd_reset_region: 0x10
D/EPD#ActivityResume( 790): resetRegion 5
D/NATIVE-EPD( 790): epd_reset_region: 0x20
D/EPD#ActivityResume( 790): resetRegion 6
D/NATIVE-EPD( 790): epd_reset_region: 0x40
D/EPD#ActivityResume( 790): resetRegion 7
D/NATIVE-EPD( 790): epd_reset_region: 0x80
D/EPD#ActivityResume( 790): Disable EPD for 350ms!!!!!!!!
I/UsageStats( 790): Unexpected resume of com.gacode.relaunchx while already resumed in com.home.nmyshkin.settings
D/ReLaunchApp( 1225): --- onResume(AllApps)
W/InputManagerService( 790): Window already focused, ignoring focus gain of: [email protected]
I/DeviceManagerHandler( 949): HandleMessage(): msg.what (1)
I/global ( 949): Default buffer size used in BufferedWriter constructor. It would be better to be explicit if an 8k-char buffer is required.
D/dalvikvm( 949): GC freed 4915 objects / 501464 bytes in 41ms
I/LogcatProcessor( 949): LOG END MARKER - 1634321464060

alexhorner said:
I have just found a new APK for Superuser, 3.0.7 which I have attached in both the unextracted ZIP form and the extracted APK form. Source is https://forum.xda-developers.com/t/app-superuser-2-3-6-1-now-on-the-market-2010-09-05.682828/page-49
Click to expand...
Click to collapse
I have tried other SU apps in the past but they were always complaining about updating binaries (not going to happen). But if you have something that works, good.
That logcat seems to point to the two maps files that are expected by Tasker or any of its kid apps (like Nook Settings). So much stuff about maps, like it can't find what it wants. I've never seen anything like that on my devices (not that I sit around watching logcats scroll by all day). Check that both files are in the proper places. The jar file belongs in /system/framework and is rw-r-r (or 644, as you said). The xml file is in /system/etc/permissions and is also rw-r-r.
In short, if the old SU popped up with ADB Konnect, it's probably not the problem. The Nook Settings app itself is not the problem. I have it running on three devices and the fresh install last night went without a hitch. I've tested it on both FW 1.2.1 and 1.2.2.
Getting one of my Nooks ready for a backup now.