yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] selw0nk:
I am not experiencing any reboots on the latest update.My kernel settings are Governor: smartmax and I/O scheduler: fiops. Even if I use bfq I have no problems. Also, I am not overclocking or undervolting anything and leave everything as default.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tiernan22:
Zen, Intelliactive, 486 max
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amf66:
Security>Lockscreen rotation>Portrait only
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RonG21:
That did it, thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amf66:
I figured I would try it a while back and it worked. Sometimes it's right there before you. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sandman97289:
Bluetooth disconnects

I posted this before but didn't get a response. Sorry if this has already come up before.

My bluetooth keeps disconnecting from my car's audio every 10-15 minutes. This didn't used to happen in the previous Quantum 3 releases. I'm currently on Quantum 4.1 and the 4/28.2 kernal. Anything I can do/try?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] UnXKnown0:


Download trickster mod from the play store, open it, slide to the left twice. You'll see the scheduler setting. Set to row press the check mark on the top right then hit the menu button or press the top right settings button. Make sure set on boot is checked. All set.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarKnight6969:
I am not having any reboots myself. On q4.1 and qk 4/30. My trickster settings are as follows:

TCP=bic or Westwood

Read ahead=256/512

Min MHz=384

Max MHz=1242/1512

Max screen off=1026

CPU gov=intellidemand

GPU gov=simple

Gpu max MHz= 200/300
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] asifbacchus:
I know you fixed the problem, but I also found that a 10-15s delay and a 1 min grace period helps the settings 'stick' with Trickster. Also, sets the read-ahead properly. Can't take credit for this idea, someone mentioned it earlier I think or on another thread I was reading. Cheers :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caulton:
So my phone has been doing some random reboots and I would like to make a log but don't know how I've searched and couldn't really find anything can someone help :sly::D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MikeWjF:
Thanks for the responses everyone. I switched from intelliactive over to smartmax and it's been pretty smooth so far.

-"No officer I wasn't texting, I was flashing a ROM."
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
Doesn't work. Got a reboot while typing using your configuration.

---------- Post added at 05:46 AM ---------- Previous post was at 05:45 AM ----------

Its been discussed few pages back... Lame searching skills I guess?

Anyways use syslog from playstore.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MikeWjF:
Yeah just got a random full reboot, and then a soft reboot while trying to grab the kmsg file. Frustrating because the kernel and ROM run flawlessly otherwise.

-"No officer I wasn't texting, I was flashing a ROM."
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] selw0nk:
Use SysLog https://play.google.com/store/apps/details?id=com.tortel.syslog
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DMF1977:
I've been running this ROM a few days now with 4/28 kernel, scheduler on tripndroid, governor on intelliactive, and screen off max set to 384, and haven't had one reboot or any issues...:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] UnXKnown0:
Love that sig :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MikeWjF:
What's the deal with all of the force closes when you try to use another kernel after this one?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
Wipe dalvik, fix permissions, wipe init.d
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ps3kev:
hey pwn were you able to use samsung source to build off of for the kernel or no?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
Try wiping cache and dalvik? I've never had that happen though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] UnknownTroll1:
Good Guy Pwn!! Looks out for all his followers even when switching bases.

Sent from Mission Control
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KorGuy123:
New kernels could be out dated after all the optimizations own had added
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Synthetic.Nightmare:
Do you still need blobs of any sort? I've pulled the system.img from the release and have it mounted on my machine. I'm gonna start picking it apart later tonight and will gladly help with that... if still needed; knowing how fast you cm guys can work :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DanKNugs:
How do you get your Trickster Mod settings to stick? When I reboot my phone, I find I have to reapply my settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Press settings then check kernel settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] selw0nk:
I finally got a hard reboot while streaming a video.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
You seem relieved... :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stew1411:
Not sure what is causing all the reboots. 4 times in 1 day. Twice while listening to music with screen off, happened around 2 minutes after music started playing. Once while watching Netflix. And once for no reason at all. Is it the kernel causing these? If so, would flashing a different kernel fix these problems?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VR32:
experiment and see for yourself. all the settings and configs in this thread.... I've tried all of them, every config, different gpu clocks, govs, etc etc. I'm now down to the most conservative config yet. more reboots now than before. and i don't push my phone much. so whatever is working for some is not for others. so, try and see, just don't forget your nandroids.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Subsonic44:
I know Pwn is working on a new release and I'm confident he will get it all sorted, but for now I'm using the following Quantum 4.1 hybrid and it is working rock steady for me.

http://xdaforums.com/showpost.php?p=52227549&postcount=768
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
thank you finding and posting this. like all others been trying to find the right combo. even went back to Q3.5 just for smoothness (well, and of course the bunnies). will try this a.m.

thank you again

err on the side of kindness
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Subsonic44:
No problem. Hope it works for you. I've been running it for a couple of days now and it's been flawless!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MikeWjF:
I ended up going back to Slim with leankernel after my own boneheaded woes in recovery while deleting old nandroids. I'll be checking out pwn's next release.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
nope. no go. downloaded. full wipe. 'fail' message after trying to flash. Redownloaded (just in case) wipe system,dalvik, cache , system , even wiped my ass just to be sure. lol. another 'fail' message when trying to flash.

oh well. a good try and thanks again.

maybe will try ONE more at work tonite.

back to Q3.5 and those crazy bunnies!!!

err on the side of kindness
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Peterbluez:
I'm having the exact same issue. Q4.1 4/30 kernel. Its only with media, though - the phone is fine. haven't really tinkered with it too much, but it wasn't a problem at all prior to 4.1.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Subsonic44:
Sounds like maybe an asset failure. What bootloader are you on?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
MJ2 and using latest TWRP. 2.7 i think (?)

err on the side of kindness
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Subsonic44:
Same as me. I'm not sure what the problem is.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ps3kev:
You need MJB
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Subsonic44:
If he flashes MJB, he can never go back to any rom that would need an older bootloader. MJ2 is very similar to MJB, but is reversible. I had no problem flashing Quantum 4.1 on my MJ2 bootloader. I'm not sure what is hanging up his install.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
as i understand it (which is maybe totally wrong) the MJ2 is the leaked version of MJB. (if not, then i've done a helluva lot of flashing on the wrong one).:)

err on the side of kindness
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MrBrady:
Went on a 9 hour road trip yesterday with Quantum 4.1 and initially kernel 4/30, all the time using my iBolt Car Dock, Google Maps and Pandora streaming to a Bluetooth speaker.

Was getting massive amounts of random reboots and even reboots followed by hot boots.

It seemed like the reboots were much more frequent when using both Nav and Pandora versus Nav and Playerpro.

Tried different Quantum kernels too and it didn't seem to help the issue.

I only seem to get random reboots when I'm away from home for some reason. Could it be from switching towers or something?

VZW SGSIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Matrioux:
I've only had one random reboot, it was while making a phone call while driving, so it could have been a tower switch
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amf66:
That's very strange.. I had lots of reboots and had to switch back to Slimkat 4.8. It's not as smooth as Quantum, but it's about the same and good enough until the next Quantum release. :) Was able to just dirty flash over Quantum 4.1 without any problems.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Can't be, I've had two random reboots while not moving anywhere.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DMF1977:
My phone ran fine the first few days, then out of nowhere starting getting a lot of random reboots! No matter what kernel settings were... Had to flash a different ROM.:confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jeff1981:
I'm a die hard quantum user but recently I've been getting all the reboots everyone is talking about and using the phone for work. So until the King (pwn) can get it sorted out I had to resort to another Rom c-rom 4.4.2 has tons of options and haven't had a single reboot since and its been about 4 days. Please fix it up so I can get back to quantum.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Sorry guys I'll pick up tomorrow. Is not the rom, it's the kernel that causes problems. I've been getting the reboots as well. I've honestly been thinking about holding off on fixing the kernel until the 4.4 source is complete. We'll see! I'll look closer once my Windows reinstall is done :s
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] androidman23:
reboots a lot with allcast

tried allcast again for the first time since it was released and I get reboots almost every time I touch the screen(while casting something). reboots are getting bad, but I'm sticking with it. hope you get time to fix the kernel pwn!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amf66:
You don't have to suffer... just flash another kernel until the issue gets resolved.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
MJ2 bootloader IS the leaked MJB without Knox, meaning you can downgrade to any version of Android you wish should the need or desire arise, whereas unlike with MJB, you can downgrade to Android 4.3 at most.

+1

I'm on Validus13's ROM with QK 4/30. No reboots. Waiting for Pwn to fix whats broken.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Subsonic44:
I went the other way; Quantum 4.1 with DKP kernel. I just couldn't handle the clowns! :silly:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tallsilver:
Works for me too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
Got no wakeup alarm this morning! Discovered no sound from any alarm or ringtone. Rebooted. Still no alarms out ringtone sound. Shutdown, pulled battery, and restarted. Phone rebooted as I tried to get an alarm sound. Did not successfully restart, black screen, non responsive to any buttons. Pulled battery, rebooted. Got sound from alarms and ringtones now.

Now I think this may be just a little too close to the bleeding edge for a daily driver. I'm going to have to do something different. Maybe give DKP a try.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
I still get reboots sometimes with he dkp kernel...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Yeah? I switched from Quantum Kernel to dkp after tiring of the frequent reboots, and I haven't had any issues at all. I've been using it for about five days now without any problems.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
Maybe it didn't flash correctly... Cause I still get the "gimme pwncakes" splash screen when booting up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Yeah, sounds like you're still on Quantum Kernel. Check your kernel version under About Phone and try flashing DKP again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
It says dkp under settings/about. I'll reflash the kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tallsilver:
No bother, he forgot to put his splash screen in the latest version...........but you got his kernel! :laugh:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
If everyone is using the other Quantum with DKP built in, bring all your issues somewhere else than here.

The issue with reboots is the kernel, not the ROM. Any bugs and whatnot can be attributed to a million different things, don't try to pinpoint it on one thing or the other because you really aren't going to be able to tell. Get ready to have the same basic bugs across the spectrum ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CCivale:
Just wanted to share my observations over the past month that I've been using this rom and kernel. I have a d2vzw and I'm currently running Quantum 4.1 and QK 4/28.2. I started following this thread because there was a lot more discussion here than in the Verizon thread.

From my personal experience, I think I've had maybe 2 random reboots over the past month. Now I never mentioned them because they were that infrequent. What I really wanted to share was this. I hardly ever use the FFC, if ever, and I never use Bluetooth to steam audio to my car.

Again, this is just what I noticed that I was doing apart from others in this thread. And I really don't know how a kernel may or may not interact with the camera or Bluetooth, but I just figured I'd share the info I could give.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MikeWjF:
I never use either of those either, still had the reboots.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CCivale:
And is your phone a Verizon S3 as well?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MikeWjF:
I'm on Sprint actually.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Najuto9tail:
Go back to 27.4 kernel no reboots at all on my phone
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
I was getting some reboots as well. I apologize for pimping out other kernels, and I mean no disrespect. But I've found heaven combining Quantum 4.1 with K747. Sick battery life and no reboots. Smooth as hell.

Sent from a warranty crushed i747 running Quantum. F**k Knox. That is all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
4 /30 Kernel for you lazy asses http://d-h.st/mRb
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bsballkingben99:
Is it fine to flash this ROM over cm 11?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
+1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jmppe3:
FWIW, 4/26-B is the latest kernel where I haven't noticed any problems. On later ones I've had in-call reboots or outgoing calls won't dial - just an instant 'call ended'. Using zen/intelliactive/simple@400
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rofflayo:
I've gotten this problem since we moved to 4.4. It's weird, but every time I anticipate needing sound (eg, setting an alarm), I double check that I have it and if not: I plug in headphones, hit the volume rocker until I hear the beeping, then disconnect the headphones and double check I still have sound.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] csingh:
I was wondering this too, does anyone have an answer?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
The answer is no.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] csingh:
Alright, thanks. I was actually wondering this because I was having an issue with the previous app not showing up in recents, and it only shows up if i open the recents menu twice. Has anyone else had this issue?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
I had that issue as well with it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bsballkingben99:
Wow. I just installed the same setup you described and you're right, its amazing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheSchatz:
I guess I'm one of the few who like the slim recent app list!

One small request if it seems feasible though, is it possible to add a way to control what side it slides in on? I prefer the style of slim, but being left dominant makes it a bit harder to use with one hand.

Also, having had reboots like a lot of us, I can now say latest quantum with dkp kernel is flawless!

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amf66:
Go to "accessibility" and scroll to the bottom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] androidman23:
could you please post the link to the kernel your using?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 4b3ck:
He is probably talking about this
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pilothaz:
Really isn't that hard to find, it is out of this forum topic and find the K747...

http://xdaforums.com/showthread.php?t=1756776
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] androidman23:
Sorry bout that, i saw a Verizon one and I just wanted to make sue I was flashing the right kernel. Also what governer and i/o scheduler are you using?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheSchatz:
THANK YOU, it makes perfect sense, but I never would have thought to look there!

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pilothaz:
Hey Pwn, think you will add in Peek? The git is up for it now.

https://github.com/lzanita09/NotificationPeekPort/releases

reference is from here: http://www.reddit.com/r/Android/comments/24unay/paranoid_androids_peek_has_been_ported_to_an_apk/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] akaTRAP:
This idle battery life insane on 4/28.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
no disrespect meant also. just trying for a stable Quantum. still best ROM that i've used.

thank you for post. trying out now.

err on the side of kindness
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Lmfao, we talked about KT's kernel a lot in this thread and I used to be a huge advocate of it right in front of Pwn's face. He don't take it personally!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ps3kev:
Little update pwn? How's it going
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Changelog? I want to update but, I don't like the new power widget/toggles that got added on the 1.17 release.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cdjaney:
Been digging in menus....2 things. Is there a "hold to kill" button? Don't see it. And, it's there a way to see RAM usage built in? Or still working on both of these? :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oriveradel:
Installed 1.18 very good impression to start everything working good! Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dotnetguyaz:
"Hold to kill"... stop that. It's as bad as using a task killer. You're doing more harm than good. Just FYI. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] joshuagalipeau:
why is it bad?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
Lol... Dotnet and I already went thru this.

I asked the same question, and he had a pretty awesome explanation. Can't remember what page it was, maybe he'll know.

I don't use ''hold back to kill'' anymore. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dotnetguyaz:
This is what I posted before:

I apologize in advance for the rambling... But you asked. LOL

Lots of things. First, you are basically defeating memory management as Android learns how to prioritize apps based upon your usage (granted, for us flashers, it's not so grand because we always wipe out the stats). When you "kill" an app, you are telling Android that you want to control memory usage. Additionally, when you switch away from an app, it's placed into a suspended state. For the most part, it shuts down (unless it is listening for intents or push notifications) so that it uses no CPU and/or battery. It is basically cached and just sitting there waiting for you to come back to it. When you send a SIG-HUP, you are telling it to be closed and removed from cache. So, when you go back to that app, you have to relaunch it all over again. Now, some apps aren't written as well as others and don't cache very well OR don't handle the finalization signals very well. Those apps silently crash in the background. It's well known in the developer community that it costs MORE resources to throw an exception (because you actually create an object to contain the exception) than to simply handle the error condition properly. You can take a look at a lot of this by simply pulling a logcat and see how many apps throw swallowed up exceptions upon being forced to shut down rather than having the OS do it gracefully.

Secondly, Android, being Linux, operates BETTER with more ram being used rather than less. It's an operating system that was built and designed from the ground up to operate on swap and caches. This isn't Windows.

Lastly, there is a reason why the "back to kill" is in the Developer Options. It's there so that as we are writing apps, we can kill them if we need to and a reason why Android "out of the box" now hides the Developer Options.

The bottom line is that when you force close apps to reclaim ram, you are actually causing Android to work harder because it has to recache what it already had cached in the first place. If your phone is acting sluggish, reboot it. You'll get better results as all the caches are cleared and the system can do what it was written to do.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dc5ftw:
deleted post
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dotnetguyaz:
LMFAO! I'll go slower next time. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fiffan86:
I personally have had 0 problems with MMS since the beginning of quantum, I use stock messenger and I'm on straight talk. I use MMS all the time to send pics of that fire near Yosemite since it is in my backyard to my family. I'm under advised evacuation.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
Then atm I don't think its fair to compare issues in 4.3 to issues in 4.2.2. Personally never had issues with the FFC on 4.2.2 ROMs. Guess some people did
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nishchhal:
flashing 1.18 currently, will report back after some testing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acme anvil:
You can disable it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
A change log ... or a pointer to the change log would be nice for those of us playing along. The rom seems to work so well it's hard to know something improved ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bxsteve31:
it worked but once i shut the screen off and turned it back on, it reset. drats.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
I know that, but I like the previous ones a lot more. Eh, I guess I'll just learn to live with it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acme anvil:
If your referring to the original toggles before they implemented the new layout, you can still have that. That's currently how mine is configured.