THIS IS ONLY FOR THE USA VERSION OF THE GALAXY PLAYER 5.0 (YP-G70). If you have a mechanical home button instead of capacitive buttons at the bottom, do not flash this (rumirand has a kernel for you)! If you have a 4.0, do not flash this (SteveS has a kernel for you)!
Read the first three posts of this thread COMPLETELY before asking questions - if you ask a question that is answered in the first three posts, you WILL be flamed.
I'm continuing my Daily Driver name, even though it isn't as good of a name as it used to be. It is my daily driver - but what kernel dev doesn't use their own kernel as a daily driver? It made more sense in the Infuse days when I was running my own unreleased kernel for months and a few people asked for it. Oh well, I'm lazy - same name for now.
This is going to be maintained in the same manner and spirit as my other Daily Driver releases for the Samsung Infuse and Samsung SGH-I777 (AT&T Galaxy S II) - http://forum.xda-developers.com/show....php?t=1212795 and http://forum.xda-developers.com/show....php?t=1289460
It is built from sources at https://github.com/Entropy512/linux_kernel_galaxyplayer and initramfs at https://github.com/Entropy512/initramfs_yp-g70
- 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 - use SetCPU or a similar app to change it
- CIFS and Tunneling modules included
- ext4 partition mounting support in kernel and initramfs thanks to rumirand - ghetto Lagfix baby!
- CWM 220.127.116.11 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 below
- 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
Planned features, short-term:
- Pull a few other bugfix commits from my other kernels
- Clean up CWM implementation
Planned features, mid-term:
- Proper Voodoo Lagfix support (Automatic partition conversion instead of manual)
Planned features, long-term:
- Overclock beyond 1.2 if people prove they can handle 1.2 with maturity (Infuse community couldn't handle any OC in a responsible manner...)
Features not planned:
- Anything that has a high risk of trading off stability for performance, unless it can be completely disabled by default
- Alternative governors - They almost always cause wacky behavior in some cases, and they don't offer anything that can't be done with a combo of SetCPU profiles and tuning the conservative governor now that the minimum poll rate has been dropped.
How to flash .tar releases:
I forgot that Heimdall doesn't like this particular device - you will need to use a Windows virtual machine with USB passthrough support (like VirtualBox) and Odin, or root the device using the zergRush exploit and follow the "rooted device" instructions. (Ambrice has a fixed version of heimdall, but it must be compiled from source. If you know how to do that you don't need tips on how to use it. )
Enter download mode - Power off your device completely, hold VolDn, and insert the USB cable
Use Odin - Google it or search these forums for details - try AdamOutler's resurrector thread in this Development forum
Any rooted device:
Extract the zImage from the .tar file of the release. On Linux, it can be the following (which should work in an ADB or Terminal Emulator shell on the Player itself.)
tar xvf <releasefile>.tar
dd if=zImage of=/dev/block/mmcblk0p11
- Put it on your sdcard, enter CWM, flash the .zip using CWM
- If you do not have CWM, install an older .tar release then flash, or follow the "Any rooted device" instructions above, but extract the zImage from the .zip instead of a .tar