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

[bigjobber69]

He was referring to the custom CWR you get with the OTB kernel. If you want to keep the original CWR3, you need to ODIN it after flashing the ROM.

+1 OTB kernels come with there own CWM...Its still only edify its 3.x somethinig dont know off hand

 

[abcs]

did u try through terminal emulator or CWM?

Through terminal emulator

 

[bigjobber69]

Through terminal emulator

I have never encountered this and i always do it through the emulator. I would say turn phone off let charge to 100% while off, than turn on and try and run the command again.It should reboot if done correctly. Im sure you r doing it correctly but just a reminder..
3. Open terminal emulator, type ?su? next to the $ sign and press enter
a. You should get a pop up that says ?super user permission granted?
b. You should see a # sign

4. Next to the # sign type "bstats? and press enter
a. Your phone will reboot

Hope this helped

 

[MHB1638]

Anyone else having calendar issues? My phone keeps getting a calander message report forcing me to force close it, and this only happens when my calendar sends a reminder. I have started fresh from stock 3 times back to 2.0 and still same problem. My wife's fascinate with 1.3 doesn't have this issue. I'm starting to feel 2.0 isn't better than 1.3, and maybe actually worse. I've gone back to stock via ODIN flash, got all the updates via Verizon than flash the 2.0. The biggest positive i can see is battery life. OMG its insane, like 12-14 hours of battery! But if I get a calendar reminder it crashes the phone forcing a reboot which then erases the downloaded apps icons on my home screens. Annoying!

 

[adamklo]

He was referring to the custom CWR you get with the OTB kernel. If you want to keep the original CWR3, you need to ODIN it after flashing the ROM.

And here I thought I was one of the few people who caught him in a mistake. Should have really known better.

 

[swenpro]

Just want to report that I successfully flashed UKB 2.0 on the first try. Coming from rooted stock ED01, I am liking the improvements. I followed this guy's step-by-step how-to. Thanks to all the devs for your work on this project!!

NOTE: Did have some issues with TSM Parts in Settings... it did not want to display changes to clock, etc., even after reboot, until I changed the color of the font. Now the clock is appearing, great! Don't know what this stuff is about display DBM value because I don't see any such values displaying.

 

[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

 

[CruiserBC]

Anyone know if there is a patch to enable bluetooth voicedialing? It seems like the dev's had a working Nuance patch for one of the older versions of either superclean or the TSM 1.x ROMs but I haven't seen anything yet for 2.0. Maybe I just missed it though.

Thanks in advance for any help!

 

[Landshark]

Anyone else having calendar issues? My phone keeps getting a calander message report forcing me to force close it, and this only happens when my calendar sends a reminder. I have started fresh from stock 3 times back to 2.0 and still same problem. My wife's fascinate with 1.3 doesn't have this issue. I'm starting to feel 2.0 isn't better than 1.3, and maybe actually worse. I've gone back to stock via ODIN flash, got all the updates via Verizon than flash the 2.0. The biggest positive i can see is battery life. OMG its insane, like 12-14 hours of battery! But if I get a calendar reminder it crashes the phone forcing a reboot which then erases the downloaded apps icons on my home screens. Annoying!

For the calendar notification FC, go into calendar and choose a different default notification ringtone. I think you can go back to the original ringtone you had set if you want after you get one successful reminder alert with the different ringtone.

 

[Landshark]

Just want to report that I successfully flashed UKB 2.0 on the first try. Coming from rooted stock ED01, I am liking the improvements. I followed this guy's step-by-step how-to. Thanks to all the devs for your work on this project!!

NOTE: Did have some issues with TSM Parts in Settings... it did not want to display changes to clock, etc., even after reboot, until I changed the color of the font. Now the clock is appearing, great! Don't know what this stuff is about display DBM value because I don't see any such values displaying.

DBM value is the true, accurate measure of your signal strength in a numeric value as opposed to the signal strength meter in the notification bar. The lower the number, the better the signal. Our phones operate mostly between -80 and -95 dbm. If you are lucky enough to get below -80 you are getting great signal strength. If you are above -95, I would generally say you have something wrong hardware wise. You can look up your phone's current dbm in menu=>settings=>about phone=>status and scroll down a little.

 

[Lttlwing16]

Anyone know if there is a patch to enable bluetooth voicedialing? It seems like the dev's had a working Nuance patch for one of the older versions of either superclean or the TSM 1.x ROMs but I haven't seen anything yet for 2.0. Maybe I just missed it though.

Thanks in advance for any help!

Nuance is functional with 2.0.. You can find that in Jaekar's thread in Add-Ons. I think it's for Evil Fascination, but it works with UKB 2.0.

 

[Lttlwing16]

Anyone else having calendar issues? My phone keeps getting a calander message report forcing me to force close it, and this only happens when my calendar sends a reminder. I have started fresh from stock 3 times back to 2.0 and still same problem. My wife's fascinate with 1.3 doesn't have this issue. I'm starting to feel 2.0 isn't better than 1.3, and maybe actually worse. I've gone back to stock via ODIN flash, got all the updates via Verizon than flash the 2.0. The biggest positive i can see is battery life. OMG its insane, like 12-14 hours of battery! But if I get a calendar reminder it crashes the phone forcing a reboot which then erases the downloaded apps icons on my home screens. Annoying!

Just open the calendar and navigate to the calendar settings within the app. Change the default notification to something other than what it's set on now and that should do it.

 

[Landshark]

Anyone know if there is a patch to enable bluetooth voicedialing? It seems like the dev's had a working Nuance patch for one of the older versions of either superclean or the TSM 1.x ROMs but I haven't seen anything yet for 2.0. Maybe I just missed it though.

Thanks in advance for any help!

There is a Nuance Voice Commands patch in post #6 of JaeKar99's themes thread:
http://forum.androidcentral.com/ver...t-animations-combined-resource-6-12-11-a.html

It is listed under ED01 patches, and since both CR 1.3 and 2.0 are ED01 ROMs, I would imagine it would still work

 

[Landshark]

And here I thought I was one of the few people who caught him in a mistake. Should have really known better.

I'll try to drink more heavily in order to make more mistakes it that will help

 

[wyllic]

There is a Nuance Voice Commands patch in post #6 of JaeKar99's themes thread:
http://forum.androidcentral.com/ver...t-animations-combined-resource-6-12-11-a.html

It is listed under ED01 patches, and since both CR 1.3 and 2.0 are ED01 ROMs, I would imagine it would still work

It works for me just fine on 2.0, just for verification

 

[adamklo]

I'll try to drink more heavily in order to make more mistakes it that will help

Deal!

 

[T3CH9ICIAN]

hey im loving KB2.0 its running great no FC as of yet but im having an issue on the miui lockscreen not being able to use the music controls they will not funtion im checked in TSM parts under music controls ive rebooted ive also wiped and reflashed and still no music controls and about once a day my phone will just turn off no vibration or FC or anything ill go to pick it up or use it and it will b off or maybe it is a SOD cause i have to batt pull to turn the phone back on am i looking at a bad download or ? thanks for anything i can get from ya im currently on the ED01 with the OTB1.5 kernel came from KB1.3 thanks

 

[Landshark]

hey im loving KB2.0 its running great no FC as of yet but im having an issue on the miui lockscreen not being able to use the music controls they will not funtion im checked in TSM parts under music controls ive rebooted ive also wiped and reflashed and still no music controls and about once a day my phone will just turn off no vibration or FC or anything ill go to pick it up or use it and it will b off or maybe it is a SOD cause i have to batt pull to turn the phone back on am i looking at a bad download or ? thanks for anything i can get from ya im currently on the ED01 with the OTB1.5 kernel came from KB1.3 thanks

My suggestion would be to upgrade from the OTB 1.5 kernel to the 1.6 kernel. I was having all kinds of problems like you are describing with the phone shutting off when I was running on the 1.5 kernel. No problems at all with the 1.6 kernel.

As far as the MIUI music controls, I don't use them so I don't have any answers for you there. Sorry.

 

[FearTheGhost13]

hey im loving KB2.0 its running great no FC as of yet but im having an issue on the miui lockscreen not being able to use the music controls they will not funtion im checked in TSM parts under music controls ive rebooted ive also wiped and reflashed and still no music controls and about once a day my phone will just turn off no vibration or FC or anything ill go to pick it up or use it and it will b off or maybe it is a SOD cause i have to batt pull to turn the phone back on am i looking at a bad download or ? thanks for anything i can get from ya im currently on the ED01 with the OTB1.5 kernel came from KB1.3 thanks

Not sure about the music controls, but as for the phone "turning off" so to speak, that is definitely SOD. Did you apply settings within the voltage control settings? If so you may consider easing up on the settings slightly to prevent the SOD.

And Landsharks post above me is definitely worth considering.

 

[swenpro]

DBM value is the true, accurate measure of your signal strength in a numeric value as opposed to the signal strength meter in the notification bar. The lower the number, the better the signal. Our phones operate mostly between -80 and -95 dbm. If you are lucky enough to get below -80 you are getting great signal strength. If you are above -95, I would generally say you have something wrong hardware wise. You can look up your phone's current dbm in menu=>settings=>about phone=>status and scroll down a little.

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