[ROM][5.07.2011][ED01]Community Rom V1.3

[Snareman]

BTW, for whomever is in control of the Swype stuff for ComRom1.4 and up - if you could change text color on the pop up words from Green on a grey background to something with a little more contrast that would be great. Its just a bit hard to read with the green.

 

[tropolis]

i do see it now on the top. in the middle though, under the google widget, there should be a clock feature though right?

thats wwhat i dont see.

i also dont see the dotted background.

thanks.

 

[tropolis]

actually i think i got the background. selected it from wallpapers.

it is the microbes background right?

just need to add that clock somehow under google.

thanks.

 

[kevinbvw]

Not sure if its been posted but since ive installed this coming from sc2.9.2 ive been.getting fc vibrates randomly all day. It was at first only when i powered the phone on and it was media scanning. Then i installed the white chrome theme and its been vibrating all day. Tried a couple other themes with similar results. Any words of wisdom here? Cleared cache/delvic

 

[Landshark]

Not sure if its been posted but since ive installed this coming from sc2.9.2 ive been.getting fc vibrates randomly all day. It was at first only when i powered the phone on and it was media scanning. Then i installed the white chrome theme and its been vibrating all day. Tried a couple other themes with similar results. Any words of wisdom here? Cleared cache/delvic

Have you tried fixing permissions?

 

[jjong]

Kevinbvw,
I had similar problem today. Landshark help me alot go to page 175, and read the comments that he made for me. Now there is no fc so far. I did reinstall and followed the steps. I hope this help.

 

[Lttlwing16]

Putting this out there, haven't seen anyone with the same problem..but just for reference.

I noticed when I switched to KB/1.2 the phone would produce a mid frequency hum when holding the phone up to my ear. I noticed that if I would move the position of the phone it would go away. I have roughly determined that this is a problem with the proximity sensor, and the OTB kernel. I switched to comavolt after reading that Landshark had good luck with it over KB. And what do you know, after a couple phone calls, I haven't been able to reproduce the same hum....a fix ? At least for today..

 

[adamklo]

Just noticed this today, but using the Miui lock with music controls, the Fwd button stops playing the music, rather than advancing to the next track. I don't use the musical player often and it may be exclusive to that lock, so it doesn't bother me; just an FYI.

My phone talks to computers.

 

[pikanate]

Just noticed this today, but using the Miui lock with music controls, the Fwd button stops playing the music, rather than advancing to the next track. I don't use the musical player often and it may be exclusive to that lock, so it doesn't bother me; just an FYI.

My phone talks to computers.

Yeah same thing here, I just learned to suck it up cause i use the music player a lot.

 

[jpprice]

Wondering if anyone else has experienced this problem. I have been messing around with the voltage control settings and everything seems to work fine. I leave my settings for a couple of days to make sure there are no issues and it seems like no matter what settings I try everything works great for about two days then my phone vibrates once and won't wake up and I have to pull the battery. I tried leaving everything at -25 voltage and it still does it. Not sure if I should try a different kernel or what the issue is.

 

[Lttlwing16]

Wondering if anyone else has experienced this problem. I have been messing around with the voltage control settings and everything seems to work fine. I leave my settings for a couple of days to make sure there are no issues and it seems like no matter what settings I try everything works great for about two days then my phone vibrates once and won't wake up and I have to pull the battery. I tried leaving everything at -25 voltage and it still does it. Not sure if I should try a different kernel or what the issue is.

To my knowledge, this wouldn't be caused by undervolting. A vibrate generally indicates a force close issue, or system error.

Are you running a custom launcher, like LP or ADW?

 

[Robo]

Having a force close issue with the stock calender included in Comrom 1.3. It force closes when it has to notify of an event. I thought perhaps it was from running undervolted but I changed it all back rebooted and the same thing so not sure. Anyone having this problem or know how to fix it? Thank you

 

[jpprice]

To my knowledge, this wouldn't be caused by undervolting. A vibrate generally indicates a force close issue, or system error.

Are you running a custom launcher, like LP or ADW?

I'm running LP+ currently. It just seems weird that it does it after a couple of days every time after a reboot.

 

[Landshark]

Having a force close issue with the stock calender included in Comrom 1.3. It force closes when it has to notify of an event. I thought perhaps it was from running undervolted but I changed it all back rebooted and the same thing so not sure. Anyone having this problem or know how to fix it? Thank you

Possible solution - select a default alarm again in Calendar settings, you will not get the FC again.

 

[Lttlwing16]

I'm running LP+ currently. It just seems weird that it does it after a couple of days every time after a reboot.

Clear LP+ cache and data in settings, then try setting the AOSP launcher as default for a couple days and see if it gives you the same problemo. Could be a widget or something..

 

[aerichards1977]

Having a force close issue with the stock calender included in Comrom 1.3. It force closes when it has to notify of an event. I thought perhaps it was from running undervolted but I changed it all back rebooted and the same thing so not sure. Anyone having this problem or know how to fix it? Thank you

There is also a more "stock" calender that adry posted with the original Com Rom that I just keep flashing after I update each time. This seems to take care of the problem for me. Adry said it might have something to do with the theme of the calender on some devices. It does have a problem with me. When I flash this, I never have any more problems. I also need to do this after themes as I would again run into problems. It should be on page one of this post.

 

[kevinbvw]

Have you tried fixing permissions?

I did the permissions fix and the other thing posted from back a couple pages. My phone was awesome today up until about the 8th hour then.i started getting the fc vibrates again. Every few minutes the phone vibrates just a little burst then three short bursts. It never shoss a fc popup message just the vibrates i also noticed it do it when i answer a phone call and again when i hang up the call.

 

[iLogikk]

Okay...I decided to go with the community Rom. I am sitting down today to do everything but first I need to know what to do. I want to go back to stock but I'm not sure which file to use.

I have a few files in a folder and I'm not sure what they are:

CI500_VZW_EB01_FROYO_REL.tar.md5.tar
DI01package3.tar.tar
DL09.tar.md5
eb01modem.tar

Which do I need to flash and is it through cwm or odin?
I'm currently running sc 2.9.2v

My intention is to go back to stock, do the three updates (I think there were three) that VZW sent (including the official Froyo) and then flash the community rom.

Just need a little guidance so that I can rename these files and keep up with them. I have about 23 files in my "Android" folder and I need to delete some of them. Anyone willing to tell me what to keep and toss I'd be grateful!! :-D

Thanks in advance to the wonderful person(s) that helps!!!

 

[jpprice]

Clear LP+ cache and data in settings, then try setting the AOSP launcher as default for a couple days and see if it gives you the same problemo. Could be a widget or something..

I will give it a shot and see what happens. Thanks.

 

[atomD21]

Okay...I decided to go with the community Rom. I am sitting down today to do everything but first I need to know what to do. I want to go back to stock but I'm not sure which file to use.

I have a few files in a folder and I'm not sure what they are:

CI500_VZW_EB01_FROYO_REL.tar.md5.tar
DI01package3.tar.tar
DL09.tar.md5
eb01modem.tar

Which do I need to flash and is it through cwm or odin?
I'm currently running sc 2.9.2v

My intention is to go back to stock, do the three updates (I think there were three) that VZW sent (including the official Froyo) and then flash the community rom.

Just need a little guidance so that I can rename these files and keep up with them. I have about 23 files in my "Android" folder and I need to delete some of them. Anyone willing to tell me what to keep and toss I'd be grateful!! :-D

Thanks in advance to the wonderful person(s) that helps!!!

All the files you have listed are applied via ODIN. If it were me I would ODIN the DL09 file (after backing everything up, of course...) and the EA28 update will get FOTA'd shortly after booting up. After that boot up, the ED01 Froyo update will get pushed, and if it doesn't, you can go into Settings>About Phone, and check for updates. Once that's all done and rebooted into ED01 goodness, you're all set to ODIN CWM and flash the ComRom! Enjoy! If you want to PM me the list of all the files you have, I'll see what I can do to help pare some of them down!