yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] 32bit:
Hi, Francisco! :) Nice to see You again after so long time (passed for me)

Think, it's not bad idea to control maximum GPU frequency via your app as it used to max/min CPU frequencies. If there is some artifacts with Live option, it could be implemented as "reboot required". So, an another profit of the solution You could support only one version of the kernel instead of two.
[Samsung Galaxy Nexus] yellowdie:
Odd. 384 or 512? Download or autoflash? Fix permissions (shouldn't need it, I know; but it can't hurt.)? Which ever way you did, maybe try the other. Lol. I autoflashed 512 from the app (my guess from past experience is that's the same thing you did :) )
[Samsung Galaxy Nexus] lsv-1:
@franco, this is about r292, honestly I haven't installed it yet because a couple of days I was playing with the louder patch, and definitely if the performance sound or the boost are enabled the beats audio processing stops working. I was having the low in call volume problem too and it was because of the dsp manager implemented with the patch, I thought that I had to manually select it in order for the beats audio to work, which according to the creator of the patch is not necessary. I will install r292 for testing purposes and I will let you know if it works correctly with the louder patch, cheers!

Sent from my Nexus Prime JB 4.1.2
[Samsung Galaxy Nexus] beyboo:
Reg #292 in call boost, had a few lazy Sunday calls. Volume is sharp and high, but that's at home. Will be able to test more towards the evening today out on the street.
[Samsung Galaxy Nexus] bioan:
Omg! The quality in call has improved a lot. The sound is higher and sharper. Thank you Franco!
[Samsung Galaxy Nexus] yyz71:
+:good:
[Samsung Galaxy Nexus] gaich:
Yes, this is really, 384 version, I tried to flash it.
[Samsung Galaxy Nexus] dyepnoodle:
call vol improved! tested on skype, viber and regular phone calls.
[Samsung Galaxy Nexus] --__LoRiS__--:
Noob question: We have 1gb of hardware ram but system give me 694MB available... why? I noticed in a galaxy s3 of a friend that Samsung improved amount of ram with an update... there is a way to unlock remaining MB or they are "reserved"?
[Samsung Galaxy Nexus] ciprianruse88:
http://xdaforums.com/showthread.php?t=1868413 here you see the answere.next time just do a search
[Samsung Galaxy Nexus] Dr Byte:
I had a look into it when I first got my GN and flashed FK. I didn't have much luck, nor expect to have much luck, because the battery chip is very limited in functionality. It seems to have virtually no knobs to twist or dials to read except for "voltage" and values that are computed/estimated from the voltage.

Unlike the Nexus One/Desire, it has no current-measuring facility. Currents are estimated by voltage drop.

Unlike the N1/Desire, it seems to have no way to disable charging and run purely on external power after the battery is full :(

I can probably put my hands on the technical papers for the battery chip if you want to have a go, Franco. It's a MAX17040 This thread might be useful too: Battery "calibration" knowledge, gleaned from the Nexus One - xda ...

It was too much of a nut for me to crack at the time :) See my earlier post in this thread, http://xdaforums.com/showpost.php?p=26086487&postcount=15707
[Samsung Galaxy Nexus] The Gingerbread Man:
On 292 384 I had a problem, phone froze up but didn't reboot, had to battery pull. I was using root explorer at the time to move my downloaded 292 to my flashing folder in my phone. Using minco v4, 1036 max cpu interactive governor

Edit

No file to pull in proc/lastkmesg

Edit 2

I'm using smart reflex and using min CPU of 230

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Tarun95:
Just flashed everything clean yesterday. Restored everything through tib. Didn't charge fully. And look at the result. Stock Franco settings and all location, sync etc everything on. First cycle BTW :p r290. Thanks a lot man. I think u should go on a vacation because your done. Kernel perfect :)
[Samsung Galaxy Nexus] SUTHRNFRIED:
Ha! Nice. :D
[Samsung Galaxy Nexus] CaspaTheGhost:
Just flashed 292 but 290 was impressive for me.

View attachment 1419160

View attachment 1419161

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] CaspaTheGhost:
???

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Better call quality makes sense, so thats definitely a plus, guess I fixed it. Someone was talking about 4G in a place where he didnt have signal before...makes some sense too. I will wait for more feedback. I would like to see some feedback regarding overall internet speed, data or wifi.
[Samsung Galaxy Nexus] mohaimed:
has anyone tried both franco r292 and trinity a67?which one gives u the best battery life? (i am currently on rasbean)
[Samsung Galaxy Nexus] Lostpick:
Default governo/ CPU clock ?

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] dracon6ai:
Franco, did you go back to deadline over bfq? Jrummy just redid the whole kernel tweaks/cpu control section of his app. Was wondering if his app was goofing when I saw deadline being used (along with vfs cache being 20%) or you really changed it. :confused: Damn mind games. Lol. No issues with r292 so far but haven't played much with it yet.

Edit- Done some digging and found out that Liquid RC5 was changing the sysctl on start up. Forgot that I experimented with liquids start up mods. Heads up for all, Franco's settings are ALOT better than liquids. :D

Laziness is nothing more than the habit of resting before one gets tired!
[Samsung Galaxy Nexus] Savant:
They both give fantastic battery life. I am going to try the beta since its in the testing phase.
[Samsung Galaxy Nexus] ghojezz:
R292 = fantastic :D

no lag at all, very smooth, but i need some tweaks to make my battery last longer (i usually got 8 hours only compared to this one :

​

picture taken on july

even though i'm using 1036 Max CPU 384 Min CPU, Interactive Governor, does anybody know an awesome tweak to give our GNexs longer breath

thanks :)
[Samsung Galaxy Nexus] farfromovin:
HSPA d/l same, WIFI d/l improve 10%, both u/l worse by roughly 50%. That's what several speed tests confirmed on my device.
[Samsung Galaxy Nexus] venividivici87:
Franco, improvements in audio Call are related to The implementation of wideband audio? I don't know if it's related to kernel or rom neither if it's already working in our nexus... But Could be something to work on?

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] franciscofranco:
I set deadline by default on r292 for testing yes.

Neps, I changed some stuff over Ezekeels sound implementation
[Samsung Galaxy Nexus] The Gingerbread Man:
Had another freeze up and had to battery pull again. Iv not bad a call to test that and am out visiting the in laws so can't comment on if music play back pausing bug has gone.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] :
Deadline seems a bit snappier :thumbup:
[Samsung Galaxy Nexus] franciscofranco:
Are you using 230Mhz slot?
[Samsung Galaxy Nexus] The Gingerbread Man:
Yes, up till now it has been stable though.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] :
+1 me too
[Samsung Galaxy Nexus] Culex316:
I can also confirm call audio is MUCH better with this build and I have always liked deadline better anyways.

As for wifi speeds I do not notice any difference. My home wifi fluctuates too much in speed throughout the day to really make any objective observations.

However overall performance with 384mhz min1536 max interactive with 1305mhz hi speed at 85% load is amazing
[Samsung Galaxy Nexus] franciscofranco:
Ok I gotta check whats up with 230Mhz. Use 384Mhz in the meantime.
[Samsung Galaxy Nexus] nuwan32:
Well the change log be released today, and any idea on why people are getting fc when in oc/uv settings?
[Samsung Galaxy Nexus] The Gingerbread Man:
Its only happened twice to me in around 8 hours perhaps. So far my CPU spy is showing 230mhz being used for 12.58 in a total of 2 hour time of my phone being turned on, which is the longest time spent in any of the speeds except deep sleep. So I'm not entirely sure if its 230mhz speed is broken as surely if it were this would happen much more regularly? 1st time I was using root explorer and 2nd time I was just flicking though my home screens.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] SIGUEL:
I'm having intermittent wifi problems, besides that, everything else is golden.

SKYNET
[Samsung Galaxy Nexus] Blackcrx:
Quick question. When you do the auto flash using the app. Does it clear cache and stuff like it would if you flashed in recovery? This was the first time I used auto flash and I noticed that it didn't do the "optimizing apps" thing at the start of the ROM load.

R292 is running great with no problems here. Battery drain is a little high but that's to be expected with the initial flash. I've always been using deadline but for some reason r292 seems a little quicker. Possibly just in my head. Haha.
[Samsung Galaxy Nexus] franciscofranco:
It shouldnt crap at all. Check if it happens with 384mhz please.

Yes makes sense I changed something on deadline.
[Samsung Galaxy Nexus] osm0sis:
Yeah, I'm not sure it's 230 that's the issue either.. though I do use it. For comparison, from my other posts:

I'll try it again with 384 as well.
[Samsung Galaxy Nexus] The Gingerbread Man:
OK, just set up a power mode for 384 - 1036 interactive to test for you

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Thanks. Let me know when you get solid data on your testing.
[Samsung Galaxy Nexus] CaspaTheGhost:
Interactive and 729/1305.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] The Gingerbread Man:
Sure will do, normally when I have a random reboot or similar I do try to provide last kmsg but because I pulled the battery I couldn't see that file. Generally speaking I use the 230 slot to help save battery, I think its crazy these people using 729 as min speed.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Same. That said, I was able to reproduce the freeze pretty readily last night just clearing my settings and redoing them, and I'm not seeing that now with 384 as a min. I'll report further after some more usage and time.
[Samsung Galaxy Nexus] obsanity:
Running 230mhz just fine now. It froze after flashing once and stuttered for a while once after that but its been stable since. Voice calls are clear and performance seems normal as always.
[Samsung Galaxy Nexus] billykxda:
I've been running CNA ROM and it's been working great for me. The ROM dev uses Faux kernel, so when I flash, I get exposure to whatever version of Faux's kernel is supplied. I typically swap-out Faux and use Franco's after a couple of days.

One thing I noticed in these a/b comparisons is that when Faux is installed, my GNex can take forever to change its orientation as I switch from portrait to landscape. When I flash Franco's kernel, the orientation is always immediate - very nice, but I am not sure that I can attribute that to the kernel choice.

Am I noticing some that that has nothing to do with kernels, or does the kernel actually affect how quickly a GNex notices that orientation has changed, and then switches to the appropriate orientation?
[Samsung Galaxy Nexus] The Gingerbread Man:
OK so my initial findings using 384 as min CPU speed my phone does infact feel that little bit more quick and snappy and there's no hint what so ever of any micro lag at all. So far I have no random freezes but it might be too early to tell. I just hope 384 will still be OK for battery life as I use xda app a lot, more than anything else which I can't imagine needs much power

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Not directed to orientation itself but if a kernel is badly optimized you'll have slowdowns every now and then.
[Samsung Galaxy Nexus] nuwan32:
I use 384 as min and under volted both 230 & 384 it's only 25mV higher for 384, so no battery problems at all and great performance
[Samsung Galaxy Nexus] The Gingerbread Man:
I'm not so much worried about the small voltage increase and I don't under volt I use smart reflex and I havent really looked to see which each CPU speeds use. When I try to save battery I lower CPU speeds. Your right in a sense that 384 probably makes things that bit better and hence its the stock minimum CPU speed chosen by Google its just kinda weird that 230 is causing minor instability for a few of us, unless it has something to do with the changing from bfq to deadline but I don't know about those and tend to just leave it as Franco intended us to use.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] obsanity:
292 froze on me again this time while listening to audio with screen off. Couldn't wake it up. Same settings as before.
[Samsung Galaxy Nexus] The Gingerbread Man:
Also, going back to where we were talking about improvements I'd quite like for an option to edit custom power modes. Would be more convenient to edit one setting that create a whole new profile, perhaps being able to edit the name of the profile would be good too.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] pen²:
Same happened to me during a call
[Samsung Galaxy Nexus] The Gingerbread Man:
That makes 4 or 5 of us with 230 being an issue for some reason which we can't provide proper documentary results because needing to pull battery. Like the boss said earlier just raise min speed to 384 and try it out

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Hmm I wonder how solidly it's frozen.. Like if we turn on USB Debugging then trigger it, I wonder if we can go in and cp or cat kmesg or trigger a reboot from the terminal, so we get a proper last kmesg.

Edit: just switching to 230 then going back to my homescreens to test out the above I got a freeze! Definitely seems like 230 is the culprit.. Definitely wouldn't trigger USB debugging once frozen then plugged in, in fact didn't even register it was plugged in since when I pulled the battery it still turned off.. going to try and do it again with it already plugged in.
[Samsung Galaxy Nexus] franciscofranco:
Yes I wonder too.

Just for confirmation, all the people that reported that freeze were using 230Mhz as minimum right? If so that will probably be easier to fix, its worse when there is no pattern :)
[Samsung Galaxy Nexus] Savant:
Yeah it happens with 230 and I've been using the one step up and its good.
[Samsung Galaxy Nexus] The Gingerbread Man:
Well from what iv read in the last hour or so 230 speed seems to be the common thing. Without knowing the full changes its harder for someone like me to say what caused the problem.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
No problem, I have an idea whats going on. I prefer to keep things shadowy for a while, helps me greatly than disclosing every change I do because the feedback is so much better and accurate.
[Samsung Galaxy Nexus] osm0sis:
Frozen up solid. I was in the adb shell terminal waiting for it an there wasn't any response once it hit.

Doing a cp /proc/kmsg /sdcard/kmsg to see if I can get it to catch the error before it freezes.
[Samsung Galaxy Nexus] GeekMcLeod:
Been running 292 since this morning and loving it. Sound is still perfect and my battery life has GREATLY improved. Ever since pa 2.0 and your, 27x or so, kernels, I've been losing 1% damn near every 20 mins, that's on idle. So far, not much screen off time but as much battery as I'd have left if i had it sit idle for 3 hours or so.
[Samsung Galaxy Nexus] franciscofranco:
Yes, its a true kernel lockup :) challenge accepted!!
[Samsung Galaxy Nexus] Vangelis13:
Very nice this r292 @ 512, very nice Sir..

P. S. From a vivid tester but hardcore trinity user. ;)
[Samsung Galaxy Nexus] osm0sis:
Hell yeah! :D Though, of course, now that I'm doing something that might catch the error, I can't seem to reproduce it. :rolleyes:
[Samsung Galaxy Nexus] yellowdie:
Okay! I'm back in the ring as well! Os and I were looking at the freeze last night and I couldn't replicate it, but now I can. *drum roll for the obvious* Setting the min to 230 = freezes. I can replicate as well now. But the question is why are people using 230? It can't seriously be worth the slowness. I use 729 as my min and it runs SUPER SMOOTH, and I get 3-4 hours of screen on time with the stock battery and stock voltages. lol. I can't see 230 being any better there.
[Samsung Galaxy Nexus] osm0sis:
Hey, everyone who can trigger the freeze: Turn on USB Debugging under Developer Options, then go in with adb shell, cp /proc/kmsg /sdcard/kmsg then leave it running and get it to trigger. It'll hopefully capture the error in the /sdcard/kmsg copy before it locks up entirely. Could do this in terminal emulator too if you wanted w/o the USB debugging, just need to su before the cp command.
[Samsung Galaxy Nexus] yellowdie:
Got a kmsg this way, but I wasn't able to get a last_kmsg. :)
[Samsung Galaxy Nexus] bradm23:
Weird, first time android os is highest battery hog vs screen in a long time. Not sure if anyone else is having this
[Samsung Galaxy Nexus] franciscofranco:
Android OS = apps.
[Samsung Galaxy Nexus] franciscofranco:
@GingerbreadMan, osmosis, yellowdie

Try to replicate the freeze with this: http://minooch.com/franciscofranco/... Bean/experiments/franco.Kernel-r294-test.zip
[Samsung Galaxy Nexus] yellowdie:
Okay, I think I got a proper last_kmsg. Unforgettably, while I know some programming, this gobbly goop is not one of them. lol Enjoy! Franco, see if this helps at all. :good:
[Samsung Galaxy Nexus] osm0sis:
@yellowdie: Doesn't look like you caught anything with those. last_kmsg looks like a normal soft reboot, and kmsg is just recalibrating mpu voltages. :(

Hopefully Boss Man has us covered with 294. ;)
[Samsung Galaxy Nexus] yellowdie:
On it.

---------- Post added at 08:24 PM ---------- Previous post was at 08:14 PM ----------

Bummer 'bout the msgs. lol. And my 192MHz is showing 1000 mV as stock. :/ So far no freezes though. Still testing.

EDIT: OH MY GOSH.

This has to be the most painful thing I have ever gone through...

I set my min and max at 192000 to lock it there for testing. IT HURTS!!! lol. Still no freezes or lockups. I tested 192 at 1000mV, and I just lowered it to 800mV and still no freezes. :)
[Samsung Galaxy Nexus] osm0sis:
Yeah. That was my init.d script setting the voltages the same as r292. Here's the real scoop ;):

Looks like 230MHz step is gone, so I guess we're testing with 192MHz, higher nominal voltage though.. 1000mV. It is SR calibrated to 830mV, same as 384MHz, so there'd be no gain to running it as is, realistically. :p Anyway it does seem stable but sort of pointless I guess. Though the 10mV difference between 230MHz@820mV and 384MHz@830mV(SR) makes that seem kind of silly too. I suppose we should just start running 384MHz as our min, is that what you're trying to tell us Franco? :laugh:
[Samsung Galaxy Nexus] yellowdie:
haha. I agree that 230 is pointless as well. But just for kicks and giggles I dropped the 192HMz down to 600mV (using 50mV drops) (with SR off) and it ran fine. No freezes (tried the UV page and the color multi page as well as general use). It's been super painful running 192 min and max, but it ran pretty stable (but very, very slow and sluggish!).

So I think it's time to stamp this one as a PASS and get back to my normal clockspeeds and no undervolting. lol. Props, Franco. :):D:laugh::good:
[Samsung Galaxy Nexus] osm0sis:
Haha. Tried 192MHz at 600mV and got a freeze. Trying to find a lower voltage that works for me, maybe 700s? If Franco dropped it down to that by default that might work for us powersaving freaks. Otherwise I'd prefer he just remove that step altogether and make 384 the lowest min.

Edit: Also froze at 700mV, so 725-750mV are what I'm liking for 192MHz.
[Samsung Galaxy Nexus] yellowdie:
Before I started reading this thread about two months ago, I was a big undervolter fan (I have since been schooled in the ways of SR and stopped). But I used to run this set up:

3xx=800mV

7xx=900mV

10xx=1000mV

12xx=1100mV

13xx=1200mV

15xx=1300mV

I'm occasionally really CDO (That's OCD but in proper alphabetical order!), and I like round numbers. lol. It used to drive me crazy when people would do like 915mV or something not even. ha. Now I don't care and let SR handle it all. But I used to push that low and be totally 100% stable and fast.

So my point in all that is that I think my phone is capable of lower voltages than normal. Which is why I can run 192MHz at 600mV totally stable. Haven't had a single freeze or reboot. Basic browsing and I took a 6 min call as well. lol. crazy. :cowboy:

---------- Post added at 09:10 PM ---------- Previous post was at 09:02 PM ----------

AH! I just got it to freeze. I had SR off the whole time, but I turned SR ON and it froze while trying to do that. So there you go! Did you have it on when you pushed down to below 700?
[Samsung Galaxy Nexus] osm0sis:
Currently rocking 192MHz min @ 725mV. No signs of instability, and this build still seems pretty snappy and smooth. :)

And yeah, I left SR on the whole time to keep calibrating the other frequencies. Since we're UVing to below the calibrated voltage of 830mV it will take whatever value we set. Try it at 725! I think we could have a winner at that voltage.
[Samsung Galaxy Nexus] yellowdie:
Out of curiosity, try turning SR off and dropping to 600mV. See if it will work. :) If it does, that means THEORETICALLY Boss Man could take 192 out of SR's calibration and manually drop the voltage really low for the uber power saving people. (Like with the 1420+ spots) Theoretically. :D

EDIT: Well scratch that. I knew 600 was too low, but it was fun. I just tried again after a reboot, and I could NOT get it to 600mV. So I'll try 700 and see if that floats. :)
[Samsung Galaxy Nexus] nuwan32:
haven't had time to flash any of the experimentals today, but 294 sounding really good. Is this the one where you guys got 192 down to 600 mv? Might give it a go when I get the chance
[Samsung Galaxy Nexus] noobiekins:
Be careful when undervolting, it may not always save power. I heard from someone with more knowledge on computer chips tell me, if voltage gets too low, it'll spit errors, which might crash/reboot device(use more power) or start error correcting(using additional cycles to repeat the task that had errors, which increases power usage)
[Samsung Galaxy Nexus] yellowdie:
Yeah r294 (384) has 192MHz instead of 230MHz, but we were just playing around pushing it to 600mV. Probably not daily driver ready. lol. 725mV may be the lowest stable we can go. :)

---------- Post added at 09:34 PM ---------- Previous post was at 09:26 PM ----------

Oh totally. I am actually against undervolting when we use Smart Reflex (SR) to control it for us. Osm0sis and I are just havin' fun. r292 had an issue with the 230MHz spot, and Franco put out a test build which turned it down to 192MHz and turned up the voltage. So Os and I are just playin' around. lol

fyi, @Os, phone froze again at 600. So it was probably a fluke the first time around. Oh well. :P
[Samsung Galaxy Nexus] osm0sis:
Ahhah that's too bad. I'm personally a fan of leaving SR on and (since I have my max at 1536) UVing those which SR doesn't calibrate (which is anything above 1305). 230 wasn't SR calibrated in the last twenty nightlies or so, so I'm thinking if we get 192 it probably won't be calibrated either, for stability sake. And in that case, we could definitely save some juice by UVing that frequency. :cool::fingers-crossed:
[Samsung Galaxy Nexus] Culex316:
Hey franco did you do anything to wifi signal strength? I get a better signal in the bathroom on the toilet now than on past builds.
[Samsung Galaxy Nexus] yellowdie:
I'm totally cool with UVing the stuff that's not SR handled, and I didn't know 230 and below wasn't done by SR. Honestly, I've never once used anything less than the 3xx spot. So I agree about turning it down. And I think you found the lowest: 725. I was freezing at 700, but 725 is running stable. So Franco, IF you wanted to drop 192 down to 750 or so, I think that would please the 230 fanboys. :)

---------- Post added at 10:01 PM ---------- Previous post was at 10:00 PM ----------

That is excellent to know. Thank you for the vivid feedback.