Originally Posted by Real_JESRadio

I've had 20+ ROMs on my SGS3. TW ROMs always have a better signal. Don't know why though. Haven't seen a good explanation yet. I travel 500-600 miles a night. Using several towers TW definitely changes between 3G-4G a lot better. Another thing is on AOSP the signal you see on your phone doesn't always mean that's actual db strength. So if you are in a strong 4G area all the time you won't have too many issues. But moving between towers a lot you will see some problems.

I'm not seeing any difference between Eclipse 3.1 and any other roms. The number of bars is significantly lower, I see 1 bar at home for instance. However that's just how the rom displays signal. I am still seeing -105dbm to -109dbm on 4G LTE, just every other rom I've ever had would display anything over -110 as 2 bars and -105 or stronger as 3 bars. So signal is the same, just the phone makes it look like there is a weaker signal.

Also does anyone know how to turn off the CRT off animation for when the screen goes off? I can't find the control for it anywhere, I know every rom has different ways to control it, but I've looked everywhere in the rom's settings.

Google Services is being a big battery drain for me.
Recommendations?

Re: [ROM][AOSP] Eclipse 3.1 d2vzw (S3) build 6 - 2/10/13 - Welcome to the Dark!!

---

Originally Posted by rfranken

Google Services is being a big battery drain for me.
Recommendations?

Settings > Accounts > Google > Location Settings > Location Access > Ensure this is turned off and your gps stays off as long as possible. Things that ping your location constantly will drain your battery.

Sent from my SCH-I535 using xda app-developers app

Originally Posted by Deliquified

Settings > Accounts > Google > Location Settings > Location Access > Ensure this is turned off and your gps stays off as long as possible. Things that ping your location constantly will drain your battery.

Sent from my SCH-I535 using xda app-developers app

thanks I'll try that.
Anyone here use the new Swift Key with Flow?
Mine works...but the pretty line that shows when you flow your finger from key to key....doesn't show up.
anyone else?

Re: [ROM][AOSP] Eclipse 3.1 d2vzw (S3) build 6 - 2/10/13 - Welcome to the Dark!!

---

Two questions I have is, does mms work and does group mms work with iPhone users?

Sent from my SCH-I535 using xda premium

Re: [ROM][AOSP] Eclipse 3.1 d2vzw (S3) build 6 - 2/10/13 - Welcome to the Dark!!

---

After I make or receive a phone call and end that call, and then receive another call, I get a screen that looks like the initial call never ended (even if the call ended hours ago). If I reboot the phone, the 1st call will show caller, ID like normal, but the next call will show the in call screen that I've attached. Is this rom related?

My Tracks app FC'ing

---

This is the only app that I have not had any luck with running Eclipse. It works with other AOSP rom's. Not a biggie, but I wish that I had the skill to figure out what was going on.

---------- Post added at 04:58 PM ---------- Previous post was at 04:58 PM ----------

Originally Posted by Adamsaudio

After I make or receive a phone call and end that call, and then receive another call, I get a screen that looks like the initial call never ended (even if the call ended hours ago). If I reboot the phone, the 1st call will show caller, ID like normal, but the next call will show the in call screen that I've attached. Is this rom related?

I've had that happen before. Usually after several days without a reboot.

Re: [ROM][AOSP] Eclipse 3.1 d2vzw (S3) build 6 - 2/10/13 - Welcome to the Dark!!

---

I've also noticed that if I put the phone on speaker phone, touch tone presses on the keypad don't register properly... For example... If I get a voice mail and dial in to retrieve the message and I put the phone on speaker phone and key in my Pin, it will say it's incorrect. If I take the phone off speaker and enter the pin, it registers correctly. The same deal if I'm navigating an automated menu like cable or insurance company. Not a big deal to work around, I just wanted to see if it was a problem specific to my device.