[KERNEL][5.0 USA][CWM/1.2GHZ] The EXODUS Kernel - R1 - Samsung Galaxy Player 4.0, 5.0

I introduce to you
The EXODUS Kernel
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This kernel is ONLY for the USA version of the Samsung Galaxy Player 5.0 (YP-G70).
PLEASE read everything before flashing.
First off, this kernel based off of Entropy512’s Daily Driver kernel sources.
Many thanks to him for his sources and work in developing his kernel.
Entropy512's Daily Driver
I’ve picked up on development and have added, tweaked and removed a bunch of features. My ultimate goal is to make a much more comprehensive gingerbread kernel for this device. ​
Current features so far –
All from Entropy’s 3/5/12 build (see below)
Swap is ENABLED (see release notes)
Loads of new governors (see below for description)
Added Smartassv2, Interactive, InteractiveX, lulzactive
Added SIO (Simple I/O) Scheduler
Removed Userspace governor – nobody ever uses it.
Ondemand is the new default governor
Lowered minimum allowable screen brightness from 30 PWM to 20 PWM
Updated LZO compression
Patched ondemand governor to make it less jumpy (may have prevented ondemand from going into deep sleep, will look into this further)
Tweaked SmartassV2 governor – set 1Ghz as “Ideal” frequency
1.2 Ghz overclock will be included
Features in the works –
V(R), BFQ schedulers
Ramzswap or something similar
Testing 1.33ghz overclock
Look at updating CWM
Look into using scripts to change governor settings
Features included from Entropy’s Daily Driver –
• coolbho3k's Samsung Sleep of Death patch - allows stable use of screen-off profiles with limits below 800 MHz in SetCPU
• netarchy's conservative governor tuning patch - Reduces the polling interval, allowing conservative to ramp up/down faster. Over in I9100 land they're calling this "lionheart" and it's all the rage. (It makes me sad when people won't accept a governor until it's renamed and hyped up way beyond what it is...) As an example, a GSII would take 0.4 seconds to ramp from 200 to 1200 MHz with the default conservative governor, it can go all the way in 0.1 second with this patch.
• conservative set to default governor - CHANGED
• jhash3
• TinyRCU
• CIFS and Tunneling modules included
• ext4 partition mounting support in kernel and initramfs thanks to rumirand - ghetto Lagfix baby!
• CWM 5.0.2.7 based recovery - Mostly tested, seems working, but may have a few bugs still to work out, rumirand helped a lot on this one
• Insecure kernel - gives you automatic root in ADB shells
• Per-file fsync() disable capability - see "dangerous features" documentation on Entropy’s page
• Standard bootanimation (/system/media/bootanimation.zip) support
• Charginghacks - faster charging at low battery, slightly slower near the end, overall faster charging while trying to minimize battery stress
• CPU core voltage control - use SetCPU or a similar app
• CPU overclock to 1.2 GHz - use SetCPU or a similar app
Feature Explanations -
SmartassV2 –
Version 2 of the original smartass governor from Erasmux. Another favorite for many a people. The governor aim for an "ideal frequency", and ramp up more aggressively towards this freq and less aggressive after. It uses different ideal frequencies for screen on and screen off, namely awake_ideal_freq and sleep_ideal_freq. This governor scales down CPU very fast (to hit sleep_ideal_freq soon) while screen is off and scales up rapidly to awake_ideal_freq (500 mhz for GS2 by default) when screen is on. There's no upper limit for frequency while screen is off (unlike Smartass). So the entire frequency range is available for the governor to use during screen-on and screen-off state. The motto of this governor is a balance between performance and battery.
Kernel is currently set to use 1.0ghz as the ideal frequency, and BLANK for sleep frequency. I also tweaked it to ramp up/down in 100mhz steps. I’m currently still testing these settings, so they may change as needed.
Taken from - http://forum.xda-developers.com/showthread.php?t=1663809
Click to expand...
Click to collapse
Interactive –
Much like the OnDemand governor, the Interactive governor dynamically scales CPU clockspeed in response to the workload placed on the CPU by the user. This is where the similarities end. Interactive is significantly more responsive than OnDemand, because it's faster at scaling to maximum frequency.
Unlike OnDemand, which you'll recall scales clockspeed in the context of a work queue, Interactive scales the clockspeed over the course of a timer set arbitrarily by the kernel developer. In other words, if an application demands a ramp to maximum clockspeed (by placing 100% load on the CPU), a user can execute another task before the governor starts reducing CPU frequency. This can eliminate the frequency bouncing discussed in the OnDemand section. Because of this timer, Interactive is also better prepared to utilize intermediate clockspeeds that fall between the minimum and maximum CPU frequencies. This is another pro-battery life benefit of Interactive.
However, because Interactive is permitted to spend more time at maximum frequency than OnDemand (for device performance reasons), the battery-saving benefits discussed above are effectively negated. Long story short, Interactive offers better performance than OnDemand (some say the best performance of any governor) and negligibly different battery life.
Interactive also makes the assumption that a user turning the screen on will shortly be followed by the user interacting with some application on their device. Because of this, screen on triggers a ramp to maximum clockspeed, followed by the timer behavior described above.
Taken from - http://forum.xda-developers.com/showthread.php?t=1663809
Click to expand...
Click to collapse
InteractiveX –
Created by kernel developer "Imoseyon," the InteractiveX governor is based heavily on the Interactive governor, enhanced with tuned timer parameters to better balance battery vs. performance. The InteractiveX governor's defining feature, however, is that it locks the CPU frequency to the user's lowest defined speed when the screen is off.
Taken from - http://forum.xda-developers.com/showthread.php?t=1663809
Click to expand...
Click to collapse
Lulzactive –
Basically interactive governor with added smartass bits and variable (as opposed to fixed amout) frequency scaling, based on currently occuring cpu loads. Has, like smartass, a sleep profile built-in. See link for details on exact scaling.
Lulzactive also has a control app provided by tegrak which is free to download on the market.
See link - https://market.android.com/details?id=com.tegrak.lulzactive
Taken from - http://forum.xda-developers.com/showthread.php?t=1663809
Click to expand...
Click to collapse
Release Notes –
R1- Initial release
Issues - ondemand governor causes device to reboot on sleep. Change the governor and theres no issue. Already fixed for next release.
Kernel seems mostly stable, a few small issues. Please confirm DEEP SLEEP is working on the new governors with your device using cpuspy or something similar. I've been having recovery loop issues on my device over the past few days so I haven't been able to test it 110%.
Governors and schedulers can be changed with SETCPU or a similar app.
Swap is now supported. You can enable swapfiles by using swapper2 or ramexpander. Please use a swapfile and do not make a swap partition unless you know what you're doing. Swap WILL put more wear on wherever you decide to put your swapfile due to increased read/write. I personally don’t think this is a problem, even using a swapfile every day for years you’ll be moving on to a new device long before you wear down the flash memory to the point of failure. If you have an issue with that, don’t enable it. I’ve been using my device with a 128mb swapfile, swappiness at 60-80 and minfrees of 6,8,16,24,32,48 (pretty mild). By taking advantage of the swap you can allow android to keep more programs running and improve multitasking. Also note that putting your swap partition on a slow SD card will slow the system down.
If people are having positive reactions to the swap, I’ll considering making it a more integrated part of the kernel.
Backlight is now supported to go down to 20PWM (which is the level it dims to when below 5% battery). Not too important , but good for people like myself who like watching movies in the dark.
InteractiveX doesn’t seem too responsive, but might work well for people concerned with battery life. It may or may not stay in the build ultimately.
This build DOES have mild overclocking enabled, I WILL NOT be held responsible for any damages it may cause. Chances are very, very slim, but just a disclaimer.
Feedback is very welcomed. If there are any other features or issues you’d like to see dealt with, please post!
FLASHING --
EXODUS R1 is CWM flashable. It can be flashed on top of Entropy's DD Kernel with no problem.
If you don't have Entropy's kernel you can either download it and upgrade to EXODUS, or download the EXODUS file, extract the zImage and flash with heimdall using
Code:
heimdall flash --kernel "C:\path\to\kernel"
Your device must be in download mode for this method (vol down+power), and the SGP5 is only supported on the most recent version of heimdall.
Download the file and place it on your external SD card (/external-sd/).
Power off your device and hold volume up + power (at the same time) to enter CWM.
Select install zip from SD card => choose zip from SD card => EXODUS_Rx.zip => yes
CWM ZIP HAS BEEN PULLED DOWN WHILE I WORK OUT A BUG,
PLEASE USE THE HEIMDALL IMAGE.
CWM zip will be back as soon as the problem is remedied.
And of course, my GIT and sources are located HERE

---

exodus454 said:
I introduce to you
The EXODUS Kernel
This kernel is ONLY for the USA version of the Samsung Galaxy Player 5.0 (YP-G70).
PLEASE read everything before flashing.
First off, this kernel based off of Entropy512’s Daily Driver kernel sources.
Many thanks to him for his sources and work in developing his kernel.
Entropy512's Daily Driver
I’ve picked up on development and have added, tweaked and removed a bunch of features. My ultimate goal is to make a much more comprehensive gingerbread kernel for this device. ​
Current features so far –
All from Entropy’s 3/5/12 build (see below)
Swap is ENABLED (see release notes)
Loads of new governors (see below for description)
Added Smartassv2, Interactive, InteractiveX, lulzactive
Added SIO (Simple I/O) Scheduler
Removed Userspace governor – nobody ever uses it.
Ondemand is the new default governor
Lowered minimum allowable screen brightness from 30 PWM to 20 PWM
Updated LZO compression
Patched ondemand governor to make it less jumpy (may have prevented ondemand from going into deep sleep, will look into this further)
Tweaked SmartassV2 governor – set 1Ghz as “Ideal” frequency
1.2 Ghz overclock will be included
Features in the works –
V(R), BFQ schedulers
Ramzswap or something similar
Testing 1.33ghz overclock
Look at updating CWM
Look into using scripts to change governor settings
Features included from Entropy’s Daily Driver –
• coolbho3k's Samsung Sleep of Death patch - allows stable use of screen-off profiles with limits below 800 MHz in SetCPU
• netarchy's conservative governor tuning patch - Reduces the polling interval, allowing conservative to ramp up/down faster. Over in I9100 land they're calling this "lionheart" and it's all the rage. (It makes me sad when people won't accept a governor until it's renamed and hyped up way beyond what it is...) As an example, a GSII would take 0.4 seconds to ramp from 200 to 1200 MHz with the default conservative governor, it can go all the way in 0.1 second with this patch.
• conservative set to default governor - CHANGED
• jhash3
• TinyRCU
• CIFS and Tunneling modules included
• ext4 partition mounting support in kernel and initramfs thanks to rumirand - ghetto Lagfix baby!
• CWM 5.0.2.7 based recovery - Mostly tested, seems working, but may have a few bugs still to work out, rumirand helped a lot on this one
• Insecure kernel - gives you automatic root in ADB shells
• Per-file fsync() disable capability - see "dangerous features" documentation on Entropy’s page
• Standard bootanimation (/system/media/bootanimation.zip) support
• Charginghacks - faster charging at low battery, slightly slower near the end, overall faster charging while trying to minimize battery stress
• CPU core voltage control - use SetCPU or a similar app
• CPU overclock to 1.2 GHz - use SetCPU or a similar app
Feature Explanations -
Release Notes –
R1- Initial release
Kernel seems mostly stable, a few small issues. Please confirm DEEP SLEEP is working on the new governors with your device using cpuspy or something similar. I've been having recovery loop issues on my device over the past few days so I haven't been able to test it 110%.
Governors and schedulers can be changed with SETCPU or a similar app.
Swap is now supported. You can enable swapfiles by using swapper2 or ramexpander. Please use a swapfile and do not make a swap partition unless you know what you're doing. Swap WILL put more wear on wherever you decide to put your swapfile due to increased read/write. I personally don’t think this is a problem, even using a swapfile every day for years you’ll be moving on to a new device long before you wear down the flash memory to the point of failure. If you have an issue with that, don’t enable it. I’ve been using my device with a 128mb swapfile, swappiness at 60-80 and minfrees of 6,8,16,24,32,48 (pretty mild). By taking advantage of the swap you can allow android to keep more programs running and improve multitasking. Also note that putting your swap partition on a slow SD card will slow the system down.
If people are having positive reactions to the swap, I’ll considering making it a more integrated part of the kernel.
Backlight is now supported to go down to 20PWM (which is the level it dims to when below 5% battery). Not too important , but good for people like myself who like watching movies in the dark.
InteractiveX doesn’t seem too responsive, but might work well for people concerned with battery life. It may or may not stay in the build ultimately.
This build DOES have mild overclocking enabled, I WILL NOT be held responsible for any damages it may cause. Chances are very, very slim, but just a disclaimer.
Feedback is very welcomed. If there are any other features or issues you’d like to see dealt with, please post!
FLASHING --
EXODUS R1 is CWM flashable. It can be flashed on top of Entropy's DD Kernel with no problem.
If you don't have Entropy's kernel you can either download it and upgrade to EXODUS, or download the EXODUS file, extract the zImage and flash with heimdall using
Code:
heimdall flash --kernel "C:\path\to\kernel"
Your device must be in download mode for this method (vol down+power), and the SGP5 is only supported on the most recent version of heimdall.
Download the file and place it on your external SD card (/external-sd/).
Power off your device and hold volume up + power (at the same time) to enter CWM.
Select install zip from SD card => choose zip from SD card => EXODUS_Rx.zip => yes
And of course, my GIT and sources are located HERE
Click to expand...
Click to collapse
I have tried to flash it, but i get recovery boot loops

---

cleve321 said:
I have tried to flash it, but i get recovery boot loops
Click to expand...
Click to collapse
Really? That's strange. Do you have a backup you can restore?
I'm pulling the CWM flashable zip until I can sort that out, heimdall zImage will be in it's place. Try restoring if you have a backup and reflashing with heimdall.
Heimdall is available here - http://www.glassechidna.com.au/products/heimdall/

---

exodus454 said:
Really? That's strange. Do you have a backup you can restore?
I'm pulling the CWM flashable zip until I can sort that out, heimdall zImage will be in it's place. Try restoring if you have a backup and reflashing with heimdall.
Heimdall is available here - http://www.glassechidna.com.au/products/heimdall/
Click to expand...
Click to collapse
Hmmm nevermind, I flashed the kernal, then a rom and now it boots

---

Not trying to be rude or anything, but you should try working on a 3.x kernel. Just saying
Sent from my YP-G70 using xda app-developers app

---

EcHoFiiVe said:
Not trying to be rude or anything, but you should try working on a 3.x kernel. Just saying
Sent from my YP-G70 using xda app-developers app
Click to expand...
Click to collapse
I absolutely will once it's out of super-alpha, I was working on this before any of the recent breakthroughs with it.

---

Wow that does look pretty nice.

---

CRAP, I soft bricked the GP5.0 when I tried to flash the kernel with Heimdall.
I used WinXP PC to flash. Put GP5.0 into Download Mode and hooked up USB. Heimdall detected device ("heimdall detect" command). I typed in the commands and flashing started - then it gave several "error -9" then stopped.
When I unplugged and replugged the device, it was no longer detected. When I pressed the POWER button to switch it off from Download Mode, it restarted with the dreaded "Phone - Yellow triangle - PC" icon. Cannot get into anything (no recovery, no Download Mode). Cannot even switch it off (POWER button -> screen goes black for a while then comes back on with that icon).
Thank goodness I bought the USB jig (their website said it was tested with the GP5.0). The guide said you have to take the battery out first but you cannot do this on the GP5.0. I just emailed the seller / builder of the jig for advice. I hope this USB jib gets me out of trouble!

---

it is still in download mode except this time it is forced mode so just flash a new kernel through odin and you should be fine

---

slim_thumb said:
CRAP, I soft bricked the GP5.0 when I tried to flash the kernel with Heimdall.
I used WinXP PC to flash. Put GP5.0 into Download Mode and hooked up USB. Heimdall detected device ("heimdall detect" command). I typed in the commands and flashing started - then it gave several "error -9" then stopped.
When I unplugged and replugged the device, it was no longer detected. When I pressed the POWER button to switch it off from Download Mode, it restarted with the dreaded "Phone - Yellow triangle - PC" icon. Cannot get into anything (no recovery, no Download Mode). Cannot even switch it off (POWER button -> screen goes black for a while then comes back on with that icon).
Thank goodness I bought the USB jig (their website said it was tested with the GP5.0). The guide said you have to take the battery out first but you cannot do this on the GP5.0. I just emailed the seller / builder of the jig for advice. I hope this USB jib gets me out of trouble!
Click to expand...
Click to collapse
Relax! You don't need a jig to fix it. It just means the flash got screwed up and you need to reflash it so it can boot normally. That yellow triangle screen IS download mode.
If you're flashing with heimdall, make sure you plug your device in while its in download mode, then go to the "drivers" folder in the heimdall directory and run the program. You should see 'samsung usb composite device' listed in the dropdown. Replace that driver with the WinUsb driver and then flash away. If you still get USB errors, check your cable and try changing USB ports. Once you reflash it should work again.
Sent from my GT-I9000 using xda app-developers app

---

Been waiting for a kernel w/ alternate gov.s and swap enabled. Thanks a bunch!
btw, just flashed using the meta.inf from Entropy's zip file. worked like a charm.

---

exodus454 said:
Relax! You don't need a jig to fix it. It just means the flash got screwed up and you need to reflash it so it can boot normally. That yellow triangle screen IS download mode.
If you're flashing with heimdall, make sure you plug your device in while its in download mode, then go to the "drivers" folder in the heimdall directory and run the program. You should see 'samsung usb composite device' listed in the dropdown. Replace that driver with the WinUsb driver and then flash away. If you still get USB errors, check your cable and try changing USB ports. Once you reflash it should work again.
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
I have used Heimdall twice before without problem. I said Heimdall ran but it gave error message ("error -9" - can't find anything on google)
It is not the large "Yellow triangle" icon with the Android robot and says "Downloading now". It is the "Phone - yellow triangle - PC" icon = no Download Mode, no recovery, cannot switch off device, PC does not detect the device, Heidmall does not detect the device. IT IS FROZEN with this icon.
See the attachment picture for the "phone - yellow triangle - PC" icon
Believe me, I've done stupid things and I have seen this "Phone - yellow triangle - PC" icon before - it means soft brick (ie nothing works except the screen is still on). I had to take it to an Android phone repair guy to get it back to Download Mode. This was the reason I bought the USB jig in case I did something stupid again.

---

ok. possible bug- (or it's just me)
the device consistently reboots instead of going to sleep/idling. have attached logcat during one of these incidents.

---

With the "Phone - yellow triangle - PC" icon, I tried Power + Volume Down buttons again then hook up the USB cable. The usual Download Mode screen never showed but the PC detected the device (Device Manager showed "Gadget serial" under "USB controller".
Heimdall also detected the device and I successfully flashed the custom kernel - unfortunately when the device rebooted, it was stuck at the "Samsung" screen (not a bootloop). I reinstalled the OEM firmware kernel for now. I'll try again tomorrow because the battery is nearly all drained.

---

alljokingaside said:
ok. possible bug- (or it's just me)
the device consistently reboots instead of going to sleep/idling. have attached logcat during one of these incidents.
Click to expand...
Click to collapse
Thanks, I'm aware. Just gotta fix it. If you switch governors the problem should go away. Ill have a fix soon.
sent from my sgp5 using xda

---

You have done exacly what I wanted
good job, gonna try to make own kernel anyway

---

BTW Exodus
Did you fix the random freezing problem of Entropy's original kernel that both you and me have experienced?
I'll try to reflash this kernel tonight.

---

slim_thumb said:
BTW Exodus
Did you fix the random freezing problem of Entropy's original kernel that both you and me have experienced?
I'll try to reflash this kernel tonight.
Click to expand...
Click to collapse
I'm working on it. Theres a bunch of compiler warnings related to the video driver when building. I'm trying to chase those down. It could have something to do with how the overclock is patched in too.
On an unrelated note, is anyone else having usb mount issues?
Edit- testing a build from late last night with video drivers from another source, lagging and stuttering is nonexistant so far. My usb mounting still isnt working though on ubuntu or windows and I can't figure out if it's my device or the kernel. All the usb modules seem to be in order.
Once I get this figured out I can release the next version with a few new things.
Sent from my sgp5 using xda app-developers app

---

Is there any other OC programs that you dont have to pay for? Im using No Frills and it works great without the overclocking support. Im gonna flash it rite now.
Update:
Maybe not........ Love the features youve installed on this kernal

---

nightfire37 said:
Is there any other OC programs that you dont have to pay for? Im using No Frills and it works great without the overclocking support. Im gonna flash it rite now.
Update:
Maybe not........ Love the features youve installed on this kernal
Click to expand...
Click to collapse
Tegrak overclock works up to 1.3ghz for free
Sent from my GT-I9000 using xda app-developers app