yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
As task said, we WILL be both supporting the S3 since task and I will still own it and my wife just got her's a few months and task's fiance will inherit his S3 so this will NOT be going anywere :D :good: :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Toonz GPS fix worked great got me to the top of a mountain and back
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
EXCELLENT!!!!!!!!!!!!!!!!!! Glad to hear it and thanks for the update :good: :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Those links are bad...I'm going to use the ones under your names :)

And here you go:

2F701310FR5999053

3XK48009V2263000N

And thank you both!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Fixed the links. I'll just post this here. ;)

@ Everyone

This only applies to whoever might be moving over to the SGS4 or who have already moved to that device. I did this when me & Ktoonsez were on the SGS2 and wanted to get him the SGS3 so he could stay with me in terms of devices. We had great success. If any would like to help Ktoonsez get the SGS4 and want to donate to the cause we are accepting any help. You know ktoonsez's donation link HERE . I already have the SGS4 and might not be keeping it due to not being able to justify the expense for the device. So if you'd like to help me justify keeping mine the you can donate to me HERE. I already have AOKP builds for it, we just need the bootloader to get unlocked and within minutes my AOKP builds will be posted for it. Let me or Ktoonsez know if you would like to help. It's your choice. We are not beggars. Just seeing who would like to pitch in. Thanks. :D

P.S- We will still be supporting this device. If you notice. I'm still supporting the SGS2 and I hate that device with a passion. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thanks buddy, you are huge and vainey!!!!!!!!!!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Ewwww!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] i5lee8bit:
9UJ974614K832215E

2U4396349S046562H

I don't even have an s4 or plan on getting one (got my s3 refurbed from att in dec for $40) but thanks for all ur work.

I know its not much but task u might remember how I do this, u can prob tell by the odd amounts but its the end of gift card balances. No better way to shave the end of the balances to u guys. besides its my only way of doing it and im still trying to get my life back together.

I wish ppl could see it this way but if every user of either tasks roms or ktoonz kernel donated a buck, theyd have thousands.

Sorry i couldnt give more but as u know ill always be sending some here and there. Thanks again!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
That's what she said.

Wait a minute... that's what who said??? :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Hey KT

Had a reboot while using GPS with you're new GPS specific settings. Anything good in lastkms?

http://db.tt/LcAAS6vu
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Still not getting a lock on GPS for some reason.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Over 4 hours, and I STILL can't figure out how to respond to that one.

Either "umm, thanks?" OR

"You forgot throbbing"

:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thejust:
Backup Rom

Install a Rom with working gps

Get a lock (with maps)

Reboot to recovery (right from maps)

Restore your backup

Worked for me!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Same stupid one, nothing to do with the new code:

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

:(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xBeerdroiDx:
Hey KT, where can I locate your recent previous releases? Specifically 4/19. I checked on dev-host. Sorry if I've missed something. Thanks and cheers, buddy
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
THE MAN
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ls3c6:
What does faux sound update mean?

Headphone output boosted in kernel already or need app still? How to configure?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Google search is wonderful. Adding XDA as a search term is helpful. Even searching this thread would have been good.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] j_r17ca:
I have a situation here guys. I dont know if this have been ask before but here it is. Ive been noticing that phone gets hot whenever i play candy crush or any kind of game. It will start from 26° and goes up to 40°. Im using the latest kernel and rom. Im uv'd by 75. Using ktoonservative and zen with the OP's settings w/ ktweaker.

Is there any other setting that i need to change?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] galaxys3man30:
Is those temps cpu or battery

President of {Team Kernelizers}

Im Gman and I approve this message
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] j_r17ca:
Im not sure. Its the one showing at the ktweaker. I guesz its cpu
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] galaxys3man30:
Ok that's ur cpu temp buddy 40c that's ok that's normal for playing games of any kind as they cause a load on the cpu my runs at 45c if ur at 40c ur good buddy nothing to worry about

President of {Team Kernelizers}

Im Gman and I approve this message
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] j_r17ca:
Ok. Thanks. Wheeeewwww. Relief. Lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] galaxys3man30:
Yw buddy anytime

President of {Team Kernelizers}

Im Gman and I approve this message
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lookitfast:
Heres something for the S4 Toonz!:angel:

58P43459UV016591H
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thanks man, you are awesome! :good: :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ls3c6:
I did before I posted and I'm qware of the program, so please explain.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Toonz do you mind checking out my BBS? I never get more then 2.5 hours screen on time on a 3.4 kernel with the exact same settings and apps vs 3.0 where I got 4.5-5 hours same conditions same locations etc
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
I don't think you did. This is just from this thread: http://xdaforums.com/search.php?searchid=173119941

;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Im not the best at BBS but post up the screen shots and hopefully we can see whats going on.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
I'll just add that I was getting an idle drain of about 1-1.5%/hr on 3.0 and now I'm getting about 3.5-4%/hr on 3.4 with nothing else changing. BBS reports about the same activity as it did before, so it appears that it's using a lot more power to do the same amount of work for some reason.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
---------- Post added at 12:49 PM ---------- Previous post was at 12:48 PM ----------

Yea I noticed that too mine is 6-8% drain at idle
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Looks like you have wake locks.. Especially if you aren't using maps. Make sure all location reporting/updating/whatever is off
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
As far as the kernel goes, looks like there is only 1 that is causing you some drain and that the MSM usual screwage: "bam_dmux". I doubt that that is the one bringing you down but it might be, I know there is some posts out there to try to get rid of that damn thing, I know it was something like Airplane mode, reboot, fix permissions and some other stuff. Very weird.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Thanks man
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jowilk:
Hi, fauxsound now has settings for poweramp headphone volume. If you use poweramp as your main player, you will like it. The only gripe I have is the huge step from -1 to 0. Hope it could be resolved.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Hey toonz any chance of getting a kernel update with all the commits from cm in the last 2 days?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] frosty5689:
What is your sample_rate_screenoff set at? After I fixed my media server/provider draining issue I benchmarked the idle drain using 70000 and 90000. With 70000 I lose about 2-3%/hr but with 90000 I lose 6-7%/hr. I know it is really weird compared to 3.0 where 90000 would basically drop the drain down to like 1-2%/hr instead of increasing it dramatically...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
Very interesting. Mine's at 90000, so that may be part of the problem. I'll bump back to 45000 and step it up from there. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Never ask for an ETA.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
If you wanna report back I'll try 180k on screen off sampling and we can compare results. Are you using ktoonservative?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ls3c6:
Search ID states no matches, either way the analog headphone output is too quiet, how can this be resolved? Poweramp with eq tweaking is a mild bandaid, still not much preamp.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Sometimes when you over-do something on these kernels it has a negative effect. Like under volting or clocking too much actually using more battery because of system instability. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] frosty5689:
Interesting... I would look into getting rid of the wakelock ktoon mentioned the. Or try setting sample_rate_screenoff higher to see if it actually lowers your drain when idle.

Yep, I experienced this with my Galaxy Nexus and the S3. Seems to be related to ECC memory causing extra drain due to constant need to correct itself. Wish theres a way to see error correction rates to find true undervolt without profiling each uv
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
For the lower MHz, I find the point of failure and add 50mV and go from there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Hey toons, just got back from that road trip I mentioned earlier and not a reboot to be had while using navigation. 2.5 hours there, 3.5 back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Excellent, so glad to hear that.

Someone asked earlier about a release today, I will try, just spending all the time I can with the wife, going on a 2 week road trip for work and gonna miss her birthday, but I will try tonight.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] frosty5689:
How would you find which frequency step is causing it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] galaxys3man30:
Do one at a time buddy that's only way I know

President of {Team Kernelizers}

Im Gman and I approve this message
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Yup... one at a time. Like I said, I only do it with the lower most frequencies and go from there on up to 1512MHz at 1150mV.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
OP Updated

Change Log 5.5.2013

1. JB_2.5.04.02.02.040.288 from codeaurora.org

2. Couple of USB patches

3. Couple of display driver updates

4. Totally sync'd with CM

5. Do NOT flash this if you are allergic to AWESOME

I WILL BE TRAVELING FOR NEXT 2 WEEKS FOR WORK AND WONT BE ABLE TO BE VERY ACTIVE DURING THE DAY.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xBeerdroiDx:
thanks! gold medal kernel. enjoy yourself. cheers! :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] statickiwi:
What a speedy update. Very impressed!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Thanks for the update... Running great!

Where you headed this time around?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] galaxys3man30:
Need some fellow att people to help test a ported rom any help is greatly appreciated

http://xdaforums.com/showthread.php?p=41096574

President of {Team Kernelizers}

Im Gman and I approve this message
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] frosty5689:
In other words.. Uv one step use for a day or two... No adverse effect then move on...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
I was getting similar results. I tried bumping my screen_off_sampling_rate to 180k and my idle drain was less than 2%. Screenshot below was with 30min screen time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Weird 5 reboots this morning while at idle screen off.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Anybody else's battery life get ridiculously terrible after this last update?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
Should probably get BetterBatteryStats to find what's draining your battery.

P.S.: Should also update your sig ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
You need to do some homework before posting (play around with settings, determine if its a rogue app/process). As its been saying 10 million times before all devices are not created equal and there are countless variables that could be causing your battery drain.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
Like the previous poster said, BetterBatteryStats should help you to find the problem...

I had an unsual battery drain when updating to a newer kernel a few days ago...

But with BetterBatteryStats, I saw that there was a weird AudioOut_2 wakelock keeping the device awake nearly all the time even if nothing was outputting any audio.

I found out that Bejewelled Blitz was causing this trouble (I installed it at the same time with the newer kernel)... as soon as I opened this app, the AudioOut_2 wakelock was appearing. The only thing that could fix the problem was a reboot. I tried different app with sound... and only Bejeweled Blitz "activated" this wakelock.

I don't know if it's a problem with the rom, kernel or something else... I will try to test it out with an other rom/kernel to see if I have the same problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
That one was different. Some kind of sdcard error in that one. I think your phone is allergic to awesome!!!!!! Nooooooooooo!!!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goobs408:
Anyone getting "Cannot connect to camera " when using this kernel? I clean flashed both tasks newest nd ktoonz newest. When I did that, camera didn't connect. So I reflashed the ROM and it was fine leading me to believe its the kernel. Unfortunately I did not get a log.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Hey toons

65V415662E4447022
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thanks man. Very, very cool!!!!!!!!!!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Has nothing to do with kernel. Check the ROM thread. if you read posts, you'll see there are a number of reports all over.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goobs408:
I did. There are mixed reviews everywhere. I mean if it were to be a ROM problem, why would the camera work if I didn't flash this kernel atop the ROM? Yet, when I flash the kernel, it doesn't work? I always had luck with ktoonz too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
That is probably not true statement. Try to clean flash ROM by itself with stock kernel, go into camera and try to change settings/ white balance. or for that matter a few other settings.

it'll give you same results.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
It's ROM related.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Camera is working just fine and everybody knows I am ALWAYS on AOKP. U need to hunt down the problem. Its probably a camera pic on your SD or u need a super wipe.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goobs408:
Explain.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
nobody needs to explain anything about a camera not working in a KERNEL DEVELOPMENT THREAD. Take it elsewhere man. the kernel is not borking your camera.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
It's something to do with commits and patches trying other kernels etc won't fix it just be patient the cm team will eventually fix it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goobs408:
Oh but it is.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
Great sounds like you figured it out. Fix the code and put in a pull request on github.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goobs408:
Nope. I flashed the ROM(full wipe), camera works. Flash kernel, freezes and fc on gallery. Wipe data and force stop gallery then reboot>recovery to fix permissions. Still does the same thing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Great you found the problem. So we will wait for you to share the code you will write to fix it then. What's you're ETA on that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goobs408:
http://db.tt/ceMwQR1P log.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
:D

---------- Post added at 12:01 PM ---------- Previous post was at 11:59 AM ----------

Hey task

7DN812890N421831Y
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
That's awesome! so now what? You confirmed that this issue is from the ROM by sending a catlog and not KMSG

are you almost done with the fix? ETA on that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
There's a $20 penalty you have to pay to Ktoonz for posting ROM related issues in kernel threads. And you have to pay the same to Task for not reading his thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goobs408:
Good one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
i like this guy a lot :cowboy:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goobs408:
Like I know the difference. I was told to use catalog so I did
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
if u dont know the difference then dont post in a development forum
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
1.) A last_msg would be necessary if a reboot occurred because of the error.

2.) A logcat would be necessary for am error like this.

3.) That's not a kernel issue. Its a ROM issue and has been reported multiple times in my thread, cm thread, and almost all the other threads that track the cm camera/gallery2 repos.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Thanks man. :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dlbjmb35:
I've gotten the camera error since who knows when.Here is the log cat..

https://docs.google.com/file/d/0BwSr5x8ZqYgrQjM0YUF0SUdacjQ/edit?usp=sharing
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ziizy:
Okay so here's my ordeal. I flashed 5/3 touchwiz on to a 4.1.2 att rom. I went about 8 hours with no issues what so ever. A little later I changed the under clock to 81 mhz to see what my phones response would be. It was fine for awhile then i saw that it had shut down and not rebooted. I then tried to hold the power button so it would reboot, nothing. Then I tried a battery pull, it would flash the ktoonez boot animation then shut down and only respond on a battery pull. Now if I try anything, recovery, download or just powering on, it flashes that screen for a moment then is unresponsive. Is that considered bricked, or can I do something to fix it....Thank you...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
Charge that bad boy. Sounds like u got a dead batt
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ziizy:
Two different batteries, same response :/. Plus the one that I tried first is extended and had at least 75 % left within the hour that I had checked it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
When u attempt recovery, do u get the Samsung splash with blue text in the top left? U shouldn't get the kt image if its a recovery boot
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ziizy:
When trying to reboot to recovery it flashes the blue text then when it goes black, it stays black and is unresponsive until a do a battery pull. When I put it back in, it automatically starts the boot process without me pressing any buttons, this leads it to go to the ktoonez bootanimation and then the screen going black and becoming unresponsive...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
Do your soft buttons stay lit while the screen is black? Maybe u could try attaching it to a computer and adb if that was the case. Is it warm like it's running after it goes black?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ziizy:
Nope completely dead, as if it was powered off, it is also cool. Also it is NOT rebooting, it is just shutting off.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
You should probably post this in the ROM thread of the ROM you are using to get better support for it. it doesn't have anything to do with this kernel. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
Plugged in?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ziizy:
Yes sir, as we speak, no charging animation, just a black screen, multiple outlets, different cables, same results.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
Sorry to hear that man :/ I don't know where to go from here, does your computer detect it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ziizy:
Prelimanary results say no....I need to search how to use adb to see if I can maybe get it to recognize it...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
Pm me if you'd like
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xhead:
Ah thanks OP :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kobos311:
Thanks for that! Glad to know that, as I know many are so fearful of bricking this caliber of device its ridiculous. lol The local ATT Store sold out a DOUBLE shipment including preorders/extras, all gone by 2PM yesterday. thank god for best buy benefits :P
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Franky_V:
Good to know about ktoon and task. I have no clue who the quality devs are here. I had quite a few I followed on vzw but they're either still there or on T-Mobile. :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Franky_V:
Has anyone else had problems with tapatalk? I'm on rooted stock and my tapatalk has clunky scrolling and occasionally force closes. I thought this kernel might help it, but it might have even got worse o_0
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
OP Updated:

Download CWM flashable zip kernel

http://www.mediafire.com/?vbqv2254e8y10yb

Change Log

•Made ondemand and noop defaults

•Some tweaks to ondemand for smoothing

•New Governors (PEGASUSQ, ADAPTIVE, SMARTASS2, LULZACTIVE)

•New Schedulers (CFQ, BFQ, VR)

•ADB remount support
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Post #2 updated:

I will keep the change logs in Post #2.

NOTE: I would not use LULZACTIVE right now for some reason it just pegs and stays on 1500mhz.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jiggytom:
Which governer/scheduler would you recommended for daily use? Mix of performance and battery savings?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] danny6514:
Hey ktoonsez...would it be possible for you to change "AT&T Only" to something like "AT&T, Telus, Bell, Rogers" or "I747M", etc since it has been confirmed to work on them. It would probably cause a lot less confusion. :) thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
All 4 are confirmed? If so I will:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Nice. Love pegasus. Glad to see it here already.

Btw can you look into the sd card problem I encountered? Right now I'm trying to recover all the photos videos and music files. Got an hour left before it's done. Hopefully it works.

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] danny6514:
Rogers, Bell, Telus, SaskTel are all I747MVLALE8