yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Are you sure you downloaded the new 3.4 release and not the new 3.0?

If the zip does not say 34, then it's the 3.0 version.

Sent from my SCH-I535
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theadb:
Not booting on aokp milestone 1 for me either (ignore my Sig)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Not booting as in stuck on splash screen or....? Which zip did you download?

Sent from my Nexus 7
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] F1reEng1neRed:
Working fine on tasks rom. :thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theadb:
3.0.

Stuck before boot ani.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] F1reEng1neRed:
Then you flashed the wrong one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theadb:
Yep I did. Didn't realize milestone 1 was on 3.4. Sorry Gid.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] F1reEng1neRed:
Are you back up and running?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theadb:
Just tried the 3.4 build. Saw the "booped" splash screen but still wouldn't boot.

Flashed back to stock AOKP kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] F1reEng1neRed:
3.4 wouldn't boot either? Very odd.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
Aokp milestone 1 is 3.0 Linux if memory serves me correctly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
My asswax settings. Gives awesome battery and performance. 324/1566 asswax/fifo.

Deviance runs in the blood...

BMS fueled.

4.2.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
You should be able to use these settings whether your on 3.0/3.4 version of the kernel.

Deviance runs in the blood...

BMS fueled.

4.2.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Habs69M:
Wont stick on reboot :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
Awesome detailed post. What are you trying to accomplish here?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Habs69M:
My reply didnt work for the asswax settings obviously
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
Obvious how? Because you quoted someone or even mentioned asswax in your awesomely detailed complaint?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Habs69M:
Ok enough go back to bed boy, i clicked reply instead of quote, SUE ME

---------- Post added at 02:43 AM ---------- Previous post was at 02:40 AM ----------

Wont stick on reboot for me anyways
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] F1reEng1neRed:
Make sure you know if you need 3.0 or 3.4. Sounds like a lot of people are flashing the wrong version.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
Mine stick on boot make sure its enabled in the app... With no delay

sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] daver68:
Nope, I've been using 3.4 for at least the past month now, I think (or at least since the beginning of April)

I made sure, twice, that I downloaded 3.4, NOT 3.0, and both times I get to the "Booped by BMS" boot screen. After that, nothing, screen is completely blank, but I can see that the menu + back keys are illuminated. I tried leaving hte phone for 20 minutes to make sure that nothing was running in the foreground causing this blank screen.

Either case, I'm back on 4/22 without any problems. I know that there were new display drivers in the 4/20 release, that may have caused blank screen problems, but I didn't have any issues with 4/22, just this one
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] micadee6453:
Thanks that worked
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oddspec:
I hope I grabbed this correctly I know some have been getting random reboots when watching vids but I just got one scrolling xda on tapatalk running slimbean current build latest BMS 3.4 with conservative/ deadline https://www.box.com/s/c5x6u7qs834s8gsu792f
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Habs69M:
+1 i needed 2 reboots for it to stick thks :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
So glad asswax is working again
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Axis_Drummer:
Latest 3.4 build combined with Slim Bean 4.2.2 build 4.2.

interactive/row with high speed frequency set to 810000 :cool:

http://i.imgur.com/sYpl6qC.png

http://i.imgur.com/kPm1Fcx.png

I'm happy with the outcome. :cool:

Sent from yours truly..

ΧΔΑ Fraternity's Rush Chairman
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Default settings or any tweaks with asswax, using row with asswax?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
5hrs screen on, wow :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Axis_Drummer:
With your Easter build 3.0 kernel and slim build 2.5 I got 6hrs screen on time pretty consistently. :)

I always recommend this kernel for everyone on AOSP :beer::thumbup:

Oh and that's stock battery by the way.

Sent from yours truly..

ΧΔΑ Fraternity's Rush Chairman
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fireforhire:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2att [2013-02-20]

What is this "colors" feature? I don't see how to configure it in the op, and it's vaguely mentioned in the thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
Do you mean Trinity Colors?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
It's Trinity colors, made by morfic and used with his permission. There is nothing to configure, it's "enabled" by default. You'll notice slightly whiter whites and the lovely bluish tint.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] superstargoddess:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2att [2013-02-20]

Best kernel I've used so far, keep up the good work! I love wheatly!

Sent from my SGH-I747 using Xparent Skyblue Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thyroidgland:
Absolutely love this kernel. Now I can't go to any other one because I love the trinity colors. It makes the whole phone look so great, and the battery life is awesome. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheSeanTeam:
Great problem to have!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BoostRoid:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2att [2013-02-20]

I don't post a lot but I just had to for this kernel. It's amazing. My phone is picky with kernels it's seems . Things may start off great but a day or so in I get lag and performance issues no matter what I do. But with this bad boy... Wow! So damn smooth even days later. ****ing loving it!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lookitfast:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2att [2013-02-20]

I must add the exact same.....looking forward to the future of this kernel ALOT!! Thanks to the dev ...very good for my setup!

Sent from my SGH-I747 using Xparent BlueTapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lookitfast:
Do we look for updates to this kernel here or in the verizon thread?:confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oddspec:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2att [2013-02-20]

Here and kernel is is running great on slim 4.2.2 only thing I'm looking forward to is a lower clock speed

sent from the samsung galaxy airplane (i747)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2att [2013-02-20]

ATT updates will be in this thread.

The vzw thread will get occasional test kernels, which may eventually end up being stables for everyone else.

Sent from my SCH-I535
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Do you still plan on letting us cut the idle down to 192? I remember seeing a 192MHz screenshot with the "hmmmmm" comment, and was wondering if that meant you changed your mind since that was about a week ago... you just making some other changes too I'm hoping?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2att [2013-02-20]

192 is in the Vzw test build. Expect it to be in all versions shortly.

Sent from my Nexus 7
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wally3614:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2att [2013-02-20]

Hey Gideon, I flash the new liquidsmooth rc2 as a tester and once I flashed BMS onto it, it turns everything upside down on orientation. If you turn screen to the right, the header also rotates to the right instead of opposite left and vise versa and the camera snap button rotates to opposite side of phone making pic upside down. Any ideas? Didn't do that on any previous version and the stock kernel works fine....love your kernel though so wanted to know what you thought ..

LiquidSmooth/Illusion 4.2.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2att [2013-02-20]

Only time I've seen that is when the wrong version was flashed. Confirmed att build was used?

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

Yeah same ROM I've been running and testing just an updated version.

LiquidSmooth/Illusion 4.2.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
it's the wrong version of the kernel that causes that. Confirm that you downloaded the ATT version of BMS.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wally3614:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2att [2013-02-20]

.........its not the wrong version. I have been on the same version since I first DL it...def would not venture into another carrier thread n DL anything :cool: not new to this but thanks for extending bro

LiquidSmooth/Illusion 4.2.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wally3614:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2att [2013-02-20]

LiquidSmooth/Illusion 4.2.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
Been running this for a few hours now. Really solid so far! Will be rocking this with LS when RC2 comes out. Starting to notice the lovely blue tint :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tunasty:
Damn! I think i need a full roll of toilet paper now lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
I was using fifo, I'm testing with row today
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Any other settings?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
I'm getting similar results with asswax/fifo. I believe it's fifo scheduler that's helping the most over row which was the scheduler I was using.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Try these asswax settings

Better battery

up_rate_us 20000

min_cpu_load 55

Better performance

max_cpu_load 80

min_cpu_load 35

awake_ideal_freq 810000
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
These are my modified 3.4 asswax settings based off the incredible 3.0 asswax battery life.

awake_ideal_freq 540000 (this controls how snappy it feels when you first wake the device. It can be lowered or raised depending on what you can tolerate)

down_rate_us 49000

max_cpu_load 85

min_cpu_load 70

ramp_down_step 192000

ramp_up_step 192000

sample_rate_jiffies 2 (only one I don't know what it means)

sleep_ideal_freq 192000

sleep_wakeup_freq 324000

up_rate_us 48000

This is based on using 192000 as my min. If you are using 324 as your min, increase sleep_ideal_freq and sleep_wakeup_freq 1 freq step each.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Sampling_rate_jiffies is the sampling rate (obviously not in the usually us) probably in respect to something... But I read through the code for asswax, and there's a comment saying its highly recommended to leave it at 2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tunasty:
These are my settings, just want to make sure I'm not messing up anything.

Are these emphasizing on performance or battery?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Probably emphasizing performance compared to stock, but not by a lot. Looks like a decent balance to me
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] voidstab:
Is fifo better to use than noop?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Should be pretty similar
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theadb:
Flashed back to Task's AOKP and 3.4 working flawless
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] awaisuk:
how do I change high speed freq on cm nightlys?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
Use a kernel tweaking app, such as TricksterMod.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Encerspay:
Just out of curiosity, how would one go about resetting any and all kernel settings to defaults?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tunasty:
Just flash the kernel again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] superstargoddess:
Every time I try to flash a 3.4 I can't boot. Tried it on Liquidsmooth the latest version, but I'm on the latest aokp version and haven't tried it on this yet.

I could swear in my kernel info it says that I'm running a 3.4 kernel. Afraid to try either of them again.

Sent from my SGH-I747 using Xparent Skyblue Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
That version of the ROM is slightly outdated. This kernel will support builds that were made after 4/19.

If you want to keep using that ROM but want this kernel you can use an older version here http://goo.gl/BMlRy. It won't have all of the newest updates though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] superstargoddess:
Just edited my post with the screen shot, was the same on liquidsmooth.

Like I said thigh, afraid to try it again on this Rom since it always failed on the other one.

Sent from my SGH-I747 using Xparent Skyblue Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
Also edited and should fix your problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I believe there were some important changes to 3.4 kernel since it got out and you would need to update your AOSP rom to be able to use it or vice versa. Someone might confirm this, but that could prevent it from working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
I just noticed that on boot my scaling_min_freq file reads 384000 (which isn't in scaling_available_frequencies), and it idles at 486000.

Has anyone else noticed this? Tried reflashing still seeing it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] superstargoddess:
I believe that the version of LiquidSmooth I was using it on was from 4/24. It did the same thing for it. I had to go in and use Odin to flash a new recovery since I couldn't get into mine then I just flashed this AOKP instead of LiquidSmooth again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
That's weird because the screen shot shows the build date for the ROM as 20130416.

I personally use AOKP over LS for various reasons so i'm not able to flash and test myself, was just going on what looked like reasons it wouldn't work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oddspec:
Yup that's y it won't boot even if its a 3.4 kernel all updated kernals now have cm display changes mergerd on 4/19/2013 so u need a build made after 4/19 for thus kernel to work on its current Version
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
right, which is why I linked to a build before those display commits were made.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Most likely the post boot file in your roms /system/etc setting the min.

Sent from my SCH-I535
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
That was it. Thanks for the response :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tunasty:
Hey Gid, any update coming? Last update was a BEAST!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
There's always something coming ;)

This week I'm back on the regular schedule for a sunday/monday release.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
I need you on the s4 Ed.

ATT S4 Rooted. Beastin.

4.2.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Lol ;)

Sent from my SCH-I535
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
3.4.y 2013-05-06 Build - http://www.droidhype.com/kernel/34/

- Merged latest CM updates, lots of it
- Revert "d2: Adjust MDP bandwidth parameters"
- cpufreq_interactive.c: hard code hispeed_freq to 810000, adjusted timer_slack
- Faux sound: updated to 1.1
- Dynamic fsync: updated and re-enabled. Forgot about this one from earlier troubleshooting. (credit to Faux123)
- Panel: color change built in (credit invisiblek and everyone involved)

sysfs interface located here: /sys/class/lcd/panel/panel_colors

Will accept 0-4 for parameters:
0 - Cold (more blues)
1 - Cool
2 - Normal (stock colors)
3 - Warm
4 - Hot (more reds)

BMS defaults to 0 (morfic's Trinity color set), but you can change and set these via your own scripting or go into CM advanced settings to change it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tunasty:
About to flash this baby! Thanks Gid! :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Flashing a baby is considered a crime in most parts of the world :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tunasty:
lmao but my BMS baby can handle everything ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
i chuckled at work. shhhh
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
They don't let you chuckle at work? That's serious.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
They just look at you weird when you do it out of the blue on your own. :silly:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
Try listening to comedic podcasts in your ear all day :)

"What's so funny?"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xxsashixx:
so many different governers now, whats the best for performance/battery ratio?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Int/row or int/fifo, hispeed_freq set to 810000.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xxsashixx:
Thanks for the fast response!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fortesquieu:
Hey Gideon,

Does the May 6 update have Trinity color?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Yup

It's set as default, but you can change it now via sysfs or thru cm advanced options.

Sent from my Nexus 7
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fortesquieu:
Ahhh I'm running Carbon Rom and Trinity isn't running. I guess I need to enable it somehow.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Using terminal emulator, enter the following:

echo 0 > /sys/class/lcd/panel/panel_colors

Then turn the display off and back on. That will set trinity colors for you.

If you want that permanent, throw it into a script under init.d to set it on boot. I have it set to that color set by default, but your rom may be overwriting it somehow.

Sent from my Nexus 7
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Yea my color setting defaults to 2 (morifc colors are 0) on boot
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Need to check on this a bit more, seems some are setting correctly, some aren't by default. You are correct, Trinity color is 0.

Sent from my Nexus 7
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CZ Eddie:
You might consider getting into the habit of reading release notes. :)

May 6th release notes (posted just above your post):
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
I wrote this in the d2tmo thread after someone brought up why my changelog's color mod was so similar to another dev's.

It seems a lot of people are confused where that color change mod comes from. It was put together by Invisiblek, who maintains part of the Cyanogenmod d2 code. Here is his commit for that option:

https://github.com/CyanogenMod/andr...mmit/41db8f4436b2c55bf9fe1932136e8cae3b04821f

If you notice, the instructions that Invisiblek wrote out is the same ones I had in my changelog which is why I gave him ample credit in my changelog.

Everyone who git pull'd from CM's source will have this commit. Chad isn't the only one

I hope that makes sense in why my changelog (and many other devs if you look around), have this very same set of instructions/commit around 5/5-5/6.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Link to commit broken, but yeah, people need to understand cherry picking.

Edit: Also for those interested, CM advanced settings to set LCD panel color don't seem to work on my end on cm10.1 5/5 for d2att. YMMV, but the GUI probably just is broken, use the sysfs interface.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
I suck at pasting. Corrected.

Sent from my SCH-I535
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
lol... that must make adding 10000 lines of code by hand a lot of fun!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
I know :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theadb:
BMS w/ interactive/fifo on the AOKP nightlies is phenomenal.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] galaxys3world:
black screen after flashing

i got a black screen after flashing this kernel on my att galaxy s3 running on aokp rom. I got this black screen rebooted my gs3 just after the installation. Any fixes.

-Thanks for any help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tunasty:
Make sure you download the right version. 3.0 or 3.4. Can't install 3.4 version on a 3.0 ROM or vise versa.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theadb:
Are you running the latest milestone? If so I had the same issue. Try going to the latest official nightly or use Task's rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] galaxys3world:
Is this the aokp kernel #??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oddspec:
Its work on all aosp ROMs and aokp is aosp
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] galaxys3world:
but why do i get a black screen after installation and reboot on aokp mr1 milestone 1?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
U need the 3.0 kernel, not 3.4
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oddspec:
Did u flash the 3.0 version I believe mr1 is still 3.0 kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] galaxys3world:
Are u sure because i did flash 3.4
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oddspec:
That would be y try the 3.0 version

Edit my bad its 3.4 kernel u need but u have to use a version before 4/19 becuz of massive display drivers changes in all 3.4 kernels and mr1 doesn't have these but any aokp nightly compiled after 4/19 will
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theadb:
This is what I was trying to say in much fewer (probably too few) words :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] galaxys3world:
cyanogenmod10.1

does this work for cyanogenmod10.1 m3?? cause i think im gonna flash this rom with the kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oddspec:
The latest kernel should cuz m3 was just released this week rite ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] galaxys3world:
Than would it be 3.0 or 3.4?

---------- Post added at 02:52 AM ---------- Previous post was at 02:44 AM ----------

so then would it be version 3.0 or 3.4??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oddspec:
ID check the ROMs change log or support thread It should be 3.4 if its releSe date is after 4/19
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
Why don't u just try both, or read instead of asking for people to hold your hand? What harm could be done by trying one, if that doesn't work, flash the other. You're cluttering this thread with **** a 2nd grader could comprehend.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
2013-05-09 BMS Display Color Boop-erizer - http://goo.gl/e4Qdj

This will be added to future kernel zips. For now, flash this one to get this script in your system.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Habs69M:
i need to change permission on the panel file on every reboot? any way around this? fix permission maybe?