Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Yes. I have made no modifications to this phone. Totally stock and Verizon approved.![]()

Yikes. It would have helped a lot to know up front that this was not a standard Verizon CDMA phone.
Who programmed the network APN's onto the phone?
Where did you get the phone?
From Verizon? From a 3rd party?
Was it originally GSM or does it have a "Verizon approved" flash?
I see the problem. I did misspeak. I am running a stock Verizon phone, but NOTon GSM.
Sorry for the confusion.
Here's a couple more aLogcat logs that show some different info:
And the phone is getting warm....
This phone is not set up like any standard Verizon CDMA/LTE phone that I have ever worked on. It is trying to do GSM. We'll probably need some deeper analysis to figure out what's going on here.
Those logs show *ERRORS* on the RIL (Radio Interface Layer).
Radio Interface Layer - Wikipedia, the free encyclopedia
Try bringing up the "hidden menu" by going to the phone dialer and dialing
*#*#4636#*#*
** Don't change *anything* **
in the menu that pops up.
(This command may not work on your phone, but there are other ways to bring up the hidden menu)
Please take a screen shot of the items in the dropdown menu just above "turn off radio". It should look something like this:
So, I've been experimenting a little. If I Force Stop K-9 Mail, GSAM looks like above, with a high Deep Sleep cycle. If I start K-9 mail and rerun, Deep Sleep is unused. So it seems that something in K-9 mail is keeping the radio alive.
Yes, K-9 may be repeatedly failing to send a message. Is there anything stuck in the K-9 Outbox?
Do you still have GSM errors in the aLogcat radio log?
I'm not sure how to proceed from here. Changing some settings in the hidden menu might help, but you don't have the Network Mode settings in your Settings that you would need to change the settings back. I don't want to change settings and screw up your phone and then not be able to change the settings back.
Hmm, let me think about this.
-or-
*** HELP !!! - ANYBODY !!! ***
There is still GSM activity, but if I filter by Error, they aren't there.
There shouldn't be any GSM activity.
There is still GSM activity, but if I filter by Error, they aren't there.
You don't have to filter. The aLogcat entries are color coded by severity. Also there is a letter following the date and preceding the / slash:
Blue & "I" for "Info"
Green & "D" for "Debug"
Orange & "W" for "Warning"
Red & "E" for "Error"
??? & "F" for "Fatal"
I understand. But just wanted to be sure I wasn't missing something. As it stands now, all the GSM messages are Info (blue). And they're still happily chugging along.
What shows in the details if you click on Maps in GSam? Maps is notorious for sucking large amounts of battery even when you aren't using it. Try disabling Maps temporarily.
What was the Total State Time on your CPU Spy stats? That stat is cut off at the bottom of your screenshot. The other CPU Spy stats show the phone in Deep Sleep most of the time, which is good.
But the GSam stats show the phone being held awake 4 hours out of the 8 hours, which is bad. Apparently the GSam stats were taken before the CPU Spy app was even started.
The GSam stats show high usage by the Kernel, which is bad. We need more info on the Kernel stats. If you click on the Kernel item in GSam stats what system processes are at the top of the detail list?
Still pondering why your S3 is doing GSM.
In GSam if you go into App Usage and click on
I thought this was interesting. GSM Service: In Service.
Here you go.