yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] misterblonde:
anarkia i have problem with the donate bottom in the first post O.o

edit. all ok :)
[Samsung Galaxy Nexus] Hetalk:
Use the donate button under anarkia1976's ID on the 1st post (or any of his posts). That works. :good:
[Samsung Galaxy Nexus] stevensoaj:
szucsgf, I have a question for you. Since it is kernel related, I'm going to ask here instead of a PM, but if it becomes a long conversation we can move it there. And before I ask my question, I have read your SmartReflex and Undervolting guide, as well as your Efficient Underclocking guide. Very informative. :good:

Since Stefano implemented Min SR Calibrated Voltages in v70, it has brought something to my attention.

I have changed the MPU Min Calibrated Voltage to 780mV, because it undervolts all frequencies from 180Mhz - 525Mhz down to 790mV. I used to undervolt 700Mhz down to 875mV, before we could change the Min SR Calibrated Voltage. According to Trickster, it always ran at 875mV (in other words, SR never calibrated it lower than the max that I manually set). So when I was undervolting v70, I thought instead of doing 875mV, I'll just bring it down to 900mV (what I want the max voltage for that frequency to be), and let SR decide the best voltage to run at as long as it's below 900mV. As soon as I clicked apply, my phone froze (due to too low of a voltage obviously).

So here's the question. I KNOW 700Mhz ran stable at 875mV in previous builds. If that's a stable voltage, why didn't SR calibrate to that? My theory is that when you change the Min SR Calibrated Voltage, it changes the voltage that SR chooses, even if it could have used the same voltage.

So to test this theory, I started playing with CORE voltages. First, I changed Core Voltage 3 to 880mV, but I kept the CORE Min Calibrated Voltage at stock (830mV). I took note that SR Calibrated the voltage at 835mV. Then I changed the CORE Min Calibrated voltage to 800mV. After that change, SR Calibrated the voltage at 873mV. Wait....What? Why didn't SR keep it at 835mV, a voltage that it had previously determined to be stable and still falls within the new range of voltages?

Can you explain this behavior? You know, since you're the SR and Undervolting expert. :p

And for all people who read this, this post does NOT imply that the voltages Anarkia1976 coded into AK Kernel are unstable. My phone froze because I started playing with voltages. If you don't know what you're doing, please don't mess with them!
[Samsung Galaxy Nexus] szucsgf:
I wish I could help but I'm just learning how to use Min Calibrated Voltage myself. And what you describe is the opposite of what I would expect!

I didn't have the same experience as you when I tried to replicate it. I saw this for Core (Min Calibrated, Optimized):

850, 911

830, 886

800, 860

750, 835

Which is more reasonable, but you would expect the Optimized voltage to not change just because you changed the Min Calibrated voltage. It's almost as if SmartReflex takes your Min Calibrated voltage into consideration when deciding on the Optimized voltage.

I have noticed that the Optimized voltage is not consistent based on the selected Min Calibrated voltage. Here are my results for MPU (Min Calibrated, Optimized):

850, 830 (a)

830, 830

800, 810

750, 800 (c)

700, 810 (b)

Then when I changed Min Calibrated voltages step by step upwards:

750, 810 (c)

800, 810

830, 830

850, 830 (a)

There are 3 funny things I noticed here. (a) When I select Min Calibrated to be 850 the Optimized voltage shown is 830, below my Min Calibrated value! (b) Optimized voltage when Min Calibrated is 700 is 10mV higher than when Min Calibrated is 750. (c) The same Min Calibrated voltage won't always result in the same Optimized voltage.

WTF.

Thanks stevensoaj for bringing this up! I don't have any answers at the moment but if I learn something useful I'll certainly share.
[Samsung Galaxy Nexus] stevensoaj:
Okay, so I'm not just going crazy. SR is definitely in some way taking into account the Min Calibrated Voltage when it determines the optimized voltage. We both agree on that. I didn't expect you to get exactly the same results (every device is different), I just found it strange that SR raised the voltage when I lowered the min voltage. If other peoples devices do this also then it brings up something else that sounds a little ridiculous...

Some people are getting random reboots, and when they show Stefano the logcat, it shows that the problem lies with the voltages and he tells them to raise them. Someone suggested that he add Min Calibrated Voltages so that they could raise the minimum in order to avoid SR going below a certain level. If their devices behave in a similar manner to mine, maybe the solution would be to (haha) LOWER the min calibrated voltage, so that SR calibrates "problem frequencies" at a higher voltage, but still allows other frequencies access to lower voltages.

Like I said, sounds ridiculous, but who knows. It might help.
[Samsung Galaxy Nexus] Blackcrx:
I tried the min cal settings like you guys, here are my test values for core and iva. I didn't bother testing the MPU since I know it works from previous experience

Core

min - actual

830-886

800-860

775-848

750-848

IVA

min-actual

830-860

800-835

775-822

750-822

edit: these values were taken when I had 85% battery life remaining. I will try to do it again later when the battery is lower to see if the values change
[Samsung Galaxy Nexus] stevensoaj:
See? This is what I don't get. If SR worked like we thought it did, your actual Core voltage should have been 848mV for each of those different Min Core voltages, because it is the lowest "stable" voltage that is above the minimum that you set.

On your IVA voltages, it should have dropped to 822mV after you lowered your Min from 830mV to 800.

It doesn't appear to be working as intended, but if we can figure out a pattern, at least we will be able to predict it's behavior a little better. :good:
[Samsung Galaxy Nexus] szucsgf:
Yeah, I expected min calibrated voltage to act exactly as you describe. The only pattern I see so far is: changes in optimized voltage are highly correlated with changes in min calibrated voltages, but not perfectly correlated. Not too helpful.

For now I'm keeping all min calibrated voltages at 700 so SR theoretically can use the full range of options. That has my optimized voltages at:

Core 835

Iva 822

Mpu 800
[Samsung Galaxy Nexus] stevensoaj:
Mine still calibrates Core voltage lower with the Min set at 830 than it does with min at 700. Strange. :confused:

Just out of curiosity, what are your IVA voltage maxes at? Did you leave them at the stock values for v70?

ie

Voltage 1 1375

Voltage 2 1291

Voltage 3 1140

Voltage 4 950

Or did you lower them? I ask because for some reason on my device, IVA is ALWAYS at 949mV. It doesn't matter what I set IVA Min Calibrated voltage to or what I set the maximum voltages to. Even if the maximum is below 949mV, it always runs at 949mV.
[Samsung Galaxy Nexus] peikojose:
Let it dry well and it will be working again.

---------- Post added at 02:29 PM ---------- Previous post was at 02:28 PM ----------

I am having good idle drain with v70 but WiFi drop... Every 5 minutes... I'll have to go back to v44..

Best regards.
[Samsung Galaxy Nexus] Blackcrx:
I did some more playing with the voltages. I think there is a buffer from min cal to actual voltage. For me the lowest possible core voltage was 848 with min cal set to 750. What I did was slowly increment my min cal voltage until the actual voltage changed.

I was able to creep up to min cal of 795 and still remain at 848. But once I got to 800 it jumped to 860

I did the same for IVA and same result. min cal 795 was still getting 822. min cal at 800 and it jumps to 835

So with that said, I think the buffer between min cal for core is 50mv and IVA is 25mv

To further confirm this I did some more voltage testing now with the 50 and 25 buffer

I set my core min to 820, actual went to 873. Set my core min to 825, actual went to 886

I set my IVA min to 820, actual went to 848. Set my IVA min to 825, actual went to 860

So as mentioned for me, I think min cal still has a buffer. Core buffer being roughly 50mv and IVA buffer being roughly 25mv

For now I have all (core, IVA, MPU) min cal set to 795 since going any lower will not change actual value. I am also scared that if I were to set lower than 795 that when my battery drains down that it might get a SOD.

I recall reading a long time ago back in the nexus s days that undervolting is truly tested when your battery is close to or below 20% because that is when voltage and current starts to dip at its greatest

---------- Post added at 12:06 PM ---------- Previous post was at 12:03 PM ----------

Here are my settings, stolen from Franco r372 since he hardcoded them (disabled smart reflex) a few releases ago

Core: 1175-1075-975

IVA: 1250-1150-1050-950

Been running these for a while now with no freezes or issues... try at your own risk
[Samsung Galaxy Nexus] frenchy714:
Just wanted to say thanks again for implementing the SR Min. Calibrated Voltage setting, I've been running v70 for hours reboot free! Not to mention v70 with Carbon 4-9 nightly is straight GANGSTER lol :thumbup:! Keep up the great work Anarkia!!

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] TheMysteriousOne:
Is all this UV really worth it? I mean, for barely a few mins of battery life.
[Samsung Galaxy Nexus] szucsgf:
Generally I agree with you. I don't bother undervolting myself, I leave that up to SmartReflex. Right now we're just trying to learn how this new Min Calibrated Voltage feature works.
[Samsung Galaxy Nexus] stevensoaj:
I agree with you that there seems to be a buffer, but I think that (a) the buffer varies from device to device or (b) Min Calibrated Voltage is not functioning in a predictable enough manner for us to determine the size of the buffer.

Here's why

(a) With CORE Min voltage set to 830mV, my actual voltage was 835mV, so a 5mV buffer. That's a big difference from your 50mV buffer.

(b) If I lower CORE Min Voltage to anything below 830mV, my CORE voltage goes up to 873mV. So that would imply a varying buffer, which isn't consistent. Also, my IVA voltage stays at 949mV regardless of what my IVA Min Voltage is set at. Even if I set the Min voltage higher than 949mV, like it's ignoring the value I set completely and just doing it's own sh**.

I agree with you also, I just would like to understand how SR works.
[Samsung Galaxy Nexus] Blackcrx:
Personally I would say it is not worth it. But min cal is something new to play with so why not. Haha

I have also read that when udnervolting it can sometimes cause your phone to run slower. I have proven this on my nexus s

while running normal voltage at 1Ghz, it was faster than 1.2Ghhz undervoltaged

---------- Post added at 12:26 PM ---------- Previous post was at 12:15 PM ----------

I think we need more ppl to test this min cal with us. With just 3 ppl reporting values it is to hard to make an accurate comment

In theory smart reflex should report the same values for the masses but not 100% because it is device dependent
[Samsung Galaxy Nexus] galakanokis:
What are you guys using to monitor the actually voltages?
[Samsung Galaxy Nexus] ak:
I want to suggest to try Westwood for people with WiFi drops ... And report here if resolved .... :thumbup:
[Samsung Galaxy Nexus] Blackcrx:
I'm using trickster mod
[Samsung Galaxy Nexus] szucsgf:
I like how we all answered in the same way.

TricksterMod. You can set your voltage values and toggle SmartReflex in the "Specific" tab, but if Smartreflex is on you can see what voltages it has chosen at the very bottom of the "Info" tab.
[Samsung Galaxy Nexus] Blackcrx:
I have always used westwood. I had wifi drops with previous builds like 44 but no drops with current 70.

70 runs like a champ!!

Only thing I have noticed is that now with Dynamic FYNC my battery stats are intermittently incorrect. Instead of showing battery drain from 100% battery it sometimes shows at 90% or random battery life.
[Samsung Galaxy Nexus] jasondowning85:
I fully submerged my phone into a jacuzzi before. Camera stopped working for 3 weeks, screen was jacked for a bit... BUT now all is normal lol and it works perfectly. Other than my insane battery drain. I don't know if it's just a bad battery or I jacked some of the components.

Just a couple months ago, it fell out of my pocket while snowboarding too. Sat on the mountain in the snow for about 30 minutes and somehow it still works. (wasn't working properly for a bit... phone would say it was charging while unplugged among other problems) but now all is good again.
[Samsung Galaxy Nexus] Blackcrx:
Ya, I noticed that too. Basically we just want something to do or play with. Typical boys and toys.

You know what they say, if you don't play, make mistakes, **** **** up... then you will never learn. Haha
[Samsung Galaxy Nexus] stevensoaj:
Hmm. All of a sudden my IVA voltage started changing. Don't know what's up with that. Now I get 797mV actual with a Min voltage of 700mv.
[Samsung Galaxy Nexus] Blackcrx:
I must have missed this post.

I had a friend with the same problem. What I did was open the nexus and clean the bottom dock connector with contact cleaner. Hit it with some canned/compressed air to make sure it is dry. reconnect the connector.. fixed
[Samsung Galaxy Nexus] galakanokis:
OK. Just curious as to the monitoring.

I just cannot get my voltages to change all that much. I run a min 350 for MPU set at 800mV with min set to 800 as well and I report back at 840mV.. I guess that's as low as mine will go.
[Samsung Galaxy Nexus] Blackcrx:
maybe you had something running in the background while you were doing your voltages tests.

I had all apps closed with only trickster open

again, from what I understand (correct me if I am wrong) smart reflex varies between devices.

Maybe your kernel just hasn't settled in yet so to speak.

Which would kind of make sense since ppl always report 2-3 charges before you can judge battery life. Most ppl says it has to do with the "fuel gauge" calibrating, but maybe it has to do with smart reflex settling and adapting voltage to hardware
[Samsung Galaxy Nexus] relax24:
I hope mine does the same. It's currently charging fine, but it's still pot luck whether when I plug it in, it wants to charge or not. Takes a few attempts, but certainly better than this morning when it wouldn't charge full stop, and only charge now and then when off.

I bought the usb charge port flex cable and screwdriver just incase I do have to replace it (only cost £6), but that's last resort, and I'm worried I'll mess it up!

---------- Post added at 08:52 PM ---------- Previous post was at 08:51 PM ----------

I did a cheat way of sticking it in rice, then got a saftey pin and pushed the connector upwards, and cleaned the port of dust using it. Didn't open the case however. As I said above, it's last resort opening up the phone!
[Samsung Galaxy Nexus] Blackcrx:
We all mentioned that there is a buffer between min cal and actual voltage. You can try setting your min cal to 775 or even 750 and see if your actual voltage changes
[Samsung Galaxy Nexus] relax24:
Ignore, I hadn't saved my settings in trickster. Testing with westwood now.
[Samsung Galaxy Nexus] Blackcrx:
opening the phone takes all of 30 seconds. May take longer on your first try but it is very simple

here is a step by step guide

http://www.ifixit.com/Teardown/Samsung+Galaxy+Nexus+Teardown/7182/1
[Samsung Galaxy Nexus] relax24:
It's the detaching of the volume rockers, and power buttons that scares me. I know with my butter fingers I'll rip something!. Although on the two different guides I've seen, one doesn't require them to be removed to acess the usb charge cable, however the ifixit one does
[Samsung Galaxy Nexus] parthipanramesh:
Diamond v70 is awesome!! It's blazing fast. But my battery percentage is incorrect. Sometimes it drops from 90 to 40 and after a while back to 75. Really weird. :D
[Samsung Galaxy Nexus] irminsul:
Westwood doesn't fix it, tried Franco and Lean kernel with Westwood, but with the drops.

Tried static IP, same problem.

Then tried WiFi optimization off + WiFi high performance on, problem gone. After that just with WiFi opt off and still no problems occurred. Saying it is being fixed is maybe to early but I'm getting somewhere, thanks.

No WiFi at my girlfriend's, so can't try an overnight drain test for the time being.

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] Az Biker:
Crack flashers + competitors = minute saving voltage testing... And I totally 'get it'... :D

Atom v11 + AK Diamond Series = Gyrannosaurus Nex
[Samsung Galaxy Nexus] Blackcrx:
nope. no need to remove upper logic board

if i remember correctly you need to remove and reseat the connector just left of the garbage symbol with the large white arrow

http://d3nevzfk7ii3be.cloudfront.net/igi/kQFOSBXfqBZ2CrkZ.large

also use a tooth brush and contact cleaner to clean the usb port connector. the part that is surface mounted to the board. I recall finding corrosion on that area also.

plus you can also tray a known good battery too
[Samsung Galaxy Nexus] sruel3216:
I always use Westwood. Maybe that's why i never had problems
[Samsung Galaxy Nexus] relax24:
Ah great, I'll give it a go when the replacement part arrives. Thanks
[Samsung Galaxy Nexus] LauraSakura:
Thanks so much! I haven't had a single SoD since making that voltage tweak! It also seemed to resolve a bit of lag.
[Samsung Galaxy Nexus] galakanokis:
I'm an idiot! I keep forgetting to apply the settings in trickster. Normally I use Franco's app but I wanted the monitor. Appears to be working now.
[Samsung Galaxy Nexus] buggerthis:
My phone seems to behave the same way as Blackcrx, just the actual voltages are slightly different. The lowest actual voltages it will go to are 873 for core and 810 for iva.

The actual core voltage remains 873 for all min calibrated values till 820. It jumps to 886 at min cal 825.

The actual iva remains 810 till min cal 780 and jumps to 822 at 785.

That seems like Blackcrx was right about the 50 and 25mv buffer, or atleast it exists on more than one phone
[Samsung Galaxy Nexus] Blackcrx:
I haven't used Franco paid app in a whole but j thought they had a voltage monitor section too?
[Samsung Galaxy Nexus] stevensoaj:
It used to, but he took the voltage monitor part out shortly after he hardcoded the voltages. Not sure why.
[Samsung Galaxy Nexus] :
Really good battery life for me on v70. I have everything syncing and have been downloading stuff from the market.
[Samsung Galaxy Nexus] stevensoaj:
I still don't get why mine calibrates CORE to 835mV when Min is 830, and 873mV when Min is lower than 830. Maybe my phone is just "special." :p

BUT, since my IVA voltage decided to play nicely finally, I can confirm that there is EXACTLY a 25mV buffer for IVA on my device as well. Woohoo!

I set IVA min to 772 and actual was 797, with min at 773, actual was 810. So that confirms that theory. :highfive:

For MPU, I'm getting a 10mV buffer. You guys?

For CORE, I can't tell because mine is wierd.
[Samsung Galaxy Nexus] buggerthis:
So this is really weird. I rebooted my phone to get back to ak stock voltages, and now my iva actual is staying at 949. I changed every setting I normally change one by one to see what would affect it but nothing did-it's still 949. Very strange.
[Samsung Galaxy Nexus] Blackcrx:
10mv buffer sounds right to me. Lowest I can get us 810.

If I set min Cal to 805 actual goes to 820

Min Cal 810 actual goes to 820
[Samsung Galaxy Nexus] buggerthis:
Yup it's a 10mv buffer here too. Lowest mine goes is 800, if I make min cal 795, it becomes 810. Funny thing though, when I do that, the actual voltage for 700mhz drops from 1000mv to 990mv
[Samsung Galaxy Nexus] ak:
SR

It would be nice to understand the algorithm behind SR and if you can improve, or if there is some repository where you can find the mod of the same.

Thank you all for the wonderful support.
[Samsung Galaxy Nexus] galakanokis:
My MPU for 350 calibrates or settles on 775mV which is what I have it set to, SR min is set to 750mV

IVA stays at 835mV regardless of how low I go on SR min, currently 790mV. Perhaps I need to lower my actual voltage but I really don't want to mess with it that much.

Haven't messed with core but it sits at 886mV with SR set to 800mV and 902mV for settings.

No voltage monitor in Franco's app anymore, as mentioned it got removed and never added back in. Think he just got sick of people playing with voltages and then whining about an unstable kernel.
[Samsung Galaxy Nexus] ToMeRv32:
V070

Stock kernel voltages (830-1251)

Sudden reset to boot image, then stuck.

Had to pull the battery out.

Lost about 18% battery.

Didn't use whatsapp this time... (I think..?)

http://db.tt/PgXtn7gC
[Samsung Galaxy Nexus] Flomaster:
Trying your settings out now.

sent from my G-nex via Tapacrap
[Samsung Galaxy Nexus] frenchy714:
I also get a +10 buffer for MPU but I believe it's supposed to be that way, it was the same while on lean as well.

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] gummie:
If there are ways to improve it by applying fancy algorithm it would have been long ago. But if you really want to tackle Voltages, you might want to try ask guys on Franco, Osmosis and the others. Often see them before testing Voltage to be applied on the Kernel as SR is off bu default on his Kernel. I personally think that SR Algorithm is quite perfect as it really does its job to not starve the CPU.

Guys doing UV, it would nice to not post SOD's you suffer when you were messing on Voltages as it really is not the Kernels fault. UV tunables are in User discretion. And seriously?! Football? Guys? You have a phone, text, chat, mail it just not here. 10 mins scrolling jumping on pages just to see this and lot of thanks man.
[Samsung Galaxy Nexus] stevensoaj:
Ha, I learned about undervolting from a post by osm0sis. He knows what he's talking about, but I don't think he'll have extensive knowledge about Min Calibrated Voltages due to the fact that Franco kernel doesn't include that feature. But your right about the SOD/reboot statement. That's why I included a similar statement in my settings post and in my original question about the SR stuff today. :thumbup:
[Samsung Galaxy Nexus] binlalo:
Wow I'm having some lags and my phone heats up while having screen on (light use and no OC or UV), the drain issue is fixed but I can't use this :(

Edit: I've just noticed the ondemandplus governor so I'll give it a shot before changing to a previous version of the kernel or a stable one. Hope it doesn't use much more battery than interactive...
[Samsung Galaxy Nexus] jeff5347:
So I am impressed. I have mpu voltages all -50. I set my sr min to 790 on mpu running odp, 230 max off, 180 min and 1060 max. Was running cubic but switched to Westwood. Rabs 1048 and sio. My batt is 50 percent with.... ... 2 hrs and 45 min. Holy canoli. Just set all sr mins to 790 so I'll see how that affects batt. No sod or any probs. Regarding WiFi drops while using the net ..none. I think this is due to setting up a static ip
[Samsung Galaxy Nexus] jreyno10:
This is the last OT I'll post about it, but the new play store is amazing. I just downloaded it and it's so much better.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] sonnydroid:
Couldn't connect to gtalk/google services on v070. Went back to v063 and it works/connects now.
[Samsung Galaxy Nexus] frenchy714:
No issues like that over here...Did you try wiping caches and rebooting, or reflashing v70??

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] musashihatred:
same here. dont have connection errors. if ever some persist. change TCP congestion algorithm. :D
[Samsung Galaxy Nexus] AKA_noodle:
New ver. of AK is pretty smooth!!! Thanx Anarkia for your awesome kernels!:fingers-crossed:

I don't have problems with wi-fi.:good::good::good: