Terminal Emulator FC's after rom install - why?

[Guest twrock]

I've been messing around with the Tre ROM, testing some stuff out. An annoying problem I've hit is after putting Terminal Emulator into /data/app, then installing the rom, it fc's continually. I have to then uninstall it via Market and reinstall it. Then it works great. But it seems to be the only app that has that problem. All the other apps I put into /data work just fine.

What am I missing?

[Guest Simon O]

I've been messing around with the Tre ROM, testing some stuff out. An annoying problem I've hit is after putting Terminal Emulator into /data/app, then installing the rom, it fc's continually. I have to then uninstall it via Market and reinstall it. Then it works great. But it seems to be the only app that has that problem. All the other apps I put into /data work just fine.

What am I missing?

libandroidterm.so is needed in /system/lib

you can get this from the apk directly (rename to zip and open it. the lib is in a folder called armeabi or something like that. )

edit: fix spelling. note to self, enable the spell check in touchpal..

Edited September 7, 2010 by flibblesan

[Guest twrock]

libandroidterm.so is needed is /system/lib

you can get this from the apk directly (rename to zip and open it. the lib is in a folder called armabi or something like that. )

Wow, where do you find all this stuff! :P Thanks.

If you happen to see this reply, I'd like to make sure ADW doesn't have something like that going on. I packed a rom recently with the latest version of ADW (I think it was 1.1.4) and weird things were happening with it. I chalked it up to "pilot error" (i.e. my error) and gave up. But it'd be nice to confirm that all that is needed is to drop the standalone version into /system/app as Launcher.apk and have it work correctly. Is that true?

Thanks again.

Edit: Should I be able to find libandroidterm.so in /system/lib if it is installed correctly and runs correctly. It doesn't seem to be there.

Edited September 7, 2010 by twrock

[Guest Simon O]

Wow, where do you find all this stuff! :P Thanks.

If you happen to see this reply, I'd like to make sure ADW doesn't have something like that going on. I packed a rom recently with the latest version of ADW (I think it was 1.1.4) and weird things were happening with it. I chalked it up to "pilot error" (i.e. my error) and gave up. But it'd be nice to confirm that all that is needed is to drop the standalone version into /system/app as Launcher.apk and have it work correctly. Is that true?

Thanks again.

Edit: Should I be able to find libandroidterm.so in /system/lib if it is installed correctly and runs correctly. It doesn't seem to be there.

I had the same problem myself when adding Android Term to my roms. The lib will be libandroidterm.so if you are using Jackpal Android Term, or libterm.so if you are using the standard Android Term. Either will be inside /system/lib/ if the apk was installed correctly. When you install them from the market they copy the lib into that folder.

Latest system version of ADW is 1.1.3, latest market version is 1.1.4. There is a system version of 1.1.4 as used by Cyanogenmod 6 roms but a lot of people are reporting that it's not running right. I'd use ADW 1.1.3 personally. It's stable and runs nice.

[Guest twrock]

I had the same problem myself when adding Android Term to my roms. The lib will be libandroidterm.so if you are using Jackpal Android Term, or libterm.so if you are using the standard Android Term. Either will be inside /system/lib/ if the apk was installed correctly. When you install them from the market they copy the lib into that folder.

Latest system version of ADW is 1.1.3, latest market version is 1.1.4. There is a system version of 1.1.4 as used by Cyanogenmod 6 roms but a lot of people are reporting that it's not running right. I'd use ADW 1.1.3 personally. It's stable and runs nice.

Well, as strange and unbelievable as it sounds, libanroidterm.so simply wasn't there, and terminal appeared to be running normally. So I don't know where it was. But in any case, I started over and worked it out the way you suggested, repackaged, reflashed, restarted, and...... success! Terminal starts and runs as expected without any fc's and without having to reinstall.