Changelog 7.2.0

New devices: Samsung Galaxy Ace, Mini, and Epic. LGE Optimus Black, 3D, Hub, Pro, Sol, and One. Motorola Atrix. Sony Ericsson Xperia Live, Pro, and Active. Huawei U8150
Common: Updated translations - (everyone)
Common: T9 predictive Phone dialer - Danesh M, Pawit Pornkitprasan
Common: Media player and recorder fixes for a number of corner cases - CAF, Danny Baumann
Common: Profile resets - Ladios Jonquil
Common: Assorted Wifi fixes
OMAP Common: Support for recent OMAP3/OMAP4 devices - omapzoom
Common: Control haptic in quiet hours - Danesh M
Common: Lockscreen updates and new styles - Andrew Sutherland, Danny Baumann, Danesh M, Sven Dawitz, Taichi Nishimura
Common: Bluetooth MAP support - Jonathan Bensen
Common: ICS telephony fix backports - Spencer Oliver
Common: Support for Bluetooth GPS dongles - Cuong Bui
Common: Better support for mouse and usb keyboards - Emilio Lopez, Tanguy Pruvot
Common: Fix timezone detection in Hawaii - Warren Togami
Common: ICS Transition effects backport - Russ Underhill
Common: ICS Rotation effects backport - Tanguy Pruvot
Common: Allow photo storage selection when possible - Greg Kochaniak
Common: Improved Calendar reminder options - Danny Baumann
Common: Fix color banding in Gallery while displaying 32bpp images - Sang Tae Park
Common: ADB over network
Common: Improved AVRCP 1.3 compatibility
Common: Improved external keyboard and mouse behaviour on some corner cases - Tanguy Pruvot
Common: Status bar battery icon configuration - Simon Davie
Samsung Galaxy S GSM devices: Fix emergency dialing
p990: Add FM Radio support
p990/p999: fix background calls, fix HDMI output in 1080p
zeppelin, morrison, motus: Fixed camera zooming issues
Samsung Galaxy S devices: Add tv-out
Several devices: Fix device identification on Android Market
crespo, jordan, blade, v9, Samsung Galaxy S devices: Device specific settings section

If you'd like to check it out and see exactly what the differences are from 7.1, go here:

https://github.com/CyanogenMod/android_vendor_cyanogen/blob/gingerbread/CHANGELOG.mkdn

 

No I haven't ran this ROM before, my phone got stolen a while back, and I'm waiting for the EvoLTE 4g to be released before I utilize my upgrade.....Huge fan of CM7 though.

 

When I came off 7.1 I realized 7.2 ran much better, then I smurfed it ran vipermod and dt a2sd with ext. 4 and the latest tiamat gb kernel. I love the way my phone runs. But I put similar set ups on other evos and it doesn't run so well. I love it though try it out.

sent from my evo 4g running a bunch of awesome mods developed by some real sweet devs.

 

Yeah, every Evo is different and reacts differently to different ROM/Kernel/Mod combinations. What works great for you may prove unstable or not so great for others.

Unfortunately I'll have to wait a little while before I can try any setup out. I'm waiting for the EvoLTE to be released, on top of that, I have to wait for a root exploit to become available for it, and on top of that I'll have to wait for ROM's to be developed for it. Hopefully it's not long after it's released. If the EvoLTE's community and support is even 1/2 of what the OG Evo's is, I'll be okay.

 

It's possible that you can, but it's always best when flashing any new ROM to perform a FULL wipe beforehand.

 

Ive had a few issues with 7.2 and the newest tiamat sbc kernel. Runs fairly well but im experiencing problems with the actual phone and camera. The phone is laggy and wont let me unlock sometimes when i get a call. My mic also doesnt work sometimes and i have to clear cache and dalvik cache to get it to work again. Ending calls is very difficult sometimes because the END button must be repeatedly tapped. The camera issue is the rom itself i believe. The dock is transparent .. so when i go to adjust the zoom slider it selects the flash option which is right behind the slider toggle.

 

Are you underclocking your Evo? If so, what's your min. set to?

 

Case and point . Do a FULL wipe and reflash the ROM (if you still want to run 7.2). I know it's a pain to set everything up again but nothing beats a clean install.

 

The nightlies always ran better for my Hero and EVO. Have you tried the latest 4/8 nightly? Team that build up with the GB Mason kernel and you'll have a nice rom

 

What does Smurfed out mean and explain Vipermod compared to supercharger. What is this (dt a2sd with ext. 4)?

 

V6 changes your OOM settings. Vipermod changes your kernel voltage table. dta2sd is a script that allows your apps to be fully stored on an EXT3 partition set up on your SD card, essentially giving you limitless space for apps.

Personally, I think V6 is overly complicated. For simplicity you can't beat the CoD tweaks. Just google it. The instructions are super easy and all you need are a couple free apps. ROM Toolbox is one of them and has since had part of its functionality taken out of the free version. Just download sysctl config, it's free as well.

 

You never know, that may be a great combination for your Evo. Make a nandroid and give it a try. That's why we all rooted, right? To have the freedom and control over our Evo's to be able to try new things.

 

I am not undervolted ... dont have vipermod installed

 

From nightly to nightly your usually fine with a cache wipe, but from rc to rc there's generally huge changes

Sent from my PC36100 using Tapatalk 2 Beta-5

 

I'm asking you if you're CPU is underclocked. Are you using SetCPU or underclocking your CPU (w/in CM7 settings) in anyway (outside of undervolting using vipermod).

 

I am overclocked with set CPU

 

The mason kernel kicks arse. I can't wait for his next release that'll include sense support

(And its been out for a month now, if it was gonna destroy your phone it'd be taken down already )

 

Okay. So you have your Max. set to whatever it's set to (ie: 998, 1036, 1115, etc.) what I want to know is what you have your Min. set to (ie: 128, 245, 384, etc.). The reason I'm asking you this is if your Min. is set too low for your Evo, it'll have trouble waking up when you answer the phone, end calls, etc...

 

I'm also interested in what you have set for a governor as well as any profiles.

There are general issues with AOSP and the phone not always waking up the first time you press the power button, but it shouldn't be disrupting how your phone works.