[Q] Every app, including launcher, crashes. - Verizon Samsung Galaxy S 4

Hi,
It appears I've gotten myself into a little predicament. As the title indicates, after restarting my Galaxy S4 last night, everything crashes, basically rendering the device useless. The launcher is stuck in a crash loop, as well as any app I open via adb. I am currently running a rooted android 4.2.2 on the stock TouchWiz ROM which I believe is the MI1 build for my GS4.
I do have access to adb as well as su, so hopefully someone can help me through this.
A little more info on the things I've tried:
My initial thought as to why this was happening was because I froze some bloatware via App Quarantine. During this process, I disabled a few keyboards since SwiftKey would never be the default when I restarted Android, hoping that it would just eventually just default to SwiftKey. However, I also recently put a magnet on the back of my phone for use with a magnetic car mount, but I don't believe this is causing the issue.
I first tried disabling Xposed, this had no effect.
Next, I tried to install another keyboard through adb.
I tried to install an alternative launcher, this crashed as well.
I booted into safe mode, still no luck.
I tried launching apps through the monkey command, they crashed after a few seconds as well.
I believe my logcat points to the following error whenever anything crashes, however I cannot be certain.
Code:
E/AndroidRuntime( 8123): FATAL EXCEPTION: main
E/AndroidRuntime( 8123): java.lang.NullPointerException
E/AndroidRuntime( 8123): at android.view.inputmethod.InputMethodManager.startInputInner(InputMethodManager.java:1203)
E/AndroidRuntime( 8123): at android.view.inputmethod.InputMethodManager.onWindowFocus(InputMethodManager.java:1411)
E/AndroidRuntime( 8123): at android.view.ViewRootImpl$ViewRootHandler.handleMessage(ViewRootImpl.java:3298)
E/AndroidRuntime( 8123): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 8123): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 8123): at android.app.ActivityThread.main(ActivityThread.java:5329)
E/AndroidRuntime( 8123): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 8123): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 8123): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1102)
E/AndroidRuntime( 8123): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:869)
E/AndroidRuntime( 8123): at dalvik.system.NativeStart.main(Native Method)
Based on the presumed error, I made one last attempt and tried to change the keyboard via adb but I got the following error:
Code:
>adb shell ime list
Error: Could not access the Input Method Manager. Is the system running?
I have attached my error logcat, as well as the verbose logcat.
I'm basically at a loss here. I do have most of the bare-minimum, important data backed up with Titanium Backup, but I really don't want it to come to the point where I have to wipe my phone. Any help is appreciated.
Thanks.

Have you tried the No-Wipe Stock Image for odin?

bamige1 said:
Have you tried the No-Wipe Stock Image for odin?
Click to expand...
Click to collapse
I have not tried this yet. I had completely forgotten about those. I'll give it a shot and report back.

bamige1 said:
Have you tried the No-Wipe Stock Image for odin?
Click to expand...
Click to collapse
I just went ahead with the no wipe image and the problem still persists. I'm at a complete loss as of what to do next.
EDIT:
The logcat is giving this error as well:
Code:
E/ViewRootImpl( 875): sendUserActionEvent() mView == null
E/AndroidRuntime( 9913): FATAL EXCEPTION: main
E/AndroidRuntime( 9913): java.lang.NullPointerException
E/AndroidRuntime( 9913): at android.view.inputmethod.InputMethodManager.s
tartInputInner(InputMethodManager.java:1203)
E/AndroidRuntime( 9913): at android.view.inputmethod.InputMethodManager.o
nWindowFocus(InputMethodManager.java:1411)
E/AndroidRuntime( 9913): at android.view.ViewRootImpl$ViewRootHandler.han
dleMessage(ViewRootImpl.java:3298)
E/AndroidRuntime( 9913): at android.os.Handler.dispatchMessage(Handler.ja
va:99)
E/AndroidRuntime( 9913): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 9913): at android.app.ActivityThread.main(ActivityThrea
d.java:5329)
E/AndroidRuntime( 9913): at java.lang.reflect.Method.invokeNative(Native
Method)
E/AndroidRuntime( 9913): at java.lang.reflect.Method.invoke(Method.java:5
11)
E/AndroidRuntime( 9913): at com.android.internal.os.ZygoteInit$MethodAndA
rgsCaller.run(ZygoteInit.java:1102)
E/AndroidRuntime( 9913): at com.android.internal.os.ZygoteInit.main(Zygot
eInit.java:869)
E/AndroidRuntime( 9913): at dalvik.system.NativeStart.main(Native Method)

Related

About invalid surfaceDestroyed(...) call ???

I'm trying to make the sample camera application on Nexus One.
Until now, the programming is not commercial and only test program.
I referenced the source code of android 1.5 platform.
The test code that I made is working well on the other android 1.5 phone.
But the code is not working on Nexus One.
I checked the log of Nexus One.
If I press shutter button, surfaceChanged(...) is called on the android 1.5 phone.
However, surfaceDestroyed(...) is called on Nexus One.
I don't why suraceDestroyed(...) is called.
If anybody has information about this problem, please let me know that.
Thanks in advance.
Hi,
I believe that there's a great change between 1.5 and 2.1 APIs. Rarely apps made for 1.5 are compatible with 2.1. Though, I'm definitely not at expert at this. Why not code a check to use which method depending on the version of the phone?
Ok.....Maybe, there is a great difference between 1.5 and 2.0.
However, I think that there is only little difference for camera application.
Maybe, you agree that the example code of android sdk 2.0 would work well on Nexus One.
But the CameraPreview.java doesn't work on Nuxus.
CameraPreview.java Example(Anroid SDK 2.0) not working......
I'm trying to program my camera application on Nexus One,
But the example code of android sdk 2.0 isn't working.
The example source is the CamraPreview.java.
Maybe, the preview size is the problem but I don't know how to fix the problem.
I include the log of CameraView.java on Nexus One.
If anybody has the information about this problem, please let me know that.
Thanks in advance.
========> The log of CameraPreview.java on Nexus One
E/QualcommCameraHardware( 52): Invalid preview size requested: 533x295
I/QualcommCameraHardware( 52): Set zoom=0
D/AndroidRuntime( 2551): Shutting down VM
W/dalvikvm( 2551): threadid=3: thread exiting with uncaught exception (group=0x4001b180)
E/AndroidRuntime( 2551): Uncaught handler: thread main exiting due to uncaught exception
E/AndroidRuntime( 2551): java.lang.RuntimeException: setParameters failed
E/AndroidRuntime( 2551): at android.hardware.Camera.native_setParameters(Native Method)
E/AndroidRuntime( 2551): at android.hardware.Camera.setParameters(Camera.java:619)
E/AndroidRuntime( 2551): at com.example.android.apis.graphics.Preview.surfaceChanged(CameraPreview.java:90)
E/AndroidRuntime( 2551): at android.view.SurfaceView.updateWindow(SurfaceView.java:460)
E/AndroidRuntime( 2551): at android.view.SurfaceView.dispatchDraw(SurfaceView.java:287)
E/AndroidRuntime( 2551): at android.view.ViewGroup.drawChild(ViewGroup.java:1529)
E/AndroidRuntime( 2551): at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1258)
E/AndroidRuntime( 2551): at android.view.View.draw(View.java:6538)
E/AndroidRuntime( 2551): at android.widget.FrameLayout.draw(FrameLayout.java:352)
E/AndroidRuntime( 2551): at android.view.ViewGroup.drawChild(ViewGroup.java:1531)
E/AndroidRuntime( 2551): at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1258)
E/AndroidRuntime( 2551): at android.view.View.draw(View.java:6538)
E/AndroidRuntime( 2551): at android.widget.FrameLayout.draw(FrameLayout.java:352)
E/AndroidRuntime( 2551): at com.android.internal.policy.impl.PhoneWindow$DecorView.draw(PhoneWindow.java:1830)
E/AndroidRuntime( 2551): at android.view.ViewRoot.draw(ViewRoot.java:1349)
E/AndroidRuntime( 2551): at android.view.ViewRoot.performTraversals(ViewRoot.java:1114)
E/AndroidRuntime( 2551): at android.view.ViewRoot.handleMessage(ViewRoot.java:1633)
E/AndroidRuntime( 2551): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 2551): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 2551): at android.app.ActivityThread.main(ActivityThread.java:4363)
E/AndroidRuntime( 2551): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 2551): at java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime( 2551): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
E/AndroidRuntime( 2551): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
E/AndroidRuntime( 2551): at dalvik.system.NativeStart.main(Native Method)
I/Process ( 74): Sending signal. PID: 2551 SIG: 3
I/dalvikvm( 2551): threadid=7: reacting to signal 3
I/dalvikvm( 2551): Wrote stack trace to '/data/anr/traces.txt'
I/Process ( 2551): Sending signal. PID: 2551 SIG: 9
E/JavaBinder( 74): !!! FAILED BINDER TRANSACTION !!!
Can you please post all your logs here and don't create new thread for each problem you have.
Thanks.
blue0sky said:
E/QualcommCameraHardware( 52): Invalid preview size requested: 533x295
...
E/AndroidRuntime( 2551): at com.example.android.apis.graphics.Preview.surfaceChanged(CameraPreview.java:90)
Click to expand...
Click to collapse
You're right, it's the preview size. http://developer.android.com/reference/android/hardware/Camera.Parameters.html states:
Different devices may have different camera capabilities, such as picture size or flash modes. The application should query the camera capabilities before setting parameters.
Click to expand...
Click to collapse
You want to use
Code:
public List<Camera.Size> getSupportedPreviewSizes ()
to get a list of supported sizes and use one of those, instead of hardcoding the values.

crash while installing most of apps

this is logcat from installing Titanium Backup for example:
Code:
W/ActivityManager( 328): No content provider found for: null
W/dalvikvm( 328): threadid=12: thread exiting with uncaught exception (group=0x2aac8578)
E/PackageManager( 328): Couldn't create temp file for downloaded package file.
E/AndroidRuntime( 328): *** FATAL EXCEPTION IN SYSTEM PROCESS: PackageManager
E/AndroidRuntime( 328): java.lang.NullPointerException
E/AndroidRuntime( 328): at com.android.server.PackageManagerService$FileInstallArgs.c
reateCopyFile(PackageManagerService.java:5011)
E/AndroidRuntime( 328): at com.android.server.PackageManagerService$FileInstallArgs.c
opyApk(PackageManagerService.java:5019)
E/AndroidRuntime( 328): at com.android.server.PackageManagerService$InstallParams.han
dleStartCopy(PackageManagerService.java:4815)
E/AndroidRuntime( 328): at com.android.server.PackageManagerService$HandlerParams.sta
rtCopy(PackageManagerService.java:4666)
E/AndroidRuntime( 328): at com.android.server.PackageManagerService$PackageHandler.do
HandleMessage(PackageManagerService.java:496)
E/AndroidRuntime( 328): at com.android.server.PackageManagerService$PackageHandler.ha
ndleMessage(PackageManagerService.java:441)
E/AndroidRuntime( 328): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 328): at android.os.Looper.loop(Looper.java:130)
E/AndroidRuntime( 328): at android.os.HandlerThread.run(HandlerThread.java:60)
cleaning dalvik cache didn't help... i was deleting a few system apps, maby thats a problem's reason? Which app if yes?
did you solve the problem? I've the same one!

Need some help

Hello,
Im working on porting an Evo 4g rom to the Thunderbolt. Problems im running into deal with 4g and WiMax differences in the rom. I dont know what to change or where to look as Im new to this. The phone works making and reciving calls. Im just stuck on data.
I do have a log cat with:
E/AndroidRuntime( 1715): FATAL EXCEPTION: main
E/AndroidRuntime( 1715): java.lang.NoClassDefFoundError: com.android.internal.telephony.cat.CatService
E/AndroidRuntime( 1715): at com.android.stk.StkAppService.onStart(StkAppService.java:180)
E/AndroidRuntime( 1715): at android.app.Service.onStartCommand(Service.java:428)
E/AndroidRuntime( 1715): at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:2160)
E/AndroidRuntime( 1715): at android.app.ActivityThread.access$2800(ActivityThread.java:123)
E/AndroidRuntime( 1715): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1002)
E/AndroidRuntime( 1715): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 1715): at android.os.Looper.loop(Looper.java:130)
E/AndroidRuntime( 1715): at android.app.ActivityThread.main(ActivityThread.java:3835)
E/AndroidRuntime( 1715): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 1715): at java.lang.reflect.Method.invoke(Method.java:507)
E/AndroidRuntime( 1715): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)
E/AndroidRuntime( 1715): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599)
E/AndroidRuntime( 1715): at dalvik.system.NativeStart.main(Native Method)
I know i have some apk editing to do for the menu stuff but im focusing on just getting the data to work.
Thanks for pointing me in the direction I need to go.

[Q] cm 10.1 2m contacts has stopped when accessing the dialer

If you click dialer you get error message that unfortunately contacts has stopped.
I have tried wipe cache, wipe dalvik fix permissions. This is on a fresh installed of cm10.1 2m from stock rooted ICS build. I did import my contacts from my back up pro. Only thing left I can think of thanks in advance for any help.
CM question answers discussion thread on the forum .
jje
Wipe contacts and dialler data
slap20 said:
Wipe contacts and dialler data
Click to expand...
Click to collapse
I had seen thar suggested. How do I wipe indivual data caches? Or do you mean deleting all contacta indivdual?
Settings/apps/all......find the apks, tap on them, hit wipe data
Thank you so much! That fixed it. So glad I didn't have to reflash
slaphead20 said:
Settings/apps/all......find the apks, tap on them, hit wipe data
Click to expand...
Click to collapse
Hi guys,
I'm sorry but I still have this problem. I wiped data from everything that may be related (contacts, dialer, google contacts, dialer/contacts storage) but still no joy.
I flashed the phone with CM 10.1 M3 a few days ago but frankly I don't remember I've ever seen the stock dialer open.
Logcat says:
W/dalvikvm( 8958): threadid=1: thread exiting with uncaught exception (group=0x40b54930)
E/AndroidRuntime( 8958): FATAL EXCEPTION: main
E/AndroidRuntime( 8958): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.contacts/com.android.contacts.activities.DialtactsActivity}: java.lang.NullPointerException
E/AndroidRuntime( 8958): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2307)
E/AndroidRuntime( 8958): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2357)
E/AndroidRuntime( 8958): at android.app.ActivityThread.access$600(ActivityThread.java:153)
E/AndroidRuntime( 8958): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1247)
E/AndroidRuntime( 8958): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 8958): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 8958): at android.app.ActivityThread.main(ActivityThread.java:5226)
E/AndroidRuntime( 8958): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 8958): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 8958): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:795)
E/AndroidRuntime( 8958): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:562)
E/AndroidRuntime( 8958): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 8958): Caused by: java.lang.NullPointerException
E/AndroidRuntime( 8958): at com.android.contacts.activities.DialtactsActivity.setupDialer(DialtactsActivity.java:747)
E/AndroidRuntime( 8958): at com.android.contacts.activities.DialtactsActivity.onCreate(DialtactsActivity.java:530)
E/AndroidRuntime( 8958): at android.app.Activity.performCreate(Activity.java:5104)
E/AndroidRuntime( 8958): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1080)
E/AndroidRuntime( 8958): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2261)
E/AndroidRuntime( 8958): ... 11 more
Any ideas or should I buy an iPhone?
Aviopene said:
Hi guys,
I'm sorry but I still have this problem. I wiped data from everything that may be related (contacts, dialer, google contacts, dialer/contacts storage) but still no joy.
I flashed the phone with CM 10.1 M3 a few days ago but frankly I don't remember I've ever seen the stock dialer open.
Logcat says:
W/dalvikvm( 8958): threadid=1: thread exiting with uncaught exception (group=0x40b54930)
E/AndroidRuntime( 8958): FATAL EXCEPTION: main
E/AndroidRuntime( 8958): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.contacts/com.android.contacts.activities.DialtactsActivity}: java.lang.NullPointerException
E/AndroidRuntime( 8958): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2307)
E/AndroidRuntime( 8958): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2357)
E/AndroidRuntime( 8958): at android.app.ActivityThread.access$600(ActivityThread.java:153)
E/AndroidRuntime( 8958): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1247)
E/AndroidRuntime( 8958): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 8958): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 8958): at android.app.ActivityThread.main(ActivityThread.java:5226)
E/AndroidRuntime( 8958): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 8958): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 8958): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:795)
E/AndroidRuntime( 8958): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:562)
E/AndroidRuntime( 8958): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 8958): Caused by: java.lang.NullPointerException
E/AndroidRuntime( 8958): at com.android.contacts.activities.DialtactsActivity.setupDialer(DialtactsActivity.java:747)
E/AndroidRuntime( 8958): at com.android.contacts.activities.DialtactsActivity.onCreate(DialtactsActivity.java:530)
E/AndroidRuntime( 8958): at android.app.Activity.performCreate(Activity.java:5104)
E/AndroidRuntime( 8958): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1080)
E/AndroidRuntime( 8958): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2261)
E/AndroidRuntime( 8958): ... 11 more
Any ideas or should I buy an iPhone?
Click to expand...
Click to collapse
Found the cause of the problem. It was the theme's fault! I was (stupidly, I admit it) using an old CM7 theme (goo.gl -slash- 5wyP4) that was also working on CM9 but not in CM10.1. Apparently the stack trace was saying that the dialer activity failed to draw the interface.
Cheers
Avio

[Q] Help implementing a settings toggle!

Hi,
I've been trying to implement a toggle for my Galaxy Ace II X (running ICS 4.0.4). I wish for the toggle to allow the enabling of the "config_unplugTurnsOnScreen" boolean. I used this DIFF guide for reference (yes, I DID sort through the several mods in the DIFF guide) because I previously had success with the CRT animation toggle on that same page. (I substituted a lot of the AOSP lockscreen code for Unplug Screen On code) Instead of referencing to /system/framework/services.jar/smali/com/android/server/PowerManagerService$BrightnessState.smali, I referenced to the PowerManagerService$BatteryReceiver.smali in the same directory (because it is the only smali I could find that mentioned "mUnplugTurnsOnScreen"). I first modded the services.jar, and I used $3100 for the access (I compared the access used for the CRT animation with the rest of the services.jar and I got found a common factor, so I searched for the factor in my services.jar and I found the access I was looking for). It booted fine, no problems at all. Then I modded the SecSettings.apk. I thought I did a pretty good job with it. Pushed it to my device. When I opened the Display Settings and clicked on the toggle, Settings FCed. Same happened with the CRT animation toggle that I had previously implemented. Logcats revealed this:
E/AndroidRuntime( 2805): FATAL EXCEPTION: main
E/AndroidRuntime( 2805): java.lang.NoSuchFieldError: com.android.settings.DisplaySettings.mUnplugScreenOn
E/AndroidRuntime( 2805): at com.android.settings.DisplaySettings.onPreferenceTreeClick(DisplaySettings.java:773)
E/AndroidRuntime( 2805): at android.preference.Preference.performClick(Preference.java:949)
E/AndroidRuntime( 2805): at android.preference.PreferenceScreen.onItemClick(PreferenceScreen.java:202)
E/AndroidRuntime( 2805): at android.widget.AdapterView.performItemClick(AdapterView.java:292)
E/AndroidRuntime( 2805): at android.widget.AbsListView.performItemClick(AbsListView.java:1394)
E/AndroidRuntime( 2805): at android.widget.AbsListView$PerformClick.run(AbsListView.java:3024)
E/AndroidRuntime( 2805): at android.widget.AbsListView$1.run(AbsListView.java:3830)
E/AndroidRuntime( 2805): at android.os.Handler.handleCallback(Handler.java:605)
E/AndroidRuntime( 2805): at android.os.Handler.dispatchMessage(Handler.java:92)
E/AndroidRuntime( 2805): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 2805): at android.app.ActivityThread.main(ActivityThread.java:4517)
E/AndroidRuntime( 2805): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 2805): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 2805): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:993)
E/AndroidRuntime( 2805): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:760)
E/AndroidRuntime( 2805): at dalvik.system.NativeStart.main(Native Method)
E/android.os.Debug( 1523): [email protected] > dumpstate -k -t -n -z -d -o /data/log/dumpstate_app_error
Click to expand...
Click to collapse
I don't know what to do. I tried modifying all the code related to mUnplugScreenOn, but I'm dumbfounded. Somebody please help me out here. Or at least, lead me in the right direction. Though, I would prefer the first choice. Anyways, here are my SecSettings.apk and services.jar decompiled and zipped up. They might be a bit messy because I have numerous mods applied to them. This is my first real mod I've tried doing without any other guides or threads related to it. I would really appreciate the help. I think if I could knock down this mod, I discover a whole new realm of modding.

Categories

Resources