- Default kernel based on TheOC kernel with overclocking/undervolting options (61 Mhz - 2 Ghz). (Beware of OC risks, it's not overclocked unless you intentionally change settings)
- Improved UI response without giving up battery life by switching to Interactive governor & SIO scheduler as default (I DO NOT recommend changing these).
- Rewrote touchscreen driver for smoother & more accurate response
- Updated Adreno 205 graphics drivers (12 -> 24 FPS in Nenamark2)
- Fixed wifi & sensor event wakelocks for better battery life.
- Intentional BT wake_lock added for reliable Bluetooth when enabled.
- BT & Wifi can now be enabled together without 100% CPU usage.
- Wifi connects to hidden SSIDs also & scans faster.
- Improved camcorder video (h264@4/2/0.5 Mbps) & audio (AAC 64kbps @ 44khz) encoding & auto-focusing.
- Improved light sensor readings for auto-backlight tuning in CM settings.
- Fixed sluggish accelerometer bug after long uptime since reboot.
- Extended time for "hold back button to kill app" to 3 seconds to prevent accidental kills.
- Restored default Android lowmemkiller settings for better multitasking apps (Can still be changed in /etc/init.d/99memory)
- Disabled DEBUG mode & HDMI service startup since it's not working anyway
- ICS Roboto font default instead of DroidSans
Updates from CyanogenMod 7.2 Gingerbread 2.3.7:
- T9 predictive search for contacts in phone dialpad
- Customizable carrier label on lockscreen
- ICS Ring (+blade) lock, rotation & transition animations
- Bluetooth external GPS dongle support
- Many other minor fixes & updates such as correct EXIF camera date, options to disable bootup animation, scrolling cache , BT quickconnect, lock volume keys in quiet mode.
Known Problems (everything else works):
- HDMI does not work (Keep a Froyo backup if need to use it occasionally)
- BT or WiFi enabled will prevent deep sleep mode, this is a required hack on custom ROMs (Use built-in Notification bar widget to quickly toggle)
- Some videos in portrait mode flickers. (Enable CM settings 180 orientation & flip upside down)
- Volume sometimes low (pausing or restarting audio sometimes helps)
This ROM is STABLE and has very good battery life when BT & Wifi are off (less than 1%/hr idle when no apps or services are transferring background data). If you encounter any issues, make a NANDroid backup in recovery (DO NOT use the Titanium Backup App, which can cause more problems), then factory-reset & reflash the ROM, try to reproduce the problem BEFORE installing/restoring any Apps. Most problems are due to apps & user settings.
Download Final Build 2012-03-25
md5sum checksum: e2fa38f568af393c525cede9f6eaf025
(I recommend PC download & USB cable transfer onto phone's sdcard for reliability)
Installation:
Follow these simple instructions if you've never flashed a ROM on the MT. If upgrading from a previous CM7, need to wipe cache & advanced -> dalvik-cache in recovery mode (it keeps user data). Also wipe BOTH caches if you experience problems. Android Market/Play is not included for legal reasons, you MUST flash gapps.zip RIGHT AFTER flashing this ROM zip for the first time before rebooting, gtalk.zip (Google Talk) is optional. After booting into the ROM, you may remove some of the bloatware, see this thread.
Special thanks to these people for financial donations: alisonc, Ben F, Brad Z, Brian C, Claude R, Chi Sung R, Chris H, David E, Deconstructed, dsmryder, eapinto, Eddy C, Jahaziel S, Jay G, Joey M, John C, John D, John K, JohnnyRocket, Jon E, Josh B, Josh H, Kannon Y, Kevin M, klehman215, linearB, Luther P, marc12868, Matthew H, MediocreBadguy, Nicholas M, OverByter, PatrickD88, pillbug, Robert M, Sam H, sharp351, soundping, Susan B, thangfish, Tim S, Volker N, xploPR, Zach B
Includes WhyKernel 03-25:
- Enabled INPUT_GPIO in kernel config again to fix proximity sensor glitches.
Other:
- Reverted to original libaudioalsa.so and liba2dp blobs to be safe & since there were no noticeable audio improvements in last build.
- Default to 'dim' auto-brightness profile values by aricblunk
Updates from Cyanogenmod 7:
- Fixed EXIF data writing for camera
- Fixed soft keyboard appearing on dialer sometimes
- Show PIN entry even if lockscreen is disabled
- Backported "disappearing SD media" fixes from CM9
- Fixed ext4 image generation when size is exact multiple of block size
- Fix cursor repeatedly moving back to beginning of To field in MMS app
- Battery status can be shown in PatternUnlockScreen also
- Added Max SMS length option
- ADWLauncher: Added option to lock Action Buttons in main dock
Includes WhyKernel 03-04:
- Updated KGSL Adreno 205 graphics drivers (12 -> 24 FPS in Nenamark2)
- Ported genlock feature, needed by newer GPU drivers
- Added ZRAM kernel support
- More battery efficient LED notification blinks
Other:
- Using newer audio & Adreno 205 driver blobs from non-MT FB0 devices on xda-forums
- Added 250 ms delay to prevent accidentally swiping from screen to capacitive buttons
- Reverted to older wifi.c in libhardware_legacy
Updates from Cyanogenmod 7:
- Updated File Manager app that's included
- View contact by long press on dialpad T9 results
- More efficient memcpy & strlen low-level functions
- Other minor fixes & improvements.
WhyKernel 02-29:
- Enabled AES & SHA256 encryption support for apps that need it.
- Disabled INPUT_GPIO to get rid of unnecessary interrupt servicing.
- Touchscreen should work with other FB0 devices again.
- Fixed proximity sensor not turning screen back on during calls
Updates from Cyanogenmod 7:
- Landscape layouts for in-call screen
- Fixed screen hang after dismissing a landscape alarm
WhyKernel 02-18:
- Fixed occasional "event" wakelocks due to 2+ sensors active at the same time
- More touchscreen optimizations, correct button layout for other FB0 devices
- Fixed broken video from 02-16 build
Other Changes
- Using same sensors & graphics blobs as CM9.
- Added /system/usr/bi041p.idc file for touchscreen calibrations
Updates from Cyanogenmod 7:
- "CM Settings - Input" now doesn't force close (only in last build)
- Fixed side swiping notifications freezes (again)
- Fixed freeze after rotating screen when off
- Fixed stock gallery app improper image scaling
- Improved scrolling cache
- Fixed music widget transparency in landscape mode
Build 2012-02-02
(CM Settings - Input Force Closes in this build. It should keep settings from prev versions)
Kernel Changes:
- Proper fix for the leftover Wifi & BT wakelocks problem
- Improved MMC/SDIO stability
Updates from Cyanogenmod 7:
- 'Blade' Ring Lockscreen style option available
- Option to disable scrolling cache in performance settings
- ADB over wireless feature built-in (missing 'adbd' on the MT)
- Fixed FC on boot when lockscreen disabled
- Fixed lockscreen alignment
Updates from Cyanogenmod 7:
- Fixed status bar swipe race (freezing) condition
- Customizable Carrier Label in Settings
- Bluetooth quickconnect option
- ICS rotation & transition animations.
- Option to lock volume keys in silent mode.
- Automatically restart ADB if TCP port settings change.
- Other minor fixes.
Kernel changes:
- Touchscreen interrupts have dedicated workqueues now for faster processing. Removed firmware update & other non-functional code.
- Disabled Smartass & SavagedZen CPU governors. They were causing extra early_suspend processing, there are better governors available still.
Other changes:
- Bluetooth & Wifi can be enabled at the same time without 100% CPU utilization.
Kernel changes:
- Default to Interactive governor & SIO scheduler (similar performance as Noop, but will give priority to UI interruptions)
- Light sensor will now report 1, 31, 61, 91, 121... values to improve average calculations for auto-backlight
- Intentional wake_lock for when Bluetooth is powered on.
- Disabled more debugging messages (cleanup devs!)
Other changes:
- Enabled AAC audio codec, videos will sound much clearer now. Also disabled continuous auto-focus hunting when recording (these small lenses have huge depth of field anyway)
- Disabled gps.conf intermediate position reporting that gave false locations until locked (problem introduced in last build)
- Updated gps.conf some more, not sure if this makes much of a difference on the MT.
- Reduced hold_back_to_kill delay to 3 seconds for those impatient serial-killas out there.
- Put RomManager back to try not to break anything, it can be removed after first boot up.
Updates from Cyanogenmod 7:
- NEW Ringlock Feature
- NEW Bluetooth GPS dongle support
- Disable Bootup animation now works
- Other minor updates such as TLS-Auth for OpenVPN & call waiting tweak.
Kernel changes:
- Reverted back to the stock touchscreen driver code (used in TG's B.08 ROM) with my rewrite & optimization of isr_workqueue function. Should be more reliable and smoother.
- New fix for MMC wake-lock that prevents deep sleep when screen is off.
- Disabled debug mode/msgs in kernel.
Other changes:
- Disabled more debugging modes in DalvikVM, GPS, & kernel. Leaner & faster ROM overall.
- Using gps.conf QUICKEST FIX V1.3 By RJLM, not sure if aGPS even works on the MT according to TG, but this won't hurt anything if it doesn't.
Kernel changes:
- Based on TheOC v1.6.14 (changelog)
Other changes:
- Fix for sluggish accelerometer.
- Extended time for "hold back button to kill app" to 4 seconds to prevent accidental kills
- Disabled DEBUG mode & most messages.
- Removed RomManager.apk from package
Cyanogen changes:
- Dialpad: perform search when retrieving last dialed number
Kernel changes:
- Kernel based on TheOC Kernel v1.6.11 (changelog)
** Using original interactive governor algorithm with 20ms intervals & 95% threshold.
** Disabled some intermediate frequencies 184, 368, 652, 806, 921 Mhz, simplifies CPU scaling, Still have 61, 122, 245, 460, 576, 768, 1024, & the rest of OC)
** Disabled proximity sensor debug msgs.
- My experimental kernel fix for the occasional "can't go into deep sleep mode until reboot" bug. This should improve battery life.
- Interactive governor default instead of ondemand
Glad to see someone else in development I'm gonna install this once I get off work also is this with the default oddball version kernel of ocv1. 5 or not?
Hey Whyzor, cool that you decided to pick this up. Is it possible for you to use PARTIAL_WAKE_LOCK when bluetooth is connected (like I think TG did for wifi) to keep BT from disconnecting when the device goes to sleep. This appears to be the a solution.
Thanks. I'm gonna check this out tomorrow.
Glad to see someone else in development I'm gonna install this once I get off work also is this with the default oddball version kernel of ocv1. 5 or not?
Not sure what you mean by oddball, I've been using v1.5 for a while now and it's pretty stable.
Quote:
Originally Posted by thangfish
Hey Whyzor, cool that you decided to pick this up. Is it possible for you to use PARTIAL_WAKE_LOCK when bluetooth is connected (like I think TG did for wifi) to keep BT from disconnecting when the device goes to sleep. This appears to be the a solution.
Thanks. I'm gonna check this out tomorrow.
I dont' want to over-promise anything, but will look into it. In the meantime keep on using the tasker app as a workaround
Device(s): HTC One S (CM10),
Kindle Fire (CM10-SGT7)
Carrier: T-Mobile USA
Thanks: 3,844
Thanked 5,034 Times in 2,658 Posts
Quote:
Originally Posted by Whyzor
Not sure what you mean by oddball, I've been using v1.5 for a while now and it's pretty stable.
In the first overclockable kernel made for the stock ROM (Umph kernel), the dev had to make a bit of a workaround for certain Triumphs. He labeled it oddball, hence the question. It was really just the difference of setting the default clock speeds for the "oddball phones".
In the first overclockable kernel made for the stock ROM (Umph kernel), the dev had to make a bit of a workaround for certain Triumphs. He labeled it oddball, hence the question. It was really just the difference of setting the default clock speeds for the "oddball phones".
I see, the defaults are not overclocked (running 245-1024 Mhz) and not undervolted, so it's running within OEM specs. Just gives the option to change those in CM settings or with an app like IncrediControl.
Awesome! I already have been using the Roboto font with the help of XDA forum and Font Changer app. It's nice to have it built into the ROM now.
Also, kudos for the disabling of HDMI on startup and the ability to disable boot animation.
So, does this mean we can actually undervolt below 800mv now?
awesome!... Whyzor would u provide more details on the new governors?
I didn't notice any new governors mentioned. Only the tweaking of the Interactive governor for potential battery life savings
Correct me if I'm wrong?
EDIT: Other than the new governors in the TheOC Kernel when compared to governors in Tickerguy's CM7
Last edited by TheBritton; December 23rd, 2011 at 11:33 PM.
Reason: EDIT: Other than the new governors in the TheOC Kernel when compared to governors in Tickerguy's CM7
The Following User Says Thank You to TheBritton For This Useful Post:
So, does this mean we can actually undervolt below 800mv now?
There's still no way to verify, but with my changes I can set it to 500 mV as minimum and it's still fine 122-1024 Mhz.
Quote:
Originally Posted by britton1981
Is there a way to restore the standard CM7 launcher to replace ADW?
ADW launcher comes default with CM7, If you google 'Launcher2.apk' and install it like a regular app (in /data partition), then clear the app cache settings to use the launcher2 by default, it should stick even when flashing newer CM7 builds in the future. That's how I'm doing it with Zeam launcher.
Sweet. This is pretty much what I'm using now but it's all built-in, so instead of flashing 3 zips I can now just flash 1. I'm assuming you'll be incorporating TheOC updates as they're released?
Glad to see another developer step in and help fill the void left by TG and Isaac.
Thanks. New at this, just rooted Triumph, installed this ROM. Have a few growing pains. Like contacts and stuff, but wow on the function of this build.
The Following User Says Thank You to wokeupdead For This Useful Post:
There's still no way to verify, but with my changes I can set it to 500 mV as minimum and it's still fine 122-1024 Mhz.
ADW launcher comes default with CM7, If you google 'Launcher2.apk' and install it like a regular app (in /data partition), then clear the app cache settings to use the launcher2 by default, it should stick even when flashing newer CM7 builds in the future. That's how I'm doing it with Zeam launcher.
Oh okay. I just noticed the launched looked different than Tickerguy's. I tried to restore my home screen with Titanium Backup but it didn't work. So Launcher2.apk is what I need to install. Okay, I'll try it. Thanks so much! Great job on this!
Device(s): Motorola Triumph (Tickerguy's CM7), LG Optimus V (CM7.2-RC3)
Carrier: Not Provided
Thanks: 34
Thanked 71 Times in 39 Posts
Good to see people are back working at it again
__________________
Always have your stuff when you need it with Dropbox. 2GB account is free!
Quote:
There's something you better understand about me, 'cause it's important and one day your life may depend on it. I am definitely a madman with a box!
-The Doctor
ADW launcher comes default with CM7, If you google 'Launcher2.apk' and install it like a regular app (in /data partition), then clear the app cache settings to use the launcher2 by default, it should stick even when flashing newer CM7 builds in the future. That's how I'm doing it with Zeam launcher.
Whyzor, this is a flashable zip for the Launcher2.apk
hehe nvmd!!..went over the thread for the kernel, got everything i needed from there guess i was just too lazy!
Okay, good to hear.
Also, here is the most common CPU governors explained. Although, TheOC kernel has a few extra governors not mentioned here, this may help get you started: [Q] SetCPU governors (explained) - xda-developers
It should work, but I would just grab the .apk (from inside the .zip) and install it like an app, that way it won't be overwritten with new ROM flashes (cache & dalvik-cache wipes).
It should work, but I would just grab the .apk (from inside the .zip) and install it like an app, that way it won't be overwritten with new ROM flashes (cache & dalvik-cache wipes).
Okay, thanks!!
also one more question.. can I flash the battery icon modifications or will that overwrite changes you have written in the framework? I can live without them if so.
I'm typing this using the reloaded ROM and I love it! Thanks!
Okay, thanks!!
also one more question.. can I flash the battery icon modifications or will that overwrite changes you have written in the framework? I can live without them if so.
I'm typing this using the reloaded ROM and I love it! Thanks!
Doubt "flashing" anything that modifies the framework would work, unless the person who created it bases it off of this new framework. It's better if you want to learn to mod stuff, open up the framework & extract the icons or .xml files from it, then save it separately so you can apply it again (when a new build comes out). Google for ways to do that.
The Following User Says Thank You to Whyzor For This Useful Post:
There's still no way to verify, but with my changes I can set it to 500 mV as minimum and it's still fine 122-1024 Mhz.
I have the spec sheet for the TI TPS65023 voltage regulator, but my knowledge is insufficient to decifer what the lowest valid voltages are. Maybe someone here can read it and help. It would be nice to know if the voltage is actually setting that low or, in fact defaulting to some higher value.
I have the spec sheet for the TI TPS65023 voltage regulator, but my knowledge is insufficient to decifer what the lowest valid voltages are. Maybe someone here can read it and help. It would be nice to know if the voltage is actually setting that low or, in fact defaulting to some higher value.
If you're looking for some leisure reading material, I definitely recommend this spec sheet
In one of the spec tables, there are the 3 voltage out lines, and it looks like minimum is 600 mV. So that would be my not-so-well-educated guess.
Code:
Output voltage range for VDCDC1 step-down converter
(1)
0.6
VO Output voltage range for VDCDC2 step-down converter
(1)
0.6
Output voltage range for VDCDC3 step-down converter
(1)
0.6
If you're looking for some leisure reading material, I definitely recommend this spec sheet
In one of the spec tables, there are the 3 voltage out lines, and it looks like minimum is 600 mV. So that would be my not-so-well-educated guess.
Code:
Output voltage range for VDCDC1 step-down converter
(1)
0.6
VO Output voltage range for VDCDC2 step-down converter
(1)
0.6
Output voltage range for VDCDC3 step-down converter
(1)
0.6
Device(s): HTC One S (CM10),
Kindle Fire (CM10-SGT7)
Carrier: T-Mobile USA
Thanks: 3,844
Thanked 5,034 Times in 2,658 Posts
Quote:
Originally Posted by Whyzor
Doubt "flashing" anything that modifies the framework would work, unless the person who created it bases it off of this new framework. It's better if you want to learn to mod stuff, open up the framework & extract the icons or .xml files from it, then save it separately so you can apply it again (when a new build comes out). Google for ways to do that.
There are a couple guides for that stuff around here too. If you don't want to do it yourself I am sure someone will get around to it before too long.
The Following User Says Thank You to agentc13 For This Useful Post:
Memory tweaks I am making in the 99memory file seem to not be sticking.
Memory still drops to 24MB. Do we still edit this the same way as we did in TG's original rom or is there another file I can try editing the values in?
Memory tweaks I am making in the 99memory file seem to not be sticking.
Memory still drops to 24MB. Do we still edit this the same way as we did in TG's original rom or is there another file I can try editing the values in?
Sorry for the many questions.
You have to mount it rw first, also remove the '#' in the beginning of line, also reboot. or use an app to do it like 'autokiller memory optimizer'.
The Following User Says Thank You to Whyzor For This Useful Post:
Just flashed this last night, and it's pretty good so far. Battery lasts longer for sure. The only problem is that the built in tether (portable hotspot) is not working. This is the first time putting CM7 on my phone, did it work in TG's original CM7? I used barnacle when i was using the stock rom, and it worked fine after I changed the mtu settings. I would like to use the built-in tether instead of barnacle or any other app. Thanks in advance
Just flashed this last night, and it's pretty good so far. Battery lasts longer for sure. The only problem is that the built in tether (portable hotspot) is not working. This is the first time putting CM7 on my phone, did it work in TG's original CM7? I used barnacle when i was using the stock rom, and it worked fine after I changed the mtu settings. I would like to use the built-in tether instead of barnacle or any other app. Thanks in advance
Make sure "USB Debugging" is enabled.
Check under Settings, Applications, Development
The Following User Says Thank You to TheBritton For This Useful Post:
Device(s): HTC EVO V 4G (JellyBean 4.1.2), Asus Nexus 7 (JellyBean 4.2.1), Logitech Revue (Honeycomb 3.2)
Carrier: Virgin Mobile
Thanks: 5
Thanked 5 Times in 4 Posts
Hate to be a n00b here, but I'm not too familiar with CPU governors and how each one behaves, and seeing as the number of governors have doubled in this build of CM7, I'm hoping someone will help explain them to me.
Mainly minimax, smartass, smartassv2, Scary, InteractiveX, and SavagedZen.
Hate to be a n00b here, but I'm not too familiar with CPU governors and how each one behaves, and seeing as the number of governors have doubled in this build of CM7, I'm hoping someone will help explain them to me.
Mainly minimax, smartass, smartassv2, Scary, InteractiveX, and SavagedZen.
Hate to be a n00b here, but I'm not too familiar with CPU governors and how each one behaves, and seeing as the number of governors have doubled in this build of CM7, I'm hoping someone will help explain them to me.
Mainly minimax, smartass, smartassv2, Scary, InteractiveX, and SavagedZen.
The best way is to just look at the source code comments since a lot of devs don't like to write separate docs.
Hate to be a n00b here, but I'm not too familiar with CPU governors and how each one behaves, and seeing as the number of governors have doubled in this build of CM7, I'm hoping someone will help explain them to me.
Mainly minimax, smartass, smartassv2, Scary, InteractiveX, and SavagedZen.
There is also a good explanation here: http://forum.xda-developers.com/showthread.php?t=1242323
The Following User Says Thank You to frdmspoplr For This Useful Post:
Hate to be a n00b here, but I'm not too familiar with CPU governors and how each one behaves, and seeing as the number of governors have doubled in this build of CM7, I'm hoping someone will help explain them to me.
Mainly minimax, smartass, smartassv2, Scary, InteractiveX, and SavagedZen.
Any luck changing yours?
I've tried changing mine too smartassv2 and after reboot the setting goes back to the original setting.
How much does disabling boot animation speed up boot time? Anyone checked it out yet?
I haven't tried this ROM yet cause I figured I've already made most of the changes to my setup, except for disabling hdmi.
My current is about 35 seconds to my lock screen shows.
Hope everyone got w what they wanted for Christmas!
How do you change the carrier name in cm7?
I decompiled the framework-res.apk and went to to strings.xml file to change the name, but i could not find the line:
that's how i changed it in my last rom. can someone tell me how to change it please? and would i need to reflash the whole cm7 file again after i make the changes to the framework-res.apk? (im a noob as u can tell by now ) thanks
Device(s): HTC One S (CM10),
Kindle Fire (CM10-SGT7)
Carrier: T-Mobile USA
Thanks: 3,844
Thanked 5,034 Times in 2,658 Posts
Quote:
Originally Posted by thunderup25
How do you change the carrier name in cm7?
I decompiled the framework-res.apk and went to to strings.xml file to change the name, but i could not find the line:
that's how i changed it in my last rom. can someone tell me how to change it please? and would i need to reflash the whole cm7 file again after i make the changes to the framework-res.apk? (im a noob as u can tell by now ) thanks
The stuff for that in CM7 is in the framework-res.apk like you thought, but it is in the eri.xml file instead of the strings.xml. Just change the lines that have "Virgin Mobile" to whatever you want it to say (I think there are 2 different lines, not sure that you HAVE to edit both, but I always have).
You won't want to flash the whole ROM again. The easiest way is to push it using ADB. If you don't know how to do that, find the CM7 flashable zip, unzip it and replace that framework-res.apk with the one you just pullled/edited from your phone. Then rezip and you should be good (not sure if you want it compressed or not, I personally use ADB). If you use something like APK Multi-Tool, you can ADB push using that as well.
The Following User Says Thank You to agentc13 For This Useful Post:
I was really excited to see that developmet was continuing on tickerguy's cm7 project, and you have done some great work.
Unfortunately, it hasn't been working very well for me. Could very well be something I am doing wrong but I've had a number of issues. Some graphical glitches in scrabble. Most importantly, wifi takes really long to connect and reconnect now. Maybe I shouldn't be using juice defender with this build? This also seems to be causing me to have problems to connect to google so I've been missing emails. I had to restore back to the b.08.
I could've just done something wrong though I guess, but I thought I should still share my experience.
I was really excited to see that developmet was continuing on tickerguy's cm7 project, and you have done some great work.
Unfortunately, it hasn't been working very well for me. Could very well be something I am doing wrong but I've had a number of issues. Some graphical glitches in scrabble. Most importantly, wifi takes really long to connect and reconnect now. Maybe I shouldn't be using juice defender with this build? This also seems to be causing me to have problems to connect to google so I've been missing emails. I had to restore back to the b.08.
I could've just done something wrong though I guess, but I thought I should still share my experience.
Quote:
Originally Posted by bobloadmire
Can we flash this ontop of TGs 0.8 build or should we do a clean install?
Make sure the download isn't corrupted, check the md5sum by opening terminal emulator, cd <dir_of_zip_file>, then md5sum <zipfile>. Also make sure to wipe cache and dalvik-cache before flashing, it will keep your old settings and apps.
5Likes
[ROM] CM7 TG-Reloaded (Final: 03-25)
Changelog
I'm gonna install this once I get off work
