ROM problems thread

[CNexus]

Hi everyone, I'm making this so that any problems with ROMS can be discussed here, and any associated fixes. This way we don't clutter the actual ROM threads and all the problems/fixes are in one place. :good:



I'll start it off.
I just ported over a 4.1.2 ROM but the soft keyboard FC's literally every 5 seconds. Any ideas? I tried pulling a logcat from the computer and it says "Unable to open log device '/dev/log/main': No such file or directory

Attached is a screenshot.
I'm gonna try to install a different keyboard from the playstore and see if that one works.

 

[bilgerryan]

Hi everyone, I'm making this so that any problems with ROMS can be discussed here, and any associated fixes. This way we don't clutter the actual ROM threads and all the problems/fixes are in one place. :good:



I'll start it off.
I just ported over a 4.1.2 ROM but the soft keyboard FC's literally every 5 seconds. Any ideas? I tried pulling a logcat from the computer and it says "Unable to open log device '/dev/log/main': No such file or directory

Attached is a screenshot.
I'm gonna try to install a different keyboard from the playstore and see if that one works.

I had that same problem on one of my first ICS ports, just sub it out for any of the working ones on the Shift. Don't forget to switch out the lib too.

 

[BigSplit]

I would say the same thing as ryan, as far as the keyboard is concerned.

And as far as the logcat problem, the only time i have ever had that error was when it was a bad flash. Googling the error gives you a bunch of different reasons this error could happen. I doubt it is a kernel problem, as some sites suggests, because I'm guessing you are using one of the kernels we already have and none of the other roms have the same problem. So I would look into one of the other suggestions that pop up when googling.

 

[CNexus]

Yeah, I'll look into it when I get home today. And i know it cant be a bad flash because i wiped 10 times before flashing it.

Sent from my PG06100

 

[CNexus]

Well i think I found the error. I found a post on stackoverflow that led me to the etc/init.d folder...and in one of the files there I found this

rm /dev/log/main

Now why that was in there, i have no idea. Hopefully that fixes that part and then I'll just swap out the soft keyboard and Latin_ime.so to fix the AOSP keyboard and all should be good....so if all goes well, expect a new port in the dev section :good:

Sent from my PG06100

 

[strapped365]

I just fresh flashed a cm build with the wrong gapps and this force close happened every few seconds.

Sent from my myTouch_4G_Slide using Tapatalk 2

 

[bilgerryan]

I just fresh flashed a cm build with the wrong gapps and this force close happened every few seconds.

Sent from my myTouch_4G_Slide using Tapatalk 2

Yeah 4.2 GApps really screw stuff up on 4.1. I went like three days trying to get JBv6 to work right and was getting really pissed when I realized I was using the wrong GApps.:banghead:

 

[CNexus]

I just fresh flashed a cm build with the wrong gapps and this force close happened every few seconds.

Sent from my myTouch_4G_Slide using Tapatalk 2

Hmm, I flashed the gapps that the original dev linked to
I'll try flashing just the rom and see if thats the problem

Sent from my PG06100

 

[CNexus]

well to update you guys on this, it seems like its the LatinIME itself, the keyboard kept FCing even after a x10 wipe with no gapps flashed

bilgerryan (or anyone else who knows), can you go into more detail about how I can replace it? sorry, but this is still my first port

 

[bilgerryan]

well to update you guys on this, it seems like its the LatinIME itself, the keyboard kept FCing even after a x10 wipe with no gapps flashed

bilgerryan (or anyone else who knows), can you go into more detail about how I can replace it? sorry, but this is still my first port

Really easy, replace the apk with one that you know works... For this example we'll use the 4.2 keyboard from my ROM. Delete both the apk and the libjniLatin_IME.so from system/lib. Replace with the working apk and the corresponding lib (libjniLatin_IMEgoogle.so or something close to that) and rezip. If that doesn't work see if you can get a flashable like the Xperia T keyboard to work after boot. If that doesn't work, there is probably a major problem.

 

[strapped365]

Really easy, replace the apk with one that you know works... For this example we'll use the 4.2 keyboard from my ROM. Delete both the apk and the libjniLatin_IME.so from system/lib. Replace with the working apk and the corresponding lib (libjniLatin_IMEgoogle.so or something close to that) and rezip. If that doesn't work see if you can get a flashable like the Xperia T keyboard to work after boot. If that doesn't work, there is probably a major problem.

I stumbled on an IME modding thread to quit that force close once, so I'm sure ill find it again. Let me go see my best friend Google and see if I can stumble there again.

Sent from my myTouch_4G_Slide using Tapatalk 2

 

[CNexus]

Really easy, replace the apk with one that you know works... For this example we'll use the 4.2 keyboard from my ROM. Delete both the apk and the libjniLatin_IME.so from system/lib. Replace with the working apk and the corresponding lib (libjniLatin_IMEgoogle.so or something close to that) and rezip. If that doesn't work see if you can get a flashable like the Xperia T keyboard to work after boot. If that doesn't work, there is probably a major problem.

Awesome, just wanted to make sure that I wasn't fooling myself and it really is that easy. Thanks :cyclops:

I stumbled on an IME modding thread to quit that force close once, so I'm sure ill find it again. Let me go see my best friend Google and see if I can stumble there again.

Sent from my myTouch_4G_Slide using Tapatalk 2

That would be great if you could



Thanks for both of your replies, bilgerryan and strapped! :laugh:

 

[strapped365]

Awesome, just wanted to make sure that I wasn't fooling myself and it really is that easy. Thanks :cyclops:



That would be great if you could



Thanks for both of your replies, bilgerryan and strapped! :laugh:

Yeah so far I haven't found it again. But I do remember one of my ports having this issue and a certain set of gapps fixed it so ill look for all that too

Sent from my myTouch_4G_Slide using Tapatalk 2

 

[BigSplit]

Did the logcat tell you anything about the error? Most times it will mention the lib missing. Even if you see it there it may be the wrong version, and you would need to grab it from the port.

 

[CNexus]

Did the logcat tell you anything about the error? Most times it will mention the lib missing. Even if you see it there it may be the wrong version, and you would need to grab it from the port.

Yeah i dont know actually....I dont think it did
But I've since then moved on to another port of a very popular rom type...been having some problems with the updater script, but one I get past those I think it will be fine
Thanks for the tip about same resolution devices btw :good:

Sent from my PG06100

 

[pastorterrylee]

Jellybelly Omega stuck

I flashed Jellybelly Omega to the Shift following the instructions to the letter (multiple times now) and it just gets stuck at the HTC screen. I have left it there for an hour or so, because I know that first boot can take a while. But it just sits there on the HTC screen.

 

[strapped365]

I flashed Jellybelly Omega to the Shift following the instructions to the letter (multiple times now) and it just gets stuck at the HTC screen. I have left it there for an hour or so, because I know that first boot can take a while. But it just sits there on the HTC screen.

Are you s-on unlocked?

If you are you need to
1. Open the ROM with 7zip or winrar and move the boot.img to where fastboot is located and then run this command from fastboot

fastboot flash boot boot.img

If your not check the md5 sum with the one provided on dev-host. And redownload/transfer if needed

 

[pastorterrylee]

Your stumbling is way better than my searching

I stumbled on an IME modding thread to quit that force close once, so I'm sure ill find it again. Let me go see my best friend Google and see if I can stumble there again.


Thank you for your work and thanks for stumbling for our benefit.

---------- Post added at 12:37 AM ---------- Previous post was at 12:24 AM ----------

Are you s-on unlocked?

If you are you need to
1. Open the ROM with 7zip or winrar and move the boot.img to where fastboot is located and then run this command from fastboot

fastboot flash boot boot.img

If your not check the md5 sum with the one provided on dev-host. And redownload/transfer if needed

Thanks and I will give it a shot for sure

---------- Post added at 12:42 AM ---------- Previous post was at 12:37 AM ----------

Are you s-on unlocked?

If you are you need to
1. Open the ROM with 7zip or winrar and move the boot.img to where fastboot is located and then run this command from fastboot

fastboot flash boot boot.img

If your not check the md5 sum with the one provided on dev-host. And redownload/transfer if needed

Should I do this while it is locked on the HTC screen?

 

[strapped365]

I stumbled on an IME modding thread to quit that force close once, so I'm sure ill find it again. Let me go see my best friend Google and see if I can stumble there again.


Thank you for your work and thanks for stumbling for our benefit.

---------- Post added at 12:37 AM ---------- Previous post was at 12:24 AM ----------



Thanks and I will give it a shot for sure

---------- Post added at 12:42 AM ---------- Previous post was at 12:37 AM ----------



Should I do this while it is locked on the HTC screen?

No you should be in bootloader then select fastboot. But that's if your s-on, you never said either way

 

[pastorterrylee]

I am s-off, unlocked, rooted, custom recovery

Are you s-on unlocked?

If you are you need to
1. Open the ROM with 7zip or winrar and move the boot.img to where fastboot is located and then run this command from fastboot

fastboot flash boot boot.img

If your not check the md5 sum with the one provided on dev-host. And redownload/transfer if needed

No you should be in bootloader then select fastboot. But that's if your s-on, you never said either way

I am S-off.