<DISCONTINUED>[KERNEL][KK4.4]Notest Kernel with Linaro 4.8 and aries-cma

<DISCONTINUED>[KERNEL][KK4.4]Notest Kernel with Linaro 4.8 and aries-cma - Epic 4G Android Development

Warning!
- This is not a stable (enough) build, (but) a random reboot or system hang (still) may occur
- Default color tweaked with darker look, this use color multiplier value from samurai kernel + my gamma set
this can be set in bbelos unofficial build. In official nightly this can be set from terminal or root explorer in this folder:
/sys/class/misc/color_tuning/
- Video capture & playback (cma problem with or without ksm) mostly working.
In rare condition it need long time to start (5 minutes or more).
You can wait it if you have time (recommended) or simply restart your phone.
- Kexec not supported!
- Maybe some more...
Features and changelogs:
build 20140401
Compiled on this HEAD
- Update iniram & cwm from 20140331-NIGHTLY
- Enable KSM_CHECK_PAGE
- Enable Advanced TCP Congestion Control
build 20140324 for 20140323-NIGHTLY and newer
- Update initram & cwm from 20140323-NIGHTLY
build 20140315 for 20140307-NIGHTLY and newer
Compiled on this HEAD
- Add 2 patches to improve swap & revert aries-common: zRAM: only read one page at a time.
This time I prefer this kernel doc:
Code:
It is a logarithmic value - setting it to zero means "1 page", setting
it to 1 means "2 pages", setting it to 2 means "4 pages", etc.
Zero disables swap readahead completely.
The default value is three (eight pages at a time). There may be some
small benefits in tuning this to a different value if your workload is
swap-intensive.
Lower values mean lower latencies for initial faults, but at the same time
extra faults and I/O delays for following faults if they would have been part of
that consecutive pages readahead would have brought in.
over aosp guide:
Code:
By default, the Linux kernel swaps in 8 pages of memory at a time.
When using ZRAM, the incremental cost of reading 1 page at a time is negligible and may help in case the device is under extreme memory pressure.
To read only 1 page at a time, add the following to your init.rc:
`write /proc/sys/vm/page-cluster 0`
build b4 march for 20140228 nightlies and older
Compiled at this kernel HEAD and initram
build 20140313 for 20140307-NIGHTLY and newer
Builded at this HEAD
- Switch cflag from -Og (reverted to -O2 then) to -O3, the kernel size was much bigger & reduce user RAM to 416MB
- Use newer linaro toolchhain 14.02
- Add aries-common: zRAM: only read one page at a time
imo default linux value will give better performance, but I prefer to follow aosp guide like in stock cm-11 for galaxysmtd.
build 20140310 for 20140307-NIGHTLY and newer
- Add 1100 oc step from mackay, full charge indicator from sc-02b and 2 other commits
build 20140308 for 20140307-NIGHTLY and newer
- Use ramdisk 0307 nightly with 144mb zram (stable enough)
build 20140305
Kernel changes in here + ramdisk 0228 nightly with 256mb zram (not stable)
- if you find phone service crash, maybe I need to update the initram soon
- default color tweaked with darker look, this use color multiplier value from samurai kernel + my gamma set
this can be set in bbelos unofficial build. in official nightly this can be set from terminal or root explorer in this folder:
/sys/class/misc/color_tuning/
- Video capture & playback (cma problem with or without ksm) mostly working, but in rare condition it need long time to start (5 minutes or more).
You can wait it if you have time (recommended) or simply restart your phone.
- add 2 commits from codeaurora I found in cm gerrit for other device to improve zram & I increase zram size to 256mb. this lead the kernel to more unstable, will fix this in next build
- kexec hardboot code removed (not only disable)
- other minor things
build 20140226
- Add 2 video for linux commits, ARM uaccess & merge android-3.0 aosp
build 20140219
- 1.2ghz OC step
- 417mb memory from pawitp cma-test
- Color & Gamma Calibration support for CM-11 Unofficial
- KSM support, off by default & recommended to disable
- aries-common: increase zRAM to 128 MB
- Kernel config for smaller kernel size (mostly taken from semaphore kernel for i9000 by stratosk)
- Merged to aosp android-3.0 kernel common
- Update gpu driver to DDK [email protected] (as on mackay kernel and others for i9000)
- Compiled with linaro-toolchain-binaries 4.8 (32bit)
- Older CWM from Preview CM-11
- Display boot progress, zcache, lz4, etc.. as commited here
Install Instruction:
- Already on CM-11 is required & unofficial build with color calibration is recommended.
- Flash from CWM or TWRP as usual
Download:
http://goo.im/devs/didhiy/sph-d700_cm-11.0
tips: check (sort by) modification time to find the latest build
Source:
- Kernel
- Ramdisk
Credits:
- bbelos
- pawitp
- zman0900
- marcusant
- stratosk
- kasper_h
- derteufel1980
- all former epic4g devs
- all aries variant devs and community

didhiy said:
Warning!
Download:
http://goo.im/devs/didhiy/sph-d700_cm-11.0
tips: check (short by) modification time to find the latest build
Click to expand...
Click to collapse
Typo, you put "short by" it's sort by.

epicboy said:
Typo, you put "short by" it's sort by.
Click to expand...
Click to collapse
thanks fixed now
btw, I just realized that no more "isaint" in kitkat era

didhiy said:
thanks fixed now
btw, I just realized that no more "isaint" in kitkat era
Click to expand...
Click to collapse
What's "isaint"? I'm kinda new here lol.

epicboy said:
What's "isaint"? I'm kinda new here lol.
Click to expand...
Click to collapse
I own epic4g in late ics era the time where nyan, shadow & samurai kernels bring us so many performance tweak with they're own style
Not old enough to know the story behind "isaint" but I found the "truth" here LOL
http://forum.xda-developers.com/showthread.php?t=1809731

Nice. How's the boot time improvement with lz4?

Also, unless my original issues happened to get fixed along the way, I might recommend reverting this one. https://github.com/didhiy/android_k...mmit/d54908fa8d8574e1e424fd4db3a4fd3be3d580d0
I ran into a lot of problems (reboots, etc) before forcing FIQ. And when I tried to debug it by adding no_console_suspend, the rest of the issues magically fixed themselves, which probably points to a race condition. But since the reboots were gone, I just left it in. I'm curious if it helps your instability.

bbelos said:
Nice. How's the boot time improvement with lz4?
Click to expand...
Click to collapse
actually I only use it for initram (rd_lz4) not the kernel, since in aries it will create big kernel size over 8mb. never try it in epic yet
bbelos said:
Also, unless my original issues happened to get fixed along the way, I might recommend reverting this one. https://github.com/didhiy/android_k...mmit/d54908fa8d8574e1e424fd4db3a4fd3be3d580d0
I ran into a lot of problems (reboots, etc) before forcing FIQ. And when I tried to debug it by adding no_console_suspend, the rest of the issues magically fixed themselves, which probably points to a race condition. But since the reboots were gone, I just left it in. I'm curious if it helps your instability.
Click to expand...
Click to collapse
I have random reboot with it enable before, so I think somewhere in my other commit cause the trouble
my best guess, the problem came from "full charge indicator from sc-02b" so I revert it & seems run much stable now (can pass 3 days uptime)

didhiy said:
actually I only use it for initram (rd_lz4) not the kernel, since in aries it will create big kernel size over 8mb. never try it in epic yet
Click to expand...
Click to collapse
Just a thought for now, but we might be able to get away with shrinking the recovery partition to increase the boot partition. The recovery.bin can be made smaller if needed. It's 6mb right now, but there's a LOT that can be trimmed out. I started reading about lz4 last week, but haven't had a chance to pull in any patches to test. I think that'd be worth trying though.
EDIT: Actually, cdesai reminds me that changing the boot/recovery partitions is probably a bad idea, due to the bml over mtd business. Need to keep the offsets where they are.
Also, I've been curious about testing out pawitp's cma patches for a while now. I know he says it's not stable yet, but the extra ram is intriguing.

Testing the cma patches in a cm kernel now, with 408MB ram. Gonna see what blows up. Video playback was a bit funky, but it fixed itself after a reboot so not sure what that was about.

bbelos said:
Testing the cma patches in a cm kernel now, with 408MB ram. Gonna see what blows up. Video playback was a bit funky, but it fixed itself after a reboot so not sure what that was about.
Click to expand...
Click to collapse
I add some patches from codeaurora & linux-next here:
https://github.com/didhiy/android_kernel_samsung_aries/commits/cma-test
you can abandoned the ksm things & some part maybe useless or unrelated, but at least video capture almost never failed for me with ksm disable
maybe you can find some idea to improve the allocation failure thing (one of pawitp to do list)

Notest are back to kitkat
Just curious, Why you were rebranding nitest to notest?
Sent from my Nexus 5 using xda app-developers app

Dropple said:
Notest are back to kitkat
Just curious, Why you were rebranding nitest to notest?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
it happened by an accident usually I change the branch name because it's difficult to apply new patch to the recent branch (too many commits to revert back)
in the beginning of notest commit, I've plan to create a stable branch without too many additions.. but I can stop myself to try something & too lazy to switch between branches so, here it is the "no-test" became "ni(ghtly) test" & going further with experimental cma, lz4, zcache etc... it should be "nu(tty crazy) test" in essential

Hey didhiy,
Add all the Crypto commits from Linaro here: https://github.com/xboxfanj/kernel_msm/commits/xb/arch/arm/crypto and topology here: https://github.com/xboxfanj/kernel_msm/commits/xb/arch/arm/kernel/topology.c and https://github.com/xboxfanj/kernel_msm/commit/28e4da175964a7f9f07c894faebe4805528f6c40 https://github.com/xboxfanj/kernel_msm/commit/9687d1d3805ed51a342b4290bff8984a50decb3b https://github.com/xboxfanj/kernel_msm/commit/175cea2c517f08b97aa5cde16a33623f51cde7b6 https://github.com/xboxfanj/kernel_msm/commit/143c6b536ee7a9e5256431de209aaf06e5704ec1 https://github.com/xboxfanj/kernel_msm/commit/1d55b62f2fef82d9113321d02728cbeda6620ecf https://github.com/xboxfanj/kernel_msm/commit/c219c0fd75543ccf5c998fcdca3483b1e8f53e56 https://github.com/xboxfanj/kernel_msm/commit/43ab731f3feb1ab9ae05e168bbe721e00983456c https://github.com/xboxfanj/kernel_msm/commit/0ce8a298dd86268af5fdb68557f8f374c577bccf
and the power efficient workqueue commits on this page: https://github.com/xboxfanj/kernel_msm/commits/xb?page=12
Should make the kernel a bit smoother and more battery friendly
As far as KSM being broken, may as well disable it in defconfig. For default color, either change the gamma values in the kernel or tweak MDNIE.
Other than that, nice job

xboxfanj said:
Hey didhiy,
Add all the Crypto commits from Linaro here: https://github.com/xboxfanj/kernel_msm/commits/xb/arch/arm/crypto and topology here: https://github.com/xboxfanj/kernel_msm/commits/xb/arch/arm/kernel/topology.c and https://github.com/xboxfanj/kernel_msm/commit/28e4da175964a7f9f07c894faebe4805528f6c40 https://github.com/xboxfanj/kernel_msm/commit/9687d1d3805ed51a342b4290bff8984a50decb3b https://github.com/xboxfanj/kernel_msm/commit/175cea2c517f08b97aa5cde16a33623f51cde7b6 https://github.com/xboxfanj/kernel_msm/commit/143c6b536ee7a9e5256431de209aaf06e5704ec1 https://github.com/xboxfanj/kernel_msm/commit/1d55b62f2fef82d9113321d02728cbeda6620ecf https://github.com/xboxfanj/kernel_msm/commit/c219c0fd75543ccf5c998fcdca3483b1e8f53e56 https://github.com/xboxfanj/kernel_msm/commit/43ab731f3feb1ab9ae05e168bbe721e00983456c https://github.com/xboxfanj/kernel_msm/commit/0ce8a298dd86268af5fdb68557f8f374c577bccf
and the power efficient workqueue commits on this page: https://github.com/xboxfanj/kernel_msm/commits/xb?page=12
Should make the kernel a bit smoother and more battery friendly
As far as KSM being broken, may as well disable it in defconfig. For default color, either change the gamma values in the kernel or tweak MDNIE.
Other than that, nice job
Click to expand...
Click to collapse
thanks, will try to apply the patches soon :thumbup:
yeah, I think disable ksm for next build is the best solution
since you mention mdnie, I just remember that I used mdnie from aries kernel that have 6 modes configurable from sysfs, will try them one by one first... if still looks ugly maybe I'll revert it too

@didhiy
I've been using your notest....20140226-cma.zip with the CM11 Nightlies until today's. Flashes OK but on reboot keep getting android phone stopped errors. Also, happens with the one dated 20140120.
:crying: Please....I need that extra 200Mhz
Seriously, Just an FYI.
Thanks
Sno

Snoshrk said:
@didhiy
I've been using your notest....20140226-cma.zip with the CM11 Nightlies until today's. Flashes OK but on reboot keep getting android phone stopped errors. Also, happens with the one dated 20140120.
:crying: Please....I need that extra 200Mhz
Seriously, Just an FYI.
Thanks
Sno
Click to expand...
Click to collapse
I still on nightly 0228 rom, got no phone crash
If you have older nightly, I suggest you try install again on top of it
afaik, there's qcril things in some newer nightly that broke old ril like in i9000 (maybe epic too)

didhiy said:
I still on nightly 0228 rom, got no phone crash
If you have older nightly, I suggest you try install again on top of it
afaik, there's qcril things in some newer nightly that broke old ril like in i9000 (maybe epic too)
Click to expand...
Click to collapse
Saw this in the merge list for the next nightly, maybe the phone crash got fixed.

mbellot said:
Saw this in the merge list for the next nightly, maybe the phone crash got fixed.
Click to expand...
Click to collapse
I got an info from semaphore s1 kernel thread that said need to update initram to fix phone service
I read this just after upload a new build

build 20140308
Features and changelogs:
build 20140308
- Use ramdisk 0307 nightly with 144mb zram (stable enough)
build 20140305
Kernel changes in here + ramdisk 0228 nightly with 256mb zram (not stable)
- if you find phone service crash, maybe I need to update the initram soon
- default color tweaked with darker look, this use color multiplier value from samurai kernel + my gamma set
this can be set in bbelos unofficial build. in official nightly this can be set from terminal or root explorer in this folder:
/sys/class/misc/color_tuning/
- Video capture & playback (cma problem with or without ksm) mostly working, but in rare condition it need long time to start (5 minutes or more).
You can wait it if you have time (recommended) or simply restart your phone.
- add 2 commits from codeaurora I found in cm gerrit for other device to improve zram & I increase zram size to 256mb. this lead the kernel to more unstable, will fix this in next build
- kexec hardboot code removed (not only disable)
- other minor things

Related

[Kernel]netarchy-toastmod, Stable: 4.3.1 Beta: 4.3.4 (17-Mar-2011) Now With HDMwIn

NOTICES: If you are noticing abnormally high battery drain and/or uptime, and you've updated to PRI 1.90, it has come to my attention
that this PRI has been problematic for a number of people, often resulting in large uptimes and/or poor battery life.
This issue affects people regardless of whether or not they are using a custom kernel
Downgrading your PRI and NV to 1.77 has been reported to resolve this issue.
You can find all PRI and NV versions by clicking here.
Due to troubling reports of battery issues possibly caused by the SBC battery charger modification, it is worth mentioning that by using any SBC build, you
fully assume any and all potential risks that the SBC modification may pose.
"netarchy-toastmod" is a kernel originally based on the GoDmOdE sources (Courtesy of Toast) integrating my work on fixing the fps for the Epson panels, and as of version 3.6.1, also integrating a fix for the Nova panels that does not require the use of Evo switch or manually setting any registers, etc, courtesy of work done by AssassinsLament (Well done on the nova fix). Special thanks needs to go out as well to Cyanogen and the cyanogen mod team, as a number of bugfixes and updates to the kernel in recent revisions have been ported over from cyanogen mod to enhance the overall netarchy-toastmod experience.
Click to expand...
Click to collapse
So what's in the kernel?
- Overclocking Support
- HDMwIn (As of 4.3.4)
- Audio gain tweaks (read: make it louder!)
- Fps Fixes
- tun.ko for openvpn users
- CIFS support (as of 4.2.2)
- BFS (in select builds)
- BFQ (in select builds)
- HAVS (as of 4.1.9)
- Assorted fixes/tweaks (that are sadly too numerous to list here)
- An army of rabid naked bunnies
Click to expand...
Click to collapse
The zipalign script in the kernel's modified inits is based on code in the Damage Control rom, and extended to check more places for apps.
The Dalvik code in the inits is courtesy of Ninpo/Hacre from the VillainRom team (over in the HTC Hero forums).
Click to expand...
Click to collapse
mroneeyedboh has written a handy little kernel starter guide with a lot of general information about custom kernels and various terms you might see flying around (such as cfs/bfs, havs/nohavs, etc).
You can view this guide Here
Click to expand...
Click to collapse
Current Revision: Stable: 4.3.1 - For Froyo Sense roms | Beta: 4.3.4
Click to expand...
Click to collapse
A note on multitouch:
Some of you may have used my 5point multitouch test builds with success, others with failure. Research has shown that the Evo's contain at least 2 different versions of the touch sensor, one of which does not support 5point multitouch (but it DOES support 3point). You can check which sensor you have using adb by issuing the following command: "adb shell cat /sys/android_touch/vendor" and examining the result. If your result is ATMEL_x0080_x0016, your phone can support 5point. If your result is ATMEL_x004F_x0016, your phone will only support up to 3point.
Click to expand...
Click to collapse
Disclaimer:
While these builds have been deemed generally safe, it is not feasible to account for all possible combinations of custom roms and uses,
custom roms may experience some breakage depending on how some features are set up, as these builds are not aimed at any one particular rom.
As such your mileage may vary, use these at your own risk.
Click to expand...
Click to collapse
2.2 Kernels (THESE WILL NOT WORK ON 2.1 ROMS):
These have only been tested against the rooted HTC 2.2 stock rom, they *may* work on the various custom 2.2 roms,
but this is NOT guaranteed. MAKE A NANDROID BACKUP JUST IN CASE!
Click to expand...
Click to collapse
If you get force closes on the camera, go to Menu -> Settings -> Applications -> Manage Applications -> All -> Camera -> clear data.
Click to expand...
Click to collapse
-----------------------------
2.6.32-based Kernels:
Click to expand...
Click to collapse
Beta Testing Builds
When making a post about any issues concerning beta builds, please include ALL of the
following information if possible:
1. Which kernel build(s) (ie; bfs/cfs havs/nohavs etc) are you using with the issue?
2. What Rom are you using?
3. If known, what OTA base is your rom using (ie; is it based on 3.29, 3.30, 3.70, etc)?
4. Does the issue persist if you go back to a stable kernel build?
5. The issue being experienced (obviously ;D)
4.3x:
To clear up some confusion that is apparently being spread around,
4.3x builds do in fact work on all current evo models, not just the newest model.
4.3.4:
--CFS builds--
No SBC:
4.3.4-cfs-nohavs-noUV-nosbc (No Undervolting)
4.3.4-cfs-nohavs-suv-nosbc (Static Undervolting)
4.3.4-cfs-havs-less-nosbc (Less Aggressive HAVS)
4.3.4-cfs-havs-more-nosbc (More Aggressive HAVS)
SBC: Use sbc builds at your own risk.
4.3.4-cfs-nohavs-noUV-sbc (No Undervolting)
4.3.4-cfs-nohavs-suv-sbc (Static Undervolting)
4.3.4-cfs-havs-less-sbc (Less Aggressive HAVS)
4.3.4-cfs-havs-more-sbc (More Aggressive HAVS)
For older beta builds click here.
---------------------------------------
Stable Kernels:
Universal Builds:
4.3.1:
--CFS builds--
No SBC:
netarchy-toastmod-cfs-havs-nosbc-universal
netarchy-toastmod-cfs-nohavs-nosbc-universal
--BFS builds--
No SBC:
netarchy-toastmod-bfs-havs-nosbc-universal
netarchy-toastmod-bfs-nohavs-nosbc-universal
These use Koush's anykernel for installation and should theoretically work on -any- rom.
*note* This is designed to be flashed over a phone that already has a working kernel of some kind flashed,
whether it's a stock kernel, or another custom kernel. In other words, if you can currently boot up your phone into whatever rom you have, this should work. ;D
The universal kernel also does not contain the tweak scripts of the normal build (ie; zipalign on boot and the dalvik tweak), it's intended to be a universally compatible kernel.
This also happens to mean the universal builds will probably work on CM
For older builds click here.
-------------

FAQ:
Code:
Havs: Hybrid Adaptive Voltage Scaling, basically tries to undervolt as much as possible to conserve power, but adapts to things like cpu load and temperature.
No Havs: Static voltage scaling, every cpu speed pulls a specific amount of power from the battery, no variation
CFS: http://en.wikipedia.org/wiki/Completely_Fair_Scheduler
BFS: http://en.wikipedia.org/wiki/Brain_Fuck_Scheduler
Q: Do I need to be rooted to use this kernel?
A: Yes, you need to be rooted, preferably a full root with nand unlock,
Q: How do I flash this kernel?
A: Copy the zip to your sdcard, and flash it from recovery mode
Q: My phone is suddenly unstable after using this kernel and I experience
weird things like reboots or other bugs
A: Are you overclocking? Try lowering the max speed of your overclock.
If the problems stop, you were overclocking too hard. If not,
please include the following information when reporting issues:
1. Your Baseband
2. What rom you're using
3. Your software number
4. Your panel type (Nova or Epson)
5. A Description of what's happening
Q: Why can I only overclock to 1152mhz? (In builds prior to 4.1.x)
A: Frequencies above 1152 have repeatedly turned out to be unstable for
a large percentage of users, so they have been removed to
eliminate the temptation to use them (and then complain because
they are unstable ;D).
Q: Does this kernel work with 2.2 (Froyo) roms?
A: The "Froyoized" kernels do
Q: Will this kernel work with my custom rom?
A: Maybe. The general population build of the kernel should work with
*most* custom roms, but as each custom rom can have it's own
customizations, your mileage may vary. In some cases, particularly
when a lot of customizations are in the rom's ramdisk, the kernel
must be repackaged with the ramdisk from the custom rom to be compatible.
Release notes:
Code:
Notes for Revision 4.3.4
- HDMwIn support added, you still need to download the free HDMwIn app
from the android market to use HDMI mirroring
- Timer tick set to 1000hz
- Unnecessary extra debugging turned off for public builds, should result in a small speed boost
Notes for Revision 4.3.2
- Wimax code updated, 4g should behave a bit better
- SD card read ahead fixed, higher class SD cards should
have an easier time reaching their potential speeds
Notes for Revision 4.3.1
- Screen tearing issues on sense roms should be fixed
Notes for Revision 4.3
- Camera drivers updated to support phones with the newer camera sensors
- ms79723's SBC v7 mod integrated for enhanced battery charging
- Misc speed tweaks/optimizations
Notes for Revision 4.2.2
- Kernel updated to 2.6.32.27
- Conservative set as default governor again
- Conservative governor defaults tweaked
- Less aggressive build has even more relaxed undervolting to aid those with REALLY picky phones
Notes for Revision 4.2.1
- Kernel updated from a 2.6.32.15 to 2.6.32.25
- Interactive governor added and tentatively set as default in some test builds
- Smartass governor added and tentatively set as default in some test builds
- Added BFS 357 smartass builds
Notes for Revision 4.1.9.1
- HAVS has made a return, this should help improve battery life by automatically dynamically undervolting the cpu when possible
Notes for Revision 4.1.8
- Added the BFQ I/O scheduler
- Split out kernel editions, now users have a choice between a CFS or a BFS kernel, if you don't like one, try the other ;D
- Enabled shadow writes on the gpu, which may result in better performance in opengl applications
Notes for Revision 4.1.7
- Add BFS to the kernel
- Allocate more memory to the gpu, this may result in better performance in opengl applications
- A rabid naked bunny vampire has materialized under your bed. Be afraid.
Notes for Revision 4.1.6
- Users with touchscreen issues should find their touchscreen is no longer as responsive as a stereotypical wife on her 10th anniversary
Notes for Revision 4.1.5
- Banished HAVS into the fiery pits of hell for now due to its inability to remain stable with any attempts to overclock. I'll be working on this on the side for possible future re-inclusion
- Clock frequency table remains opened up, with static undervolting in place
- Thanks to l33tlinuxh4x0r for being a guinea pig and helping test this build
Notes for Revision 4.1.4
- The beast responsible for the ridiculous overclocking instability at *any* speed beyond stock has been severely beaten and castrated by rabid naked bunnies (without anesthetic)
- Update scripts redone in the interests of making sure people who have had issues flashing the kernel in the past can do so
- The conservative governor has had some more tweaks to give it better out of the box performance, but you are free to set ondemand as your governor in setcpu if you wish. (If you want to migrate to ondemand you'll also need to set it as the governor in your setcpu profiles)
- The clock frequency table is fully opened up (re-detect frequencies in setcpu to see them) As always your mileage in overclocking may vary, but for some perspective, I ran 1152 through many loops of neocore and quadrant just fine.
Notes for Revision 4.1.3
- The ondemand governor is enabled as an option (switch to it in setcpu if you want to use it, remember you'll have to update your profiles to use it as well).
The default currently remains conservative to have a balance between performance and battery.
- The small segment of users getting bootloops due to the undervolting being too aggressive should be able to boot the kernel now (though if it persists the undervolting can still be adjusted)
Notes for Revision 4.1.2
- All frequencies above 1152 should now be properly visible/usable in setcpu (You may need to re-detect speeds in setcpu first)
Notes for Revision 4.1.1
- Hot on the heels of 4.1.0, a minor versioning fix ;D (4.1.0 reports itself as 4.0.3)
Notes for Revision 4.1.0
- Adapted HAVS for the evo, this may improve battery life by allowing the cpu to run at lower voltages when possible
- The overclocking range has expanded to allow attempting to clock above 1152, Remember that overclocking is unpredictable and potentially unstable by nature, if you encounter problems overclocking, lower the speed.
- Some threshold adjustments to the conservative governor in the interest of improving performance without obliterating battery
- Wired tethering should theoretically work, however if there are problems with the app, an alternative is azilink for wired tethering
Notes for Revision 4.0.3a
- An experiment of sorts, changing from the ondemand speed governor to the conservative governor (with some tweaks), in the interests of keeping good performance with less impact to battery life.
- Rewritten update scripts to hopefully alleviate the small number of people who seem to be having a problem flashing the kernel
Notes for Revision 4.0.2:
- People having stability issues with overclocking to 1152 *may* find it is a bit more stable (your mileage may vary)
Notes for Revision 4.0.1:
- Speed range should now allow underclocking to 128mhz (You may need to re-detect frequencies in setcpu)
- The Nova panel T2 register should be changeable again (for you Evo Switch/Novareq users)
Notes for Revision 4.0:
- Updated to the latest HTC released kernel sources (2.6.32)
- Camera should now be working properly
- HDMI output should be working in Froyo again
Notes for 3.7.8b-Froyoized
- Camera should no longer take dark snapshots when using the flash, the monster responsible has been severely beaten with a twig.
Notes for 3.7.8-Froyoized
- Camera app should no longer crash when changing from 5:3 widescreen to 4:3 standard ratio
- Camera app should properly allow 720p video recording and playback
- Japanese researchers have begun construction on a mecha-rabid naked bunny, codenamed: Bunnytron.
Notes for 3.7.7-Froyoized
- Re-integrate zipalign check and Dalvik cache tweak from the 2.1 line
- Some adjustments made to bluetooth-specific audio tweaks to combat distortion
- Audio adjustments to combat background noise overpowering the voice on the other end of a call
- Set version tag correctly (har har!)
- Super-mutant rabid naked bunny successfully created in lab conditions, however it disintegrates upon exposure to reality.
Notes for 3.7.6c-Froyoized
- SDcards with ext partitions added on should now cease confusing Froyo and allow the card to be mounted properly (Special thanks to Ninpo for directing me to the fix)
Notes for 3.7.6b-Froyoized
- Touchscreen adjustments, this may fix those who had touchscreen issues with 3.7.6
Notes for 3.7.6-Froyoized:
- Compatibility with the leaked 2.2 ota (and probably other 2.2-based roms)
- Working Camera (Limited to 3megapixels) EDIT: Reports indicate it claims 3mp but actually functions at 8mp
- Fps fix (of course ;D)
- Wireless Tether is reported as working with this as well
- 4g is confirmed as working
Notes for 3.7.5:
- Toned back audio boost tweaks a little to address distortion issues
- Updated gpu code for some 3d speed improvements
- Prevented the horde of mutant hairy toe-monsters from spreading toejam
all over the thread.
Notes for 3.7.4:
- Updated bluetooth code, courtesy of cyanogenmod
(You may have to re-pair your bluetooth devices)
- A new audio boost tweak has been applied
(This should not have the issues of the previous audio boost)
- Fixed an issue that would cause some Nova users to mysteriously
revert to 30fps. (Bad nova! no cookie!)
- Successfully avoided maiming any sabretooth'd tiger-striped cows
during the production of this update.
Notes for 3.7.3c:
- Some more tweaks to default performance (when not using setcpu/overclock widget)
Notes for 3.7.3b
- Killed that damn bug monster that decided yet again to sneak into one of my builds. Bad monster! No cookie.
Notes for 3.7.3:
- Adjusted the behavior of the speed scaling governor to give better performance out of the box for people that don't use setcpu or overclock widget
- Made adjustments to the general population build in the interests of making it compatible with Apps2SD by request.(Damage control users should have already been unaffected)
Notes for 3.7.2a
- Gave the monster holding wifi and 4g hostage a spanking (read: wifi/4g should be fixed)
Notes for 3.7.2
- Tweaked Nova settings in the interests of making sure everyone with a nova panel benefits from the fps fix
Notes for 3.7.1:
- Kernel should now have 100% more working HDMI output, no really, we mean it this time!
Notes for 3.7:
- HDMI output should now work in conjunction with boosted Nova/Epson fps
- tun.ko is now included by default for VPN users
Notes for 3.6.4:
- Behold, the return of 5point multitouch! This build should now automatically enable 5point multitouch for all phones that can support it. If the phone does not support 5point, it will default to 3point.
Notes for 3.6.3:
-Removed problematic audio boost patch that was giving issues with bluetooth
-Adjusted overclocking frequency tables to remove some problematic frequencies (Yes I know a small selection of you are going to be disappointed with the lowered cap, but I felt that the problems were more important at this time.)
-Evo switch ideally should not be required for decent framerates on Nova panels, but if users desire, by popular request, they can now use Evo Switch to tweak their T2 register [U]without[/U] it resetting after a screen cycle
-Default T2 value adjusted to 370, AssassinsLament believes this to present a good balance between out of the box performance and compatibility
-No fluffy pink bunnies were harmed in the making of this build

Can this be flashed with clockwork? Or just amon ra?
Is this a Froyo or Eclaire kernel? Any radio requirements?

Awesome, I have a Novatek. /facedesk.

jerryparid said:
Can this be flashed with clockwork? Or just amon ra?
Is this a Froyo or Eclaire kernel? Any radio requirements?
Click to expand...
Click to collapse
Should be flashable with either Clockwork or Amon Ra. Theoretically it might work on Froyo, but I've only tested it on Eclair.

This was not answered in the Godmode kernel thread. Does Camera work on this for 2.1.

mattrb said:
This was not answered in the Godmode kernel thread. Does Camera work on this for 2.1.
Click to expand...
Click to collapse
Yes the camera works on this in 2.1

Just flashed on Snacks v0.8 w/ Clockwork.
fps2d, avg 53-55, ~12 std
fixes touchscreen delay
can observe tearing
camera works
screen seems to be less responsive?

VoXHTC said:
Awesome, I have a Novatek. /facedesk.
Click to expand...
Click to collapse
me too. I am going to wait till things cool down a bit and bother HTC for another phone.

jerryparid said:
Just flashed on Snacks v0.8 w/ Clockwork.
fps2d, avg 53-55, ~12 std
fixes touchscreen delay
can observe tearing
camera works
screen seems to be less responsive?
Click to expand...
Click to collapse
I haven't noticed any loss of responsiveness on my end, if anything I'd swear it feels more responsive. Touch lag seems fairly significantly lessened.
I wonder if it could be related to the fact that I'm using a 1.47.651.1 based rom plus the latest radio/etc, curious.
Makes one wonder what all HTC changed in the update...

imaxreed said:
me too. I am going to wait till things cool down a bit and bother HTC for another phone.
Click to expand...
Click to collapse
umm? http://forum.xda-developers.com/showthread.php?t=711964

Best kernel on my epson screen. I like how i can overclock as well

jerryparid said:
umm? http://forum.xda-developers.com/showthread.php?t=711964
Click to expand...
Click to collapse
Thanks. I have seen that thread a hundred times but never entered it. The FPS doesn't bother me too much I am going to mess with this tomorrow i have the day off thank you.

jerryparid said:
umm? http://forum.xda-developers.com/showthread.php?t=711964
Click to expand...
Click to collapse
Yeah i'd love to see this fix for nova

netarchy said:
I haven't noticed any loss of responsiveness on my end, if anything I'd swear it feels more responsive. Touch lag seems fairly significantly lessened.
I wonder if it could be related to the fact that I'm using a 1.47.651.1 based rom plus the latest radio/etc, curious.
Makes one wonder what all HTC changed in the update...
Click to expand...
Click to collapse
I just flashed back to the Snacks kernel (v0.8 is 1.47 based); there is a substantial difference in sensitivity (not delay) between the two kernels.

jerryparid said:
I just flashed back to the Snacks kernel (v0.8 is 1.47 based); there is a substantial difference in sensitivity (not delay) between the two kernels.
Click to expand...
Click to collapse
Hrmm, is it glaringly obvious in any particular app? I'd like to see if I can reproduce the experience myself.

My phone keeps locking up when trying to watch youtube videos. Sorry if this is already a known issue.

krazyflipj said:
My phone keeps locking up when trying to watch youtube videos. Sorry if this is already a known issue.
Click to expand...
Click to collapse
Trying it out now, no problems with youtube for me.
Tearing doesn't seem as bad as I remember, but still bothersome.

when i seen this, i jumped into the air with my fist up like a touchdown at the superbowl.
flashing in juuusssst a second..

VoXHTC said:
Awesome, I have a Novatek. /facedesk.
Click to expand...
Click to collapse
same !!!!

[Rom][32A][6.35] Fusebox v1.3 - A Lean AOSP Froyo Machine

This is a no-frills, lean, clean Froyo AOSP machine.
Thanks:
Giant_Rider and Capychimp for the collaboration, klothius for the dalvik-cache script, dferreira for his AOSP source, Fightspit for the battery indicator and Carz for his kernel source.
Sources:
Froyo AOSP
Kernel
Battery Mod
Email.apk
Not Working:
Camera
Includes:
Google apps
Optimizations
Custom hosts file
Swap (requires swap partition)
Apps2SD (requires ext partition)
JIT
Cache on Cache
Renice
Highly OC'd kernel
Launcher Pro
Customizations:
Apps2SD and Swap are enabled on boot but you need the required partition structure. Jit is enabled out of the box. Kernel OC is set at 352MHz (under volted) when idle and 652MHz under load. You can use SetCPU to change the scaling, the scaling range is currently 122-748 MHz.
** Warning **
Typical behavior of an unstable device at high clock speeds are random reboots, black screen of death, and the phone not waking up.
Rom:
Recommended to do a full wipe first including dalvik-cache and sd ext, unless an update is specified "no-wipe".
Fusebox v1.3
*No-Wipe Update*
- New kernel compile (smaller and cleaner)
- Replaced custom hosts file with stock file (was causing battery drain errors in some programs that use a certain implementation of ads).
Fusebox v1.2
*No-Wipe Update*
- Includes updates from v1.1
- New kernel compile (2.6.34.2)
- Changed the default CPU scaling governor to interactive
Fusebox v1.1
*No-Wipe Update*
- New kernel compile
- Updated Brut maps
- Updated Google apps
Fusebox v1.0
*Full Rom*
- New Froyo AOSP base
- Email.apk that works with Exchange
- Addded ES File Explorer
- Updated LauncherPro
- Added latest kernel compile
- Moved default cpu frequencies to init.d
- Added script to clear app cache
- Memory tweaks
Fusebox v0.5
*No-Wipe Update*
- New kernel compile
- Default 352 min CPU speed (reported to fix wake issue for some people)
- Added afflaq's Email.apk to fix Exchange (thx lodewj)
Fusebox v0.4
*No-Wipe Update*
- Added missing speech lib
- Tweaked internal memory management
- Adjusted default clock speeds
Fusebox v0.3
*Full Rom*
- New kernel compile
Fusebox v0.2
*Full Rom*
- New kernel compile
Fusebox v0.1
*Full Rom*
- Initial release.
Themes:
*Updated: For Rom v1.0 Only*
These are flashable updates you apply over the base rom.
Stock White
White with circular battery with % (Fixed)
Black with circular battery with % (Fixed)
Screens:

does anything not work? camera/BT/etc?
EDIT: nvm you edited your post

zeotrope said:
does anything not work? camera/BT/etc?
EDIT: nvm you edited your post
Click to expand...
Click to collapse
Just camera as far as I know right now.

fast rom but have one issue, when phone locks i cant get it unlocked, the screen stays black and no response on buttons. noticed that games not getting laggy when touching screen, had that issue with all other roms for new radio. tried to check out new froyo rider to compare, but its looping while booting so i tried only this rom. sorry for english if its poor

bartasrex said:
fast rom but have one issue, when phone locks i cant get it unlocked, the screen stays black and no response on buttons. noticed that games not getting laggy when touching screen, had that issue with all other roms for new radio. tried to check out new froyo rider to compare, but its looping while booting so i tried only this rom. sorry for english if its poor
Click to expand...
Click to collapse
That's typical of the device not being stable at the clock speed, is still at the default clocks? I may have to bump down the speed if this is an issue.

Switch33 said:
That's typical of the device not being stable at the clock speed, is still at the default clocks? I may have to bump down the speed if this is an issue.
Click to expand...
Click to collapse
yes its on defoult clocks. just managed to flash froyorider rom, as far as i have checked its not freezing while locking the phone, clocks and kernel are the same so maby the problem is somewhere else

bartasrex said:
yes its on defoult clocks. just managed to flash froyorider rom, as far as i have checked its not freezing while locking the phone, clocks and kernel are the same so maby the problem is somewhere else
Click to expand...
Click to collapse
Ok keep me posted, I have only noticed that behavior over 700MHz on my device...

Switch33 said:
Ok keep me posted, I have only noticed that behavior over 700MHz on my device...
Click to expand...
Click to collapse
i think its my device, cause the same just happened with froyorider

bartasrex said:
i think its my device, cause the same just happened with froyorider
Click to expand...
Click to collapse
Hmm ok, you can try installing setcpu and bump it down a notch, if it turns out to be a common problem then I'll adjust the default kernel frequencies.

@Switch33
does it have multilanguage support? (need dutch belgium ).
I was actually working on my own but now that you made one, the need for making one myself is pretty much gone
btw, I would clock it a little bit lower by default and use setcpu to bump it some higher if the phone handle's it
thnx for your work!! keep it up
P.s. got a small request. Don't know if you compiled the kernel from source, but if you do, could you use the slub alocater instead of slab? (if that isn't already the case) ^_^
edit:
some questions:
undervolted?
JIT ?
renice init scripts?
edit2:
Allready compiling carz12 kernel as we speak with slub instead of slab.
Will upload it later today and share it.
if it works well, I will repost it with a lot of kernel debugging disabled. I saw that the cm source that Carz uses has ktimes and stuff enabled. disabling this stuff shoud shaves off a little bit in boot time. I hope that this will apply to our phones as well. I do this stuff for embedded devices (routers) with a x86 base (amd/NS geode cpu's). But I have little to no experience on arm based devices.

thanks it realy fast and nice
also i have set CPU and i changed it to
max 576000
min 245760
its now working great and verry fast

ROM is unstable for me; used SetCPU to lower the clock speeds and it still has trouble waking from sleep or unlocking. Very annoying to say the least since the ROM is great when it's properly working.
EDIT: Rebooted phone and now a new problem -- all my downloaded applications are corrupted. I can not access any of them, just the default apps that came with the app. They do not show up in my app drawer but they show up in my Manage App. settings and they just appear as a 0kb with their system name on the side, not even the application name; seems like a reboot fixes this though.

Can those with problems try this kernel please.
http://gwww.multiupload.com/L6F13CDQYD
Just flash from recovery

download link is broken or filevo has some issues with their servers

lodewj said:
@Switch33
does it have multilanguage support? (need dutch belgium ).
I was actually working on my own but now that you made one, the need for making one myself is pretty much gone
btw, I would clock it a little bit lower by default and use setcpu to bump it some higher if the phone handle's it
thnx for your work!! keep it up
P.s. got a small request. Don't know if you compiled the kernel from source, but if you do, could you use the slub alocater instead of slab? (if that isn't already the case) ^_^
edit:
some questions:
undervolted?
JIT ?
renice init scripts?
edit2:
Allready compiling carz12 kernel as we speak with slub instead of slab.
Will upload it later today and share it.
if it works well, I will repost it with a lot of kernel debugging disabled. I saw that the cm source that Carz uses has ktimes and stuff enabled. disabling this stuff shoud shaves off a little bit in boot time. I hope that this will apply to our phones as well. I do this stuff for embedded devices (routers) with a x86 base (amd/NS geode cpu's). But I have little to no experience on arm based devices.
Click to expand...
Click to collapse
Thanks for the suggestions, I'll take a look at those today. The kernel is undervolted below 384 MHz, JiT is enabled out of the box and includes renice scripts as well as others.

hol17 said:
ROM is unstable for me; used SetCPU to lower the clock speeds and it still has trouble waking from sleep or unlocking. Very annoying to say the least since the ROM is great when it's properly working.
EDIT: Rebooted phone and now a new problem -- all my downloaded applications are corrupted. I can not access any of them, just the default apps that came with the app. They do not show up in my app drawer but they show up in my Manage App. settings and they just appear as a 0kb with their system name on the side, not even the application name; seems like a reboot fixes this though.
Click to expand...
Click to collapse
Do you have an ext partition on your sd card?

who know the "clock + weather" app is?

itenno said:
who know the "clock + weather" app is?
Click to expand...
Click to collapse
Beautiful Widgets 'smaller home'

Switch33, would you mind forging dutch language support in there? (belgium)
It may be netherlands as well ....
I'll send your fresh pina colada while I'll send carz12's as well

lodewj said:
Switch33, would you mind forging dutch language support in there? (belgium)
It may be netherlands as well ....
I'll send your fresh pina colada while I'll send carz12's as well
Click to expand...
Click to collapse
I'll look into multi-language this weekend, long weekend in canada should be able to get some stuff done.

[ROM] CM7-TG-Reloaded (Final: 03-25)

Here's an introduction to CyanogenMod 7 for the un-initiated. This ROM is an update to the original CM7 ROM by TickerGuy. A big thank you to Isaacj87 (ikarosdev), TickerGuy, & Mantera for making this possible.
{
"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"
}
For even more theme customizations, see the Ultimate Online Theme Kitchen
Updates since TickerGuy's final CM7 B0.8:
- 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 ([email protected]/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.
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

Changelog
Build 2012-03-25
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
Build 2012-03-04
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
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.
Build 2012-03-01
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
Build 2012-02-18
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
WhyKernel 02-08
- Removed some BKLs in input processing.
Build 2012-02-02
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
Build 2012-01-26
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.
Build 2012-01-21:
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.
Build 2012-01-14:
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.
Build 2012-01-07:
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. May have fixed the occasional freezing capacitive button bug too.
- 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.
Build 20111230:
Kernel changes:
- Based on TheOC v1.6.14 (changelog)
Other changes:
- Experimental 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
Build 20111228:
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
Build 20111223:
First version.

nice! one of the things that is holding me back from upgrading from the optimus v to the triumph is that cm7 is still lacking but glad to see some progress is being made.

Very nice. Keep the development alive for this awesome device.

Whyzor, is the sluggish acclerometer fix confirmed working? I've tried farting around with it to no avail on my personal build, but I'm having difficulty making headway.
sent from my ASUS Transformer running Prime 2.1.1 using Tapatalk

APN settings.
Great work guys. I have just a minor question, Lately my sms/mms stops recieving. After being told to check my apn settings, i have noticed that alot of settings are missing. this is what i have. i am running cm 7.2.0-RC0
Name virgin mobile
APN virginmobileUS
proxy not set
port not set
username not set
password not set
server not set
mmsc thehttp
mms proxy 205.239.233.***
mm port 81
mcc 310
mnc 053
authentication type not set
apn type mms
apn protocol ipv4

Sharpe351 said:
Whyzor, is the sluggish acclerometer fix confirmed working? I've tried farting around with it to no avail on my personal build, but I'm having difficulty making headway.
sent from my ASUS Transformer running Prime 2.1.1 using Tapatalk
Click to expand...
Click to collapse
Interesting that you asked, I was just trying to get a new build out today, I thought this fix worked since some others in another forum reported it did, and also a few Optimus V CM7 devs reported working too. So I did a 'make clobber', 'make clean' today, and it apparently broke proximity, light, accelerometer, magnetic sensors (GPS, temp, mic still worked according to AndroSensor app) on a clean build. I haven't confirmed everything yet, I'm making another clean build tonight & will know tomorrow if I reverted the fix above would work. I think originally I did a clean build before the fix, then applied fix, and did a 'dirty' build on top to get the sensors working AND (apparently) fixed.
I'd be interested to know if you apply the fix & do a clean build, whether the sensors still work.
daveb272 said:
Great work guys. I have just a minor question, Lately my sms/mms stops recieving. After being told to check my apn settings, i have noticed that alot of settings are missing. this is what i have. i am running cm 7.2.0-RC0
Click to expand...
Click to collapse
Try rebooting into recovery & wipe cache AND dalvik-cache, it won't erase personal data.

Whyzor said:
Interesting that you asked, I was just trying to get a new build out today, I thought this fix worked since some others in another forum reported it did, and also a few Optimus V CM7 devs reported working too. So I did a 'make clobber', 'make clean' today, and it apparently broke proximity, light, accelerometer, magnetic sensors (GPS, temp, mic still worked according to AndroSensor app) on a clean build. I haven't confirmed everything yet, I'm making another clean build tonight & will know tomorrow if I reverted the fix above would work. I think originally I did a clean build before the fix, then applied fix, and did a 'dirty' build on top to get the sensors working AND (apparently) fixed.
I'd be interested to know if you apply the fix & do a clean build, whether the sensors still work.
Click to expand...
Click to collapse
I'll look into it sometime in the next few days. My build has very little that actually bugs me (g-sensor is the only one I can think of). My OP-V on IHO had the same issues, so I kinda expected it with this build. I did a custom build there as well based on Jerry's setup. I built my Motorola CM7 as a re-sync with CM essentially, based on Issac's git through the guide on androidforums, but everything that was questionable before worked on this build. I think the CM team hasn't paid too much attention to the g-sensor issue because the phones with the problem are constantly being rebooted (testing). If you reboot and use it, the sensor works fine for a while. It's just after a while that I notice sluggish performance (same on the OP-V). I'll try to get back with you or upload and send you my build with the fix integrated to test as soon as I can.
-Mike
sent from my ASUS Transformer running Prime 2.1.1 using Tapatalk

Well something is hosed pretty badly with my local repo, because even after reverting the fix I posted earlier, and a clean build, I still can't get sensors. I'm going to have to erase everything and sync from Isaac's repo if I want to build another ROM (it took over 24 hrs the first time).
I may just focus on kernel tweaks from now on since the CM7 side isn't getting much updates anyway. I've restored from a previous working nandroid backup and the sensors still work (so it's not a hardware problem).

Whyzor said:
Well something is hosed pretty badly with my local repo, because even after reverting the fix I posted earlier, and a clean build, I still can't get sensors. I'm going to have to erase everything and sync from Isaac's repo if I want to build another ROM (it took over 24 hrs the first time).
I may just focus on kernel tweaks from now on since the CM7 side isn't getting much updates anyway. I've restored from a previous working nandroid backup and the sensors still work (so it's not a hardware problem).
Click to expand...
Click to collapse
Is the sensor fix uploaded to Issac's current repo? I'm also trying to get a git of my own to fork from Issac's and TG's builds respectively. I'm loading it onto my laptop now to see if the build changes. If not I can try to merge the changes with a bit of a tutorial and run another build. If you want, I can PM you a current link to the build I'm using right now as my daily. The updates haven't been pushed, but the ROM is dead stable. As far as repo sync is concerned, my first took about 3 hours. The computers I use are old and outdated. Both are 32bit systems. My desktop is 2.8Ghz single core with 2 gig of ram. My laptop is 1.4Ghz single on 1 gig of ram. They work great for me and I've had very few issues.
**sidenote** You may be able to repo sync to get the additional fixes that may be missing. Or, you may try to reload the "proprietary" files. I had a borked build that was missing some proprietary files. I had to reload them to rebuild and fix the issues.
sent from my ASUS Transformer running Prime 2.1.1 using Tapatalk

Sharpe351 said:
Is the sensor fix uploaded to Issac's current repo? I'm also trying to get a git of my own to fork from Issac's and TG's builds respectively. I'm loading it onto my laptop now to see if the build changes. If not I can try to merge the changes with a bit of a tutorial and run another build. If you want, I can PM you a current link to the build I'm using right now as my daily. The updates haven't been pushed, but the ROM is dead stable. As far as repo sync is concerned, my first took about 3 hours. The computers I use are old and outdated. Both are 32bit systems. My desktop is 2.8Ghz single core with 2 gig of ram. My laptop is 1.4Ghz single on 1 gig of ram. They work great for me and I've had very few issues.
**sidenote** You may be able to repo sync to get the additional fixes that may be missing. Or, you may try to reload the "proprietary" files. I had a borked build that was missing some proprietary files. I had to reload them to rebuild and fix the issues.
sent from my ASUS Transformer running Prime 2.1.1 using Tapatalk
Click to expand...
Click to collapse
No the sensor fix isn't in Isaac's repo, I had to manually add it. Here's a discussion about it: https://github.com/inferiorhumanorgans/android_device_lge_thunderc/issues/50
I'll try reloading the proprietary files, I have a working binary ROM from before still (with some optimizations of my own), just can't get that same config from building source. I'd be curious to see your changes pushed to a github. I was going to get to that with my optimizations as soon as I confirm a working build, until this happened.

Whyzor said:
No the sensor fix isn't in Isaac's repo, I had to manually add it. Here's a discussion about it: https://github.com/inferiorhumanorgans/android_device_lge_thunderc/issues/50
I'll try reloading the proprietary files, I have a working binary ROM from before still (with some optimizations of my own), just can't get that same config from building source. I'd be curious to see your changes pushed to a github. I was going to get to that with my optimizations as soon as I confirm a working build, until this happened.
Click to expand...
Click to collapse
My changes aren't really much IMO. Essentially a sync with minor tweaks.
Currently, I think github is screwy. I'm getting a fetch error.
Code:
fatal: The remote end hung up unexpectedly
error: Cannot fetch CyanogenMod/android_prebuilt
I think it's on their end. My desktop has the same issue. My sync on the laptop is sunk at 94%.
sent from my ASUS Transformer running Prime 2.1.1 using Tapatalk

New 01-07 build uploaded. Check post #1 & #2 for link & changelog. If upgrading, just wipe cache AND dalvik-cache before flashing, it should keep all your user data & settings.
In the spirit of new years resolutions (what? a ROM needs to go to the gym once in a while too). These apps can safely be removed if you don't use them (it's from a script that I run after every new CM7 install on my MT.
Code:
#!/system/bin/sh
mount -o rw,remount /system
rm /system/media/bootanimation.zip
rm /system/app/ADWLauncher.apk # IF you have another launcher already installed.
rm /system/app/Androidian.apk
rm /system/app/AndroidTerm.apk # Market version is more up-to-date
rm /system/app/Calculator.apk # I prefer RealCalc
rm /system/app/CMStats.apk
rm /system/app/CMUpdateNotify.apk
rm /system/app/CMWallpapers.apk
rm /system/app/Cyanbread.apk
rm /system/app/DSPManager.apk
rm /system/app/Email.apk
rm /system/app/Gallery3D.apk # Quickpic is much nicer replacement
rm /system/app/LiveWallpapers.apk
rm /system/app/LiveWallpapersPicker.apk
rm /system/app/MagicSmokeWallpapers.apk
rm /system/app/Pacman.apk
rm /system/app/Protips.apk
rm /system/app/ThemeChooser.apk
rm /system/app/ThemeManager.apk
rm /system/app/VisualizationWallpapers.apk
rm /system/app/VpnServices.apk

In case anyone only monitors this thread here, new version 01-14 posted, see #1 & #2 for details.

Whyzor said:
In case anyone only monitors this thread here, new version 01-14 posted, see #1 & #2 for details.
Click to expand...
Click to collapse
Is the AGPS patch included with 01-14 version?

destroyer67 said:
Is the AGPS patch included with 01-14 version?
Click to expand...
Click to collapse
Yes. I'm not noticing much difference (I don't use GPS that much, it's always been ok for me).

Whyzor said:
Yes. I'm not noticing much difference (I don't use GPS that much, it's always been ok for me).
Click to expand...
Click to collapse
My GPS has always worked fine. All I had to do was be connected to Wifi the first time I initialized the GPS. Now it connects in 10 seconds or less.
sent from my ASUS Transformer running 8.6.5.21 using Tapatalk

hi, do you know a command to make android not to monitor the battery status?.

Whyzor said:
In the spirit of new years resolutions (what? a ROM needs to go to the gym once in a while too). These apps can safely be removed if you don't use them (it's from a script that I run after every new CM7 install on my MT.
Click to expand...
Click to collapse
thanks a lot for this info. but now question is how to run this. and what am i supposed to save this file as. *.sh ??
and how to call this script from updater-script file ?
do you know what are we supposed to enter/ syntax for renaming a file if we dont want to overite it(regarding updater-script)
say i want to change calculator.apk but keep the original in place as *.apk.old

zailer said:
thanks a lot for this info. but now question is how to run this. and what am i supposed to save this file as. *.sh ??
and how to call this script from updater-script file ?
do you know what are we supposed to enter/ syntax for renaming a file if we dont want to overite it(regarding updater-script)
say i want to change calculator.apk but keep the original in place as *.apk.old
Click to expand...
Click to collapse
I save it as /sdcard/os/c.sh (I don't think the suffix is important, it can help you remember it's a sh script). Not sure about updater-script, I don't use that. Then every time after new version of ROM installed, just run:
su
sh /sdcard/os/c.sh
If you want to copy an old copy, just insert something like:
cp /system/bin/blah.apk /system/bin/blah_apk.bak
rm /system/bin/blah.apk
...

[ROM][CM-10.1][JB 4.2.2][KANG] NameLess Bean [28.03.2013]

Hi!
I've decided to post my build of CM10.1 for all you flash-o-holics so let me introduce NameLess Bean:
based on CM10.1 sources
bruce2728 kernel sources
Evervolv's media-legacy and display-legacy repos (up to 22.03.2013 build)
Arco's media-legacy and display-legacy (since 28.03.2013 buil)
What's not working:
while in call touchscreen stays active even when backlight is off because of that you can accidentally do all weird stuff while talking.
1080p recording credits to cile381
MHL (most probably I have no means for testing this but I've also made nothing that could possibly fix this)
gfx glitches when playing video using Gallery
tethering fixed upstream (CM)
no autofocus while recording
System Settings>System>Hardware keys "Enable custom actions" does not appear to work (thanks @zath for bug report)
Sweep2Wake causing random touchscreen freezes
most probably there is more and I'm sure you'll find it fast
Additional features:
Frequent contacts in Contacts and Phone app can be hidden (see settings in Contacts app)
sweep2wake control in Settings -> Display
pinch to zoom (all credits go to ufrat
scrolling cache disabled in framework
audio volume control files taken from ARHD 7.0 (most probably HTC is the real source of those)
Install notes::
If you are coming from any other ROM wipe everything (except SDCard) in Ext4Recovery (Do not use Superwipe script!).
When upgrading from earlier version of this kang there is no need to wipe anything.
Make a nandroid backup. Just in case.
Flash the ROM
If flashing for the first time flash GApps.
Reboot
ROM can be downloaded here:
NL-J.org
Box.com
Please use latest GApps from Goo.im
Sources are on my GitHub
Please add logcat if you are reporting a bug. This will make my life a bit easier. THX
Now the most important part:
You would have nothing to flash if not some hard working people:
Team Cyanogen and all devs that contribute to this project
Vorbeth, TamCore, intervigilium, cretin45, for their excellent work on getting CM on HTC Sensation
bruce2728 for his excellent work on CM10
Team Evervolv for getting things done for CM10.1 on HTC Sensation
ufrat for pinch-to-zoom camera
arco and tbalden
Big THANK YOU!!
Changelog
28.03.2013
NameLessBean-20130328.zip md5sum: f4001aa53f72f9a76b71ba9eabc2a925
Fixed touchscreen issues while in-call (again! Stupid mistake!) thx @txgaryf for catching this bug
raised volume levels thx to @erraggy
switched to arco's media-legacy and display-legacy (to be closer to CM sources)
upstream changes
22.03.2013
NameLessBean-20130322.zip md5sum: 7e78c917b5ff73e5bc73c38817c76725
fixed Camera issues other than that only upstream changes (mostly translations)
20.03.2013
NameLessBean-20130320.zip md5sum: fba5ef3f631725ab7c3842fc3a74422f
This is just refreshed build so all changes are from upstream. Last one merged changes is Calculator: Fix build warnings
11.03.2013
NameLessBean-20130311.zip md5sum:b989d3f1f2573835f23843ed803fa221
soft reboots should be gone for good thx to Ablinoman887 shifting of various PMEM bases around
Showing/hiding frequent contacts is now user selectable (see settings in Contacts app)
upstream changes (last merged LockscreenPattern: Fix toggle dots/error pattern visibility
06.03.2013
NameLessBean-20130306.zip md5sum: b7a5c10b6782726f1a5c411d66b7fbb9
Fixed sweep2wake issues
Bumped PMEM size a bit. Should get rid of softreboots and wallpaper reverting to default one. If this proves to be stable I'll plan to wait for ION implementation in kernel. As soon as bruce2728 posts patches I'll try to work on it too
Upstream changes
05.03.2013
NameLessBean-20130305.zip md5sum: 651bf1736cb47c3ffbe88a1822e5a559
switched to CM-10.1 branch of GPS code (uptill now I was using older jellybean (CM-10) branch)
disabled scrolling cache in framework (should improve scrolling)
reverted all in kernel PMEM allocation changes. This trashed display badly. Potentially soft-reboots might come back. Please let me know if you get this
audio volume control files taken from ARHD 7.0.
26.02.2013
NameLessBean-20130226.zip md5sum: 5baa32b805e27308852c9d48c5242dd4
really fix touchscreen freezes when s2w enabled
custom action for hardware keys fixed (wasn't working only for Search key)
bumped PMEM size in kernel (hinted by Albinoman887 and bruce2728) - this should stop soft reboots and wallpaper reverting to default one. This also lowers a bit amount of gfx glitches tho doesn't help in Chrome
upstream changes as of Feb, 25th 2013
22.02.2013 test build
NameLessBean-20130222.zip md5sum: f60976b666478a83f67280fb2e7fd3e1
Fix for touchscreen freezes with s2w enabled
upstream changes as of Feb, 22th 2013
20.02.2013
fix sweep2wake logic in Settings
upstream changes (will update this later when I'll have some time)
18.02.2013
If you want to use sweep2wake than don't flash other kernels You will most likely experience touchscreen problems. You've been warned
(if you don't want to use sweep2wake you can flash whatever kernel you want)
JellyBean 4.2.2
Upstream changes from CyanogenMod (last change included: Feature : Volume adjust sound preference 2/2 (Merged)
Proper (as much as it can be) fix for spurious touch events while calling when sweep2wake is enabled
05.02.2013
pinch-to-zoom by ufrat
Upstream changes from CyanogenMod (last change included: Restored Fused Location app name (Merged)
tethering fixed (upstream)
30.01.2013
workaround for spurious touch events while in-call.
1080p recording now works (thanks to cile381)
Sweep2Wake control in Settings.
Upstream changes from CyanogenMod (last change included: Keyguard: Remove duplicated code).

reserved just in case

welcome and good luck :fingers-crossed:

Nice to see new cm10.1 dev for sensation topic every day.

[ROM][CM-10.1][JB 4.2.1][KANG] NameLess Bean [26.01.2013]
Can you tell me what's different on this one from the other 4.2.1 builds?

Re: [ROM][CM-10.1][JB 4.2.1][KANG] NameLess Bean [26.01.2013]
blahbl4hblah said:
Can you tell me what's different on this one from the other 4.2.1 builds?
Click to expand...
Click to collapse
+1? Just wondering
Sent from my HTC Sensation using xda premium

The differences from albinoman887 ROM are minimal:
working GPS
no frequent contacts list both in Phone and Contacts (frequent not starred)
it's safe to use even with kernels that do not have built-in thermald and mpdecision
Both mine and his ROM are based on CM10.1 so naturally they are similar. I'm quite sure that you can switch back and forth between albinoman887 build and mine without wiping.
Team Evervolv uses some mixture of pure AOSP, CM10(.1) and their own changes. As a result they f.ex have working 1080p recording. As I mentioned in OP I've used their work too.
Why I posted my build? Well I tend to build ROMs for my own usage. I thought maybe someone will make some use of them too. And I can feel the fun of having Android again... Just like in the good ole HTC Dream and FroYo days....

How much time you spend on it per day?

Today? hmm took aroound 2hrs to figure out the gps thingie (not counting build time) thermald/mpdecision was easy so not counting it at all
Before? At least 4hrs probably some more.
Why are you asking? Does this matter at all? After all I'm doing it for fun so time does not matter that much
I've just now started complete rebuild of sources with a bit of repo rebasing. I think this should make build more consistent. Most probably the build will fail so tomorrow I'll have something to do. If not I'll probably add Sweep2wake control in Settings or have a look at tethering depending on the mood if my wife or kids won't mind

delete..........

thanks for contributing. Tried to download, but got Out of Bandwidth from Box.

Awesome, I think I'll try this soon. I remember you from the G1 forums. Great to see some CM 10.1 ROMs!

papikev1714 said:
I can report that adb was not picking up my device with your rom. I could neither push or pull or any other function with adb. Reverted to a backup and it is fine now. By no means a complaint, just informing you if it helps. Everything else seemed to be good. Thanks for your efforts. Regards.
Click to expand...
Click to collapse
Odd... I've been using adb quite a lot.. Did you enabled developer settings in ROM? (tap several times on build number in About phone in Settings). If not - enable them and check again.
THX
BTW I've added another download location in OP.

NLJ said:
Odd... I've been using adb quite a lot.. Did you enabled developer settings in ROM? (tap several times on build number in About phone in Settings). If not - enable them and check again.
THX
BTW I've added another download location in OP.
Click to expand...
Click to collapse
silly.....of course. My bad, simple oversight on my part. Preoccupied with something else when I flashed. Works fine. Sorry for the post......deleted. Good work bro.

i downloaded today in the morning, till now works fine, happy to have it:good:
im planning to use this a s my daily use rom, we will need to see how about battery drain in next days.

Thanks for the ROM NLJ. Been testing since last night. For the most part, very solid, just the odd thing here and there. I received two calls, during the first my ear managed to set an alarm for Sunday 9 am and the second managed to change my time zone and kept setting off key tones like it was pressing on the dailer. The proximity sensor had the screen off, but it still managed to do things behind the curtains. I'll test some more today.

namaste74 said:
Thanks for the ROM NLJ. Been testing since last night. For the most part, very solid, just the odd thing here and there. I received two calls, during the first my ear managed to set an alarm for Sunday 9 am and the second managed to change my time zone and kept setting off key tones like it was pressing on the dailer. The proximity sensor had the screen off, but it still managed to do things behind the curtains. I'll test some more today.
Click to expand...
Click to collapse
You should have a serious talk with your ear, playing with other peoples phones is bad.

namaste74 said:
Thanks for the ROM NLJ. Been testing since last night. For the most part, very solid, just the odd thing here and there. I received two calls, during the first my ear managed to set an alarm for Sunday 9 am and the second managed to change my time zone and kept setting off key tones like it was pressing on the dailer. The proximity sensor had the screen off, but it still managed to do things behind the curtains. I'll test some more today.
Click to expand...
Click to collapse
I've noticed that too and I'll update OP with this bug in a few. Don't quite know where to start at fixing this tho.
At this moment I'm trying to rebase whole source tree and get rid of Evervolv repos as it seems they don't like this. I've spent whole sunday on this but it will take some time
Right now I have two separate source trees and one of them (the one I've build ROM in OP) is quite a mess. If time permits I'll make it compilable again today and see if I can fix this bug as it seems most serious atm.

New build is up on OP.
I managed to find a workaround the bug reported by namaste74. Let me know how this works for you.
As small bonus you can now toggle sweep2wake in Settings -> Display

awesome, will be setting this up now and put it through basics tomorrow. Really love 4.2.1, be great to iron out the issues.

[ROM][6.0.1_r68][Grouper|Tilapia]30Sep2016 FINAL] OmniROM 6.0.1-HOMEMAKE

This is an unofficial build of OmniROM for Neuxs 7 (2012).
**Click the above logo to visit the official Omni site
I list some Extra info. and Q&A for MM in my other thread, it might be helpful
Release notes:
2016/9/30
Omni update to Android-6.0.1_r68 earlier and I have included a few things like USB & Bluetooth Tethering in the device tree. So I built another final update. As many of you would install Mods which might turn off the selinux. Seems no reason to release any security patches. With limited resources, it's time to move on. Bye
HISTORY:
2016/9/6
Omni stop the update of Android-6.0 earlier last month so this is the final update of Omni-6
2016/8/8
This is the monthy update to Android 6.0.1_r62 (MTC20F).
2016/7/13
This is the Android 6.0.1_r54 (MTC19Z) version.
2016/6/21
This is the monthy update to Android 6.0.1_r46.
2016/5/26
This is a monthy update.
2016/5/4
Omni had merged the 6.0.1_r43 source. In this build, I included the modification of activity manager and service in my DU. It provide some improvement in overall performance and memory management.
The ApkPermission script is updated. Hoping to aware of any combination of flashing. A wipe data/Factory reset will reactivate the script on the next boot. Cheers!
2016/4/20
Omni had merged the 6.0.1_r30 source. This is a version update.
2016/4/10
This is an version update. Omni had merged the 6.0.1_r24 source. A few fixes were made in Performance Settings. The native AOSP "Tap to wake" settings is enabled. Cheers!
2016/3/24
Omni had merged the 6.0.1_r22 source. In this build, the camera is partially fixed. Video capture and preview are OK but the AOSP Camera app fail to connect to the buffer of the Camera HAL. Thus the picture remains at preview quality. I don't want to change the AOSP camera app too much and there are other apps so leave it for the time being. The latest DC-kernel features are also included. Cheers!
2016/3/12
I have put some tests on the kernel. Seems I messed it up... :cyclops:. I just rebuild the last release. Omni has a few updates too so I rebuild Tilapia too. As a bonus, I enabled the zRAM in kernel. Hoping this end the sloppiness... :
2016/3/11
Seems the last Omni not boot for grouper. I have removed the files from the host. I'm building another one now. I just pulled the battery out. I'm charging it directly now. I'll release again after testing for both.
Sorry for the troubles caused... :
2016/3/10
Finally, Omni merge the 6.0.1_r17 source. It's been a while for an update. I was busy in job and other projects. :cyclops: After I few months, I'm itchy to try new things. I planed to move my daily driver to Dirty Unicorns.
As a closure, I want to get rid of all the know issues firs so I take a look at the last issue of our Tilapia and Grouper -- the Camera2 apk. It was just a simple wrong initial value cause that. The issue that bug every developers in this forum is finally fixed. :highfive:
I seldom quit. I think I would keep Omni up to date for a while. Might be a dual weekly, monthly or when new versions come. Cheers!
PS: Right before I finish the last build, the usb port of my Tilapia was dead. I just can't test it thoroughly before the battery flat. I had order the part but I don't know when it would arrived... :cyclops:
2016/2/28
It's been a while for an update. I was busy working on the Tegra3 support in Performance Settings. Layout, dialogs, preferences are time consuming boring routines but somebody got to do the dirty works. :cyclops: Minimum and maximum backlight, GPU frequency and various Voltage Controls are added now. Stand alone app for DC-kernel will be available shortly. A few bugs in settings are fixed and the fix for 3MinitBattery crash is also included. Cheers!
Note: 1. New backlight limits will be activated after you change the brightness.
2. Settings respond to the BOOT_COMPLETED signal for resuming the values.
Features like DT2W, freq. and voltages might are not be available right after boot.
2016/2/17
In the last build, SystemUI would crash if 3MinitBattery apks not installed. This View attachment omni6-patch-20160217-nexus7.zip would fix the issue. Normal battery icon will be shown if 3MinitBattery is not installed.
2016/2/15
This is just the weekly update. Latest Omni source is merged.
2016/2/6
Right after I uploaded the files, TeamWin released the TWRP-3.0.0-0. There were a few language update on top. However, tilapia still doesn't have the official update so I uploaded my TWRP-3.0.0-0 for tilapia too.
I just put a fix in the DT2W. Hoping it would be more reliable at deep sleep. If anyone interested to help testing, here is the test View attachment omni-boot-20160206-nexus7.img.
2016/2/5
Omni had merged the Android-6.0.1_r13 source now. I added two fine tune settings, double tab bound and duration to the DT2W settings. Hoping to increase the reliability and avoid false activations. This feature definitely consume power (no matter how little) so it is by default disabled.
There is a bug in Omni's init.d script. It can only start once after factory reset. I don't know why yet. I use the init.d for those settings need to be set early. It just fail to work so I have to revert to the traditional preference.
Note: 1. DT2W might not be started before the first suspend.
2. At deep deep sleep, you might need a few more taps to wake the system.
TWRP has a different UI for some time but there is no official release yet. As a side product of building ROM, I'm using it myself for some time. I think it doesn't hurt to include it here. I had updated the F2FS driver and fixed the exFat support. I tagged it 2.8.7.4 for my other devices after a few patches. I keep the version number to differentiate with the official build only. Doesn't mean it is better. This is probably just a one time deal.
{
"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"
}
2016/1/30
I have tried my new port of "double tap wakeup" for a few days. For those who want to join the test, flash this View attachment omni6-patch-20160130-nexus7.zip in recovery. Kernel and Settings will be updated in this patch. A new setting is added to the Advanced page of Performance Settings. Cheers!
Edit: I have already pushed the source to my github. No more e-mails and PM please.
2016/1/29
This is just the weekly release. Latest Omni source is merged.
2016/1/21
Since there are something missing in the last built, I release this build earlier. I finally fix the issue of audio not started after reboot. No more silly rotation to get it back now. :highfive:
After testing for sometime, I think performance settings are presentable. Voltage controls, LP core O/C and GPU O/C are enabled now. I can't guarantee it works for all devices but it works for me. TricksterMod seems to have better support for the new Tegra settings. The UID_CPUTIME support in kernel is also ready. Hoping everything is in the right place now. Cheers!
2016/1/17
A library is missing in the 20160115 build. Can't find the SIM card in Tilapia. The patch in post#47 would fix it.
2016/1/15
Finally recover from the hard drive failure. After painful exercises, the new system is much slimmer. Some valuable data and junk are gone now. "Begin again" is not necessarily a bad thing. In this build, I included the Power tile and 3minit battery mod. For some security issue, Performance data was not persist after reboot. To fix this, PerformanceControl would ask for ROOT (once) now. There are issues in the other Governors. For the time being, just keep the default interactive.
Hoping nothing is missing after the crash.
2016/1/7
Omni just merged the 6.0.1_r10 tree. It is also the time for my new build. After testing for some time, I think F2FS and other few patches are ready. My tilapia has been staying ON (With a few reboot to recovery flashing test builds) for over 10 days now. I'm not a gamer nor a frequent You Tuber so I can't represent neither of them. There might still be some glitches but good enough for myself as daily driver.
2015/12/30
I wait for a while for an MM to be my daily driver. I have a Tilapia which only have few choices. Dmitry's AOSP is quite good but lack of the "basic" features I was spoilt. I have tried a few ROMs in my other devices. I think Omni is the best for me so I added the device trees to my working directory. Dmitry's works make life much easier. I have added a few features and patches to the the Offical Omni. Cheers!
Change log: :victory:
Code:
Official Omni [URL="https://changelog.omnirom.org/"]Change log[/URL]
[COLOR="Blue"]2016/9/30[/COLOR]
- Final release of Omni-6 Android-6.0.1_r68 (MTC20L)
- USB and Bluetooth tethering support
- Kernel:Security update
- Kernel:DT2W reliability patches
[COLOR="Blue"]2016/9/6[/COLOR]
- Final release of Omni-6 Android-6.0.1_r62 (MTC20F)
[COLOR="Blue"]2016/8/8[/COLOR]
- Latest Omni source 6.0.1_r62 (MTC20F)
[COLOR="Blue"]2016/7/13[/COLOR]
- Latest Omni source 6.0.1_r54 (MTC19Z)
[COLOR="Blue"]2016/6/21[/COLOR]
- Latest Omni source 6.0.1_r46 (MOB30M)
[COLOR="Blue"]2016/5/26[/COLOR]
- Latest Omni source 6.0.1_r43 (MOB30J)
[COLOR="Blue"]2016/5/4[/COLOR]
- Latest Omni source 6.0.1_r43 (MOB30J)
- Frameworks: Adjustments in activity manager and service
- ApkPermission: Add a retry loop to wait for PM to start
- ApkPermission: A done flag is added. Script will be disabled after permission is assigned.
[COLOR="Blue"]2016/4/20[/COLOR]
- Latest Omni source 6.0.1_r30 (MOB30D)
[COLOR="Blue"]2016/4/10[/COLOR]
- Latest Omni source 6.0.1_r24 (MHC19Q)
- kernel: DT2W region increase to 50 pixels
- PowerHAL: Adjusted to O/C frequencies
- PowerHAL: Support the native AOSP "Tap to wake" feature
- Settings: Native AOSP "Tap to wake" is enabled in Display settings
[COLOR="Blue"]2016/3/24[/COLOR]
- Latest Omni source 6.0.1_r22 (MHC19J)
- kernel: Fix a bug in DT2W
- kernel: DT2W duration increase to 80ms
- kernel: Include the kexec patch for MultiROM
- PerformanceControl: Fix the Tegra3 settings crash at the first launch.
- Camera apk : fix the crash when select video
[COLOR="Blue"]2016/3/10[/COLOR]
- Latest Omni source 6.0.1_r17 (MMB29V)
- kernel: zRAM support as promised
- kernel: Change the permissions for CPU and governors so that performance apks would work.
- kernel: Merge the rotation fix
- Reinstate the much lighter AOSP browser to replace the bulky Chrome.
- Fix the Camera apk from crash.
- PerformanceControl: simplify the Helper functions.
- Settings: fix a bug in Tegra3 settings
[COLOR="Blue"]2016/2/28[/COLOR]
- Latest Omni source 6.0.1_r13 (MMB29U)
- kernel: Add support for custom panel backlight limits
- Settings: Add Tegra3 settings to Performance Settings
- Tegra3: Add backlight limits, GPU freq and various voltage controls.
- DT2W: Fix a bug in Settings
- Settings: Update translations for zh-rCN, zh-rHK and zh-rTW
- SystemUI: Fix the crash when 3Minit apks not installed
[COLOR="Blue"]2016/2/15[/COLOR]
- Latest source from Omni
- To unify with other developer's build, move rotation fix to kernel. This is for the DC-kernel update.
[COLOR="Blue"]2016/2/5[/COLOR]
- Latest Omni source 6.0.1_r13 (MMB29U)
- kernel: Add support for double tap to wake (DT2W)
- Settings: Add DT2W settings to Advanced page of Performance
- DT2W: Add taping bound and duration settings
- DT2W: Add translations for zh-rCN, zh-rHK and zh-rTW
- Settings: revert to traditional preference for Set on Boot
- SystemUI: Fix a bug in 3Minit port
[COLOR="Blue"]2016/1/29[/COLOR]
- Latest source from Omni
- Fix a bug in SystemUI
- Some adjustments to the Governors
[COLOR="Blue"]2016/1/21[/COLOR]
- Latest source from Omni
- Fix audio not started after reboot.
- Kernel: Enable Voltage control for CPU, GPU, LP core and RAM
- Kernel: Enable GPU max. frequency control
- Kernel: Add UID_CPUTIME support with power consumption settings
- Kernel: Adjust a few settings in Governors
- Reinstate stlport for Tilapia
- Fix a bug in PerformanceControl
- Fix a bug in QS
[COLOR="Blue"]2016/1/15[/COLOR]
- Latest source from Omni
- To fix the permission issue at boot, PerformanceControl requires ROOT now.
- Add the Power (screen off) Tile to QS. Short press:sleep, Long press:power menu.
- Include the 3minit battery mod (v3.1) from Gary Harrington.
- kernel: fix a bug in F2FS
- kernel: fine tune the CPU values
- Chromium replace the default browser
[COLOR="Blue"]2016/1/7[/COLOR]
- Latest Omni source 6.0.1_r10 (MMB29T)
- kernel: Fix a bug in Voltage control
- kernel: LP core O/C to 666Mhz
- kernel: GPU max. set to 446Mhz
- kernel: full F2FS support
- kernel: time out for a few wakelocks
- Fix rotation freeze after deep sleep
- Include the journal_async_commit flag for ext4 partitions
[COLOR="Blue"]2015/12/30[/COLOR]
- Latest Omni source 6.0.1_r3 (MMB29M)
- Dmitry's patches
- gcc 4.9 to compile kernel & platform
- kernel:CPU O/C and Voltage control
- kernel:GPU O/C and more Governors
- Override the healthd
- Add OTG support
- Add screenshot tile to Quick settings
- Add an init.d script to fix the permissions of Gapps
- Add a Captive portal check switch to build prop.
- Add Messaging
- F2FS support (will be available later when kernel is ready)
- Fixes to get Omni build.
- Reinstate some Omni features (eg. reboot menu)
Know issues:
1. Default Omni Wallpaper not show (Select with File explorer again will bring it back)
2. Only the interactive Governor is complete. Other Governors might require adjustments.
3. May be more....
Screenshots:
Downloads: :highfive:
Host: Android File Host mirror: 百度网盘
Gapps: ** We have a 650M system partition. Only pico Gapps can be installed.
All those with pico Gapps is recommended. (eg. OpenGapps)
** latest TWRP is recommended.
Omni is not rooted. To root, flash the latest systemless SuperSU(2.6x) from @Chainfire in recovery.
Source:
kernel & device trees on Github
Credits: :good:
** The OmniROM team who have such a good idea and their hardworks
** Dmitry Grinbeg for his work making our life easier.
** All those who donate and/or help the developers. Giving us the resources and reason to carry on.
** @Chainfire for the great SuperSU
Donations: :angel:

Great. I am using OmniRom4.4. Definitely gonna try this one. Thanks for the efforts u put into it.

Looks great! Any recommandations regarding the need to upgrade Bootloader/Radio or anything else before switching to MM Omni?

Title says 30OCT... Might wanna correct that

cosmickamal said:
Great. I am using OmniRom4.4. Definitely gonna try this one. Thanks for the efforts u put into it.
Click to expand...
Click to collapse
Omni is always one of my favourite.
Bingoig11 said:
Looks great! Any recommandations regarding the need to upgrade Bootloader/Radio or anything else before switching to MM Omni?
Click to expand...
Click to collapse
I haven't updated those for months so I think you may try directly.
KawaiiAurora said:
Title says 30OCT... Might wanna correct that
Click to expand...
Click to collapse
Yeah! That's a good example of "overlook".... Whatever corrections and suggestions are welcome.
Happy New Years!

daniel_hk said:
Omni is always one of my favourite.
I haven't updated those for months so I think you may try directly.
Yeah! That's a good example of "overlook".... Whatever corrections and suggestions are welcome.
Happy New Years!
Click to expand...
Click to collapse
Lol :3 Good job on porting OmniROM! Hmm, does OmniRom contain a custom switcher like Slimrom does with Slimrecents?

KawaiiAurora said:
Lol :3 Good job on porting OmniROM! Hmm, does OmniRom contain a custom switcher like Slimrom does with Slimrecents?
Click to expand...
Click to collapse
No. Just the AOSP style recent menu with a "clear all" switch at the bottom.
EDIT: I forgot there is the OmniSwitch which is a side panel.

This is fantastic! Thank you so much! How awesome to find a build of OmniROM on the latest AOSP.
I didn't realize OmniROM was still being actively developed on this level, but this really is a great ROM. I was a big fan of OmniROM back in 2014, but lost interest when it seemed to take forever for them to get a stable release of Lollipop together---turns out Android never really produced a stable release in the 5.x AOSP branch. lol
I feel pretty confident that this will be my daily driver on my N7 for a while now, so long as it stays current with new releases of AOSP. It has just the right amount of minimalistic customization built in, without needless or buggy features. I love that I can adjust the CPU clock speed right the settings, and that there is a beautifully simple dark theme built in.
Two quick questions though...
1) Does this (or could it) include some of the performance boosters that @AndDiSa has in his excellent ROM, namely the "low memory device," and ZRAM tweaks?
2) Will the built in OpenDelta system for incremental system updates work? That feature was killer back in 2014.
For anyone not familiar with the process or unsure of what to do, here are the steps I took:
1) Wipe system, data, cache, dalvik cache.
2) In TWRP 2.8.7.0... Flash current omni-6.0.1 zip.
3) Flash current OpenGapps pico. (http://opengapps.org/)
4) Flash current BETA-SuperSU-v2.65. (http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3)
5) Flash one of the current remove journaling .zips floating around. (e.g. http://forum.xda-developers.com/showthread.php?t=2280496)
6) Boot tablet, and after setup install the Trimmer app and set to run fstrim daily. (https://play.google.com/store/apps/details?id=com.fifthelement.trimmer)
7) Increase to max CPU clock speed in Settings > Performance.
I mostly use this tablet for reading, browsing, email, and texting, so I can't comment on things like gaming performance, camera, music playback, etc. (I removed those apps). That being said, so far performance and stability seem to be the best I've seen on this tablet yet, and I don't notice any problems or anything not working.
Great work!

wrkerr said:
This is fantastic! Thank you so much! How awesome to find a build of OmniROM on the latest AOSP.
I didn't realize OmniROM was still being actively developed on this level, but this really is a great ROM. I was a big fan of OmniROM back in 2014, but lost interest when it seemed to take forever for them to get a stable release of Lollipop together---turns out Android never really produced a stable release in the 5.x AOSP branch. lol
I feel pretty confident that this will be my daily driver on my N7 for a while now, so long as it stays current with new releases of AOSP. It has just the right amount of minimalistic customization built in, without needless or buggy features. I love that I can adjust the CPU clock speed right the settings, and that there is a beautifully simple dark theme built in.
Two quick questions though...
1) Does this (or could it) include some of the performance boosters that @AndDiSa has in his excellent ROM, namely the "low memory device," and ZRAM tweaks?
2) Will the built in OpenDelta system for incremental system updates work? That feature was killer back in 2014.
For anyone not familiar with the process or unsure of what to do, here are the steps I took:
1) Wipe system, data, cache, dalvik cache.
2) In TWRP 2.8.7.0... Flash current omni-6.0.1 zip.
3) Flash current OpenGapps pico. (http://opengapps.org/)
4) Flash current BETA-SuperSU-v2.65. (http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3)
5) Flash one of the current remove journaling .zips floating around. (e.g. http://forum.xda-developers.com/showthread.php?t=2280496)
6) Boot tablet, and after setup install the Trimmer app and set to run fstrim daily. (https://play.google.com/store/apps/details?id=com.fifthelement.trimmer)
I mostly use this tablet for reading, browsing, email, and texting, so I can't comment on features like camera, music playback, etc. (I removed those apps). That being said, so far performance and stability seem great, and I don't notice any problems or anything not working.
Click to expand...
Click to collapse
My tilapia is also my daily driver so my main concern is stability. I didn't try all the fancy features, at least not in deep.
1. I need the mobile data so I haven't studied gouper ROMs in deep yet but I think most of the tweaks are already there.
I also have a few threads on my other device (GalaxyTab 7.7) which has even lesser RAM. Therefore I tried KSM and zRAM for some time. I'm not a gamer nor a frequent Youtuber (Thanks for those "genius" politicians, I can't access Google service locally without a VPN!). Those features doesn't help me. In KK and early LP, I enabled those supports in the kernel and add a configuration page in the performance settings. I let the user to decide if they want them. After a while, those inquiries seems lost their interests and I stop updating it. I might do the same if it is really that important to someone.
Actually, I'm already on a test build before releasing this one. For journaling, I'm using the journal_async_commit flag instead of completely disabling it. I think it is safer and yet reducing some overhead. I tested both briefly with a few benchmark apks. The difference is not obvious.
I also disabled some wakelocks, hoping to extent the battery life. Together with a few bug fixes, I'm live testing it now. I don't have too much resource and I'm maintaining a few threads at the moment. I usually release weekly or longer. I rather sleep on it for several days instead of rushing it out.
Correct me if I'm wrong. I'm open to all suggestion or corrections.
2. OpenDelta is for official only. It simply requires too much resources (space and bandwidth) to maintain. I don't think any individual would have that kind of resources to maintain one. I don't know if Omni still support it but donations are essential for them.
There are a few things can be done (eg. f2fs support in the kernel) but not that urgent. I rather get rid of all the bugs first. At the moment, Gapps are the source of errors. Any suggestions are welcome.
Edit: Sorry, I overlook the fstrim part.
Take a look at the file MountService.java
Since KK, fstrim is embedded in an idle maintenance service. It will be executed when the tab is idle at midnight and battery is over half (forgot the exact value). Some might notice extra background activities since then.
In the age of LP, the aggressiveness is increased. If the backgroup fstrim is not done for a period of time, it will be forced to execute in the next reboot. That means even if you turn the device off at night, fstrim will be executed the next time you turn it on.
Therefore I don't think explicit fstrim is required after KK.

How long should first boot take? I tried full wipe dalvik,cache, data, system, then flash omni 6.0.1, pico gapps, su 2.65, and then boot. I just get animated omni logo for like 15 minutes before i shutdown. Thank you.

alcuin said:
How long should first boot take? I tried full wipe dalvik,cache, data, system, then flash omni 6.0.1, pico gapps, su 2.65, and then boot. I just get animated omni logo for like 15 minutes before i shutdown. Thank you.
Click to expand...
Click to collapse
It shouldn't be more than 15 min. If you have f2fs partition(s), it might not boot at the moment....
If this is the case, you might need to wait or reformat.
I'm on a test build which supports f2fs. Right now, I can only test the cache partition because I still need the data (about 20G which might take hours to back up...).
If nothing ugly float up, I'll release it in a few days.
Sent from my Nexus 7 using Tapatalk

I'm eager for f2fs support. In the past, that really seemed to boost performance, on lollipop at least.
I have noticed a few freezes and crashes lately, and sometimes autorotate stops working, so hopefully the new build will correct some of that.
Thanks for your work!
Sent from my Nexus 7 using Tapatalk

wrkerr said:
I'm eager for f2fs support. In the past, that really seemed to boost performance, on lollipop at least.
I have noticed a few freezes and crashes lately, and sometimes autorotate stops working, so hopefully the new build will correct some of that.
Thanks for your work!
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
OK, I made a patch for those want to test before the next release.
As usual, backup first! Flash this View attachment omni6-patch-20160103-nexus7.zip in recovery. It should work for both grouper and tilapia.
The latest fixes are:
kernel: bug fix in voltage control, f2fs support, enable journal_async_commit for ext4, time out for RIL wakelock
platform: a fix for rotation fail after deep sleep (hoping it work)
Note: you need to flash SuperSU again to regain ROOT.
Please report and Good luck!

Awesome work dev. I see that you are supporting tilapia (thankfully some one is). I have been running grouper MM fw on mine. I tried patching their kernels to include the BASEBAND_XMM wakelock fix, but didn't seem to prevent that wakelock. Maybe it was a poor implementation. I've not seen my n7 sleep on MM yet because of this bug. Hopefully your ROM does the trick. Off I go to backup and flash.

enzoevo said:
Awesome work dev. I see that you are supporting tilapia (thankfully some one is). I have been running grouper MM fw on mine. I tried patching their kernels to include the BASEBAND_XMM wakelock fix, but didn't seem to prevent that wakelock. Maybe it was a poor implementation. I've not seen my n7 sleep on MM yet because of this bug. Hopefully your ROM does the trick. Off I go to backup and flash.
Click to expand...
Click to collapse
Sure! I got the tilapia too.
Make sure you got the patch in post#13. It included the wakelock fix.
SuperSU should be the last to flash.
Good luck!

Is busybox installed as well?

Hi all, for some reason there is no sound... device is muted! Any idea what's wrong?

Flashed supersu beta 2.66, can't seem to get root however
Edit:
Nevermind. It took after the 3rd try. Weird.
---------- Post added at 03:17 PM ---------- Previous post was at 03:06 PM ----------
Sound works for me.
---------- Post added at 04:13 PM ---------- Previous post was at 03:17 PM ----------
Everything seems to be working now for me. I installed the patch and will see if it will sleep.
Feature request. 3minit battery mod = https://github.com/gharrington/framework_base/commit/dec329383060c4c6044b980a49d0578e828d6a5d
Also, any chance you are willing to share your source repo so we can tinker?
Thanks.

Did you say OC, OC!!! On a device not supported officially THIS EARLY!!! Gonna try right now!!!

Sleeping like a baby on Benedryl. Awesome.
---------- Post added at 09:47 PM ---------- Previous post was at 09:46 PM ----------
I did have a freeze while I was in Chrome Beta. Rebooted then ran Dungeon Hunter 4 for an hour without any issues. Thanks again dev.

Database Info

welcome