Jump to content

Welcome to CyanogenMod

Welcome to our forum. Like most online communities you must register to post, but don't worry this is a simple free process that requires minimal information for you to signup. Be a part of the CyanogenMod Forum by signing in or creating an account. You can even sign in with your Facebook or Twitter account.
  • Start new topics and reply to others
  • Subscribe to topics and forums to get automatic updates
  • Get your own profile and make new friends
  • Download files attached to the forum.
  • Customize your experience here
  • Share your CyanogenMod experience!
Guest Message by DevFuse
 

Terminal Emulator Not Working Anymore


  • Please log in to reply
5 replies to this topic

#1 Henkir

Henkir
  • Members
  • 11 posts
  • Country:
    se - Sweden
  • Location:
    Sweden
  • Device Model:
    Samsung Galaxy S III
  • CM Version:
    10.1 - nightly
  • Recovery Image:
    ClockworkMod

Posted 10 January 2013 - 07:19 AM

I'm running the nightly cm-10.1-20130109-NIGHTLY-i9300 and wanted to start Terminal emulator yesterday and it just crashed. I've used it before but that was quite a while ago, I don't know when this problem started occurring as I have been updating to new nightlies quite frequently using the CyanogenMod update feature.

I'm using gapps 121212 and have tried to restart the phone but I did not wipe.

Does anyone have a solution or know what is causing this? It's nice not having to use ADB if I just want to check something quickly.

Below is a piece of logcat. If you need more, let me know.

Spoiler


#2 slashwalker

slashwalker
  • Members
  • 4 posts
  • Country:
    de - Germany
  • Device Model:
    Samsung Galaxy S3 i9300
  • CM Version:
    CM 10.1 Nightly
  • Recovery Image:
    Stock

Posted 10 January 2013 - 11:17 AM

Same problem here, if i start terminal a popup occurs "terminal has been quit". I'm new to android at all, I have my s3 since about one week. Startet with build 20130105 and updated daily till 20130109. Terminal didn't work in any of these builds

#3 r2d2-aku2

r2d2-aku2
  • Members
  • 75 posts
  • Country:
    us - United States
  • Device Model:
    HeroC
  • CM Version:
    cm7 nightlies
  • Recovery Image:
    ClockworkMod

Posted 10 January 2013 - 12:56 PM

I think I read somewhere that if you delete term.apk and go to the play store and install from there it will work. I haven't tried it myself.

#4 slashwalker

slashwalker
  • Members
  • 4 posts
  • Country:
    de - Germany
  • Device Model:
    Samsung Galaxy S3 i9300
  • CM Version:
    CM 10.1 Nightly
  • Recovery Image:
    Stock

Posted 10 January 2013 - 01:25 PM

As said, I'm new to android. Where is term.apk stored?

edit: got it /system/app

Works now. I opened the built-in explorer (with root perms) searched for term.apk and clicked on it. it asked for updating, I confirmed update and now it works. Great!

Edited by slashwalker, 10 January 2013 - 01:28 PM.


#5 Henkir

Henkir
  • Members
  • 11 posts
  • Country:
    se - Sweden
  • Location:
    Sweden
  • Device Model:
    Samsung Galaxy S III
  • CM Version:
    10.1 - nightly
  • Recovery Image:
    ClockworkMod

Posted 10 January 2013 - 06:15 PM

I inactivated it in app settings and then went to Play store where I activated it again. It started working, but I had also installed nightly 20130110 without trying to start Terminal Emulator before inactivating/activating it. So I don't know exactly what fixed it. A friend who has a Nexus 4 also had the Terminal Emulator crash when running 20130109 but not with 20130110, and he did not inactivate/activate it.

Just glad it work. Thanks for the help.

#6 andrewpayne

andrewpayne
  • Donators
  • 36 posts
  • Country:
    uk - United Kingdom
  • Location:
    London UK
  • Device Model:
    Samsung S4 GT-I9505
  • CM Version:
    10.2 Nightlies
  • Recovery Image:
    ClockworkMod

Posted 11 January 2013 - 04:25 PM

I can confirm this was fixed in yesterday's nightly (CM 10.1 BUILD 2013-01-10)