Database Info

[Kernel] CM6-Snapv7.6 Turbo! Splash Screens, Papersv4, Widgetv5

{
"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"
}
Join us on irc.freenode.com #cm6-snap​
Snap F.A.Q.
(maintained by shift_)​
Click to expand...
Click to collapse
Daily Drivers
The best options for daily drivers are:
Downloads:
cm6-snap-v7.5-havs925 Download md5 bcdb177c62b51542e450ce2e620fea45
cm6-snap-v7.01 Download md5 80cfe44a7043a4a6d06cd0eefca88bb4
cm6-snap-v7.11 Download md5 9ed1236e28a82766f46c5eea994eac5e
Read the rest of the OP and ask questions in the thread for additional information.
Click to expand...
Click to collapse
Snap kernels are built to work only on CM6 based ROMs
You assume all responsibility for the use of this software.​
Version 7.6 [cfs/bfs]/nhavs925/qs2
Before I start, I want to give a special thanks to the usual suspects: spiicytuna for his work on SNAPturbo, and shift for his outstanding graphics work. We also had a very helpful beta testing team open their phones up to some fairly wild experimentation and some late nights: drmacinyasha, jabbawalkee, i[e, gerald410, swatspyder, nicholaaaas, mrkmrk, and jsseidel1. (Deepest apologies if I missed anybody, please let me know and I'll update the list)
Initially there are two releases of v7.6: CFS and BFS. Try both and use the one that works best for you. v7.6 is built from the CM6 2.6.32.15 source. It includes the first release of SNAPturbo, SNAPpapers, SNAPwidget, overclocking to 1.19ghz, netarchy's modified HAVS [nHAVS], and my modified conservative governor. You do not have to utilize SNAPturbo: It is an optional feature. Instructions for use are below.
The BFS version of v7.6 uses BFS Scheduler-v318 of BFS because this version currently provides the best results on CM6. All other features of the BFS release are identical to the CFS release.
SNAPturbo
SNAPturbo is a proprietary application designed to enhance system performance with no additional overclocking or battery penalty. SNAPturbo is not derived from the kernel source, is not subject to GPL, and the source code will not be shared, so please do not ask. SNAPturbo may not be distributed without prior written consent from jmxp69 and spiicytuna. SNAPturbo will only activate on a snap kernel.
Once you've successfully activated Turbo, you never have to do it again as long as you stick with a v7.6 kernel. You can safely flash v7.6 directly on top of CM6 nightlies in the same recovery session.
Before using SNAPturbo, please follow these instructions:
Perform a nandroid backup. Really, you should be doing this anytime you flash customized software.
Optional but recommended: Use Titanium Backup or My Backup Pro (available in Market) to backup your data and applications.
Enable Airplane Mode
Run the SNAPturbo application
Give SNAPturbo SU permissions
Do not touch any controls or the screen until after the phone reboots.
Note: You will probably see force closes while running SNAPturbo. This is normal and expected. Just let SNAPturbo run and it will reboot your phone when it finishes.
Known Issues
Important: During beta testing, some members of the beta team reported they stopped receiving SMS messages. We were unable to directly correlate this to anything happening with the kernel. In other words, it was not repeatable and the majority of testers never saw the issue. In one case, a re-flash of CM6 restored inbound SMS, and in another, it took a re-flash back to Stock Sense (with root). In each case after flashing either CM6 or a Sense ROM, the testers were able to re-flash v7.6 and never encountered the issue again.
Occasionally after activating SNAPturbo, one or two applications may repeatedly FC after rebooting. If this happens, try clearing data in application manager or just re-install the app. This has cleared the problem 100%.
SNAPturbo may look like it's destroying your phone when it runs. You may see force closes and maybe even smoke coming from the battery compartment. This is NORMAL. Let it run, leave it alone, and it should reboot on its own. After reboot, your phone should run normally. (Actually, I'm kidding about the smoke, but it does look ugly at first. Just let it ride…)
If for whatever reason SNAPturbo does not reboot your phone and return you to normal operating conditions (boot loops/odd behavior):
Do not attempt to re-activate.
Use the failsafe installation method listed below.
The only current method of disabling SNAPturbo is to wipe. v2 of SNAPturbo will provide a disable function.
Screen Tearing - v7.6 sets Nova panels T2 to 380. Previous testing indicates this is the best option for most phones. If you encounter any tearing, find Assasainslament's Novafreq and try 371.
After enabling turbo, if SetCPU FC's, uninstall and reinstall. That fixes it.
Failsafe Install
As much testing as went into SNAPturbo, the possibility exists you may run into problems. If you do, the following method is known to work 100%.
Backup apps with Titanium or My Backup Pro
Wipe Everything
Flash CM6
Flash v7.6
Reboot-DO NOT sign-in to Google
Turn Airplane Mode On
Activate Turbo
Sign-In to Google (Open Market)
Restore Apps
Resume normal use
Flashing Nightlies
If you flash a new nightly, make sure you flash v7.6 immediately afterwards. I recommend flashing in the same recovery session. If you do not flash v7.6 after flashing a nightly, you will bootloop.
If you forget to flash v7.6 after a nightly and you start to bootloop, just go back into recovery (hold Volume down while powering phone on) and flash v7.6. You will work fine afterwards.
v7.6 Changelog
Kernel now includes SNAPturbo application only. All other applications have been removed
Set the maximum CPU freq to 1.19. Many people were able to run 1.22g, but there is no practical benefit to doing it, so 1.19 is the new max across all revisions.
Minimum UV is 925. I've found this value to be the most stable and best for my battery.
Added Koush's AnyKernel Updater. Wiping Dalvik should now be a thing of the past.
BFS Version: Revert to BFS v0.318
Set interactive as default governor
Legacy snap tweaks to filesystem, network, vm, etc..
Tweaked conservative governor timings
Downloads
Click to expand...
Click to collapse
SNAP Extras - Here are a few extra user installable goodies to round-out SNAP on your CM6 installation.
SNAPsplash
For even greater Snapification of your phone, check out the graphics madness from Shift available now via SNAP Themed Splash Screens. Shift posted screenshots and detailed instructions here.
Update: SNAP Turbo Splash Screens now available in the Extras folder. See this post for screenshots.
Downloads
Click to expand...
Click to collapse
SNAPpapers
SNAPpapers is for those who want to sport their love and support for SNAP. Application credit goes to spiicytuna with wallpapers by Shift. It will work on any version of CM6, even if you don't have a SNAP kernel installed.
You install SNAPpapers just like any other .apk and use it by long press on the home screen, selecting wallpapers, and clicking SNAPpapers. For those unsure on how to install SNAPpapers: download a versions below and simply do an "adb install c:\path\to\snappapers.apk" or download an installer from the Market and install the SNAPpapers.apk from your sdcard.
v0.0.5 Changelog
New Snap Graphix themed wallpapers
Includes everyone's favorite Timeless Classic wallpapers (a la Lady in Red & Grunges)
Known Issues
Link to SNAP thread is not clickable as of yet
Planned Updates
Clickable link(s) to SNAP thread
Live wallpapers
v0.0.3 Changelog
Some wallpapers from v1 & v2 modified as per request
More wallpapers, including pics graciously provided by kpoz
known issues
Link to SNAP thread is not clickable as of yet
Planned Updates
Clickable link(s) to SNAP thread
More requested wallpapers
Live wallpapers
???
Downloads
Click to expand...
Click to collapse
SNAPwidget
The SNAPwidget is a widget created by our own spiicytuna for use with snap kernels that utilize H/AVS. It will not work on non-snap h/avs kernels. You install this just like any other .apk and
use it just like any other widget--ie. long press on the home screen. For those unsure on how to install SNAPwidget: download a version below and simply do an "adb install c:\path\to\Widget.apk" or download an installer from the Market and install the SNAPwidget.apk from your sdcard.
The goal of SNAPwidget is to provide easy access to H/AVS adjusted voltage at any given CPU frequency. The widget also displays the current battery draw in mA; red for discharging, and green for charging. Testing has shown no noticeable loss of battery with SNAPwidget when using update intervals of greater than 15 seconds; even with logging enabled.
**Please note that the frequency and temperatures displayed may not match setCPU. Rest assured that SNAPwidget has been triple checked and it's information is exactly the same as what the kernel/EVO is providing.
v0.0.5 Changelog
FIXED: bug that widget showed o[email protected]
Planned Updates
Additional skins/colors (post suggestions to thread)
Downloads
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Version 7.5 BFS/UV/OC/nHAVS
v7.5 is built from the CM6 2.6.32.15 source. It incorporates the latest BFS Scheduler-v0.330, overclocking to 1.19g, netarchy's modified HAVS [nHAVS], and my modified conservative governor.
There have been some mixed results with v8.x kernels. Some people have charging issues, some don't. Some people have screen tearing issues, some don't. While 2.6.34 issues continue to be sorted out, I decided to release a known stable version with the latest BFS/nHAVS implementation.
Known Issues
Testing revealed a down threshold of approximately 40 for the conservative governor to yield the best screen interaction. You can set this value in the advanced tab in SetCPU.
Since the introduction of AVS, some users see bootloops after installing. The known fix is to wipe dalvik. Since moving away from the ultra-undervolt kernels, I have yet to see a bootloop on my device. YMMV--if you encounter a bootloop, wipe dalvik.
This kernel is not as fast as v8.x. It's not because anything is wrong, it's because it is an older kernel revision. Please do not fill up the thread complaining about quadrant scores. For reference, I saw [email protected] vs [email protected] on v8.x
v7.5 Changelog
Set the maximum CPU freq to 1.19. Many people were able to run 1.22g, but there is no practical benefit to doing it, so 1.19 is the new max across all revisions.
Minimum UV is 925. I've found this value to be the most stable and best for my battery.
Added BFS v0.330
Built with CM-6.0.0 ramdisk. Works great on the first official CM6.
Legacy snap tweaks to filesystem, network, vm, etc..
Tweaked conservative governor timings
Downloads:
cm6-snap-v7.5-havs925 Download md5 bcdb177c62b51542e450ce2e620fea45
Click to expand...
Click to collapse
Version 8.2/BFS/U-UV/OC/nHAVS
v8.2 is built from Toastcfh's 2.6.34 source. It incorporates the BFS Scheduler, Overclocking to 1.19g, and netarchy's modified HAVS [nHAVS].
With BFS enabled, we're seeing quadrant scores approaching 2000 @ 1.19g. Stock frequencies (998mhz) routinely achieve 1500-1600.
Known Issues
Some phones have demonstrated difficulty charging via AC. So far, I've been unable to replicate the issue. I'll keep an eye out for updates and apply anything that looks relevant.
In-line headset buttons don't work. I patched 8.2 with the latest HTC Headset driver, but I don't believe this fixed the problem.
Led Flashlight - Toast commented that Torch didn't light the led flashlight on github. I have not experienced this problem. Two tools I've used (torch and switchpro widget) both light the camera leds just fine on my phone.
Conservative CPU governor is the default in v8.1 and it does not appear to log the correct minimum CPUFreq in kmsg so the snap widget will continually report 384mhz. You can check the actual frequency with:
Code:
adb shell s.getfreq
This should show you 245mhz if your phone is idle. If this really bothers you, switch to interactive as your default.
v8.2 Changelog
IPv6 added (Google Goggles fix)
Set the maximum CPU freq to 1.19. Many people were able to run 1.22g, but there is no practical benefit to doing it, so 1.19 is the new max across all revisions.
Added BFS
Regulator patch from toast's github
Built with CM-6.0.0 ramdisk. Works great on the first official CM6.
Fixed 802.11n - works again
Legacy snap tweaks to filesystem, network, vm, etc..
Tweaked conservative governor timings
Downloads:
cm6-snap-v8.2-havs800 Download md5 45a9428cf556d4d44d16dbb295b41d23
cm6-snap-v8.2-havs825 Download md5 5f207d52e44878b8fdae78fc541e8db9
cm6-snap-v8.2-havs850 Download md5 668f0eb6115c68e980b37a0867c867c9
cm6-snap-v8.2-havs875 Download md5 618b4c4c2dbff49ce5bf7816b054af3e
cm6-snap-v8.2-havs900 Download md5 7fd5a621592f4775ed971ce19ec71057
cm6-snap-v8.2-havs925 Download md5 262c5a836e75ac0643f7115fd7d5f853
Click to expand...
Click to collapse
Version 8.1/U-UV/OC/nHAVS
v8.1 is built from Toastcfh's 2.6.34 source. It incorporates netarchy's modified HAVS [nHAVS] introducing the ability to specify the maximum and minimum voltage range at every frequency step. This differs from the original implementation of HAVS which only permitted specifying the maximum voltage at a given step. By incorporating a minimum we still benefit from voltage scaling, but it provides a little human intervention to prevent AVS from trying to undervolt too far.
This first v8.1 release uses an 850mv floor. With the more stable implementation of HAVS, I have high hopes that it addresses some of finicky behavior we've seen with previous revisions. My preference is to start reducing the number of versions in each release which is why this first version is U-UV or UltraUnderVolt.
This is a significantly faster kernel out of the box than .32.
Known Issues
Led Flashlight - Toast commented that Torch didn't light the led flashlight on github. I have not experienced this problem. Two tools I've used (torch and switchpro widget) both light the camera leds just fine on my phone.
Conservative CPU governor is the default in v8.1 and it does not appear to log the correct minimum CPUFreq in kmsg so the snap widget will continually report 384mhz. You can check the actual frequency with:
Code:
adb shell s.getfreq
This should show you 245mhz if your phone is idle. If this really bothers you, switch to interactive as your default.
I will closely monitor toast's github for updates to address this and other remaining minor issues.
v8.1 Changelog
Added Static version of Snap 8.1. This build eliminates nHAVS and uses stock frequency/voltage scaling. For those of you unable to find a stable nHAVS implementation, this one is for you.
Removed 1.22g in havs825. We've gone back and forth with 1.22 in various revisions of snap, but I've come to the conclusion that downside outweighs upside. So 1.19g will be the new max in snap going forward.
Fixed 802.11n and Wifi AP.
Merged netarchy's HAVS from .32 enabling specification of min/max AVS voltages at each frequency step.
Built with CM-6.0.0 ramdisk. Works great on the first official CM6.
Fixed 802.11n - works again
Fixed 1.22g - confirmed working
Legacy snap tweaks to filesystem, network, vm, etc..
Removed - Added OC up to 1.22
Tweaked conservative governor timings
Downloads:
cm6-snapv8.1-static.zip/OC Download md5 30485362938e2c586d6abc4b67479487
cm6-snap-v8.1-havs825/OC Download md5 5b4949ab11c81ffb30e107a3dcbce0b0
cm6-snap-v8.1-havs850/OC Download md5 99955f8d1a6eaeb98ffa7d578717cb73
cm6-snap-v8.1-havs900/OC Download md5 8fc3b56f0a50d1dfae4e80715a9abc5d
Click to expand...
Click to collapse
Version 7.4 HAVS/OC/UV
The 7.4-havs kernel incorporates BFQ and AVS. After spending some quality time discussing HAVS with intersectRAVEN, this release should work on most phones. If it doesn't work for your phone, let me know in the thread and we'll try to sort it out. v7.4 is a minor update from v7.3 below focused on enabling stable Hybrid AVS. BFQ from v7.3 is also included, but I took it out of the kernel name because it's also now a standard feature in CM6.
About AVS
Code:
Adaptive Voltage Scaling (AVS) for ARCH_MSM_SCORPION
The AVS driver adjusts the CPU voltage based on hardware feedback. Using
hardware feedback AVS is able to achieve lower voltages than the equivalent
static voltage scaling (SVS) voltage.
The Scorpion architecture includes three ring oscillators for AVS. The
ring oscillators provide real time feedback about the voltage requirements
for the current operating conditions. The hardware can sense when the voltage
can be lowered and needs to be raised.
The AVS software keeps track of the current operating conditions. Periodically
AVS queries the hardware. Every query AVS updates a table of required voltage
indexed by operating conditions, CPU frequency and temperature.
This first release uses 975mv as the floor voltage based on intersectRaven's test results from his work on the N1. The current release plan for 7.4 includes:
UV - 975 - Available now
UV - 875 - Available now
UV - 825 - Available now
Version 7.4-havs Changelog
Modified conservative CPU governor set as default. Modifications designed to reduce scaling lag.
HAVS implemented with min voltages set to 975mv in -havs975 and 875mv in -havs875
Known Issues
Do not reboot your phone with adb reboot. Use the power button and reboot/power off from within the phone. Using adb reboot causes HAVS minimum voltages to stay at the maximum specified in the AVS voltage table. This will cause battery drain equivalent to stock kernels.
If you get a bootloop after installing one of the v7.4 kernels, reboot into recovery and wipe dalvik/cache. That generally fixes things.
Downloads:
cm6-snap-v7.4-havs975/OC/UV Download md5 d121ee63c9f147dcadd91ebd1626fa83
cm6-snap-v7.4-havs875/OC/UV Download md5 cb4ff35841eadc47651e19d24c7f64cf
Avoid this one unless you know what you're doing.
cm6-snap-v7.4-havs825/OC/UV Download md5 d138071715a7d5137622c57867f56271
A big thanks to intersectRaven for discussing AVS with me and clearing up some nagging problems!
Click to expand...
Click to collapse
Version 7.3-avs
The 7.3-avs kernel will be the only 7.3 option. I've decided against making a 7.3-noavs version because BFQ is not enough of a performance enhancement to warrant a new revision beyond 7.x1. So if you can't run AVS, I suggest you stick with 7.01 or 7.11. Version 7.3-avs incorporates BFQ and AVS (see codebox below).
** Note: The version numbers are known to be off in the betas.
Click to expand...
Click to collapse
Experimental zImages
Experimental zImages are provided only for those interested pushing their devices for even more performance. They are not intended as daily drivers, although some may find them perfectly acceptable as a daily driver.
I will not provide update.zips for experimental zImages so please don't ask. These zImages are intended for seasoned users who are comfortable restoring their phones and using fastboot.
Please see the readme in each download section for further information.
CFS Releases
v7.6cfs-havs800
v7.6cfs-havs825
v7.6cfs-havs850
v7.6cfs-havs875
BFS Releases
v7.6bfs-havs875
This zImage is identical to the production release of v7.6 except the undervolt floor has been dropped to 800/825/850/875 for 128 and 245mhz.
Download
Click to expand...
Click to collapse
Click to expand...
Click to collapse
EOL Revisions
cm6-snapv7.3beta1 (900mv) Download
cm6-snapv7.3beta3 (875mv) Download
cm6-snap-v7.3 AVS Final (875mv/tweaked conservative governor) Download
cm6-snap-v7.3-avs825 Download
cm6-snap-v7.3-avs850 Download
cm6-snap-v7.3-avs875 Download
cm6-snap-v7.3-avs925 Download
cm6-snap-v7.3-avs950 Download
cm6-snap-v7.01 Download
cm6-snap-v7.11 Download cm6-snap-v5.01 Download
cm6-snap-v5.11 Download
cm6-snap-v5.0 Download
cm6-snap-v5.1 Download cm6-snap-v4.0-cc Download
cm6-snap-v4.1-cc Download
cm6-snap-v4.0 Download
cm6-snap-v4.1 Download cm6-snap-v3 Download
Click to expand...
Click to collapse
Before proceeding, please run a nand backup!​
Download and Install
You do not need to wipe. Just flash over your CM6 nightly builds.
If you are flashing nightly CM6 builds, you'll need to flash this kernel again after each nightly. Just flash your nightly build, reboot and make sure everything is working, then reflash your favorite snap kernel.
Click to expand...
Click to collapse
v8: Thanks to toastcfh for his tireless efforts getting .34 working on CM6 and to netarchy for a great job modifying HAVS for stability.
I need to thank netarchy, assassinslament, joeykrim, sentenced, ffolkes, spiicytuna, and of course toastcfh for helping me along the way. Special thanks to ffolkes and netarchy for their work on the 2.1 kernels which has made its way to CM6. They are an incredibly helpful and patient group, and this community is lucky to have them working for all of us. Thanks to Cyanogen for providing crucial tips during the development of snap, and the entire CyanogenMod crew for a wicked 2.2 ROM. Thanks to intersectRaven for the AVS code.
GPL Compliance and Credits
My github
Koush for this exceptionally clever AnyKernel Updater template.
v8.x is built from toastcfh's source.
v8.1 nHAVS merged from netarchy's HAVS source.
spiicytuna for SNAPwidget, SNAPpapers, and the upcoming SNAPturbo.
shift for the incredible graphics work.
v7.x and below snap kernels are built from the CM6 git source.
v7 and below AVS code imported from intersectRaven git source.
Click to expand...
Click to collapse
Donate!
Ok, I've been asked multiple times how to donate for my work on snap, so I added a button to my sig.

Great job. Just installed it and working fine so far.
Will update more later after I put all my apps back on.
Thank you for the tweaks.

will this help improve battery or drop it quicker lol sorry

What the hell,Ill give it a shot.

Sporkman said:
will this help improve battery or drop it quicker lol sorry
Click to expand...
Click to collapse
Try it and tell me. It certainly will not *improve* the battery life, but I don't expect the penalty to be material.

E: No signature (11 files)
E:Verification failed
Installation aborted.
Any advice? Does this need to be run off Clockwork?

Fps2d before was roughly 49 fps with a stdev in the high 7s
now its 53 fps avg with stdev=5.26
gears is chilling at 53-54 fps
quadrant is 1279.
This is all without setcpu.

TheMike1 said:
E: No signature (11 files)
E:Verification failed
Installation aborted.
Any advice? Does this need to be run off Clockwork?
Click to expand...
Click to collapse
Yes, I'm sorry, I should have mentioned it's unsigned. I'll update the OP.
J

Just flashed, novatek 003 -- getting fps2d 51 with StDev of 9 after several runs, which is actually a slight downgrade. My Long Bench in SetCPU is in the 600's vs the 300's as before.
LinPack is very strange. I get my usual 39-43 but every once in a while it seems to lag and I get 2MFLOPS - 6MFLOPS, not 20, literally 2.
I have a feeling something must not be right, is there anyway to debug what is going on?

Didn't change anything, just sat around and did a bunch of LinPacks, then noticed they were pretty consistent so went into SetCPU and started doing a bunch of Long Bench, and actually started to get into the low 400s consistently, high 300s. Back to fps2d and now I am getting 54 avg with a 5.5StdDev consistently.
Strange, I cannot figure out what changed, any idea?
edit: Just ran a 1571 Quadrant too
My SetCPU Current profile btw is 1152max, 245min performance

It helps to let the phone settle for a while before testing. When you first boot, it's pretty busy.

This kernal just put me back to 29 fps. With or without setcpu. ?? Mflops was 46 tops though
Sent from my PC36100 using XDA App

TheMike: How does that quandrant score compare to your stock ROM?

jmxp69 said:
TheMike: How does that quandrant score compare to your stock ROM?
Click to expand...
Click to collapse
I am getting 1575+ Consistently now, vs 1400-1530 with CM6 stock kernel.
My stock ROM was like a 500 quadrant or something
This is Awesome!!
HAHAH! I just got a 1620 Quadrant with your Kernel, my first time breaking 1600
Awesome Kernel man, thank you very much

Attempted to flash this kernel on top of baked pastries beta 2 with the 2.2 update and just got a boot loop. The nexus boot logo animated fast then slower then screen for a blank and starts all over again.
Sent from my PC36100 using XDA App

rmriggin said:
Attempted to flash this kernel on top of baked pastries beta 2 with the 2.2 update and just got a boot loop. The nexus boot logo animated fast then slower then screen for a blank and starts all over again.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
This is based on CM6 rmriggin. Kernel update.zips contain ramdisks with rom specific information. So you can't do it that way. I could make the zImage, and modules available to you if you want to flash it with fastboot and manually copy the modules over. That would likely work.
J

If you want to experiment, this kernel may work on a non-CM6 or maybe even a 2.1 ROM with the following steps. I have no idea. Proceed at your own risk.
**Warning** Don't try this without a backup! You'll need to nandroid restore to undo this.
1) Download this and unzip on your PC (do not try to flash it).
adb shell reboot bootloader
fastboot boot zImage <-----this will let you test to see if it works. If it does, proceed with the following to survive reboot. If it doesn't work, just reboot your phone and you'll be back to normal. No other action required.
2) Move to a different directory from where you unzipped donotflash.zip and do the following:
adb pull /system/lib/modules/bcm4329.ko
adb pull /system/lib/modules/sequans_sdio.ko
Save these somewhere safe.
3) From the location you unzipped donotflash.zip:
adb remount
adb push bcm4329.ko /system/lib/modules/
adb push sequans_sdio.ko /system/lib/modules/
adb shell reboot bootloader
fastboot flash zimage zImage ** pay attention to the caps!
fastboot reboot
If you try this, I'd be interested in hearing about your results.

Thank you so much for this kernel, I ran my FPS2d app on the HTC EVO 4g running under the latest Cyanogen ROM and I get 54 AVG with 5.45 stdev...
It's a lot faster and I'll check about battery usage when I get a full charge overnight.
Thanks again!

Quick question.. I've flashed latest nightly today and I'm capped at 28~30 fps now.. and I flashed this kernel and still stuck at 30 fps.. can anyone tell me what might be causing this? Any help will be greatly appreciated.
Sent from my PC36100 using XDA App

mizerab1e said:
Quick question.. I've flashed latest nightly today and I'm capped at 28~30 fps now.. and I flashed this kernel and still stuck at 30 fps.. can anyone tell me what might be causing this? Any help will be greatly appreciated.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Do you have setCPU installed? If so, uninstall it, reboot, and see what happens.

[ROM][Sept26][INSPIRE] Virtuous Unity 2.39.0 Sense 3.0 Based on Pyramid

{
"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"
}
Virtuous Unity is the first custom Sense 3.0 ROM, scaled for WVGA screens, to be based on an official shipping release from HTC (1.45.401.2).
The entire ROM is brand new, taking no application or framework components from any prior Sense 3 releases.
Unity is the result of a collaborative, team effort by the following developers:
Flemmard
Diamondback2010
rmk40
chrisch1974
m-deejay
seo
eViL D:
cypis
cjward23
Screenshots
Features
Based on the official Sensation shipping ROM (1.45.401.2).
Ported for full functionality on each supported devices. Additional device support is being added regularly.
Resized for WVGA (800x480) displays, using a purpose built tool to modify HTC's proprietary m10 binaries, developed by Flemmard and Diamondback.
Heavily optimized for fluid performance and usability.
Overclocked kernels with numerous additional kernel modules.
Built-in screen state frequency scaling (1.2Ghz-245MHz/ondemand screen-on, 806Mhz-245Mz/conservative screen-off), via custom built Virtuous_OC C daemon.
Trackpad wake support (DesireZ/G2 and MT4G only).
WiFi calling (T-Mobile USA only).
Fully functional device hardware, including wifi, bluetooth, camera, camcorder, etc.
Market-sourced applications (Gmail, Maps, Voice, etc) automatically installed on first boot into /data/app for easy removal.
Bloatware and unnecessary applications removed.
Supported Devices
Desire HD
Desire Z
Desire S
Incredible S
Inspire 4G
myTouch 4G
Porting Information and Credits
There has been an enormous amount of interest surrounding utilizing components or modifications from our ROMs. To this point, our policy was that any such work needed to explicitly be approved by the team. The fact of the matter is that the policy is simply not enforceable and any time consumed working to enforce it detracts from the time we have to work on Android (which is what we really enjoy). As such, we’ve decided to go in a different direction.
Going forward, ROM developers are welcome to utilize any portions of our ROM which are of interest.
Our only requirement is that you let us know about what you’re doing by sending an email to (devteam|at|virtuousrom.com), credit the Virtuous Team in your thread(s) and provide a link to our website. No response on our part is required whatsoever, we’re just interested to hear about how our work is helping you.
Our plan is to continue to innovate and push the envelop of ROM development; with the goal of staying enough ahead of the curve to merit a desire to clone our work.
hrk - Allowing use of ghostySMS Vision version.
cypis - For his awesome Unity-banner
robocik - Tips regarding APK compression.
capychimp - Tips with DHD audio optimization.
HTC/Google- For building such a good base system.
Important Notes
If you are experiencing random freezes and/or reboots, this is likely due to your device being incapable of handling our overclocking defaults. Download and apply this flashable patch, which will reduce the maximum CPU frequency to 1Ghz and likely eliminate this issue.
You must complete a full wipe prior to installing this ROM the first time. We also recommend wiping between upgrades, but you are welcome to try upgrading without a wipe. However, no support will be provided if you file a bug without having wiped prior to submission.
Bugs and Errors
To ease the process of reporting bugs to the team, we made a public bugtracker where you can report the bugs you found. Please make sure you read all the existing entries there to avoid doubling the errors.
The bugtracker is located here.
Device specific information
Download :: Changelog :: More Information​​(Official Website of Virtuous ROM)​Check out our forums​

Install instructions (thanks to lollylost100):
1. Make a full wipe (please don't use Full Wipe 1.5 (EXT4) or such tools)
2. Flash ROM
3. Reboot
Please keep in mind:
You can always try to do a non wipe install, but we can't provide you support in this case.
If you find any errors in the ROM and you have NOT wiped before, please wipe and see if the errors persists.
Special features
This ROM has some unique or not widely known features which I want to explain here.
Screenshot
This ROM (in fact most Sense 3 ROMs) has the unique feature to make screenshots without any additional app.
Just Hold the "Power"-Button and then press "Home" at the same time and the phone will save your screenshot in the Images folder on you SD-Card.
OC Daemon
This ROM deals with overclocking a little bit different than other ROMs. To get further information read this post.
Fancy input animations
Unfortunately HTC removed from all their Sense ROMs the "open" and "close" animations for the keyboard.
Thanks to seo we were able to get them back
There are two different animation versions. The normal one is always activated and there is also no way to deactivate it.
The second "fancy" version can be enabled via the app "Spare Parts" which is in the Android Market.
Custom user app install during first boot
The ROM has the ability to automatically install custom user apps during the first boot (after a wipe)
All you need to do is the following:
Create an folder on your SD card and name it virtuous_unity
Create another folder inside virtuous_unity folder and name it 'app.user'
Copy all the desired apps in this directory in there paketname form, for example: 'com.quoord.tapatalkxda.activity.apk'
Now flash the ROM via your recovery
During the first boot the apps get installed from your SD card, as this will take a while, don't get impatient
Release strategy
We are planing to release our ROM in the future every week on the same day and around the same time.
This point in time will be every Monday night (GMT). Which is ca. 24h from NOW.
If there are no MAJOR bugs we will release what ever we have done at this time.
Saturday night (GMT) is the so called feature freeze, then the ROM will enter the testing phase. It gets tested until monday and then the team will talk about the results.
Once everything is approved we'll release the next version.
As you should know now when the next version arrives I won't answer ANY questions concerning ETAs.
Further information and support at #virtuousrom on Freenode

Changelog
Our changelog lives here.
Supported devices
Desire HD (Ace)
Desire Z (Vision)
Desire S (Saga)
Incredible S (Vivo)
Inspire 4G
T-Mobile MT4G (Glacier)
Addons for v1.27.0
CRT patch (add CRT animation): Flash in recovery.
NO CRT patch (revert CRT animation back to stock): Flash in recovery.

Introduction to the new Overclocking Daemon
This ROM features a completely new way of Overclocking and managing screen states.
The History
But before explaining it further, let's talk about previous solutions.
There are several different approaches to archieve "screen-state-scaling".
That means basically that the govenor changes if you turn the screen off and changes back to normal when turning the screen on.
This is mainly used to restrict the amount of CPU usage (the frequency in fact) during screen off. This can lead to a major battery life increase.
The solutions so far were:
App like SetCPU, which change automatically the govenor based on profiles
integrated solutions in the govenor itself
Both these solutions have major problems.
The one with a tuner app is always a little laggy right after turning on the screen because SetCPU (or any other CPU tuner) needs some time to change the govenors (up to 7 seconds). This leads mostly to major lag in the lockscreen.
The second solution is the smartass govenor. It has already a screen-state-scaling included, so it reduces the frequency when the screen turn off.
This could be a really nice solution but it has some problems too.
Smartass most of the time is not really stable and has problems with its frequency scaling.
State-of-the-art-solution
So we (more precisely rmk40) thought of a better solution.
He wrote a native C Daemon which changes the govenors instantly without any lag.
This leads to major performance improvements right after turning on the screen and in the lockscreen.
But at the moment this solution is a little bit harder to configure. We are plaing to make a GUI for this, so you get the same comfort as using SetCPU.
Nevertheless you can even now adjust the daemon to your needs.
Be aware that the daemon only works if all CPU tuner apps are deinstalled. Otherwise it deactivates itself.
How to adjust the daemon
The daemon is configured with 6 files in the folder /system/etc/virtuous_oc/.
There are 3 files for the wake state and 3 for the sleep state. For each state one file for the govenor, one for the minimal frequency and one for the maximal frequency.
You can easily edit these files eg. with RootExplorer or any other app which can edit system files. So you can adjust the frequencies and the govenor for each state just like with SetCPU.
In order to get the available frequencies for the current kernel, just open your favorite terminal app and type
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
You could also use adb shell to show the frequencies on your computer.
To get the available govenors use a similar approach:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
Please make sure, you are entering the right values in the daemon's config files.

reserved for future use4

At the risk of sounding like a complete ass, if we are already running VU 1.0, do we still need to wipe data, or can we leave that partition be? I'm asking because the previous thread for 1.0 indicated that future releases would not require a full wipe, so the instructions above are not entirely clear for those of us who are already on board.
Thanks for keeping up the great work!!!!!

BillTheCat said:
At the risk of sounding like a complete ass, if we are already running VU 1.0, do we still need to wipe data, or can we leave that partition be? I'm asking because the previous thread for 1.0 indicated that future releases would not require a full wipe, so the instructions above are not entirely clear for those of us who are already on board.
Thanks for keeping up the great work!!!!!
Click to expand...
Click to collapse
Wait for me to finish the post
Easy way : no wipe = no support, wipe = support

LOL! Sorry, pulled the trigger a bit too quick on that. Been anxiously looking forward to this release and jumped the gun.

Do the widgets with buttons still hang below Rosie or has that been fixed? I don't see it in the change log....

Nick12484 said:
Do the widgets with buttons still hang below Rosie or has that been fixed? I don't see it in the change log....
Click to expand...
Click to collapse
If you don't see it in the changelog....
No not fixed right now, not such a big issue there were more important things
Fix would be easy but dirty, i'm trying to find a better way.

Diamondback2010 said:
If you don't see it in the changelog....
No not fixed right now, not such a big issue there were more important things
Fix would be easy but dirty, i'm trying to find a better way.
Click to expand...
Click to collapse
Oh ok, just asking. in the issues that were listed in the Desire HD thread it had said it was fixed in the next version so I was confused when I didn't see it. Great ROM thanks

Nick12484 said:
Oh ok, just asking. in the issues that were listed in the Desire HD thread it had said it was fixed in the next version so I was confused when I didn't see it. Great ROM thanks
Click to expand...
Click to collapse
Oh yea, sorry my bad Deleted a line to much

Diamond, will all APKs in the virtuous_unity folder automatically installed during flashing the ROM?

destroyer67 said:
Diamond, will all APKs in the virtuous_unity folder automatically installed during flashing the ROM?
Click to expand...
Click to collapse
You can't put custom apps in there atm, this feature is planned for a future version

Ok, I had trouble flashing. Individually wiped each partition (data/cache/system/dalvik), then also wiped via 'factory reset' for extra measure. Then mounted /system and /data, chose .zip file and get the error: "Error in /sdcard/virtuous_unity....zip (Status 1). Installation aborted.
When I **UNmounted** /data and /system, then flashed, it worked.

BillTheCat said:
Ok, I had trouble flashing. Individually wiped each partition (data/cache/system/dalvik), then also wiped via 'factory reset' for extra measure. Then mounted /system and /data, chose .zip file and get the error: "Error in /sdcard/virtuous_unity....zip (Status 1). Installation aborted.
When I **UNmounted** /data and /system, then flashed, it worked.
Click to expand...
Click to collapse
Normally you don't need to mount. That was just a workaround in the first version.
Sent from my Desire HD using Tapatalk

Diamondback2010 said:
Normally you don't need to mount. That was just a workaround in the first version.
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Cool. Suggest you amend the first post to indicate this.
And, for the record... WOW!
Holy $hit!!!!!
Cool.
Fast.
Stable.
What more can one ask?

ROM is excellent... tried it out yesterday. RMK was able to fix the issues I encounted when I first got this ROM.
Only issues, which I hope will be fixed/resolved ..
- The hanging of buttons from the widgets below dialer/phone button.
- Like RCMixKingdom, video playback in portrait mode is distorted.
Most of the widgets I use are affected by the low buttons, so until these are fixed .. I'm gonna stick with RCMix Kingdom.
Don't get me wrong here, ROM is excellent. Like the fact that the OC is built in without having to use an app to control .. fast, smooth etc etc .. definately a ROM I will keep my eye on, very promising
Be interesting to see if someone can port this into 2.3.4 instead of 2.3.3 .. LOL
*** EXCELLENT WORK PEOPLE ***

Hi man, this rom looks great, tell me what its the diference between this rom and rcmix3d?

What's the difference in this and rcmix? Reason I ask is i want sense 3.0,but with rcmix its sluggish for even oc'd to 1.5.
Edit: jamm13 must have posted his question as I was typing mine lol. Just didn't want it to seem like I didn't read the thread
Sent from my HTC Desire HD using XDA Premium App

[ROM][JB]CM10 with Linaro toolchain based on Quarx repo

I've created a fork of Quarx's Defy CM10 repository, to build the latest version from Quarx but using the Linaro 4.7 toolchain. I encourage anyone who might stumble upon this thread to go to linaro.org and read about this non-profit organization and what they are trying to do. Note that TI is a supporting member of this non-profit org, as well as Samsung, LG, ARM, etc. All of these companies have interests in optimizing code performance on ARM architectures.
Now, Quarx has already created a couple of builds using the Linaro 12.10 toolchain. These builds are available as his November 17th and 18th builds, but there was much debate in the original CM10 thread (here) as to whether or not there was (1) any benefit from using the Linaro toolchain and (2) if the Linaro toolchain was adding instability. I think after these discussions Quarx decided to revert back to the original prebuilt Android toolchain.
I've created this build as an experiment, using the latest available (12.11) version of the Linaro toolchain.
Builds are located here:
http://goo.gl/vbAKN
Changelog:
cm-10-20121215-UNOFFICIAL-mb526.zip: First build, based roughly on Quarx 05-Dec or perhaps later; I just forked his most recent repo, then added Linaro 12.11 and made a few small changes to get it to build. (Thank you Quarx)
cm-10-20121218-UNOFFICIAL-mb526.zip: Cherry picked "Volume adjust sound preference 1" and Volume adjust sound preference 2 from ICS. (StevenHarperUK)
cm-10-20121219-UNOFFICIAL-mb526.zip: wpa_supplicant_6 switched to CyanogenMod official jellybean-stable branch. This means maniac's and Quarx's commits and changes involving AdHoc are not in this version. Trying to see if this helps wifi connectivity at my gym where the phone seems to get very confused and drops/connects to wifi many times. Wifi at my home is no issue. This version also reverts a change from Quarx that may or may not have an effect on reading NTFS cards... No idea, for testing.
cm-10-20121222-UNOFFICIAL-mb526.zip: using Linaro 2012.12. Screenshot option in long press power much enabled by default, cherry pick for screen off animation (not sure what benefit this was), more debugging statements in MediaProvider to debug NTFS issue.
cm-10-20121224-UNOFFICIAL-mb526.zip: same as above, but used Linaro optimizing compiler flags from Kayant, removed the screen off animation cherry pick.
cm
cm-10-20130104-UNOFFICIAL-mb526.zip: Switch to JellyX kernel repo from Blechd0se (thanks!), kernel built with standard gcc 4.4.3 while everything else is built with Linaro gcc 4.7. Seems to be stable overnight, I had to wipe cache/dalvik/data to get it to boot. I've rebooted it several times on purpose to check stability and it is, so far, stable.
The forked repo is located here:
https://github.com/skelliam/android
If you want to try to build this yourself, you *will* encounter build errors. One in particular with Linaro is regarding strict-aliasing. There is some discussion of this on the Linaro blog here. There are several other errors that you'll enounter, but fortuantely, Quarx has already created a script that checks out fixes for most of these.
So in general, the process will be something like this:
Move to a directory that will hold the sources. I just created a directory 'cm'.
Code:
$ mkdir cm
$ cd cm
$ repo init -u git://github.com/skelliam/android.git -b jellybean
Now you need to run Quarx's script to make the fixes required for Linaro. From the ROOT of your repository (in my case the cm subdirectory):
Code:
$ ./device/moto/jordan-common/apply_linaro.sh
Now, what the heck, try to build it. You will encounter more compile errors but it is worth it to see what I'm talking about. To build:
Code:
$ source build/envsetup.sh
$ brunch mb526
You should get a bunch of errors related to strict aliasing. To fix these, right now I've applied local changes on my repo, in the remaining makefiles responsible for the errors. Here are the changes I've made locally to get around these issues. I will try to make an update to the apply_linaro.sh script as Quarx did, it was 2 am when I did this and I just wanted to get it built.
Update 5-Jan-2013 I've checked in everything now, so if you use my base manifest file (from github.com/skelliam/android) you should not need to make any changes OTHER than to run the apply_linaro.sh script.

Someone mentioned that the BBC I player app doesn't work.
First of all, are we talking about this app?
{
"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"
}
So I tried this out here. On first install, when I tried to open a program, the phone became almost unresponsive, something was hogging the CPU. I had to pull the battery.
After rebooting, this app seems to work fine:
That's my experience anyway. As far as Netflix, I've just recently cancelled my subscription, so I can't do much with that one.
Sent from my MB526 using Tapatalk 2

Nice ROM seams to be verry smooth. battery life is as far as I can say quite good.
I think I found a bug - Bluetooth is not working I think. Same behavior as on quarx' 2012-11-18 - build.
At least for me. Maybe quarx' bluetooth-fix for this build can solve the problem? Couldn't test yet.

Thread moved as your OP has no format whatsoever and the Development section isn't for discussions. If you want this in Development please make it clearer that this is an actual ROM and not just a discussion and also add all credits with links to the original work. Just look at some of the other ROM threads for an example of what should be included e.g changelog/features, what changes have been made, what you're asking people to test for you to discuss, just anything really to give more info then you have given already.
Thanks
AvRS

AvRS said:
Thread moved as your OP has no format whatsoever and the Development section isn't for discussions. If you want this in Development please make it clearer that this is an actual ROM and not just a discussion and also add all credits with links to the original work. Just look at some of the other ROM threads for an example of what should be included e.g changelog/features, what changes have been made, what you're asking people to test for you to discuss, just anything really to give more info then you have given already.
Thanks
AvRS
Click to expand...
Click to collapse
Really a PM would have been fine.
This thread was created to avoid clutter in another thread.
At the bottom of the post I'm pretty sure it says that it was posted with Tapatalk from my phone? As soon as I'm on my PC I'll add as much rich content as you desire... There is only so much I can do from my phone.
Lastly, each thread IS a discussion, I have no idea what a "forum" is for other than discussing things.
Sent from my MB526 using Tapatalk 2

I'll confirm that Netflix does not work. Stuck on splash screen with loading wheel spinning. Never tried it on quarx 0512, though.
Great build, IMO. No problems on any of my heavy use apps. No reboots or freezes yet. 20 hrs uptime.
Using my standard setup; no ksm, no zRam, no overclocking, 16 bit transparency. Interactive and noop.
Sent from my Red Lens MB525 using xda app-developers app

EldonTyrell said:
I'll confirm that Netflix does not work. Stuck on splash screen with loading wheel spinning. Never tried it on quarx 0512, though.
Great build, IMO. No problems on any of my heavy use apps. No reboots or freezes yet. 20 hrs uptime.
Using my standard setup; no ksm, no zRam, no overclocking, 16 bit transparency. Interactive and noop.
Sent from my Red Lens MB525 using xda app-developers app
Click to expand...
Click to collapse
Awesome, thanks for testing it. I've been having some instability regarding wifi and Tasker, but I experienced this also with the Nov-18 from Quarx. I will keep investigating it.

On last builds by quarx I had problems with touch screen input getting delayed/unresponsive some times. Until now I don't experience that in this build, but I should use it longer to be sure.

Oh I see now it's the same as what I did before the difference was I was trying to compile CNA with it but it broke in so many places I just gave up loool I will try again I guess and see if there is indeed some improverments in CNA because I remember full linaro CM & kernel that I tried before was a bit smoother that just having linaro compiled kernel.
Anyways thanks for clearing that up for me

wskelly said:
Someone mentioned that the BBC I player app doesn't work.
First of all, are we talking about this app?
View attachment 1568120
So I tried this out here. On first install, when I tried to open a program, the phone became almost unresponsive, something was hogging the CPU. I had to pull the battery.
After rebooting, this app seems to work fine:
View attachment 1568122
That's my experience anyway. As far as Netflix, I've just recently cancelled my subscription, so I can't do much with that one.
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
It was I. I was looking at the official BBC iplayer app which is here and requires the BBC Media Player to do the heavy lifting here
It's not as severe a crash as on the 05/12, where I had to yank out the battery, it crashes when it should hand off to the stream, the rest of app works, you can navigate the programme listings etc but just at the point when the stream starts on CM7.20 it hangs. I have access to 3 defys so I can confirm that is the point when the app crashes. I can also confirm the Netflix issue. Are these two related?
As I said in the other thread it is significantly snappier, I'll keep one defy on Quarx, one on this linaro build and one on CM7.20 for feedback (well at least until xmas when they're all being given as presents) :laugh:

The problem I get with all newer builds by Quarx , from 11/18 onwards, is this logcat entry: "E/MediaProvider( 9674): Can't obtain external volume ID even though it's mounted.", which causes process media to be killed all the time, making the user experience a true hell: camera, music player, Play Store, etc, etc, etc, i,e. practically nothing which requires access to my NTFS formatted 64GB card works! So, I'm always back to his 11/17 build (for a month now). I already posted thiis many times on his CM10 dev thread, but, as usual, I get ignored. You, most probably, have already read my posts about this issue there. Anyway, any thoughts if I would face this issue if I flashed your ROM?

Awesome job ...works fine on MB525 green :thumbup:...
Sent from my MB525 using xda app-developers app

casouzaj said:
The problem I get with all newer builds by Quarx , from 11/18 onwards, is this logcat entry: "E/MediaProvider( 9674): Can't obtain external volume ID even though it's mounted.", which causes process media to be killed all the time, making the user experience a true hell: camera, music player, Play Store, etc, etc, etc, i,e. practically nothing which requires access to my NTFS formatted 64GB card works! So, I'm always back to his 11/17 build (for a month now). I already posted thiis many times on his CM10 dev thread, but, as usual, I get ignored. You, most probably, have already read my posts about this issue there. Anyway, any thoughts if I would face this issue if I flashed your ROM?
Click to expand...
Click to collapse
Hi casouzaj... This is interesting that it started happening between 11/17 and 11/18, so it should be easy to find and fix.
Yes you should probably face this issue with this build because I'm using the repo from Quarx, all of the files are the same except for some changes to get it to build with Linaro.

wskelly said:
Hi casouzaj... This is interesting that it started happening between 11/17 and 11/18, so it should be easy to find and fix.
Yes you should probably face this issue with this build because I'm using the repo from Quarx, all of the files are the same except for some changes to get it to build with Linaro.
Click to expand...
Click to collapse
Thanks a lot, wskelly! Would you be meaning that you1ll get this issue fixed anytime soon?

wskelly said:
Hi casouzaj... This is interesting that it started happening between 11/17 and 11/18, so it should be easy to find and fix.
Yes you should probably face this issue with this build because I'm using the repo from Quarx, all of the files are the same except for some changes to get it to build with Linaro.
Click to expand...
Click to collapse
So, your rom will be 'fork with linaro' only, or you have plans to change something?
I ask, because after 18.11 Quarx builds start drain battery (Android OS takes half of usage), wipes, reinstalls, clean rom, nothing can help.

Great ROM!
Using bf5x batt have jumps
Bluetoot fix from quarx work!
Any idea for batt jumps? Installed on top from 18/11 quarx with full wipe>rom > gapps>reboot

After 24h use:
Verry smooth and in my opinion best responding CM10 I used until now. Usally I stick with quarx' build.
Battery drain about 2% per hour at light/normal use (just a little surfing, reading news, checking mails, etc)
Bugs so far:
Bluetooth disabling crashes phone app.
Bluetooth fix of quarx helps to at least solve the crash. Got bluetooth mouse correctly working. File transfer to a compueter doesn't work.
Reboot into bootmenu/recovery fails - just a reboot happens

wskelly said:
The completed build is located here:
http://goo.gl/vbAKN
Click to expand...
Click to collapse
Is there any mirror? I can not download from this link - download resetting every time when reaching ~25%.

casouzaj said:
The problem I get with all newer builds by Quarx , from 11/18 onwards, is this logcat entry: "E/MediaProvider( 9674): Can't obtain external volume ID even though it's mounted.", which causes process media to be killed all the time, making the user experience a true hell: camera, music player, Play Store, etc, etc, etc, i,e. practically nothing which requires access to my NTFS formatted 64GB card works! So, I'm always back to his 11/17 build (for a month now). I already posted thiis many times on his CM10 dev thread, but, as usual, I get ignored. You, most probably, have already read my posts about this issue there. Anyway, any thoughts if I would face this issue if I flashed your ROM?
Click to expand...
Click to collapse
Could this be the reason, that i am not able to listen properly to music anymore?
Every 5-10 minutes my mobile forgets almost every song on my sd-card, there are some left, but most have gone.

trurl3 said:
Is there any mirror? I can not download from this link - download resetting every time when reaching ~25%.
Click to expand...
Click to collapse
http://www.multiupload.nl/M1QNFOA0JS

[ROM][7.1.2][i9305]Unofficial LineageOS 14.1 with modifications

Hi,
I am back with one of my builds. Again this is just result of my hobby, feel free to use it, but do it on your own risk. Also any updates will be probably sporadic.
I wanted to publish my build as quickly as possible, becasuse I promised in another thread. So I simply took, what I have (and I am using right now). As a result there some detail I`d like to change for public release like this for the future (e.g. all the special feature enabled by default, the big dmesg buffer). Be careful. I`ll try to do better version as soon as possible. I don`t recomend this for begginers. Be sure you have backup.
This build is based on the official LineageOS code and contains several of my changes. In some cases it could be considered as fix, improvement, but sometimes a hack or even even security risk, so please read carefully following list. All the changes I did because I wanted the system on my device behave that way (at least time to time). Take it or leave it. Please note, that all the features are enabled by default. Be careful.
- built-in root support
- RIL is based on stock KitKat version (works better for me than the official version)
- the sensors libraries are also from stock KitKat (same reason as above )
- barometer sensor is correctly recognized by the system
- the menu button does, what it always did
- notification led brightness can be configured by user
- entering safe mode by holding specific keys during boot can be disabled by setprop persist.safe_mode_disabled true (this has always only annoyed me, but be sure you know you are doing)
- device wakeup by power button can be disabled when proximity and light sensors are blocked (e.g. in a pocket). Execute setprop persist.pwrbtn_proximity_block true
- external sdcard can be made world writeable by setprop persist.world_writable_sdcard true (be careful with this one, this opens a security risk)
- the notification led can blink when the battery is fully charged - enable by setprop persist.blink_when_charged true
- F2FS support
- the notification icons are also on the lock-screen as they ware in
previous Android versions. The carrier name is moved above the clock
(this cannot be turned off)
- the dmesg buffer size is increased to 16M. I set this for debugging
and remove it in next published build.
- ramdisk LZMA compression support
- sdcardfs support - This is faster replacemnt for the FUSE filesystem. I backported this for higher kernel version. Although I`ve been using this for several months without any problem, please consider this experimental. Enable with setprop persist.sys.sdcardfs
force_on
- mount directories for sdcard are protected against writing while the sdcard is not mounted (this solves a race condition problem which allows some apps to create files in there)
- there some other small changes related to my multiboot envrionment, czech translation, carrier name, etc.
Source code
In the installation zip there is a directory code_info with following content:
roomservice.xml - roomservice.xml for the build
commits - list of git repositories and commits used for the build
patches - directory tree with structure reflecting the source and containing
patches for individual projects. The idea (not always followed) is that one patch is one feature,if possible.
code1.diff - all the patches from patches directory together
code2.diff - changes which are not in patches directory
diff-commits.txt - obsolete, I`ll remove this one in the future or maybe use
it again
The only bug I know about is occasional crash of MTP, but I didn`t notice any negative consequences. There may some problem with battery charging (the display turns on time to time without no obvious reason during charging), but it may be some hardware error (bad cable or charger).
Since this is based on official LineageOS, thanks to everyone who contributed to it.
I am using this build for over a week without any problem, except those mentioned above.
Continue here, for the latest build.
UPDATE:
I totally forget about this yesterday - here are the proprietary files I used for this build proprietary-files-ocm13-skk-ril.tgz It is a mixture from the CM 13 official build and KitKat stock files, with modified ks file (then connect symbol is replaced with xonnect, so it doesn`t crash), maybe some other files and changes. I really don`t remember, I put this together during a long period of time. If you find any of your work inside, please accept my apologies and let me know. From my point of view it just works. If you want to apply the patches, then you will most probably want to change the hardcoded full path to these files in device/samsung/i9305/extract-files.sh.
UPDATE:
If you want to use anything from my patches, feel free to do so, just follow the license of the original project.

I tested it for about 4 hours for modem stability, taking the logs. All SAHARA transfers were ok, with no errors and retries. I should have mentioned your name in some post earlier

gongrats and many thanks @p.a.n. Your rom runs very well, its awesome. :good:
Do you mind, if I take your sources or parts of it or some files from your rom.zip for my builds? If I do so, I will mention you and what I took and give you credits.

rodman01 said:
gongrats and many thanks @p.a.n. Your rom runs very well, its awesome. :good:
Do you mind, if I take your sources or parts of it or some files from your rom.zip for my builds? If I do so, I will mention you and what I took and give you credits.
Click to expand...
Click to collapse
Thanks Use whatever you want from it just follow the license of the original project (I updated OP with similar note).

Help??? How to fix gps on this Rom plzz

Great work p.a.n.
Using for 24 hours no problems yet and seems very smooth.
Used it for a few hours with the built-in kernel then switched to Boeffla to get Boeffla Sound etc.
Very nice to have the customisable LED again as it was missing from the official LineageOS.
More importantly for me, the magnetic compass seems to work properly. I couldn't get it to work on official, nor on Rodman's RR.
No issues with GPS for me.
I had to install 'The SELinux Toggler' to set permissive so I could get Viper4Android to work (as with official) but I expected that.

One other thing, the MTP crash is the 'MTP host' app. I just disable this as it's only needed if you need your phone to be an MTP host for something like a digital camera, which I don't. It doesn't affect connections to your PC.

Is there an issue with the automatic execution of init.d scripts? I'm on Boeffla so it may just be that. Luckily you can tell Boeffla app to execute them anyway.

@Glenn2, thanks for testing I am not completely sure about it, but if I remember well, the compass problem is caused by the opensource sensor library (I think that just replacing the/system/lib/hw/sensors.smdk4x12.so with the one from my build should fix that). But the problem is not actually with the compass sensor, that one is ok, but in the opensource version there are missing some "fake" sensors, which provide calculated data based other "real" sensors. One of them provides orientation information, often used in apps as compass. Try some app (e.g. Androsens2) which lists all the sensors and you`ll see the difference - the "fake" ones have iNemo in their name.
I actually don`t care about the MTP crashes. It mostly happens after uninstalling some app, which doesn`t happen too often and otherwise I haven`t noticed any negative related to that. It is just annoying popup for me.
What do you mean by the question about init.d scripts?

p.a.n said:
What do you mean by the question about init.d scripts?
Click to expand...
Click to collapse
I have a couple of scripts and they were not running on boot. I don't know if Boeffla kernel affects busybox. I remedied this by telling the Boeffla Config app to run init.d scripts when it launches.
Also, I had a power manager service wakelock that kept my phone awake for hours, only a reboot cleared it. I had this happen a couple of times on official LineageOS too. Not the famous mdm_hsic_pm0 which now seems to be cured at long last! I had a period of no signal when I was on the London Underground, maybe that was the cause.

Glenn2 said:
I have a couple of scripts and they were not running on boot. I don't know if Boeffla kernel affects busybox. I remedied this by telling the Boeffla Config app to run init.d scripts when it launches.
Click to expand...
Click to collapse
There is /system/etc/init.d/* scripts, which run OK, or at least /system/etc/init.d/00banner does. There is also /system/etc/init.d/90userinit, which executes /data/local/userinit.sh. I remember that seme previous CM version there was also a user defined init.d somewhere in /data. This may what has changed, but I am not if this is your case.
Glenn2 said:
Also, I had a power manager service wakelock that kept my phone awake for hours, only a reboot cleared it.
Click to expand...
Click to collapse
This on is also often on the top of my kernel wakelock list, but never that bad, always with reasonable times.
Glenn2 said:
Not the famous mdm_hsic_pm0 which now seems to be cured at long last!
Click to expand...
Click to collapse
Yes, the solution has been sitting in the Samsung kernel source for a long time ...

Glenn2 said:
Great work p.a.n.
Using for 24 hours no problems yet and seems very smooth.
Used it for a few hours with the built-in kernel then switched to Boeffla to get Boeffla Sound etc.
Very nice to have the customisable LED again as it was missing from the official LineageOS.
More importantly for me, the magnetic compass seems to work properly. I couldn't get it to work on official, nor on Rodman's RR.
No issues with GPS for me.
I had to install 'The SELinux Toggler' to set permissive so I could get Viper4Android to work (as with official) but I expected that.
Click to expand...
Click to collapse
Do you install the last rom ??? Or not

It is worth pointing out that after backing and restoring between roms, the SELinux attributes for efs files can become not correct. That can lead to something like this :
Code:
06-28 04:17:43.705 3799 3799 W ks : type=1400 audit(0.0:30): avc: denied { read } for name="efs1.bin" dev=mmcblk0p11 ino=8200 scontext=u:r:qcks:s0 tcontext=u:object_r:unlabeled:s0 tclass=file permissive=0
Code:
06-28 04:17:43.712 3799 3799 E kickstart: Requested ID 16, file "/tombstones/qcks/efs1.bin"
06-28 04:17:43.712 3799 3799 E kickstart: ERROR: function: open_file:80 Unable to open input file /tombstones/qcks/efs1.bin. Error 13: Permission denied
It results in not working RIL because of enforced SELinux. Running restorecon fixes the problem.

moad gastro said:
Do you install the last rom ??? Or not
Click to expand...
Click to collapse
I don't know what your question means, as there is only one ROM. I installed from the link in the OP (dated the same date as the OP).

Still using this ROM, and still very few problems.
The day before yesterday it crashed with the screen off. Had to hold power button in to restart.
And yesterday the damn wakelock. It got stuck at a time when I had no signal, and also I used the camera, so either may be relevant. It didn't seem to cause any drastic battery drain though (see images attached). I suppose when the CPU is awake but only at 200MHz and not doing much it uses little more than when it is sleeping?

Regarding init.d scripts. I added one to /system/etc/init.d that simply writes a file to /data when it runs, to test that it DID run. Script starts #!/system/bin/sh
Results:
1) rom with its own kernel - didn't run
2) rom with Boeffla kernel - didn't run
3) rom with Boeffla kernel and Boeffla Config app set to execute init.d scripts itself - did run

One more, just for fun!
Two days ago I was at the Wimbledon tennis, and the location service and/or weather widget decided I was in Boulogne-Billancourt (Paris) instead! I then opened and closed Maps, refreshed the widget and it changed to the correct location!

..

Hi,
I'm trying to install the current build using TWRP 3.0.2-1, but it gets stuck at the "Patching system image unconditionally..." step with the progressbar at around 40%. It's been sitting there for about 10 minutes. Does anyone know how that'd be fixable?`
Cheers

Latest build is ok for me. I've flashed it using TWRP 3.1.0 build from rgib
https://drive.google.com/drive/folders/0B7pwslEEF0l4Yzk2Nm1jOGRDQVU

[ROM][64BIT][8.1] UNOFFICIAL LineageOS 15.1 for LG STYLO 2 PLUS

{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 8, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
What's working :
RIL (Calls, SMS, Data)
Wi-Fi
Bluetooth
Video Playback
Audio
Sensors
GPS
FingerPrint
tap 2 wake
Known issues:
Volte
you tell me!
Follow Instructions Carefully otherwise you will get error :
Use this 64 bit twrp to flash http://www.mediafire.com/file/i1911qqxlx9v6sm/twrp-3.2-x64-ph2n.zip
Wipe cache, dalvic cache,system,data
Flash ROM-Flash Gapps [Arm64-8.1]
Done-Reboot Now
Enjoy the clean rom
Downloads :
https://www.mediafire.com/download/t9b8g097ihhu7b4
Credits:
Lineage Team
Please Consider donating if you appreciate my work
https://paypal.me/messi2050
Sources:
Device:
https://github.com/messi2050/android_device_lge_ph2n
https://github.com/messi2050/android_device_lge_msm8937-common
Kernel:
https://github.com/messi2050/android_kernel_lge_msm8937
XDA:DevDB Information
[ROM][64BIT][8.1] UNOFFICIAL LineageOS 15.1 for LG STYLO 2 PLUS, ROM for the LG Stylo 2 Plus
Contributors
messi2050
Source Code: https://github.com/LineageOS
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: Nougat bootloader
Version Information
Status: Abandoned
Created 2018-05-03
Last Updated 2019-05-09

Reserved
2018-june-13 build changelog:
-June security patch
-Update power scripts from last caf
-Fix vendor mismatch error message
-enable dual wifi bands
-build using last sources

Thanks for the ROM, messi, it's greatly appreciated even if development stops cold after the post you just made.
And for those that might care, the MD5 of the archive is: 00dd56ee08963da05195915dd528d9b1

The headphone audio output on this ROM is rather weak, but that's not messi's fault, it's because of how Oreo is working on this device. There appears to be no mixer_paths.xml file in Oreo now, and I added the older mixer_paths.xml (with permissions 0644 as required) with the necessary adjustments to boost the audio output from the default of 84 to 92. It had zero effect so it seems the audio subsystem in Oreo is now working differently for whatever reason, not sure if there's a way to adjust the defaults at all.
Also, the kernel for this ROM appears to be defaults to just 6 core operation: I've installed the ROM twice now on my S2P and when I check the core activity with CPU-Z it always shows 2 little cores active, 2 offline (always), and all 4 big cores active. And of course the minimum CPU speeds are 960 for the little cores and 768 for the big cores - they should be (or at least I should say they could be set in the kernel parameters down to the minimum of 384 MHz and that would save a bit of battery life.
Overall it's been great so far, really, everything seems to work fine. The flashlight didn't work so I installed a flashlight app then suddenly the toggle started working so, there's something funky going on there but everything else so far has been great. Would be nice if there was a more customized kernel available, yes, with more governors and perhaps even some undervolting potential but I know this device just doesn't have much developer love at all.
Regardless, it's very cool to be able to run Oreo 8.1 now since I have never really given a damn about it at all previously. I may go back to running the stock T-Mobile 20a rooted ROM on my S2P however, it depends on how things work out.
:good:

br0adband said:
The headphone audio output on this ROM is rather weak, but that's not messi's fault, it's because of how Oreo is working on this device. There appears to be no mixer_paths.xml file in Oreo now, and I added the older mixer_paths.xml (with permissions 0644 as required) with the necessary adjustments to boost the audio output from the default of 84 to 92. It had zero effect so it seems the audio subsystem in Oreo is now working differently for whatever reason, not sure if there's a way to adjust the defaults at all.
Also, the kernel for this ROM appears to be defaults to just 6 core operation: I've installed the ROM twice now on my S2P and when I check the core activity with CPU-Z it always shows 2 little cores active, 2 offline (always), and all 4 big cores active. And of course the minimum CPU speeds are 960 for the little cores and 768 for the big cores - they should be (or at least I should say they could be set in the kernel parameters down to the minimum of 384 MHz and that would save a bit of battery life.
Overall it's been great so far, really, everything seems to work fine. The flashlight didn't work so I installed a flashlight app then suddenly the toggle started working so, there's something funky going on there but everything else so far has been great. Would be nice if there was a more customized kernel available, yes, with more governors and perhaps even some undervolting potential but I know this device just doesn't have much developer love at all.
Regardless, it's very cool to be able to run Oreo 8.1 now since I have never really given a damn about it at all previously. I may go back to running the stock T-Mobile 20a rooted ROM on my S2P however, it depends on how things work out.
:good:
Click to expand...
Click to collapse
Mixer is moved to vendor/etc in o

messi2050 said:
Mixer is moved to vendor/etc in o
Click to expand...
Click to collapse
Geezus, I spent an hour looking for that information on multiple forums and websites and you're the first person to point out where it is, damn.
Thank you, thank you, thank you. Adjusted the default path name="headphones" from 75 to 90 and w00t, much much better now.

messi2050 said:
Mixer is moved to vendor/etc in o
Click to expand...
Click to collapse
I want to ask a question. This Custom ROM support the LG Stylus 2 Plus K520TR model?

There are two issues I've noticed, can't say they will, would, or do affect other people and I'm using the MetroPCS model with T-Mobile (I was using the T-Mobile stock ROM originally).
- the Mobile Hotspot does not function. It says it's working in the Settings submenu but the actual hotspot never does function, it never shows up as a visible AP for another device to connect to, the SSID is not broadcast, etc
- the USB options when you plug in a USB cable will not stick, I've got into the Developer Options and I have it set to always MTP and every single time I plug in I have to go manually change it from charging to MTP to get it working
They're not massively important things but for me the Mobile Hotspot could be useful for my Wife when we're out and about; her Flex 2 doesn't have cellular service so in the past she'd just tether to my Stylo but now that's not possible.
Not sure this can even be resolved given the nature of the usage but it would be nice to have those two nitpicks working properly. Aside from that this ROM so far has been spectacular: I'm getting 7+ hours of SOT at 50% brightness, with cellular and Wi-Fi enabled constantly, and using L Speed to handle background performance.
So far so good.

I am getting a vendor ID error every time I restart the phone. T-Mobile version stylo. Clean install followed to a T. I also noticed some games aren't working either like they cannot community ate with the server mainly Paladins strike that game also starts with an error.
I'll try to screenshot the error and write it down as well as the vendor id it says I need to match

Did a full reflash and the vendor id error persists. Also not sure if its because of that but most of the apps and games I try to play are giving me network errors and not downloading the content. I can download from the app store no problem but its within the app that problems with network start. My APN is correct as well.
Wondering if I missed a nougate update that is causing the vendor id error.

rsuthers08 said:
Did a full reflash and the vendor id error persists. Also not sure if its because of that but most of the apps and games I try to play are giving me network errors and not downloading the content. I can download from the app store no problem but its within the app that problems with network start. My APN is correct as well.
Wondering if I missed a nougate update that is causing the vendor id error.
Click to expand...
Click to collapse
I believe the vendor id is used to pass safetynet easier. Expected behavior

Anything going on with this rom?

rsuthers08 said:
Anything going on with this rom?
Click to expand...
Click to collapse
@messi2050 said he was done with this phone and I haven't heard anything from him since, so no. @deadman96385 @Travisholt92 @xRaZeR_FuZioNx and @cospalet are all working on roms still. If you wanna talk to them and see what their plans are, we have a telegram group, but you'll have to find it yourself

Ya I'm not looking to pay for nightlies of an unfinished rom

The ROM works, the only thing that doesn't for me is the hotspot but that's a given anyway and nothing can really be done with it.
Only thing I wish we had at this point is a custom kernel to get the idle speeds down from the current ones of 960/768, they should be 384/384 and it would help with battery life (which is fine even in spite of this current limitation). Maybe some more governors would be nice too but so far I've been running this ROM since it was put out and haven't had a single thing to legitimately complain about unlike others it seems.
Use it, don't use it, but for Pete's Sake® STFU about it and messi, will ya?

I just got my computer up with 14.04.5 TT and set up my build envir. I just need the time. I cant leave my computer set up at home right now and thats where i have the best connection. Its my first time so i intend to do a couple dry runs first, maybe play around with the kernel. But i never have to time to get rling with it

Google lens
I can't believe it but Google Lens actually works on this ROM. I haven't done a lot of testing but so far so good.
---------- Post added at 06:08 AM ---------- Previous post was at 05:42 AM ----------
I can't believe it but Google Lens actually works on this ROM. I haven't done a lot of testing but so far so good.
Edit, I haven't found anything not working.

rsuthers08 said:
I am getting a vendor ID error every time I restart the phone. T-Mobile version stylo. Clean install followed to a T. I also noticed some games aren't working either like they cannot community ate with the server mainly Paladins strike that game also starts with an error.
I'll try to screenshot the error and write it down as well as the vendor id it says I need to match
Click to expand...
Click to collapse
Did you ever find a fix for the mismatching vendor.img? I feel dumb bit its been years since i've fiddled with android internals. They've change quite a bit since lollipop lol

lixer8 said:
Edit, I haven't found anything not working.
Click to expand...
Click to collapse
So, for you, if you have cellular service, can you test out the hotspot functionality and let me know if you're successful with getting it to work? It's the only thing that doesn't work for me, so I switched back to the 7.1.1 ROM where it works just fine. I'd love to continue using the 8.1 ROM but without that hotspot it's a problem.