Related
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.
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
EDIT: With the exposed method working well, I think it goes without saying that I will be moving on from this thread. Now on to the ouya store on CM10! lol
If for some reason you come here from google or some other place, the thread your looking for to get the play store working is below.
http://forum.xda-developers.com/showthread.php?t=2350639
Original----------------------------------------------------------------------------
This thread will be for working on getting the Google Play Store to work, aka com.android.vending.
Here is a logcat of the play crash when the vending apk has been sideloaded along with the google login and framework apks to /system/app. This was not from flashing the gapps.zip with CWM, this was sideloading the com.android.vending-4.0.25.apk... and GoogleLoginService.apk and GoogleServicesFramework.apk and setting permissions to 6755...
Process com.android.vending has crashed too many times
: killing!
I/ActivityManager( 310): Killing proc 2860:com.android.vending/u0a61: crash
V/DropBoxReceiver( 2593): Starting service for tag: system_app_crash, time: 1369
507749067
D/CrashReportService( 2593): Writing crash report to: /data/data/tv.ouya/cache/.
reports/1369507749067
W/ActivityManager( 310): Unable to launch app com.android.vending/10061 for ser
vice Intent { cmp=com.android.vending/com.google.android.finsky.services.DailyHy
giene }: process is bad
Click to expand...
Click to collapse
I also tried editing the /system/build.prop to say the device was a galaxy s4... same error on logcat...
adding the crash report files that should be in /data/data/tv.ouya/cache... not sure how to get the report data out of the bin file though.
tried this too... same
http://forum.xda-developers.com/showthread.php?p=40823085
tried the old kindle market. the EULA comes up click except and then dies. different logcat though...
http://forum.xda-developers.com/showthread.php?p=41831758#post41831758
Process com.android.vending (pid 1340) has died.
D/CrashReportService( 563): Writing crash report to: /data/data/tv.ouya/cache/.
reports/1369511460591
W/InputMethodManagerService( 311): Window already focused, ignoring focus gain
of: [email protected] attribute=n
ull
Click to expand...
Click to collapse
professorpoptart said:
tried the old kindle market. the EULA comes up click except and then dies. different logcat though...
http://forum.xda-developers.com/showthread.php?p=41831758#post41831758
Click to expand...
Click to collapse
I'm working with the full gapps install and having no better luck. As long as I don't sign into my google account the rest of the ouya functions fine, but as soon as i log in I start getting "com.google.process.gapps" and play store crash messages, even if I never open the store and sign in through music.
Update: I think we need to meet somewhere in the middle. I may be way off, but heres my reasoning...
I have installed the full gapps on my Ouya, and I can't get the terms to pull up on either market. You have no gapps installed and it is getting a little further but still crashing. I believe I have something on there the ouya doesn't like and that's stopping me, and you are missing something the play store needs. I was able to get my error to stop by uninstalling the talk.apk, but still no play store.
Are you getting the same logcat's?... just got to find the right thing to google! lol
This is with the old kindle apk from qwerty790
I/ActivityThread( 1306): Pub com.android.vending.SuggestionsProvider: com.androi
d.vending.SuggestionsProvider
D/vending ( 1306): [1] VendingApplication.onCreate(): Resetting ServiceLocator f
rom app
D/dalvikvm( 1306): GC_CONCURRENT freed 722K, 7% free 11293K/12103K, paused 5ms+3
ms, total 32ms
D/dalvikvm( 1306): WAIT_FOR_CONCURRENT_GC blocked 17ms
W/ResourceType( 1306): Failure getting entry for 0x7f020052 (t=1 e=82) in packag
e 0 (error -75)
D/AndroidRuntime( 1306): Shutting down VM
W/dalvikvm( 1306): threadid=1: thread exiting with uncaught exception (group=0x4
1022300)
E/AndroidRuntime( 1306): FATAL EXCEPTION: main
E/AndroidRuntime( 1306): java.lang.RuntimeException: Unable to start activity Co
mponentInfo{com.android.vending/com.android.vending.AssetBrowserActivity}: andro
id.view.InflateException: Binary XML file line #54: Error inflating class <unkno
wn>
Click to expand...
Click to collapse
this is from the start of the activity from the top of the error stack.
professorpoptart said:
Are you getting the same logcat's?... just got to find the right thing to google! lol
This is with the old kindle apk from qwerty790
Click to expand...
Click to collapse
Not even close. I'll post mine in a bit.
as much of a "bad" idea it is we could write script to recursive (or do it by hand) chmod 777 everything in /system to make sure it everything has permissions to do what it needs... unless the issue is the perms have to be set specifically... but I would think the gapps would have set them correctly if that was the case...
edit: ...almost beer o'clock!
sonofskywalker3 said:
Not even close. I'll post mine in a bit.
Click to expand...
Click to collapse
After installing the gapps did you clear cache?
looking into "com.android.vending.SuggestionsProvider" seems like its usually a cache issue. I get the same logcat after clearing in recovery but just hoping since you have the whole gapps and different errors this mighht be it.
found the cache idea here...http://forum.xda-developers.com/showthread.php?t=649149
ok so I went back to the 4.1.2 gapps files for vending and framework, set permissions and cleared cache. Still dies but now I get a toast fc message. now I'm getting something about the login service in the cat log.
here is the full logcat, did a logcat -c right before launching play. so the whole stack is the play event...
--------- beginning of /dev/log/main
D/su ( 1540): su invoked.
D/su ( 1541): Allowing root/shell.
D/su ( 1543): 2000 /system/bin/mksh executing 0 /system/bin/sh using shell
/system/bin/sh : sh
D/AndroidRuntime( 1542):
D/AndroidRuntime( 1542): >>>>>> AndroidRuntime START com.android.internal.os.Run
timeInit <<<<<<
D/AndroidRuntime( 1542): CheckJNI is OFF
D/dalvikvm( 1542): Trying to load lib libjavacore.so 0x0
D/dalvikvm( 1542): Added shared lib libjavacore.so 0x0
D/dalvikvm( 1542): Trying to load lib libnativehelper.so 0x0
D/dalvikvm( 1542): Added shared lib libnativehelper.so 0x0
I/ethernet( 1542): Loading ethernet jni class
D/AndroidRuntime( 1542): Calling main entry com.android.commands.am.Am
--------- beginning of /dev/log/system
I/ActivityManager( 309): Start proc com.koushikdutta.superuser for broadcast co
m.koushikdutta.superuser/.SuReceiver: pid=1554 uid=10038 gids={1028}
D/AndroidRuntime( 1542): Shutting down VM
I/AndroidRuntime( 1542): NOTE: attach of thread 'Binder_3' failed
D/dalvikvm( 1542): GC_CONCURRENT freed 100K, 88% free 492K/4096K, paused 1ms+0ms
, total 4ms
I/ActivityManager( 309): No longer want com.google.android.gsf.login (pid 1518)
: hidden #2
I/ActivityManager( 309): START {act=android.intent.action.MAIN cat=[android.int
ent.category.LAUNCHER] flg=0x10200000 cmp=com.android.vending/.AssetBrowserActiv
ity bnds=[960,540][960,540] u=0} from pid 1082
I/ActivityManager( 309): Start proc com.android.vending for activity com.androi
d.vending/.AssetBrowserActivity: pid=1568 uid=10061 gids={3003, 1015, 1023, 1028
}
I/ActivityThread( 1568): Pub com.google.android.finsky.RecentSuggestionsProvider
: com.google.android.finsky.providers.RecentSuggestionsProvider
I/ActivityThread( 1568): Pub com.google.android.finsky.QSBSuggestionsProvider2:
com.google.android.finsky.providers.QSBSuggestionsProvider
I/ActivityThread( 1568): Pub com.google.android.finsky.AppIconProvider: com.goog
le.android.finsky.providers.AppIconProvider
D/Finsky ( 1568): [1] FinskyApp.onCreate: Clearing cache due to crash on previo
us run.
D/Volley ( 1568): [1] DiskBasedCache.clear: Cache cleared.
I/dalvikvm( 1568): DexOpt: access denied from Lcom/google/android/volley/elegant
/ElegantThreadSafeConnManager$ElegantPool; to field Lorg/apache/http/impl/conn/t
sccm/ConnPoolByRoute;.poolLock
W/dalvikvm( 1568): VFY: unable to resolve instance field 10430
D/dalvikvm( 1568): VFY: replacing opcode 0x54 at 0x0000
I/dalvikvm( 1568): DexOpt: access denied from Lcom/google/android/volley/elegant
/ElegantThreadSafeConnManager$ElegantPool; to field Lorg/apache/http/impl/conn/t
sccm/ConnPoolByRoute;.poolLock
W/dalvikvm( 1568): VFY: unable to resolve instance field 10430
D/dalvikvm( 1568): VFY: replacing opcode 0x54 at 0x0000
I/dalvikvm( 1568): DexOpt: access denied from Lcom/google/android/volley/elegant
/ElegantThreadSafeConnManager$ElegantPool; to field Lorg/apache/http/impl/conn/t
sccm/ConnPoolByRoute;.poolLock
W/dalvikvm( 1568): VFY: unable to resolve instance field 10430
D/dalvikvm( 1568): VFY: replacing opcode 0x54 at 0x0020
I/dalvikvm( 1568): DexOpt: access denied from Lcom/google/android/volley/elegant
/ElegantThreadSafeConnManager$ElegantPool; to field Lorg/apache/http/impl/conn/t
sccm/ConnPoolByRoute;.poolLock
I/dalvikvm( 1568): DexOpt: unable to optimize instance field ref 0x28be at 0x42
in Lcom/google/android/volley/elegant/ElegantThreadSafeConnManager$ElegantPool;.
getEntryBlocking
I/dalvikvm( 1568): DexOpt: access denied from Lcom/google/android/volley/elegant
/ElegantThreadSafeConnManager$ElegantPool; to field Lorg/apache/http/impl/conn/t
sccm/ConnPoolByRoute;.poolLock
I/dalvikvm( 1568): DexOpt: unable to optimize instance field ref 0x28be at 0x76
in Lcom/google/android/volley/elegant/ElegantThreadSafeConnManager$ElegantPool;.
getEntryBlocking
I/dalvikvm( 1568): DexOpt: access denied from Lcom/google/android/volley/elegant
/ElegantThreadSafeConnManager$ElegantPool; to field Lorg/apache/http/impl/conn/t
sccm/ConnPoolByRoute;.poolLock
I/dalvikvm( 1568): DexOpt: unable to optimize instance field ref 0x28be at 0xec
in Lcom/google/android/volley/elegant/ElegantThreadSafeConnManager$ElegantPool;.
getEntryBlocking
D/Finsky ( 1568): [1] FinskyApp.onCreate: Initializing network with DFE https:/
/android.clients.google.com/fdfe/
D/Finsky ( 1568): [1] DailyHygiene.goMakeHygieneIfDirty: Dirty, need more hygie
ne.
D/dalvikvm( 1568): GC_CONCURRENT freed 609K, 6% free 11398K/12103K, paused 14ms+
4ms, total 52ms
D/dalvikvm( 1568): WAIT_FOR_CONCURRENT_GC blocked 22ms
E/AndroidHttpClient( 1568): Leak found
E/AndroidHttpClient( 1568): java.lang.IllegalStateException: AndroidHttpClient c
reated and never closed
E/AndroidHttpClient( 1568): at com.google.android.volley.AndroidHttpClient.<
init>(AndroidHttpClient.java:175)
E/AndroidHttpClient( 1568): at com.google.android.volley.AndroidHttpClient.n
ewInstance(AndroidHttpClient.java:161)
E/AndroidHttpClient( 1568): at com.google.android.volley.GoogleHttpClient.<i
nit>(GoogleHttpClient.java:117)
E/AndroidHttpClient( 1568): at com.google.android.finsky.FinskyApp.onCreate(
FinskyApp.java:295)
E/AndroidHttpClient( 1568): at android.app.Instrumentation.callApplicationOn
Create(Instrumentation.java:999)
E/AndroidHttpClient( 1568): at android.app.ActivityThread.handleBindApplicat
ion(ActivityThread.java:4151)
E/AndroidHttpClient( 1568): at android.app.ActivityThread.access$1300(Activi
tyThread.java:130)
E/AndroidHttpClient( 1568): at android.app.ActivityThread$H.handleMessage(Ac
tivityThread.java:1255)
E/AndroidHttpClient( 1568): at android.os.Handler.dispatchMessage(Handler.ja
va:99)
E/AndroidHttpClient( 1568): at android.os.Looper.loop(Looper.java:137)
E/AndroidHttpClient( 1568): at android.app.ActivityThread.main(ActivityThrea
d.java:4745)
E/AndroidHttpClient( 1568): at java.lang.reflect.Method.invokeNative(Native
Method)
E/AndroidHttpClient( 1568): at java.lang.reflect.Method.invoke(Method.java:5
11)
E/AndroidHttpClient( 1568): at com.android.internal.os.ZygoteInit$MethodAndA
rgsCaller.run(ZygoteInit.java:786)
E/AndroidHttpClient( 1568): at com.android.internal.os.ZygoteInit.main(Zygot
eInit.java:553)
E/AndroidHttpClient( 1568): at dalvik.system.NativeStart.main(Native Method)
I/ActivityManager( 309): Start proc com.google.android.gsf.login for service co
m.google.android.gsf.login/com.google.android.gsf.loginservice.GoogleLoginServic
e: pid=1600 uid=10044 gids={3003, 1007, 2001, 3006, 1028}
D/Finsky ( 1568): [1] 2.run: Loaded library for account: [FljaznBLk4v9VpY6BInpX
qtpvXA]
D/Finsky ( 1568): [1] 2.run: Finished loading 1 libraries.
D/libEGL ( 1568): loaded /system/lib/egl/libEGL_tegra.so
E/ ( 1568): file /data/data/com.nvidia.NvCPLSvc/files/driverlist.txt: not
found!
I/ ( 1568): Attempting to load EGL implementation /system/lib//egl/libEGL
_tegra_impl
I/ ( 1568): Loaded EGL implementation /system/lib//egl/libEGL_tegra_impl
D/libEGL ( 1568): loaded /system/lib/egl/libGLESv1_CM_tegra.so
D/dalvikvm( 309): GC_CONCURRENT freed 1104K, 17% free 15096K/17991K, paused 5ms
+11ms, total 107ms
D/libEGL ( 1568): loaded /system/lib/egl/libGLESv2_tegra.so
I/ ( 1568): Loading GLESv2 implementation /system/lib//egl/libGLESv2_tegr
a_impl
D/OpenGLRenderer( 1568): Enabling debug mode 0
I/ActivityManager( 309): No longer want com.koushikdutta.superuser (pid 1554):
hidden #2
W/dalvikvm( 1568): threadid=13: thread exiting with uncaught exception (group=0x
40bed300)
E/AndroidRuntime( 1568): FATAL EXCEPTION: Thread-139
E/AndroidRuntime( 1568): java.lang.IllegalAccessError: tried to access field com
.google.android.volley.elegant.ElegantThreadSafeConnManager$ElegantPool.poolLock
from class com.google.android.volley.elegant.ElegantThreadSafeConnManager$Elega
ntPool
E/AndroidRuntime( 1568): at com.google.android.volley.elegant.ElegantThre
adSafeConnManager$ElegantPool.getEntryBlocking(ElegantThreadSafeConnManager.java
:140)
E/AndroidRuntime( 1568): at com.google.android.volley.elegant.ElegantThre
adSafeConnManager$ElegantPool$1.getPoolEntry(ElegantThreadSafeConnManager.java:1
22)
E/AndroidRuntime( 1568): at com.google.android.volley.elegant.ElegantThre
adSafeConnManager$1.getConnection(ElegantThreadSafeConnManager.java:64)
E/AndroidRuntime( 1568): at org.apache.http.impl.client.DefaultRequestDir
ector.execute(DefaultRequestDirector.java:456)
E/AndroidRuntime( 1568): at org.apache.http.impl.client.AbstractHttpClien
t.execute(AbstractHttpClient.java:898)
E/AndroidRuntime( 1568): at org.apache.http.impl.client.cache.CachingHttp
Client.callBackend(CachingHttpClient.java:670)
E/AndroidRuntime( 1568): at org.apache.http.impl.client.cache.CachingHttp
Client.handleCacheMiss(CachingHttpClient.java:451)
E/AndroidRuntime( 1568): at org.apache.http.impl.client.cache.CachingHttp
Client.execute(CachingHttpClient.java:377)
E/AndroidRuntime( 1568): at org.apache.http.impl.client.AbstractHttpClien
t.execute(AbstractHttpClient.java:797)
E/AndroidRuntime( 1568): at com.google.android.volley.AndroidHttpClient.e
xecute(AndroidHttpClient.java:308)
E/AndroidRuntime( 1568): at com.google.android.volley.GoogleHttpClient.ex
ecuteWithoutRewriting(GoogleHttpClient.java:217)
E/AndroidRuntime( 1568): at com.google.android.volley.GoogleHttpClient.ex
ecute(GoogleHttpClient.java:259)
E/AndroidRuntime( 1568): at com.google.android.volley.GoogleHttpClient.ex
ecute(GoogleHttpClient.java:316)
E/AndroidRuntime( 1568): at com.android.volley.toolbox.HttpClientStack.pe
rformRequest(HttpClientStack.java:83)
E/AndroidRuntime( 1568): at com.android.volley.toolbox.BasicNetwork.perfo
rmRequest(BasicNetwork.java:93)
E/AndroidRuntime( 1568): at com.android.volley.NetworkDispatcher.run(Netw
orkDispatcher.java:98)
W/ActivityManager( 309): Force finishing activity com.android.vending/.AssetB
rowserActivity
V/DropBoxReceiver( 552): Starting service for tag: system_app_crash, time: 1369
518820421
D/CrashReportService( 552): Writing crash report to: /data/data/tv.ouya/cache/.
reports/1369518820421
I/ActivityManager( 309): Displayed com.android.vending/.AssetBrowserActivity: +
517ms
I/ActivityManager( 309): No longer want com.google.android.gsf.login (pid 1600)
: hidden #2
D/dalvikvm( 110): WAIT_FOR_CONCURRENT_GC blocked 0ms
I/ActivityManager( 309): Start proc com.google.android.gsf.login for service co
m.google.android.gsf.login/com.google.android.gsf.loginservice.GoogleLoginServic
e: pid=1618 uid=10044 gids={3003, 1007, 2001, 3006, 1028}
D/dalvikvm( 110): GC_EXPLICIT freed 39K, 7% free 10748K/11459K, paused 2ms+2ms,
total 27ms
D/dalvikvm( 110): WAIT_FOR_CONCURRENT_GC blocked 0ms
D/dalvikvm( 110): GC_EXPLICIT freed <1K, 7% free 10748K/11459K, paused 2ms+3ms,
total 25ms
D/dalvikvm( 110): WAIT_FOR_CONCURRENT_GC blocked 0ms
D/dalvikvm( 110): GC_EXPLICIT freed <1K, 7% free 10748K/11459K, paused 1ms+3ms,
total 22ms
I/ActivityManager( 309): No longer want com.android.vending (pid 1568): hidden
#2
W/ActivityManager( 309): Scheduling restart of crashed service com.android.vend
ing/com.google.android.finsky.services.DailyHygiene in 5000ms
W/InputMethodManagerService( 309): Got RemoteException sending setActive(false)
notification to pid 1568 uid 10061
Click to expand...
Click to collapse
sonofskywalker3 said:
as soon as i log in I start getting "com.google.process.gapps" and play store crash messages
Click to expand...
Click to collapse
I'm getting the play crash every 10-15 minutes or so now too since clearing the cache, so I bet the update script cleared it for you...
Doing a little research on what play requires I was reading the below link that says phonesky.apk is the new vending.apk, and that like we thought for the store to just open all you need in the /system/app is the framework, loginservice and phonesky apks. It doesnt say anything about permissions so I re pushed each of them with default perms, cleared cache in recovery ...And!... same thing.
http://blog.apkudo.com/2012/08/08/run-google-play-on-an-emulator-and-pretend-to-be-any-device/
next I'm going to look at this from the logcat... looks like this fall apart after that...
E/ ( 1568): file /data/data/com.nvidia.NvCPLSvc/files/driverlist.txt: not found!
looking at:
Lorg/apache/http/impl/conn/tsccm/ConnPoolByRoute;.poolLock
I wonder if this apache client is stopping it? Maybe running something for the ouya store on the same connections as play store uses? I will try and go through the app manager and try to force stop/disable the other ouya store apps and see if there are any changes to the logcat.
Also tried to push the vending-4.1.6 apk... (might have needed to push an updated frame work too)
Clearing cache and data from the app manager and rebooting on every test...
edit:
After killing all of the ouya stuff, it looks like it is getting farther into the launch as now there is some stuff about syncing with my gmail account info in it.
edit:
using titanium backup to freeze the ouya framework and apps to make sure they do not get in the way...
Well I started from scratch again just so I know I'm at a clean start. flashed the OTA zip. I've been working with the old vending logcats, as its a little easier to follow whats "not" working with it...
I'm starting to think I will have to build a port of CM to get play to work, I think the ouya framework is using some resources that normally the play store uses so when play launches it gets access denied when trying to use those parts. I think I will try to remove as much ouya branded files as I can and see what the logcat looks like.
edit:
just thinking, has anyone tried to backup and restore the ouya stuff on another device yet? wonder if it would result in breaking the play store there... nice proof of concept....
professorpoptart said:
Well I started from scratch again just so I know I'm at a clean start. flashed the OTA zip. I've been working with the old vending logcats, as its a little easier to follow whats "not" working with it...
I'm starting to think I will have to build a port of CM to get play to work, I think the ouya framework is using some resources that normally the play store uses so when play launches it gets access denied when trying to use those parts. I think I will try to remove as much ouya branded files as I can and see what the logcat looks like.
edit:
just thinking, has anyone tried to backup and restore the ouya stuff on another device yet? wonder if it would result in breaking the play store there... nice proof of concept....
Click to expand...
Click to collapse
I'm not going to be much help here, like, at all. I do have a OUYA tho, I can follow instructions, have a lot of free time, and have CWM/busybox/wireless ADB/superuser on it already. So if theres anything I can do to help, let me know.
I also got my ouya just today.
I'm having some trouble getting adb to work but Iam also ready to test things.
GizmoTheGreen said:
I also got my ouya just today.
I'm having some trouble getting adb to work but Iam also ready to test things.
Click to expand...
Click to collapse
Sweet, I am in the process of porting a rom from another tegra 3 device so I will have a base aosp to work with. Play market will probably just work then... and the new task may then be how to load the OUYA stuff onto the new rom. I'm having issues getting video output on CWM to test the new rom though.
Do you CWM up and running?
Well I may be able to play with it some tonight. If you've got something you want me to try flashing PM me a link and I'll give it a shot and see what happens.
sonofskywalker3 said:
Well I may be able to play with it some tonight. If you've got something you want me to try flashing PM me a link and I'll give it a shot and see what happens.
Click to expand...
Click to collapse
K, I'm hoping its not too bad as we don't care about camera,gps,radio,screen,ect... we just need it to boot and get wifi which we should be able to pull out of the current /system/etc/permissions/android.hardware.wifi.xml. I will start a new thread to document the rom though I just want to get the CWM recovery working first so I dont have to flash OTA every time it breaks... even if I have to fastboot recovery.img every time thats fine...
I managed to get adb to work, added superuser and sideloaded xbmc, works wonderfully even without logging in to ouya account.
I have not installed cwm just yet, will tomorrow.
GizmoTheGreen said:
I managed to get adb to work, added superuser and sideloaded xbmc, works wonderfully even without logging in to ouya account.
I have not installed cwm just yet, will tomorrow.
Click to expand...
Click to collapse
Be sure to install the hw accelerated xbmc beta, handles 1080p perfectly
Sent from my GT-P1000 using Tapatalk HD
Paulenski said:
Be sure to install the hw accelerated xbmc beta, handles 1080p perfectly
Sent from my GT-P1000 using Tapatalk HD
Click to expand...
Click to collapse
yep, I did, works well, tried 60fps 720p amv
Hey Guys,
I am helping a friend of mine out with her watch. She is having an issue in which each time she opens the camera on her watch she gets a force close. I forgot my watch at home and can't look. I was wondering if someone would be willing to check their system folder for me and see if there is an FactoryCamera_FB.odex file? The FactoryCamera_FB.apk seems to be the only one without a matching odex file. In general, she is getting the following errors.
10-21 13:29:55.755 D/IS_FW_DEBUG( 1448): [TS:00000250 ms][F:00000000][SMIA_StreamOn]===========================================
10-21 13:29:55.755 D/IS_FW_DEBUG( 1448): [TS:00000252 ms][F:00000000][ISP_ENTRY]ApplyM2MData
10-21 13:29:55.755 D/IS_FW_DEBUG( 1448): [TS:00000252 ms][F:00000000][ISP_ENTRY] [M2M] No data or invalid data !!
10-21 13:29:55.760 W/dalvikvm( 2989): threadid=12: thread exiting with uncaught exception (group=0x419d0930)
10-21 13:29:55.765 E/AndroidRuntime( 2989): FATAL EXCEPTION: startPreviewThread
10-21 13:29:55.765 E/AndroidRuntime( 2989): java.lang.RuntimeException: startPreview failed
10-21 13:29:55.765 E/AndroidRuntime( 2989): at com.sec.android.seccamera.SecCamera.startPreview(Native Method)
10-21 13:29:55.765 E/AndroidRuntime( 2989): at com.sec.android.app.camera.CommonEngine$1.run(CommonEngine.java:746)
10-21 13:29:55.765 E/AndroidRuntime( 2989): at java.lang.Thread.run(Thread.java:856)
10-21 13:29:55.775 W/ActivityManager( 1781): Process com.sec.android.app.camera has crashed too many times: killing!
10-21 13:29:55.780 W/LicenseLogService( 1781): log() is called by non admin
10-21 13:29:55.810 W/ContextImpl( 1781): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1337 com.android.server.am.ActivityStack.startPausingLocked:1412 com.android.server.am.ActivityStack.finishActivityLocked:5894 com.android.server.am.ActivityStack.finishActivityLocked:5808 com.android.server.am.ActivityManagerService.handleAppCrashLocked:9497
10-21 13:29:56.120 E/android.os.Debug( 1781): [email protected] > dumpstate -k -t -z -d -o /data/log/dumpstate_app_error
Additionally, I see up the log a bit where it appears to be setting properties and is setting orientation to 0 and two inprintable hex characters (Screenshot attached). Does anyone have any ideas what could be causing this? I have also attached the full log dump.
Thanks in advance for any help!
Is it rooted?
Sent from my SM-N9005 using Tapatalk
download firmware and flash with odin
galaxy note 3
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.