• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Kernel] [O/C] Testing

animania260

animania260

Android Enthusiast
About to upload and send a link to superboy4444 to test a 1.5 GHz, 1.6 GHz, and (for extreme users- not recommended for most) a max o/c 1.8 GHz kernel :-) This kernel is also optimized using 'make -o3' also (all compiler optimizations), seems to help performance a little and also memory usage (on boot at least).

I'm from the Galaxy Rush forum. Superboy4444 did a port of his ROM for us and I just built a working OC kernel for the Rush yesterday ( the Reverb has the same chip set ). Anyway superboy4444 asked me to do a kernel for you guys and I am glad to do so!!!

For now kernel is just O/C, but will soon have extra CPU governours, I/O scheulers, and patches (for built-in Apps2sd, Zram, and init.d support etc.)

Untill I get extra's added I'm going to let superboy4444 distribute the Reverb version, and also I can't get a flashable zip to work yet just for the kernel, but once I do I'll upload the kernels separately on this thread. Superboy4444 will release his ROM with the O/c kernel after we test soon.

Note: 1.8 Ghz is a bit extreme but is actually stable and did not even get hot on the Rush, though I don't recommend it for prolonged use, I'm just putting it out there because I had it running for a few hours with no problems. It will probably reduce the life of your phone a little bit though. 1.5-1.6 Ghz is probably the sweet spot for these chips (the first working O/C I flashed defaulted to the highest frequency availble in the frequency table.)

I am not a developer, you can just call me the middle man, downthemachine added the code for a ZTE phone with the same chip we have and I just merged his code with our source to compile this working kernel. Also without Shabbypengin (as always lol), who pointed me to the source and gave advice, this would not be possible.

Enjoy!
 
Well I think 1.8 Ghz wont be a problem because is is not that big of a jump. The Optimus elite comes at 1 Ghz and is easily clocked to 1.6 Ghz no problem. Im sure this phone has better parts that can withstand more o/c.
 
Yeah our Rush comes at 1 Ghz, and I was suprised to see 1.8Ghz run so stable but I ran it for a few hours no problems so, that's why I'm putting it out there.
I'm sending the kernel to superboy4444 now to test.
 
animania260 said:
Yeah our Rush comes at 1 Ghz, and I was suprised to see 1.8Ghz run so stable but I ran it for a few hours no problems so, that's why I'm putting out here.
I'm sending the kernel to superboy4444 now to test.
Click to expand...

O, the reverb comes at 1.4 Ghz. Does this mean VM o/c their phones?
 
Did you wipe dalvik before flashing this time?

I'm going to do a completely stock build and have you test just to make sure the kernel I'm building is bootable. Then if it works I'll redo the edits and it should work.

I'm surprised it boot looped though because there were no build errors. Thought for sure it was going to work.

Are you still up for testing ? We will just do 1.6 GHz to test. It won't brick your phone, but up to you though. I'd like to get you guys a better kernel.
 
animania260 said:
Did you wipe dalvik before flashing this time?

I'm going to do a completely stock build and have you test just to make sure the kernel I'm building is bootable. Then if it works I'll redo the edits and it should work.

I'm surprised it boot looped though because there were no build errors. Thought for sure it was going to work.

Are you still up for testing ? We will just do 1.6 GHz to test. It won't brick your phone, but up to you though. I'd like to get you guys a better kernel.
Click to expand...

I'm still down to test
 
Okay, I used this tool called 'meld' last night downthemachine pointed me to and it's a lot easier to merge the changes with that tool. It's basically a diff viewer/merger tool and it's pretty sweet.
So I'll re-do the merger's to your guys' kernel tonight, recompile and re-upload and we'll see how it goes.
 
uploadfromtaptalk1360929484438.jpg
Compilation issue
 
Working on another clean build tonight. Martiniz41613 verified a stock build I compiled so that's good, and I've gotten more familiar with the code and directory structure so hopefully this build will work for you guys. :-)

Stay posted.
 
Yeah I actually just realized the Galaxy Rush- board-name: prevail, Galaxy Reverb- board-name: Icon (and one other) are actually exactly the same. I could actually compile the kernel for my Rush and it should pretty much work on the Reverb, all the files needed for the kernel on the Reverb is uncluded in the source of the Rush kernel, and vice versa for the Reverb kernel. This is because these devices are almost identical and that's how samsung does things.. Make 3 different phones even though they are really the same thing but the Reverb has a bigger screen and etc.

Which is cool, I love choices but I think Samsung makes to many damn phones sometimtes.
Anyway just little info there. Compiling in a few minutes and will wait for testers to get back to me on status.

config SEC_MODEM_PREVAIL
bool "Prevail with msm8x55"
depends on SEC_MODEM
select LINK_DEVICE_DPRAM
select CDMA_MODEM_MSM8x55

config SEC_MODEM_ICON
bool "Icon with msm8x55"
depends on SEC_MODEM
select LINK_DEVICE_DPRAM
select CDMA_MODEM_MSM8x55

config SEC_MODEM_VITAL2REFRESH
bool "Vital_refresh with msm8x55"
depends on SEC_MODEM
select LINK_DEVICE_DPRAM
select CDMA_MODEM_MSM8x55
 
I'm working on it. Thread will be up in a minute.
I don't know the partitions on the Reverb so I can't make a flashable zip..
 
Okay, somebody test this for me and let me know if it works.
Flash it in CWM, it won't mess anything up, it will either work it won't. Please let me know.

Make SURE you clear Dalvik cache in CWM before flashing or it may not boot or work properly.

CWM OCKernel1-sph_m950-test.zip
 
You must log in or register to reply here.
Back
Top Bottom