yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] GideonX:
Build 2013-03-01 d2vzw EXP - http://goo.gl/UN48A

- Mystery sauce

This is VZW testing only for now. Need some feedback before setting it free.
[Verizon Samsung Galaxy S III] illyfilly:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2vzw / d2usc [2013-02-20]

AOSP or TW?
[Verizon Samsung Galaxy S III] GideonX:
Always AOSP.
[Verizon Samsung Galaxy S III] cvsolidx17:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2vzw / d2usc [2013-02-20]

Gonna test it with SlimRom 4.2.2 that dropped
[Verizon Samsung Galaxy S III] RaiderX29:
So far so good on the 3/1 linaro build of AOSPA 3.1!!!
[Verizon Samsung Galaxy S III] x86cpu:
So far no problems running latest PacMan ROM on VZW. Thanks!
[Verizon Samsung Galaxy S III] GideonX:
For folks who flashed the test kernel, all is well in regards to battery life? Better, worse, or the same?
[Verizon Samsung Galaxy S III] juancaperez2000:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2vzw / d2usc [2013-02-20]

Better, @ least for me runnig asswax/row freq 192/1134 UV 75 on all freq,
[Verizon Samsung Galaxy S III] RaiderX29:
The same or better. Running Asswax / SIO / UV -50 on all freqs.
[Verizon Samsung Galaxy S III] Cruiserdude:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2vzw / d2usc [2013-02-20]

Battery life has been about average for aosp roms, I've been running it since you dropped it, and mostly it's been great. Performance is awesome and it's quite stable.

However, I am having a fairly serious issue. A few of the "custom" governors I've tried, namely smartassv2 and asswax, don't appear to be working properly. Sometimes, after the first few seconds, it goes to its maximum speed and stays there. Doesn't appear to be a wakelock situation, as better battery stats doesn't show anything, but it stays at maximum speed over 90 percent of the time.

This does NOT happen with the standard governors, or some of the custom ones, like badass and Wheatley. No idea what causes this, as it doesn't always happen, but when it is occurring I can switch to another governor and speeds will settle back down, but switching back to the "offending" governor will make the speeds jump back up again. But to repeat, this is NOT an issue that's always present, and I am not yet sure what causes it's occurrence.

Oddly, this doesn't seem to have a huge impact on battery life, but still an issue you'd want to be aware of. Anyone else having similar issues?
[Verizon Samsung Galaxy S III] GideonX:
I'm seeing the same thing, which generally makes it perform a bit better I suppose. I'm going to venture a guess that that's how those two governors work based on cpu load. Since asswax is based on smartass, they're a bit similar.
[Verizon Samsung Galaxy S III] Cruiserdude:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2vzw / d2usc [2013-02-20]

Okay, after playing around with it a bit more, it appears to happen every boot and persist for a while if I don't play with the settings. Actually, it seems to do it with all governors at first boot, except for one, msm-dcvs. Several times now, switching to msm-dcvs for a few seconds then back to whatever I want seems to fix the issue, and I haven't seen it return until I reboot.

This testing is by no means definitive, and I'm not sure what the root problem is. But no governor other than performance should stay locked to its highest frequency all the time, because that's missing the whole point of a governor. So if I'm not the only one seeing it, it is a kernel issue, though I couldn't tell you where it springs from or how to fix it.

For a quick and dirty fix, you could try setting msm-dcvs to the default governor on boot, and the delay between booting and your kernel tweaking app of choice being granted superuser permissions and setting your desired governor may be enough to keep this from happening. You'd just have to remind people to switch governors to something else if they want to use higher and/or lower than stock freqs.

Granted, this may not work, and wouldn't be truly fixing the issue, but may prevent it from manifesting, and may help you nail it down.
[Verizon Samsung Galaxy S III] GideonX:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2vzw / d2usc [2013-02-20]

I just did a quick test and I can't reproduce the on boot max cpu speed issue. It hits max after a boot, but it lowers on it's own after things settles down (give or take 2 mins or so). Some govs do this quicker (ondemand, interactive, etc.) while others slower (smartass2, asswax). I'm on wheatley/row with invisiblek's cm nightly kang if that matters.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] RaiderX29:
I'm not having this issue either. I'm hitting all freqs running most of the governors and none stay pegged at the highest frequency.
[Verizon Samsung Galaxy S III] GideonX:
Build 2013-03-04

d2vzw - http://goo.gl/Q66xg

d2usc - http://goo.gl/ROn60

- Sync'd to latest CM

- Uses latest Linaro toolchain 4.7-2013.02

- Added 192Mhz stepping

- Other changes and tweaks, check my bitbucket

Zen scheduler didn't make it in this one mainly because I don't see it being anything better than SIO.
[Verizon Samsung Galaxy S III] x86cpu:
I installed this last night.....normally when I go to bed my battery (extended) is 50%. Today at 5pm is was 29%. Something is really wrong here. The PRE one to this worked much better. My governer didn't change, I'm trying a new one now to see, but the battery life really went down hill on this last one.....not sure why....Thanks for doing this!!!
[Verizon Samsung Galaxy S III] GideonX:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2vzw / d2usc [2013-03-04]

Give it another day or two and see if you are still seeing that difference.

I'm seeing a slight increase on my end here in my daily usage.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] GideonX:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2vzw / d2usc [2013-03-04]

Using latest BMS with cm10.1 on 4g most of the day. Screen at 2.5hrs so far. I'm alright with it ;)

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] hallstevenson:
I just flashed 10/23 kernel and it's charging fine...
[Verizon Samsung Galaxy S III] GideonX:
Can't reproduce this.

I'm on 11/17 carbon nightly if that matters.
[Verizon Samsung Galaxy S III] hallstevenson:
I'm on PAC 11/5 nightly. On 11/12 and later, I was getting terrible battery life with stock kernel or your 10/23 kernel. I'll try it again to make sure it's not something else...
[Verizon Samsung Galaxy S III] beepea206:
Pacman has a lot of battery Wasting **** in it... I'm not surprised you're having issues. I had terrible battery life on that rom too.
[Verizon Samsung Galaxy S III] hallstevenson:
I routinely get 18-24 hours with PAC and BMS. Just yesterday, I got 33 hours! I do NOT think his ROM is that bad...
[Verizon Samsung Galaxy S III] ladclothing:
Hey I'm using the miui port and flashed this kernel twice and both times my screen was all wacky
[Verizon Samsung Galaxy S III] GideonX:
What's the rom build date on that port? If it's missing some video commits, you'll get the rainbow display.
[Verizon Samsung Galaxy S III] garyh2:
Compass messed up

I am running PAC 10/28 nightly with 11/13 BMS and when I run GPS Status (as well as anything using the compass) directional changes are updated very slowly and choppy. The GPS seems to lock just fine, it seems it's just the compass that has an issue. Let me know if you need any more info, I'd be happy to provide it.
[Verizon Samsung Galaxy S III] ladclothing:
http://xdaforums.com/showthread.php?t=2388076

There that's the ROM I'm running and I'm running the latest miui 3.11.1 I must be missing it cause I don't see a build date. And I don't think its a rainbow display it looked more like when you drop your phone the colors where inverted someplace and the parts of the screen where all over the place. Thanks for the help!
[Verizon Samsung Galaxy S III] countryfolk07:
The build date on this is 11-3 I believe.
[Verizon Samsung Galaxy S III] ladclothing:
Oh OK thanks using the app on my phone so its easy to miss stuff!
[Verizon Samsung Galaxy S III] peekeesh:
is the USB fast charge already enabled or do I have to get an app to turn it on? if its the latter, can anyone tell me which app to download? sorry ima noob with cm. thanks!
[Verizon Samsung Galaxy S III] mudsam:
You can use Trickster MOD to enable fast charge.
[Verizon Samsung Galaxy S III] peekeesh:
Thank you kind sir!
[Verizon Samsung Galaxy S III] ladclothing:
So does anyone have any ideas why my screen was all whack both times
[Verizon Samsung Galaxy S III] GideonX:
Only suggestion I have is to go back a version of bms and see if it does the same thing. If it does, then stick with an older release until the rom catches up.
[Verizon Samsung Galaxy S III] ladclothing:
So try a later update of your kernel?
[Verizon Samsung Galaxy S III] GideonX:
An earlier release.
[Verizon Samsung Galaxy S III] ladclothing:
Yeah that's what I ment and thanks I'll give it a shot!!
[Verizon Samsung Galaxy S III] ladclothing:
Well I tried that and same result so idk oh well...
[Verizon Samsung Galaxy S III] GideonX:
You tried 11/13 and 10/23 and both do not work properly?
[Verizon Samsung Galaxy S III] ladclothing:
Yeah and I even tried wiping cache before flashing too. Its weird never had a problem installing a kernel before
[Verizon Samsung Galaxy S III] garyh2:
Has anyone else seen this and know of a solution?
[Verizon Samsung Galaxy S III] picarito:
So I was looking to see if the last BMS kernel for android 4.2.2 had int.d support but pimp my rom app says it doesn't and I want to have it so I can put some scripts in the folder so they can run at startup . can I enable it or is there other way to do it??? Help will be much aprecciated

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] GideonX:
2013-12-06 Build - http://www.droidhype.com/kernel/34/
[Verizon Samsung Galaxy S III] Dcox28:
Just flashed this newest kernel on gummy 4.4.1, it breaks WiFi and won't allow me to turn it on. It worked fine before flashing kernel

Edit - guess I should add that I have a D2VZW. just dirty flashed the ROM and WiFi is back with the stock kernel
[Verizon Samsung Galaxy S III] garyh2:
The bad compass behavior continues w/ the 12/06 kernel on the PAC 11/05 nightly.
[Verizon Samsung Galaxy S III] beepea206:
Unless something changed, you'll lose functionality if you use a custom kernel with Gummy. I'm on Gummy 12/8 and haven't tried KT or BMS, because it previously lost root access or killed the modem.
[Verizon Samsung Galaxy S III] GideonX:
Got a link to their source or thread? I can take a look.

Need to check on this. Have any logs I can look at?
[Verizon Samsung Galaxy S III] Dcox28:
Thanks Gideon. I think I'm gonna try the new PA that just came out but here is that link to Gummy....... http://xdaforums.com/showthread.php?t=2556839
[Verizon Samsung Galaxy S III] hallstevenson:
PAC 11/5 ? That's rather old.... It works fine on current builds, FWIW.
[Verizon Samsung Galaxy S III] garyh2:
Yes, attached are logs and the process I used in generating them. Let me know if there are any flaws in my methodology.

reboot, when cell service is found, unlock, let sit for 2min, unlock, launch logcat & save

stock kernel-clean boot.txt

reboot, when cell service is found, unlock, launch gps status, let sit for 2min, launch logcat & save

stock kernel-clean boot-gps status.txt

installed BMS

reboot let sit for 10m timer started after cell service was found

reboot, when cell service is found, unlock, let sit for 2min, unlock, launch logcat & save

bms-clean boot.txt

reboot, when cell service is found, unlock, launch gps status, let sit for 2min, launch logcat & save

bms-clean boot-gps status.txt

In addition, I have noticed the same behavior in the dkp kernel but NOT the kt kernel. Hopefully this is sufficient information to get you on the right track! And please don't hesitate to let me know if you need any additional info.

--EDIT--

to clarify, DKP compass was NOT working, similar to BMS

KT compass seemed to function properly

--EDIT--

hallstevenson-

Yes, on PAC 11/05. I was getting the same behavior on the 10/28 build and after reading about your success w/ BMS & the 11/05 nightly I decided to give that a shot in hopes of the compass working again, but it did not.
[Verizon Samsung Galaxy S III] hallstevenson:
Ahhh, your name sounded familiar.... I've re-flashed PAC 12/7 and now 12/8 and keep forgetting to flash the latest BMS kernel, but I'll do it as soon as I post this and see how things go.
[Verizon Samsung Galaxy S III] GideonX:
Thanks for the info.

Fixed in the new build coming up in a few mins.
[Verizon Samsung Galaxy S III] GideonX:
Build 2013-12-09 - http://www.droidhype.com/kernel/34/
[Verizon Samsung Galaxy S III] MrBrady:
XDA search functionality is out of service at the moment, so I figured I would ask. It appears this kernel does not support the new 4.4 ART Runtime. Is that correct?

I installed it over an unofficial build of 4.4.1 Carbon. With the stock kernel I can run ART but once I flash the 12/9 BMS kernel, it always reverts back to Dalvik.

EDIT: Turns out it was Xposed Framework causing the issue. NOT this kernel. Kernel is running well with ART.
[Verizon Samsung Galaxy S III] garyh2:
!

I have confirmed the compass is working as expected now.

Thank you for the quick fix!
[Verizon Samsung Galaxy S III] beepea206:
Running 12/9 on Gummy 4.4.1... like buttah. :D
[Verizon Samsung Galaxy S III] GideonX:
No idea on this one, I don't run ART or Carbon. Anyone else can confirm this?
[Verizon Samsung Galaxy S III] MrBrady:
I did some more research and it turns out it's not a BMS kernel issue. I assumed it was because when I re-installed the ROM with the stock kernel, the issue went away. It turns out it is an issue with Xposed Framework being installed and activated. BMS kernel is now running smooth with ART enabled. Sorry for the confusion. :good:
[Verizon Samsung Galaxy S III] YevOmega:
Hey guys. Can anyone break down the advantages and disadvangtages of BMS over Ktoonsez and the kernel CM11 comes with? Thanks!
[Verizon Samsung Galaxy S III] GideonX:
Stock doesn't have voltage control, cpu slot control, fast charge, simple gpu gov, numerous cpu gov, numerous cpu schedulers, and BOOP.

Either custom kernel works, it's how well it works on your phone that counts. Again, not all d2vzws function the same and your experience on the same rom and kernel can be drastically different than someone else running the same setup. Experiment, that's what makes this interesting.

Oh yeah, advantage, boop.
[Verizon Samsung Galaxy S III] YevOmega:
I agree that experimentation is fun. What about in terms of battery life?
[Verizon Samsung Galaxy S III] Atrizzain:
I'm well on pace for over 4 hours of screen on time. With CM 11 official, 12/10 nightly, ondemand/row, underclocked to 1350.
[Verizon Samsung Galaxy S III] Atrizzain:
Here's the overall.
[Verizon Samsung Galaxy S III] YevOmega:
Thanks. Brightness?
[Verizon Samsung Galaxy S III] Atrizzain:
I always use auto brightness.
[Verizon Samsung Galaxy S III] YevOmega:
Ok. Thanks. I suggest you don't use auto because it's known to drain battery. You'd be better off at a set 1/3 or so.
[Verizon Samsung Galaxy S III] Atrizzain:
Hmm, never heard that before but it's worth a shot. I may just try that out on a full cycle tomorrow. Thanks for the heads up.
[Verizon Samsung Galaxy S III] YevOmega:
No prob. Let me know your results. Please.
[Verizon Samsung Galaxy S III] LeoRex:
Ok... loaded the latest up.. on top off paranoid android 3.99 (4.3 based). When it boots, the video is all chewed up as if the resolution is shot.

Any ideas?
[Verizon Samsung Galaxy S III] GideonX:
Try an older bms release. Sounds like there's some video driver goofiness.
[Verizon Samsung Galaxy S III] goldsmitht:
I'm on official 4.4 and video is fine
[Verizon Samsung Galaxy S III] LeoRex:
Awesome.. didn't even think of that. I had to go back to a build in September, a version that matched what was with the ROM... booted like a boss.

Noticed that the next build had some info about video driver updates to cm 10.2 (which pa 3.99 is based on).

Thanks
[Verizon Samsung Galaxy S III] GideonX:
Bingo :)
[Verizon Samsung Galaxy S III] YevOmega:
Hey man. Results?
[Verizon Samsung Galaxy S III] Atrizzain:
I haven't noticed any improvement overall. I'm still right around 3.5-4 hours of screen on time, the adaptive backlight seems to do a good job of saving juice. I say if it ain't broke, don't fix it. If you haven't installed this kernel, take the plunge. It's worth it.
[Verizon Samsung Galaxy S III] YevOmega:
Someone else told me he gets 2 hours more life with his usage pattern on Ktoonsez when compared to BMS. And it is broke. Adaptive backlight doesn't properly adjust to the brightness in your environment, and it usually sets the brightness higher than is needed. If you like it, suit yourself, though. Thanks for the feedback Atri. Really appreciate it.
[Verizon Samsung Galaxy S III] MrBrady:
Lux Lite seems to work well, and it's quite tweakable: https://play.google.com/store/apps/details?id=com.vitocassisi.luxlite
[Verizon Samsung Galaxy S III] YevOmega:
Nothing beats setting the brightness to like 30-40% and keeping it there, in my book. But thanks!
[Verizon Samsung Galaxy S III] Mattish13:
What about those of us who wander outside and try to use the phone in full sun?
[Verizon Samsung Galaxy S III] YevOmega:
When I do that on rare occasion, I just max it out. CM has a nice brightness slider and I think TW did too.
[Verizon Samsung Galaxy S III] savagebunny:
Using mastamoons CM11 12/10 build.

Flashed the latest BMS I have my phone on the loudest notification sound settings plus for phone calls, but still doesn't make any sound at all.
[Verizon Samsung Galaxy S III] GideonX:
Try any of the newer mastermoon builds?
[Verizon Samsung Galaxy S III] savagebunny:
EDIT: I figured it out. I have no idea why it took me so long. It isn't the kernel or ROM. PEBKAC :P
[Verizon Samsung Galaxy S III] GideonX:
It's ok, it happens.
[Verizon Samsung Galaxy S III] GideonX:
Build 2013-12-15 - http://www.droidhype.com/kernel/34/
[Verizon Samsung Galaxy S III] Atrizzain:
Your kernel is bliss, I've come to a point where every ROM I flash instantly gets booped! Great work!
[Verizon Samsung Galaxy S III] Maphack:
For the life of me I cannot figure out why I always default to interactive/row

I tried searching the thread but I didn't get much info...I tried editing any time I saw interactive to ondemand and I see nothing mentioning schedulers or governors in my init folder...

Will this cause any problems for me?

Sent from my SCH-I535

:thumbup:
[Verizon Samsung Galaxy S III] GideonX:
It's usually set by your /etc/init.qcom.post_boot.sh file. It defaults to int/row for just about every rom.

Why not just use an app like trickstermod and have it set on boot?
[Verizon Samsung Galaxy S III] duarian:
Just an FYI, I am on masta's CM11 and I could not get this to flash, it gave me a status 7. I had to delete the entire first line of code up to the semi-colon and it flashed just fine.

Anything I can do to avoid that in the future?
[Verizon Samsung Galaxy S III] GideonX:
What recovery?
[Verizon Samsung Galaxy S III] duarian:
CWM touch. Its still the latest one, but I think it was modded to accept swipes.
[Verizon Samsung Galaxy S III] GideonX:
Tried redownloading the d2vzw zip?

Cant say I've encountered the status 7 issue on cwm or twrp.
[Verizon Samsung Galaxy S III] duarian:
About 10 times over, both from my phone and my computer. No matter what I do I get the status 7 with a bunch of code after it (the code in the script).

It's not a big deal for me to delete the code. I just figured i'd bring it to your attention in case something needed done. Awesome kernel by the way!
[Verizon Samsung Galaxy S III] Maphack:
Thanks. I was just wondering if it would be unstable or something, I have no problem setting them on boot.

Sent from my SCH-I535

:thumbup:
[Verizon Samsung Galaxy S III] Bamdroid:
This. Kernel. Rocks.
[Verizon Samsung Galaxy S III] GideonX:
If anyone feels like running a couple of 4.4 roms that work well with BMS, download them here:

http://www.droidhype.com/roms

These are kangs that I've built for myself and some friends to play with. I'm not the rom dev -- I just compiled.

Enjoy
[Verizon Samsung Galaxy S III] kinnerful:
Use another recovery like the regular CWM-touch. The CWM-swipe from Masta's post doesn't seem to flash a lot of zips, giving tons of status 7's.
[Verizon Samsung Galaxy S III] duarian:
Are these CM or AOSP based? I realize they are almost the same but I just figured I'd ask. Also are they both 4.2.2?

I'll probably give them a flash tomorrow :)
[Verizon Samsung Galaxy S III] hallstevenson:
Let me check the OP and get back to you on that...
[Verizon Samsung Galaxy S III] GideonX:
Everything is 4.4.2, based on bits of CM and AOSP.
[Verizon Samsung Galaxy S III] duarian:
I'll give them a shot later tonight. Really wanted to try an aosp ROM, and gummys is the only one available right now. For whatever reason my phone just will not accept a flash of his ROMs. Always gets stuck at a corrupted boot logo AMD locks up and resets.

Trying to get away from CM as I use gravity box, makes me have no real need of CM and I've heard stock aosp is more stable.

What is the difference between the two builds? I notice one is newer than the other but I won't be able to flash until later tonight.

If you were responding to me, I was not referring to his kernel but the two builds he posted one post above.
[Verizon Samsung Galaxy S III] GideonX:
Gummy is not truly entirely AOSP. Check the git and manifests - CM is sprinkled here and there. It might be AOSP based, but definitely not entirely AOSP. Then again, no rom for the S3 will ever be.
[Verizon Samsung Galaxy S III] beepea206:
Yea, they're AOSP-based with CM-sourced hardware and device repos. A dev with the skills could make non-CM device files and I assume they could with the hardware too. Is there a kernel issue that requires a CM-based kernel or are the device/hardware repos the only thing stopping an pure AOSP build?
[Verizon Samsung Galaxy S III] GideonX:
Mostly just device and hardware.
[Verizon Samsung Galaxy S III] beepea206:
Then we just need some coding ninjas to get the hardware and device files to jive with AOSP. That stuff is way above my paygrade.. which is why I bet most people use the CM repos.
[Verizon Samsung Galaxy S III] duarian:
So Gid, what's the difference between the two ROMs you listed? I'm definitely intrigued to try them out, just figured I'd ask since you compiled em.
[Verizon Samsung Galaxy S III] GideonX:
Beanstalk has halo/active display/etc.

Cyan doesn't.

Try them both out, just nandroid ;)
[Verizon Samsung Galaxy S III] duarian:
Sounds good to me! Any particular GAPPs you recommend? I only ask because there are about 4 different sets floating out there. Banks, PA..etc etc.
[Verizon Samsung Galaxy S III] GideonX:
I use PA gapps, seems to work just fine.
[Verizon Samsung Galaxy S III] hallstevenson:
There's really no differences in the various ones out there. Some "groups" just package different versions of the apps (for no obvious reason), some invert the color schemes, or play with the install scripts. The apps themselves, Gmail, Play Store, etc, are proprietary and can't be changed.
[Verizon Samsung Galaxy S III] duarian:
Just in time for the new build today on cyan!
[Verizon Samsung Galaxy S III] beepea206:
Same here. I've had less issues with the mini package, though.
[Verizon Samsung Galaxy S III] duarian:
Hey Gid, just wanted to let you know CM made some kernel changes again, kernels are breaking the battery readout since 12/18 updates.
[Verizon Samsung Galaxy S III] flyestAC:
Hey Gideon thanks for sharing these. I'm running the 12/18 CyanFox and I see your name in the baked in kernel. Question... is the baked in one BMS or do you recommend flashing the latest BMS with the ROM? Thanks again for all your work.
[Verizon Samsung Galaxy S III] GideonX:
My name is in there only because it was built/compiled by me. It's the stock kernel as chosen by the rom devs.

I will never bake BMS into any of the roms I kang. I don't believe in forcing anyone to use my kernel.

I've got some liquidsmooth 4.4 kangs coming, I'll let you folks know when it's up :)
[Verizon Samsung Galaxy S III] flyestAC:
Great. More flashing.

;) :D :thumbup: