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

[bigjobber69]

I think shark says it does that. But still actually wipes. Flash the rom.

 

[Froalskiner#WN]

Yeah I'm in the middle of doing a Titanium restore.

 

[bigjobber69]

Did u try ur sms? Make sure its working.

 

[Lttlwing16]

Did u try ur sms? Make sure its working.

+1 to that..

Try mms before restoring anything.

 

[Froalskiner#WN]

+1 to that..

Try mms before restoring anything.

I did. Looked good. Hopefully this will work going forward...at least until 2.1 comes out of course!

 

[jampot]

Yay! It worked. Once again I feel so... powerful! Uber-user me
Looking forward to fiddling with it today.

I LOVE YOU GUYS!!!

 

[domenci]

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..

I got the alarm out of the status bar by following these directions. I then set a new alarm, and the icon is now not showing up even if there is an alarm set. I deleted the new alarm, unhid the alarm in TSM, and rebooted. Now the icon is back, even though there is no alarm at all. How do I get the icon to show up when an alarm is set and not show up when there is no alarm set?

 

[Landshark]

I got the alarm out of the status bar by following these directions. I then set a new alarm, and the icon is now not showing up even if there is an alarm set. I deleted the new alarm, unhid the alarm in TSM, and rebooted. Now the icon is back, even though there is no alarm at all. How do I get the icon to show up when an alarm is set and not show up when there is no alarm set?

Unfortunately that's a glitch in the way that works. There is no fix for it right now. The TSM crew is aware of it and if there is going to be any kind of fix for that, I would imagine it will be a part of Comm ROM 2.1.

 

[jampot]

Hey Shark,
Any idea on why it would say bstats is missing?

Was there any answer to this? I didn't see one.
I also can't clear battstats via terminal emulator.

It says: rm failed for /data/system/batterystats.bin, No such file or directory

 

[Landshark]

Was there any answer to this? I didn't see one.
I also can't clear battstats via terminal emulator.

It says: rm failed for /data/system/batterystats.bin, No such file or directory

I don't understand why. I just checked all versions of the ROM and they all contain the bstats and fxpms scripts in the bin folder.

 

[jampot]

I don't understand why. I just checked all versions of the ROM and they all contain the bstats and fxpms scripts in the bin folder.

Weird. I tried again. Same thing. I reinstalled the terminal emulator, but got the same message.
I'll mess with it tomorrow!

Thanks, Lando

 

[park_timmy]

Is overclocking worth the risk of cooking your processor? I see the OTB 1.6 can go up to 1.5ghz. Is there really much gain? I noticed without the Lagfix, testing running Quadrent to test stock vs OC'd I get the following results (I know doing the lagfix would increase these as well.)

with no voltage change
Stock - 750s
OC'd to 1.4 - 1050s

 

[iLogikk]

Question: What about the OTA update from VZW? I need it (I think) because my calls were not all coming in. I'm hoping this would fix it. I thought it was the community ROM but apparently it was not. How would I get that update AND will it work with 2.0?

I am on COM 1.3 and I'm going to do a data wipe and a wipe of both cache. I'm going to save the -50 2.0 version to my sdcard. Am I missing anything?

Also, I am using CWM3_Voodoo.tar.md5 from [RECOVERY][ODIN][ZIP][4.22.11]Voodoo CWM 3.x UPDATED 5.8.11 - xda-developers ... is this the one I should be using? If not, can someone point me there?

I apologize in advance if this has been asked already but I don't get a chance to follow the forums as closely anymore with the new job I have so I'm often lost now :-(

I just found our about 2.0 today....better late than never but never late is BETTER!!!!


EDIT: Can someone explain the difference in the download files? I was going to do the first 2.0 (-50...fixed)...not sure what the difference is though.

 

[dwitherell]

I have not personally done the OTA yet - from what I've gathered, it's a bit of a mixed bag as far as helping the core issue it is said to address (one I suffer from as well - the missed call issue). There are a number of threads on the topic - check out here for one set of thoughts on ED04.

It might be useful to check out this guide that I put together - it can get you through obtaining both ED04 and community ROM 2.0. This is just one way to go about the process, but it seems like it could work for you. I use the same CWM you referred to in that guide.

The different download files are for variants on the included kernal (and there is a kernal-less one). The OTB kernal allows you to customize voltages (so you can under- or over-volt - most undervolt as all strive for amazing battery life), where the PBJ ones have the undervolt pre-set (either -50 or -100, but many seem to have issues with -100). I've tried both the OTB and the -50 PBJ - they seem similar (at least how I used the OTB one) all in all; I was quite happy with each. If you don't want to mess with voltage settings, just stick with your original -50 PBJ plan. I hope this helps!

Question: What about the OTA update from VZW? I need it (I think) because my calls were not all coming in. I'm hoping this would fix it. I thought it was the community ROM but apparently it was not. How would I get that update AND will it work with 2.0?

I am on COM 1.3 and I'm going to do a data wipe and a wipe of both cache. I'm going to save the -50 2.0 version to my sdcard. Am I missing anything?

Also, I am using CWM3_Voodoo.tar.md5 from [RECOVERY][ODIN][ZIP][4.22.11]Voodoo CWM 3.x UPDATED 5.8.11 - xda-developers ... is this the one I should be using? If not, can someone point me there?

I apologize in advance if this has been asked already but I don't get a chance to follow the forums as closely anymore with the new job I have so I'm often lost now :-(

I just found our about 2.0 today....better late than never but never late is BETTER!!!!


EDIT: Can someone explain the difference in the download files? I was going to do the first 2.0 (-50...fixed)...not sure what the difference is though.

 

[Froalskiner#WN]

Is anybody having a problem with account settings for apps being reset in this ROM? For example, I have to re-login to Facebook and other apps about once a week for example.

 

[Pags]

will bluetooth ever work properly? or is that something for which we're waiting on Verizon, i.e. a later ED0x radio update?

 

[djmackee]

is there a fix/patch for facebook account?

 

[Froalskiner#WN]

will bluetooth ever work properly? or is that something for which we're waiting on Verizon, i.e. a later ED0x radio update?

What's not working for you? Which radio are you running? I am running ED03 and not seeing any issues. Connecting to my car works as well as my headset.

 

[Froalskiner#WN]

is there a fix/patch for facebook account?

Are you referring to my post or are you having some other Facebook problem?

 

[Pags]

What's not working for you? Which radio are you running? I am running ED03 and not seeing any issues. Connecting to my car works as well as my headset.

My phone will connect to my car just fine (2011 Jetta). The problem is that once my first phone call ends via bluetooth, something on my phone crashes (presumably bluetooth...i get 4 buzzes but no error message). My car says that my bluetooth is still connected, but I can no longer transmit phone audio over bluetooth. If I go into my bluetooth options, the check box for Phone Audio is blank. If I try to select it, it hangs at a loading screen and then nothing happens...it stays blank.

I'm pretty sure I'm rocking ED01. I've had this issue since I started using SC 2.5 (frankenclean I believe).

I'm assuming it's something with the bluetooth drivers and not the radio since it can still connect and everything. I've been wrong before though. I can play music over bluetooth as well. The only workaround I have discovered is to shutoff bluetooth before my call ends. Also if I immediately call someone after my first call ends it will keep working.