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

[MHB1638]

I'm having the same FC's with Weatherbug and I also have an alarm notification in the status bar even if no alarm is set? Any fix for either of these yet?

Weatherbug is broken in this version. Uninstall it. As for the alarm, go into TSM settings-status bar - make sure the "hide alarm" is checked. if it is, unselect it, then reselect it and then reboot. That fixed mine.

Still undecided if this ROM is better since there are bugs present. But i can testify that after 12 hours of work, using my phone and such, I'm down to 44% battery! I have NEVER had that much left.

 

[ckrenek23]

I'm having the same FC's with Weatherbug and I also have an alarm notification in the status bar even if no alarm is set? Any fix for either of these yet?

The weather bug im not sure of but for the alarm notifications to in tsm settings /status bar settings and uncheck the.hockey that has the alarm icon to be shown. Says will be fixed after a reboot but mine took two or three.

Sent from my SCH-I500 using Tapatalk

 

[flamingoezz]

can i flash straight from 1.3 to 2.0 or do i need to go back to a stock rom first?

 

[mer7]

But Sharky, the wipe instructions call for a data wipe. Are you saying that a dalvik and cache wipe are sufficient if coming from V1.3 or not?

Sent from my SCH-I500 using Tapatalk

Landshark went into a lot of detail for you, so this might not be necessary...

I installed 2.0 over 1.3 without a data wipe (I did wipe both caches) just to see what would happen. Everything seemed smooth for a few hours, but then I would get a ton of FCs randomly on random apps it seemed. So I wiped all 3 and reinstalled 2.0. Everything has been very smooth the last few days. So, just as the devs recommend, I would wipe data along with cache/dalvik.

 

[mer7]

can i flash straight from 1.3 to 2.0 or do i need to go back to a stock rom first?

you can go right from 1.3 to 2.0 ( after backups and wiping and all that fun stuff). If you use the 2.0 with no kernel, you'll be using the same kernel you used on 1.3. Or you could try one of the 2.0 ROMs that come with a different kernel.

 

[joebob2000]

Weatherbug is broken in this version. Uninstall it. As for the alarm, go into TSM settings-status bar - make sure the "hide alarm" is checked. if it is, unselect it, then reselect it and then reboot. That fixed mine.

Still undecided if this ROM is better since there are bugs present. But i can testify that after 12 hours of work, using my phone and such, I'm down to 44% battery! I have NEVER had that much left.

Broken broken? Bummer, I was getting psyched about this rom.

 

[cableguy1]

Is anyone getting a force close on messaging at startup?

Sent from my SCH-I500 using Tapatalk

 

[gunnermike53]

Is anyone getting a force close on messaging at startup?

Sent from my SCH-I500 using Tapatalk

logcat????

please read the op in regaurds to roporting issues.

 

[sfobrien]

Is anyone getting a force close on messaging at startup?

Sent from my SCH-I500 using Tapatalk

Try fixing permissions in CWM.

 

[eibbed0001]

Any chance that this will be able to be flashed over CommRom 1.3 in the future or is the full data wipe always going to be a prerequisite? Our second child is due any day now and I can't be spending time horsing around with my phone... my wife would literally kill me.

I was going to be obsessive and post this anyway, so I'll do it here. This is the step by step method I used going from ComRom 1.3 to 2.0 UKB and changing to CWM 3. I also was already running Voodoo. Sorry it's so long but maybe it will help someone.

1. Used Titanium Backup to backup all apps+data
2. Create recovery app for Titanium Backup so I don't have to download it from the Market after flashing new ROM. Made two - one for CWM 3 and one for the older version just in case.
3. Backup data in My Backup - all selected
4. Backup photos in My Backup - no apps included
5. Boot to recovery
6. Clear cache
7. Clear Dalvik cache
8. Clear cache
9. Clear Dalvik cache
10. Reboot
11. Boot to recovery
12. Make a Nandroid backup
13. Clear cache
14. Clear Dalvik cache
15. Odin CWM 3
16. Reboot
17. Reboot to recovery
18. Clear cache
19. Clear Dalvik cache
20. Wipe data/factory reset
21. Clear cache
22. Clear Dalvik cache
23. Wipe battery stats
24. Install new ROM
25. Clear cache
26. Clear Dalvik cache
27. Wipe voltage settings
28. Wipe battery stats
29. Reboot and make sure everything appears to work
30. Boot to recovery
31. Flash the Titanium Backup file I created earlier
32. Reboot
33. What? No Titanium Backup installed??
34. Boot to recovery
35. Again flash the Titanium Backup file I created earlier
36. Still no TiBu
37. Boot to recovery
38. Flash the other Titanium Backup file I created (for old CWM)
39. Would not install that version
40. Flash TiBu again
41. Still no TiBu
42. Reboot to recovery
43. Because TiBu wasn't working: Select Advanced Restore in Nandroid backup
44. Select Data Only
45. Restore data
46. Clear cache
47. Clear Dalvik cache
48. Reboot
49. Check to be sure Miren browser and bookmarks work
50. Check that contacts, calendar and dialer all work
51. Check to see that I can access the Market
52. Looks good!
53. Used TSM to hide alarm icon in statusbar
54. Used TSM to change color of fonts in statusbar
55. Reboot
56. Alarm icon still in statusbar. Open the clock/alarm app and delete any alarms.
57. Double check that hide alarm icon is still set
58. Reboot
59. Check in Settings - About Phone to see what ROM I was running: Firmware UKB 2.0
60. Success!

Technically, I didn't create a Nandroid backup because I had just done one the day before so after checking everything out I used Titanium Backup to install the new Amazon free app I had downloaded since that time.

 

[eibbed0001]

Weatherbug is broken in this version. Uninstall it. As for the alarm, go into TSM settings-status bar - make sure the "hide alarm" is checked. if it is, unselect it, then reselect it and then reboot. That fixed mine.

To get the alarm clock out of the status bar go into the clock app delete both alarms, then use tsm to disable alarm clock in status bar, then reboot. You might have to do that more than once.

For what it's worth, Weatherbug Elite works fine for me. The Kindle app gave FCs, though. To fix the Kindle app you can install the previous version.

 

[atomD21]

Weatherbug's fine for me, but Kindle had to get rolled back.

 

[hillview]

To get the alarm clock out of the status bar go into the clock app delete both alarms, then use tsm to disable alarm clock in status bar, then reboot. You might have to do that more than once.

For what it's worth, Weatherbug Elite works fine for me. The Kindle app gave FCs, though. To fix the Kindle app you can install the previous version.

Weatherbug still works in the status bar, but if I try to open the app for the full weather then I get the force closes. By the way, the TSM directions worked for the alarm notification in the status bar

 

[hillview]

Also, twice today I removed my phone from my belt holster and it was turned off. Had to remove the case and battery to get it to come back on. Anyone else having similar issues? I don't have a clue how long it was "turned off" just thought I would throw that out there to . Besides a few little bugs, this is a pretty awesome ROM

 

[dgwood12]

I loaded this Rom on my girlfriends fascinate last night and today she is having problems with her 3g connectivity. The 3g drops off what seems like every 2 minutes or so in areas where 3g has been strong in the past. Came from superclean doing a full wipe beforehand. Running the EC01 radio. Flashed with CWM3.0 and flashed the touchwiz with dark status bar theme right after first boot. Also after a little bit with the rom flashed back down to CWM2.5.something because I couldn't make a nandroid backup in 3.0 for some reason. Created a nandroid with the older CWM. Not sure if any of this is relative but I just wanted to include everything done up to this point. Now she tries to download something from let's say the amazon app store and it tells her the network connection was lost. She hits retry a couple times and it still remains down. She cancels and finally a couple mins later its back for about a min or two. Searched around and couldn't find any similar problems. Anyone know what could be up? Thanks in advanced! I've already programmed through *228 and updated the roaming capabilities through that as well. No help...

Sent from my Droid Incredible

 

[atomD21]

Unfortunately, that seems to be a common occurrence lately. It's not the ROM, it's an issue with Verizon. Try calling Tech Support and having them do an ESN swap. That seems to work for some people.

 

[DerekCA]

Next time you are getting random FC's and not in a specific program or app, just go into terminal emulator and run the fix permissions script. This worked when my phone was randomly turning off. This should be added to a rom so that it runs every night so that the phone is refreshed for the next day. It really does make a big difference.

1. Download Android Terminal Emulator
https://market.android.com/details?id=jackpal.androidterm&feature=order_history
2. Open terminal emulator, you will see a $ in the top left corner of the blue screen.
3. Next to that type su and hit the enter key on your keyboard
4. Terminal emulator will be given superuser permission after you hit "Accept" on the pop up.
5. Hit the menu soft key and choose the option to bring the keyboard back up.
6. You will now notice a # after the su.
7. Type fxpms next to the # and hit the enter key.

A bunch of scripts will scroll on the screen. It will take a while, (Took almost 6 minutes on my phone but will vary based on the number of apps) but when it's done you will see another # at the end and will give you an end time. Done. Back out of terminal emulator, give the phone a minute or two to settle and you should notice a difference.

I have selected to run the fix permissions option in CWM but it only takes a few seconds and doesn't seem to fix any problems. This method actually works and is definitely worth the extra steps.

Thanks to Landshark for providing this information in the Fascinate forum on Android Central.

 

[dgwood12]

Unfortunately, that seems to be a common occurrence lately. It's not the ROM, it's an issue with Verizon. Try calling Tech Support and having them do an ESN swap. That seems to work for some people.

Really? I'm not sure its purely coincidence. 3g was fine one hour/day the next hour/day I have a new Rom and its dropping...

Sent from my Droid Incredible

 

[eibbed0001]

Unfortunately, that seems to be a common occurrence lately. It's not the ROM, it's an issue with Verizon. Try calling Tech Support and having them do an ESN swap. That seems to work for some people.

Is there a website that will show which providers are having outages/issues in different parts of the country? I'd love to be able to look this stuff up and verify if Verizon or another link in the internet (a series of tubes, you know) chain is having problems.

 

[sfobrien]

Next time you are getting random FC's and not in a specific program or app, just go into terminal emulator and run the fix permissions script. This worked when my phone was randomly turning off. This should be added to a rom so that it runs every night so that the phone is refreshed for the next day. It really does make a big difference.

1. Download Android Terminal Emulator
https://market.android.com/details?id=jackpal.androidterm&feature=order_history
2. Open terminal emulator, you will see a $ in the top left corner of the blue screen.
3. Next to that type su and hit the enter key on your keyboard
4. Terminal emulator will be given superuser permission after you hit "Accept" on the pop up.
5. Hit the menu soft key and choose the option to bring the keyboard back up.
6. You will now notice a # after the su.
7. Type fxpms next to the # and hit the enter key.

A bunch of scripts will scroll on the screen. It will take a while, (Took almost 6 minutes on my phone but will vary based on the number of apps) but when it's done you will see another # at the end and will give you an end time. Done. Back out of terminal emulator, give the phone a minute or two to settle and you should notice a difference.

I have selected to run the fix permissions option in CWM but it only takes a few seconds and doesn't seem to fix any problems. This method actually works and is definitely worth the extra steps.

Thanks to Landshark for providing this information in the Fascinate forum on Android Central.

Great tip didn't know you could run fix permissions that way. Thanks.