Don't know if the problem is wide spread, or just my bad luck, but everytime I try to install Google Sky Map from the Market, after downloading the app and before going into install my phone reboots.
I've gone from latest Cyan 5.0.7 to leaked froyo FRF50, then FRF72 and now FRF83.
So, to find out whether it's a problem for many people, if you've upgraded to Froyo, try to install Google Sky Map (save all work first and participate in this poll.
ps. Is there any log file I can check via adb?
Had Sky Map since I installed FRF50, no problems.
I have the same problem. It also happened when I tried to install the koi pond LW.
Is it really that big of a problem. Sure it's a little bug, but it doesn't effect the OS or the app permanently. How often do you install SkyMap?
For the record, I've never had a reboot after installing SkyMap or any other app.
anstosa said:
Is it really that big of a problem. Sure it's a little bug, but it doesn't effect the OS or the app permanently. How often do you install SkyMap?
For the record, I've never had a reboot after installing SkyMap or any other app.
Click to expand...
Click to collapse
well, thing is that I can't install SkyMap at all, only option it seems to wipe completely and reinstall Froyo.
I just hope there's some kind of way to remove something manually without complete wipe. I just need some directions, where to look and what to try.
after using logcat on the device during installation of Sky Map here's what happens:
W/dalvikvm( 79): threadid=11: thread exiting with uncaught exception (group=0x4001d7f0)
E/AndroidRuntime( 79): *** FATAL EXCEPTION IN SYSTEM PROCESS: PackageManager
E/AndroidRuntime( 79): java.lang.SecurityException: Requires android.permission.ASEC_CREATE permission
E/AndroidRuntime( 79): at android.os.Parcel.readException(Parcel.java:1247)
E/AndroidRuntime( 79): at android.os.Parcel.readException(Parcel.java:1235)
E/AndroidRuntime( 79): at com.android.internal.app.IMediaContainerService$Stub$Proxy.copyResourceToContainer(IMediaContainerService.java:164)
E/AndroidRuntime( 79): at com.android.server.PackageManagerService$SdInstallArgs.copyApk(PackageManagerService.java:5341)
E/AndroidRuntime( 79): at com.android.server.PackageManagerService$InstallParams.handleStartCopy(PackageManagerService.java:4956)
E/AndroidRuntime( 79): at com.android.server.PackageManagerService$HandlerParams.startCopy(PackageManagerService.java:4815)
E/AndroidRuntime( 79): at com.android.server.PackageManagerService$PackageHandler.doHandleMessage(PackageManagerService.java:470)
E/AndroidRuntime( 79): at com.android.server.PackageManagerService$PackageHandler.handleMessage(PackageManagerService.java:415)
E/AndroidRuntime( 79): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 79): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 79): at android.os.HandlerThread.run(HandlerThread.java:60)
Click to expand...
Click to collapse
anyone know where I can add permission ASEC_CREATE to make it work?
The problem has to do with /sdcard/.android_secure
Removing teh entire directory solves things for some people, but not for me though. Have also the same problem with androidVNC...
i dont think u need to reboot... i never did
I was able to get it installed again. I turned on USB storage and had the external drive mounted in my OS. I then installed from the market place. I am guessing that forced it to install internally, which worked fine. Up to that point, it kept rebooting my phone every time I tried to install it.
or just unmount the SD card
in Settings->SD card & phone storage, then install the app and then remount the SD card. That worked for me.
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.
I updated to Froyo from CM.
Some market updates/installs are fine. Some cause this crash and the Android GUI restarts (the whole N1 doesn't reboot however).
D/VoldCmdListener( 54): asec list
I/PackageHelper( 652): Size of container 2 MB 689299 bytes
W/dalvikvm( 83): threadid=11: thread exiting with uncaught exception (group=0x4001d7f0)
E/AndroidRuntime( 83): *** FATAL EXCEPTION IN SYSTEM PROCESS: PackageManager
E/AndroidRuntime( 83): java.lang.SecurityException: Requires android.permission.ASEC_CREATE permission
E/AndroidRuntime( 83): at android.os.Parcel.readException(Parcel.java:1247)
E/AndroidRuntime( 83): at android.os.Parcel.readException(Parcel.java:1235)
E/AndroidRuntime( 83): at com.android.internal.app.IMediaContainerService$Stub$Proxy.copyResourceToContainer(IMediaContainerService.java:164)
E/AndroidRuntime( 83): at com.android.server.PackageManagerService$SdInstallArgs.copyApk(PackageManagerService.java:5341)
E/AndroidRuntime( 83): at com.android.server.PackageManagerService$InstallParams.handleStartCopy(PackageManagerService.java:4956)
E/AndroidRuntime( 83): at com.android.server.PackageManagerService$HandlerParams.startCopy(PackageManagerService.java:4815)
E/AndroidRuntime( 83): at com.android.server.PackageManagerService$PackageHandler.doHandleMessage(PackageManagerService.java:470)
E/AndroidRuntime( 83): at com.android.server.PackageManagerService$PackageHandler.handleMessage(PackageManagerService.java:415)
E/AndroidRuntime( 83): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 83): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 83): at android.os.HandlerThread.run(HandlerThread.java:60)
I believe I get the same issue and log messages when I try to move applications to my sdcard either from the applications menu or by adb command. :/
I have the same error when trying to install the latest version of Neocore.
I have the same problem. Is there a solution ? Would full data wipe help ?
Just did a full data wipe, and it helped for me.
Yeah, have to do full wipe to fix it.
Isn't there any other solutions ?
I don't really feel like wiping now.. :s
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
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.
Hello,
My phone keeps crashing and rebooting. When I shut it down it freezes on battery charging screen. It can only be unblocked via adb or by pushing power+volumeUP+volumeDOWN.
I got a new HTC One Mini 2 and tried to install Cyanogen Mod on it.
I unlocked the bootloader via the HTC website and flashed TWRP for recovery.
Via TWRP I installed the build provided by cyanogenmod.
The build worked fine on my old HTC One Mini 2.
I have tried different versions of TWRP and various ROMS, same problems occur every time (although it used to get stuck on a non-responsive twrp menu screen before, instead of the battery charging screen).
I always factory wipe the phone, and make sure cache and dalvik have been wiped.
I've also been looking for the stock version of android to see whether the problem came from cyanogen mod. Has anyone got it?
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.101.1102.19.1017
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.19.401.2
(bootloader) version-misc: PVT SHIP S-ON
Click to expand...
Click to collapse
Also this is present in all the logs I managed to obtain from the phone:
--------- beginning of crash
E/AndroidRuntime( 1979): FATAL EXCEPTION: main
E/AndroidRuntime( 1979): Process: com.cyanogenmod.eleven, PID: 1979
E/AndroidRuntime( 1979): java.lang.RuntimeException: Unable to instantiate application com.cyanogenmod.eleven.ElevenApplication: java.lang.ClassNotFoundException: Didn't find class "com.cyanogenmod.eleven.ElevenApplication" on path: DexPathList[[zip file "/system/app/Eleven/Eleven.apk"],nativeLibraryDirectories=[/vendor/lib, /system/lib]]
E/AndroidRuntime( 1979): at android.app.LoadedApk.makeApplication(LoadedApk.java:564)
E/AndroidRuntime( 1979): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4524)
E/AndroidRuntime( 1979): at android.app.ActivityThread.access$1600(ActivityThread.java:147)
E/AndroidRuntime( 1979): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1357)
E/AndroidRuntime( 1979): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 1979): at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime( 1979): at android.app.ActivityThread.main(ActivityThread.java:5254)
E/AndroidRuntime( 1979): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime( 1979): at java.lang.reflect.Method.invoke(Method.java:372)
E/AndroidRuntime( 1979): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:898)
E/AndroidRuntime( 1979): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:693)
E/AndroidRuntime( 1979): Caused by: java.lang.ClassNotFoundException: Didn't find class "com.cyanogenmod.eleven.ElevenApplication" on path: DexPathList[[zip file "/system/app/Eleven/Eleven.apk"],nativeLibraryDirectories=[/vendor/lib, /system/lib]]
E/AndroidRuntime( 1979): at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:56)
E/AndroidRuntime( 1979): at java.lang.ClassLoader.loadClass(ClassLoader.java:511)
E/AndroidRuntime( 1979): at java.lang.ClassLoader.loadClass(ClassLoader.java:469)
E/AndroidRuntime( 1979): at android.app.Instrumentation.newApplication(Instrumentation.java:979)
E/AndroidRuntime( 1979): at android.app.LoadedApk.makeApplication(LoadedApk.java:559)
E/AndroidRuntime( 1979): ... 10 more
E/AndroidRuntime( 1979): Suppressed: java.lang.ClassNotFoundException: com.cyanogenmod.eleven.ElevenApplication
E/AndroidRuntime( 1979): at java.lang.Class.classForName(Native Method)
E/AndroidRuntime( 1979): at java.lang.BootClassLoader.findClass(ClassLoader.java:781)
E/AndroidRuntime( 1979): at java.lang.BootClassLoader.loadClass(ClassLoader.java:841)
E/AndroidRuntime( 1979): at java.lang.ClassLoader.loadClass(ClassLoader.java:504)
E/AndroidRuntime( 1979): ... 13 more
E/AndroidRuntime( 1979): Caused by: java.lang.NoClassDefFoundError: Class not found using the boot class loader; no stack available
Click to expand...
Click to collapse
coliiibri said:
Hello,
My phone keeps crashing and rebooting. When I shut it down it freezes on battery charging screen. It can only be unblocked via adb or by pushing power+volumeUP+volumeDOWN.
Click to expand...
Click to collapse
when battery discharges completely, its normal getting stuck in TWRP until you use the buttons to restart. Its a bug that was never fixed i guess.
Phone crashing and rebooting with no reason its another problem.
Im using TWRP 2.7.1.0 in mine with no problems, but it varies from phone to phone. Im also using cm13 with no major problems.
PS: you installation might be corrupted as the system keeps trying to open "Eleven.apk" but its not there.
kativiti said:
when battery discharges completely, its normal getting stuck in TWRP until you use the buttons to restart. Its a bug that was never fixed i guess.
Phone crashing and rebooting with no reason its another problem.
Im using TWRP 2.7.1.0 in mine with no problems, but it varies from phone to phone. Im also using cm13 with no major problems.
PS: you installation might be corrupted as the system keeps trying to open "Eleven.apk" but its not there.
Click to expand...
Click to collapse
Thank you for your answer.
I have tried using the TWRP and cm13 files you gave me the links to, but the same problem occurs (crashing and rebooting).
What do you mean by "installation is corrupted"? What could have caused it?
I have done it in that order
fastboot flash recovery twrp-2.7.1.0-20140802-memul.img
fastboot erase cache
adb push cm-13.0-20160910-UNOFFICIAL-memul.zip /external_sd
factory wipe
install the zip file
wipe cache/dalvik
reboot
Click to expand...
Click to collapse
coliiibri said:
Thank you for your answer.
I have tried using the TWRP and cm13 files you gave me the links to, but the same problem occurs (crashing and rebooting).
What do you mean by "installation is corrupted"? What could have caused it?
I have done it in that order
Click to expand...
Click to collapse
can you tell me at what point the phone crashes?
kativiti said:
can you tell me at what point the phone crashes?
Click to expand...
Click to collapse
It doesn't always happen at the same time.
Occasionally, if the phone had been turned off for a long time, it can last up to 15 minutes.
Most of the time it does not even complete booting.
coliiibri said:
It doesn't always happen at the same time.
Occasionally, if the phone had been turned off for a long time, it can last up to 15 minutes.
Most of the time it does not even complete booting.
Click to expand...
Click to collapse
it seems more like a battery issue. Not holding the charge anymore.
kativiti said:
it seems more like a battery issue. Not holding the charge anymore.
Click to expand...
Click to collapse
That could explain why it gets stuck in TWRP even when the battery is full.
And recovery doesn't need as much power so it holds well.
But then what does the crash with Eleven.apk, present in all the logs, mean? It is irrelevant to the crashes?
coliiibri said:
That could explain why it gets stuck in TWRP even when the battery is full.
And recovery doesn't need as much power so it holds well.
But then what does the crash with Eleven.apk, present in all the logs, mean? It is irrelevant to the crashes?
Click to expand...
Click to collapse
eleven.apk its the cm media player. its hard to tell but if the packages are loaded in alphabetic order and the phone starts to shut down it could give a false crash log.
to be sure, you could try to install the original ROM and if same appends, there's a good chance its the battery. If not, could be something worst.