Segmentation Fault when deploying to handset

Question

I've got a Galaxy Nexus and today it started to give me a Segmentation fault error when deploying to it:

[2011-12-07 16:19:17 - Flinders Lite] Android Launch!
[2011-12-07 16:19:17 - Flinders Lite] adb is running normally.
[2011-12-07 16:19:17 - Flinders Lite] Performing com.istudentgroup.flinders.lite.activity.MainMenuActivity activity launch
[2011-12-07 16:19:20 - Flinders Lite] Uploading Flinders Lite.apk onto device '0146914B19021011'
[2011-12-07 16:19:23 - Flinders Lite] Installing Flinders Lite.apk...
[2011-12-07 16:19:25 - Flinders Lite] Success!
[2011-12-07 16:19:25 - Flinders Lite] Starting activity com.istudentgroup.flinders.lite.activity.MainMenuActivity on device 0146914B19021011
[2011-12-07 16:19:26 - Flinders Lite] ActivityManager: Segmentation fault

I can open a shell in to the handset and can navigate the directory structure and the phone seems to be operating normally otherwise.

Does anyone know what is going on? How do I fix it?

Logcat output : http://pastebin.com/VxGdAbap

Is there anything useful in LogCat around when the activity starts? — Emyr, Dec 07 '11 at 16:27
Does your app work in the emulator or on another device? Are you sure it isn't your code? — Andrew Rasmussen, Dec 07 '11 at 16:32
yeah, tried different devices, usb lead and code. have rebooted everything multiple times — Martyn, Dec 07 '11 at 16:34
I'm getting this also on my Asus Prime. Was working fine, now for any APK: adb install whatever.apk gives me Segmentation fault... — barkside, Jul 02 '12 at 11:01

score 0 · Answer 1 · edited Apr 27 '18 at 10:02

0

I also had the issue.
Make sure your sdk and adt are of latest version.
If the issue still there then its due to the rom installed.

Some custom roms may leads to this issue.

Installation of busybox may lead to this issue.

Corrupted OS installation.

This can be solved by wiping all data and putting stock rom back.

edited Apr 27 '18 at 10:02

Rahul Sharma

2,867
2
27
40

answered Feb 19 '13 at 13:08

Vishnudev K

2,874
3
27
42

score 0 · Answer 2 · answered Dec 07 '11 at 18:07

0

Have you updated the Android SDK / ADB / Eclipse recently? I had a similar problem after an update due to inconsistency between versions. The problem was corrected after forcing eclipse to check for updates (and install them) of anything that I had installed.

answered Dec 07 '11 at 18:07

jap1968

7,747
1
30
37

Not updates recently. It was literally working and then it stopped. No reason I can tell as to why. I'm baffled and thinking it's a hardware issue at this stage – Martyn Dec 07 '11 at 18:28

score 0 · Accepted Answer · answered Dec 08 '11 at 08:57

0

Reflashing the stock image, using tools from the superboot from modaco worked. I used the 4.0.1 (ITL41F) version as this includes the recently released volume bug fix.

answered Dec 08 '11 at 08:57

Martyn

16,432
24
71
104

Segmentation Fault when deploying to handset

3 Answers3

Linked