yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] momomok:
4.2 builds of franco kernel are very weird to me. Ususally, after a whole day use. The phone become very very laggy.

The available memory as shown in the Running section of manage applications is usually < 80 MB at that moment.

I know what some of you may say

"Android fills up all the memory as cache, to speed up loading; memory will be freed when it is needed, so no worry"

but that's not the case, take this screenshot as an example (it is taken when the phone is not lagging):

when the phone starts to lag, I found that the part between green line and yellow line expanding so big, around 500MB in total.

And the part between yellow line and red line (that should be covering the memory in use by your apps right?) shrinks to extremely small (50-60MB perhaps)

this is not normal right? I mean in 4.1 even if I run a lots of apps, the green-yellow part won't grow so badly.

it is obvious something is leaking and cause the green-yellow part to grow so badly, leaving basically not enough memory for apps to run, LMK killing apps all the time and causes the heavy lag.

I have been seeing this on multiple 4.2 ROMs and 4.2 kernels (even stock ROM + stock kernel combination), but the degres varies, with franco lagging the most, and stock kernel the least. And it is interesting that only a few of us experience this...

I am not complaining, I am just asking to see if anyone also experienced this and if they have found any solutions.

and I also wonder if it has anything to do with vm.swappiness? (franco put it @ 0 while stock put it @ 60)
[Samsung Galaxy Nexus] bradm23:
Hey osmosis,

I am giving your settings a try and so far very impressed. Are you still running 384 as min or rocking 192? Your post says 384 but i remember you talking about using 192.

Thanks in advance!
[Samsung Galaxy Nexus] t1.8matt:
the only way that i have been able to deal with this on 4.2 roms is to odex the rom. don't know how it helps really, but read somewhere that it does help and it's been helping me. i'm currently running liquidsmooth and was having lag problems with franco and other kernels when multiple apps were open, odexed the rom and no where near as much lag.
[Samsung Galaxy Nexus] osm0sis:
Played around with 192 and cfq but still ended up coming back to 384 and deadline for overall smoothness. Fear not, if I change my daily driver settings I'll update my post. :)
[Samsung Galaxy Nexus] evilssj4:
hey osm0sis, I am trying your guide for UV and at 192MHz I have gone as slow as 325mV and it still has not crashed. is something wrong?? I did turn off MPU smartflex
[Samsung Galaxy Nexus] osm0sis:
My guess is you have 384 as your min? 192 won't crash if you never use it. ;)

Check the guides again. You need to make sure you're on the frequency you're testing. :)
[Samsung Galaxy Nexus] Khrushy:
lol!
[Samsung Galaxy Nexus] evilssj4:
nope I actually changed the min to 192Mhz before starting the guide :confused: I expected it to crash at like 725mV
[Samsung Galaxy Nexus] osm0sis:
Performance governor? ;)
[Samsung Galaxy Nexus] evilssj4:
well in your guide it says to crash the phone and boot it up and then change the performance governor. The only way it crashes is if I don't turn off SR when I lower the voltages.
[Samsung Galaxy Nexus] allgsmnetwork:
Use + 25 all Mhz and battery good ;)
[Samsung Galaxy Nexus] osm0sis:
No. First, that's not what we're talking about and second, this guy is actually trying to properly create a voltage profile; he's doing it right, what you've done is incorrect, uninformed and lazy.

Only performance governor for the higher freqs since it forces the max. So it wouldn't matter that you set 192 as your min since it's still going to run at whatever your max is. To crazy ensure using 192 you could set 192 min, 384 max and lazy governor.
[Samsung Galaxy Nexus] allgsmnetwork:
do not get mad friend :) even to me with your values ​​u reboots I've tested it several times I do not understand perhaps the maguro is unlike the others I do not know what to tell you you're the expert :confused:
[Samsung Galaxy Nexus] evilssj4:
oh ok ill try this right now thanks for the help. :good:
[Samsung Galaxy Nexus] osm0sis:
I want people to learn. Blanket adding or subtracting 25mV from all frequencies isn't how to properly UV. Please go back to my post and follow my linked UV guides and properly read them to create a UV profile like evilssj4 is trying to do, or just use stock voltages and let SR do its thing if that's too difficult for you.

No problem! Thank you for taking the time to do it right! :good::D
[Samsung Galaxy Nexus] Khrushy:
What I always do when testing voltages is set both the min and Max CPU freq to whatever freq I'm testing to ensure it's using that speed, then go play a game to stress the system.

Sure the responsiveness at 192 max in games isn't great, but it does stress test well.

You might still run into problems later if your voltages are stable at each individual setting, but you have instability when it switches frequency under normal use - but those issues can usually be nailed down with a bit further testing by restricting the available clock frequencies with min/max CPU speed to force it to change between certain frequencies only.

Edit Allgsmnetwork: osm0sis isn't angry, per se, but he *is* trying to help a guy do it properly. Your "advice" and comments re: UVing in this thread can basically be summarised as "copy osm0sis, then if there's a problem, don't actually try to find the cause of the problem, just raise all voltages +25".

Which isn't really good advice, and just gets in the way of others who are trying to give advice properly.
[Samsung Galaxy Nexus] osm0sis:
Ah can you set the max to 192 now? You didn't used to be able to do that before, I think because it was the lowest slot.

Performance gov is equivalent to that idea though by forcing the max. So either way. :)

Edit: Exactly. Thank you.
[Samsung Galaxy Nexus] evilssj4:
it still isn't crashing :confused: turning off SR i just have to check "Disable MPU Smartreflex" right?
[Samsung Galaxy Nexus] osm0sis:
That is really odd. Must be something we're missing. Checking does disable it, yes. Leave SR on for now though, and go to Device Monitor. What freq does it show you idling at?
[Samsung Galaxy Nexus] evilssj4:
I changed everything back to stock except max is at 1036MHz. It keeps going back and forward from 192MHz to 729Mhz
[Samsung Galaxy Nexus] Khrushy:
This is really obvious, but this getting so weird I'm going to go with obvious anyway - but your Franco app does have root rights and is actually applying the voltages?

When you check in system monitor, your voltages actually reflect what you've set right?

Edit: os: yeah you've been able to set 192 max for a while now. But yeah, performance/lazy governors achieve the same thing for testing max/min, so whatever.
[Samsung Galaxy Nexus] evilssj4:
yeah it definitely does. It only crashes when SR is On and I change the voltages.
[Samsung Galaxy Nexus] osm0sis:
And it shows the wildly low voltage you set for 192 in Device Monitor as well?
[Samsung Galaxy Nexus] calibachrome:
Does anyone know how I can free up memory. These emulated folders are taking up all the space. I tried to delete one folder in my file explorer except what you delete in one deletes the same thing in them all. I also did a forum search and couldn't find anything relevant.
[Samsung Galaxy Nexus] evilssj4:
ok so i set the governor now to lazy, max 384/min 192, disabled SR, I changed the voltage for 192MHz to 500 lol just to have it really low, and now in device monitor it just shows 0mv-192Mhz?? and it doesn't move just the temperature does.
[Samsung Galaxy Nexus] Khrushy:
So how are you checking what voltage is actually applied when you turn SR off? I just see 0mv in the device monitor for all voltages if I disable SR.
[Samsung Galaxy Nexus] osm0sis:
Your question doesn't belong here, it belongs in Q&A. Either way, sdcard space isn't the same thing as memory, and the emulated and legacy folders are just symlinks to the same folder which is why you see the file disappear in "them all". Symlinks don't take up any extra space since the files are only there once.

---------- Post added at 02:21 AM ---------- Previous post was at 02:20 AM ----------

Yeah you've got to leave SR on for it to show correctly in Device Monitor. Current limitation of the UV interface/f.Ku. It shouldn't matter if it's on or off with voltages that low though. They go outside of SR's control as soon as they're set below the voltage that SR calculates for its calibrated voltage.
[Samsung Galaxy Nexus] evilssj4:
If i turn SR on it will definitely crash my phone which it just did haha. Idk this is the first time I've really wanted to do this so I can get the best battery life.

---------- Post added at 10:26 PM ---------- Previous post was at 10:24 PM ----------

I thought by going to device monitor it would show me but like you said, once SR is disabled it just shows 0mV
[Samsung Galaxy Nexus] osm0sis:
Weird. So it's like it's only really setting the voltage for you when SR is enabled. Alright.. That's how you should do it then. Start again but with SR enabled.

Maybe wipe data+cache on f.Ku then reboot for good measure too, just to make sure it's not some weird settings file derp you've stumbled upon, and you're starting from scratch.
[Samsung Galaxy Nexus] evilssj4:
I thought by going to device monitor it would show me but like you said, once SR is disabled it just shows 0mV

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

Yeah, the app has superuser permission and everything so I'm not sure what's the problem. I'll try doing it with SR enabled then, see how that goes.

---------- Post added at 10:30 PM ---------- Previous post was at 10:29 PM ----------

Yeah, the app has superuser permission and everything so I'm not sure what's the problem. I'll try doing it with SR enabled then, see how that goes.

---------- Post added at 10:30 PM ---------- Previous post was at 10:30 PM ----------

Yeah, the app has superuser permission and everything so I'm not sure what's the problem. I'll try doing it with SR enabled then, see how that goes.
[Samsung Galaxy Nexus] Khrushy:
Ok, something stupid is happening here, but I have NFI what it is.

I suggest going into app settings and clearing ALL Franco updater data to reset everything to defaults, then rebooting, and lets start again from scratch.

After you reboot, start at the highest frequency first, (eg: 1200mhz if that's what your highest freq you're going to use is) and set both min / max cpu freq to that, lower the voltage a bit, then go play a game or some other form of stress test (there's an app called cputest on the market which is good for this too). If it survives about 5 minutes of that, go back in and lower voltage further. Repeat until you crash, then write down whichever voltage was the stable one before you had the reboot.

Then repeat the process with the next frequency until you find the lowest stable setting for all the frequencies you want to use.

Leave SR on at all times.

Before you go to test it each time, check in the device monitor that your cpu is actually running at the frequency and voltage you just set.

Do NOT set "apply on boot" until after you've finished with all your testing and are REALLY SURE that all your voltages are stable. Test each freq individually to find the safe minimum, then test ALL your safe minimums together for at least a couple of days - if you have no problems after a couple of days, then you can set "apply on boot" without worrying you're going to get stuck in an UV bootloop.

Good luck!
[Samsung Galaxy Nexus] osm0sis:
What's your root app? Superuser or SuperSU?
[Samsung Galaxy Nexus] allgsmnetwork:
so basically you say that even if you restart at the beginning then slowly settles SR?
[Samsung Galaxy Nexus] osm0sis:
I'm saying my voltages are just for reference. You (and everyone) should start with the default nominal voltages and work your way down one freq at a time as per mine and Khrushy's repeated explanations of the method. This is how you intelligently build a voltage profile for your device.
[Samsung Galaxy Nexus] evilssj4:
I am using SuperSU
[Samsung Galaxy Nexus] mariosraptor:
Can anyoneone tell me why phone idle has 20% usage in flight mode? Phone is in deep sleep but still consuming about 2-3% per hour.
[Samsung Galaxy Nexus] osm0sis:
Hmm should be fine then. I just disabled SR here and lowered 384 and caused a freeze and reboot, so it's definitely something odd on your end. Anyway if you wipe f.Ku data+cache then reboot and start again with SR on I imagine you'll be fine.

I'm heading to bed now. That was a fun couple hours. ;)

Good luck and let us know how it goes! :)
[Samsung Galaxy Nexus] allgsmnetwork:
I'm testing with stability test 192MHz min / max with your voltage does not restart .. so then start with 384 with your frequency 775 min / max test again and so 'on until you find the frequency that will restart :good:
[Samsung Galaxy Nexus] evilssj4:
haha weird. No problem I'll let you guys know. Thanks for the help :)
[Samsung Galaxy Nexus] allgsmnetwork:
384 I do not booting me with Franco 348 and 775 mV voltage step 537 and another test
[Samsung Galaxy Nexus] galakanokis:
Just to chime in on the UV conversation, I like evilssj4 get crashes when I undervolt to far with SR enabled. For me, and it has always been this way, I undervolt with SR off as I can seem to go lower than with SR on.
[Samsung Galaxy Nexus] ashclepdia:
That's because when you undervolt just a smidge too much and SR tries to go even lower then your CPU starts to hate you :D

Remember, with SR enabled, the UV value you "set" is whats known as the "nominal voltage", aka the "upper limit" that SR starts its calibration from. It will always try to go lower than what you set(and isn't ALWAYS so "smart" it seems Lol)

(And SR does not stop calibrating if you go below the calibrated voltage it had originally. It will keep on going.

If u TURN OFF smart reflex device monitor will not show the voltage Cuz it only shows a calibrated voltage. REST ASSURED knowing that if you TURN OFF SR, then WHAT YOU SET in UV interface IS being used. Its not gonna use anything other than what u tell it to of SR is off)

(Edit: my apologies for not reading back a couple pages . seems as tho I'm not on the same page as everyone here. Sorry guys!)
[Samsung Galaxy Nexus] Khizar:
something is wrong on your end.. i lose around .2-.4% per hour
[Samsung Galaxy Nexus] mariosraptor:
Thanks. Actually i think i found it. It is xda premium app.

I do not close it before i set my phone to flight mode. I will try it again though.
[Samsung Galaxy Nexus] allgsmnetwork:
All OK for the frequency by osm0sis after 3 hours of test the best all end thanks also Khrushy :)

Sent my Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] billykxda:
Francisco,

I've been cruising with r348 stock.

Just perfect on my GNex running MMuzzy's ROM.

Thanks and Happy Holidays!

-bk
[Samsung Galaxy Nexus] Bonvaz:
Guys I tried the voltages posted some pages ago but I want ripristinate the default ones... I use trickster mod, and the eraser zip posted some pages ago didn't work...
[Samsung Galaxy Nexus] Khizar:
clear trickster mods data..
[Samsung Galaxy Nexus] Bonvaz:
Didn't work...
[Samsung Galaxy Nexus] whitedragonz83:
Just achieved crazy 0.4%/hr over 6 hours idle drain on WiFi. This is the best I've ever had and I have all syncs going, Google Now, facebook/G+, no latitude.

Using r348 and RasBeanJelly's latest ROM.

The new interactive patches are crazy good too for keeping my CPU 'lower' <= 1 GHz even though I let it ramp up to 1.5 GHz. I was following the changes in the Mako builds with more interactive patches and just start to drool... Keep up the great work Franco!
[Samsung Galaxy Nexus] Bonvaz:
I also try to flash another kernel, let boot, reboot again and flash again franco, but still didn't have default voltages.....
[Samsung Galaxy Nexus] Khizar:
i dont have much experience with trickster but.. i guess it wouldnt hurt to delete the app and then install it again
[Samsung Galaxy Nexus] JBNex:
Have a problem. The BeastlyBattery profile, my phone wont enter deep sleep. And the dyninteractive governor, if you change min to 384> or max CPU screen off to 537> it will constantly reboot.
[Samsung Galaxy Nexus] Bonvaz:
Did it...... Not work.. Anyone can post me default voltages?pleeease
[Samsung Galaxy Nexus] gaich:
Just uncheck "set on boot" and reboot.
[Samsung Galaxy Nexus] osm0sis:
If you leave SR on and look at Device Monitor while you UV you'll see: as soon as you put your nominal below the SR calibrated voltage, Device Monitor shows exactly what you entered, meaning SR doesn't control it anymore. SR calibrated voltages are only calculated on boot so it's not working on-the-fly to take your new lower values and make them even lower.

I used to think it was bracketed like you suggested too, and I think at one point it was even, but Franco must have changed his implementation slightly, because now it does definitely appear to work as I stated above, and leaving SR on is basically harmless.
[Samsung Galaxy Nexus] haxor:
When I set min frequency to 192 MHz and other setting like max screen off from trickster mod then it all revert back to default :confused:
[Samsung Galaxy Nexus] mariosraptor:
Stock voltages
[Samsung Galaxy Nexus] galakanokis:
Just going off of my experiences I can run my low frequencies, 192 and 348 around 700 to 725 mv with SR off and have zero problems. The moment I enable SR with voltages this low I crash. If I want SR enabled I need to bump up to 750 to 775 and things will run smooth.

Just using those numbers as examples, I get the same issue with the higher frequencies. Definitely seems to be a sweet spot on the voltages and SR. And at least in my case SR seems to have some action on the voltages even on the low end.
[Samsung Galaxy Nexus] Roscopcoletrain:
maybe a dumb question, but are you hitting the check mark to apply the settings?
[Samsung Galaxy Nexus] Khrushy:
Just for the hell of it, giving this a shot.

Drunk random undervolting. It's what all the cool kids do on a Saturday night at 2am.
[Samsung Galaxy Nexus] osm0sis:
For me, 384 is borderline at 750mV and crashes at 725mV regardless of whether SR is on or off, which is why I keep it at 775mV on my device. With SR on, anything between the default nominal voltage and 830mV (the SR calibrated voltage) will show 830mV in Device Monitor since SR is acting on it. As soon as I lower it below 830mV then Device Monitor shows exactly what I've entered, meaning SR isn't acting on it anymore. This also works the same for all higher frequencies. Have you tried to reproduce that lately?
[Samsung Galaxy Nexus] timbck2:
I'm not in a position to do any wiping and reflashing right now, I'm on vacation. I'm starting to think this battery is losing its ability to hold a charge (original stock battery) and wouldn't you know it, I left my spare battery at home. I'll try my other battery when I get home in a couple of weeks and just do my best to keep this one charged until then. Thanks for the suggestions.
[Samsung Galaxy Nexus] calibachrome:
So is r348 worth going to or are there issues with it like 344? Ready to upgrade but I just remember a few days ago people were having some issues.
[Samsung Galaxy Nexus] bombadier:
Good results with r348 although have had some random reboots using the CFQ scheduler, Deadline is fine for me
[Samsung Galaxy Nexus] Khrushy:
Drunk UV testing 101:

So I have two possibilities here.

Option 1: Turning SR off puts my CPU into God mode.

Option 2: Turning SR off makes it ignore your set voltages and just uses defaults or something to that effect.

I'm reasonably sure my CPU can't actually run at 1mv, even at the bargain basement speed of 192mhz, so I'm going to have to go with option two.
[Samsung Galaxy Nexus] smileyanz:
Yeah no probs on 348, think if ya screw around with it to much you mite get little bit bother but in opinion its the best out there
[Samsung Galaxy Nexus] galakanokis:
Sorry, running around this morning, wide took the ass end out on the van and completely destroyed the rear tire, perfect timing to have to fix a vehicle.

I'll play with slightly higher voltages with SR on and see what happens.

Just read Krushy's drunken random undervolting results and it looks like without SR on the UV has no effect. My recollections of crashing are pre 4.2 builds.
[Samsung Galaxy Nexus] osm0sis:
Okay so that's what we were seeing with evilssj4 last night. Still not the case on my device though. Can you try wiping f.Ku data+cache then rebooting immediately then try it again?
[Samsung Galaxy Nexus] galakanokis:
Quick test.

With SR off I can UV like a mad man, 1mv for 192 and 384 and phone runs great. But, as soon as I try to go to far on the higher frequencies I get a crash. Looks like it is just 192 and 384 that are funny.
[Samsung Galaxy Nexus] osm0sis:
Can you do the same (wipe f.Ku+reboot)? I'm trying to figure out why it works correctly for my device but not either of yours. My only guess is a settings file issue.
[Samsung Galaxy Nexus] galakanokis:
Yeah, that did it. Cleared the data and the bottom two frequencies now calibrate as you would expect. I start to crash right at 700. Seeing it to 1mv is instant crash, black the moment I hit the apply button...

Of to play some hockey but will test the rest of the UV after that.
[Samsung Galaxy Nexus] osm0sis:
Perfect. So settings derp it is. Glad we solved that mystery. :)
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
Does this have CM10.1 support yet?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] marcusva79:
Yessir it does. Using it right now. Franco or anyone I have a question. Was using the latest nightly with an unofficial aokp rom. Everything was working great and then on the 2nd day it just totally dragged ass out of nowhere. Has anyone had similiar experiences?
[Samsung Galaxy Nexus] grotesque02:
I have a question!

With stock battery I set extender battery at 96.

Now I have a 2000mAh battery, I can leave at 96 or I have to change?

If yes, with what value?
[Samsung Galaxy Nexus] Bonvaz:
Great performance, thanks franco! Maybe a little too much battery drain, but phone is smooth, very smooth!
[Samsung Galaxy Nexus] Khrushy:
Not for me ^^

Cleared f.Ku, cleared and disabled Performance Control included in AOKP, cleared system cache, cleared all of the above in varying permutations, rebooted 37 times, and danced the funky chicken naked in the snow.

None of which seemed to have any effect on my ability to set stupidly low values for the 192 or 384 slot with SR disabled.

Weird. I might clean flash something to see if it changes anything (if I can be bothered).

Edit: Clean wipe fixed this. See 4 posts below.

Edit 2: No it didn't. Settings and reality with sr off still don't match up.
[Samsung Galaxy Nexus] Khizar:
too much battery drain? on r348? r348 for me is the second best franco kernel in terms of battery

---------- Post added at 09:12 AM ---------- Previous post was at 09:11 AM ----------

yeah it works

---------- Post added at 09:13 AM ---------- Previous post was at 09:12 AM ----------

yeah it works
[Samsung Galaxy Nexus] nathanson666:
Yes same here. I have a feeling it is ROM related though.
[Samsung Galaxy Nexus] arhung:
delete