Database Develop

[Q] Magic 32B calling problem with latest Cyans 5.0.7 or SuperE ROMS.

Hi,
I have found problem for both mentioned ROMs. My phone behaves completely same on both roms which are presumably using Cyan's core and work. This problem can be replicated any time on both.
Here is the description:
1. Go to Contacts
2. in Contacts choose either tab Contacts or Favourites
3. Choose any contact (doesnt matter whether it has one, two or more numbers to its name) to get into Contact details and information
4. Press green hw call button on phone
=
immediately i get "Sorry! The process android.process.acore has stopped unexpectedly. Please try again. Force close"
If i try to call this way:
1. Go to Contacts
2. in Contacts choose either tab Call log or Phone
3. Choose contact
4. Press green hw button on phone and all works fine
also it works fine if you
1. Go to Contacts
2. in Contacts choose either tab Contacts or Favourites
3. Choose any contact (doesnt matter whether it has one, two or more numbers to its name) to get into Contact details and information
4. instead using green hw call button just choose number on screen and touch screen for call number and you will get successful call.
-----------------------------------------------------------------------
This is adb logcat of crash:
Code:
MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.conta
cts/.DialtactsContactsEntryActivity bnds=[83,138][157,217] }
I/ActivityManager( 111): Starting activity: Intent { act=android.intent.action.
VIEW dat=content://com.android.contacts/contacts/lookup/2322i5b23ef238d0dad28/81
cmp=com.android.contacts/.ViewContactActivity }
W/Sources ( 565): Unknown type=com.google, mime=vnd.com.google.cursor.item/cont
act_misc
W/Sources ( 565): Unknown type=com.google, mime=vnd.android.cursor.item/group_m
embership
W/Sources ( 565): Unknown type=com.google, mime=vnd.android.cursor.item/group_m
embership
I/ActivityManager( 111): Displayed activity com.android.contacts/.ViewContactAc
tivity: 449 ms (total 449 ms)
D/dalvikvm( 565): threadid=25 wakeup: interrupted
I/ActivityManager( 111): Starting activity: Intent { act=android.intent.action.
CALL_PRIVILEGED dat=content://com.android.contacts/contacts/81 }
D/AndroidRuntime( 565): Shutting down VM
W/dalvikvm( 565): threadid=3: thread exiting with uncaught exception (group=0x4
001e180)
E/AndroidRuntime( 565): Uncaught handler: thread main exiting due to uncaught e
xception
D/dalvikvm( 565): GC freed 6275 objects / 412856 bytes in 139ms
E/AndroidRuntime( 565): android.content.ActivityNotFoundException: No Activity
found to handle Intent { act=android.intent.action.CALL_PRIVILEGED dat=content:/
/com.android.contacts/contacts/81 }
E/AndroidRuntime( 565): at android.app.Instrumentation.checkStartActivit
yResult(Instrumentation.java:1408)
E/AndroidRuntime( 565): at android.app.Instrumentation.execStartActivity
(Instrumentation.java:1378)
E/AndroidRuntime( 565): at android.app.Activity.startActivityForResult(A
ctivity.java:2749)
E/AndroidRuntime( 565): at android.app.Activity.startActivity(Activity.j
ava:2855)
E/AndroidRuntime( 565): at com.android.contacts.ViewContactActivity.onKe
yDown(ViewContactActivity.java:731)
E/AndroidRuntime( 565): at android.view.KeyEvent.dispatch(KeyEvent.java:
1037)
E/AndroidRuntime( 565): at android.app.Activity.dispatchKeyEvent(Activit
y.java:2043)
E/AndroidRuntime( 565): at com.android.internal.policy.impl.PhoneWindow$
DecorView.dispatchKeyEvent(PhoneWindow.java:1631)
E/AndroidRuntime( 565): at android.view.ViewRoot.deliverKeyEventToViewHi
erarchy(ViewRoot.java:2368)
E/AndroidRuntime( 565): at android.view.ViewRoot.handleFinishedEvent(Vie
wRoot.java:2338)
E/AndroidRuntime( 565): at android.view.ViewRoot.handleMessage(ViewRoot.
java:1641)
E/AndroidRuntime( 565): at android.os.Handler.dispatchMessage(Handler.ja
va:99)
E/AndroidRuntime( 565): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 565): at android.app.ActivityThread.main(ActivityThrea
d.java:4363)
E/AndroidRuntime( 565): at java.lang.reflect.Method.invokeNative(Native
Method)
E/AndroidRuntime( 565): at java.lang.reflect.Method.invoke(Method.java:5
21)
E/AndroidRuntime( 565): at com.android.internal.os.ZygoteInit$MethodAndA
rgsCaller.run(ZygoteInit.java:860)
E/AndroidRuntime( 565): at com.android.internal.os.ZygoteInit.main(Zygot
eInit.java:618)
E/AndroidRuntime( 565): at dalvik.system.NativeStart.main(Native Method)
I/Process ( 111): Sending signal. PID: 565 SIG: 3
I/dalvikvm( 565): threadid=7: reacting to signal 3
E/dalvikvm( 565): Unable to open stack trace file '/data/anr/traces.txt': Permi
ssion denied
I/DumpStateReceiver( 111): Added state dump to 1 crashes
Also I would like to clarify how to wipe phone before flashing new ROM:
1. fastboot boot recovery.zip
2. go to wipe options
3. wipe data/cache/dalvik cache (options 1,2,3)
Is there anything else I should do for wiping phone for clean installation?
Because I have feeling that action might not be working correctly either, after clean installation of phone I had all my previous packages (.apk) installed so reinstalled and wiped again and then again I did not have any packages but in market application and download I had all previous applications ready for installation. How was this remember? Thru Google Apps login and password from last time?
Please help me with this issue, I love 2.1 so much more than stock 1.6 but really cant get rid of this issue with calls.
Thank you

hi! you should post this issues on their respective thread
good luck

I think this is just a known bug to all of those eclair roms that just hasn't been fixed yet

juangil said:
hi! you should post this issues on their respective thread
good luck
Click to expand...
Click to collapse
I thought of creating own forum post as it relates not to one ROM but probably to series of ROMs using possibly one kernel or some part ?
Should I post it in SuperE or Cyan ROMs forums please lock/close this post and I will copy paste this post to relevant forums.

s0mep00p said:
I think this is just a known bug to all of those eclair roms that just hasn't been fixed yet
Click to expand...
Click to collapse
I havent found simillar issue here or looked at wrong posts. Than you for you information, means should I just use this for time being and wait for corrections?

It's already been fixed for CM-5.0.8 which should be out soon.

cyanogen said:
It's already been fixed for CM-5.0.8 which should be out soon.
Click to expand...
Click to collapse
Excellent work, cant wait! Last issue for me on this great ROM.

[Q] Market FCs after installing applications.

Hi All,
This is my first post here, sorry if this thread is duplicate but I was unable to find a similar thread.
I have a SGS9000 that I bought from Turkey, since Market and YouTube is not bundled here, I rooted the official 2.2 update with Z4 and pushed Vending.apk and YouTube.apk. The problem is my Market application is FCing after updating or installing applications. I install an application, installation finishes and I get an FC. Then, when I open the installed application for the first time, I get another Market FC. Then everything works fine.
I didn't wipe the system after installing 2.2 update but wiped cache from recovery. Since I pushed the latest versions of the applications, there are no updates to remove. Also clearing cache or stored information doesn't help either.
Is this a known bug or are there any solutions?
Thanks in advance.
P.S: I'm a seasoned Linux admin and programmer and I'm probably able to pull most of the tricks you can propose.

I am having the same problem with my galaxy s too. I followed the same procedure you described. I heard you are bound to get FCs this way. Apparently you should install google apps by applying update.zip via recovery. However, I have recovery 3e and it does not have the capability to use unsigned update.zip. It seems you need to have 2e and I don't have that so I could not do it. As you are a capable linux admin, maybe you can figure out how to revert back to 2e and can share with us.
Sent from my GT-I9000 using XDA App

Actually this is kinda absurd because the g-apps package doesn't have any files related to market besides the Vending and MarketUpdater apks and when you put the packages to the /system/app, they are installed by the phone anyway. I'll try to find some logs in the phone. Maybe then I can understand the real cause of the problem and dig deeper.

It might have something to do with some permissions etc. set by some sys files. I heard something about conflicts/permissions issue with market causing FCs. If you can check the sys logs and figure out th rd problem, that would be great.
Also I read somewhere in these forums who had the same issue solved it via update.zip way.
Sent from my GT-I9000 using XDA App

I had time to debug the problem and I isolated the problem. I have both good news and bad news.
The good news is, the problem looks like a simple permission problem. adb logcat spilled all the guts of the problem and it looks like it:
Code:
E/DatabaseUtils(25977): Writing exception to parcel
E/DatabaseUtils(25977): java.lang.SecurityException: Permission Denial: writing com.google.android.gsf.settings.GoogleSettingsProvider uri content://com.google.settings/partner from pid=8129, uid=10008 requires com.google.android.providers.settings.permission.WRITE_GSETTINGS
E/DatabaseUtils(25977): at android.content.ContentProvider$Transport.enforceWritePermission(ContentProvider.java:337)
E/DatabaseUtils(25977): at android.content.ContentProvider$Transport.insert(ContentProvider.java:173)
E/DatabaseUtils(25977): at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:146)
E/DatabaseUtils(25977): at android.os.Binder.execTransact(Binder.java:288)
E/DatabaseUtils(25977): at dalvik.system.NativeStart.run(Native Method)
W/dalvikvm( 8129): threadid=11: thread exiting with uncaught exception (group=0x4001d7d0)
E/AndroidRuntime( 8129): FATAL EXCEPTION: UpdateCheckinDatabaseService
E/AndroidRuntime( 8129): java.lang.SecurityException: Permission Denial: writing com.google.android.gsf.settings.GoogleSettingsProvider uri content://com.google.settings/partner from pid=8129, uid=10008 requires com.google.android.providers.settings.permission.WRITE_GSETTINGS
E/AndroidRuntime( 8129): at android.os.Parcel.readException(Parcel.java:1260)
E/AndroidRuntime( 8129): at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:160)
E/AndroidRuntime( 8129): at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:114)
E/AndroidRuntime( 8129): at android.content.ContentProviderProxy.insert(ContentProviderNative.java:408)
E/AndroidRuntime( 8129): at android.content.ContentResolver.insert(ContentResolver.java:587)
E/AndroidRuntime( 8129): at com.google.android.gsf.GoogleSettingsContract$NameValueTable.putString(GoogleSettingsContract.java:55)
E/AndroidRuntime( 8129): at com.google.android.gsf.GoogleSettingsContract$Partner.putString(GoogleSettingsContract.java:126)
E/AndroidRuntime( 8129): at com.android.vending.UpdateCheckinService.updateCheckinDatabase(UpdateCheckinService.java:140)
E/AndroidRuntime( 8129): at com.android.vending.UpdateCheckinService.access$000(UpdateCheckinService.java:34)
E/AndroidRuntime( 8129): at com.android.vending.UpdateCheckinService$ServiceHandler.handleMessage(UpdateCheckinService.java:85)
E/AndroidRuntime( 8129): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 8129): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 8129): at android.os.HandlerThread.run(HandlerThread.java:60)
I/PowerManagerService( 2475): Light Animator Finished curIntValue=32
W/ActivityManager( 2475): Force finishing activity com.android.vending/.SearchAssetListActivity
I/ ( 2475): dumpmesg > /data/log/dumpstate_app_error.log
The bad news is, I'm not familiar to the internal workings of the android yet and I was unable to modify the permissions. I tried /system/etc/permissions and added some xml files that contained proper syntax but that was unable to solve the problem.
I'll be glad if someone more experienced can give me some hints because I want to solve this annoying problem.
Cheers and thanks in advance to all.

[SOLVED] Market FCs after installing applications.
Nevermind, just use the new market app, updating solves all the problems.
I copied APK to my sdcard, became root from adb shell and moved the APK to /system/app, then ran "pm install -r Vending.apk" and now everything is silky smooth.

Hey man,
I tried to do what you've described but when I tried to install the vending.apk
I got the following error:
Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE]
Can you describe the procedure step by step for a noob please ?
thearif

Ok I found another solution that works. Simply install Sgstools from market (this will be your last FC) and update market from there. Not only will you have the latest market but you will get rid of FCs as well.
Note that you need to have root (i had temporary Z4root). That is it.
Sent from my GT-I9000 using XDA App

thearif said:
Ok I found another solution that works. Simply install Sgstools from market (this will be your last FC) and update market from there. Not only will you have the latest market but you will get rid of FCs as well.
Click to expand...
Click to collapse
This worked well until I rebooted. After the reboot FCs were back. Logcat is identical to yours:
Code:
I/ActivityThread( 1151): Publishing provider com.android.vending.SuggestionsProvider: com.android.vending.SuggestionsProvider
D/vending ( 1151): [1] VendingApplication.onCreate(): Resetting ServiceLocator from app
D/GoogleLoginService( 409): onBind: Intent { act=android.accounts.AccountAuthenticator cmp=com.google.android.gsf/.loginservice.GoogleLoginService }
I/ActivityManager( 259): Displayed activity com.android.vending/.AssetBrowserActivity: 906 ms (total 906 ms)
D/ResourceType( 1151): calling getConfigurations
D/ResourceType( 1151): called getConfigurations size=230
I/dalvikvm( 409): Jit: resizing JitTable from 4096 to 8192
D/dalvikvm( 1151): GC_FOR_MALLOC freed 6455 objects / 553792 bytes in 53ms
E/DatabaseUtils( 409): Writing exception to parcel
E/DatabaseUtils( 409): java.lang.SecurityException: Permission Denial: writing com.google.android.gsf.settings.GoogleSettingsProvider uri content://com.google.settings/partner from pid=1151, uid=10025 requires com.google.android.providers.settings.permis
sion.WRITE_GSETTINGS
E/DatabaseUtils( 409): at android.content.ContentProvider$Transport.enforceWritePermission(ContentProvider.java:348)
E/DatabaseUtils( 409): at android.content.ContentProvider$Transport.insert(ContentProvider.java:196)
E/DatabaseUtils( 409): at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:146)
E/DatabaseUtils( 409): at android.os.Binder.execTransact(Binder.java:288)
E/DatabaseUtils( 409): at dalvik.system.NativeStart.run(Native Method)
W/dalvikvm( 1151): threadid=11: thread exiting with uncaught exception (group=0x4001d7e8)
E/AndroidRuntime( 1151): FATAL EXCEPTION: Thread-12
E/AndroidRuntime( 1151): java.lang.SecurityException: Permission Denial: writing com.google.android.gsf.settings.GoogleSettingsProvider uri content://com.google.settings/partner from pid=1151, uid=10025 requires com.google.android.providers.settings.permission.WRITE_GSETTINGS
E/AndroidRuntime( 1151): at android.os.Parcel.readException(Parcel.java:1260)
E/AndroidRuntime( 1151): at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:160)
E/AndroidRuntime( 1151): at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:114)
E/AndroidRuntime( 1151): at android.content.ContentProviderProxy.insert(ContentProviderNative.java:408)
E/AndroidRuntime( 1151): at android.content.ContentResolver.insert(ContentResolver.java:592)
E/AndroidRuntime( 1151): at com.google.android.gsf.GoogleSettingsContract$NameValueTable.putString(GoogleSettingsContract.java:55)
E/AndroidRuntime( 1151): at com.google.android.gsf.GoogleSettingsContract$Partner.putString(GoogleSettingsContract.java:126)
E/AndroidRuntime( 1151): at com.android.vending.compat.MarketCheckinHelper.updateCheckinDatabase(MarketCheckinHelper.java:12)
E/AndroidRuntime( 1151): at com.android.vending.CheckinUpdater.sendContentSyncViaCheckin(CheckinUpdater.java:219)
E/AndroidRuntime( 1151): at com.android.vending.CheckinUpdater.performCheckin(CheckinUpdater.java:176)
E/AndroidRuntime( 1151): at com.android.vending.CheckinUpdater.access$000(CheckinUpdater.java:38)
E/AndroidRuntime( 1151): at com.android.vending.CheckinUpdater$1.run(CheckinUpdater.java:109)
E/AndroidRuntime( 1151): at com.android.vending.util.WorkService$1.run(WorkService.java:37)
W/ActivityManager( 259): Force finishing activity com.android.vending/.AssetBrowserActivity
W/ResourceType( 259): Skipping entry 0x7f040006 in package table 0 because it is not complex!
W/ResourceType( 259): Skipping entry 0x7f040005 in package table 0 because it is not complex!
I/Process ( 1151): Sending signal. PID: 1151 SIG: 9

I dont know what is causing your problem to come back after reboot. The very first thing that I checked was to is to see if the problem would pop back up after a reboot but it did not.
So you were on a rooted phone when you did this and gave root access to the sgstools app. If this is the case, maybe you can try clearing your cache.
thearif
Sent from my GT-I9000 using XDA App

Gtalk from 2.3.4 to 2.3.3

So I have been an android user for about 3 days now and just signed up for the forums. So I cannot post this to the dev section.
Anyway.
So I'm trying to port the new Gtalk to 2.3.3 from 2.3.4.
I have used adb push to move the appropriate apk and odex files as well as moved the libtalk_jni.so
The app loads and it looks new and all but there is no video option.
So I decompile the apk and there seems to be some reference to video in the AndroidManifest
com.google.android.talk.permission.VIDEO_CHAT_SERVICE
Can someone get me up to speed? Am I missing something?

Well i am not as lucky as you,man. MIUI just cannot recognize new version gtalk.
Sent from my Google Nexus S using XDA Premium App

xiambax said:
So I have been an android user for about 3 days now and just signed up for the forums. So I cannot post this to the dev section.
Anyway.
So I'm trying to port the new Gtalk to 2.3.3 from 2.3.4.
I have used adb push to move the appropriate apk and odex files as well as moved the libtalk_jni.so
The app loads and it looks new and all but there is no video option.
So I decompile the apk and there seems to be some reference to video in the AndroidManifest
com.google.android.talk.permission.VIDEO_CHAT_SERVICE
Can someone get me up to speed? Am I missing something?
Click to expand...
Click to collapse
where to find the .so file? could you post a link please?

elban said:
where to find the .so file? could you post a link please?
Click to expand...
Click to collapse
Here are the files,, can anyone deodex the apks please

I was thinking the same thing, so I did a bit of research into this.
I was able to successfully deodex and recompile the app, however it doesn't show up in the launcher. I think because it's Talk2.apk it needs to be launched from "Talk". Looking at the update, there are patches for Talk.apk and Talk.odex, which confirm that suspicion.
Looking at the manifest however, it looks like there is some new video service, so I'm not sure if just installing the updated talk app will work.
If someone would like to upload a dump of their /system on 2.3.4 I can try deodexing the new talk and talk2 apks, and we can try that, but otherwise there isn't much I can do since I don't have a NS in my possession right now.

edude03 said:
I was thinking the same thing, so I did a bit of research into this.
I was able to successfully deodex and recompile the app, however it doesn't show up in the launcher. I think because it's Talk2.apk it needs to be launched from "Talk". Looking at the update, there are patches for Talk.apk and Talk.odex, which confirm that suspicion.
Looking at the manifest however, it looks like there is some new video service, so I'm not sure if just installing the updated talk app will work.
If someone would like to upload a dump of their /system on 2.3.4 I can try deodexing the new talk and talk2 apks, and we can try that, but otherwise there isn't much I can do since I don't have a NS in my possession right now.
Click to expand...
Click to collapse
Talk.apk isn't present after the update, updater-script deletes it entirely. It's never replaced and not present in /system/app any longer. There is not a single call to patch Talk.apk in the updater-script that I can find nor do I see the .p patch under the patch dir of the packaged update.
Talk2.apk and Talk2.odex are then extracted to /system/app (they are present in the update in their entirety, they are not patches). libtalk_jni.so is extracted to /system/lib (also present in its entirety in the update).
Here's Talk2.apk, Talk2.odex and libtalk_jni.so directly from the update.

krohnjw said:
Talk.apk isn't present after the update, updater-script deletes it entirely. It's never replaced and not present in /system/app any longer. There is not a single call to patch Talk.apk in the updater-script that I can find nor do I see the .p patch under the patch dir of the packaged update.
Talk2.apk and Talk2.odex are then extracted to /system/app (they are present in the update in their entirety, they are not patches). libtalk_jni.so is extracted to /system/lib (also present in its entirety in the update).
Here's Talk2.apk, Talk2.odex and libtalk_jni.so directly from the update.
Click to expand...
Click to collapse
The app has to be deodexed to be useful. For that we need the whole rom dump (well /system).

blunden said:
The app has to be deodexed to be useful. For that we need the whole rom dump (well /system).
Click to expand...
Click to collapse
Dumping system now - I'll upload when finished.
edit: Uploading now - this will take a little while. I'll post a link when it's finished.
And completed: https://docs.google.com/leaf?id=0B_...IxZTktNWQzNGFmYTExY2Y1&hl=en&authkey=CL2J6csE

Thanks for the dump krohnjw and thanks for the correction. I was looking at the wrong version of the OTA (I was looking at the 2.3.2 -> 2.3.3 OTA :s)
EDIT 2: Here's the de-odexed APK, signed with testkeys. http://dl.dropbox.com/u/9720998/Talk2.apk. As of right now, on GRI40 and XXJVK (android 2.3.3 on a GT-i9000) it gives me a permission error. I've tired adb install and adb push /system/app; chmod 644 Talk2.apk. '

Almost there, though for some reason it's getting a permission error even though I'm running it from /system/app
Code:
flg=0x10200000 cmp=com.google.android.talk/.SigningInActivity } from pid 446
I/ActivityManager( 307): Start proc com.google.android.talk for activity com.google.android.talk/.SigningInActivity: pid=2035 uid=10067 gids={3003, 1015, 1006}
D/dalvikvm( 260): GC_EXPLICIT freed 12K, 53% free 2580K/5379K, external 1625K/2137K, paused 67ms
D/dalvikvm( 260): GC_EXPLICIT freed <1K, 53% free 2580K/5379K, external 1625K/2137K, paused 100ms
D/szipinf ( 2035): Initializing inflate state
D/dalvikvm( 260): GC_EXPLICIT freed <1K, 53% free 2580K/5379K, external 1625K/2137K, paused 76ms
I/ActivityThread( 2035): Pub com.google.android.talk.SuggestionProvider: com.google.android.talk.SuggestionsProvider
V/PlayerDriver( 261): HandleInformationalEvent: 23
I/ActivityManager( 307): Starting: Intent { dat=content://com.google.android.providers.talk/accounts/1 cmp=com.google.android.talk/.SigninActivity } from pid 2035
W/ActivityManager( 307): Trying to launch com.google.android.talk/.SigninActivity
D/dalvikvm( 2035): GC_EXTERNAL_ALLOC freed 115K, 51% free 2715K/5447K, external 2120K/2137K, paused 22ms
D/AndroidRuntime( 2035): Shutting down VM
W/dalvikvm( 2035): threadid=1: thread exiting with uncaught exception (group=0x40015578)
E/AndroidRuntime( 2035): FATAL EXCEPTION: main
E/AndroidRuntime( 2035): java.lang.SecurityException: Need GTalk_SERVICE permission: Neither user 10067 nor current process has com.google.android.gtalkservice.permission.GTALK_SERVICE.
E/AndroidRuntime( 2035): at android.os.Parcel.readException(Parcel.java:1322)
E/AndroidRuntime( 2035): at android.os.Parcel.readException(Parcel.java:1276)
E/AndroidRuntime( 2035): at com.google.android.gtalkservice.IGTalkService$Stub$Proxy.getImSessionForAccountId(IGTalkService.java:252)
E/AndroidRuntime( 2035): at com.google.android.talk.SigninActivity.signInAccount(SigninActivity.java:414)
E/AndroidRuntime( 2035): at com.google.android.talk.SigninActivity.access$200(SigninActivity.java:52)
E/AndroidRuntime( 2035): at com.google.android.talk.SigninActivity$1.run(SigninActivity.java:165)
E/AndroidRuntime( 2035): at android.os.Handler.handleCallback(Handler.java:587)
E/AndroidRuntime( 2035): at android.os.Handler.dispatchMessage(Handler.java:92)
E/AndroidRuntime( 2035): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 2035): at android.app.ActivityThread.main(ActivityThread.java:3687)
E/AndroidRuntime( 2035): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 2035): at java.lang.reflect.Method.invoke(Method.java:507)
E/AndroidRuntime( 2035): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:842)
E/AndroidRuntime( 2035): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:600)
E/AndroidRuntime( 2035): at dalvik.system.NativeStart.main(Native Method)
E/ ( 307): Dumpstate > /data/log/dumpstate_app_error
W/ActivityManager( 307): Force finishing activity com.google.android.talk/.SigninActivity
I/dumpstate( 2047): begin
W/ActivityManager( 307): Activity pause timeout for HistoryRecord{40be0658 com.google.android.talk/.SigninActivity}

edude03 said:
Almost there, though for some reason it's getting a permission error even though I'm running it from /system/app
Code:
flg=0x10200000 cmp=com.google.android.talk/.SigningInActivity } from pid 446
I/ActivityManager( 307): Start proc com.google.android.talk for activity com.google.android.talk/.SigningInActivity: pid=2035 uid=10067 gids={3003, 1015, 1006}
D/dalvikvm( 260): GC_EXPLICIT freed 12K, 53% free 2580K/5379K, external 1625K/2137K, paused 67ms
D/dalvikvm( 260): GC_EXPLICIT freed <1K, 53% free 2580K/5379K, external 1625K/2137K, paused 100ms
D/szipinf ( 2035): Initializing inflate state
D/dalvikvm( 260): GC_EXPLICIT freed <1K, 53% free 2580K/5379K, external 1625K/2137K, paused 76ms
I/ActivityThread( 2035): Pub com.google.android.talk.SuggestionProvider: com.google.android.talk.SuggestionsProvider
V/PlayerDriver( 261): HandleInformationalEvent: 23
I/ActivityManager( 307): Starting: Intent { dat=content://com.google.android.providers.talk/accounts/1 cmp=com.google.android.talk/.SigninActivity } from pid 2035
W/ActivityManager( 307): Trying to launch com.google.android.talk/.SigninActivity
D/dalvikvm( 2035): GC_EXTERNAL_ALLOC freed 115K, 51% free 2715K/5447K, external 2120K/2137K, paused 22ms
D/AndroidRuntime( 2035): Shutting down VM
W/dalvikvm( 2035): threadid=1: thread exiting with uncaught exception (group=0x40015578)
E/AndroidRuntime( 2035): FATAL EXCEPTION: main
E/AndroidRuntime( 2035): java.lang.SecurityException: Need GTalk_SERVICE permission: Neither user 10067 nor current process has com.google.android.gtalkservice.permission.GTALK_SERVICE.
E/AndroidRuntime( 2035): at android.os.Parcel.readException(Parcel.java:1322)
E/AndroidRuntime( 2035): at android.os.Parcel.readException(Parcel.java:1276)
E/AndroidRuntime( 2035): at com.google.android.gtalkservice.IGTalkService$Stub$Proxy.getImSessionForAccountId(IGTalkService.java:252)
E/AndroidRuntime( 2035): at com.google.android.talk.SigninActivity.signInAccount(SigninActivity.java:414)
E/AndroidRuntime( 2035): at com.google.android.talk.SigninActivity.access$200(SigninActivity.java:52)
E/AndroidRuntime( 2035): at com.google.android.talk.SigninActivity$1.run(SigninActivity.java:165)
E/AndroidRuntime( 2035): at android.os.Handler.handleCallback(Handler.java:587)
E/AndroidRuntime( 2035): at android.os.Handler.dispatchMessage(Handler.java:92)
E/AndroidRuntime( 2035): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 2035): at android.app.ActivityThread.main(ActivityThread.java:3687)
E/AndroidRuntime( 2035): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 2035): at java.lang.reflect.Method.invoke(Method.java:507)
E/AndroidRuntime( 2035): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:842)
E/AndroidRuntime( 2035): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:600)
E/AndroidRuntime( 2035): at dalvik.system.NativeStart.main(Native Method)
E/ ( 307): Dumpstate > /data/log/dumpstate_app_error
W/ActivityManager( 307): Force finishing activity com.google.android.talk/.SigninActivity
I/dumpstate( 2047): begin
W/ActivityManager( 307): Activity pause timeout for HistoryRecord{40be0658 com.google.android.talk/.SigninActivity}
Click to expand...
Click to collapse
Have you tried to fix permissions or clear data for Talk? Sounds like a permission or UID error.

I've pushed the apk but it doesn't get loaded (no dex in dalvik cache), unfortunately no errors in logcat.
I think it's because it's not signed.

No I did sign it, let me clear the caches and data though just to make sure.
Sent from my GT-I9000 using XDA App

On cm 7 I can confirm it opens starts running then force closes.
Sent from my HTC Glacier using XDA Premium App

xiambax said:
Mine doesn't force close
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
You already have the update for the nexus s meaning you are on 2.3.4 cm7 runs 2.3.3
Sent from my HTC Glacier using XDA Premium App

Can you tell me exactly where you push the files? Talk is system app and lib would go into system lib correct?
Sent from my HTC Glacier using XDA Premium App

edude03 said:
Thanks for the dump krohnjw and thanks for the correction. I was looking at the wrong version of the OTA (I was looking at the 2.3.2 -> 2.3.3 OTA :s)
EDIT 2: Here's the de-odexed APK, signed with testkeys. http://dl.dropbox.com/u/9720998/Talk2.apk. As of right now, on GRI40 and XXJVK (android 2.3.3 on a GT-i9000) it gives me a permission error. I've tired adb install and adb push /system/app; chmod 644 Talk2.apk. '
Click to expand...
Click to collapse
I installed it successfully,, but I don't see the option for video calling ?!

I'll look into why that is as soon as I can get it working myself, probably because of some check for the video service.
What OS are you on Nokia7Vista?

edude03 said:
I'll look into why that is as soon as I can get it working myself, probably because of some check for the video service.
What OS are you on Nokia7Vista?
Click to expand...
Click to collapse
Android 2.3.3 on Galaxy S
I copied the .so file and your apk to their appropriate locations and removed the old talk.apk version and it worked,, but no video calling option

OK. I got it running now, it was a permission error.
That said it has a weird graphical glitch and doesn't show any contacts.
I'll investigate when I get home.
Sent from my GT-I9000 using XDA App

[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.

[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.