Database Develop

[UPDATED][MOD] LOTS of Build.prop edits!

UPDATED 9/4​
Ok, so I went through the build.prop tonight and tried a few things out. I figured I'd just post all of my edits for you guys to try and use also. Here goes...
I am listing the changes one by one w/ descriptions, as well as providing all the mods rolled up into a single build.prop which will be posted at the end of these directions. Enjoy
To make the phone ring faster when dialing out, I changed
ro.telephony.call_ring.delay=3000
to
ro.telephony.call_ring.delay=1000
Now the phone rings pretty much instantly when dialing out.
To enable better scrolling speed through lists, I changed
windowsmgr.max_events_per_sec=55
to
windowsmgr.max_events_per_sec=60
Scrolling through the app drawer and contacts and any lists really is now smoother
Now, to save battery by decreasing the amount of time Wifi looks for an access point, I changed
wifi.supplicant_scan_interval = 60
to
wifi.supplicant_scan_interval = 90
Now wifi will scan once every 1.5 minutes when not around a known location instead of once every minute which will save battery.
I also changed the Dalvik VM heap size from
dalvik.vm.heapsize=30m
to
dalvik.vm.heapsize=32m
I remember doing this on my Eris and I was able to run JIT w/ sense enabled (which was a major hassle at the time) So I'm only assuming it will help performance on the X also.
To change LCD Density (How much is displayed on screen) visit my other build.prop mod page
Here -- Droid Life Forum • View topic - [MOD] LCD Density - DIY! - Droid X
And To fix your 2.2 market to display all apps Go
Here -- Droid Life Forum • View topic - [FIX] - 2.2 Market Issues - Show All Apps
Now for everything listed here all rolled up into one single build.prop, download this
http://www.mediafire.com/?25xh9gjwx5meds9
Install using any method of your choice
Method 1 - ADB
1. Download
2. Put the build.prop in your android-sdk\tools folder
3. Connect your phone via usb, make sure it shows up with adb devices
4. adb remount (or whichever way u prefer to mount ur system)
5. adb push build.prop /system/build.prop
6. adb reboot
Method 2 - Root Explorer
1. Copy the build.prop to the root of your SD card
2. Long press on build.prop
3. Select "Copy"
4. Navigate to /system
5. Click R/W in the top right corner
6. Paste, and overwrite
7. Reboot
My results - 1484
{
"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"
}
EDIT: If you do not like or want to use the LCD Density mod, use this build.prop. Everything else is included.
http://www.mediafire.com/?w4860c0fddw4ao2
-----------------------------------------------------------------------------------
UPDATED BUILD.PROP
Ok here are a few updates.
To enable the hard key lights to stay on while the screen is on and not timeout, I changed
ro.mot.buttonlight.timeout=1
to
ro.mot.buttonlight.timeout=0
To make the phone come off of the "black screen" in the middle of, or the end of phone calls when you pull the phone away from your face, I changed
mot.proximity.delay=450
to
mot.proximity.delay=150
The delay is almost no longer NOTICEABLE at all. (It was very annoying to me personally)
*Note - this will not include the lcd density mod, but everything else mentioned on this post included. Thanks guys! Enjoy
UPDATED Build.Prop

WOOT! These made it into an option on Birdmans FlyX in Rom Manager.
Birdmans twitter Update - Added Beesleys buid.prop edits

Anyone have a stock build.prop? Everything worked fine, I just want a file to fall back on.

not what you're going to want to hear... but my score dropped. my build.prop before only had the market fix and when i ran the test (immediately after reboot) i got 1390. i pasted your build.prop in and rebooted and ran test again (immediately after reboot) and the score dropped to 1304.
not a huge drop but no where near your score and certainly not a gain.
any ideas as to why?

byproxy said:
not what you're going to want to hear... but my score dropped. my build.prop before only had the market fix and when i ran the test (immediately after reboot) i got 1390. i pasted your build.prop in and rebooted and ran test again (immediately after reboot) and the score dropped to 1304.
not a huge drop but no where near your score and certainly not a gain.
any ideas as to why?
Click to expand...
Click to collapse
Did you run it multiple times? I am able to get a wide range of scores that are over 100 points in difference each run sometimes....

@OP
Good post..nice one.
I was wondering if u messed with some other buil.prop.
Couple other thoughts I had to edit :
#Proximity sensor debounce time
mot.proximity.delay=450
# disable touch below 60 pixels
mot.proximity.distance=60
Seems plausible to edit the delay for quicker response .
This defines the max event window manager can
# handle in 1 s. We may adjust this # for performance
# reason later
windowsmgr.max_events_per_sec=55
# This defines the min duration between two pointer event
ro.min_pointer_dur=10
Messed with this at all?

cbaty08 said:
Did you run it multiple times? I am able to get a wide range of scores that are over 100 points in difference each run sometimes....
Click to expand...
Click to collapse
ahhh... nope. just once. ran a couple more times and got the following:
1304 (first one mentioned before)
1482
1486
1481
so ya... that's good. lol. should have run it multiple times with the old build prop to see the difference. suppose i still could, but too lazy to load the old file. hehehehe. thanks for the tip!

byproxy said:
ahhh... nope. just once. ran a couple more times and got the following:
1304 (first one mentioned before)
1482
1486
1481
so ya... that's good. lol. should have run it multiple times with the old build prop to see the difference. suppose i still could, but too lazy to load the old file. hehehehe. thanks for the tip!
Click to expand...
Click to collapse
No sweat man, enjoy.

acidbath5546 said:
Good post..nice one.
I was wondering if u messed with some other buil.prop.
Couple other thoughts I had to edit :
#Proximity sensor debounce time
mot.proximity.delay=450
# disable touch below 60 pixels
mot.proximity.distance=60
Seems plausible to edit the delay for quicker response ...?
ro.telephony.call_ring.delay=3000
Seems like we can lower.
This defines the max event window manager can
# handle in 1 s. We may adjust this # for performance
# reason later
windowsmgr.max_events_per_sec=55
# This defines the min duration between two pointer event
ro.min_pointer_dur=10
Messed with this at all?
Click to expand...
Click to collapse
I like the idea of making the sensor quicker to respond.... It isn't as bad as it was on 2.1, but I still think it could be quicker

I agree...but im not sure if it will have any adverse effects if changed.
It seems to me that as of right now ..with stock rooted 2.2 it takes about 1-2 seconds for the phone to switch between landscape and.potrait ...like counting out loud One ...Two...it switches as soon as I.say two....same for you?
EDIT :
I edited #Proximity sensor debounce time mot.proximity.delay=450
Took it down to 100....and well I really can't tell if its quicker or not ...it seems it but might be a placebo effect ...hasn't given me any issues ...someone else wanna test that and tell me what they think?

cbaty08 said:
Did you run it multiple times? I am able to get a wide range of scores that are over 100 points in difference each run sometimes....
Click to expand...
Click to collapse
This is why I dislike quadrant, it's really not a good benchmark tool. Too many factors can influence the score, take the lagfix for some phones, they just replace the file system with the faster ex2, offers little real world difference but because the I/O section of quadrant jumps through the roof then the total score goes much higher than other phones that are actually faster. The paid quadrant is a little better in that it shows how much of the score is from what subsytem or whatever, but the score is too easily influenced by too many factors to be really effective as a benchmark tool. Not to mention it's easy to trick.

What App
I placed in the Build.prop edits and what an improvement in speed. What app are you using as illustrated in your post?
Thanks

chazall1 said:
I placed in the Build.prop edits and what an improvement in speed. What app are you using as illustrated in your post?
Thanks
Click to expand...
Click to collapse
It would be nice if you addressed who you are talking to If you're talking about the OP, its Quadrant advanced.

Craziness, I uninstalled adw and the adw theme because I was getting random freezing after this build.prop and now my phone is blazing fast! I don't think the official 2.2 could even touch this! Im just saying, nice work
Sent from my DROIDX

lilmoney30 said:
Craziness, I uninstalled adw and the adw theme because I was getting random freezing after this build.prop and now my phone is blazing fast! I don't think the official 2.2 could even touch this! Im just saying, nice work
I've been running my phone now for few hours now since this post and im now getting quadrant scores in the upper 1400's and it is zippy.
Sent from my Droid X
Click to expand...
Click to collapse

lilmoney30 said:
Craziness, I uninstalled adw and the adw theme because I was getting random freezing after this build.prop and now my phone is blazing fast! I don't think the official 2.2 could even touch this! Im just saying, nice work
Sent from my DROIDX
Click to expand...
Click to collapse
Thanks, I really appreciate it.

my score droped from 1400 avrg to 900... help

soleicey said:
my score droped from 1400 avrg to 900... help
Click to expand...
Click to collapse
lol. Bummer.
try the updated build.prop.

LexusBrian400 said:
lol. Bummer.
try the updated build.prop.
Click to expand...
Click to collapse
why didn't you include the lcd mod in the new version?

because many people dont like the LCD mod

Voltage Control - control OC/UV for OC kernels.

I take no responsibility for ANY damage / data loss may occur. Use this at your own risk. Beta quality software!/Alpha quality features!
The news:
Completely rewritten whole app! Epic 4G FCs gone thanks to theimpaler747
Voltage Control Extreme unlock Key on Android Market!
For now features exclusive to Extreme version are:
+ overvolting capability (max +50mV, 1500mV absolute maximum)
+ increased uv range (max -250mV)
Click to expand...
Click to collapse
Sources available, project on google code:
http://code.google.com/p/voltage-control/
Look for kernels with this label:
Kernel developers who added VC support please show this image in your topic
{
"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"
}
Uploaded with ImageShack.us
Features:
- minimum/maximum CPU frequency choosing
- selecting IO scheduler
- selecting CPU governor
- changing voltage per frequency
- chosing which frequencies should be used and which shouldnt
- saving settings to be automatically applied at boot (init.d script)
- saving/loading a OC profile
- well designed and highly optimised UI (I hope..)
- robust kernel detection, support of not-so-well-working kernels
About donations:
This software is available free of charge.
It cooperates with OC kernel by raspdeep.
It uses some code from: MarketEnabler (Fool your market to make all apps visible!)
If you find this software useful, please consider funding a beer and pizza. There is a "Donate to me" link just over my avatar.
Donator list:
nitr8
kalpik
laststufo
glitterballs
screwyluie
Gembol
Coreym
Thanks!
How to?
Generally idea is simple: make changes to one tab and hit apply. If any changes have been made apply/discard buttons appear on bottom.
The first tab, "General" allows to change Scheduler,Governor/min and max frequencies.
Make changes and click apply
So, you want to pick a maximum/minimum frequency?
Just chose from slider and hit apply.
Governor/scheduler can be choosen by picking from the list, then hitting apply.
You can always discard changes before applying if you want start from loaded settings.
The "Advanced" tab has sliders to control undervolting settings and green/red icons, representing enabled/disabled state.
(green = enabled, red = disabled)
Pick your settings and hit apply, or discard and start over.
Profile support:
If you want to save as boot or as profile, you need to make adjustments and on "General" or "Advanced" tab and then apply them where applicable.
To save as boot -> press menu key, then select "Save as boot settings".
To save as profile -> press menu key, then select "Save profile".
Boot settings are automatically loaded on every device boot.
Profile settings can be loaded by pressing menu -> "Load profile"
Both "boot" and "profile" settings can be deleted from menu.
RECOVERY
If Your device freezes after boot because of too agressive boot settings:
Flash Voltage Scheduler Remover by user Coreym, via CWM. Don't forget to press thanks under one of his posts!
FAQ:
Q: Extreme version?
Yes, I wanted to give some extras for people that support my work.
For now features exclusive to Extreme version are:
+ overvolting capability (max +50mV, 1500mV absolute maximum)
+ increased uv range (max -250mV)
Q: What is it?
Its voltage control app for undervolt and overclocking kernels providing sysfs interface, designed and implemented by raspdeep (thank You!) It is being tested on his kernel releases and I can guarantee (kind of) its functionality on those kernels.
The idea of the app is to keep all simple as possible, not adding any startup services and reusing existing solutions (such as init.d support).
Q: What does it mean to undevolt, and what is overclocking?
Read more in "OC / UV 101" section That is a detailed(sort of) explanation what UV/OC means.
Check this great overclocking/undervolting guide by shaolin95 (thanks!) and discussion topic!
Prerequisites:
-root (superuser + su)
-busybox
-OC kernel supporting either UVLF and UVHF (Version 1.61) or UV_mV_table (1.97 and up)
-init.d scripts support for apply on boot

xan said:
Hi I've seen some reports on market that new version is broken on Epic4g. Anybody knows whats goin on?
Logcat output welcome.
Click to expand...
Click to collapse
First!!!
I tried it with the Bonsai Rom a couple of days ago and it worked for me. I purchased the extreme and I undervolted straight across the board 250mv and I have no problems so far. I think it all depended if the kernel on the phone is compatible or not.

xan said:
Hi I've seen some reports on market that new version is broken on Epic4g. Anybody knows whats goin on?
Logcat output welcome.
Click to expand...
Click to collapse
It made me smile when I saw that you posted. Taking a personal interest and such.
I think you might be getting reports from Syndicate people. Syndicate's Twilight kernel didn't implement sysfs very well. Voltage Control will recognize it but changes can't be made and some clocks aren't read correctly. PimpMyCPU won't read it all.
Genocide kernel, Vision kernel, and Bonsai's kernels all work flawlessly.

Thanks
This rewrite costed me *a lot* of work seeing 1 star ratings on market makes me sad ;p

I'm using twilight kernel without any problems but I'm no longer on SFR anymore.
Sent from my SPH-D700 using Tapatalk

xan said:
Thanks
This rewrite costed me *a lot* of work seeing 1 star ratings on market makes me sad ;p
Click to expand...
Click to collapse
Yeah, that's not right. My Epic doesn't play nice with Voltage Control but I know better than to rate the app bad. These Epics each have a mind of their own. Some like undervolting, some dont. Some like certain ROMs better. I can run 1400 all day but no undervolting for me
Sent from my SPH-D700 using XDA Premium App

FCS on some kernels fixed ;p
Thanks going to theimpaler747, for detailed bug report and testing

I have found multiple issues with the Twilight kernel, I love the rom, just Genocide has been a lot more stable AND I never had any issues with Voltage Control. I was wondering if you might incorporate multiple profiles like SetCPU? I had to start looking for a different program when it would constantly lock my phone when trying to use them and then I found Voltage Control, and after the rewrite it just makes it that much easier to use.

This might be good, true.
Multiple profiles seem doable...

xan said:
FCS on some kernels fixed ;p
Thanks going to theimpaler747, for detailed bug report and testing
Click to expand...
Click to collapse
Happy to have helped out for a great app!

hey all, im running SFR 1.1.1 with its stock twilight kernel.
i use to run genocide, but i think i messed up with the UV features and i started getting a lot of lockups. right now i just run setcpu with 1300/400 and i seem to be ok.
i think i bought the WRONG voltage control app also. i bought voltage control extreme by sulph8.
i would love to get back to 1400/400, but im really unsure what the best course of action is. are there default voltage settings in this app? initially, i'd like to run 1400/400 with all the standard voltage settings to see if my phone acts normally again.

Well, Voltage Control by nitr8 is a unlock key for 'mine' voltage control. For now all money goes to him, he promised to send it to me.
To revert to stock settings -> Chose delete boot settings and reboot.
Viola, you have booted on stock settings!
Then set desired frequency limits and you are done

so i should set my setcpu back to 1000, remove setcpu, flash genocide kernel, install your voltage control and start from there?

Sounds ok

what should i set my governers to?

Well, depends on your experience with kernel, generally:
For battery saving try conservative.
For reasonable performance try interactive/ondemand or smartass.
Some kernels have bad implementation of some governors, which can make them unstable, so you need to test, test, test and observe
From my experience smartass (where implemented) is very smooth.
Stock Samsung Gingerbread kernels came with ondemand (not entirely sure)
Stock Froyo/Eclair was conservative.

useport80 said:
so i should set my setcpu back to 1000, remove setcpu, flash genocide kernel, install your voltage control and start from there?
Click to expand...
Click to collapse
Well, I just flashed it again on Genocide. I am running 1400/200 on demand. I am going to check CPU Spy to see if it performs similar to SetCPU. Curious if on demand still drops below 200 if its set as my minimum like Set did
Sent from my SPH-D700 using XDA Premium App

Voltage Control doesnt use any "hacks" for setting frequencies, it just works with standard implemented sysfs.
The governor is responsible for respecting max/min frequency, its kernel implementation that should keep CPU running within desired freqs.

Can the UI include a CPU temp and aninfo page?
Sent from my armed and operational battle station.

SGS's only thermal monitor is refferred as "battery"...
Info page is somewhat coming, but I have to be sure what and how to put there.

[ROM][Sept26][INC S]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
User Mods
Revolution HD Theme from he_stheone64: Click. Please don't download, needs to be redone for the new framework
Theme from ATZ-007: Click.
Font-Mod fromATZ-007:Click.
Autobrightness-Mod from ATZ-007: Click.
Theme from liamstears: Click.

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

So far it seems to be a nice, clean and fast ROM.
But I noticed 2 Things:
1.) The 4 buttons on the bottom (home, menu, back and search) are not enlightened. So you can't see them in dark surrounding
2.) Gmail is missing and I can't install it from Google Market
But: Nice Work *thumbs-up*

Thanks，Thanks，

qarclub said:
Download link？
Click to expand...
Click to collapse
Look at the first post. There is a link to our site where you find the download for your device.

vaothien said:
So far it seems to be a nice, clean and fast ROM.
But I noticed 2 Things:
1.) The 4 buttons on the bottom (home, menu, back and search) are not enlightened. So you can't see them in dark surrounding
2.) Gmail is missing and I can't install it from Google Market
But: Nice Work *thumbs-up*
Click to expand...
Click to collapse
Thanks for reporting this with the buttons. I'll put it on our bug list.
This is with Gmail is strange because it should be installed during first boot.

It seems nice, thanks..

omg i need a s-off soon !! excellent 1

Great! I will download it sooner

As soon as the buttons lighting are fixed, this is getting a download! Well done guys.

At first: Thanks for your work! Nice to see a real Sense 3.0 ROM for our IncS.
The bugs (no video in landscape and backlight of the keys) seems to be a problem of most Gingerbread ROMs for IncS.
Do they come from the kernel or a bad file in the framework?

I thought it had something to do with the CRT affect. Is that included in this ROM?
Sent from my HTC Incredible S using XDA Premium App

We probably found a solution for the market issue with gmail. Any one here there has this problem and is able to try it?

AndroidMobileNZ said:
I thought it had something to do with the CRT affect. Is that included in this ROM?
Sent from my HTC Incredible S using XDA Premium App
Click to expand...
Click to collapse
CRT is not included at the moment. It is on the list for a upcoming release.

chrisch1974 said:
We probably found a solution for the market issue with gmail. Any one here there has this problem and is able to try it?
Click to expand...
Click to collapse
What can I do?

vaothien said:
What can I do?
Click to expand...
Click to collapse
Can you please try to install this fix and report if the market then works as expected?

Mhm seems unchanged.
After flashing the update, I still cant download Gmail from market.
Then I made a full wipe in recovery, and flashed the update right afterwards (without reboot)
Still no Gmail.
Maybe the Problem is that you cant download Gmail from the market in germany?
I even cant find Gmail in market .

[krn.modules] smartassV2 governor for Galaxy S3 stock Kernel

I've FINALLY managed to compile smartassV2 module for SGS3's stock kernel.
{
"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"
}
The trouble is that the stock kernel does not accept modules...
Every attempt I made ended up with an error about the version of module_layout. I even wrote to Samsung asking for clarification, but I have no reply yet (after about 24 hours).
I will write a post on my blog describing all the investigations; I had to go the hard way and patch /dev/kmem to skip the validation. I've created a small executable which does this.
The good part about it ? It is already included in the .tar.gz below and once executed, it allows any modules to be installed on stock!
I am almost sure that Samsung did not provide the up to date .config file (I am using the Update 1 .tar file) since I had to disable flags in .config to get rid of "unknown symbol" errors. And another proof, the validation errors related to the version of the module_layout symbol.
Thus, the install procedure is a one step longer, patchs3k needs to be executed once, and then any module can be inserted.
Installation procedure:
a) mount your /system in RW mode.
b) create folder /system/xbin/lib
c) copy the contents of the archive to that folder.
d) execute the provided load_smartassV2.sh script (which already does all the steps: calls patchs3k, inserts the module and sets it as current governor).
That's it!
Observations:
a) only for stock kernel.
a1) repeat after me: I will not attempt to run patchs3k if I already flashed a different kernel!
b) load_smartassV2.sh script is made so it is also runnable by Script Manager at boot as super user using the paths in the Install procedure.
c) if you have another way of loading things, you need to figure out how to execute the patchs3k file before inserting the module - I found that the easiest is with the method above.
d) smartassV2 supports lots of configuration options. The only think I made default is the ramp up increment, which is in 500MHz so you don't have to wait forever until the phone gets to max speed. The ramp down I left it at 100MHz increments. All these are configurable and you can echo values in the files found in the list below.
A brief description of each field (but with different values since back then I did it for Sony X10) is found in the Settings part of this post: http://forum.xda-developers.com/showthread.php?t=1212012
Code:
[[email protected]]/sys/devices/system/cpu/cpufreq/smartassV2# ls -1
awake_ideal_freq
debug_mask
down_rate_us
max_cpu_load
min_cpu_load
ramp_down_step
ramp_up_step
sample_rate_jiffies
sleep_ideal_freq
sleep_wakeup_freq
up_rate_us
Download:
Update: download disabled until hotplug issues will be fixed! Please check 4th post below, thanks AndreiLux!
Use it at your own risk!
cpufreq_smartass2_sg3_1.0.tar.gz
Enjoy!

Im really interested in the part regarding the patch to use any module without validation...
Waiting for kernel patch
Sent from my Desire HD using Tapatalk 2

The patchs3k is already bundled in the .tar.gz file above - is this what you meant ?

There's absolutely no point in having smartass on this device, especially on a stock kernel since there is no remaining hotplug logic on it to be used, if that would be even possible. It has major detrimental effects on battery life.
However, we would be interested in what you are doing inside of patchs3k to make it load the module properly and to see if we can use any of that to load Samsung's exFat driver module on custom kernels. Sources please?

viulian said:
The patchs3k is already bundled in the .tar.gz file above - is this what you meant ?
Click to expand...
Click to collapse
AndreiLux said:
There's absolutely no point in having smartass on this device, especially on a stock kernel since there is no remaining hotplug logic on it to be used, if that would be even possible. It has major detrimental effects on battery life.
However, we would be interested in what you are doing inside of patchs3k to make it load the module properly and to see if we can use any of that to load Samsung's exFat driver module on custom kernels. Sources please?
Click to expand...
Click to collapse
That's what i mean
Sources for patchs3k please
Sent from my Desire HD using Tapatalk 2

About the sources - I will create the article these days but I believe it doesn't matter; if you already have control over the custom kernel then you can just make it accept everything and see how things behave.
The trouble with what exFat (which I could also investigate if I have time) is that the CRC checks are thorough and if ANY of the structs used by exFat are different that what the kernel is build with, then there could be big issues with corruption of data and so on. Only Samsung (or sheer luck) could solve this issue. But I did not investigate so these are just assumptions..
@AndreiLux
Then it means I was extremely tired thanks for the explanations with hotplug. I have disabled the download so people won't take it without reading below.
One other thing, the kernel (3.0) like all other kernels has the posibility to create high priority work queues - alloc_workqueue with WQ_HIGHPRI as flag. It means that the work queue that rises the frequency should have higher priority so you don't notice any lag for example.
What I don't like about pegasusq is that it doesn't appear to create high priority work queues. I did not study carefully, but a quick search on the cpufreq_pegasusq.c doesn't show the high priority flag. Maybe the phone one has it ?
They also keep a history of the CPU usage (probably used with hotplugging also).
So I believe the two factors above might contribute to the lag I notice when waking up the phone.
I did notice this weird fact with the cores of the CPU not turning on or off with smartass2 - or remain in the state that pegasusq left them. I was checking test results and it appear to behave normally and have all 4 cores ON during stress test. It was late in the night and I did not check that they are not also shut down.
Maybe I should work on a smartass3 since I can add hotplug logic to smartass - but it is tedious you have to use locks and so on - and I don't have much time.
I think I have more success here with just building ROMs and not digging deep since you just take what everybody does and put a small thanks in a corner then you get all the Thanks and donations.

viulian said:
So I believe the two factors above might contribute to the lag I notice when waking up the phone.
Click to expand...
Click to collapse
The wake up lag is irrelevant to priorities or anything, it's caused by a) if you are referring to the wake up delay then it is because of the kernel is waiting for the modem to wake up which takes an eternity. b) if you are referring to unresponsiveness at the lockscreen, it was due to something in the Wifi drivers.

@AndreiLux Ok cool the modem interaction worths an additional look then!
BUT I have good news!
cpufreq_smartass2.c will be able to have hotplugging! I did a test module that activates cores and shuts them down and there it works.
In few days I will release the smartass2 with hotplug support for stock kernel.
One thing I saw, the pegasusq does NOT have a high priority work queue to bring the frequency up meaning that other work queues could interfere and actually introduce delays. It also has a complex logic to decide when to bring another core back online and it brings them back one by one.
I would like to have feedback from the community on what should be the bringing up / down behavior for each core for the new smartass2 governor.
I am tempted that upon waking up, to actually bring back all 4 cores at once. It is easier for me, FASTER to be executed (instead of going through heaps of samples to decide if one more core is needed) and is also on the same track with the initial smartass concept, FAST AND QUICK or go slow.
The delicate thing is how to handle shutting down cores. I can make it go back to 1 core and if loaded then bring back all again.
What do you guys think ?
I like this new way in customizing phones design by the community, not by what the rom cooker / kernel builder decides and that's it.

I find it fine and dandy, but the most critical point is why you would want to port such a feature to smartass when you already have pegasus with much more optimal frequency scaling. Also the frequency of which the cores are being hotplugged is incredibly high with runqueue sample rate/times of 50 milliseconds and time of bringing up the cores of only a couple of microseconds, all several orders of magnitudes below usual frequency scaling latencies. We've ported it to the S2 with magnificent results and ditched interactive based governors a long time ago, there is no benefit to it. Exynos is relying on aggressive and optimal DVFS scaling for power efficiency and interactive governors do not suit that too well.
It means that the work queue that rises the frequency should have higher priority so you don't notice any lag for example.
Click to expand...
Click to collapse
This is fine in theory but does it hold up in practice? The S3 is already considered as the smoothest running device running Android or even the smoothest device bar the iPhone.
Not trying to critique your work but I think your approach into improving things here is a bit flawed and viewing it from an odd angle.

Excellent constructive feedback! Thank you,
Let me explain my point of view:
1. First, there are many users that do not feel comfortable putting a custom kernel on the phone. Personally, I do not trust custom kernels even if they come with source code. Theoretically is correct to have the open; but I save a lot of time customizing what I trust (Samsung's stock kernel) than checking all the patches of custom kernels to start trusting them. And is not about privacy and so on, but I need the phone to work and I can't really tell if the custom kernel won't decide to play tricks when I mostly need it to work. So I stick with defaults and try to customize here and there.
2. Second, I have no idea how pegasusq compares with smartass2 unless I see them running - also, since I do debugging and so on, the phone uses different frequencies (mostly plugged and running stuff) and so I can't say if pegasusq matches the time_in_state pattern that smartass2 shows. Too early to tell.
And if it can be done why not ? It gives me more experience, it gives people alternatives. Plus, S3 is better than 4s, for sure, but what about the next phones appearing in the next half of year ?
This is just warm up for me to the phone, I have other ideas to dig and hopefully something will come up out of them (at least until the new big market killer comes around and we all jump ship to that one )

Any progress on this

None as it doesn't support multicore correctly...
Sent from my GT-I9300 using xda app-developers app

That was what he was trying to accomplish.andreilux and Simone gave him some new pointers.that's why I ask.

I had no time to take care of it but I am curious to do at least a bare metal version that will wake up with all 4 core at once instead of one by one which I believe pegasus does.
With the default one, the phone is sluggish for half a second when unlocking - I can see it because the launcher struggles for a bit.
But is true, smartass doesn't support cores activation/deactivation.

[Q] AHD custom kernel and settings

Hey guys and gals,
I've been searching AHD forums for a while now and I could find zip zero result on custom kernels even though I'm sure that I've read people write about Aaargh kernel before... [his user name's spelling ain't really helping either....]
So here I ask: where can I find it (or other custom kernels?), read what people have to say about it and what results are to be expected?
Lastly, what are you guys settings? I mean what voltages are you guys using? I understand that no phone/cpu reacts the same to undervolting, but I'd like to get an idea on how low I could expect to go...
I'm not really after overclocking as I find my AHD's performances acceptable at stock values; I'm just after better battery performance really.
Thanks in advance for your replies; I will be offline for the next few days, but will sure give thanks hits upon my return.
Cheers
/AL

[] AL [] said:
Hey guys and gals,
I've been searching AHD forums for a while now and I could find zip zero result on custom kernels even though I'm sure that I've read people write about Aaargh kernel before... [his user name's spelling ain't really helping either....]
So here I ask: where can I find it (or other custom kernels?), read what people have to say about it and what results are to be expected?
Lastly, what are you guys settings? I mean what voltages are you guys using? I understand that no phone/cpu reacts the same to undervolting, but I'd like to get an idea on how low I could expect to go...
I'm not really after overclocking as I find my AHD's performances acceptable at stock values; I'm just after better battery performance really.
Thanks in advance for your replies; I will be offline for the next few days, but will sure give thanks hits upon my return.
Cheers
/AL
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1893050

Ok thanks for the link.
I wasn't searching at the right place and on the wrong device forum...
So in an attempt to make this thread useful, I'd ask again: anybody wants to share their experience with that kernel on AHD?
I mean other than getting a phone that can basically now running up to 2GHz and down to 96 MHz, what did you get from it?
- How (and how much) undervolting did you do?;
- Any noticeable and verifiable battery saving doing so?;
- Any before/after benchmark results to share?
- any observations, bugs or just general opinion on the subject?
Personally, I've noticed once or twice that the phone had a hard time waking up when I used 144MHz (forgot the exact value) as min cpu frequency (no undervolting). The screen would not turn on with either volume rocker or power button...it only did after a lot of insisting... And that was just within a couple hours of testing.
I've since reverted to CM11 kernel since I was eager to find out if a semi-dirty (no stock rom reflashing first) nand backup restore would switch the kernel back. And it did, but then I've also re-installed CM11-M8 for other reason/issues... (that too brought back CM kernel - at least that's what the "about phone" is giving).
Anyhow, the debate is open on the usefulness of that custom kernel. If no one dare to pitch in here, I'll just ask a moderator to delete the thread...
But I'm still eager to find out about how to undervolt as I always did on my Defy.
Cheers
/A

I'm also curious about any battery-saving benefits that can be gained with Kernel adjustments; especially when screen is on (since I drive a lot with the screen on all the time). I have no interest in Overclocking, and would rather have the phone last as long as possible and still be useable.
Currently using arrrghhh's kernel (May 23 version) with:
1. Min 384000 (default)
2. Max 1458000
3. Scheduler: deadline
4. Governor: smartassV2
5. App: Trickster MOD
Also, the only way I've been successful in changing anything is by using the Trickster MOD app. Between CarbonROM and the CM11 (epinter) that I'm using now, I've never been able to get the kernel changes to stick. Didn't matter whether I used the default kernel or arrrghhh's, any modifications in my settings always reverted back at some later time.
Trickster MOD uses some workarounds to get it to stay, and I haven't had any issues since.

quasihellfish said:
I'm also curious about any battery-saving benefits that can be gained with Kernel adjustments; especially when screen is on (since I drive a lot with the screen on all the time). I have no interest in Overclocking, and would rather have the phone last as long as possible and still be useable.
Currently using arrrghhh's kernel (May 23 version) with:
1. Min 384000 (default)
2. Max 1458000
3. Scheduler: deadline
4. Governor: smartassV2
5. App: Trickster MOD
Also, the only way I've been successful in changing anything is by using the Trickster MOD app. Between CarbonROM and the CM11 (epinter) that I'm using now, I've never been able to get the kernel changes to stick. Didn't matter whether I used the default kernel or arrrghhh's, any modifications in my settings always reverted back at some later time.
Trickster MOD uses some workarounds to get it to stay, and I haven't had any issues since.
Click to expand...
Click to collapse
do you mean may 25?
{
"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"
}

sliker90 said:
do you mean may 25?
Click to expand...
Click to collapse
No. "CLICK TO SHOW CONTENT", then download the latest version (May 23) that doesn't use SaberMod. Only reason I was using that was because arrrghhh mentioned that SaberMod thing was experimental and may have issues. So I just chose the safe option.

ok thank you

sliker90 said:
ok thank you
Click to expand...
Click to collapse
Since you're a new xda member, I'll remind you that there is a button specially made to thank people... Look at the bottom left of the post useful to you...
As far as the undervolting goes, I found that the free app called "Trickster Mod" can do voltage changes. So I've done a bit more testing with the May 23rd anykernel and my results weren't that great....
First, I went too aggressively and try to lower the voltage by 150mV for every cpu frequency and that made the phone reboot as soon I applied it. I mention this because the lesson here is to
*** NEVER SET THE "apply settings on boot" OPTION UNTIL YOU ARE ABSOLUTELY SURE THAT YOUR NUMBERS WORK FINE. ***
Not doing so might make your phone unbootable and you might not even be able to boot to recovery/bootloader mode to revert kernel/settings....
Ok, that being said and since I'm after battery saving while the phone is in use*, I then went ahead and lowered by a more reasonable 50mV for each frequency (the app let's us move by 25mV steps). That 'worked' fine and I've experienced no sudden reboot. BUT, after some time (30 minutes), I've noticed some slowdowns and I've also had issues with an app that stopped creating video thumbnails. So all in all, that called for the end of my testing and I restore my CM11-M8 nandroid as I'm not going to live with such drawbacks for some slight (still yet to be proven) battery improvements.
So no custom kernel for me afterall.
.... Should this thread be deleted???
You guys tell me.
Cheers
/AL
- - -
*: hence I see no point of lowering the minimum cpu frequency: my phone does not take excessive power when on iddle, it deepsleeps fine and I use airplane mode at night..
*': some have argued that increasing the max cpu frequency allows the phone to complete tasks faster and return to a low power state sooner resulting in a lower overall battery use. I have my doubts on this and I'm pretty sure that it depends on what kind of task the phone is mainly doing. Anyhow, this is not something worth testing at this time... My AHD does its job just fine at the stock max cpu f.