yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II SGH-I777] iXNyNe:
I understand your point, but there's a thread by gecko about his magic configuration (voltage control settings) that seems to work for 600+ users on a few different kernels, which seems pretty universal to me.

This prepackaged configuration is just a handy set of tweaks, at best a shortcut, but a handy one no less.

My guess on my random freezing is a gpu level is undervolted a bit too much for my device.

At this point I'm almost tempted to recommend/request that cwc3 drops the 3 gpu state idea from the configuration, and switch back to using a prepacked S#voltctrl file (keep anything that has nothing to do with the voltage control app in the separate init.d script). This way if one individual person has need to change a value from the preconfig offered here it can be done via voltage control app, and as users get to know their devices better they will know what to change, this will just cut down on how much has to change.

That way the settings are more of a recommendation than a preset.
[AT&T Samsung Galaxy S II SGH-I777] pikachu01:
You can test if the undervolting is too much on the GPU by testing it with Nenamark2. If Nenamark2 cuts to black in the beginning (or slightly jerky with undervolting), then your GPU can't handle it.
[AT&T Samsung Galaxy S II SGH-I777] iXNyNe:
Well that's a clear indication for me. Its jerky just opening the app and pressing run results in reboot.
[AT&T Samsung Galaxy S II SGH-I777] iXNyNe:
At this point after some testing I'm comfortable saying the CPU voltage settings from geko are solid but the gpu settings we are using here are not quite stable (at least for me) so I'd say for the sake of being universal (and DOH! Being lazy and simple) the gpu settings need some work

I'm finding low state being 100mhz @ 800mv seems pretty stable for daily use

High state being 267mhz @ 1000mv seems more stable

The middle state I can't find a good balance, and testing without it seems to be more stable than testing with it

I see the idea of a middle state saving battery, but it seems to sacrifice stability, and with all the other stuff we have going on to save battery I hardly see dropping the middle state as a big loss.
[AT&T Samsung Galaxy S II SGH-I777] Dimatchka:
Not sure why but I dropped 9 percent in battery in the last hour.... From texting and reading xda 4 % in 30 min on stand by? .2.5 might be better i'm continue to test
[AT&T Samsung Galaxy S II SGH-I777] dc41:
MIUI 2.2.3 w/ Siyah 2.6.12 & Init.Doh 0.2.8 exp. Nenamark2, Quadrant, etc. all fine. Install with double boot with no problem.

I'll uses it for a few days and report back stability and battery performance. Thanks for the scripts!
[AT&T Samsung Galaxy S II SGH-I777] cwc3:
Been playing with conservative/noop a bit. I think I like it and should suit most people. Not like its hard to change at all. Also changed sleep bus back to 400, and its going to stay there for some time. Change 2nd step in GPU back to 160, but keeping the %'s the same. Commented out ondemand scaling. Couple tweaks on screen off hotplug parameters. Changed 500Mhz bus to 266Mhz.

Keeping the voltages the same as geko. People will have to try to find the right one for themselves from here.

I will do some more testing on my phone and see how it works then put it as new EXP.

Update: No SoD's today for me, plenty of usage. Main post updated.
[AT&T Samsung Galaxy S II SGH-I777] iXNyNe:
Grabbed 0.2.9 and the only thing I had to change was the voltage foe gpu 267 from 950 to 1000. No other changes. At 950 nenamark2 freezes when I hit run. At 1000 it runs but is a little choppy, hardly noticeable. I haven't tried upping it any further to see if it gets rid of the (hardly noticeable) choppy-ness.

50 extra mv shouldn't impact battery, especially with the lower two states and their lower voltages.

More testing could be done by setting the gpu min and Max to the same speed and then find minimum voltage tolerable for 100, then 160, then 267 one at a time, maybe ill do that tomorrow.

But main point, 267@1000=stable
[AT&T Samsung Galaxy S II SGH-I777] cwc3:
In .3.0 I will go 1000mV and see how it plays. Also going to throw in some network/memory tweaks along with loopy_smoothness_tweak in case people don't have already. Testing that right now.
[AT&T Samsung Galaxy S II SGH-I777] Alucardis666:
Gonna give this a shot and see what happens. Thanks for sharing.
[AT&T Samsung Galaxy S II SGH-I777] chase10784:
Just thought I would inform you guys of my experience on .2.8/9 I swithced about 75% into it off charger. I have one of my own modifications in changing CPU max to 1000 instead of 1200, I'm on the latest Siyah running Turkbey minus all the scripts that they put in and replaced with these scripts. Also changed the turkbey modem back to kk6 instead of the one included with the rom

The phone is running smooth and battery life has been fantastic. I have 16 hours 15 min off charge with a display time of 7 hours 30 min from 100 to 5%. Mostly use during this time was lots of txting, web browsing, checking emails (set to push), about 40 min of music, a few apps like Movies for watching trailers and such, and weather widget updating on occasion

Display settings are min brighness and power savings off. I had wifi on the entire time with GPS and bluetooth off. Never seen battery results this good with these settings. Thanks for all contributors that helped put this together :).

Edit: From 100 to death I got 8 hours and 17 min of screen time
[AT&T Samsung Galaxy S II SGH-I777] cwc3:
8 hours? Maybe 5. Next time show us some screenshots, that's crazy.
[AT&T Samsung Galaxy S II SGH-I777] chase10784:
I have one for the 7.5 hours but not the over 8, i forgot.the dip on the overall battery use was strange but it still lasted that long. The dip was when i flashed .29 but as long as it still survived a few more hours it's all good
[AT&T Samsung Galaxy S II SGH-I777] iXNyNe:
I tested higher voltages for the gpu, none made a difference at all, ninamark2 still slightly choppy. I'm assuming this is caused by the conservative governor, but I also consider ninamark2 to be a case of extreme. Its very rare that you will be doing something with your phone (other than benchmarks) during your day to day activities. So my opinion of conservative being the best option for a daily driver still stands.
[AT&T Samsung Galaxy S II SGH-I777] :
Installed latest 0.2.9 and now all the images from drawable, drawable-hdpi, etc are showing up in my gallery :(
[AT&T Samsung Galaxy S II SGH-I777] cwc3:
:( That's a first. Can't think of anything different I have done with permissions/directories since I released v0.2.

Check out: http://androidforums.com/android-media/444601-photo-gallery-showing-drawable-folders-content.html

Doubt this will help but 0.3.0 is out.

I was going to do the loopytweaks, but doing some reading up on it I am not sure how beneficial it is. Placebo for most.
[AT&T Samsung Galaxy S II SGH-I777] :
Fixed by pulling "framework-res.apk" and "twframework-res.apk" from ROM zip file.

Then

"adb push framework-res.apk /system/framework"

"adb push twframework-res.apk /system/framework"

"adb reboot".

No more drawable etc showing up in gallery.
[AT&T Samsung Galaxy S II SGH-I777] iXNyNe:
Gpu 267 still set to 950 in 0.3
[AT&T Samsung Galaxy S II SGH-I777] cwc3:
Yea, I decided against it at least for now. People are going to need to find what works best for them.

Anyone having any networking issues with the latest version? Dropping wifi etc.
[AT&T Samsung Galaxy S II SGH-I777] DefTaker:
Yeah, I have this issue too...ICScrewd 2.0.1 and in Gallery, I see icons for blue and "frosted" themes, I guess? :confused:

I've just been ignoring it - wondering if maybe just dropping a nomedia.txt file will stop them from showing up in the gallery.
[AT&T Samsung Galaxy S II SGH-I777] Alucardis666:
Seems every time I flash this it either messes up my rom/theme or kills my battery. Idk if I'm doing something wrong but I've tried out the last 4 updates of this and it never seems to go very well. Just my 2 cents.
[AT&T Samsung Galaxy S II SGH-I777] cwc3:
Did this happen with .3.0? I am currently looking into what might of caused that in .2.9 at the moment, possible unmounting issues.

I will see if we can handle no cache cleaning next exp.
[AT&T Samsung Galaxy S II SGH-I777] DefTaker:
I don't think it happened in 2.5 stable but it did happen in 2.9. I just installed 3.0 and it's still there...
[AT&T Samsung Galaxy S II SGH-I777] cwc3:
0.3.0 doesn't fix it. Sadly I don't have a fix for it right now, but I will be looking into it. I am currently using jivy's ics also, and with the Green theme. I have noticed a couple images turning to blue lately, so I will look into that.

Probably tomorrow before I have a answer for you, for the time being you might have to try the fix a couple posts above:

Possibly this cache cleaning/mounting is too much. Thanks for reporting this to me, some people just revert and never let me know why.
[AT&T Samsung Galaxy S II SGH-I777] DefTaker:
No worries cwc! :thumbsup: It's just a minor annoyance more than anything.
[AT&T Samsung Galaxy S II SGH-I777] :
Got one SoD today on 0.3.0. Not sure why. Hasnt acted up since and battery has been great. Jivys ICScrewD 2.0.1 with Siyah 2.6.12 and changed the max CPU in script to 1Ghz

---------- Post added at 07:20 PM ---------- Previous post was at 07:19 PM ----------

Also noticed that the fix I posted says youre not signed into a Google acct and makes you add your acct back. Just a heads up
[AT&T Samsung Galaxy S II SGH-I777] Shadow12347:
After updating from 0.2.5 to 0.3.0 my whole interface seemed to get a little bit laggy. Before it was nearly perfect, but now I'm starting to see the effects of UV xD. If this helps I'm using MIUI 2.2.3 with siyah 2.6.12 and I am also using the v6 supercharger.

This may seem like a stupid question but should I be using a program like cpu master with this? Or would cpu master override the effects of this? I mean even though I still have it and its profiles I do see a significant increase in battery life and such so idk. I also manually changed any setting in my default profile that differed from what init.doh had (minus the voltages) so for example I am at 200 min 1000 Max, conservative and noop.
[AT&T Samsung Galaxy S II SGH-I777] Scott Summers:
Battery life has been exceptional with .3. Two things I've noticed so far:

1.) SOD x1. I will monitor to see if it will happen again. :-(

2.) Slightly sluggish when navigating between screens. Very minor and almost impossible to notice. Not an issue with me but I'll play with other governors later to verify for improvement.

Siyah .12 + icscrew 2.01

Sent from my SGH-I777
[AT&T Samsung Galaxy S II SGH-I777] kest874:
.3 working awesome here!
[AT&T Samsung Galaxy S II SGH-I777] :
Havent noticed that at all
[AT&T Samsung Galaxy S II SGH-I777] cwc3:
Thanks a lot for the feedback folks. Helping me make this a better script.
[AT&T Samsung Galaxy S II SGH-I777] nyydynasty:
030 is working great (running turkbey v32). Not one problem yet.
[AT&T Samsung Galaxy S II SGH-I777] dahlem:
.3 worked great I also felt a bit of sluggishness so went back one version . . .
[AT&T Samsung Galaxy S II SGH-I777] cwc3:
Trying to make a new stable version, so .3.1 is my attempt.

DOES NOT REMOVE CACHE. Brought voltages up 25mV on most (the same as .2.5). Removed a few things in memory/network tweaks. Threw in AGPS PATCH thanks to crypted, hopefully for faster fixes on GPS. Dropped max down to 1000Mhz. Brought up 267Mhz GPU to 1000mV. resolv.conf to Google DNS. Attached.

I will put on main post once more people try.
[AT&T Samsung Galaxy S II SGH-I777] Nuskul:
Is anyone else having shutdowns when plugging in the charger? If I unplug, it will automatically reboot and run fine, plug back in and it shuts down and is unresponsive. If I powered down and plugged in normal charge screen appears.

I flashed thunderbolt 2.51 yesterday and had same problem. Used nandroid backup and ran fine with just siyah 11.

Using 3.0 by the way
[AT&T Samsung Galaxy S II SGH-I777] DefTaker:
Hmm...that's odd - usually after flashing the init.doh script, the 1st book takes anywhere from 2 - 3 minutes usually. This time I installed the new 0.3.1 file and it booted up like normal. So re-flashed it and the initial boot still booted up quickly...I made sure to watch the install screen and it said that all the old files were deleted...

Did you do something to shorten the initial reboot time? <-- No, I'm definitely not complaining...I'm just wondering if 0.3.1 got flashed properly.
[AT&T Samsung Galaxy S II SGH-I777] cwc3:
Made it so it doesn't clear your cache.
[AT&T Samsung Galaxy S II SGH-I777] DefTaker:
D'oh! Read that but it didn't register!

Anywhoo - I figured out where the ICScrewd icons are coming from if you're on Jivy's ISCrewd 2.0.1 ROM (don't know if this is happening to previous versions or not).

They're the lock screen icons that are appearing in the gallery so I just used Root Explorer to search for the three folders (i.e.: ICS_Icons; White PFittech Icons; and Cobalt_blue PFittech Icons) and created a .nomedia file in each folder > REBOOT > wait for phone to finish scanning media > go to Gallery and voila! the icons are now gone from the gallery!

(Good thing I remembered how to do this from the G1 days! ;):D )

I know someone else posted a different way of doing this but I think this way is easier.
[AT&T Samsung Galaxy S II SGH-I777] :
Yes very much easier. I didnt know about those folders. Thank you sir :)
[AT&T Samsung Galaxy S II SGH-I777] DefTaker:
You're welcome! I'm glad to help out anyone here after all the tremendous amount of help I've received! :D
[AT&T Samsung Galaxy S II SGH-I777] Shadow12347:
Unfortunately I'm still finding 0.3.1 to be laggy on my phone... it is definitely better than 0.3.0, but it is also definitely not as smooth as 0.2.5
[AT&T Samsung Galaxy S II SGH-I777] cwc3:
Most likely governor. Change from conservative to ondemand and noop to sio.
[AT&T Samsung Galaxy S II SGH-I777] Shadow12347:
Yeah I kinda figured that was why haha. I just liked the extra battery life I got from conservative/noop.
[AT&T Samsung Galaxy S II SGH-I777] DefTaker:
Well in terms of battery life, v0.3.1exp has been the best for me (so far). 91% deep sleep compared the previous releases that I have tried (v.0.2.5; v.0.2.8exp; v.0.2.9exp; v.0.3.0exp).

The best I was getting before was 84% deep sleep according to CPU Spy (but the battery still lasted a long a while & I didn't see anything that was holding a wakelock or partial wakelock in BBS.

For performance though, upon initial boot up / reboot / or unplugging from a 100% full charge and opening up the applications drawer, I'll only have 3 or 4 apps showing and then about 1 second later (or if I blink :D) all of sudden the rest of my applications show up. <-- If I try to scroll left or right, immediately after this happens, it'll lag for 2 seconds and then the system becomes normal (i.e.: quick, snappy & responsive) again.

I can only assume this is due to the conservative setting on this script - that's fine by me. I'm willing to trade a little bit of lag on initial start up / wake up (<-- haven't really tried to see if it's the same when waking up the phone from deep sleep) for better battery so the slight lag becomes a non-issue for me.

Keep up the great work cwc3!
[AT&T Samsung Galaxy S II SGH-I777] mrRobinson:
You'd rather have lag then maybe 1 hr less battery?

I want max battery as much as the next guy but having lag on this phone is unacceptable to me. This script says "battery & performance" but as it stands now its really just battery sacrificing performance. I love the script but i need to set it to ondemand and I also enable 1200 and 1400 cpu states. Days go by where cpu spy doesn't show I hit 1400 at all but when I launch an app or game that needs it I don't want it to run like crap. At the end of a day with heavy usage I'm docking my phone to charge for the night with anywhere from 20-30% left on it.

If you find you are doing the same then you don't have to live with lag either. Not saying my settings work for everyone but I think we can get to a point we where get good battery life without sacrificing performance as you are accepting now.
[AT&T Samsung Galaxy S II SGH-I777] pikachu01:
The percentage of deep sleep is just a ratio. It a direct correlation to how much screen on time is (unless you've developed a pattern of using the phone 100% the same every time you charge the phone).
[AT&T Samsung Galaxy S II SGH-I777] Stevenrogers_420:
Im only getting 2 gpu states.. 100 and 167.

Edit: im on 3.1
[AT&T Samsung Galaxy S II SGH-I777] cwc3:
I don't blame you. I want to find that right balance for the time being before I hit version 1.0. Conservative/1000 definitely screams lag for a lot of people. Also the gpu 3 step causes a decent amount of lag. With these experiments I can see how people respond to certain setups.

Bare with us here. Changing a few things like governor/CPU frequency is no biggie. Thanks for the review, however blunt they are.
[AT&T Samsung Galaxy S II SGH-I777] mrRobinson:
I didn't intend to bash your script at all, sorry if it came off that way. I also don't expect to install it and have it be perfect for me. If it is, great, but if not it is designed that it can be edited/tweaked to suit each user.

My only real point was that I personally will tweak it (if needed) to get it to the point where I have max battery with no lag (good perf). Once i've introduced lag, I've gone too far one direction.
[AT&T Samsung Galaxy S II SGH-I777] treyvaporizer:
How is 3.1 working for everyone?
[AT&T Samsung Galaxy S II SGH-I777] nyydynasty:
0.3.1 has slightly better battery life than 0.3.0, which worked great for me ... so thats saying a lot for 0.3.1. No lag issues on either version.

2 thumbs up, so far.

edit: I should add that I'm not using setcpu or voltage control (or any of those types of apps). Just the rom and this script...thats it.
[AT&T Samsung Galaxy S II SGH-I777] DefTaker:
Yeah, 3econds of Lag! IS that really that much LAG? 3 SECONDS is really KILLING YOU???

Damn, do what you want and OV & OC if you really want MAX peformance but 3 seconds for 2 - 5 more hourse of BATTERY LIFE --> LAG, YEAH - I CAN LIVE WITH IT when it's only 3 or so seconds.
[AT&T Samsung Galaxy S II SGH-I777] iXNyNe:
i had a lovely type up response to a couple posts here but session timed out

the short and dirty was this

cpu clock speed 1200 = good

samsung designed the phone to be that way

if someone wants to oc they should learn to edit the scripts and understand what they are doing

related side note, captivate (sgs1) gpu was underclocked out of the box on stock roms because of battery drain and overheating - samsung felt it wouldnt affect performance thanks to the boss processor

samsung isnt always right, but you can bet they do a good bit of mass scale testing before they ship a device

also my rig is pretty basic, no unwanted wakelocks, no stock samsung framework, no carrier apps

so for me this setup (0.3.1) is stable, smoothe (no lag), and gets good battery life

on a stock rom this might not be the case

for the person saying they only have 2 gpu states while running this script

wrong

do not use voltage control or another cpu app, they are not built to show you all the stuff this script has included

learn to read and edit the script - this has been said many times, including in the OP

if you cant read then dont flash things

cwc3, keep up the good work, your efforts are very appreciated

"If it's not broken, keep fixing it until it is!"
[AT&T Samsung Galaxy S II SGH-I777] DefTaker:
Just woke up the phone from a 10 hour standby and absolutely NO LAG. The LAG only happens on REBOOT/POWER ON when the phone is running media scanner and loading/drawing files in the applications drawer. Again total of 3 seconds MAX LAG.

Now, if you're constantly turning off and then turning on your phone or rebooting, then you may experience this INITIAL lag. Other than that, I haven't experienced any other lag.

Haven't played with Youtube or videos or the camera yet to see if I've come across any issues though. I'll give that a try later and report back if I run into any issues.

So far, so good.
[Samsung Galaxy Nexus] daledenton:
My experiences with Google wallet have been strange. Here's a run down:

Attempt 1

Went to Macy's, took about 4 tries before it went through.

Attempt 2

Went to meijer, got an error saying card reader could not be detected. I tried several times before giving up.

Attempt 3

Went to 7-11, no problems whatsoever.

Attempt 4

Went back to meijer tried a different checkout lane then the last time. No problems.

Attempt 5

Meijer, one more time went to the SAME lane as the time it worked. Didn't work this time got that error again saying couldn't detect card reader.

Is anyone else's this inconsistent? I don't understand. I unlock my phone, hold it up to the machine until it says sent. Any suggestions? Why is it like this? Everyone else stories I read say it works flawlessly or it doesn't work at all.
[Samsung Galaxy Nexus] NyPlaya513:
are you using any particular case, did you update the app to the newest build?
[Samsung Galaxy Nexus] krichek:
Any errors I've encountered could be chalked up to one of two things. Either the pad was not turned on/not connected (make sure there is a green light on the pad), or the network is down\you dont have a network connection.

The network has been somewhat spotty for me over the last day or two. Today it was down for almost 2 hours. An easy way to tell if the network is down is to look at the app, select payment cards, then choose the card you are using. I use the google prepaid card, tap it and at the bottom under userid if there is a number you are connected to the network.. If the network is down or you do not have connectivity you will see something that says "can't connect to bank". You can not make a purchase if you do not see your userid, I always open the app now and check while I'm waiting in line.
[Samsung Galaxy Nexus] daledenton:
Thanks! I'll give that a shot(checking the user id) that sounds like it could be helpful.

@nyplaya

no, I don't have a case and I don't know if I have the latest updated version. I haven't checked because I didn't want to update and become a victim of the secure element error. I'm not exactly sure what the cause is and didn't want to risk it. But if its safe to do so, how do I find out if I have the latest version and where would I get it?
[Samsung Galaxy Nexus] NyPlaya513:
you can do one of two things, follow the OP here:

Or you can try my little faster method: not sure if it is for the paid version only but if you download and install the APK of wallet, then use the app appmonster to backup the app, you can then simply select it in appmonster to view in the market and it bi-passes the restriction of the carriers in the normal market app it allows updating
[Asus  Eee Pad Transformer Prime] benefit14snake:
I was wondering if anyone else has had problems with this encryption type? I usually run with no encryption and don't broadcast my ssid but since my Fios router went out the new one requires it. It seems to stay connected for about 5 to 10 minutes then pages stop loading.. I don't seem to have this issue on wep .... my laptop and Droid razr don't seem to have this problem. I am using the actiontec rev I which is the newest router Verizon offers.
[Asus  Eee Pad Transformer Prime] Lock-N-Load:
I am using WPA2 on my TFP no issues. I came from WEP to WPA2 after reading some info about how WEP can stunk speed.
[Asus  Eee Pad Transformer Prime] benefit14snake:
Really weird....ill try wep at my house... maybe ill call Verizon to see if I can disable encryption all together. Wep at work runs pretty well.
[Asus  Eee Pad Transformer Prime] BarryH_GEG:
I strongly advise against it. It's also pretty shocking it's still being used at a place of business.

http://www.pcpro.co.uk/realworld/356572/the-ease-of-hacking-a-wep-network
[Asus  Eee Pad Transformer Prime] bobd2754:
I had the same problem, what fixed it for me was using WPA 2 AES only no TRIP. Hope that helps.
[Asus  Eee Pad Transformer Prime] benefit14snake:
Ill try this but I think that's how it already is.