Related
Read the Known Issues section of this post below along with the FAQ a few posts down before posting.
A few people have asked about I9100 builds of my Daily Driver kernel for the SGH-I777. I normally hate blind development, but since most I9100 guys are doing it for I777 targets, I may as well try going the other way. Since it fails the definition of being a "daily driver" as I own an I777 and not I9100 - it will not be using the Daily Driver name.
This should be compatible with most stock-derived Gingerbread firmwares, with a few exceptions listed below. It is NOT compatible with CM7/MIUI or any other AOSP-derived firmware. It is NOT compatible with ICS and WILL NOT BE until ICS kernel source for the I9100 is released. At that point a new thread will be created for those kernels. I am testing it currently with self-deodexed/debloated/Hellraised XWLA4.
The following firmware bases are likely to deliver poor battery life with this kernel due to wifi bugs in the firmware:
XXKI3, UCKK6, XWKK5 - especially UCKK6 and XWKK5
This kernel series is intended to be similar in spirit to my Daily Driver series for the Infuse at http://forum.xda-developers.com/showthread.php?t=1212795
It is built from sources at https://github.com/Entropy512/linux_kernel_sgh-i777/commits/oc_codeworkx, and initramfs at https://github.com/Entropy512/initramfs_sgh-i777/commits/master
My general goals are to focus on stability and battery life. If it comes to a tradeoff between performance and the above two, I will choose stability/battery life. In general I will choose stability first, with the exception of undervolting.
I keep my initramfs clean - There are no tweaks or other automated scripts built into this kernel. For a collection of tweaks I am working on and documentation on them, see http://forum.xda-developers.com/showthread.php?t=1378080
Current features:
I9100 Update3 base
Touchscreen drivers from I777 source code base
codeworkx's cpuidle patch - should improve battery life a bit. In most cases it will likely not improve things much, but in rare cases it will result in significant improvements. (I only have one partially-reproducible test case on the Infuse so far)
JHash 3
BFQ I/O scheduler
CIFS module in initramfs
CWM 5.0.2.8 compiled from CM7 sources on 2/28/2012
"insecure" kernel (meaning root in ADB)
CPU governor set to Conservative by default to conserve some battery - this will make your device slightly less responsive, use SetCPU or a similar app to return to ondemand if you want it, or reduce the conservative polling interval
Filesystem readahead tweaks in initramfs
netarchy's Sleep of Death fix
netarchy's conservative governor tuning patch - should improve responsiveness of devices when using the conservative governor if you reduce the polling interval (misnamed as sample_rate) - the I9100 community calls this "lionheart" even though it's really only a 2-line patch
Battery charge current monitoring (CurrentWidget) support - only reports charge current and not discharge, and reports a value 2.85 times the actual current. Use CurrentWidget's "operation on value" to divide by 2.85.
Miscellaneous bugfixes pulled from Ninphetamine and CM7 sources - see github for details
/system/etc/init.d support in initramfs - Note that this only runs stuff in /system/etc/init.d - ROM developers or you need to create it. Attached is an example script that will change the CPU frequency governor to ondemand if placed in /system/etc/init.d and set to executable
Four "use at your own risk" features that trade performance for stability - See Post #4 for details
Standard bootanimation support
/proc/last_kmsg crash debugging support
NFS modules in initramfs - note that they must be insmodded in a specific order: sunrpc.ko, lockd.ko, then nfs.ko
Fix for fuel_alerted perma-wakelocks
Fix for wifi tethering on I9100 ROMs that have been Hellraised to I777
Bump up TCP buffer sizes in initramfs to match that of the Infuse - may help network performance in some cases
cpuidle driver from Tab 7 Plus kernel - allows entry into AFTR more often - includes MFC interoperability fix (Should not break video playback.)
Support Bluetooth HID on newer firmware bases
3-step GPU clock/voltage control
Extended hotplug tuning
Support for Xan's ExTweaks universal tuning app - https://market.android.com/details?id=com.darekxan.extweaks.app
Planned features, short term:
Determine if issues with PINlock when running I9100 firmwares on I777 have kernel involvement, and fix them if this is the case.
Planned features, mid-term:
Potentially my first departure from "standard" governors, with a focus on improving hotplugging logic
Planned features, long-term:
Improved battery charge algorithm for faster charging - Initial research indicates we have an alternate battery charger chip (MAX8922) that differs from the MAX8997 used in the I9100. We DO have an 8997 also - but on our device for some reason Samsung decided to use an alternate chip instead of using the 8997's built-in charging. This means we have far fewer options (90,400,660 mA) in terms of charge rates compared to the I9100 (from 200 to 950 in 50 mA steps). So we might not be able to implement any fancy charging algorithms.
Features not planned:
BFS process scheduler - I have only once ever seen a test case where this clearly outperformed the mainline Linux scheduler (multithread x264 encoding) - The mainline schedule was fixed in the next release and BFS now has no performance benefits
Any feature that trades off stability or data integrity for performance unless it can be disabled entirely and defaulted to "off"
Any feature that cannot have functionality tested without a paid app. Interface-only checks don't cut it - I don't want users complaining that the app they paid for didn't work because an interface check worked but function didn't
Touch recovery - too prone to unintentional user input in dangerous situations. I will reconsider this with ICS.
ARM_TOPOLOGY/SCHED_MC - See http://forum.xda-developers.com/showpost.php?p=23193259&postcount=100 for details
Known issues:
Power management regression somewhere between 12/8/11 and 1/2/12 - Intermittent high drain without high AOS or reduced deep sleep percentage when on some wifi networks - seems more likely if GPS is used when connected to wifi. Wifi with high AOS/reduced deep sleep is not a kernel problem. This appears to only happen on some firmwares - it happens on XXKI3 but not XWKL1. It is likely connected to a wifi power management bug in some firmwares. A debugging feature in 2/7 and later will allow identification of such firmwares - see http://forum.xda-developers.com/showpost.php?p=22581928&postcount=1777 for details
Some people have reported touchkey lights becoming disabled until the screen is turned off and back on again. Under investigation - seems to mainly happen on firmwares with BLN-modded liblights even if the BLN app isn't used
Internal and External SD card are swapped in CWM currently
Keymap is a little funky in CWM for I9100 users. VolUp/VolDn to move, Power to select is reported to work, but bottom keys are funky. Working on it
A few users have reported that when Hellraising I9100 firmwares to I777, they are unable to set up a PIN-lock. If this occurs for I9100 users on their own devices, I need to look into initramfs fixes and this will be my top priority.
Basic flashing instructions for .tar releases (NOTE - There are currently no releases in this category. These instructions only remain for heimdall+ZIP users:
(Tested on Linux, not tested MacOS/Windows but should work) Heimdall - Extract the contents of the tar file, enter download mode, and flash with the following command line:
Code:
heimdall flash --kernel zImage
Flashing instructions for .zip releases:
Flash in CWM, or extract the zImage and use the Heimdall instructions above.
Please do not ask how to enter download mode or install Heimdall/Odin in this thread - these are basic generic skills anyone flashing custom firmwares on Samsung devices should know and plenty of documentation exists elsewhere. If you really need to ask, use the General forum, or if created, the Q&A forum. I want to try to keep this thread clean and only with bug reports and issues specific to this release, not general HOWTO or troubleshooting posts. Some of the information you need is in jivy26's FAQs thread at http://forum.xda-developers.com/showthread.php?t=1288112 - Reading at least the first post of this thread in its entirety is STRONGLY recommended.
Bug reports:
If you have a crash (reboot all the way to Galaxy S I9100 screen), use ADB dump the contents of /proc/last_kmsg and post
If you have oddball behavior, include a clearly reproducible test case with your report, or use ADB to obtain a dmesg and logcat capturing the odd behavior at the time of error.
Similar to flashing - using ADB and obtaining last_kmsg, dmesg, and logcat dumps are basic skills that anyone working with custom firmwares on Android devices should have. If you need help with these, do some searching, or post in the General forum or Q&A forum.
Firmware ("ROM") Developers:
While I cannot restrict anyone from putting this kernel into a ROM as long as links are given to the github sources for GPL compliance, I request that anyone who includes this kernel in a firmware release does the following out of courtesy:
Link to this thread
Clearly indicate in your firmware changelog which Daily Driver kernel release is included in your firmware release whenever you change DD releases - this lets users identify whether a fix is present in the kernel they're using or not
Kernel Developers:
Similar to my request for ROM developers, while I can't restrict you from doing anything, I ask as a courtesy that if you cherry-pick my commits, you do the following:
Please don't rebase my commits into a large multi-feature without consulting me - rebasing related bugfixes together is OK.
Please try not to implement lots of unrelated features or bugfixes in a single git commit - it makes it hard to reimplement that when Samsung drops new sources or releases a new device
ALL OF MY RELEASES ARE NAMED BY RELEASE DATE - MMDDYYYY. See the changelog for differences between Experimental (exp) and non-exp versions for days where dual releases are made.
Change Log
The primary change log will be kept in my I777 kernel thread at http://forum.xda-developers.com/showpost.php?p=18129037&postcount=2
Unless I9100-specific items are implemented, this post will simply indicate which I777 release the kernel corresponds to.
3/7/2012:
Corresponds to Daily Driver 3/7/2012
03/05/2012:
Corresponds to Daily Driver 3/5/2012
03/04/2012-B:
Corresponds to Daily Driver 3/4/2012-B
03/04/2012:
Corresponds to Daily Driver 3/4/2012
03/03/2012-B:
Corresponds to Daily Driver 3/3/2012-B
03/03/2012:
Corresponds to Daily Driver 3/3/2012
Initial release was bad, that was an I777 build. Reuploaded at 4:22 PM Eastern Standard time on 3/3 - Redownload if you downloaded before that
3/02/2012:
Corresponds to Daily Driver 3/02/2012
2/28/2012:
Corresponds to Daily Driver 2/28/2012
IMPORTANT: Internal/External sdcards have been swapped in CWM to be consistent with Android standards!
2/26/2012:
Corresponds to Daily Driver 2/26/2012
Initial release, 02/15/2012:
I know it's dated 2/15 and not 2/26, because that's when it was built. Thanks to khartaras for indicating that it isn't at least a horrible turd when used on an I9100.
This release corresponds to the 2/15/2012-C release of I777 Daily Driver
Here Be Dragons
This post is for features present in the kernel that are "use at your own risk" - They have either potential or guaranteed negative side effects if used.
Overclocking (CPU):
Enable using SetCPU or a similar app
USE AT YOUR OWN RISK. DO NOT REPORT BUGS OR PROBLEMS IF YOU ARE OVERCLOCKING OR UNDERVOLTING. IF YOU EXPERIENCE ANY STABILITY PROBLEMS, DISABLE ALL OC/UV
Overclocking (GPU):
See Ninphetamine kernel for documentation - Same control method
USE AT YOUR OWN RISK. DO NOT REPORT BUGS OR PROBLEMS IF YOU ARE OVERCLOCKING. IF YOU EXPERIENCE ANY STABILITY PROBLEMS, DISABLE ALL OC
Per-File fsync() disable:
This allows you to disable per-file write forced syncs. (e.g. if an app tries to force a write straight to disk, it'll just go to cache). This achieves the same goal as the modded sqlite hacks seen in tweaks such as USAS, however it can be disabled at runtime.
WARNING: THIS CAN CAUSE DATA LOSS OR CORRUPTION IN A CRASH
To enable, do the following in a terminal, or add it to an init.d script (look at my ondemand script as an example):
Code:
echo "1" > /sys/module/sync/parameters/fsync_disabled
And to disable (return to the default):
Code:
echo "0" > /sys/module/sync/parameters/fsync_disabled
Good for around 200 points of epeen in the database benchmarks in Antutu or 500-600 points of epeen in Quadrant. Real-world benefit: Probably not worth the data integrity risk, but you've got a choice now.
Backlight Notifications (BLN):
This allows the touchkey backlights to be used for notifications. Some stock apps (such as stock MMS) don't support it. Supposedly services.jar mods can change this.
This WILL drain your battery when a notification is active due to a wakelock that holds deep sleep. Sorry, it's either this or instability for the time being.
In addition to the BLN control app, the ROM needs a modified liblights file for this to work
Attached here - Liblights - both BLN-modified (extracted from VillainROM 3.0) and stock I777
To install, take the file and push it to /system:
Code:
adb remount
adb push <file> /system/lib/hw/lights.SGH-I777.so
adb chmod 644 /system/lib/hw/lights.SGH-I777.so
Then reboot
Note that on a Hellraised ROM, you need to replace SGH-I777 with GT-I9100. This includes manually ported ROMs like Cognition 777
Like my prerooted system image, this file is compressed using 7-Zip to prevent people from trying to flash it with CWM
OK, right now this post only has documentation of one "special but safe" feature:
To enable debugging of high deleted_wake_locks time, I've set this up to allow wake_lock_destroy() to be debugged without enabling DEBUG_WAKE_LOCK (which spams dmesg with a ton of stuff not needed for wake_lock_destroy() debugging). To enable, add 32 to the value of /sys/module/wakelock/parameters/debug_mask - This defaults to 3, so the proper value is 35.
Code:
echo "35" > /sys/module/wakelock/parameters/debug_mask
Return this to 3 to set it back to the default.
With this, you'll see wake_lock_destroy debugging information in your dmesg output. This is only needed if you have very high deleted_wake_locks times.
The following is known to cause deleted_wake_locks:
Turning off wifi will convert all wlan wakelocks into deleted_wake_locks
FAQ
Q: I installed this and still don't have root?
A: I keep a clean initramfs. There are NO tweak scripts in it, and no autoinjection scripts. To root your device, flash one of ChainsDD's Superuser packages in CWM
Q: I don't like the default I/O governor, why is it this way?
A: Clean initramfs (if you need to flash a kernel cleaner script after my kernel, I have failed or an app cluttered up your init.d) - If you want to change the default governor and tune the filesystem, see my init.d scripts thread.
Q: Why is it so laggy by default?
A: I don't believe in having half my patches tuning default values of things the user can change. In addition, as stated above - battery life is valued over performance, so default governor settings will be biased towards battery. My personal recommendation if you wish to increase performance (at the cost of battery life) is to drop the sample_rate for the conservative governor using SetCPU or a similar tool - this will significantly improve performance. It provides nearly all of the benefits of the original "lionheart" without allowing the sample_rate to go dangerously low. In a future release I'm going to drop the minimum a little bit more.
Q: Something went wrong. I'm using some stupid comprehensive tweakscript. Y U NO FIX?
A: I will not support anyone who is using a comprehensive tweak script (Thunderbolt, V6 Supercharger, etc. - ESPECIALLY V6 Supercharger, as its developer has multiple times in the past put in dangerous tuning options. For example, he disabled the panic reboot timeout, which combined with Samsung's ****ty wifi driver on the Tab 7 Plus, led to multiple Tabs draining their battery all the way to the battery's failsafe cutoff.) If a specific individual tweak causes a problem, let me know - but you'd better know EXACTLY which tweak it is. In addition to the above issues with V6SC, many "tweak scripts" achieve their goals by trading filesystem integrity for performance, and irresponsibly don't warn the user about this fact. See, for example, the fsync disable feature above - it's dangerous, but don't say I didn't warn you it was.
Q: What voltages do you use?
A: This is irrelevant. Every device is different, if a given set of voltages worked on all devices, Samsung would've made it stock. I will report any discussion of voltage recommendations to the moderator for cluttering the thread. If you're undervolting, you need to take responsibility and do it on your own.
Q: Why don't you support AOSP firmwares (CM7, etc.)?
A: I know that the CM team frowns upon alternate kernels as it makes their testing job more difficult. Similarly, supporting too many firmware bases makes my job more difficult. Out of respect for the skills of codeworkx and atinm, I will not release kernels that could make their life harder. I periodically give them the heads-up on patches that I think are important though.
Q: What's with the toilet humor of the name?
A: Long ago in the Infuse community, there was a person (lemons) that was starting to do some smali hacks (camera modding and such), and was planning on eventually releasing a ROM. He was a pretty good guy, and had lots of potential. He and others joked that since it was his first attempt, it should be called ****ROM. Sadly, lemons never followed through and just disappeared, so for months, ****ROM never became a reality. Eventually it was realized in the form of a deodexing/porting/basic modding guide for I777 users at http://forum.xda-developers.com/showthread.php?t=1505685. In addition - I hate hype and marketing, better to set expectations low and let the code prove itself on its own merits. Since I'm blind-developing, I can't just say it's my daily driver because in this case, I am unfortunately not eating my own dogfood.
Q: Why don't you base on 2.6.35.14?
A: That would be my Experimental series. It's temporarily on hold for a variety of reasons but will return once I finish reimplementing some patches. The great thing about git branching is I've been able to maintain .7 and .14 trees simultaneously with ease.
Q: Sometimes my touchscreen is unresponsive right after a wakeup, why?
A: It seems, based on reports from khartras and teiglin, that TouchScreenTuner does not play well with the I777 touchscreen drivers. I'm not sure if it's even necessary with them - in the months since October, the only time I have ever received touchscreen complaints from I777 users was when running I9100 update3 touchscreen drivers. TST may just be working around broken drivers...
Reserved for ?????
Thanks for this. I will try later.
Again very thanks.
Enviado do meu Galaxy S2 usando TapaTalk
Going to try this kernel for the sole reason that I think you're a great guy on here and I enjoy reading your informative posts - you always seek to educate rather than put people down.
Thanks Entropy.
Uploaded a new release, this has just a few small patches, bringing it up to the same base as Daily Driver 2/26/2012
As a compulsive lurker, reader and searcher, ive been looking forward to this release..
Alongside Pulser and Ninpo, your informative postings and professional ethic enable users like myself to maximize the potential of our devices.
Thanks mate, i have no doubt this will be brilliant..
Thanks Entropy, I've missed your work since I moved from Infuse over here instead of to I777-land. I do have a question, though--I note the only "nonstandard" I/O scheduler you included was BFQ. Do you find sio/vr problematic, or do they just not provide any benefit from your perspective?
teiglin said:
Thanks Entropy, I've missed your work since I moved from Infuse over here instead of to I777-land. I do have a question, though--I note the only "nonstandard" I/O scheduler you included was BFQ. Do you find sio/vr problematic, or do they just not provide any benefit from your perspective?
Click to expand...
Click to collapse
I'm considering adding these - I've found that alternate governors/schedulers often cause more problems than they solve.
Thanks for sharing your kernel with us i9100 users Enthropy. I really like your stability+ battery approach. Will be giving the kernel a good go.
Sorry...this kernel is comparible with jkay brightness profile?
Inviato dal mio GT-I9100 usando Tapatalk
coloxim said:
Sorry...this kernel is comparible with jkay brightness profile?
Inviato dal mio GT-I9100 usando Tapatalk
Click to expand...
Click to collapse
No - And right now, I am unaware of any kernel that is. As much as I like JKay's work, I believe he lacks understanding of how screen brightness works on the I9100 and I777.
Even JKay is unaware of any kernels that support those profiles. See entry 12 in his FAQ.
To implement additional brightness steps, an additional gamma table for each brightness step needs to be implemented - https://github.com/Entropy512/linux_kernel_sgh-i777/blob/master/drivers/video/samsung/ld9040_gamma.h
So until FAQ section 12 has clearly defined (and achievable) requirements for compatibility, or JKay declares a specific kernel compatible in FAQ section 12 of his mod, I won't be doing anything. Creating a custom gamma table entry is not easy as it requires a LOT of tweaking and good colorimeter hardware. Supercurio has done it at high brightness levels to my knowledge, but I don't think he's done it for low brightness levels and I don't think he's added extra gamma tables for additional brightness steps.
Edit: I have seen that Speedmod and Redpill do change the table entries for the lowest two brightness settings - however, they don't add any new bins, so the brightness change is achieved even on JKay profiles that don't supposedly require kernel support. e.g. JKay's "dark, requires kernel support" are pointless because the only kernels that actually provide dimmer minimum backlight do so even with his profiles that don't claim to require custom kernels. (And the "super dark" and "dark" profiles will behave the same regardless of kernel.)
What's interesting is hardcore did it for only two of three available panel types. Either two of Samsung's panel types are brighter than others, or hardcore did this without testing on some panel variants and just thought "the numbers are different, I'll change them". I'll look into playing with this as it would be nice to have lower minimum brightness, but it's somewhat low priority as it's easy to simply make things look like **** if you're not careful.
its possible to make your kernel fully compatible with the cmw manager of chainfire
for now some fonctions are desactivate
anyway i m testing it now and all seems to be good
So far so good mate.
Batterylife we will see in a day or two but all in all running fine.
Thanks and go ahead with ur work.
CHEERS ;-)
Sent from my Galaxy S2 - I9100 with SensatioN Rom!
F3nr1s said:
its possible to make your kernel fully compatible with the cmw manager of chainfire
for now some fonctions are desactivate
anyway i m testing it now and all seems to be good
Click to expand...
Click to collapse
Others have asked me this - if he has compatibility guidelines posted somewhere, I'll take a look at them.
{
"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"
}
Battery in deep sleep is exceptional, 2% lost in 5 hours with WiFi enabled and emails syncing.
Sent from my GT-I9100 using XDA App
Facality
weird name for a kernel..or for pretty much anything..dude
CounterShrike 3.1.1
About the ROM
This is the most feature-packed CM9-based ROM on the Rezound, giving you some of the most popular customization options while maintaining the stability of CM9. Features Aroma Installer for a highly customizable experience, complete with S-ON and GSM support, and lots of application In addition to adding dozens of options, I've added in the latest bugfixes and enhancements that didn't make it into the final release of CM9.
S-ON users: Please see the FAQ in post 2 for more information on flashing when S-ON.
IMPORTANT ALERT TO ALL USERS: GAPPS INSTALLATION NO LONGER REQUIRED. Recently, it was brought to my attention that the legal limitations on including Google Apps in an AOSP ROM was specific to the CyanogenMod team, so I have decided to include them in the installer now. If I get a letter from Google, I'll pull them out again, but for now, one download and one install is all you need.
As well as having all of the standard features of CM9, CounterShrike contains the following features:
Aroma Installer:
S-ON kernel installer
CDMA or GSM support
Choose from Trebuchet, Nova Launcher, and Apex Launcher
Choose between Superuser or SuperSU
Choose between stock keyboard or Jellybean 4.2 keyboard with swipe input
Choice of tweaks to install
AGPS patch by crypted. GPS should lock very quickly now, and even work better indoors and under cover.
Darky zipalign at boot
SQLite database optimization at boot
Debloating options
Choice of Google Search or Google Now
Choice of Jellybean Camera or ICS Camera
Choice of Google apps to install
Gmail
Google Maps w/ Street View
YouTube
Google Voice
Google Play Music
Google Talk
Compiled with Linaro optimized toolchain
Choice of kernels
UPDATED: Funky Kernel 2.5 by Snuzzo
UPDATED: Ermahgerd Kernel build 13.02.13 by me
CM10 Boot Animation
Bottom status bar option
Option to set brightness on long press on the status bar
Center status bar clock option
Lockscreen rotation option
I/O scheduler settings
Wifi idle timout setting
Popup settings instead of knobs in Camera app
Option to disable camera shutter sound
Face dection in camera
Clever dialing feature in Messaging app
Smileys in keyboard
Option to reverse volume key cursor logic in keyboard
Option to allow answering of incoming call with Home button
Option to allow the download/upload of potentially insecure attachments in Email app
Deskclock buttons hide completely during fullscreen
New battery icon options
Hide ADB notification option (reboot required)
Color weather images for lockscreen from AOKP
Option to remove "bong" sound on volume change when using the hardware volume rockers.
In addition to the above features, contains the following enhancements and bugfixes:
bionic: Add ARMv7 optimized string handling routines
telephony: Fix MMS for when operator has different APNs for Data and MMS
SystemUI/res: Move files to proper directory
Folder : Show folder name in expanded view w/ hide icon labels set
SurfaceTexture: Reset buffer values during connect
"Avoid multiple dns lookups for the same query"
Usb: Don't touch mobile data on USB event
Make lib dir before changing ownership of app dir
audioflinger: Fix for Equalizer effect not to turn off
frameworks/base: Fix for LPA volume change with headset
libstagefright: LPA: Fix flush issue when seek in A2DP
DateUtils: Avoid Time.format() calls when unnecessary.
Telephony: Reset the data registration state on radio off/unavailable
Phone: Ignore touch during network operators search
SurfaceTextureClient: Add null-pointer check.
surfaceflinger: Improve dithering method
fix Caller name disp not sticking for missed calls
telephony: neighboring cells are now handled properly
Make alternate character popup for hardware keyboard more user-friendly and locale-specific
Frameworks-base: Fix wifi-sleep-policy
"Revert "Add SCENE_MODE_OFF support for Camera "
fix wifi strength indicator (bcm4329+wext) on ics
Trebuchet: Add overlayable config for tablet workspace grid size
CallNotifier: Ring in PHONE_INCOMING_RING only if it has already rang once.
Make sure widget is notified on message-related changes
Telephony: Use time services daemon to set time
Contacts: force left justification on separator headers in contact list.
ActivityManagerService: stay away from zombie content providers
Added Long Press App Switch and Long Press Home alternative Removed white space
libstagefright: Enable hardware thumbnail generation
libstagefright: Add HW thumbnail support for 8x55.
libstagefright: use hw codec only for thumbnail mode
libstagefright: Software decoder is the first choice for thumbnail generation
StagefrightMetadataRetriever - fixed source start assertion failure on MPEG4Source
StagefrightMetadataRetriever: use cm platform naming
frameworks/base: Handle Out of Memory Exception when creating video thumbnails
libstagefright: Fixing a crash in EOS for thumbnail generation.
libstagefright: fix thumbnails for videos with non multiple of 4 width
Mms: fixes battery drainage while receiving Mms with data connection off
Remove live wallpaper lines
increase max EAS heartbeat to 30 minutes - Exchange
Fix heartbeat not incrementing on trivial changes - Exchange
stagefright aacenc/amrwbenc: Remove trailing whitespace
Launcher2: Improve launcher app launching performance
Improve HttpResponseCache performance.
Cleanup of the translation and added missing lines for Superuser
Fix 5701: Email widget displays valid emails then lots of empty entries with 01/01/1970
Browser: Update search engines
Remove 10MB of useless video from builds
Fix Issue 5547: Apollo will not play MP3 files when using Root Explorer
stagefrightaacenc: Properly terminate a comment
Browser: Quick control updates from Jelly Bean
Fix Qcom ifdef
SystemUI: Fix RecentsPanel deadlock on rapidly pressing
SurfaceTexture: Reset buffer values during connect
SurfaceFlinger: Dont skip composition if it is incomplete
libstagefright: Fix for audio fail issue during continuous BT switching
libstagefright: Convert mono to stereo for LPA clips
libstagefright: Prevent sink from starting in paused state
telephony: Handle RIL_APPSTATE_ILLEGAL
Telephony: Try setup data call when the conditions are met in applyNewState
Apollo: Don't show action overflow on devices with hardware menu keys.
CounterShrike v3.1.1 Download
md5: d124018dd41f0438d0bcf3e8da6cb9d2
Bonus carrier label tweak
The eri.xml file attached to this post will allow you to change where it says Verizon to anything you want to change it to. Download the eri.rar. Extract it. Open the eri.xml. Find where it says apophis9283. Change all of them to whatever you want. Put the xml file in /data. Reboot and enjoy! Thanks to TheBr0ken for the xml file.
Thanks go to:
apophis9283: All credit for the original rom base goes to him. Thanks for letting me take it over in your absence.
IAmTheOneTheyCallNeo: For answering my questions and encouraging me to get involved.
Snuzzo: Thanks for letting me use your kernel and for answering my questions.
chad0989: For making AOSP on the Rezound a reality.
crypted: For the use of the AGPS patch. If you find it useful, please consider donating to his server costs that are required to make this patch great.
cslingerland: My S-ON tester of DOOM. Seriously, he put his phone and himself through hell helping me test and perfect the S-ON installer. Without his help, it wouldn't have happened, so give him an extra thanks next time you see him.
Antoneus1231: For the name idea.
Changelog:
v3.1.1
Fixed GSM (for reals this time)
Update kernels
Funky Kernel 2.5
Ermahgerd Kernel build 13.02.13
Remove Seeder entropy tweak. Both bundled kernels now include this functionality without anything extra.
v3.1
Offer choice of Funky Kernel or Ermahgerd Kernel
Removed obselete fsync disable script. Funky Kernel now implements dynamic fsync control, and Ermahgerd Kernel currently does not (yet) implement any form of fsync control
Fix double gallery issue when installing ICS camera - This should hopefully also solve any lingering camera and gallery issues with the ICS camera.
Upgraded Funky Kernel to 2.2
Finished transition to VigorCM9 common resources
Miscellaneous Aroma config cleanups
v3.0.1
Updated to Funky Kernel 2.0
Switched to HTC wifi drivers for improved reliability
Updated GSM installer to hopefully fix issues. Please provide feedback
NOTE: Separate GApps installation no longer required or recommended. Please see first post for more details.
Old changelogs:
v3.0 release 2
Added Seeder tweak
v3.0
GSM support added - Experimental! Please report problems in thread
Integrated Google Apps into main installer - Separate Google Apps install no longer required
smartassV2 governor added back to kernel
Bundled apps updated to latest Play Store versions
Jellybean camera and gallery once again removes all previous versions
Major version incremented due to the vast restructuring of the installer
v2.4
Updated to newest Linaro 12.11 toolchain, 7 months newer than previously used toolchain. Resulted in a much smoother build overall. This is a completely fresh build so a full wipe is recommended
Added debloating options to Aroma installer. Choice of 18 apps to exclude from final installation.
Charge light now remains orange through 97% and turns green from 98%.
Installing Jellybean camera now leaves existing ICS camera and gallery intact. (Google Apps Aroma Edition)
v2.3a
Updated to Funky Kernel 1.7
Added: Apollo: Don't show action overflow on devices with hardware menu keys.
Jellybean 4.2 keyboard with swipe typing available as optional install
Jellybean 4.2 Gmail with pinch to zoom available as optional install (Google Apps Aroma Edition)
Jellybean 4.2 camera with Photosphere available as optional install (Google Apps Aroma Edition)
Bundled app updates:
SuperSU v0.98
Nova Launcher v1.3.3
Apex Launcher v1.3.4
Google Play Music v4.4.811H.526848 (Google Apps Aroma Edition)
YouTube v4.1.47 (Google Apps Aroma Edition)
Google Voice v0.4.2.54 (Google Apps Aroma Edition)
v2.3
Updated to Funky Kernel 1.6
Added: libstagefright: Fix for audio fail issue during continuous BT switching
Added: libstagefright: Convert mono to stereo for LPA clips
Added: libstagefright: Prevent sink from starting in paused state
Added: telephony: Handle RIL_APPSTATE_ILLEGAL
Added: Telephony: Try setup data call when the conditions are met in applyNewState
v2.2
Added Aroma Installer
S-ON kernel installer option
Choice between Trebuchet Launcher, Nova Launcher, or Apex Launcher
Choice between SuperUser and SuperSU
Made AGPS patch optional
Added optional zipalign at boot
Added optional SQLite vacuum and reindex at boot
Added option to disable fsync
v2.1
Option to mute volume adjust sounds. (added in 2.0, but missed the changelog)
Added back: Fix Qcom ifdef (frameworks/base)
Added back: SystemUI: Fix RecentsPanel deadlock on rapidly pressing
Added: SurfaceTexture: Reset buffer values during connect
Added: SurfaceFlinger: Dont skip composition if it is incomplete
Revert "Don't process INCOMING_RING notification if we're not currently ringing" to fix bug: default ringtone not playing on incoming calls
Revert "Fix custom ringtones" to fix bug: default ringtone not playing on incoming calls
Revert "move ACTION_MAIN intent-filter form settings to alarm list activity" to fix bug: can't dismiss alarm after deep sleep
v2.0a
Updated to Funky Kernel v1.4
Added crypted's AGPS patch
Added "Browser: Quick control updates from Jelly Bean"
v2.0:
Renamed to CounterShrike
Rebuilt from base
Added set brightness on long press on status bar option
Added disable ADB notification option
Added commit "stagefrightaacenc: Properly terminate a comment"
Added Rezound specific permissions fix for I/O scheduler setting
Removed "implement 1% battery on select devices" as it was only useful on Motorola devices
Baselined entire rom to github. Repository manifest at https://github.com/shrike1978/CounterShrike
v1.3
f/b: fix wrong qcom ifdef
Fix Issue 5547: Apollo will not play MP3 files when using Root Explorer
Known bugs:
Bluetooth calling does not work
MHL/HDMI output does not work
Jellybean Gallery force closes when attempting to edit photos
FAQ
Q: How do I install this ROM if I am S-ON?
A: Install the ROM from recovery as you normally would. During installation, select S-ON when prompted by Aroma. The installer will create a PH98IMG.zip file on your /sdcard. When installation is complete, reboot to your bootloader, either from Amon-Ra's Developer menu or TWRP's Reboot menu, and then select BOOTLOADER from the fastboot menu. The bootloader will prompt you to press VolUp to install the PH98IMG. Do so, and the kernel image will install. Be sure to delete the PH98IMG.zip file from your SD card when you're done so you'll be able to get back into your bootloader easily if necessary.
Q: What's the difference between SuperUser and SuperSU?
A: Functionally, both provide control over root access given to applications and services. SuperUser is the default app in CM9, and has been the long time standard on Android. The basic version simply provides per app allow/deny options, logging, and a few global options. A donate version is available that provides more granular per app logging and notification options. SuperSU is a recent entry that fixes some problems that the developer perceieved in SuperUser and seeks to provide more advanced features. The basic version provides all of the features of the basic version of SuperUser and more, including temporary unroot, per app notification configuration, wake on prompt, and more. The choice between the two is completely user preference. SuperUser has the edge in longevity and familiarity, SuperSU has the edge in advanced features. For most users, one will work as well as the other, but if you are having trouble getting root to stick on one, try out the other.
Q: Why does my screen go black when I'm on a phone call?
A: Your proximity sensor is being incorrectly triggered. Most of the time, this is calibration problem rather than a sensor problem. To fix, download Chad0989's Rezound Proximity Sensor Calibrator app. You will see a "NEAR" reading on the screen. Slowly increase the High Threshold until you see a "FAR" reading. Increase the High Threshold by 3-5 more than it takes to trigger a "FAR" reading. Test the new settings by covering and uncovering the Verizon logo on the front of the phone. The reading should switch between NEAR and FAR. Check "Set on boot" and close the app. If this fix does not work for you, your proximity sensor is bad, and you will need to contact Verizon for a replacement phone.
Github info
The main manifest of this ROM is at https://github.com/CounterShrike/android. While anyone is free to view the code and compile it on their own, no one else is given permission to release the ROM as is without written permission. The purpose of the public git is for open collaboration, so I encourage everyone with anything to contribute to go check it out. This github contains the main rom code only. Boot animation, tweaks, and Aroma configurations and scripts are only available in the official release.
I'll take this one just in case.
Sent from my ADR6425LVW using xda app-developers app
I'm really sorry to hear that he had to give it up. I remember him saying that he was having nerve issues, but I didn't realize that it was that serious. I've had great success with Project Rachel so far, but I'm still looking forward to see what you can do with it.
Edit: I saw that it was unrelated to nerve issues in his thread. Hurt his back.
Mine
Sent from my iPhone...
I want to say this. I have a lot of time invested in this rom. I have become good friends with these guys and I know they wont let me down. Snuzzo should get the biggest thanks because without him the OG rom would have never happened. Shrike, I know you wont let me down . Synister I am sure will do some kind of mods for it so I know thats taken care of. I would appreciate it Shrike if you would ALWAYS use Snuzzos kernel. Plain and simple, his kernels are unmatched. Well I will be on and off the scene and I hope this project turns out as good as I hope it will. Thank you all for your support and assistance.
I have a dream. That the community could come together and make an awesome rom.
Will offer any support I can to this rom.
apophis9283 said:
I have a dream. That the community could come together and make an awesome rom.
Click to expand...
Click to collapse
this is awesome haha. im really glad that shrike could step in to help. with my lack of knowledge all i can really contribute is bug reports and testing , but ill be here
He’s the hero XDA deserves, but not the one it needs right now. So we’ll hunt him. Because he can take it. Because he’s not our hero. He’s a silent guardian, a watchful protector. Apophis9283.
Lol, sorry, I had to. In all seriousness though, thank you Apophis. We appreciate everything you've done, and I hope your medical issues get resolved.
Thank you guys. Appreciate it
Sent from my ADR6425LVW using Tapatalk 2
Just to let everyone know what's going on right now, I want to make this ROM easy to maintain, and easy to contribute to. To that end, I'm currently in the process of merging every commit this ROM has into my github. It's a long, involved process, but I think it will pay off dividends when I'm done. Anyone will be able to view the code, and anyone will be able to contribute code for consideration. As I said in the OP, this might take a week or two, but I think it will really allow this ROM to come alive as a true community effort.
Sent from my ADR6425LVW using Tapatalk 2
I should be able to upload all that for you to mine. Let me know something. I can probablt do it tonight or tomorrow night. If that makes it easier
Also just to clarify it was a combo of both, nerve issues in my right leg ( going to see a specialist soon ) and lower back injuries that caused me to decide to pass this on. I cant sit at my computer desk for long periods of time. I am only too happy that I have some good friends and good people on this rom now.
Sent from my ADR6425LVW using Tapatalk 2
Also I will bve uploading a new version tonight. It was what I had already started and he can add it to the op whenever the changelog is only 2 things but they are fixes. heres is the changelog....
1) f/b: fix wrong qcom ifdef
2) Fix Issue 5547: Apollo will not play MP3 files when using Root Explorer
http://beta.androidfilehost.com/?fid=9390135922294522588
he can upload this version to the op and I am out fellows. I will also try to upload what I have to github for everyone else
dirty flash should be fine.
Bruce , thank you very much for the donation man. I really do appreciate it.
Just to note that the new build from apophis is up in the OP now.
Also, Neo is awesome. Just saying...
Things are going much faster on my end than I expected. No promises, but I should have the first new build up for you guys early next week. Have a few more commits I'm eyeing, so I'll try to finish getting everything in my git and get those new commits integrated and get a new build out. The new name will be debuting at that time as well.
Quick opinion poll: would anyone be upset if I took ROM Manager out of the build?
shrike1978 said:
Just to note that the new build from apophis is up in the OP now.
Also, Neo is awesome. Just saying...
Things are going much faster on my end than I expected. No promises, but I should have the first new build up for you guys early next week. Have a few more commits I'm eyeing, so I'll try to finish getting everything in my git and get those new commits integrated and get a new build out. The new name will be debuting at that time as well.
Quick opinion poll: would anyone be upset if I took ROM Manager out of the build?
Click to expand...
Click to collapse
Nope. Off with its head!
@shrike
Don't try brunching in my kernel . You won't have wifi. I am setting something up to keep using aokp's wifi
Sent from my ADR6425LVW using xda app-developers app
Snuzzo said:
@shrike
Don't try brunching in my kernel . You won't have wifi. I am setting something up to keep using aokp's wifi
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Yea, I already noticed.
I'll switch my manifest back to Chad's for now and put yours in post-build. Let me know when I can brunch again, and let me know if I need to pull in or revert some commits.
shrike1978 said:
Yea, I already noticed.
I'll switch my manifest back to Chad's for now and put yours in post-build. Let me know when I can brunch again, and let me know if I need to pull in or revert some commits.
Click to expand...
Click to collapse
Yeah what I'm thinking about doing is keep using AOKP's wifi for my own personal builds and revert with a cherry-pick whenever I build a kernel. Either that or setup another branch to pull from.
What you think? Might even be able to use the funky_kernel repo for brunching.
As that is setup to use HTC binaries from source. Not quite sure if that will break anything tho
Sent from my ADR6425LVW using xda app-developers app
Um... Guys... Experiencing random reboots on latest build. Could it be the governor? Currently using lazy.
Hey guys!
So from observations by @rkoby13 and myself, there seems to be a demand for regular builds of DorimanX's kernel!
This thread will serve as a place for logs, reports, and discussion relating to these unofficial builds by me.
Currently the plan is to compile v9 builds, whenever @dorimanx adds major updates or significant modifications to his source, however this may, and probably will, result in UNSTABLE AND EXPERIMENTAL RELEASES
Disclaimer:
Dori tests highly experimental commits prerelease, and if your device is damaged, wiped, or in any way negatively affected by these releases it's not the fault of Dorimanx, or me. In flashing these releases you accept full responsibility for any consequences of its use.
In this op, I'll have a log of which builds are most stable and which ones have bugs reported or major issues in code, and builds with extreme issues will be removed.
As x.39 was just released, the first build will be uploaded after the next major addition to the kernel sources, and every major change after that.
If there is a commit that I have not considered major but is important to you, either reply to the thread or pm me with a link to the commit, and I'll probably update the build to include it. In future, I may also build v8 kernels until their end of life, if many people show a desire for this
Finally, just a reminder not to post logs or reports/discuss these builds in any other thread, thanks
I'll also soon be adding my new and improved stweaks settings guide, nearly everything is covered now.
Source: http://github.com/dorimanx/dorimanx-SG2-I9100-Kernel
http://github.com/dorimanx/initramfs3
if anyone has a domain they'd like to offer to mirror I'd be glad (hint hint)
dorimanx has decided to help out with building sometimes, and he'll post here! and apparently no one reads whole op, is this big enough?
latest build by cybernetus http://www.dorimanx.ataliba.net
aaaaaand computoncio has a fileserver too now!
http://dorimanx.casoncia.org
Changelogs:
9.39
v1 - 23/8 up!
- ram value display fixed
- toggle to completely stop logcat from writing
(accidentally messed up defconfig and reset it so the kernel id is the same as usual but I renamed the zip)
v2 - 26/8 up!
-compiled with linaro 13.08 gcc 4.8.2 (tuned and optimised by dori for i9100 and his kernel)
- zzmoove updated to 0.7b
- cortex brain tuned and some bugs fixed
v3 - 27/8 up
-various driver updates, cleans and optimisations
v4 - 27/8 up
-as previous
-fix for reset profiles on boot
v5 - 29/8
-ton of pulled 3.11.y driver update
-cleaning
-more optimisations from stantrc (new dev )
-there was something else I saw but I forgot
9.40
v10 cybernetus - 9/9
- changelog
Eskriminal's New and Improved DorimanX Stweaks Guide!
Starting off, I will not be covering stock standard info such as cpu clock, voltage, or the most basic governor variables. @droidphile has a brilliant comprehensive guide to these things and more, search!
Now let's get started! This guide will be in the same order as stweaks itself, and if i miss anything that you wanted, pm me
Topic 1. Advanced/Custom Cpu Governor variables
Here will be discussed governors such as nightmare, darkness, and perhaps zzmoove (if i have time), and their variables.
Freq_step
this controls how large the step up should be when the cpu load hits either the up_threshold, or the inc_cpu_load, depending on your governor.
It is a percentage, where the percentage involved is that of the cpu clock prior to the switch.
Down_threshold/dec_cpu_load
same as up_threshold or inc_cpu_load, but in the reverse, these dictate at what load to decrease frequency
Cpu_up_rate/cpu_down_rate
these values determine how many readings of cpu load will be collected (i.e. 60% or 80%) before being compared to the inc_cpu_load or dec_cpu_load respectively
Freq_step_dec
the same as freq_step, but for decreasing frequency
Freq_step_dec_at_max_freq
identical to freq_step_dec, but while cpu is at values above freq_for_responsiveness_max
Up_sf_step/Down_sf_step
both have detailed descriptions in app from alucard
<more to come>
Topic 2. Memory Management
This tab in stweaks dictates whether Dorimanx kernel should control the Android memory management system (Auto Oom Control switch)
The settings here control how it should control it, with the more aggressive the setting, the quicker apps will be killed at low memory.
<more to come>
Topic 3. GPU Tab
The GPU settings are all identical in function to the way CPU control works, with the frequency steps available and voltage/threshold changes.
The GPU utilisation timeout controls how fast the gpu should respond to a heavy load.
With the thresholds, as with cpu the higher they are the slower it will scale frequencies up, and the faster it'll scale down.
<more details to come>
Topic 4. Screen Tab
Here all screen settings and brightness controls are changeable.
min_bl controls how fast auto-brightness should increase screen brightness level, when this value is higher the screen will stay on minimum brightness for longer.
min_gamma and max_gamma control the minimum and maximum brightness available to auto-brightness
LCD Power Reduce lowers screen brightness to save battery
Screen colour modes control colour levels
Gamma Shift changes all brightness system-wide up or down based on the value put in
FB early suspend delay controls delay after sleep should activate before running the screen off animation
Vibration force controls the power of vibrations system-wide
Slide2Wake toggles waking the device by swiping across the screen from left to right
mDNIe Negative Toggle enables or disables inverting colours by pressing the home button the number of times set below
Touch screen tweaks control sensitivity options - They're advanced, and usually don't need to be touched
Topic 5. Sound Tab
Most settings are self-explanatory, if anyone wants this actually explained, shoot me a pm.
Topic 6. Big Collection, all Misc. Kernel settings! (BLN, CRON, Logger, Auto wifi etc.)
BLN controls whether to switch on backlights when notifications are received during phone sleep.
The bln effect controls the light mode of these keys (doesn't work with BLN without wakelock)
Notification timeout controls the maximum length of time the keys should be on before turning off (doesn't work with BLN without wakelock)
LED timeout controls the timeout on backlight keys during phone use
BLNWW sets BLN to run without forcing the cpu to stay out of deep sleep, saving battery
LED fadeout controls the effect when the keys switch off
LED on touch determines whether the keys will turn on when pressed during use
LED voltage level controls the key brightness
CRON is a timed automatic service which can be used to run various optimisations and updates as detailed in the 'Other' tab in Stweaks
Fix Permissions may solve fcs in apps
Zipaligning apps may optimise them to run faster
Database optimising will clear and compact the system data, potentially increasing system performance
GPS zone changes to your local ntp server may decrease gps lock times and increase accuracy
USB settings control the device storage mount mode.
Charge current levels control speed of charging from various sources, with the higher the current, the faster the flow and therefore charge
Resetting the fuel guage chip may solve issues when battery appears to drop after reboots, as the chip will recalibrate
The Ad-blocker will block advertisements by ip in most apps
Filesystem tools attempt to recover corrupt partitions on the disk
Root settings control device root security
Cortexbrain controls the switching between various things based on screen state including cpu governor and clock, io scheduler, auto wifi, auto data, and logger control
The android logger writes logs of system errors, disable unless you plan on using this
auto data disables mobile data when the screen is off, with the delay before doing so below it (auto wifi is the same for wireless internet)
Various tweaks change system values relevant to each one
Eco tweaks modifies hotplugging logic when battery drops below the eco-level threshold to save battery by preferring use of only a single cpu core
This is just a preliminary guide, my corrupted hdd destroyed the other one I'd been writing for @rkoby13
Reserve one more! Just in case!
Sent from my GT-I9100 using XDA Premium 4 mobile app
and another at the recommendation above
Sent from my GT-I9100 using Tapatalk 2
Hehe, can't wait. This is an good idea.
Galaxy S2 powered by Dorimanx!
so what do you guys think of v8? want me to build it also?
Sent from my GT-I9100 using Tapatalk 2
Great idea
Posté via Vanilla Rootbox
Can you please build a dori Kernel for 4.3 where internal sd card is switched? Internal -> external.
Gesendet von meinem Galaxy S2 mit CM10.1
SWTR said:
Can you please build a dori Kernel for 4.3 where internal sd card is switched? Internal -> external.
Gesendet von meinem Galaxy S2 mit CM10.1
Click to expand...
Click to collapse
we'll see, unless many people want it it's probably not worth patching the changes in if I can
Sent from my GT-I9100 using Tapatalk 2
@eskriminal
can you just link to git where you build from?....or maybe build one kernel....if there are any new commits ....because place holders are not allowed at xda.....you need at least source link ma8 .....and keep up great job.....because last one you shared with me was awesome build.....although latest 9.39 is a beast.........waiting for new commits and build.....
rkoby13 said:
@eskriminal
can you just link to git where you build from?....or maybe build one kernel....if there are any new commits ....because place holders are not allowed at xda.....you need at least source link ma8 .....and keep up great job.....because last one you shared with me was awesome build.....although latest 9.39 is a beast.........waiting for new commits and build.....
Click to expand...
Click to collapse
edited op to include source and info for when downloads are up
Sent from my GT-I9100 using Tapatalk 2
hi guys..im using philz touch kernel..i want little more brightness ..so which kernel has got the maximum brightness ?? i dont have issues with battery drain
hunkyycbz said:
hi guys..im using philz touch kernel..i want little more brightness ..so which kernel has got the maximum brightness ?? i dont have issues with battery drain
Click to expand...
Click to collapse
any dorimanx build has gamma control in the screen tab on stweaks, raise it to increase brightness
Sent from my GT-I9100 using Tapatalk 2
I bought an optimus g for wife, but started to play with it, lock bootloader, hard to root, no custom kernel for oc. It's nice to see that s2 community it's still active.
Regarding domain, maybe ApriliaM3 from neatrom thread, he has an huge one with mods, kernels, rom.
http://d-h.st/users/ApriliaM3/?fld_id=8738#files
Galaxy S2 powered by Dorimanx!
Agreed. Nice to see the i9100 community still active
I have a question. What is a "V8" kernel and if its good stuff, why isn't included in Dorimanx official build? I'm assuming because of possible bugs?
StatusQuo209 said:
Agreed. Nice to see the i9100 community still active
I have a question. What is a "V8" kernel and if its good stuff, why isn't included in Dorimanx official build? I'm assuming because of possible bugs?
Click to expand...
Click to collapse
maybe you lost track....but dorimanx kernel has 2 branches....8.xx & 9.xx....
8.xx has support for Samsung stock JB roms...aswel as aosp/aokp/cm....<---4.2.2 and bellow...to 4.1.2...
9.xx branch supports 4.2.2 and 4.3 only...aokp/cm/aosp roms and dualboot between them....and with 9.xx you have more ram avaliable ....other things you can find in original dorimanx kernel thread....
v8, for official roms. v9, custom roms.
Dorimanx put sources in git daily and build his kernel. Anyone who could and want, take his sources and make an kernel, based on his sources. So, that's what we are here on this thread, we wait to grab and test an custom kernel
Galaxy S2 powered by Dorimanx!
rkoby13 said:
maybe you lost track....but dorimanx kernel has 2 branches....8.xx & 9.xx...8.xx has support for Samsung stock JB roms...aswel as aosp/aokp/cm....<---4.2.2 and bellow...to 4.1.2...
9.xx branch supports 4.2.2 and 4.3 only...aokp/cm/aosp roms and dualboot between them....and with 9.xx you have more ram avaliable ....other things you can find in original dorimanx kernel thread....
Click to expand...
Click to collapse
dude! I totally lost my mind. Lol. I totally got confused, I know there is a version 8 of the kernel. I was thinking that this was like the "V6 Supercharger" mod that some people use. I thought there was a new version or something that was kernel based. Hahaha. Thanks for clearing that up for me bud.
Excuse my ignorance...
StatusQuo209 said:
Agreed. Nice to see the i9100 community still active
I have a question. What is a "V8" kernel and if its good stuff, why isn't included in Dorimanx official build? I'm assuming because of possible bugs?
Click to expand...
Click to collapse
aaaaand V8.xx is official..,just like 9.xx
bugs(if any) are the same.....but 9.39 is.....<3
Here is an enhanced version of the battery gauge driver. It will likely work with all kernels. A couple of bugs have been fixed and new sysfs properties have been added. These changes are in large part based on enhancements of the Ubuntu battery gauge driver for the original Nexus 7.
The following new properties are added to '/sys/class/power_supply/battery/':
charge_now: remaining battery charge in uAh; compensated for load current/temperature (higher load current = lower usable capacity)
charge_avg: remaining battery charge in uAh; uncompensated
charge_full: charge in uAh, when battery is fully charged (as determined by battery gauge -> will go down as the battery ages)
charge_full_design: design value of battery charge (the capacity a new battery is supposed to have)
energy_now: remaining battery charge/energy in uWh; compensated for load current/temperature
charge_counter (signed value): coulomb meter measuring amount of charge that has flowed into or out of the battery; periodically set to 0, when battery has minimal load (e.g. on USB power and fully charged or during deep sleep)
power_now (signed value): amount of power flowing into or out of battery in uW (updated by the gauge every second); useful to see how fast/with how much power the battery is being charged
cycle_count: battery charge cycle count; around 4000mAh worth of charging correspond to a full cycle (e.g. when the battery is charged 50% = 2000mAh two times, you get a full cycle)
Reading the sysfs properties results in the battery gauge driver requesting the current value via I2C from the battery gauge. AFAIK, the I2C transaction uses software I2C and will block the CPU for a few dozen micro seconds.
A public datasheet for the battery gauge exists:
http://www.ti.com/lit/ds/symlink/bq27541.pdf
Disclaimer: The changes are not extensively tested and missing locking has been added to the driver (previously, concurrent requests via sysfs could result in wrong values) - there may be deadlocks lurking. The driver plays a role in controlling the battery charger, use it at your own risk (if your N7 burns and takes your house with it, don't come running to me).
Feel free to submit these changes to Google, I won't. The Ubuntu enhancements for the original N7 were submitted in January and have been ignored.
reserved
This looks awesome!
Sent from my Nexus 7 using xda app-developers app
This sounds interesting, I don't know if it is though!
Sent from my 2014 Nexus 7 using Tapatalk 4.4
For the non-kernel developers a bit more explanation. This is a kernel patch that modifies the battery gauge driver.
The kernel exposes certain information via sysfs, which is a virtual file system. If you have a kernel with this patch, you can open a terminal window and do something like:
Code:
cd /sys/class/power_supply/battery/
cat power_now
This will print the current amount of power used (in micro-Watt). You can also use a root-capable file browser (e.g. ES Explorer) to look at the sysfs files; you can open /sys/class/power_supply/battery/power_now like a 'normal' file (same thing with other properties mentioned in the first post).
If you want to try this, ElementalX 1.6 beta has this patch applied:
http://forum.xda-developers.com/showpost.php?p=45944453&postcount=1034
tni.andro said:
For the non-kernel developers a bit more explanation. This is a kernel patch that modifies the battery gauge driver.
The kernel exposes certain information via sysfs, which is a virtual file system. If you have a kernel with this patch, you can open a terminal window and do something like:
Code:
cd /sys/class/power_supply/battery/
cat power_now
This will print the current amount of power used (in micro-Watt). You can also use a root-capable file browser (e.g. ES Explorer) to look at the sysfs files; you can open /sys/class/power_supply/battery/power_now like a 'normal' file (same thing with other properties mentioned in the first post).
If you want to try this, ElementalX 1.6 beta has this patch applied:
http://forum.xda-developers.com/showpost.php?p=45944453&postcount=1034
Click to expand...
Click to collapse
any others aswell?
{
"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"
}
MeanPop for the Nexus 6!
MeanPop is built on stock 5.1.0 base (LVY47H)
TOP FEATURES
Color Battery %
Green battery when charging (% still visible while charging)
Time w/seconds and date on ambient display and lockscreen
Native notification LED
No special kernels or apps needed: the LED "just works"
Supports LED color (chosen in any app)
Flashing or solid LED (configurable - see post 2)
User configurable LED color priority system! (see post 2)
Can be turned off completely in build.prop (last line)
MEANPOP GOALS
----------------------------------------------------------------------------------------------------------------------------
To be clean: mostly stock look and feel
To be mean: apply optimizations for smoother performance
To be nice: provide cool functionality not present in the stock base
VIDEOS
----------------------------------------------------------------------------------------------------------------------------
Thanks Mike for the great video review!
NEWS/HAPPENINGS
----------------------------------------------------------------------------------------------------------------------------
v2.15 - Added color battery text (configurable, see post 2) and reduced contrast "Android is starting..." dialog to reduce screen burn-in
ROM/RADIO CONFUSION?
We developers are still getting a handle on exactly what changes were made in LMD47D, E, M, I and LVY57H and which radio works best for which carrier. Keep in mind that this ROM will run with any of those radios, just be sure to use the radio that is best for your carrier. You are likely to get service on any carrier using any of the three available bootloaders/radios but based on feedback in multiple threads and user testing, it is my recommendation that:
- T-Mobile users use the LMY47M bootloader/radio (flash via TWRP - thanks @scrosler)
- Everyone else use the LMY47E bootloader/radio (batch file: flash via fastboot - thanks @scrosler)
NEED A PROXIMITY SENSOR FIX?
MeanPop v2.09 now has the proximity sensor fix built in: you will not have proximity sensor issues with this ROM!
For those running other 5.1 ROMs, some users are experiencing problems with the increased sensitivity of the proximity sensor on 5.1 ROMs and are cutting, removing, or buying new screen protectors to fix the problem. This is no longer necessary! Just download my proximity sensor fix. It should fix your proximity sensor on any 5.1 stock based ROM. Installation is simple: just install your ROM and then flash the fix over top.
SECTION I: ROM SPECS
The clean:
Built on stock 5.1.0 LVY47H
Smooth and stable (I don't release betas)
User configurable options (see post 2) - set once and they stick through updates: no weeding through Aroma settings with each update!
The mean:
Performance tweaks
Screen on/off performance and battery tweaks for snappier UI and better battery
The nice:
Rooted (SuperSU)
Non-forced encryption
init.d support
Signature checking disabled
De-odexed for your modding pleasure
Zipaligned
6 way power/reboot menu (includes ability to turn off ambient display when you pick up the phone - useful when phone is in a moving vehicle)
To disable ambient display activation due to movement when in a vehicle, long press power and check the box for "Ambient Pickup OFF" (ambient display will still light for incoming notifications)
Re-enable ambient display on pickup with a long press on power, then check "Ambient Pickup ON"
Built in proximity sensor fix: you will not have the black-screen-in-calls issue with this ROM and your ambient display will work
Fixed low/inconsistent initial volume of ringtones and alarms (5.1 bug)
Clear all recent tasks
Battery % on status bar
Battery % on ambient display
Color battery text: white --> yellow --> red based on battery level (configurable - see post 2)
Ability to disable proximity sensor for those having black screen issues in calls on 5.1 ROMs (see post 2)
Ability to disable proximity sensor for ambient display (see post 2)
Native notification LED w/color support (solid or flashing - see post 2)
User configurable LED color priority: make your most important colors "stick" (see post 2)
Native LED can be turned off by modifying the last line in /system/build.prop (debug.nativeled=false)
Set your own LED blink rates (on/off times) in /data/meanpop.opt (see post 2)
Fast blinking blue LED for missed calls
Quick flash charging LED (red = charging, green = full, see post 2)
Ability to turn on/off LED notifications from the power menu (now you can sleep without the blinking and still see status when you turn notification LED back on)
Volume boost mod: thanks @scrosler
Reduced navigation height for more screen real estate (configurable: see top of post 2)
Adaptive brightness adjustments (brighter in bright light such as outdoor indirect sunlight)
Ambient notification - longer display time and slower fade-out
Ambient notification motion sensing improvements (display activates more consistently)
Ambient display lights once for each new notification instead of each notification reactivating the display several times over several minutes
Ambient display works indefinitely instead of stopping after 3 notifications
Ambient display shows time w/seconds and date
Fixed (stock) bug where ambient display can be up to several minutes slow
Double tap home for screenshot
Hold back button for screen off
Battery %
Battery green when charging, shows % while charging
Bonus ringtones, notifications, and alarms from other devices
Stock Android so no carrier bloatware (you'll have to install that yourself)
This is based on Google stock: so gapps already installed
More to come...
Changelog is in post #2
Problems?
Everything has been tested and is working based on initial tests. Since 5.1.0 is a new base, however, if you run into any problems, please just reply in this thread and I'll check into it.
Credit where credit is due:
As with any open source stuff, some of this work is my own and some comes from other sources. So in addition to my own work (mostly in the "mean" category), here's a quick thanks to those of you who contributed knowingly (thank you) and not-so-knowingly via open source 5 finger discount (thank you just the same: your stuff is good and that's why I used it). Sometimes it's not entirely obvious where the source started so if I missed someone, please let me know and I'll add you. Also, I'm careful to only include other work where the author does not specify any usage restrictions or has given approval. If you believe, however, that I've included something that shouldn't be in this ROM, please just PM me.
@scrosler: I started with your stock 5.1 LVY47H odex ROM, so thank you!
@scrosler for your help on the clear all recent tasks mod
Thanks @r4wOne for the MeanPop logo
Want my stuff?:
I list credits in the features section above and links to original works: if you see something credited there and you want to use it, click the link and seek permission from the developer I've credited. If you see something in this ROM and I don't reference some other source, I probably coded it myself. If you want it: take it and use it in your ROM, your theme, whatever you like. I just ask that you please credit me. I'm a firm believer in Android and open source so you don't even have to ask. Anything you see here... it's yours for just the price of a simple line crediting me. I always share as I believe that's the way we developers put the power in Android... and one way we can fight "the Apple brainwashing machine".
SECTION II: FLASHING NOTES
Below are some pointers on flashing before we get to the good stuff (installation and downloads).
Problems after you flash?:
PLEASE DO NOT REPORT PROBLEMS IN THIS THREAD UNTIL you've done a full wipe and fresh install to see if that cures it. I know I should really just do like most devs and proclaim REQUIRES FULL WIPE/FRESH INSTALL on every version. That saves me a lot of headaches but I know what a PITA a fresh install can be even with MyBackup or Titanium at your disposal. So it never hurts to try just a flash without a full wipe, but if you run into any HINT of a problem... anything at all... don't report the problem in this thread until you've tried a full wipe and fresh install first to see if that cures the problem!
Note regarding tweaks: don't flash tweaks or themes on top unless you KNOW the tweak/theme is compatible with the the 5.0.1 base
Flashing - a final note:
Use this ROM at your own risk as I won't be responsible for bricks or any other untoward happenings. I spent a lot of time ensuring that the stuff in this ROM is fast, smooth, and compatible. But... it always helps to have some familiarity with flashing ROMs to keep yourself safe. If you're starting from stock, be sure to familiarize yourself with the unlocking/rooting process (from other threads) before flashing this ROM.
SECTION III: INSTALLATION
Download links are below
Now to installation of the ROM itself...
Always make a backup before installing anything on your phone!
Make sure you already have the proper bootloader/radio installed: I recommend T-Mobile customers use @scrosler's LMY47M radio/bootloader (flashable ZIP) and everyone else use his LMY47E bootloader/radio (fastboot batch file).
On first install of MeanPop, do a full wipe (although if you are coming from a stock 5.0.1 or 5.1.0 base, you can try a dirty flash).
Subsequent updates: no wiping necessary BUT...
If you have any trouble at all, do a full wipe and then reinstall
Install using recovery (I use latest TWRP)
SECTION IV: DOWNLOAD
... you're gonna break it!
Don't flash any other mods, tweaks, or themes unless they specifically say they are built for (the latest version of) MeanPop or you WILL break features in this ROM and/or cause instability! While this ROM is designed to have the general look/feel of the stock ROM, it is highly customized under the hood and mods, tweaks, or themes not designed specifically for this ROM will cause problems. If you want this ROM to run perfectly without any issues, do not flash anything on top.
NEW releases (5.1.0):
Note: coming from MeanPop v1.x, v2.x (or any stock based 5.0.1 or 5.1.0 ROM for that matter): YES! You can dirty flash! But if you run into problems, please factory reset and install fresh before reporting issues.
Just remember to flash the 5.1 radio/firmware before flashing MeanPop v2.x.
Download from Android File Host
OLD releases (5.0.1):
Download from Android File Host
DONATIONS
Click to Donate
Donations are greatly appreciated! If you use this ROM as your daily driver, please consider contributing. This development takes time from my regular job so more contributions = more of my time.
Mike
OPTIONS AND CONFIGURING:
(scroll down for changelog)
Options (flashable ZIPs):
Look in your /data/MeanPop folder
stock-nav-bar.zip - flash this to restore stock navigation bar height
stock-proximity-5.1.zip - flash this if you have no trouble with the proximity sensor on 5.1 ROMs and you'd rather use the stock 5.1 proximity sensor code
CPU optimizations:
If you are running a custom kernel, I would recommend turning off the CPU optimizations. Open /data/meanpop.opt and set:
CPUOPT="false"
Color Battery Text
If you would rather have plain white battery text instead of the default color-level text, open /data/meanpop.opt and set:
BATTCOLOR="false"
Configuring the LED options:
Flashing notification LED and user configurable color priority is now available:
- Use Root Explorer or other root file explorer and open /data/meanpop.opt and edit parameters to your liking
- Set priorities so your more important LED colors stick and are not overwritten by lower priority colors
- Priority 9 will never overwrite priority 8, priority 8 will never overwrite priority 7, and so on
- Keep all priorities set to the default 9 if you don't care and always want to see the most recent notification color
- Default LEDBLINK mode is "auto" = LED will blink as long as there are not more (different) color notifications "underneath". If multiple color LED notifications exist, the LED goes solid.
- When LEDBLINK is set to "true", the LED always blinks
- When LEDBLINK is set to "false", the LED will always be solid
- You can open /data/meanpop.opt and change the blink rate (ON ms and OFF ms - see last two lines in that file)
- Don't go crazy with the blink rates: I recommend keeping the on and off periods at 500ms or higher
- New: LEDCHARGEMS controls how long the LED flashes when charging (red = charging, green = full). Set LEDCHARGEMS=0 to disable charging LED flash.
Notes on native LED... should you use it?:
The native notification LED built into this ROM needs a wake lock to run the LED, but only when the LED is actually on or blinking. Even with nativeled enabled, the phone will deep sleep as long as the LED is off but when the LED is on (solid or flashing), a wake lock is acquired and your phone will use slightly more battery. The difference in battery usage, however, is minimal and the fraction of extra battery used to run the LED is well worth the feature! Even with the LED on or blinking constantly, your phone will typically use only around 1% battery per hour with the screen off/idle.
If you don't plan to use the LED at all, I would recommend opening /data/meanpop.opt (you can do that with something like Root Explorer), and changing this line:
NATIVELED="false"
CHANGELOG
v2.15 released Apr 20
Added color battery text (configurable, see above) and reduced contrast "Android is starting..." dialog to reduce screen burn-in
v2.14 released Apr 13
Added ability to turn on/off notification LED from the power menu
v2.13 released Apr 11
Fixed LED so that it goes out after deleting or archiving an email from Gmail notification
Added volume boost mod: thanks @scrosler
v2.12 - pulled due to LED bug
v2.11 released Apr 6
Fixed low/inconsistent volume of ringtones and alarms (5.1 bug)
Fixed ability to turn off native LED (see above)
v2.10 released Apr 2
Rebased to LVY47H
v2.09 released Apr 1
Added ability to turn ambient display off when the phone is moved/picked up: long press power button and select "Ambient Pickup OFF"
Added ability to turn off CPU optimizations: useful when running custom kernels (see above for setup)
Built-in the proximity sensor fix
v2.08 released Mar 29
Added battery % to ambient display and replaced battery icon with battery % in status bar
v2.07 released Mar 28
Added quick flash LED for charging (see above for options)
Added ability to disable proximity sensor for ambient display (see above for options)
v2.06 released Mar 27
Fixed some minor issues with LED notifications and updated system apps to latest
v2.05 released Mar 25
Added ability to disable proximity sensor during calls for those having black screen issues (see above)
Updated some system libraries
v2.04 released Mar 24
Updated to LMY47M (all-carrier compatible) and updated all system apps
v2.03 released Mar 21
Added clear all recent tasks
Improved LED notifications so that the phone deep sleeps: wake lock is only used when the LED is actually on (solid or flashing)
Removed the second/small time display on the ambient display/lockscreen
Zipaligns all apk's and jar's
v2.02 released Mar 18
Update to LMY47E base
v2.01 released Mar 17
Added 4 way power/reboot menu
Reduced navigation bar height to increase screen real estate
Reduced home button lag
v2.0 released Mar 16
Upgrade to 5.1.0 base
v1.08 released Mar 8
Changed LED code to improve reliability
Added a flashable zip in /data/MeanPop to revert to solid signal bars
v1.07 released Mar 7
Improved clock on ambient display
Fast flashing blue LED for missed calls: never let a missed call go un-noticed!
v1.06 released Mar 5
LED notification reliability improvements
Ability to set blink rates (on/off times): see above
v1.05 released Mar 4
Ambient display shows time w/seconds and date
Fixed ambient display time lag bug (bug exists in stock ROM) where ambient display could show time up to several minutes slow
Improved native LED reliability
v1.04 released Mar 2
Fixed random blue notification LED that was popping up on rare occasions when another color LED is already lit
Improved the nativeled=false in build.prop for people who want their device to deep sleep and don't mind losing the LED (see above)
v1.03 released Mar 1
Fixed status bar signal meter transparency
Improved some boot parameters: should take care of any "storage space is running out" messages that a few people were seeing
v1.02 released Feb 28
Made changes to the native LED code to make it non-stock-kernel friendly
v1.01 released Feb 28
Ambient display lights once for each new notification instead of each notification reactivating the display several times over several minutes
Ambient display works indefinitely instead of stopping after 3 notifications
Fixed a bug that was causing long press back to sometimes not turn off the screen
v1.0 released Feb 27
LED blinking/solid options
LED color priority settings
Instant screen on (zero wake lag)
v0.3 released Feb 25
Improvements to native LED code
/data/meanpop.log that shows LED and screen on/off status messages
Updated superuser binaries
v0.2 released Feb 24
Native notification LED w/color support (solid only, no flashing)
Native LED can be turned off by modifying the last line in /system/build.prop (debug.nativeled=false)
Adaptive brightness adjustments (brighter in bright light such as outdoor indirect sunlight)
Ambient notification mods - longer display time and slower fade-out
Ambient notification motion sensing improvements (display activates more consistently)
Nice to see another option for stock based. I'll have to try it out.
Sent from my SinLess Shamu
Can you list exactly what your "performance tweaks and battery tweaks" are?
Hey I remember you.wasn't your ROM one of the more popular ROMs from the evo 3d?
Sent from my Nexus 6 using Tapatalk
mikeyxda said:
reserved
Click to expand...
Click to collapse
shizkoff777 said:
Hey I remember you.wasn't your ROM one of the more popular ROMs from the evo 3d?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Welcome to Nexus 6 Mikey! Fellow meanbean user from the EVO 4G LTE days.... Good times! Will be sure to Flash [emoji3] [emoji106]
antiochasylum said:
Can you list exactly what your "performance tweaks and battery tweaks" are?
Click to expand...
Click to collapse
Basically...
While screen is on:
- Stock 300Mhz - 2.6 Ghz CPU scaling
- Slightly lower than stock CPU up-threshold: 80%
While screen is off:
- Lowered 300Mhz - 1.6 Ghz CPU scaling
- Stock CPU up-threshold: 90%
Mike
shizkoff777 said:
Hey I remember you.wasn't your ROM one of the more popular ROMs from the evo 3d?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yeah. I started with the Evo 3D and then developed for the Evo 4G LTE and later the Samsung Galaxy Note 2. I'm on the Nexus 6 now: figured it was time for a true Android device.
Mike
With stock kernel right? Forced encryption?
Sent from my Nexus 6 using Tapatalk 2
mikeyxda said:
Yeah. I started with the Evo 3D and then developed for the Evo 4G LTE and later the Samsung Galaxy Note 2. I'm on the Nexus 6 now: figured it was time for a true Android device.
Mike
Click to expand...
Click to collapse
I remember you. I ran your Vzw note 2 rom on my note. It was a great rom. I'm gland to see you here.
janjan said:
With stock kernel right? Forced encryption?
Sent from my Nexus 6 using Tapatalk 2
Click to expand...
Click to collapse
Stock kernel, decrypted (not forced). I haven't played with decrypting my device though: mine is encrypted.
Mike
Changelog?
mikeyxda said:
Yeah. I started with the Evo 3D and then developed for the Evo 4G LTE and later the Samsung Galaxy Note 2. I'm on the Nexus 6 now: figured it was time for a true Android device.
Mike
Click to expand...
Click to collapse
Yeah i after the nexus 5 I didn't won't another HTC or Samsung device.well its good seeing you here
Sent from my Nexus 6 using Tapatalk
Mikey knows his stuff. I remember his killer rom on the VZW Note 2. Thanks for this rom, Mike!
Oh my god I haven't seen you since the early days of the note 2! You were the first dev I ever donated to. Wow this is awesome. I loved that status bar gradient you had
Clear All and Power Menu....?
Welcome Mikey! I ran nothing but MeanBean on my EVO4GLTE. Glad to see you made the move to Nexus device.
Mervingio said:
Clear All and Power Menu....?
Click to expand...
Click to collapse
Power menu is provided in the included Quick Boot app. I find that faster and easier than using the power button anyway (plus it saves your power button) but my intent is to not code stuff that already exists. That way I have time to do the stuff no one has done yet... and I don't have to redo it every time there is a base update.
As for clear all, I personally don't see any need for it: let the OS do what it does. But if lots of people want it, I can look into coding it.
Mike
Alright downloading this finally
Welcome to this awesome phone!! This ROM sounds promising from the other comments I've read, can't wait to flash it!