yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] nemesis2all:
It includes the dummy tethering module that has been used for a while. If the mod for straight dhd.ko without dummy module proves alright I will switch to that.
[Fascinate Android Development] TheSonicEmerald:
Dang, what settings are you using? My smartbench is 900 and 2100 on 1.4ghz cfq. That's some insane speed!

EDIT: nvm, I forgot to see the states for higher oc in voltage control. Oops. My scores higher than yours now, problem fixed :)

Sent from a Limited Edition phone from a Premium app..
[Fascinate Android Development] heloguy:
Thanks much. I can't believe I missed that. It's in BOLD
[Fascinate Android Development] bhfd64:
Reflashing ROM fixes the broken root issue as well.

Tappaty Talk'd
[Fascinate Android Development] saps:
I see a lot of you guys using SmartBench 2010, you do know there is a 2011 version ;)
[Fascinate Android Development] jam.i.s0n:
1500 mhz with 1500 mv and running stable for about 8 hours.. still getting great battery life!!!

very amazing, and great job nemesis.
[Fascinate Android Development] nemesis2all:
Interested to know what kind of quads and linpacks to you see at 1500mhz.
[Fascinate Android Development] TheSonicEmerald:
Been running at 1.3ghz and been playing Dungeon Defenders for the last 2 1/2 hours. No lockups, perfectly stable. Have to see battery life after some calibration tomorrow.

Sent from a Limited Edition phone from a Premium app..
[Fascinate Android Development] hecantbreathe:
Freezes on boot up. Any help is appreciated.

EC01 debloated

EC01 Radio

Newest CWM

MIUI/GB theme
[Fascinate Android Development] saps:
I was getting the same problem and I couldnt figure it out. I was wiping cache and dalvik and nothing. My fix was to in voltage control remove the boot settings. I then was successful in booting the latest OTB reloaded kernel.

Sadly, I cannot match the uv with this new kernel I did on the 1.0b from 4-12. Most of my steps have had to come up by 25mv. Not an earth shaker but still. Oddly, I de-selected 100Mhz since I too found rock solid stability with a 200Mhz floor but the step is still active according to Root System Tool. The previous 1.0b from 4-12 did not even have 100Mhz enabled per se so that was a non-issue there. I suppose as long as its stable I dont care about 100 vs 200Mhz as the bottom step as I always had them at the same voltage anyway. I just hope I can get that battery life where I it was.

Also nemesis or anyone who knows. Can someone give a quick synopsis or idiots guide to the various scheduler options? That would be most appreciated :)
[Fascinate Android Development] neyenlives:
So its a bit early to judge but I flashed this this morning with a full charge and have been listening to music all morning, even made a call and surfed a few pages and I am only down to 62% battery. That activity on the other common kernels floating around would have had me around 50% remaining, so some improvement.
[Fascinate Android Development] dalrym05:
Its not to early. Mine has been very good with all of his kernels. I've been unplugged for 10 hours with moderate texting and a little web reading the forum at work and I have 79%.
[Fascinate Android Development] CrucialBT:
I got 38 hours (most using wifi) out of my phone over the last 2 days with moderate usage. I think that's remarkable.

I just flashed the reloaded kernel and I can also state that regardless of having 100 mhz unchecked in the states tab, I still show 100 mhz being used. However, so far it hasn't caused an issue. My damn phone still doesn't like to operate at anything over 1200 mhz though. :/
[Fascinate Android Development] ruswood:
I don't see how people get so much battery life I use my phone a good bit and have tried lots of kernels on superclean but after 4-5 hours its dead. I don't have any Widgets running either. I'd be amazed if I could just get through a day without swapping batteries.
[Fascinate Android Development] saps:
I see Im not the only one then with the 100Mhz issue.

RE: the scheduler -

I messed around with bfq, cfq and sio. Interesting as soon as I changed it my quadrant IO score shot up several hundred points. Voltage control told me it was cfq but perhaps it was not enabled? Previously I was getting near to 4000 on the IO score and now its in the 4600 range. The also of course brought my overall into the low 1900's. In the end after running 2-3 tests with each scheduler I can say they all bench about the same. For me on my phone perhaps a slight edge to cfq so thats what Im using now. But I mean the difference is maybe no more than a few dozen points in IO which affects overall quad score by just a few single digit points between cfq, bfq and sio.

Im further pleased to report 1300Mhz is stable for me on the same 1300mv I had previously and that 100 and 200Mhz are doing fine with their -100mv UV. The problem for me is one of the following steps. Either 400 800 or 1000. Right now I have them all at -50mv whereas previously I had 400 at -100mv and 800 and 1000 at -75mv. In then end its not a huge deal since at idle rest Im still at -100mv on my bottom. Just curious that the middle steps have been affected as much as they have been.

With all the kernel flashing Im probably going to reset batt stats once I finalize a new voltage profile and then go from there.
[Fascinate Android Development] saps:
Thats probably it you just use it more than most of us likely. I mean if I play robo defense Im burning like 30% per hour on the battery or something like that. Most battery savings and life come from just having it sit idle with the screen off. Constant use will kill even the best uv in hours; thats just the way it is.
[Fascinate Android Development] chrisexv6:
Do you have a complete list of your current steps + voltages? I can gleem most of it from this post, but wasnt sure about 600, 1120 or 1200 (or if they are even in use)

Thanks.

-Chris
[Fascinate Android Development] beray5:
Here is my settings.
[Fascinate Android Development] saps:
Please note 100 and 200Mhz are -100mv. As you see by my states shot I don't intentionally enable 100Mhz but it still engages for whatever reason.
[Fascinate Android Development] nemesis2all:
OP updated. Changes are location of su binary and it installs Superuser.apk during kernel install. Should give you root no matter what. If you are already on OTB-Reloaded-ver 1.0 no need to wipe current voltage control settings. If you are not on OTB-Reloaded you will need to.
[Fascinate Android Development] tapout27:
hahaha awesome
[Fascinate Android Development] nemesis2all:
Also I changed it to where rootfs is remounted ro as a safety net. I'm not sure if it will cause any issues, just testing it out. If you need to remount rootfs rw do the following from adb shell or terminal emulator.

# busybox mount -o remount,rw /
[Fascinate Android Development] NOsquid:
TY for update nemesis2all :)

I can't toggle 100mhz off either. Something about the bottom step doesn't play nice with voltage control, it was weird when you had 200mhz as default too.

Easy enough to change in Root Explorer but doesn't last through reboot unfortunately.
[Fascinate Android Development] nemesis2all:
Does this not work to set minimum?

echo "200000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
[Fascinate Android Development] NOsquid:
Does that last through reboot? Sorry I just edited the file in RE because I'm lazy. I will try, my bad..

Edit: ADB didn't last through reboot either. Oh well :)
[Fascinate Android Development] ssewk2x:
It does work, but it does not stick after a reboot.

In order to have it work through a reboot, I had to create an init.d script that did that command. I've attached a zip file you can flash through clockwork (not the edify version, sorry) that will take care of it for you.

Note that this is a butt-ugly hack - all it does is the "echo" command nemesis gave you above every time you boot.

Another thing the zip file has in it is a script called sys_rw.sh that, when run from terminal emulator, will remount your /system partition read/write.

Enjoy!
[Fascinate Android Development] nemesis2all:
I may take that script and modify it for edify. Thanks for helping out.
[Fascinate Android Development] ssewk2x:
Hey nem,

Yeah, that works, but like I said before, it doesn't persist past a reboot. I think the real problem here is that the kernel is ignoring the "0" for 100MHz in /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table. Speaking as a professional software developer, it seems to me that the states_enabled_table should take precedence over scaling_min_freq. Maybe I'll pull your source and see if I can track it down myself. Race ya? ;)
[Fascinate Android Development] NOsquid:
Thank you for this, worked like a charm :)
[Fascinate Android Development] nemesis2all:
Can check Kernel/drivers/cpufreq/cpufreq.c off the top of my head I believe that is the path. I don't feel like racing and don't feel like doing any more commits today, so you win :P.
[Fascinate Android Development] BeeDubs:
Just bought you a beer. Hope others do the same.

You deserve it, man! Cheers!
[Fascinate Android Development] nemesis2all:
Thank you sir. Beer is always appreciated, and glad people are enjoying the work. A lot when into rebuilding from ground up.
[Fascinate Android Development] ssewk2x:
That's what I needed - thank you!

I'll let you know if I find anything. Downloading your source now :)
[Fascinate Android Development] rsswga:
yea... I often wonder which leg these guys are pulling
[Fascinate Android Development] neyenlives:
So its looking like 18 hours roughly for me. Fairly heavy use. Voodoo Sound really put a hit on the battery, but worth it.
[Fascinate Android Development] ssewk2x:
I think I got something, but...

Hey again, Nem!

I think I found something and fixed it.

I ended up changing cpu-freq.c under Kernel/arch/arm/mach-s5pv210/atlas, and then running the build_kernel.sh file under Kernel. Nice, btw, how you guys bootstrap the toolchain like that :)

But .. I just want to be sure that if I flash the resulting ZIP file and the kernel is completely fscked, that I'll still be able to get into recovery and flash something else. I would have tried it this morning, but I'm already late for work. Also, the IT environment at work would make trying to recover my phone wildly impractical, if not impossible.

If nothing else, I'll try it tonight and let you know.

Thanks!
[Fascinate Android Development] Snyperx:
I just flashed 1.1 and noticed something odd. I used voltage control to set the scheduler to bfq and not to go aboe 1200MHz. I also selected 200,400,600,800,1000, and 1200 for the speeds to use. When I use Android System Info to look at the CPU usage it is showing 100MHz still being used even though I do not have that checked in voltage control. Any ideas as to why that might be? I have applied the settings and rebooted.
[Fascinate Android Development] ssewk2x:
Yes, there is a bug in the way the active states are filtered out. In general, to make it happen, you must disable the lowest frequency you previously had active. If you do that, then you will see that it will drop to 100Mhz. I'm pretty sure there's a routine or two that's looking for the next available step down, and when it doesn't find it, it just takes the lowest frequency in the table without checking to see if it's enabled or not.

I've been poking at the code today, and I think I have an idea why this is happening (sorry, Nemesis2all, the fix I thought I had this morning didn't work). I'll be coding and testing tomorrow morning, and if it works, I'll pass it on to Nemesis2all so he can review it and maybe include it in his next update. That is, unless he beats me to it, lol!
[Fascinate Android Development] nemesis2all:
It is alright. No rush. Today I will probably work on some edify scripts for our su zip and roms. Also maybe try to get out a kernel for cm7 if jt gets around to posting a cleaned up initramfs for it.
[Fascinate Android Development] bmangia1:
BLN support

First, this latest release is running great for me. Actually hitting 1400 (so far)stable now. Very smooth. Really great work and thank you!!

But....I noticed BLN support doesn't seem working?? BLN Control app says the phone is not (officially) supported. I was wondering if anyone else has noticed this? I ask because the OP noted the inclusion of BLN. Not a huge issue just trying to sort out why...
[Fascinate Android Development] Chewy1576:
BLN Control is working fine for me.
[Fascinate Android Development] bmangia1:
K. Thanks. Had a feeling it might be unrelated and unique to me. Now to figure out why...
[Fascinate Android Development] Chewy1576:
The last few times I have installed a new kernel I had to deactivate BLN, restart, then activate it again to get it working.
[Fascinate Android Development] bmangia1:
Yeah, I decided to re-flash the kernel, in recovery this time instead of through SGS, and now BLN is back. Shoulda just went there from the get go I guess. :rolleyes:

Thanks for the advice...

In my case I couldn't do anything at all with BLN cause it was on an "unsupprted" device as far as the app was concerned.
[Fascinate Android Development] Daswolven:
Loving this so far. I'm more concerned with battery life, so I've been running bfq through 900 at 50 across the board. Seems great, only one freeze so far, unsure of the problem.

Looking forward to calibrating to gauge conservation with the extra steps. :)

Great job man.
[Fascinate Android Development] Daswolven:
Too lazy to edit, but I had to revert to Jt's latest kernel. I had three calls mute on me with no indication. One I had to disengage and call back. I work from my phone, so this is a significant issue for me, but I will keep an eye on this.
[Fascinate Android Development] ssewk2x:
I found my phone is a lot more stable with my oc and uv settings if I use the cfq scheduler. It for sure does not like the sio one.

Also, Nemesis2all, check your PM. I have something for you :)
[Fascinate Android Development] Chewy1576:
It plays nicely with the OTA ED01 too. First thing I did after updating was rooted, flashed CWM, and the OTB kernel. Works great!
[Fascinate Android Development] deaffob:
Use Blinky instead
[Fascinate Android Development] stephenj37826:
Nemesis2all,

I have a question on each step does the gpu have a seperate clock speed or is it dependent on the cpu speed?
[Fascinate Android Development] nemesis2all:
GPU speed is dependent on bus speed and divider, so gpu speed changes slightly at different frequency steps.
[Fascinate Android Development] egorzilla:
This kernel rocks the house thank you so much :D!!!!

So I wasn't aware of that Android System Info app so thanks for that :D.

I noticed while sleeping it was running at 100mhz which was about 80% of the time. So since it sits there so much I did have that set at -100uv I decided to try running it even lower I mean why does 100mhz need so much juice anyways, its not like I need it balls out while its sleeping. So I set it to -150uv and have been running it there for about 6 hours with no problems.

100 -150uv

200-400 -100uv

600-1000 -75uv

1150-1200 -50uv

1300 -75uv

So far everything is stable and running awesome!

Not that these settings will work awesome for anyone else so I would say use caution.
[Fascinate Android Development] stephenj37826:
I see..... I am so close to running 1500 at 1375mv. It will linpack perform all tests in setcpu and does the stress test fine. The problem is 3d graphics. I get 20.9 to 21+ on linpack but it won't finish quadrant. Freezes on the 3d stuff. i really think its the gpu could be me though lol.
[Fascinate Android Development] nemesis2all:
Patch applied. Will test it out and if all goes well will update tomorrow or day after. I appreciate your help. Thank you so much.
[Fascinate Android Development] Sgtmack:
Well, my phone doesn't like 1300. I have been running 1200 at 1275mv for a couple of hours without a hiccup. Any lower voltage or higher speed and it freezes in Quadrant. But it runs smooth, so I'll keep it at 1000 and enjoy the under volted battery life.
[Fascinate Android Development] suppliesidejesus:
My phone keeps freezing while asleep, it's done it twice today now. I've wiped cache and backed off my uv settings to -25mv to see if that helps, otherwise I'm just at a complete loss as to what could be causing this.

ED01 de-bloated is the ROM I'm running.
[Fascinate Android Development] scarmon25:
FWIW. Mine was doing same thing until I updated to 1.1 and flashed that patch and disabled the 100 mhz setting. Hasn't done it since.
[Fascinate Android Development] egorzilla:
I upped my 200mhz to -125, and so far so good its been about 3 hours now with no lockups or freezing and no issues with sleep. Here is what I am currently running.

Evil Fascination 3.3.2 with all the extra's except facebook :).

1.0_420 of the kernel.

100mhz -150uv

200mhz -125uv

400mhz -100uv

600mhz-1000mhz -75uv

1120mhz-1200mhz -50uv

1300mhz -75uv

running the cfq scheduler

I also have unselected 600mhz 900mhz and 1120mhz

though 600mhz is showing 0.71% usage weird. and 1120mhz is showing 0.01% usage.
[Fascinate Android Development] suppliesidejesus:
I am already on 1.1 and I never use the 100 MHz setting, lol.

Looks like my next step is to try the patch...whatever that is.
[Fascinate Android Development] scarmon25:
This is the patch I was reffering too.
[Fascinate Android Development] suppliesidejesus:
Found it a few pages back, thanks dude!
[Fascinate Android Development] CC268:
Currently been unplugged for 31 hours and at 46%! Awesome kernel and great battery life using Tapouts recommended voltage settings for 1.3 GHz
[Fascinate Android Development] scarmon25:
No prob. I hope that helps.
[Fascinate Android Development] ssewk2x:
No problem, man! I'm glad to finally be able to do something useful around here :)
[Fascinate Android Development] Neuman.Tim:
Any word on an edify version of that patch?

[xda premium]

SCH-I500 - EC10-EC01/Nemesis 1.3ghz OTB-Reloaded/Voodoo/Crysis Revolution/Zeam Launcher
[Fascinate Android Development] nemesis2all:
I am testing with changes to kernel that will make that script not needed. If testing goes alright new kernel will be out later. So not too worried about switching that script to edify.
[Fascinate Android Development] Neuman.Tim:
Awesome. Also when the new kernel us available will we have to set voltage control's params again or will they have been saved?

[xda premium]

SCH-I500 - EC10-EC01/Nemesis 1.3ghz OTB-Reloaded/Voodoo/Crysis Revolution/Zeam Launcher
[Fascinate Android Development] nemesis2all:
If you don't wipe settings should be saved. Probably be a good idea when it does boot to go back in and save settings at boot again tho. Also for those running that script it will probably be best for them to remove it when flashing new kernel.
[Fascinate Android Development] Neuman.Tim:
Thanks nemesis

[xda premium]

SCH-I500 - EC10-EC01/Nemesis 1.3ghz OTB-Reloaded/Voodoo/Crysis Revolution/Zeam Launcher
[Fascinate Android Development] ssewk2x:
Yeah that patch was just a hack. The new kernel will be the real fix, so you will definitely want to undo the hack once the new kernel is out.
[Fascinate Android Development] scarmon25:
Just curious, and no rush to answer. The script you said that would need to be removed I'm assuming is the one done by Ssewk2x. How would one go about removing that script.
[Fascinate Android Development] ssewk2x:
The hack is in /etc/init.d/S_cpu_hax. When/if nemesis2all releases the kernel with my fixes, you'll want to delete that file.

If I'm feeling particularly motivated, maybe I'll make an "undo_ssewk2x_hack.zip" file that you can apply in cwm to get rid of it.
[Fascinate Android Development] scarmon25:
That's what I was looking for. The path. Thanks man
[Fascinate Android Development] suppliesidejesus:
Won't wiping cache also remove the script since it is an init.d script?
[Fascinate Android Development] scarmon25:
I noticed there's another file in that folder too. Looks like the settings from the voltage control app. I just wiped cache through cwm and both files are still there so I don't know. Unless I did something wrong which is entirely possible.

Edit. No problem with deleting them through RE just throught I would see if wilding cash cleared them.
[Fascinate Android Development] justinjbaron:
I read this entire thread over the past couple days but don't seem to see the answer to this question. Apologize if i missed it. If if use this kernel and either A) don't install voltage control or B) install it but leave all settings to default -- am I running at stock voltages and cpu stepping settings, or does this kernel have inherent defaults that are different from stock?

Thanks!
[Fascinate Android Development] ssewk2x:
/etc is a symlink to /system/etc, so probably not. Flashing a new rom that formats /system would do it, though (talk about overkill)! The other file you see in there, if it's called S_volt_scheduler, then that's the "saved bootup settings" from the voltage control app.
[Fascinate Android Development] cwingard:
New to forums here, I have to thank Nemesis. I am at 1.4ghz 100% stable and I couldn't ask for more, though at least 1.5 is likely achievable with some tuning.

I have the following steps and voltages enabled, cfq scheduler, 1400mhz max:

200 - 875mV

600 - 1150mV

1000 - 1250mV

1400 - 1350mV

So far, at 1500mhz, 1350-1375mV has worked best for me, but I haven't seen 100% stability yet. Thanks again, Nemesis!
[Fascinate Android Development] suppliesidejesus:
I've still been having random shut down while asleep issues even with the dirty hax patch. I'm trying the bfq i/o scheduler instead to see if that stops my phone from being a dirty whore, lol. Will let you know.

EDIT: Nope, did it again. I suppose I'll try another cache wipe, I hope that's what the issue is.

EDIT EDIT: Looks like I can reproduce the issue very easily. All I have to do is plug in the phone when the screen is off. I will try all stock voltage settings and see if the problem can be reproduced that way as well.

EDIT EDIT EDIT: Yep, confirmed. Stock voltage, no OC, if I plug my phone into USB when the phone is in a sleeping state, the phone will lock up and power off. I will see if the issue occurs if I plug the phone in from a waking state. In the past, I have been able to put the phone to sleep and wake it if it is already plugged into USB. Unfortunately, I have not been able to get any logcats of this. Logcat stays at waiting for device when I try to capture something.

EDIT AGAIN: I thought I figured out the issue, but I apparently did not. Thought it had to do with the Stay Awake option, but no such luck.

ONE MORE EDIT: Well, it only happens when the screen is off and I plug in USB. It does it every time though. If the screen is on, no problems, and I don't think it does it if plugged into just power. Again, I have no logs to give you since adb logcat won't capture anything. No idea if this is a ROM issue or a kernel issue.

LAST EDIT: It has to be a kernel issue. I flashed imnuts' latest kernel on here, and I cannot reproduce the freeze, no matter the conditions.

Another note, I noticed that imnuts kernel lowest speed is 100 MHz, so it stands to reason that 100 MHz shouldn't cause problems for anyone on the OTB kernel. Just a thought.

Sorry I can't be more helpful with any logs. :(
[Fascinate Android Development] ssewk2x:
Once the baby lets me, I'll try to see if this happens with my kernel fix.

I did find an issue where, if clock speed is decreasing, the code could potentially access an invalid memory location. It seemed like it would be more random than what you're seeing, but who knows? I'll post again soon and let you know.

Happy easter ;)
[Fascinate Android Development] suppliesidejesus:
Kewlness. At least there is SOMETHING that could be causing what I am seeing, lol. I am SUPER bored at work for another 3 and a half hours. If you want, you can hit me up on IRC, it's in my signature.

Happy Easter to you as well!
[Fascinate Android Development] krispuniq:
M having not so good battery life using this kernel on evil rom.. I observe that in spare parts android system is topping the list of applications using partial wake lock... How to fix this? No theme used on this setup... Plz help