yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
The only reason I even asked is because under the exact same conditions, location, streaming content, but only difference being a different kernel/gov, my drain while streaming pandora was about 2% an hour.

Since the idle drain with nothing was mind blowing, i'm just trying to think of a way I can replicate the streaming drain without compromising the idle drain too much.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
U have one of the rare ones that needs high voltage... Try dkp the special version lol

sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
run a logcat while playing music. do u have a continuous error from lpaplayer? this happens to me unless i go into build.prop and change lpaplayer from true to false. maybe this could help you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
I'll check it out! Thanks!

Just curious, do you have this problem specific to this kernel or in general?

catlog was showing TONS of these errors a second so i went in and set it to false, errors no longer showing up. Will be testing for batt life. If this works i'll be one happy camper.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chrisj22:
Yea all of that upon install. I'm using hellfire newest release
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bakasam:
Yeah seems to be the case. I'm on deviant xone rom so it should be 3.4 supported
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Whatever you or cyanogenmod did in the latest 3.0 release seems to have brought back the audio sputtering bug. :/ it wasn't doing that on the last release.

The log cat looked the same as it did when it skipped before. Want me too pull it for you?

Sent from a Galaxy far far away...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
MBC663 Thank you for this. Freakin LPAplayer was draining the life out of my wife's battery. I just stumbled upon your reply and made the changes to build.prop and it's no longer there. Thanks dude. :good::highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] leos0000:
Best kernel ever fast and stable just problem with battery idk why ****
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheSchatz:
Hey KT, had my first spontaneous reboot with your latest 3.4 kernel.

Not sure what caused it, but here's my last_kmsg http://db.tt/5iEIrA1p if it interests you.

No other problems to report, thanks for your awesome work!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thanks for last_kmsg, looks like the same issue with adreno/video driver interaction
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Sorry for the off topic.

Does anybody knows if our phone has the same broadcom bcm4330 WiFi chip set as the gsII? I searched all à round the net but it is not specified anywhere
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] byte9:
No, the GS3 supports both 2.4 and 5ghz wireless N. The GS2 does not.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Sgs2 supports both 2.4ghz and 5ghz also. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
But not very well (except for Entropy) ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
It has the bcm4334 ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Damn :( no monitor mode for me then. Thank you for the info tho! Where did you find it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
My computer. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I feel stupid now :banghead:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] byte9:
You feel stupid. I (incorrectly) took a time frame guess on assuming it didn't have 5ghz N for when it was manufactured. That being said, go go Samsung for including 5ghz in a product when most would have put 2.4 with a smile.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] trh1341:
On the latest release I had to disable HW overlays to stop the screen from freaking out when anything on the screen changes..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
reboot message

Hey KT... I haven't had a restart in quite a while. I was plugging into computer's USB when this happened... Your newest along with Task's newest ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Im guessing you cant reproduce it very easily?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
No... it was the only one, and not since either... makes perfect sense then... :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Getting random reboots on tw version with any hot plugging governors or with auto hot plugging checked. Deleted the usual tw system/bin files. Reboots don't produce a last_kmsg, is there anything else that might be helpful?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
This kernel is the sweet tits.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
^This.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
Could not have said it any better.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] leos0000:
Yea.This Kernel its so sweet and best ever.Thanks Devs .
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sk8trix:
I am using The last 4.2 aosp kernel released along with the newest nightly.I have one small question.

U am getting some immediate reboots when I clock to 2.1Ghz if I stay one step below I'm fine.

My thermal throttling is set at 55 and 60 degrees

What is the max safe temperature for our devices? Att S 3?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
That's kinda debated... the hotter you go the lower the life expectancy. Stuff gets worn out. I'd maybe say, for myself alone(if you break your phone I'm not responsible), maybe 65-70 C maximum

Sent from a Galaxy far far away...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sk8trix:
That's what I've read too that's what blows my mind because it will restart and its usually running somewhere around 40-45c which is write this started a few build with the previous build and this newer one for me if I'm sitting at 1.5Ghz stock its runs amazing its just at the max freq that my phone gets retarded
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] leos0000:
Wich governor do u use man and shedule
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
If you get an instant reboot at 2.1ghz, it means your phone just can't over clock that much. There's nothing you can do about it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sk8trix:
Even though I was able to run it at those frequencies in past builds?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
In past builds it wasn't really that high. Some math was wrong and overvolting wasn't as high as it was set for
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Yep, you need to read the changelogs
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
KT explained this in detail about a hundred or so pages ago. Do a search. You will not overclock to 2.1 now and you did not before, you just thought you did. About 1860 was rendered 2100... these phones were not made to handle that kind of OC... and they don't.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] friedsonjm:
OK, this is going to sound a bit bizarre.. upgraded to latest Task650, latest TWRP, 'installed' this kernel, booted, 'underwear' boot graphics gone, this kernel's in place...but... after boot, ktweaker not installed, and system info still shows task's kernel! I've installed the ROM and kernel many versions many times.. this is a first.

Thoughts? jf
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
You have to flash the kernel after flashing the ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] friedsonjm:
Of course, that is exactly what I did... twice. And, for that matter, ONLY flashing the kernel. jf
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
I would redownload the kernel.zip - If that doesn't work, clean flash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] friedsonjm:
Yep, re-download did it! thanks. jf
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mahler47:
Random Reboot

Been getting random reboots for about a week. I haven't been getting anything useful from last_kmsg, but this morning I did get something. Can anyone diagnose and better yet, suggest a fix?

I'm running CM 4/14 build with the 4/11 kernel build, no OC, stock voltage table. Using interactive/row, auto hotplug off.

Thanks!

http://pastebin.com/aAhzju4c
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
First thing would be to try changing your scheduler/gov.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] geoldr:
Thanks for the kernel. I am using it on TW Intergalactic and with the Ktoonservative I lose only 1% over 8hrs at night. Also I am really glad I can disable the trinity colors because it just makes my screen so blue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
KT

Just had another reboot but I think I noticed a common thing from last time:

It looks like reboot happens exactly at the time when MHz overwrite kicks in. I have my battery high set at 30% to go down to 1026 from settings in OP. I think at that moment when it lowers mhz it rebooted last time as well as now. Last kms here if you want to have a look

http://db.tt/LcAAS6vu

Thanks.

EDIT: Looks like the same error as last time - modem:

[13637.070652] SMSM: Modem SMSM state changed to SMSM_RESET.

[13637.076573] Notify: start reset

[13637.076664] Probable fatal error on the modem.

[13637.076695] modem subsystem failure reason: (unknown, smem_get_entry failed).

[13637.076725] subsys-restart: subsystem_restart_dev(): Restart sequence requested for modem, restart_level = 1.

[13637.076756] Kernel panic - not syncing: subsys-restart: Resetting the SoC - modem crashed.

Could this be related to the change in freq, with battery control?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Yep, modem again, wonder what the heck is wrong with your modem to keep doing that, really bizarre.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Looks to be the same thing people are getting, seems to be related to wifi drivers not going to sleep and when it tries to wake it crashes, I still cant reproduce it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
The 4/11 build has been the best 3.4 kernel for me yet, KT. Can't thank you enough for your work. I wish everything in life was as good as your kernel! :D:thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
In response to this, I'd like to say that my phone handles 2.1 perfectly, even on the newer releases.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
guess you got the only one... ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
1350mv on that 2106mhz? Or did you need higher? Stable as in what? Stable for browsing but not for a full antutu run as I would expect or quite the contrary? Just curious :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
1350mv. Stable on all benchmarks attempted. I can't run it at 2106 on touchwiz though.... Just aosp.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
Very cool so your on the 3.4 kernel with corrected math on upper mhz and that's something funny there on Touchwiz lol go figure... AOSP has much less overhead so maybe its stable due to the lower ram usage and resources being used up at all times like in Touch Wiz. But shhhhh buddy lol don't encourage many people to try 2106mhz lol as just before a few were thinking there was something wrong when they couldn't get to 2106mhz anymore. Most will never even stay stable to sit idle with a 2106mhz max just end up rebooting upon applying. Joking aside enjoy your phone, most of these CPUs can't handle the stress at that level overclock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thegame3202:
Hey Ktoons! (and/or anyone else ;) )

I've been having an issue where after a 15 minute or so phone call, my phone screen freezes on, and I have to pull the battery. People can't hear me and vice versa and it just shows the phone screen like I'm on the phone, but obviously non-responsive and the call timer isn't ticking. I have the "screen off MHz call" off. Running 4/11 3.0 kernel on AOKP 3-13. Not sure if ROM or kernel issue. Any ideas on how to troubleshoot? There's no last_kmsg (but it's been like 2 hours since I had to pull batt). Thanks!

EDIT: Also, I was off a little bit :) It's 5-10 mins. Just happened again. If I plug it in, the charging LED turns on, hardware buttons do nothing no lights or anything, screen is completely frozen and unresponsive. Going to check for last_kmsg and logcat. Not sure which is more helpful :-\
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
I'll let Ktoonsez answer the hard part, but you never have to pull the battery. If you hold down the power button long enough, it WILL reboot. No reason to pull the cover (and maybe case) off.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thegame3202:
Awesome! Thank you! My case is a pain in the ass to pop off while driving. Lol! I'll try this tomorrow:)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] noamaniac:
I also have experienced this problem and cannot seem to recreate it on my own. I have tried different io/governers, voltages, clock speeds and can't seem to find what sets it off. I have even had the problem when stock settings are in place. It isn't very frequent but alacrify is correct holding power button will force it to cycle.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jbradbury:
I believe this is a known bug on AOKP for d2att.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
Not just aokp, slim and other aosp roms as well.

It is a well known issue in all the threads.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
The ROM is just to old is my best guess, why still on 3.0? Yes last_kmsg can be helpful.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thegame3202:
3.4 and my phone hate each other for some reason lol. This rom with intellidemand gets me 18+ hours of batt life with no crashes (except this issue). I get reboots all the time on any 3.4 rom. I've tried a bunch of governers and schedulers to no avail. Even did the +25 you suggested :) I'll grab a last_ksmg next time it happens. I have this one now, but not sure if it's the right one. I held down the power button to restart. Thanks Ktoons! And hope you got a couple beers with my donation ;)

EDIT: Also, any plans on adding a Bluetooth stack that can support a wiimote? ;) I tried an app and got "no route to host" and something about unmodified Samsung devices.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Same here I can't use 3.4 kernels I get horrible battery life constant reboots and that static screen glitch.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phantomofheat:
I have had the same problem with the screen not coming on but it is a 3.4 issue it will happen on cm For me with all settings from any version to date some nightlies are better than others but the issue will pop up with in 24hrs. I have to stay with the last 3.0 to keep from having the issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Hi KT. I'm using Ktoonservative, as always, but my Sampling Rate NOW will not come off of 10000. I have it set to 30000, min 10000, and off to 75000. Every time I leave with it at 30000 (it has always worked before) and go back in, it is immediately back at 10000. I looked at the config file and it is at 30000. Any idea why it won't stick?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] metalchef:
I kept getting fairly consistent -- yet random -- screen wakes with latest version of TW kernel (KT747-Kernel-TW-JB-ATT-04-11-2013) on stock VLDLK4, so I went back to stock kernel 3.0.31

And the worst part is, I forgot to ask if submitting a logcat would help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chipstien:
Hey KT. Have a strange battery drain. Tweaker had top battery usage today. Using Task 4/12b and your governor. I did change up threshold to 90 and down threshold to 50, freq step to 2 and sampling rate screen off to 100000(which is my best guess as to the cause). Going to drop it to 90000 and see what it does tomorrow.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
Ktweaker doesn't run in the background technically so it must of been still open in foreground perhaps you hit home vs backing out of app...? There is very little to Ktweaker almost everything is part of the kernel and ktweaker merely presents a gorgeous user interface to adjust our kernel parameters. I'd say swipe the app from recent next time or give a full reboot and do a run from boot without entering ktweaker.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
test FLOAM.... :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jgaf:
Hello KT,

I just had my first random reboot in a long time. It happened after I turned off the screen. I am currently using Task's latest ROM and your latest kernel. Most likely is that I undervolted too much, but I want to make sure. Although everything has been running smoothly even gaming.

I am using Row and ktoonservative (adjustments: boost_cpu 1296 and sampling_rate_screen_off 90000), no OC 189mhz-1512.mhz. My voltage table is -100 (I played ingress which uses a lot of power and no reboots so far). Anyways I attached my last_kmsg to this post. If you need anymore info let me know.

Thanks in advance :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
Standard troubleshooting procedure would be to increase your voltage table. -100 is pushing it, I believe KT is running -25 across the board. I didn't have a single reboot with Tasks 4-12 build and those settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rfb813:
Am on Hyperdrive RLS11 and installed the latest 4/11 TW version. The ROM is running great and good battery life. Using on demand gov and noop scheduler. Am also oc to 1674. Went back in to look for qosmgr in system/bin but not there. I did a search and the latest on Apr 8 says still change qosmgr to qosmgr.bak. Has anything changed? Am I missing something. As said the Rom is running great.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
They must have removed it from the ROM so you are good to go.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
Anyone get this booted on tasks 4/19?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
NO ONE WILL GET MY LATEST RELEASE TO BOOT WITH TASKS RELEASE FROM TODAY!!!!!!!!!!! CM MADE DISPLAY UPDATES YESTERDAY. You will have to wait a little bit for me to upload newest.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jgaf:
The thing is it has only happened once, I am not able to recreate. I've been running with those settings for a day and a half without any problems, except for that one reboot. I want to know what my kmsg says went wrong, maybe the error was not related to uving.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
If it only happened once and you are not able to reproduce it then it could've easily been a fluke, an app that decided to go haywire, ect... If you can't reproduce it then I would just forget about it if everything's running fine now. Not really worth the wasted time if it's not a reoccurring issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Did somebody say my name??? :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
OP Updated

This version will only work with Task's AOKP from TODAY and 4/19 CM nightly

Change Log 4.19.2013

1. Linux 3.4.40

2. Linux 3.4.41

3. ROW scheduler updates

4. Update to date with CM and code aurora

5. Lots of Linux patches for SMP and some optimizations

6. More but no time........
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
Awesome Linux 3.4.41 !
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
Confirmed running on the 4/19/13 CM nightly. No more of the animation jitter I've always had on 3.4 kernels.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thanks for confirmation on CM, updated my post :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Psychosi42:
Won't boot for me. I'm running CM10.1 M3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
It only works on builds from today or newer.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
So long as AOKP official boots, I'm happy. Big ups toons.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Unless the official AOKP has a release for today it won't.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Psychosi42:
Ah reading comprehension 4tw
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Ah poop.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jaysmi32:
ktoonz, is nightmare fixed in this version?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
No. All the one that don't work for 3.4 are still broke
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jproy12:
Do you have the link to the last 3.4 kernel before the one released today?

JP

Edit: found it on page 1116!

http://xdaforums.com/showthread.php?t=1756776&page=1116
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MWilkenson:
For some reason I'm having random reboots on the latest kernel. Full wipe, tasks latest. All stock values except min I bump up because I thought that was the issue.

https://www.dropbox.com/s/vhxr8cjj4xye5jp/last_kmsg1.txt

I would appreciate it if you have time to look at my last kmsg. If not then no worries! Thanks for your work man
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] G-Man.:
Kernel running great with Tasks latest! Thanks for all the work you've put into this dude! You should see the cool stuff my device does now :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Nothing good in there unfortunately, just a generic "raw_spin_lock_irqsave" unhandled error that could be from anywhere. :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xBeerdroiDx:
kernel running solid on aokp's 4.2.2 milestone release. thanks for all the work, kt!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MWilkenson:
Well thanks for looking into and taking time. I switched back to the underwear kernel for now. Your awesome though man
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] s384:
im running max mhz screen off at 81mhz. is this safe? streams music just fine. and loses maybe 1% of battery idling all day. love it! thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Of course its safe, Overvolting is really the only thing that can over heat your CPU with can be bad. Awesome numbers
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
This version will only work with Task's AOKP and CM nightlies that are from 4/19 and newer

Change Log 4.20.2013

1. Butt-load of updates from CM last night so you guys are up to date

ENJOY!!!!!!!!!!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GalaxyHeart:
4/19 with Task's 4/19 was the smoothest Android experience I have ever had.

4/20 feels just as buttery. Thanks, Ktoonsez!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] s384:
why do most people run higher mhz with screen off? wake up times are sfficient for me. and no performance issues. and clearly easier on battery. im just worried about the phone not waking up when I get a call or have alarm set. otherwise great. yes thank you
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tprophit:
If voltages are the same for 81 and 378, would battery drain be the same for screen off irrespective of whether it was set at 81 or 378?

Thank you.