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

[Canuckfan]

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

Welcome to AC! Just download it from the market or....mine auto updates even on the rom. updated today actually

doh, for some reason I thought it was somehow integrated into the rom. Just got it updated. Thanks bigjobber!

 

[icu]

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

Well at least it isn't unique to me I guess. I kept trying to get a logcat, but I grew impatient (read: wanted to flash something) and decided to switch to ComaVolt last night - so far so good, but it's a bit early to say for sure yet.

I just had to say that I've encountered this exact same issue and I thought I was alone.
Thing is - besides this issue I am in love with my phone ASIS in almost every way. It can be annoying when it happens at an inopportune moment, but it boots back up in about 3 minutes or so and I just deal with it. I guess I'm not annoyed by it enough to try and get a lulzcat for the error, but I guess it would be great if someone else did (maybe I will if I get a spare moment - I understand why the devs put this in place and I should be able to figure it out).

Let me know if the switch to CV 1.6 seems to do the trick. I just am liking PBJ -100 atm, but I've got CV on my SD ready to flash. I just don't know what voltage settings to try to get the same/similar UV performance. Cheers.

* sorry to be noobish, but I flashed PBJ -100 and now I appear to have yellow Clockwork Recovery. What should I know i.e. is there things I cannot do with yellow that I could do with Red. Do I need to worry about this at all? Thanks.

 

[dwitherell]

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

I just had to say that I've encountered this exact same issue and I thought I was alone.
Thing is - besides this issue I am in love with my phone ASIS in almost every way. It can be annoying when it happens at an inopportune moment, but it boots back up in about 3 minutes or so and I just deal with it. I guess I'm not annoyed by it enough to try and get a lulzcat for the error, but I guess it would be great if someone else did (maybe I will if I get a spare moment - I understand why the devs put this in place and I should be able to figure it out).

Let me know if the switch to CV 1.6 seems to do the trick. I just am liking PBJ -100 atm, but I've got CV on my SD ready to flash. I just don't know what voltage settings to try to get the same/similar UV performance. Cheers.

* sorry to be noobish, but I flashed PBJ -100 and now I appear to have yellow Clockwork Recovery. What should I know i.e. is there things I cannot do with yellow that I could do with Red. Do I need to worry about this at all? Thanks.

Drat - while this wasn't fully unexpected (in irc last night same issue was confirmed with a ComaVolt user), I had my first mini-reboot on ComaVolt today... I think I might try to force some things in an attempt to get a logcat... Not sure if it's worth it (pretty minor annoyance really), but maybe it's indicative of other not-so-good things - who am I to say. Better to know I suppose.

I've heard mixed things on the yellow recovery - usually dealing with data wipe issues, but I'm not sure if that still is a concern (or if it's even a concern if it still is an issue). After flashing pbj I ended up ODINing the recovery from here just in case as I had no issues with that one.

 

[johnsma22]

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

Drat - while this wasn't fully unexpected (in irc last night same issue was confirmed with a ComaVolt user), I had my first mini-reboot on ComaVolt today... I think I might try to force some things in an attempt to get a logcat... Not sure if it's worth it (pretty minor annoyance really), but maybe it's indicative of other not-so-good things - who am I to say. Better to know I suppose.

I've heard mixed things on the yellow recovery - usually dealing with data wipe issues, but I'm not sure if that still is a concern (or if it's even a concern if it still is an issue). After flashing pbj I ended up ODINing the recovery from here just in case as I had no issues with that one.

Had a mini-reboot on Comvolt today as well. I have my camera app set as the custom app for the 4-tab lockscreen. Opened it, took a picture and went to view it. Phone locked and rebooted. Just as the reboot was completing I got the those four force close vibrations, but no force close notification. It completed booting up and it's been fine all day. Not sure what's going on, but I suspect a rogue app or something.

 

[sdog21]

anyone having issues with swype? The drag line shows up but nothing happens???

Sent from my SCH-I500 using Tapatalk

 

[atomD21]

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

anyone having issues with swype? The drag line shows up but nothing happens???

Sent from my SCH-I500 using Tapatalk

Yeah, for some reason, the swype that's built in to CR 2.0 is coming up as expired. There's an easy fix right here:

http://forum.androidcentral.com/verizon-fascinate-rooting-roms-hacks/95827-swipe-issues.html#post1017592

Or you can uninstall all the swype files with root explorer and get the 3.0 beta. Personally, I went the easy way...

 

[rlkmartin]

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

Having an issue with a Force Close when I select sound to attach an MP3 file as a ringtone in contacts.
I flashed CR 2.0 over stock ED04 and then flashed CR2.1 patch. I am running CR 2.1 pbj-50. I did wipe cache Dalvik and Data when I flashed CR2.0. I get a error "android.process.acore has stopped unexpectedly. Please try again" My logcat can be found at pastebin.com/ez5tPZHk

Any help would be appreciated. I have gone back to stock several times. This error does not occur in stock. Only after I flash CR 2.0. The last time I flashed back to stock I also used the Atlas 2.2 pit file with repartition checked to try and clear things up also.

Thanks,

Rick

 

[atomD21]

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

Having an issue with a Force Close when I select sound to attach an MP3 file as a ringtone in contacts.
I flashed CR 2.0 over stock ED04 and then flashed CR2.1 patch. I am running CR 2.1 pbj-50. I did wipe cache Dalvik and Data when I flashed CR2.0. I get a error "android.process.acore has stopped unexpectedly. Please try again" My logcat can be found at pastebin.com/ez5tPZHk

Any help would be appreciated. I have gone back to stock several times. This error does not occur in stock. Only after I flash CR 2.0. The last time I flashed back to stock I also used the Atlas 2.2 pit file with repartition checked to try and clear things up also.

Thanks,

Rick

I would try a different kernel. There have been a lot of people running into issues with the pbj -50 set up. Comavolt has been pretty successful for most people, as well as OTB 1.5 or 1.6.

 

[rlkmartin]

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

I would try a different kernel. There have been a lot of people running into issues with the pbj -50 set up. Comavolt has been pretty successful for most people, as well as OTB 1.5 or 1.6.

My fault. I did try the Comavolt kernel the last time and still get the FC in the acore process. Thanks for the suggestion though.

Rick

 

[dwitherell]

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

Drat - while this wasn't fully unexpected (in irc last night same issue was confirmed with a ComaVolt user), I had my first mini-reboot on ComaVolt today... I think I might try to force some things in an attempt to get a logcat... Not sure if it's worth it (pretty minor annoyance really), but maybe it's indicative of other not-so-good things - who am I to say. Better to know I suppose.

Well, I spent a few hours today trying to get a logcat to no avail. After I had given up, I of course got a mini-reboot, although this was in a slightly different scenario (although ultimately I think it all is pointing in the same direction). I was simply texting, but I had to set the phone down for a few seconds. I set it on my lap, and right after the display turned off I felt a single vibration. It felt like it was going to be a force close of some sort, so I quickly turned my attention back to the phone - it woke up, still in the process of texting (although with no lockscreen, which happens with the quick wake-up right after the screen turns off), and I starting typing again. A second or so later, the Android logo appears...

I'm going to keep trying to get a logcat, but this is such a minor annoyance/issue I doubt much would be done (could be based on currently installed apps or something else I've done to the phone and therefore external to the ROM - who knows). It's more of a curiosity thing for me now.

As an aside, I am digging ComaVolt with 2.1! I used this back in my SuperClean days, and I am remembering why it was one of my favorite kernels!

 

[ExpertZero]

Market, apps and browser not "working"

I was having an exact same problems as you over the weekend. Come to find out, there was no 3G icon on my status bar at all and no connection. I called verizon customer service and talked with 'Android specialist' (yeah.... don't ever do that). If you have an older verizon phone, get them to do the ESN swap on your account. what do you know, the 3G icon came back magically and everything works now (I was on ECLAIR) and ODINed UKB 2.0 no kernal and flashed 2.1 patch.

it's like the applications/browser/email isn't telling the phone to "kick in" the serivce, and that being under the impression that the stuff using the 3g data does that in the first place. i'm assuming the 3g data part goes into a rest or sleep mode when not in use and then when something accesses the 3g part it fires up the 3g and does it's thing? i'm not exactly sure what an esn swap will do for me but i found the reply to this too late at night and after calling Big Red found out tech support and sales are both closed this time of night... soooo i'll try this tomorrow and report how it worked out.

I found in a thread somewhere that if i use airplane mode for about 20seconds then turn it off, have google maps "find me" that should help... tired that, still didn't help any... soooo ESN swap in morning.

 

[Allsack]

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

Hello All,

Having some pretty annoying shutdowns. Here's the info:

Went from 2.9 to stock to 1.3 then wiped back to stock, then 2.0 then patched 2.1. Then fixed swype.

I chose UKB -50 PBJ.
Current stats on the phone say :
I500.04
Firmware version UKB2.0
Baseband version S:i500.04V.ED03
Kernel 2.6.32.9
Build number SCH-I500.ED01

Also, when I say locked up i mean just that- power button will not turn the phone on. only battery pull will restart it.

When I was on 1.3, I was getting random lock-ups. Like locked up. Had to battery pull for a restart.I also noticed after the lock-ups the phone was warm, and the battery had been run down quite a bit.
It is hard to be more specific about these lock-ups because I will just randomly pick up the phone, and it will be warm and wont turn on. I figured 2.0-2.1 might fix the problem, but alas, it still does it. Tonight went to a party, (phone was 80% charged) phone was in my pocket unused for 5 hours or so. When we decided to go home, checked phone, wouldn't turn on. Got home plugged it in- was dead.

I read pages and pages of info, and although this may have been addressed previously, I couldn't find it.

Any suggestions ?

Thank you in advance for any help

 

[atomD21]

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

Hello All,

Having some pretty annoying shutdowns. Here's the info:

Went from 2.9 to stock to 1.3 then wiped back to stock, then 2.0 then patched 2.1. Then fixed swype.

I chose UKB -50 PBJ.
Current stats on the phone say :
I500.04
Firmware version UKB2.0
Baseband version S:i500.04V.ED03
Kernel 2.6.32.9
Build number SCH-I500.ED01

Also, when I say locked up i mean just that- power button will not turn the phone on. only battery pull will restart it.

When I was on 1.3, I was getting random lock-ups. Like locked up. Had to battery pull for a restart.I also noticed after the lock-ups the phone was warm, and the battery had been run down quite a bit.
It is hard to be more specific about these lock-ups because I will just randomly pick up the phone, and it will be warm and wont turn on. I figured 2.0-2.1 might fix the problem, but alas, it still does it. Tonight went to a party, (phone was 80% charged) phone was in my pocket unused for 5 hours or so. When we decided to go home, checked phone, wouldn't turn on. Got home plugged it in- was dead.

I read pages and pages of info, and although this may have been addressed previously, I couldn't find it.

Any suggestions ?

Thank you in advance for any help

Ok, just to cover some bases, did you do the cache/dalvik/data wipe prior to flashing 2.0? When you went from stock to 2.0, did you hear the female robot voice on first boot? Have you tried flashing a different kernel to see if that helps? Have you tried reflashing 2.0?

 

[Allsack]

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

Atom, thanks for your reply.

Yes I did do all the wipes prior to any flash upgrades.
Yes I did hear the female robot voice telling me the update status when I went to 2.0.
As far as flashing a different kernel, no have not done that, and I guess I could reflash 2.0 Ill do that but odd thing is the same thing was happening with 1.3.

 

[atomD21]

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

Atom, thanks for your reply.

Yes I did do all the wipes prior to any flash upgrades.
Yes I did hear the female robot voice telling me the update status when I went to 2.0.
As far as flashing a different kernel, no have not done that, and I guess I could reflash 2.0 Ill do that but odd thing is the same thing was happening with 1.3.

Ok, just wanted to make sure. Yeah, the only thing I could suggest then would be to try a new kernel and if that doesn't work, try a reflash.

 

[ExpertZero]

Re: Market, apps and browser not "working"

it's like the applications/browser/email isn't telling the phone to "kick in" the serivce, and that being under the impression that the stuff using the 3g data does that in the first place. i'm assuming the 3g data part goes into a rest or sleep mode when not in use and then when something accesses the 3g part it fires up the 3g and does it's thing? i'm not exactly sure what an esn swap will do for me but i found the reply to this too late at night and after calling Big Red found out tech support and sales are both closed this time of night... soooo i'll try this tomorrow and report how it worked out.

OH KAY... if you guys have never done this after you got your phone, you should...

called Big Red, told them to do the esn swap... happy to do it for me, took all of 10min and seems to fix the problem, 12hrs without a 3g issue so far...
went from 130kbps download and 133kbps upload to a blazing 1910kbps download and 558kbps upload (per speedtest app)...WELL WELL WELL WORTH THE TIME...

 

[icu]

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

Had a mini-reboot on Comvolt today as well. I have my camera app set as the custom app for the 4-tab lockscreen. Opened it, took a picture and went to view it. Phone locked and rebooted. Just as the reboot was completing I got the those four force close vibrations, but no force close notification. It completed booting up and it's been fine all day. Not sure what's going on, but I suspect a rogue app or something.

By no means do I think that I'm in the clear, but as an experiment I switched the MIUI lockscreen and since doing so I have not have one of these "random mini reboots" *fingers crossed* Now if this in fact "fixes" the problem it would stand to reason that the problem may lie with the lockscreen(s) and/or the music controls?

Up until this point I was using the 4-tab with the music controls visible at all times. I'll miss the music controls, but the tradeoff for avoiding the previous reboots is worth it. I'll let y'all know if it happens again (so far 3 days and no reboots).

 

[Allsack]

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

Does anyone have any other possible solutions to my above posts?

I tried the kernel without pbj, reflashed. 2.0 then 2.1. Still getting random lock ups (no force close) that require a battery pull to fix.

I guess if I keep having this problem, will go to stock root debloat.

Thanks for any help.

 

[Lttlwing16]

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

Does anyone have any other possible solutions to my above posts?

I tried the kernel without pbj, reflashed. 2.0 then 2.1. Still getting random lock ups (no force close) that require a battery pull to fix.

I guess if I keep having this problem, will go to stock root debloat.

Thanks for any help.

Just my two cents....sounds like an application is locking up and draining your battery.. A battery saving app, like juice defender, could be the culprit. Do you use anything like that? If so un-install and see if the problem goes away.

IF not,

How do you backup/restore? Titanium Backup? My Backup Pro?

Try this:

Do a full data wipe in cwm and flash a stock rom and kernel(make sure you have backup's of all user data) like stock ED01 and don't restore any applications. Bare with it and use your phone bone stock (with exception to stock apps and contacts of course).

Use it for a couple of days and see how it works.

If it doesn't act up..then try flashing UKB (wipe caches etc..), once again don't restore any apps. Try that for a couple days and see if it locks up.

A lot of work, but basically you have a problem that is very bad. Almost makes your phone useless.

Your best bet is to start stock and download apps from the market one at a time.

read here if you have questions about the back up /restore

http://forum.androidcentral.com/verizon-fascinate-rooting-roms-hacks/85675-how-preparing-yourself-wipe-data-factory-reset-clockwork-recovery.html

 

[Allsack]

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

Thank you for your suggestions. In fact I will do this.

In the mean time---between posts, I thought an app may be causing the headaches. So I deleted them all except handcent, rom manager, Ti and back up pro. It's been a couple of hours, hasn't locked yet, but typically only 1-2 times a day. Will keep yall posted, and thanks again for your comments.

If it locks again I will step by step your advice.