yashsingh1/xdaforums huggingface dataset:
[myTouch 4G Q&A, Help & Troubleshooting] sharly:
I'm having trouble finding the APN settings for Simple Mobile on the MT4G ANYWHERE on the internet. Can someone please help???? Please please please! :D
[myTouch 4G Q&A, Help & Troubleshooting] oc3rulz:
It's the same for almost any smartphone.

A one second search yielded the answer immediately, so that pretty much leads me to believe you never searched. Never the less it's X-MAS and this site is about teaching/learning, so happy Christmahanukwanzakuh!

http://www.mysimplemobile.com/Support-Center.aspx make sure to click on the Phone Programming Tab Android is the first one
[Android Q&A, Help & Troubleshooting] surendrashet:
I lost my recovery img when I upgrade FRG83D on my nexus one.can any body help me plz....
[Fascinate General] Daswolven:
I know this is beating a dead horse to a pulp, but I'm going to ask any way. I have never been a typical user, and I burn my phone to the ground fast. My usage fluctuates so much testing is almost impossible.

Just asking anyone who has had the patience what they have found the best results with.

I'm currently on Super Clean 0.9 and the OTB ul 1200. Flameless responses appreciated.
[Fascinate General] Kamar234:
I have the same setup that you do and it seems that I am blowing through my battery even faster with the lower voltage, which makes no sense. I also have noticed significantly worse battery life with DJ05. Not sure if you have noticed these things as well and was the reason for the post.
[Fascinate General] ksizzle9:
Im not sure if super clean 0.9 is based off of dj05 as I use my own fragmented rom with prices of everyone elses ROMS. But the best battery life I get is out of dj05 for sure. Running a random kernel that I think adrynalyne or jt posted in irc and I usually get a full day with moderate to heavy web browsing and 3-4 hours of music. But I also have outstanding 3g in both of the places where I live so that doesn't deplete my battery like most people
[Fascinate General] rmtobler:
With stupidfast 1.54 and superdark dj05 I feel like battery life has improved. I can go through a whole day, minimal use, and still have 82% battery life at the end of the day or hover around 40-50% with regular use.

its 9:20pm right now and I am still at 76%. With some browsing, music, phone calls.
[Fascinate General] Daswolven:
I have seen the same with lv kernels both here and on my N1. possibly needing more pull for higher resource usage, but I'm lacking on the technical knowledge to make sense of that, and have had too much egg nog as of now. :D
[Fascinate General] Daswolven:
I somehow seem to get better life from a stock with BS apps removed, but like I said, haven't tested properly. I usually hate battery life threads but have been aggravated by 9-10 hours before death as of late. Probably just excessive usage, but I'm banking on the community to share exp. with their phones. :)

Flameless response appreciated.
[Fascinate General] Daswolven:
ROFL. If I could ever put my phone down i might see better life. :) I like the stupidfast, but saw some minor performance delays that led me back to voodoo. Not much of an improvement on my life tho.
[Fascinate General] Powell730:
I have been frustrated with battery life on the sf from day one. I called VZ the other day to have the lady tell me it's normal to charge it 3 times a day due to widgets, I then proceeded to waste my breath by telling her I don't run widgets.. Her response was well they will still drain your battery.

I don't want to un root my phone just to take it in to a store and get the battery replaced and apparently calling them won't get me any where either :(
[Fascinate General] syaoran12:
I use blue tooth + 3g for an hour drive to work and since the voodoo 5 kernels with the ul settings I have been at 85+% each day from the normal 75+%. So my battery life has improved greatly! Keep up the awesome work devs!
[Fascinate General] Hitokiri24:
I get pretty decent battery life out of the DJ05 OTB Voodoo sv combo (around 7 hours with periods of heavy usage). I also use juicedefender but I've heard it cant control the CDMA radio properly (ie disable data and etc) but it appears to lengthen my battery life (could just be a placebo effect however)
[Fascinate General] justinc101011:
I had the same problem....crappy battery life with DJ05 and I tried everything from wiping to endless kernel/rom combos. In the end I found out standby was killing me. Like sometimes an hour would pass without me touching my phone and it would drop 5%. Someone suggested dialing *22899 ( I think that was it) and it was instantly fixed. Now idle I drop maybe a percent every 3 hours.
[Fascinate General] soba49:
What I have found is the governor does a great job of managing battery use of the CPU in conservative mode. My best combo is jt 1129 novoodoo kernel paired with black hole 2.1+ (I noticed no significant difference between 2.2 and 2.4 for battery life). My usage is fairly high, 3-8 hours of display on each day, running light apps (hardly any music, never games, synched email). Some of my numbers are posted.

Counter to intuition, I can't seem to get aggressive undervolt kernels to give me an improvement. I think it is because the minimum processor has to be kept a little higher to sustain the underlying, so on average more offline drain. This makes no sense though, because when I look at it in os monitor, the governor seems to be doing fine.

Speculating here is pretty dicey, because I have a hard time doing a lot of testing of something that doesn't seem to work. I use my phone a lot, and it is hard to justify having 40% less life span when I know of better combos.

In summary:

* I have NOTHING to say about voodoo kernels.

* negligible difference from leaving wifi and GPS and live wallpaper on.

* negligible difference between dj05 roms.

* running a custom rom gives a noticeable improvement betrays simply running ADW on to of touch wiz

* stock kernel is pretty darned good for battery life, competitive with best kernels.

* the cpu does great self management stock and mostly runs at 100 mhz for my use

* certain under volt kernels appear to under perform during non intensive tasks, but it is hard to be certain.

* bluetooth matters, only turn it on when driving or planning to talk; it does eat battery.

* leave brightness at auto or lower, pick a dark theme wherever possible. Display is the number one eater of battery. White sucks your life.

* there isn't a lot you can do to optimize battery life. Retraining the battery either works or it doesn't, but it isn't really necessary for most system or kernel changes and should be done infrequently.

* there are a few ways to eat battery fast.

* use a theme that shows battery in 1% increments, great for sanity!

* rule of thumb display on uses 4.5 times the power of display off for light apps. -- So theoretical max life on this phone is around 8.5 hours with display on, 42 hours with display off. (typical is about 4.5 hours of display on before I charge it) and yeah I should check my math... I have never had a practical test anything close to 8 hours. I would expect about 6.5 if I never locked it and kept it running in a dark app, with little data and sound use. I think a review I read got about 7.5 hours of playing avatar on loop (probably tmo galaxy s)- a result I found mystifying at the time. My personal best is about 5.5 display on.

Swyped w/ XDA App. When in doubt, jingle.
[Fascinate General] RacerXFD:
That was very informative.
[Fascinate General] dricacho:
I'm on Blackhole 2.4 and I tried one of the Stupidfast undervolted kernels (v1.5.4) for a week and although the battery useage improved a bit, it was somehow affecting my phones wireless reception, wifi and mobile signal. My phone usually flies thru webpages at home when it gets wifi yet it was crawling when I was on that kernel. My phone would randomly freeze as well. I just switched back to JT's 12/12 DJ05 kernel and eventhough battery useage is less desireable, I got my wireless reception back. I also just switched to a dark wallpaper, used to have an ocean / blue sky image as wallpaper. I think those beautiful/fancy weather/clock widgets affect battery useage on how often it updates itself. I switched out of beautiful widgets to gTabSimiClock widget, see if that makes a difference. I like its more simpler look.
[Nexus S Q&A, Help & Troubleshooting] selectormoldy:
I've been experiencing an issue with the Home button since the day I got the device.

A few times the Recent Applications screen has popped up seemingly on its own, while I was in the middle of doing something else. At first I thought it was just a software glitch and carried on. The haptic feedback pulses twice quickly. The backlight of the Home button turns off, the backlights for the Back, Menu and Search buttons stay on, the Back, Menu, Search and Home buttons no longer respond to touch or generate haptic feedback, essentially paralyzed. It remains this way for approximately nine seconds before the Home button lights up again and the all of the shortcut buttons become responsive again, otherwise the only way to get out of the Recent Applications screen is to either cycle the power button and unlock the screen, or select one of the recent applications.

I have figured out how to reproduce this problem by pressing around with the very tip of my thumb along the seam where the glass and plastic lip meet with a little more pressure than normally necessary to register a touch. I am careful to avoid touching the normal hot zone for any button. I start from the far left corner under the search button, and make my way towards the home button little by little. Somewhere between the Menu and Search buttons when I release my thumb after pressing firmly, the haptic feedback pulses twice and the issue occurs. I can reproduce this issue anywhere along the edge on the bottom right half of the phone and about 1" up the right side of the phone, far from the Home button.

I suspect there is something wrong with the capacitive layer of my screen.

Please see if you can reproduce this or something similar on your phone, just bear in mind that you will need to press firmly (not too hard but not soft).

The unfortunate thing about this problem is that it can be activated inadvertently while gripping the phone during normal operation, interrupting whatever you are doing for the time it takes to resolve itself.

This is literally the only issue I've had with the phone in the week I've owned it and I am considering whether or not I want to play russian roulette with exchange units (and other issues like bad screens and bad weak back buttons) because everything else seems to be perfect.

Video of the issue in action here:

http://www.youtube.com/watch?v=5gqqeVbePYA
[Nexus S Q&A, Help & Troubleshooting] ztm.000:
Same thing happens with me on the swap unit I got today. Bummed like no other.
[Nexus S Q&A, Help & Troubleshooting] unremarked:
Tried replicating this with my device with (thankfully) no results.
[Nexus S Q&A, Help & Troubleshooting] selectormoldy:
one and one... I wonder how many other phones are affected then, and how many people have it but haven't noticed yet, e.g.; "you're holding it wrong". :)
[Nexus S Q&A, Help & Troubleshooting] Xandlinger:
Hm. Just tried to replicate this on my Nexus S, no issues.
[Nexus S Q&A, Help & Troubleshooting] midyear66:
Mine did the same thing at least twice a day. However, it has not happened again since the GRH78 update. (Knock on wood).

Have your received the update?
[Nexus S Q&A, Help & Troubleshooting] ericc191:
This just happened to me for the first time about an hour ago. I have the new update too, sadly.
[Nexus S Q&A, Help & Troubleshooting] selectormoldy:
Yes I have the update.
[Nexus S Q&A, Help & Troubleshooting] ztm.000:
I can't replicate this problem, but nonetheless, it still happens.
[Nexus S Q&A, Help & Troubleshooting] tokomoto:
I have this same problem with my back button. I can't replicate it but it just randomly happens to me. I have the update and I also tried using Paul's Tom and it still happens.
[Nexus S Q&A, Help & Troubleshooting] redcodefsu:
This happens with my back button.
[Nexus S Q&A, Help & Troubleshooting] bledina:
happens to mine too, also the home button. doesn't bother me too much, though. and I also have the update.
[Nexus S Q&A, Help & Troubleshooting] bledina:
I had something even weirder tonight.

I did a factory reset, then proceeded to install everything back on when I noticed that my home key wasn't doing its job at all. Still had the haptic feedback so the input was received, but it did absolutely nothing. So I did another factory reset and that seemed to have cured the problem. My home button is working again (but i still have the other problem from time to time)
[Nexus S Q&A, Help & Troubleshooting] selectormoldy:
Had it happen again inadvertently today, if you notice from my video the spot where it can be activated next to the Maps icon also happens to be conveniently where your finger ends up when swiping to unlock. I was holding the phone one handed and unlocking with my thumb and it triggered the problem. Might try for an exchange this week. It shouldn't behave this way.

For those of you who are experiencing it with your Back button, does the backlight turn off for 9 seconds on your Back button?

I don't know everything about how the hardware works but I'm guessing that there is some kind of short, the controller for the capacitive layer gets confused and resets. Could explain why it takes the same amount of time to come back to normal every time. It also seems like it might be related to case/screen flex, where pressing on a part of the case bends the capacitive layer just enough to short the circuit.
[Nexus S Q&A, Help & Troubleshooting] ViLANDER:
This issue came on my two days old Nexus S too, but with the back button. It has happened two times now. I think that's a software issue that come along with Gingerbread. It's something like it registering a touch and sometimes the OS think it was the buttons that were pressed...
[Nexus S Q&A, Help & Troubleshooting] selectormoldy:
Does your back button black out for ~9 seconds?
[Nexus S Q&A, Help & Troubleshooting] mortzz:
I haven't had any button issues whatsoever since I got mine on the 24th.
[Nexus S Q&A, Help & Troubleshooting] ViLANDER:
No, more like two seconds.
[Nexus S Q&A, Help & Troubleshooting] selectormoldy:
Here's a new video shot today showing the issue occurring with only normal light touching:

http://www.youtube.com/watch?v=z6YFcOZwX2o

Also last night it happened while I was inserting a cable into the headphone jack.
[Nexus S Q&A, Help & Troubleshooting] selectormoldy:
I've sent both videos to @GalaxySsupport on Twitter as well as the link to this thread and they are going to pass it on. Hopeful that we can get an official answer from Samsung and/or Google, as the problem is a hinderance to normal operation.
[Nexus S Q&A, Help & Troubleshooting] ViLANDER:
You've got more serious problems with your buttons than I. My back button bug just appear for one sec and actually I think that must be a software related bug.
[Nexus S Q&A, Help & Troubleshooting] selectormoldy:
Samsung support suggested I exchange mine and I did.

I'm on my third unit now.

I exchanged my first one and received one with an extremely faulty touch screen, whole sections of the screen would become unresponsive to touch every few minutes rendering dialer, keyboard, and certain home screen icons unusable.

I've experienced the same issue with the back button twice now on this third unit (in 3 days). Home button is behaving correctly and I have been unable to reproduce the back button glitch although it does exist. Also the volume rocker is solid (does not rattle) and the oleophobic coating seems to be superior. Can you tell me what the manufacturing date was on yours? Mine have all been listed as December 9th on the Samsung registration site. This one seems to be the best I've received so far.
[Nexus S Q&A, Help & Troubleshooting] ViLANDER:
My date was: 12/9/2010.
[Nexus S Q&A, Help & Troubleshooting] alpha300:
I have the exactly the same problem with my back button on my nexus s. I hope its a software issue.
[Nexus S Q&A, Help & Troubleshooting] selectormoldy:
Just had the back button problem happen again.

This time it was in my car, driving with Waze running and the phone in a generic car dock (the spring-loaded kind with foam grips that hold the sides of the phone).

Back button brings up a menu in Waze with options including exiting the application. If you hit the back button while the menu is up, the menu goes away.

The back button was blacked out and the menu was appearing and disappearing rapidly, repeatedly. The screen is definitely registering a back button press even though nothing was touching the back button. It's like a phantom long press of the button.
[Nexus S Q&A, Help & Troubleshooting] justsignbythex:
Just to compare, my first unit (manufactured 12/18/2010) had a defective back button. It would still function and light up, but just wouldn't be as responsive as the other 3 buttons.

My current/second unit, manufactured only a day after on 12/19/2010, is flawless.

It seems that the QC on these units aren't that great, and you'd have to be lucky to score a perfect unit on the first purchase.
[Nexus S Q&A, Help & Troubleshooting] Ry-Guy615:
I was having similar issues with my home button registering phantom long presses. Occasional but less frequent back button issues as well. I started to notice after installing noLED. So I uninstalled noLED and haven't had another problem yet. Could be a coincidence and it's only been about 24 hours since removal of the app. Curious to see if others with button issues have noLED installed.

-Ryan
[Nexus S Q&A, Help & Troubleshooting] selectormoldy:
I don't use noLED, I think that's a coincidence. It also seems like this issue might be exacerbated by the temperature of the phone changing. Playing Pocket Legends, the phone begins to warm up a bit. Multiple phantom back button long presses occurred during play, and I had the handset flat on a table while using only my pointer finger far away from the back button.
[Nexus S Q&A, Help & Troubleshooting] Farb63:
Heat related.

I think you are on to something. After your comments I set my non-responsive phone (back button) down in a cool place and it behaved normally after about five minutes. Summer might prove interesting when ambient goes back up. :(
[Nexus S Q&A, Help & Troubleshooting] ViLANDER:
You mean me? :p

And what do you mean with QC? :)
[Nexus S Q&A, Help & Troubleshooting] distortedloop:
Quality Control...

not sure if your question was serious or not.
[Nexus S Q&A, Help & Troubleshooting] mayhem1983:
My buttons are ok just my back button messes up sometimes I have press it real hard for it to respond it comes and goes anyone having the same issue?
[Nexus S Q&A, Help & Troubleshooting] selectormoldy:
Our problems aren't related to a lack of response, but bizarre behavior (buttons long pressing themselves intermittently).
[Nexus S Q&A, Help & Troubleshooting] Farb63:
Back Key.

Would someone try holding their phone in front of their AC or other cool air stream when they are experiencing problems and see it it resolves the problem? I am batting 100% with doing this. Unfortunately as soon as the temperature rises I am right back where I started.
[Nexus S Q&A, Help & Troubleshooting] selectormoldy:
I can't seem to get it to reproduce as easily on my third handset as I could on my first handset. But I had it happen while I was outside in cold weather today, and also inside while using it for the first time after an overnight charge.
[Nexus S Q&A, Help & Troubleshooting] selectormoldy:
OK. Here's a fun little test which I think helps explain some of our problems.

1. Go to Market (just for example, so you are at a screen you can go back from)

2. Press and hold back button

3. With another finger, press and hold menu button

4. Release back button while continuing to hold menu button

5. Notice the back button backlight is off (phone still thinks you are pressing back button)

6. Release menu button, back command is issued

Now follow those steps up to #4, but start counting in seconds and do not release your finger from the menu button. After 10 seconds the back command should be issued without lifting your finger. You should also notice that by simply holding the back button normally for 10 seconds it will issue the back command without lifting your finger.

What we're simulating here is part of the issue with the back and home buttons on some handsets. Sometimes our buttons detect a finger touch (in my case often erroneously), fail to detect a finger release, and we have to wait for the 10 second timeout (what I previously described as "paralysis").

If the 10 second timeout is normal operation for Android, it seems like there are indeed hardware issues at fault here. A lot of users are reporting that their back and home buttons do not detect finger touches reliably, but in our case it appears that the buttons are not detecting finger releases reliably.
[Nexus S Q&A, Help & Troubleshooting] gap0210:
Now were getting somewhere. I have the same problem. This one is going back.
[Nexus S Q&A, Help & Troubleshooting] markeph:
I replaced my first ns due to intermittent problems with the home button only. I've had my new handset for over a week now and no matter what I throw at it, the soft keys have remained super responsive throughout. I've been left in no doubt that some of these phones have hardware issues with their keys.
[Nexus S Q&A, Help & Troubleshooting] selectormoldy:
Posted on Google Support. Please star and add your two cents if you have a chance. Thanks.

http://www.google.com/support/forum...ad?fid=455215ff8747658b0004998517ff30a4&hl=en
[Nexus S Q&A, Help & Troubleshooting] ViLANDER:
Done.

10 chars.
[Nexus S Q&A, Help & Troubleshooting] gap0210:
If you want to test this issue on your phone. Put your index finger lightly on the home button and run it lightly towards the back button. You will feel 3 vibrations instead of 4.
[Nexus S Q&A, Help & Troubleshooting] Epiktetus:
Yeah, the heat suggestion makes sense to me too. I'm having phantom home button presses that escalate when playing games. I'll try to return it, but it sounds like that might now solve the problem.
[Nexus S Q&A, Help & Troubleshooting] selectormoldy:
I exchanged at BestBuy for a new unit manufactured on 12/18/10. So far so good.
[Nexus S Q&A, Help & Troubleshooting] eladkatz:
Same here

Same thing happens to me, stock, no rom or anything, since day one

very annoying!
[Nexus S Q&A, Help & Troubleshooting] foxehkins:
I'll be trying to return mine soon. Hopefully they let me.
[Nexus S Q&A, Help & Troubleshooting] selectormoldy:
A response from Google!

http://www.google.com/support/forum...ad?fid=455215ff8747658b0004998517ff30a4&hl=en
[Nexus S Q&A, Help & Troubleshooting] ViLANDER:
Saw this recently. Really nice!
[Nexus S Q&A, Help & Troubleshooting] Farb63:
Any update to this issue?
[Nexus S Q&A, Help & Troubleshooting] coloxim:
I've the same problem....any solutions?