yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 850T5m:
I keep losing my baseband when I flash your kernel. I flash it, reboot and never get a signal. Need to flash the Rom again with different kernel.

Anyone else have this problem?

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
Yeah it happened to me earlier. Reflashed ROM, Gapps, BMS, and all is good now.

It's not just this kernel, it's been happening with other kernels as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 850T5m:
I tried flashing it 3 separate times, and downloaded it twice...I'll try a last time lol

Anyone have other input?

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
I should put this in the op or on the download page.

This happens with other combos, not just BMS. It's an easy fix, just reflash your rom, gapps, BMS (in that order) without rebooting in between zips. Don't wipe cache or dalvik.

Everything will come back after you reboot.

This doesn't happen to everyone, only a select few. I've never seen the issue first hand, while it happens to others anytime they flash an update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 850T5m:
That worked perfectly

Thanks a lot!

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sepharite:
Quite a while ago, perhaps a month ago. It's a 4.2.2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Sounds like it's missing a few commits. Best suggestion would be to upgrade if possible.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
Thanks for your work!

Does it default to interactive now? I'm asking the question because it's in interactive by default on my device and I don't have any script or apps configuring this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
It's likely your post boot script from your rom. It usually defaults to interactive.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
Yeah you are right... I just looked at the wrong place. Qcom script was there...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
Just use trickstermod kernel controller from play store to change your kernel settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbze430:
anyone using this kernel experience bam_dmux wakelocks?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
You have an app keeping your data open.

I'd check if you have anything automated, like backups or location check-ins.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bradld:
Not sure if kernel or ROM related but I am noticing that right after boot I have random times where the network signal will show no service until I either toggle WIFI or airplane mode. I have reinstalled rom, gapp & kernel consectively w/o reboot as suggested previous posts with no change to this random behavior.

Any ideas? :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Which rom?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bradld:
AOKP(Jellybean 4.3 )Task650 (9.10.2013)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fireforhire:
With the new version of slim bean official release, it kills the IEMI. status = unknown. Out of fear, I restored my back up, and it fixed it. Reinstalled this kernel, and it did it again. Flashed lean kernel, and it fixed the IEMI error.

Beware trying this kernel on the official slim bean rom
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Did you see the big red note on the download page in regards to losing signal? It's not a BMS unique anomaly, it happens with other kernels when you jump to another. Just follow the big red directions and you'll be back in business.

On another note, I run slim as my daily. Stable 1 and BMS is smooth like butter on hot corn.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bradld:
Mmm butter. :highfive: BTW, awesome job with this Kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Beware of what? I've been running this kernel since slim beta 2 and currently running it on slim official build 1. You're not following the OP instructions is what's happening.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] allrockedout:
Anyone else try this with AOKP(Jellybean 4.3 )Task650 (9.10.2013) any problems?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tobesedated:
You are absolutely correct about losing IEMI... But it happened to me on CarbonRom ... Installed as per instructions.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
And you've installed according to the red instructions on the download page?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tobesedated:
Yes I tried just the kernel after I had been running the rom and when I realised I had lost the IMEI, I flashed rom, gapps and kernel... In that order no reboot in between. I even tried reflashing and then fixing permissions... All 3.4 versions. I'm just glad restore fixed it. I used your kernel faithfully but to be honest I hadn't flashed it in a while. Too bad cause I really do like running BMS as my go to... All trial and error :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Care to try out this zip and see if you get the same results?

http://goo.gl/gOSI5m
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tobesedated:
Definitely thank you

---------- Post added at 09:00 AM ---------- Previous post was at 08:43 AM ----------

Worked beautifully! Thank you so much!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Chr0nicDreamz:
I still have yet to come across this issue. With all the different ROMs and kernels I've flashed I guess I've been lucky. Hope it gets taken care of for you.

Sent from my SAMSUNG-SGH-I747 using Xparent Skyblue Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SlothlyDX:
Happens to me every time I flash BMS kernel. The easy fix is in this order after you have flashed rom and gapps. Reboot back into recovery then : flash kernel, flash rom again, gapps again, kernel a second time. Then reboot. Your IMEI is back. I'm a tester for this kernel and it never fails. I always lose my IMEI but it comes back
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Chr0nicDreamz:
I've been using BMS since 4.1.2. No issues ever on my end. I refuse to use another kernel as they do not meet my needs.

Sent from my SAMSUNG-SGH-I747 using Xparent Skyblue Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tobesedated:
After flashing BMS via the link Gideon posted issues have been resolved..yay :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Chr0nicDreamz:
Always good to hear. Didn't realize it was fixed before I posted that. Haha. I realized it after the fact when I went back and read the additional posts.

Sent from my SAMSUNG-SGH-I747 using Xparent Skyblue Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Build 2013-09-29 - http://www.droidhype.com/kernel/34
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
Fixs IMEI issue. Gonna test battery. What's you're kernel settings? (:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
I'm on sioplus/interactive, hispeed at 1080.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
Will try. (: Hopefully battery is good.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SyNRGz:
Thank you! I am amazed at the improved Battery life with these settings on current SlimRom. I also have multicore set to 2. Your thoughts?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
I'm not sure if that multicore does anything useful. I've changed it a bunch of times and didn't feel anything different at the end of the day.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pberge:
I have never noticed much difference between schedulers, but sioplus seems to really work well. I was playing around with a few different govs, but mostly used interactive today and I just hit 4 hours screen time and almost 18 hours total with 10% remaining. Not sure if it makes a difference, but I have multi core saving at 1.

I listened to at least 4 hours worth of podcasts and some Spotify throughout the day as well.

I'm running Task650's latest 4.3 release and it has been flawless so far with this kernel. Nice job as usual Gideon!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
What kind of difference does the sioplus from boype and boostpulse sync'ing from motley did to performance would you say Gid?

I contacted you by PM, you said nothing changed since 7/30. You...!! Knew I had to glance at the sources! :D

I really need to get into compiling my own stuff eventually haha. Do you have a VM for compiling all setup? It's like nobody uses any VM anywhere for some reason and i'm hella too lazy/busy to set all that up atm.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
You asked about 4.2 source, which has not changed much from upstream since 7/30. You didn't ask about 4.3 ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Deal deal. So no build environment in a VM you can share? I'll probably end up doing one so I can do CM builds and kernels, eventually.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
I don't use a VM so can't tell you much about it :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Alright thanks a lot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
Don't use a VM. I tried that and compiling Slim took 6 hours on a decent machine. Go dual boot. My time went down to an hour for the compile step once I did that. PM me if you want to know more about how I set things up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Hey thanks for the heads up. That might be why we don't see many of these. I'll pm you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] WarER4X:
Apologies if this has been discussed already (XDA search is broken at the moment). This is my for try at using a kernel other than the one prepackaged with my chosen ROM. I'm currently running LiquidSmooth 2.9. Everything runs ok except that I cannot get Tasker to turn Wifi off on the first try (if the run the task a second time, it will work). After researching the cause of that problem, I discovered some info from earlier in the year (when CM10.1 was still in nightlies) that said this Wifi switching problem (with Tasker) was a kernel issue and that a different kernel (or a rollback to the previous CM kernel) would fix it. So, I decided to look for a different kernel than what LS 2.9 came with and went for the BMS kernel.

After installing it, everything is stable (no baseband issues either) except that I am still having the Wifi switching problem. Additionally, scrolling is rather glitchy after installing BMS. It works, but the screen redraw isn't right. I presume it is a performance setting of some kind, but don't know where to start?

Any advice?

-SR-

PS: If you have any advice on the Tasker Wifi switching issue, that would be helpful, too.

PPS: Before going to LS 2.9 yesterday, I was running Vanilla Rootbox before that (the latest version available, can't remember the version number at the moment). Tasker had no problem switching Wifi off when running Rootbox.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I believe the wifi switching issue is a rom issue, not a kernel issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] WarER4X:
Good to know; thanks.

-SR-
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
LS 2.9 is old. Latest BMS is based on newer CM sources. You should try to keep your kernel and ROM close together in release dates to help avoid these kinds of screen tearing issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] WarER4X:
Thanks for the reply. The ROM packaged with LS 2.9 is versioned as 3.4.53 from July 20th, about 2 months older than the BMS kernel I just downloaded. Is that really enough difference in iterations to cause such an issue?

-SR-
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Yup, lots of changes since then.

Tasker turns wifi off/on for me without a problem. I'm on latest slim and bms.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] WarER4X:
OK, thanks. I'll check that one out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ryanoption:
Love this! Flashing this cleared up some issues i has having with AOKP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MaLiXs:
Hmm my device just got an SOD with this kernel. Anyone else having sod?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Nope, rock stable here. What rom?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MaLiXs:
Slimbean 4.3 stable on d2att
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
What kernel settings? Min/max/voltages/etc/etc/etc.

Any scripts installed?

Any changes made to your build.prop changes? sysctl?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SyNRGz:
+1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MaLiXs:
Min 189 , max 1512, gpu 400, cpu gov interactive, i/o sioplus, gpu gov simple, stoc voltages, no change in buildprop, idk what is sysctl, no script
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbze430:
anyone here using this kernel have any issues with Bluetooth music streaming once in a while it would do a drop off?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
Just want to say my battery life is awesome with this kernel and thank you for fast charge! Please keep updating!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
[MENTION=2645480]GideonX[/MENTION]

Is simple GPU governor still in? I can only see ondemand and performance on latest build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
It's still in there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Hmm that's strange, can't see it in Trickster's, but I can see everything else just fine (sioplus is there for instance). :|

Any idea?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
You are looking at the gpu options under the Specific section in Trickster?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Yes, shows Performance and Ondemand under GPU Governor.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbze430:
I've been using Android Tuner for most of the CPU configuration, does Trickster have the option to control the Screen off part of the cpu or this kernel doesn't support it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] trecko1234:
Trickster does not have this option but I'm not sure if its just Trickster or the kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbze430:
that sux... using V4A... but I don't htnk there isn't enough CPU power while screen off... so I am getting all kinds of "hickups" using V4A.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Shows up ok for me, see attached.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Flash slim nightly. The commits I have are ahead of the stable build and can possibly cause some unexpected weirdness.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SlothlyDX:
This had nothing to do with a kernel issue. This issue is known for all roms lately. I have had many hiccups with V4A and is while using other roms and kernels as well. It seems to be an app issue
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbze430:
It probably has nothing to do with the kernel technically. But rather V4A being CPU intensive. For example. If I leave the screen on running Performance governor Music never gets a hiccup.

Same scenario, but if another background is going on, V4A starts to act up.

Which makes me believe that during screen off, there is not enough CPU multiplier to really make V4A smooth.

So technically speaking its not Kernel but a kernel that allows screen off adjust might help. unfortunately Ktoonz's kernel is way way behind on the CM commits. Now, have to rely on other kernels
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I swear I'm not entirely retarded haha

Am I missing the obvious?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
That is really bizarre, it should be there. I'm looking right at it on mine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Alright I'm gonna reflash! No idea why it's not there, maybe reflashing fixes it.

Edit: Nope, no go. :|

Edit 2: Duh huh huh, I restored an old Trickster MOD from my TiBU backup for some reason. Those governors just weren't supported by the old version, and I didn't update it even though it was bugging me in the Play Store. Updated and voilà... Took me entirely too long to figure out and it was so stupid.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
I should have asked if you were on latest Trickstermod version, oops.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Build 2013-10-16 - http://www.droidhype.com/kernel/34/

This one is mostly a maintenance build, nothing really new aside from fixing the 4.3.1 pac-man problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
There were touchscreen issues? >_>
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
CM merged in some touchscreen adjustments which caused some other problems. Anyway, it's working and peachy now, I hope.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Ah, wasn't aware.

Running CM10.2 20131014 nightly here and nothing really seemed wrong. But hey, less problem mo' better. Will flash when I update to the 20131016 nightly.

Thanks! :D

---------- Post added at 09:54 AM ---------- Previous post was at 09:39 AM ----------

Lost network on flashing CM10.2 20131016 nightly + BMS 16-10. Rebooted to recovery and reflashed kernel, all is good. I thought we were clear of that problem? :S
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
May have been a fluke :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
First time ever for me. I'll blame it on not updating something. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Hey gid what is the latest kernel settings for good battery life?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
I'm using sioplus/interactive, I'm digging it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prufta:
You can use the setting posted on the reply # 1535 by #Gideon, I'm using it and have excellent battery life and speed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Post #1535 isn't by Gideon...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prufta:
Sorry mistyped, it was a reply to [MENTION=227136]Gideon[/MENTION].
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
[MENTION=2645480]GideonX[/MENTION]

Kernel will need an update for d2xxx 20131019 nightly. :)

Unless you want to end with buggy graphics. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Link me to said changes! :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
:D

http://review.cyanogenmod.org/#/c/51980/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
That's for the apex, has little to do with d2 even though kernel is just about identical :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
You should try your 20131016 kernel on the 20131019 nightly and see the beautiful inverted colors then. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Dammit, there are other changes.

Brb...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
To the Gid-cave! :silly:

Will wait somewhat patiently for an update. Had got used to sioplus, smartmax and simple GPU.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Try this one - http://goo.gl/bimXYb
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Successfully booped by BMS. Thanks a bunch!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
I'm assuming it's not worth it to flash this if not running cm?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Only if you're running CM 10/19 and up for the time being. Other roms should follow suit shortly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Fair enough. We'll see what slim does this week then.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
The test builds look to be working, so here's the official release.

Build 2013-10-19 - http://www.droidhype.com/kernel/34/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Party hard. Do I get a cookie? It's my birthday too. :cool:

Been running this all night and all is superb as usual.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
No cookie for you!

---------- Post added at 11:57 AM ---------- Previous post was at 11:41 AM ----------

Heads up for anyone flashing the new slim weekly: the 10/19 kernel release makes the blues yellow. Stick with the 10/16 version.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pberge:
New release is working great on the latest Carbon nightly (10-20).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jayRokk:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2att [2013-03-04]

Going to try this bad boy out :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thehavock18:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2att [2013-03-04]

Using liquidSmooth ROM the built in performance monitor works with on demand
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lessthanzach:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2att [2013-03-04]

You won't be disappointed. I just tried it out for the first time and it is incredibly well made. Using on tasks latest. Gonna have to send a donation now! :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] toyanucci:
Here's a screenshot. I really can't figure this out. Did a fresh install, same problem, even tried a different rom from a fresh install and had the same issue of 192 not showing up. Guess I'll just have to do without it for now.

Thanks again for all the time you've dedicated to making this great kernel!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2att [2013-03-04]

When you say fresh install, did you format system before installing your last ROM? Maybe some junk from past installs is lingering.

SlimBean 4.2.2 with BMS kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2att [2013-03-04]

That's really odd, 192 isn't even listed as an unused step. :what:

Sent from my SCH-I535
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2att [2013-03-04]

Why run 192 tho honestly... It just gives the phone more steps to take to highest frequency... I run 540 minimum and uv that step to the 192 voltage... No battery sacrificed.... Yet so much gain by saving steps and better performance ;) just a tip tho.

trolol and awayyy!! Expect typos this is my phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2att [2013-03-04]

I do have 192 as my lowest freq but i think I have some extra frequencies

I could of sworn some of those weren't there on the last version?

But everything is running amazing super smooth and no issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] toyanucci:
That's what I'm saying, but all the other kernel features are there. I don't even know what to think lol.

---------- Post added at 06:22 PM ---------- Previous post was at 06:20 PM ----------

Yup. Cleared both caches and formatted. Tried carbon 1.5 as well with the same results. Fresh install and only installed trickster mod to check. Guess it's just a mystery!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] toyanucci:
I definately don't have some of those
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2att [2013-03-04]

Not sure if you wiped data. Is it possible that TricksterMod has cached data? Have you tried clearing the app data and cache? Clearly grasping at straws here.

SlimBean 4.2.2 with BMS kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] toyanucci:
I tried setcpu as well, same results so irdk
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jproy12:
12packabs, I'm seeing that you are running this kernel with the slim ROM, what are your settings and roughly your battery life?

JP
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nklenchik:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2att [2013-03-04]

Has anyone questioned mpdecision, or have it enabled?