[ROM][Repost][06/05/11] Comm ROM 2.1 (UKB) from TSM **Updated 06/20/11**

[adamklo]

Okay, thanks for that info, Shark. However, it seems that I should be seeing these DBM numbers on the Statusbar? In Settings-->TSM Parts-->Statusbar Settings it currently shows on my phone:

Hide Signal (Hides signal when dbm shown) CHECKED
Show dbm (Display dbm value) CHECKED

I have never seen any dbm numbers show up on the Statusbar, only bars of signal.

On a side note... what is "Launcher2 Orientation"? Thanks

Reboot your phone. That should get them to show. Also, sometimes it just takes a minute for them to refresh.

the Launcher2 Orientation is for those of us who like the older launcher, when rotation is disabled, the home screen does NOT rotate.

 

[Landshark]

Okay, thanks for that info, Shark. However, it seems that I should be seeing these DBM numbers on the Statusbar? In Settings-->TSM Parts-->Statusbar Settings it currently shows on my phone:

Hide Signal (Hides signal when dbm shown) CHECKED
Show dbm (Display dbm value) CHECKED

I have never seen any dbm numbers show up on the Statusbar, only bars of signal.

On a side note... what is "Launcher2 Orientation"? Thanks

Just like the clock, you have to change the text color then reboot. If you've already changed the text color and rebooted so you now see the clock, try toggling the checkmark. I just toggled the checkmark and the dbm value appeared, then hid every time I toggled the checkmark. To hide the signal you have to have show dbm checked first, then put a checkmark in hide signal. Launcher 2 orientation is supposed to allow the launcher and homescreen icons to either rotate when you rotate the phone, or stay stationary when you rotate the phone. Not sure if that is completely working as intended. I wanted my homescreens and icons to not rotate and no matter what i did, they rotated. For others the autorotate did not work and they had to delete a file. I'm looking for which file but haven't found the answer yet.

 

[Froalskiner#WN]

I've been running this ROM successfully for the last week or so and so far it's going well. Aside from a few random lockups that were probably due to voltage settings, my main reoccurring issue right now is FC's on sms messages. I'm also getting FC's on calendar reminders. I remember seeing a fix for the calendar but I can't find it right now.

My more serious issue is with the SMS service. As soon as I click into a message I get a FC message. I did a Catlog trace but I wasn't sure what was the relevant section yet. I am seeing these errors though this seems to be the culprit possibly. Any thoughts? I've already tried clearing the dalvik cache and clearing the data for SMS in applications but so far nothing is working. Any ideas?

I/Database( 4697): sqlite returned: error code = 14, msg = cannot open file at source line 35106
I/Database( 4697): sqlite returned: error code = 14, msg = unable to open database file
E/Database( 4697): CREATE TABLE android_metadata failed
V/AudioFlinger( 2591): PlaybackThread::Track::destroy
V/AudioPolicyManager( 2591): releaseOutput() 1
V/AudioFlinger( 2591): remove track (4098) and delete from mixer
V/AudioFlinger( 2591): PlaybackThread::Track destructor
V/AudioFlinger( 2591): removeClient_l() pid 2591, tid 2591, calling tid 2591
I/AudioService( 2746): AudioFocus abandonAudioFocus() from android.media.AudioManager@48ad5bd0
E/Database( 4697): Failed to setLocale() when constructing, closing the database
E/Database( 4697): android.database.sqlite.SQLiteException: unable to open database file
E/Database( 4697): at android.database.sqlite.SQLiteDatabase.native_setLocale(Native Method)
E/Database( 4697): at android.database.sqlite.SQLiteDatabase.setLocale(SQLiteDatabase.java:2059)
E/Database( 4697): at android.database.sqlite.SQLiteDatabase.<init>(SQLiteDatabase.java:1927)
E/Database( 4697): at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:883)
E/Database( 4697): at android.database.sqlite.SQLiteDatabase.openOrCreateDatabase(SQLiteDatabase.java:960)
E/Database( 4697): at android.database.sqlite.SQLiteDatabase.openOrCreateDatabase(SQLiteDatabase.java:953)
E/Database( 4697): at android.app.ContextImpl.openOrCreateDatabase(ContextImpl.java:638)
E/Database( 4697): at android.content.ContextWrapper.openOrCreateDatabase(ContextWrapper.java:203)
E/Database( 4697): at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:98)
E/Database( 4697): at com.sec.android.provider.badge.BadgeProvider.update(BadgeProvider.java:124)
E/Database( 4697): at android.content.ContentProvider$Transport.update(ContentProvider.java:216)
E/Database( 4697): at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:201)
E/Database( 4697): at android.os.Binder.execTransact(Binder.java:288)
E/Database( 4697): at dalvik.system.NativeStart.run(Native Method)
I/ActivityManager( 2746): Displayed activity com.android.mms/.ui.ComposeMessageActivity: 935 ms (total 935 ms)
E/DatabaseUtils( 4697): Writing exception to parcel
E/DatabaseUtils( 4697): android.database.sqlite.SQLiteException: unable to open database file
E/DatabaseUtils( 4697): at android.database.sqlite.SQLiteDatabase.native_setLocale(Native Method)
E/DatabaseUtils( 4697): at android.database.sqlite.SQLiteDatabase.setLocale(SQLiteDatabase.java:2059)
E/DatabaseUtils( 4697): at android.database.sqlite.SQLiteDatabase.<init>(SQLiteDatabase.java:1927)
E/DatabaseUtils( 4697): at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:883)
E/DatabaseUtils( 4697): at android.database.sqlite.SQLiteDatabase.openOrCreateDatabase(SQLiteDatabase.java:960)
E/DatabaseUtils( 4697): at android.database.sqlite.SQLiteDatabase.openOrCreateDatabase(SQLiteDatabase.java:953)
E/DatabaseUtils( 4697): at android.app.ContextImpl.openOrCreateDatabase(ContextImpl.java:638)
E/DatabaseUtils( 4697): at android.content.ContextWrapper.openOrCreateDatabase(ContextWrapper.java:203)
E/DatabaseUtils( 4697): at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:98)
E/DatabaseUtils( 4697): at com.sec.android.provider.badge.BadgeProvider.update(BadgeProvider.java:124)
E/DatabaseUtils( 4697): at android.content.ContentProvider$Transport.update(ContentProvider.java:216)
E/DatabaseUtils( 4697): at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:201)
E/DatabaseUtils( 4697): at android.os.Binder.execTransact(Binder.java:288)
E/DatabaseUtils( 4697): at dalvik.system.NativeStart.run(Native Method)
W/dalvikvm( 4753): threadid=13: thread exiting with uncaught exception (group=0x4001d7f0)
E/AndroidRuntime( 4753): FATAL EXCEPTION: Thread-23
E/AndroidRuntime( 4753): android.database.sqlite.SQLiteException: unable to open database file
E/AndroidRuntime( 4753): at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:158)
E/AndroidRuntime( 4753): at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:114)
E/AndroidRuntime( 4753): at android.content.ContentProviderProxy.update(ContentProviderNative.java:506)
E/AndroidRuntime( 4753): at android.content.ContentResolver.update(ContentResolver.java:707)
E/AndroidRuntime( 4753): at com.android.mms.transaction.MessagingNotification.updateBadgeProvider(MessagingNotification.java:1101)
E/AndroidRuntime( 4753): at com.android.mms.transaction.MessagingNotification.blockingUpdateNewMessageIndicator(MessagingNotification.java:224)
E/AndroidRuntime( 4753): at com.android.mms.transaction.MessagingNotification$1.run(MessagingNotification.java:185)
E/AndroidRuntime( 4753): at java.lang.Thread.run(Thread.java:1096)
W/ActivityManager( 2746): Force finishing activity com.android.mms/.ui.ComposeMessageActivity
I/ ( 2746): dumpmesg > "/data/log/dumpstate_app_error.log"
I/dumpstate(17613): begin

Anybody have any insight into this?

 

[Lttlwing16]

Anybody have any insight into this?

You can flash the SMS patch from here..

http://forum.androidcentral.com/verizon-fascinate-rooting-roms-hacks/79483-rom-5-07-2011-ed01-community-rom-v1-3-a.html

For calendar, just open the calendar and change the default notification to something different than what it is set to now.. should be good after that.

 

[Froalskiner#WN]

You can flash the SMS patch from here..

http://forum.androidcentral.com/verizon-fascinate-rooting-roms-hacks/79483-rom-5-07-2011-ed01-community-rom-v1-3-a.html

For calendar, just open the calendar and change the default notification to something different than what it is set to now.. should be good after that.

I flashed both already. The calendar appears to be good to go now but messaging is still broken. I wiped partition cache and dalvik cache before and after flashing the messaging patch.

 

[Lttlwing16]

I flashed both already. The calendar appears to be good to go now but messaging is still broken. I wiped partition cache and dalvik cache before and after flashing the messaging patch.

Both what? The calendar patch and the SMS patch?

Give me a minute and I'll pull the sms.apk from 2.0 and let you try it.

EDIT: Do you have Root Explorer 2.15 or greater?

EDIT 2 : Have you fixed permissions yet" Either via CWM or Terminal Emulator?

 

[Froalskiner#WN]

Both what? The calendar patch and the SMS patch?

Give me a minute and I'll pull the sms.apk from 2.0 and let you try it.

EDIT: Do you have Root Explorer 2.15 or greater?

EDIT 2 : Have you fixed permissions yet" Either via CWM or Terminal Emulator?

Oh wait, I may have grabbed the wrong one. I flashed the message_patch.zip which sounds like the wrong one.

Yes, I have root explorer 2.16.

I fixed permissions in both Term emulator and CWM.

EDIT: It's hard to search for SMS patches because it's too short of a search term.

 

[Lttlwing16]

Oh wait, I may have grabbed the wrong one. I flashed the message_patch.zip which sounds like the wrong one.

Yes, I have root explorer 2.16.

I fixed permissions in both Term emulator and CWM.

Did you ensure that data was mounted in cwm before fixing permsissions? Did it take a couple seconds or a minute or two with a bunch of scripts.

Are you on KB 2.0?

 

[bigjobber69]

Did you ensure that data was mounted in cwm before fixing permsissions? Did it take a couple seconds or a minute or two with a bunch of scripts.

Are you on KB 2.0?

Do as Lttlwing has told u make sure that data was mounted in CWM, and make sure it took minutes not seconds. If this still didnt work im going to recommend to redownload 2.0 and then to reflash it. Make sure to wipe d-cache and cache. maybe you got a bad download, happens to the best of us. If that doesnt work which it def should, have u tried handcent? I love it for sms thats what I use as my sms app.

 

[Froalskiner#WN]

Did you ensure that data was mounted in cwm before fixing permsissions? Did it take a couple seconds or a minute or two with a bunch of scripts.

Are you on KB 2.0?

I ran it a couple of times. I think the first time it was quick in CWM. The second time was in terminal emulator and that took a bit and showed it was going through for sure. Did I flash the right patch?

Yes, KB 2.0

 

[Lttlwing16]

Oh wait, I may have grabbed the wrong one. I flashed the message_patch.zip which sounds like the wrong one.

Yes, I have root explorer 2.16.

I fixed permissions in both Term emulator and CWM.

EDIT: It's hard to search for SMS patches because it's too short of a search term.

Here is the mms.apk from 2.0.

Mms2.0.apk

Follow the steps here to install.. Just skip over the intro and start at the steps...substitute mms.apk for swype.apk in the instructions.

http://forum.androidcentral.com/verizon-fascinate-rooting-roms-hacks/82298-how-changing-out-themed-swype-apk.html

 

[Lttlwing16]

I ran it a couple of times. I think the first time it was quick in CWM. The second time was in terminal emulator and that took a bit and showed it was going through for sure. Did I flash the right patch?

Yes, KB 2.0

Go into CWM...

mounts and storage..

make sure you have something like this for the top 4.

unmount/system
unmount/data
ummount/dbdata
unmount/cache

if it says 'mount' the cursor to it and hit the power button to mount. it should change to unmount then.

After you are mounted correctly,

Then fix permissions in CWM..

reboot when its done..

 

[Froalskiner#WN]

Here is the mms.apk from 2.0.

Mms2.0.apk

Follow the steps here to install.. Just skip over the intro and start at the steps...substitute mms.apk for swype.apk in the instructions.

http://forum.androidcentral.com/verizon-fascinate-rooting-roms-hacks/82298-how-changing-out-themed-swype-apk.html

Ok, backed up and replaced MMs.apk in system\app updated permissions and ownership. Ran the term emulator and fxpms script. Tried the messaging app, crashed after a test message. Rebooted. Retested. Still crashing.

EDIT: I also cleared out all of the existing txt messages before sending a test. The test went through before crashing however,

 

[Lttlwing16]

Ok, backed up and replaced MMs.apk in system\app updated permissions and ownership. Ran the term emulator and fxpms script. Tried the messaging app, crashed after a test message. Rebooted. Retested. Still crashing.

Just to check, you did switch the mms2.0.apk to mms.apk before copying to the system/app . It did prompt you to overwrite the existing. Upon installing the new mms.apk all app data should have been deleted. You shouldn't have had any text messages.

did you check the mounts in CWM were as I listed above and fix permissions from Clockwork? Make sure they are and re-fix.

THEN

Wipe your cache and davlik cache in CWM three times each. and reboot..

IF that all fails,

Ithen your only option is to reflash the ROM... make sure you got a backup fresh..

 

[Froalskiner#WN]

dang...did you check the mounts in CWM were as I listed above and fix permissions from Clockwork?

If so, then your only option is to reflash the ROM... make sure you got a backup fresh..

I just saw your steps after I was already going through the Mms update...running through it now...

EDIT: no luck. Need to reflash I think

 

[Lttlwing16]

That's a for sure fix..

One last try...Try wiping caches in clockwork...

 

[Froalskiner#WN]

Just to check, you did switch the mms2.0.apk to mms.apk before copying to the system/app . It did prompt you to overwrite the existing. Upon installing the new mms.apk all app data should have been deleted. You shouldn't have had any text messages.

did you check the mounts in CWM were as I listed above and fix permissions from Clockwork? Make sure they are and re-fix.

THEN

Wipe your cache and davlik cache in CWM three times each. and reboot..

IF that all fails,

Ithen your only option is to reflash the ROM... make sure you got a backup fresh..

When I replaced the mms.apk it asked me to overwrite and I said yes however it didn't wipe the existing data out. I still showed my test messages I had earlier. I'm going to go through the steps one more time in case I did anything out of order. If all else fails, I'll do a factory reset, wipe/flash

 

[bigjobber69]

When I replaced the mms.apk it asked me to overwrite and I said yes however it didn't wipe the existing data out. I still showed my test messages I had earlier. I'm going to go through the steps one more time in case I did anything out of order. If all else fails, I'll do a factory reset, wipe/flash

When you wipe data make sure you do it from within CWM and not from the phone itself. Ok, If you still are not up and running heres what you need to do, 2 options. Go straight to option number 2 if you havent set up your phone to your liking yet. Definitely redownload 2.0 and put that on your SDcard. Boot to CWM wipe only cache and D-cache. than flash 2.0 see if that works. If that still doesnt work option 2, I would wipe your data and the other 2 caches and flash again. That will work and problem should be fixed.

 

[swenpro]

Reboot your phone. That should get them to show. Also, sometimes it just takes a minute for them to refresh.

the Launcher2 Orientation is for those of us who like the older launcher, when rotation is disabled, the home screen does NOT rotate.

Just like the clock, you have to change the text color then reboot. If you've already changed the text color and rebooted so you now see the clock, try toggling the checkmark. I just toggled the checkmark and the dbm value appeared, then hid every time I toggled the checkmark. To hide the signal you have to have show dbm checked first, then put a checkmark in hide signal. Launcher 2 orientation is supposed to allow the launcher and homescreen icons to either rotate when you rotate the phone, or stay stationary when you rotate the phone. Not sure if that is completely working as intended. I wanted my homescreens and icons to not rotate and no matter what i did, they rotated. For others the autorotate did not work and they had to delete a file. I'm looking for which file but haven't found the answer yet.

Okay, thanks to both for your responses. I UNchecked both boxes, rebooted, then REchecked them and now the dbm shows in Statusbar.

I wonder what other features I'm supposed to toggle for them to starting working!

 

[Froalskiner#WN]

When you wipe data make sure you do it from within CWM and not from the phone itself. Ok, If you still are not up and running heres what you need to do, 2 options. Go straight to option number 2 if you havent set up your phone to your liking yet. Definitely redownload 2.0 and put that on your SDcard. Boot to CWM wipe only cache and D-cache. than flash 2.0 see if that works. If that still doesnt work option 2, I would wipe your data and the other 2 caches and flash again. That will work and problem should be fixed.

Ugh...so the initial reflash didn't fix the issue so I backed up and I'm wiping my data. Unfortunately I'm stuck at the /sdcard/.android_secure section of the format. Pain in the a**...