yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RampageRR:
Are you sure you have the CWM fladhable zip? You might have the zip that just has the 2 files you need without the installer script. Just open the zip and place both files in system/cameradata. Overwrite the 2 files currently in there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ThatTmoGuy:
try a different launcher like nova, then you can setup the second press to open any app you like. the app you are looking for is simply voice search.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dmize:
Haven't noticed any other posts on this, but are the animations for locking the screen in place or bugged? I see the options for screen on and screen off there but nothing happens.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Hypercore:
Flashing CM10 has also removed my hardware unlock. It's asking me to type in my SIM unlock code again but the code isn't working. Not a huge problem because data. calling and texting all works for some reason but I'm still curious as to why it's doing that.

The build on the other hand is fantastic, I absolutely love Android 4.1 and you're doing a great job developing it. Keep up the good work!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theadb:
Netflix video isn't playing for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jshamoon:
Latest build is AMAZING! Cyanogen, beer coming your way. This is the first build where the camera works after the fix is applied! One issue though, I can't get the phone to go into landscape, lol. I unchecked and checked the settings with no success. I am using Nova launcher which worked fine before. Any suggestions?

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Hypercore:
Camera fix? Am I missing something? Could you provide the link for me please?

Edit: Nevermind, found it. For anyone else wondering where it is: http://xdaforums.com/showpost.php?p=28957409&postcount=458
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fruitycups:
from the "lost imei" post i just read, im a bit nervous on reverting to stock.

Does anybody have step by step directions on how to revert to stock from CM10?

I don't think its as easy as just loading up ODIN and putting the stock firmware tar in the PDA slot :/

ALSO

how would i flash this updated version when Im unable to move the zip over because of the messed up MTP? My comp doesn't read the phone at all.

(hoping that both questions are answered!!!!)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ThatTmoGuy:
i went back and forth a few times already, just use your nandroid you made before installing CM10. you did make a nandroid right?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jshamoon:
Scratch that, I switched back to the stock launcher, landscape worked. Went back to Nova for kicks and it worked. Veerd. All is well! :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Hypercore:
You can use the Rogers/Telus/AT&T .tar files in the General section with Odin to revert back to stock.

Also, install AirDroid if you have WiFi in your house. You can transfer files through it, very fast as well. It's what I've been doing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] IpodLover77:
I was curious about this also, so does just restoring the stock firmware also restore the stock kernel for you or do you first have to find the stock kernel, flash that through odin, then flash the firmware.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MicroBerry:
Can anyone confirm if wireless hotspot is working for them with this new update? It used to say it was on, but i couldn't connect any of my devices to it. Had to go back to cm9 to use the feature.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Hypercore:
As far as I know the stock kernel is included in the .tar file. If not, there's a thread on here that has the stock kernel as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brorex:
You could just download the update to your phone
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fruitycups:
the reason i ask how to restore to stock is from the quote above.

I was under the impression when you flash the stock rom, the stock kernel is automatically restored to the stock kernel also. I didnt know you had to separately flash the kernel then go back and flash the rom.

ALSO

Do you guys think the person lost his IMEI because he restored to a stock rooted rom instead of the stock stock rom? Im trying to avoid any issues that may result in me losing my imei.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mitchdickson:
Could we keep this thread on topic? There is a Q&A forum for a reason.

Sent from my Motorola DynaTAC 8000X
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xetrev:
So you are running the latest nightly with 12/29 kernel and streaming audio via bluetooth with no issues?

Did you test longer than 5 minutes?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
Is the extremely low call audio fixed in 1/1/13 ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
Yeah, I tested it and it sounded fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smelenchuk:
The 12/29 KT kernel still has the audio bug present.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MoeisHere:
no its still low

---------- Post added at 10:35 PM ---------- Previous post was at 10:34 PM ----------

Have u tried it with a bluetooth headset or speakerphone? Thats when its really low
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] frankrocks:
I don't use Bluetooth. Bluetooth wasn't brought up until now.

But yes, 1-13 build + 12-29 kernel. I'll try out audio in wifeys car tho...

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xetrev:
Bluetooth will end up being borked after 4-5 minutes and speed up and sound crazy.

There is also low call volume on bluetooth during phone calls (the person on the end comes in very very low and turning the volume all the way up doesent help).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dammit_dan:
I have 3 times. Still no luck.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pwned101:
Is it just me or is audio from the speakers a lil distorted at high volume? :confused: I just flashed the latest nightly.

PS: Moved over from Dec16th CM10. Did a full system wipe (system,data,cache,dalvik,sdcard). 12-12 GApps. Stock kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goobs408:
Nope. Full wipe via ROM manager and still play music locks up the phone. 12/12 gapps 12/29 kernel 1/1 nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pwned101:
I mostly use spotify and poweramp and I'm yet to have a phone lockup with stock kernel. But coming from CM10, the audio quality degradation on CM10.1 is pretty evident.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bbgt2:
Flash KT 12-21 and 1-1-13 nightly all works great, Apollo etc.

Edit Apollo stopped working now. Trying 12-29 kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
Off a dirty flash of 1/1/13 over 12/31, in call volume is SO low I literally can't hear unless I use headphones.

Is this present after a full wipe?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pwned101:
Yup..i noticed that too (even after a full wipe)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thecapitalr:
Is there any one that has a link for 12/16 CM10? (not 10.1). Am I correct in saying that this is the last nightly for CM10? Get. Cm only links to 10.0.0. and this release continually gives me the SD card unexpectedly removed error and it is getting pretty annoying. Just looking for something stable don't want to use 10.1 yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
Did you try stock kernel or did you flash ktoonsez 12/29 before first boot?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pwned101:
Im on stock kernel..didnt try ktoonez..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
I tried with 12/29 and in call volume is heinously low. Speaker too
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pwned101:
If only u had used the search button :)

CM10 Decemeber 16th Build

http://db.tt/ZtqxYRFg
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goobs408:
Ya the 12/29 is the kernel I've been using. I might flashback to 12/21

Ktoonz 1/1/13 kernel fixes the music.

Flashed 12/21 and it worked
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
Because this is bugging me about everyone saying the same thing over and over again..

EVERYONE NEEDS TO BE USING THE 12/21 KT KERNEL

There is also build.prop fix some pages back that help with low volume and some bluetooth issues: lpa.decode=False
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dschamis:
Running 1/1/13 - I don't know of anything that is working with the 12/21 kernel versus stock - what am I missing?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smelenchuk:
I, for one, just noticed the availability of the 1/1/13 KT kernel. It sounds to me like it has the aforementioned audio bugs fixed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
A majority of people are having audio problems where system apps such as Play Music and Apollo will not play audio and cause the phone to freeze. I have this problem if I do not use 12/21 KT. There is also bluetooth audio problems.

---------- Post added at 04:49 PM ---------- Previous post was at 04:47 PM ----------

Gonna test it out now.

Edit: 1/1/13 KT Kernel has working audio for Play Music, Apollo, and Pandora YMMV

Someone will probably beat me to testing bluetooth.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sNoxious:
For those who want to use the Stock kernel and want the audio problem gone, just edit the build.prop, find 'lpa.decode' and set it to false. Use Build Prop Editor from the Market.

Sent from my Samsung Galaxy S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RegBuckley:
I am using 1/1/13 build no kt kernel and Apollo is fine
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smelenchuk:
The 1/1 build's stock kernel has this fixed already. (This, I suspect, is related to why KT's 1/1 kernel also has it working.)

---------- Post added at 05:12 PM ---------- Previous post was at 05:03 PM ----------

The Bluetooth audio hiccup is still present. I suspect this is an underlying problem with 4.2 which won't go away any time soon.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xetrev:
Latest nightly with the new kernel (KT 1/1/13) still has the bluetooth audio problems.

2 minutes in the song sped up and sounded like an alien.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chrisj22:
Make sure your on LK3 and go back and to full wipe and reinstall
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
I'm on the latest build 1/1/13 and there are no audio issues. I don't use Bluetooth that much so I haven't tested it. Running stock kernel and Pandora works without editing the build.prop.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RegBuckley:
I can't get 4G either on Rogers all I get is H+ I just figured it was because this is att rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] humblehyper:
Confirmed bluetooth audio is still bad, it stops playing then resume and the sound is like listening to AM radio :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chrisj22:
H+ is 4G LTE I believe shows the LTE symbol but Idk I don't have it in my area
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
No, H is HSPA. H+ is HSPA+. LTE will display as 4G
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] peneoark:
H+ is H+ and 4G is 4G
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smelenchuk:
Thoroughly false. On this ROM (and most similar ROMs, I assume), H(+) on the status indicator means HSPA(+) and 4G means LTE.

---------- Post added at 06:16 PM ---------- Previous post was at 06:14 PM ----------

There have been hiccups related to Rogers APN settings, so you might want to check those. I'd also check your network type settings to make sure LTE is enabled there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
OK my dudes, this low call volume is killing me. My ears are bad enough as it is, and with the volume being SO low I literally can't hear people. And also speaking on the phone today, the other person said they heard "a lot of feedback" which meant the call echo is still there. This is running 1/1/13 and ktoonsez 12/29 kernel.

Does anyone know of any files that can be edited to force an increase in call volume or is that beyond meager file edits through root explorer?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smelenchuk:
Did you see the 1/1 KT kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RegBuckley:
Yes on stock rom I always have 4G there's no lte in this area but when I go to Toronto its lte. I just don't see how 4G could be lte etc. 4G should be 4g. My apn settings are correct as I have my wife's stock phone to compare. I just happened to notice someone's screen shot had 4G on bell
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smelenchuk:
Blame the telcos for claiming that HSPA+ is a 4G technology, and making the stock ROMs say so. The closest thing we have right now to 4G standard speeds is LTE (and even LTE technically falls short of the speeds that are supposed to be reached), which is why HSPA+ has long been displayed as H+ in CM. 4G is used for LTE on the basis that there's nothing else in common use nowadays that can be considered 4G in any sense.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
Well if we want to get technical around here, current LTE is not TRUE 4g either.... haha but let's just go with what the companies tell us! On stock "4G" denotes anything higher than 3G UMTS.. thusly, H, H+, AND LTE are all "4G" BUT really only LTE can be somewhat considered it.. And that's really only 3.75G... LTE Advanced which will be out in a year or so is real 4G and can do over 100 mbps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xetrev:
I just switched to the AOSP rom.

Bluetooth works perfect with the 1/1 kernel..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blackroseMD1:
I have no idea what's going on. The issues I was having yesterday (incoming calls freezing the phone on answering, media storage locking up the phone when choosing a ringtone) seem to be gone. Everything seems to be working well, except none of my notification/ringtones work. I have audio, as playing music works and so do touch sounds, but not notification sounds or ringtones. Weird.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smelenchuk:
Did your ringtone/notification volumes somehow get turned down (check in Settings -> Sound -> Volumes)?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blackroseMD1:
Nope. If I change them from that panel, I hear the sounds ok. I just don't get any sound when notifications/calls come in. This is on a clean install. Gonna download an earlier build (looks like 12/27 is the earliest I can get from get.cm) and try dirty flashing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
Just did a full wipe and flashed 1/1 nightly 12/12 gapps and 1/1 ktoonsez kernel. In call audio is still horribly low. I tried enabled boosting the gain for in call volume in Settings->Advanced as well. No luck.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kinghorsey:
Sound is good here. Google music works perfectly so I haven't touched third party kernels.

Best build yet!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
Are you including call volume in that statement as well?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MethodX:
I have the stock ROM kernel and have tried the KT kernel 1/1 and in call volume is loud and clear. Never tried over Bluetooth though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xaznxplaya:
Bah I don't get this using speed test to compare my 3g and Wi-Fi, 3g barely reach 6k and Wi-Fi like.5.1k, there's something wrong

PoWeReD By that SeXy s3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] huladaddy:
Does anyone have a call recorder working with this ROM? I was using Evercall (FrienzPlay), but it stopped working with 4.2.1.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] erbsmokah:
That seems normal to me. Unless you have a really good wireless router your speeds aren't going to be spectacular over wifi
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ExcelonGT:
I live in a HSPA(+) area and work in a LTE "4g" area and have not been able to get on HSPA or HSPA+ at all with these last few night lies. If I'm not I. LTE (which works ok) then I'm only on 3g. Not seeing H or H+ at all.

Anyone else notice the same?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smelenchuk:
Have you tried doing something data-intensive while in a "3G" area? For a lot of people, this causes it to "ramp up" to H/H+, and ramp back down when it's no longer in use. (This is apparently a 4.2 power-saving measure. Or something.)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chrisj22:
According to att HSPA+ or H+ is 4G. 4G and 4G LTE are 2 totally different things. Even on stock when the 4G symbol is on it shows mobile network type as HSPA+. Unless I've read there info wrong.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smelenchuk:
There's the problem right there :p. It's all marketing on their part. Did you see the other posts on the subject?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chrisj22:
I saw that just figured being my phone shows the 4G symbol and network mode as HSPA+ I figured it wasn't lying.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 02busa:
Yep purely AT&T marketing.. They had one of the provisions in iOS for the iGarbage 4S changed to where the signal icon for HSPA+ was set to show "4G". Can't remember exactly what iOS build it started on, but either way it has become nothing more than a bad joke on their part.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Electroz:
I had this same issue with a Canadian model. I updated to the latest modem/baseband and it fixed the issue.

Sent from my Bell I747M Galaxy S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 02busa:
New 1-2-13 build is up...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
Here
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amzi:
hows the build going guys?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MoeisHere:
not much change between nightlies
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Pretty happy with the ROM since 2912 nightly.. Its rock solid with only few noticeable bugs like low call volume.. Give it a try,,,
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Emil9727:
So I moved away from CM and 10.1 because of two major issues.

Low volume and bad GPS.

Have either of these been fixed in recent builds? Once they are its golden :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MoeisHere:
gps is good. still low volume. which rom are u using that doesnt have volume problem?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] huladaddy:
What ever happened to the ability to long-tap on the homescreen and bring up a menu of things that can be added to the homescreen, such as an app, a widget, an action, a wallpaper, etc. I liked that a lot. Will we be seeing that again?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
I just experienced the first random reboot with stock kernel. Anybody experienced it as well?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dLo GSR:
that is launcher specific
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] huladaddy:
Mmm, I don't think so. It was in an earlier 10.1 nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adammur:
On the latest build with ktoon latest kernel and have had two random shut Downs already while just playing music from double twist.

When I attempted to turn it back on, a battery symbol filling up was displayed instead. It would only power on after a battery pull.

Sent from the future in a tie-fighter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
I think they removed some stuff. I saw it there too about a week or 2 ago before they fixed the data problem. I haven't seen it since they fixed the data.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ExcelonGT:
Yes..happens to me about once a day, sinceI made the jump to CM10.1 on 12/26/ I've been on the 12/26, 12/29 and 12/30 nightlies.

Always using the stock kernel

---------- Post added at 08:37 AM ---------- Previous post was at 08:34 AM ----------

Yes. I've run the speedtest app a few times and even tried surfing content heavy webpages (ie NYtimes.com). never do I see the jump from 3g to H+. The switching from 3g to H+ and back to 3G under activity was present in CM10 nightlies. I have yet to see H or H+ with any of the CM10.1 nightlies I've been on (12/26, 12/29 and 12/30).

some have reported flashing a new modem/baseband will help. However, I'm not sure how to find the exact baseband i need.

I live in the NY/NJ metro area and am on AT&T.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] peneoark:
Um, mine shows 4G signal and network type is showing LTE:13
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pberge:
I'm also in NY on AT&T and my phone sits on 3g until I start using data and then immediately switches to H or H+. This behavior has been the same on the 10.1 nightlies that I tried (12/26 and 1/1) with both the stock and KT kernels. I'm currently testing out a different CM10.1 based ROM and it is also behaving in the same way.

Are you using the latest modem?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] imstill@g:
Just to chime in, you guys are making the changes to your APN, correct? Default seems to be the WAP protocol by default.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] benjihana:
My default APN is AT&T PTA

---------- Post added at 09:42 AM ---------- Previous post was at 09:40 AM ----------

I saw a few posts earlier in the thread, but nothing conclusive - is anyone having trouble getting AT&T Visual Voicemail to get past the password screen? Mine just times out. Apologize if it's been answered, but I can't find anything.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dlove27:
I have had this issue for awhile now as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
It works for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MoeisHere:
it seems it doesn't work with cm10.1 ive tried it on different phones with this rom and i got it running but after 1 voicemail it crashed. So now i just use google voice just for voicemail and its much better. I can actually play the voicemail from the dialer. i used the instructions http://xdaforums.com/showthread.php?t=1882181
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mharmon:
It's working fine for me, at least for now.

After I "clean" flashed from CM10 to CM10.1 (12/29/2012 build), I allowed all the apps to reinstall and then I restored the data for Visual Voicemail and the other apps using Titanium Backup. At that point, Visual Voicemail would not go past the password prompt. I gave up on the issue until after I dirty flashed to 1/1/2013 CM10.1. After I flashed that CM10.1, I did another restore of the data with TB and Visual Voicemail works for me now. Seems to work correctly.

I'm using the UCDLK3 modem, which I flashed before 10.1. Stock kernel.

Now I'm trying to get Light Flow and Terminal Emulator working. Light Flow doesn't seem to work, but doesn't display an error. Terminal Emulator just says "Unfortunately, Terminal Emulator has stopped." I'm not really worried about either one, but I wouldn't mind them working again at some point to satisfy my own OCD.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] twostep665:
how is everyone's battery life? I had been trucking a long nicely with battery life but after taking off charger around 8 hours ago before bed, i wake up a few minutes ago and the phone is at 13% with a huge chunk of it listed as cell standby. im on the 12/31 build with the 12/21 Ktoonz kernel. Gonna go to the latest build to see if that fixes things.