yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] scarmon25:
I use cf bench for benchmarks and lindpack for cpu benches. And yes we are talking about different versions. There is a newer version of voltage control on the market :). As far as undervolt. This is what I have found by trial and error

Too much on low end clocks normally effects things like keyboards and such. Example would be a lag in keypress response and may lockup and require reboot.

Too much on high end can causs issues with downloads and cpu heavy tasks. Example downloading a large file may lock up the phone or cause it to freeze for a minute.

As for the unstable boot settings. I forgot about the option in cwm to remove those. So yes in the event that happpens you can just wipe the voltage settings in cwm. :)

Tap-a-Talked from my Mesmerize
[Fascinate Android Development] Syndacate:
Gotcha, thanks.

Definitely taking a hit in the SD card I/O with the OEM SD card, but blah, not about to run right out and buy a faster class..

Running -75 across the board on 200-1200, I'm getting:

CF-Bench:

Native: 4367

Java: 1415

Overall: 2595

Linpack:

ST: 20.201 MFLOPS, 4.15s, Norm Res 5.68, Precision: 2.22e-16

MT: 18.576 MFLOPS, 9.08s, Norm Res: 3.24, Precision: 2.22e-16

AnTuTu (all):

Total Score: 3163

I didn't expect it to be spectacular, but it seems to be holding its own in most cases, like I don't expect the SD card to be up there, same with RAM, but the 3D graphics are close to the Galaxy II, and the 2D graphics are better, but the FP...what the hell? The FP is crap. Why? Do the later gens have a separate FP unit or something?

The "scores" don't mean a lot to me :-\ Just numbers, hard to compare, it seems.
[Fascinate Android Development] scarmon25:
Honestly I'm not real sure what the FP is. :) I just go on how it performs in everyday situations to determine a difference or not. :)

Tap-a-Talked from my Mesmerize
[Fascinate Android Development] Syndacate:
FP = Floating Point

Those are data types which represent decimal values, such as the common "float" or "double" types in C, C++, Java, C#, VB, etc.

Floating point calculations take many more cycles (especially when it comes to multiplication/division) than standard integer (no decimal) arithmetic. Some systems have a separate floating point unit, which is dedicated, designed, and architected to do arithmetic on floating point values. Graphics cards are a good example of this, all the cores on the GPU are heavily designed to do floating point arithmetic, except it's done in a cluster form (ie. a couple hundred cores do all the work) instead of 1 or 2 "general" CPU's. All graphics is at the core is a bunch of floating point calculations, so that's why intense graphics can't be done well by an integrated graphics card.
[Fascinate Android Development] scarmon25:
Good info. Thanks for that. I learned me something new :)

Tap-a-Talked from my Mesmerize
[Fascinate Android Development] exzacklyright:
Anyone care to upload 1.6 to there drop box public? I can't download from media fire

Sent from E.T.
[Fascinate Android Development] scarmon25:
Here ya go. http://db.tt/m5GWdLX

Tap-a-Talked from my Mesmerize
[Fascinate Android Development] exzacklyright:
You sure that's the right file? Says tw_v1

Sent from E.T.
[Fascinate Android Development] scarmon25:
The one in my dropbox says tw v1.6. File name might be getting cut off but its otb v1.6. Same one I'm running

Tap-a-Talked from my Mesmerize
[Fascinate Android Development] scarmon25:
I see what ya mean. I just downloaded it too from my own link. That's wild cause its not labeled that way in the dropbox

Tap-a-Talked from my Mesmerize
[Fascinate Android Development] exzacklyright:
Thanks

Sent from E.T.
[Fascinate Android Development] scarmon25:
No prob. Gonna have to look into that though. :)

Tap-a-Talked from my Mesmerize
[Fascinate Android Development] Syndacate:
Hrm, yesterday I got ridiculous usage. After 20 hours (mostly deep sleep, moderate usage for e-mail/txt, 20m phone conversation) I was only down to 40% battery!!

This was after pulling -75mV from 200-1.2.

Fast forward to today:

- 1.5 hours, down to 78%

- Pressing back button is giving me the menu like crazy

Arggg, what's going on??
[Fascinate Android Development] scarmon25:
That's wild. Sounds like the launcher got closed. That happens to me and I just hit the home key. As far as battery. Honestly I have to give mine a day or two after flashing and adjusting voltage settings to see any results. But with so many things that come into play with battery life it generaly isn't my top priority. Might wanna make sure you voltage settings stuck. If that is so. Then calibrating the battery should straighten it out. At least it does for me.

Tap-a-Talked from my Mesmerize
[Fascinate Android Development] beray5:
Too much under volting.

Too much WILL cause shorts, the shorts could be hard or just lightly, producing varied symptoms. Reduce under volting by 25mV, shut down the phone if possible and pull out the battery for 5 minutes to clear the shorts.

Typically the shorts cause transistor latching conditions and could only be clear by complete power removal to the phone, reseting/rebooting alone is not good enough to do so.
[Fascinate Android Development] scarmon25:
That's some good info to have. Thanks.

Tap-a-Talked from my Mesmerize
[Fascinate Android Development] beray5:
Golden rule of thumb.

When undervolting low voltage/power devices causing operational problems, always completely remove power from the devices to clear out and reset transistor errors.

Transistor latching problems is "persistent" even when already restored to original hardware setting condition hence the phrase "latching", the latching errors would definitely survive through phone wipes, resetting, and rebooting without complete power removal.
[Fascinate Android Development] scarmon25:
That's cool. I personally don't have any issues right now but in the future I'm deffinately gonna remember that. Makes sense when ya think about it.

Tap-a-Talked from my Mesmerize
[Fascinate Android Development] Syndacate:
That was a no-brainer. I didn't set it to apply settings at boot, just a "for now" as a test.

I restarted the phone this morning because the ringer was retardedly low when it rang and when I was on it I could barely hear the person on the other end...so that killed the voltage steps which RAPED my battery. Woops :).

Though the volume and menu malfunctions are still unanswered :(.

What do you mean by "latching conditions" - if it has to do with variance in transistor proximity it should be the same every part of the circuit is executed - even at a given humidity, temperature, elevation, etc. Undervolting shouldn't cause such intermittent problems. It should run like ass regardless. This is the first problem I've had in a week :-\.

Yeah, I removed the battery for a few minutes. Not much I can do about the physical architecture. If they're too close or too far away and it skews the logic results, it is what it is.

It's obviously a common problem with the circuit involved in relaying the interrupts for the soft keys, (the symptom seems to be pretty similar across many peoples' phones), as sucky as it is, if it happens once a week, then it doesn't warrant a voltage increase - especially since my battery voltage has been awesome - a bit better than what I got on Eclair (sad to say).

I wonder if anybody caught the error in ADB, if it's a pure signal error in the HW or if it's an issue handling it. If it's an issue where it's coming up as an unrecognized keypress, and it's always the same result (ie. 2's compliment -1 or something), it's decently easy to stick a hatck/fix in the keypress queue in the kernel to make it a menu button click. Use some SW to fix some HW :).
[Fascinate Android Development] beray5:
My best guess is the shorts caused huge abrupt increase in temperature besides excess power usage.

Which in turns creating far more false capacitive touch screen triggers, as well as the phone becoming much more sensitive to conductive noise false triggers if the USB charge cable was connected.
[Fascinate Android Development] Syndacate:
It's definitely possible. Though it only was acting up that once, out of a good solid week now :-\. Environment has been pretty much the same, it's hard to tell.

Not much you can do but increase the voltage, but I guess if the problem is so rare, with the battery life I've been getting pulling 75 across the board, I'm just not sure I can justify it putting it up.

It's definitely annoying that the capacitive buttons seem to be the major thing that's affected - like it's not a global (whole phone) issue. Not like you're getting bad touches on the screen or anything.

Though I think there's a little more to it, because sometimes when it flips out (from what I've both seen and heard), the haptic feedback blips 3x quick, in a very uniform way. Almost like an error or something, it doesn't reflect a random electrical signal, you know?

On the flip side it's so rare and random I doubt anybody has a logcat of it...and even if they did, it probably won't show anything out of the ordinary of the HW is fuxing up :-\.
[Fascinate Android Development] Syndacate:
Okay, so I found out when the button malfunction happens, it's quite simple: Low battery power. Not sure why, but that's when.

It happened again today - I didn't sleep last night so I never charged it so it started at like 40% today, then just now it was like "I NEED this download from the market" and I was like "no, stop, you don't have the power to keep the modem on that long (bad reception here) or the proc high for that long!" and it was like "screw you, I need this app" - So at like 1200Mhz with the 3G going full blast (going nowhere) it drained the battery from like 15 or 18% (I forgot) to about 10% in like 5-10m.

At first, at the higher percentage, it was just a hiccup every now and then when I hit the back button. By the time it hit 8%, the phone was barely usable. Seeing as I couldn't stop the market download I went into Voltage Control - knocked the max clock down to 200Mhz, set the only stage it's allowed to be in as 200Mhz, and dumped the undervolt at 200Mhz - hit apply for now. I was then able to stop the download, and the phone's running 100% smooth...slow, but smooth and peaceful.

Lesson learned: Check your battery if you have problems undervolting only intermittently, because that is DEFINITELY a large contributing factor. It goes ape **** sub 10% if you're having problems.

My voltage was -75mV across the board, NO problems (except one last weekend or something, but I have no idea what the battery level was) until I got into the lower battery powers. Hope that helps some people..definitely cleared up what the issue was for me.

Only thing I can think of is when the battery is low, the power output is lowered a bit, and to keep the current up for everything to get the power it needs, the voltage takes a hit (or vice versa).

Cheers :)

EDIT:

Yeah, when it was just about dead, reboot didn't fix ****, it was pwned. Battery ended up not making it back (damn CA traffic :(), but I got back, plugged it in, charged it for like an hour up to 45%, rebooted so it had the default settings (-75mV .2-1.2), and absolutely no problems. Def. has something to do with the battery being too low.
[Fascinate Android Development] dricacho:
So I flashed the SC 2.9.2 voodoo and this kernel to see if my phone will stop locking up. It still does, and it got worse. So I am now back to Blackhole 4.3 and the EC10 Voodoo(lagfix+sound)+BLN+UV+Misc tweaks kernel.
[Fascinate Android Development] M00NEY:
No thanks button on the xda app, so I just wanted to thank you for the awesome work.

Swyped on my Fascinate - please excuse any swypo's...
[Fascinate Android Development] kuronosan:
I'm sorry, Nem. I can't get my phone to stop doing some kind of Partial Wake Lock no matter which Kernel of yours I put on. Last night I went to bed and the battery was at 95%; this morning I wake up (5 hours later) and the battery is at 42%. That was after hard rebooting.
[Fascinate Android Development] minho422:
Usually my battery drops only 1~3% during the night, but it dropped 40% with this kernel. Also my phone was always hotter than usual, and a lot of crashes including wifi disconnections. Now I'm back to jt's EC10 kernel and it's all good
[Fascinate Android Development] nemesis2all:
New kernel with steps added testing in irc.
[Fascinate Android Development] exzacklyright:
new kernel as in OP updated?
[Fascinate Android Development] nemesis2all:
That is correct.
[Fascinate Android Development] bignew67:
The updated UBER kernel, is that UV -50 as well?
[Fascinate Android Development] TheSonicEmerald:
I'm assuming the new kernels are the OTB kernels?
[Fascinate Android Development] bigmike88:
Trying the uber now, not getting the death sleep with low profile settings in setcpu. Like the added steps too.

Sent from my SCH-I500
[Fascinate Android Development] nemesis2all:
Yes sir.

(plus 10 char)
[Fascinate Android Development] ssewk2x:
Great work! My phone and battery do really well with -50 kernels ... Not so much with -100 tho.

Any chance you could throw together a -50 mv version of today's kernel so I could try it out?

Rock on!
[Fascinate Android Development] nemesis2all:
Original post update with information about voltages and kernel.
[Fascinate Android Development] PeterGunz:
How long are you guys seeing on the reboot from recovery with the uber kernel? I'm on first boot and at about 15 minutes. No boot lock, just looping. Going to pull battery and try another reboot at the 20 minute mark.

Update: Pulled battery and it rebooted in a minute or two. Excited to drive this kernel.
[Fascinate Android Development] cpark_12:
Normally it takes about 5-10 minutes fort me on the first boot...
[Fascinate Android Development] cpark_12:
Okay...i flashed it and it took the normal good 5 minutes or so to boot, but everything seems good so far. I'll let you know if anything happens good or bad
[Fascinate Android Development] iTz Nicholas72:
Does this include Blinky 2.3?
[Fascinate Android Development] PeterGunz:
So far so awesome. Uber indeed. 2 hours and only problem was the camera acting up a little bit. Got wonky but still took the picture I needed.
[Fascinate Android Development] TheSonicEmerald:
My phone loves your OTB kernels :) Camera/camcorder are both a little unstable, but speed is awesome.
[Fascinate Android Development] DaleV:
I've been running this EnderstSpecial_ver.02 happily for the last few days but UBER?? I have so gotta try this.
[Fascinate Android Development] nemesis2all:
To those having issues with camera/camcorder can you test at stock speeds as well. If issues persist at stock speeds i will investigate to see if I changed something that affected it. Thanks.
[Fascinate Android Development] bwheelies:
Great job nemesis. 1300 seems like nothing for the phone.

Edit: looks like it's 1200 still. Still works better than v2 for my phone. Not sure if it is kernel related but anything requiring data seems to wait a bit and then download rapidly.

Camera is still glitchy at stock max. Also there is a clicking noise every 5 or ten seconds.
[Fascinate Android Development] bigmike88:
I've noticed the camera issues as well. Laggish and clicking noises. Doesn't do it when cpu scaling is set to performance 1200

Doesn't seem to do it at all when set to as low as 400 scaling performance either.

Sent from my SCH-I500
[Fascinate Android Development] kuronosan:
My sleep of death issue is gone with this Kernel, but I too am having the lagging camera problem.
[Fascinate Android Development] bizzshow26:
Yep the camera crashed at stock speeds but I don't care my phone flies with this kernel
[Fascinate Android Development] uslacson1:
OTB working flawlessly for me on DR4, taking for a test drive to compare battery life with previous OC1200, I was getting around 30hrs, will see how far this one can go.

Great work, thanks.
[Fascinate Android Development] ssewk2x:
Thanks, man! Running Uber right now, just tested the camera. It was a little weird when I first started it, but it stabilized quickly and worked fine.

Running conservative max 1200. This kernel looks pretty good for me - can't wait to try faster oc speeds. I bet this thing will crank at 1.6 ghz :-D
[Fascinate Android Development] uslacson1:
Both OC1200 and OTB works stable on my phone, battery use on OTB is at about 5% / hr while OC1200 is at 3% / hr.

I know that getting multiple steps working is a big step but without noticeable boost on performance and battery use with OTB i will stick with your OC1200 for now.

Waiting for your OTB UV OC1300..perhaps, better yet if possible an automatic CPU voltage regulator?? Just a noob idea.

Thanks again for the long hours of work that you put into this kernels.
[Fascinate Android Development] nemesis2all:
I do plan on eventually having steps up to 1.6 ghz but first I need to make sure stock clock is used at boot. I've been looking into it and I believe that the only way to accomplish it is a custom script in the initramfs.

I will try to figure out what is going on with the camera. I experienced the same clicking as well but had no issues taking pictures or recording video.
[Fascinate Android Development] cpark_12:
my camera is a little glitchy too. i can still take pics, but it doesn't focus. i can deal with it though
[Fascinate Android Development] suppliesidejesus:
Bluetooth will not pair or connect to previously paired devices with the OTB kernel.

Sent from my Samsung Fascinate
[Fascinate Android Development] BakaUnchi:
nemesis

my camera is all glitchy and freezes a lot on this but is fine on test5
[Fascinate Android Development] PeterGunz:
I was really enjoying the uber kernel, but I got locked while texting texting with go sms pro and streaming radio. I was going to keep testing it, but the phone was starting to feel really warm and I got worried.

Is it normal that it gets hot? Or is that the sign to shut the phone down?
[Fascinate Android Development] uslacson1:
Can the clock voltage settings / steps from Sir Gatez kernel work with OTB?

Found from this thread.

http://xdaforums.com/showthread.php?t=902136
[Fascinate Android Development] BakaUnchi:
Sooo even on test 5 camera locks up
[Fascinate Android Development] TheSonicEmerald:
The uber kernel is the coldest kernel I've ever used, and I'm on 1.2ghz, when normally I'm on 1ghz!. If your phone gets hot, its a sign that if you keep using it, its gonna burn your hand. No danger to the phone, but rather yourself. Unless you reach 100C.
[Fascinate Android Development] Mean Sixteen:
thought I would add one to the funky camera croud. Definitely acting strange and clicking just like the others reporting. Not a huge deal.

I will eagerly await updates as your OTB kernels were my best performing pre froyo.

I should add while my quadrants aren't through the roof (I know they dont matter anyway) MY PHONE FLIES ON THIS KERNEL. At least for the hour I have been playing with this one.

Keep up the great work!

Sent through mental telepathy
[Fascinate Android Development] PeterGunz:
Okay! I'm going to give it another shot tomorrow. Hopefully I don't get another lockup.
[Fascinate Android Development] DownRiver_Droid:
OTB kernel absolutely flies! No lockups like I had with the 100UV kernels.
[Fascinate Android Development] BeeDubs:
I'm confused. OTB is voodoo? It used to be non I believe.
[Fascinate Android Development] BeeDubs:
Has anyone who ran into issues tried decreasing Max clock in setcpu to 800?
[Fascinate Android Development] ssewk2x:
Confirmed on my device as well. :(
[Fascinate Android Development] saps:
It is voodoo now, it was voodoo on eclair as well
[Fascinate Android Development] mgrimmenator:
sorry if this has already been asked but can you make a -100mv undervolt version?
[Fascinate Android Development] saps:
I'm sure nemesis is working on under volting the lower steps some more, with a one size fits all kernel its tough to please everyone all the time
[Fascinate Android Development] Mubassmastajoe:
Using sc 2.9.2, OTB, and nitro honeycomb and she has only locked up once so far; while using gmaps, tunein radio (through jack), and texting (stock text). I'm not sure if that helps you at all, but she runs better than the original "special" as far as lock-ups go. Many thanks nemesis

Sent from my $600 occasional paperweight
[Fascinate Android Development] nsmal24:
BT Issues

+1 on BT issues. Just tried to pair my BT and it does not find any devices. I know it worked correctly on the EB01 stock kernel. I ran the stock EC10 kernel for awhile, but I'm not sure I ever tested BT on it. All using SC 2.x.x. Currently on SC 2.9.2.

Just fyi, not a big deal. Love this kernel though. Thank you for your hard work.
[Fascinate Android Development] Mean Sixteen:
+1 on Bluetooth

Here is what I did in case it helps...

Notification pulldown button failed to turn on Bluetooth. Went to settings and it worked from there.

Tried to pair with my car kit...failed.

Deleted car kit from devices.

Tried to scan for car kit so I could try and re-pair...failed to find any devices.

hope it helps.

Still love the kernel.

Sent through mental telepathy
[Fascinate Android Development] nickfury718:
Camera continually freezes for me on uberotb. I hear a physical clicking noise every time the screen freezes, which is every 5 seconds or so. chose to flash back to enderst. Everything worked on that for me except for swype (and even that's still usable). Pity though, otb was snappier and better on my battery.
[Fascinate Android Development] nemesis2all:
I am aware of camera and bt issues. I am currently working on rebuilding from ground using ec10 initramfs and source. It may take a while but there will be another release. Check my git for current progress.
[Fascinate Android Development] BakaUnchi:
:Dspank jew!
[Fascinate Android Development] akatcl:
Confirmed camera issue on my device too... Need details?

Also, phone just force- rebooted the first time I was typing this message and also wanted to mention that after re-wiping the davlik cache, it hung on the boot screen for 25' before I pulled the battery.

Other then that (and the blue tooth), I love the rom. Thanks to nemesis for his work; looking forward to the next update.
[Fascinate Android Development] allcity187:
I flash enderst oc 1200uv mhz last night and so far its been running good. I mostly keep my phone on 1000 mhz, but when I need more juice i bump it up to 1200. I notice my youtube app starts running quicker on 1200, the phone opens up apps real fast. I'm loving this kernal, i love having the choice of oc my cpu when I need it. Thanks nemesis.
[Fascinate Android Development] dricacho:
It's been 9 hours since I flashed the Uber OTB kernel, so far no lockups at all. <crossing fingers> I also have the laggy camera operation. It does take good pictures and the focus works. It takes about 4-5 seconds before the shutter goes after pressing the shutter button.
[Fascinate Android Development] dricacho:
Still going and no lockups. Impressive kernel!
[Fascinate Android Development] CrucialBT:
Locked up once during the last 4-5 days of use. Not bad at all.

My phone runs at 800mhz most of the time when I have a live wallpaper on. But when I use a static one the phone stays nice and low at 100mhz. The difference in battery life is like night and day with and without a live wallpaper running on this kernel. I haven't seen that much fluctuation on any other kernel.

Not a complaint mind you, just an observation.
[Fascinate Android Development] nemesis2all:
New kernel added to main page. Camera fixed and I believe bluetooth fixed as well.
[Fascinate Android Development] bwheelies:
My quadrant score is only 1054 with the new test. Does this mean ext4 is not enabled?

Can't say I am a fan of cwm3 as nothing flashes. I know we will eventually use it but why switch now?

Edit: on demand at 1.3 locks up while watching videos. Performance and conservative are good though.

Hope to see you crank it up more! Good work.