yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] timbck2:
I had a random reboot with r360 earlier today. I didn't have time to get last_kmsg right after it happened, so I don't know if the one attached will be useful. I'm running default settings except I changed scheduler to row and TCP algorithm to westwood. http://db.tt/5EFHCtKA

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Charmacas:
That may be a row error because the scheduler is experimental. :)
[Samsung Galaxy Nexus] malaroth:
http://xdaforums.com/showthread.php?p=34155147

[GUIDE] Build a Kernel! + [KERNEL] marmite_v7.2 MTP

JBSourcery 4.1 Franco 358 FTW! Keep the Magic alive!

---------- Post added at 04:00 PM ---------- Previous post was at 03:59 PM ----------

LOL yeah same here... 3 hours on 1 hour 15 min screen on

JBSourcery 4.1 Franco 358 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] enel_:
Just flashed 360... What the hell just happened to my GNex =D?!

This baby flies! I think we should 360 call Project double butter =)

Thank you Franco thank you...
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
What exactly was changed in r360 that made it so good? Is it something that could be implemented to other devices like grouper or mako?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Culex316:
Or Project baby's ass, because it IS THAT smooth.
[Samsung Galaxy Nexus] malaroth:
....what if the device starts doing gangnam style??

It's always possible mesmerize... but I think Franco wants to know how it works without people complaining about individual changes without posting documentation.

JBSourcery 4.1 Franco 358 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] The Gingerbread Man:
Something tells me 360 is gonna be the next 'reference' kernel, the one to compare stuff to in terms of smoothness and performance, the one where people decide to roll back to for what ever reason.

About these cracking sounds that were being mentioned before, is this down to poor app coding possibly? The only thing I can fault on 360 was I had a call which I couldn't hear using my wired headphone with mic but unplugging it and using the phone as a phone worked fine. Just this audio thing needs to be sorted then we are at a new level of perfection

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] TyroneLT:
I switched back to Franco's Kernel yesterday after using Lean Kernel for about a month on AOKP 4.1.2. I have to say r360 combined with some settings Osmosis posted a good while back that I found, and updating to AOKP 4.2 my device is running better than ever before. In past running Interactive with 1536/384 would have resulted in very fast battery drain with just over 2 hours screen by the time my battery is under 20%. But somehow with this version of Franco's kernel, Osmosis' governor control settings and the ROW I/O scheduler I am now closer to 4 hours screen time after the 1st day of usage. So for what its worth, this kernel is working really well with practically zero lag.

Great work Franco!
[Samsung Galaxy Nexus] -star-:
If I reboot or start my phone the Franco kernel app crashes.

Used the google feedback agent function (that one if an app crashes) to submit the report or do you want a copy of the logcat here on xda?
[Samsung Galaxy Nexus] nikulogical:
Has anyone here used AK purity 005? Apparently it has some of the same changes as r360.. I'm using it now and its pretty great.

I will probably use r360 tomorrow to compare but I'm wondering if some of you has done this already.

Sent from my Paranoid Maguro
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
I saw his post. I was just wondering if he or anyone else said what actually changed since that post since I haven't been checking this thread frequently. Been working on my N7 and hoping to get some 360 magic on it :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
If you check the first few pages after he posted it he explained a few of the changes he made.
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
Got a page number? Tapatalk doesn't make it easy to find that kind of stuff.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] RayGarden:
why is it i do NOT see #360 in FKU?
[Samsung Galaxy Nexus] TyroneLT:
I cant remember the page # but i did copy the settings to my Evernote knowing i might use them at some point. The onky thing different is the scheduler being ROW. Hope this helps:

MORE SETTINGS FOR Android 4.2

Device: Galaxy Nexus

Max Frequency: 1536 MHz

Min Frequency: 384 MHz

Governor: interactive

Governor Tunables: 60000 / 65 / 45000 / 15000; 1036 MHz hsf / 729 MHz ibf

IO Scheduler: deadline

TCP Congestion Avoidance Algorithm: westwood

Screen Off Max Frequency: 537 MHz
[Samsung Galaxy Nexus] malaroth:
+1 post 176 page 4 (latest post first)

JBSourcery 4.1 Franco 358 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] chickentuna:
cause it's a test/experimental version, get it here if you want to test it :http://minooch.com/franciscofranco/Galaxy Nexus/JB/JB-4.2/tests/
[Samsung Galaxy Nexus] bombadier:
[QUOTEWhy don't you guys just install the xlouder mod. It works perfect and my volume is totally fine.

I have got it installed,as gingerbread man says the sound is almost there,my issue is with the wired headset volume,ringing is loud but when call is answered volume dips,struggled to hear when driving with my window open,stock earphones
[Samsung Galaxy Nexus] Sveke:
I have got it installed,as gingerbread man says the sound is almost there,my issue is with the wired headset volume,ringing is loud but when call is answered volume dips,struggled to hear when driving with my window open,stock earphones[/QUOTE]

Got ya, sometimes toggling speakerphone on and off again helps.

Give that a shot.
[Samsung Galaxy Nexus] jeetS:
Franco, 360 is a beast.

Been running it for half the day now.

Also gone back and forth from deadline to row... I'm definitely noticing a smoother snappier experience with row.

Great work!
[Samsung Galaxy Nexus] Shadow-Nexus:
360 is perfect in speed but unfortunately its not the same for battery :(

Yesterday I got 10 hours with 3 on screen

In previous releases I would get over 20 hours with 3 30 hours on screen or more

But in the other hand I have to spare batteries so battery is not a big problem here!
[Samsung Galaxy Nexus] kCelsius:
It seems that Google Services is really suckin some battery right now for me...how to I disable some things so that it's not a battery hog? I have location services on, but only on wifi.
[Samsung Galaxy Nexus] jeetS:
That's not been my experience. I'm oc'd to 1305. Flashed it this am with around 90% battery left. I had over 3 hours screen on time this evening with 21% left... So I know that at least with active use its handling battery life really wel
[Samsung Galaxy Nexus] gaich:
Could anyone tell me what the kernel processes mean. The phone lays still, but the top process waisting the battery is the kernel:

GSam Labs - Battery Monitor export

Kernel(ОС Андроид)

05.01.2013 17:27:48

Детали использования

Использование CPU:1m 43s

Бодрствование:13m 47s

UID приложения:0

Включенные пакеты

Включенные процессы

irq/379-rtc0

vold

migration/1

file-storage

row_idle_work

kworker/u:4

kworker/u:3

kworker/u:6

kworker/u:5

loop2

kthreadd

kworker/u:7

loop0

loop1

kworker/u:0

kworker/0:0

kworker/0:1

kworker/u:2

kworker/0:2

kworker/u:1

bdi-default

kcryptd_io

debuggerd

flush-254:0

flush-254:1

sh

kdmflush

irq/131-ABE

ueventd

jbd2/mmcblk0p12

dhd_watchdog

mmcqd/0boot1

kswapd0

twl6030-irq

logcat

/init

ksoftirqd/0

ksoftirqd/1

irq/206-mms_ts

flush-0:19

cfinteractive

rcuc1

rcuc0

mmcqd/0

netd

adbd

flush-254:2

zygote

kworker/1:3

kworker/1:2

kworker/1:1

flush-179:0

kworker/1:0

kcryptd

khubd

ext4-dio-unwrit

dhd_dpc

sync_supers
[Samsung Galaxy Nexus] lippol94:
This is unbelievable based on my previous experiences with Franco kernel. I always loved it on performance side, but I was used to experience very low battery runtime.

On the latest 360 I'm getting the best of both! Great performance without sacrificing battery life. Here's my usage so far.

No wifi. Only HSPA+ connection.

I can't be happier :)

Thank you so much Franco! To me 360 test is passed ;)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Ok r361 is official:

r361:

* Interactive governor patches from Google

* Hardcoded voltages instead of letting Smartreflex calibrate them (users with my app will see the voltages return 0 on the Device Monitor - I will fix that on the app side soon)

* Removed the audio hacks on latest builds. Its not worth the trouble, users need the device to be working correctly on the audio side (calls etc).

* Some other minor changes and improvements

The only change between r360-test and this one is that I removed the audio hack - no more troubles with calls and sound.
[Samsung Galaxy Nexus] Jamdat33:
Staying up pays off!
[Samsung Galaxy Nexus] Fenvarien:
Thanks for the new release, I like to start the day with a fresh franco.Kernel :)

GNex with franco.Kernel r361 / CM10.1
[Samsung Galaxy Nexus] calinoii:
Do I need to flash the original sd binary after I flash r361?
[Samsung Galaxy Nexus] razvanultra:
I can confirm that, the InCall audio volume is loud and clear with last build, #361. Thanks
[Samsung Galaxy Nexus] gaich:
Confirming too!:good:
[Samsung Galaxy Nexus] Fenvarien:
No, that's not necessary anymore.

GNex with franco.Kernel r361 / CM10.1
[Samsung Galaxy Nexus] Icecoldmeat:
R361 runs fine with UV after 4 hours, I love it.
[Samsung Galaxy Nexus] Shadow-Nexus:
So its OK to UV now that SR is off right?
[Samsung Galaxy Nexus] smileyanz:
Must say these kernels from Franco are getting to the point of being stable. No sods at all , mind you I don't tinker to much with them!! Thanks to Franco and to all who have stayed and experimented with them!!!:D:thumbup::thumbup:
[Samsung Galaxy Nexus] allgsmnetwork:
First flashing 361,then UV or not?

Thanks a lot!
[Samsung Galaxy Nexus] calinoii:
Is anybody experiencing stutters from time to time? I'm getting them no matter what version of franco's kernel I am using ,even on 4.1.2 and 4.2.1.
[Samsung Galaxy Nexus] Khizar:
read my post that is 1 post above yours...
[Samsung Galaxy Nexus] haxor:
No audio boost in #361 :(
[Samsung Galaxy Nexus] Khizar:
nope.. kernel ran very smoothly with me, i was using it with default settings

its better that way...so no more volume issues that ppl were experiencing
[Samsung Galaxy Nexus] allgsmnetwork:
Then using UV do not need to remain what they are right? ;)

---------- Post added at 01:47 PM ---------- Previous post was at 01:46 PM ----------

Audio is perfect i use DSP manager if I want to change :good:
[Samsung Galaxy Nexus] Khizar:
not sure what you mean
[Samsung Galaxy Nexus] allgsmnetwork:
I mean if I use UV works or not with SR disabled by the kernel?
[Samsung Galaxy Nexus] kissme99:
Does this kernel fix this problem?

Or this problem can't be solved by kernels?

http://xdaforums.com/showthread.php?t=2029246
[Samsung Galaxy Nexus] allgsmnetwork:
GPU very stable and high perfomance... with antutu 2 test 3000 point before at 1420 after at 1536...for now without UV using deadline :good:

Good work franco :)
[Samsung Galaxy Nexus] logi43:
R361 is fast and fluid shows more so than previous versions, the headphone volume is high quality, No problem cutting or decrease of the same sound at any volume.

Great kernel

Thanks for your hard work
[Samsung Galaxy Nexus] supernova_00:
I've had this problem for weeks with the minimum CPU frequency setting.
[Samsung Galaxy Nexus] momomok:
I wonder why Franco suddenly abandon SR. Isn't it doing its job pretty good?

Sent from my Nexus Prime
[Samsung Galaxy Nexus] peikojose:
Testing r361, so far so good.

I have one question, what would be better for battery saving:

Profile 1: Max frecuency 1228Mhz and minimun 700Mhz (Takes less time to do tasks)

Profile 2: Max frecuency 1228Mhz and minimun 192Mhz (Lower frecuency but it would take more to do tasks)
[Samsung Galaxy Nexus] osm0sis:
SR is disabled AND voltages are hardcoded, meaning you CANNOT undervolt anymore. This has been explained several times by myself, by Franco in the release posts and on the last page for you.

He just wants to disable them for now at least because too many idiots were UVing incorrectly (blanket -100mV style or by taking my posted voltages and using them without properly testing each freq, despite several warnings). This way is less headache to try and sort out any other issues since now the voltages remain a known quantity for him.
[Samsung Galaxy Nexus] -star-:
In combination with which governor? And what would be the screen off frequency?

Without a mentioned governor and only for battery saving: 2, but for other situations it could be another choice.
[Samsung Galaxy Nexus] LibertyMonger:
Awesome!
[Samsung Galaxy Nexus] allgsmnetwork:
He has done well and does not heat the battery and it is ok, franco has created the best kernel so far and he will always give the best.

Thanks osm0sis by more precise explanations :)
[Samsung Galaxy Nexus] shawnaye:
R361 has been awesome thus far. Flashed about 3-4 hours ago.

Changed to ROW as I felt it suited my needs more.

Think it might be possibly a good default, especially if it can be tweaked more.

Using interactive as always.

Hey Franco, I've read on some thread that 512mhz for gpu has a higher power consumption compared to 387mhz.

Is this true?

If so, is it possible to get an option to uc the gpu between these two possible frequencies?

Just a question, haha.
[Samsung Galaxy Nexus] CommanderDuplex:
Franco, something gets wrong with the GN o may your Kernel , i like your Kernel really but i still can`t understand why the old Nexus S is FASTER ! then the GN in most case, of course when i do much Multitasting the GN wins (thanks 1024mb Ram) but the stock apps and some games would launch a lot faster on the Nexus S (cm10.1 jelly bro , with marmite 7.2.3 Kernel) that is really impressive to see !

I think you should talk a little with bedalus and ask him witch tweaks he used for the Nexus S and look if its possible to port it on the GN.

Im using cm10.1 jellybro with your r361 Kernel , stock freq. on both devices .

Keep going with your great work on the Galaxy Nexus :good:
[Samsung Galaxy Nexus] osm0sis:
2 would be best. The time to complete tasks thing is about Screen off max, and 537 (default) is the sweet spot there so leave it. If you find 192MHz min too laggy then just bump it back to the default 384MHz and you'll be fine.

Franco is planning on adding a screen off min at some point too. If/when he does that, naturally 192MHz will be the perfect choice.
[Samsung Galaxy Nexus] whitedragonz83:
Profile 2. Less cpu speed at idle = battery savings.

Instead of 192 or 700, use the default 384 min. You will be happier overall.
[Samsung Galaxy Nexus] osm0sis:
The slot uses roughly 100mV more but it only uses it when it needs to so with regular use the battery life difference is negligible; gaming it drops a little more quickly due to this but it's worth it for the performance.
[Samsung Galaxy Nexus] whitedragonz83:
Funny how the complaints about instability are non-existent almost now... ;)
[Samsung Galaxy Nexus] osm0sis:
Haha yup. ;) Though in all likelihood the fixed interactive patches from Todd at Google are going a long way towards this too. :good:
[Samsung Galaxy Nexus] allgsmnetwork:
Another test with 3000 points in antutu GPU always stable :good:

I using 384/1536

Governor interactive

Shudler deadline

NO UV

For me the best kernel

- Audio perfecly

- GPU super fast and more stable

- Battery is OK

- No lags

- Temperature is OK

- ALL OK :)

Great franco :)
[Samsung Galaxy Nexus] shawnaye:
Cool beans. Meaning that our gpu's have a choice for 512. But isn't necessarily always on 512 right?
[Samsung Galaxy Nexus] peikojose:
I have been testing screen off between 384 and 537... There is a little lag when using 384 but I think I can live with it.

I use the default governor (Is it Interactive ?? Let me know please ). But I have been trying with lazy (trying to beat my best battery life )

Thanks for your answer and all others that replied too.
[Samsung Galaxy Nexus] osm0sis:
Glad you're pleased but please stop spamming the thread with your bench results. We don't care about benchmarks here, we care about real world usability. Read the quote from Chainfire in franciscofranco's signature. Benchmarks are almost meaningless.

---------- Post added at 12:07 PM ---------- Previous post was at 12:05 PM ----------

Yessir scales as needed just like the CPU. Check the CORE UV page in f.Ku to see the freqs and voltages the GPU uses. :good:
[Samsung Galaxy Nexus] Syfer_Fever:
guys if i OC the GPU to 512Mhz or 384Mhz what will happen to my phone? (pros & cons)

faster? of course right?

but how about battery, performance, temperature, stability etc? thanks :)
[Samsung Galaxy Nexus] shawnaye:
BLOCK HIM DUDE! BLOCK HIM LIKE I DID A WEEK AGO!

Oh and thanks for the affirmation regarding the gpu! :thumbup:
[Samsung Galaxy Nexus] joaquinf:
The gpu is already oc'ed to 512. It improves the overall user experience with minimal (near to no) battery impact.
[Samsung Galaxy Nexus] Sveke:
Everyone's phone responds different. Try it. 384 has been good for me forever.
[Samsung Galaxy Nexus] -star-:
512mhz gives you some extra fps for eg gaming etc. you won't feel the battery influence through the oc. Some phones can handle the oc and run stable, others not. 384 is near the normal stock frequency.
[Samsung Galaxy Nexus] Syfer_Fever:
thanks for you answe guys, will try that ;) i'd never OC the GPU before hehehe :D
[Samsung Galaxy Nexus] Sveke:
If you play games I would def try 512. I don't so 384 improves scrolling and response for me and I'm happy with it.
[Samsung Galaxy Nexus] osm0sis:
What the hell are you guys talking about? :laugh: The GPU with franco.Kernel is already 512 if you're using it with JB4.2. There is no option. :p
[Samsung Galaxy Nexus] vigan_ks:
i tried

max1800

min 384

deadline

my phone is gettin too hot and freezes

im on xylon 014
[Samsung Galaxy Nexus] Sveke:
Face palm...correct. I've been crack flashing lately. My bad.
[Samsung Galaxy Nexus] allgsmnetwork:
OK I have understood it is only a comparison with other kernel by franco :)
[Samsung Galaxy Nexus] osm0sis:
Are you ****ing kidding me? Take a wild guess what the problem is.
[Samsung Galaxy Nexus] Khrushy:
You overclock your max by 50% and then comment your phone is hot and freezes?

Do you have any f%%king idea what you're doing?

(Actually, that's rhetorical, it's clear you don't)

I firmly suggest you stop what you're doing and do a simple Google search about overclocking your phone, starting with the basics of "what happens when I increase the frequency of my CPU".

Come back later when you've done some basic research yourself.
[Samsung Galaxy Nexus] shawnaye:
maybe it's time franco hardcodes frequencies as well!!
[Samsung Galaxy Nexus] joaquinf:
Did you wipe cache and dalvik cache?

:D sorry I couldn't resist

Man you are just doing it wrong, I case you haven't realized what your problem is: you are doing an extreme overclocking and that causing you all kind of issues. Leave it on the stock values until you do some more reading about pros and cons of overclocking.
[Samsung Galaxy Nexus] mixtapes08:
hands on face...

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] OtavioMalzone:
I know that I'm not a kernel developer but, I think the low sounds bug come from ROM.

Maybe It doesn't have the necessary libs and files. Maybe those flashable sounds mod can handle it.

If someone still with those bugs, for tests only,flash this http://xdaforums.com/showthread.php?t=1748803 (if you want to).

Or, try with ROM that comes with adio patches like Xylon.

Audio has never been so clear and loud. now its gone :crying:

I'm on 361, xylon 14stb, gsm gnex. no sound mod. just those build ins.

Tnx!
[Samsung Galaxy Nexus] osm0sis:
Oh god. Please edit out the images. I hated them the first time. ;)

Edit: Whew, nevermind. Saved by the page break. :p
[Samsung Galaxy Nexus] vigan_ks:
I just asked a question because in my old phone when i add any kernel first i tried a max. freq and then looking benchmark results. i asked only a question there is no need to talk to use words with f***ing
[Samsung Galaxy Nexus] mixtapes08:
That's fine atleast they know how many in here is disappointed to them lol

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Don't set it to the absolute max and act surprised when it crashes. Really it's only in there for crazy people benchmarking in front of air conditioners, etc.

You might be on to something... Maybe the kernel isn't for power users anymore and needs all sorts of idiot proofing. :rolleyes: In all seriousness though, nobody in their right mind uses 1.8GHz so maybe he really should make 1.7GHz the max since it's relatively stable (on the majority of devices).
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
Benchmarks? Digging yourself deeper man

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mixtapes08:
Your question is commonsense dude... Even a ten year old can solve that by himself.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] -star-:
Just an friendly advice: if you put your max frequency so high, never turn the thermal throttle off.
[Samsung Galaxy Nexus] vigan_ks:
Thanks for your advice and i never used my phone overclocked i used this just to look the pperformance on the borders just like i said before on my old phone galaxy fit s5670 i always tried on new kernels max cpu and now i bought a nexus and i did same that i did with my old phone but i didn't know that im killling my phone for that i asked a question. Thanks for your answer i will keep your advice .
[Samsung Galaxy Nexus] Craxx:
Hy kissme

For me in 360 it was fixed, but i changed to ak purity05 because of BETTER battery life. Smoothness is same;)

Craxx;)

Send from my Galaxy Nexus with Tapatalk :)
[Samsung Galaxy Nexus] osm0sis:
So I just played around with the settings in r361 a bit and interestingly enough the snappiness goes away if I change hsf to 1036MHz or, more importantly, if I put the max any higher than 1305MHz. Is it possibe with a wider range interactive has to work harder to know when to scale up and becomes less smooth? I've suspected something like this for awhile actually but now it's much more obvious.
[Samsung Galaxy Nexus] Puzzlegirl:
I would like to recommend you for Sainthood ;) :banghead:
[Samsung Galaxy Nexus] markop90:
No, you simply need an init.d script that remounts data and cache with discard at boot...

Write this in the script:

#!/system/bin/sh

mount -o remount,discard /data

mount -o remount,discard /cache

Save it, set permissions (rw-r--r--) and reboot
[Samsung Galaxy Nexus] osm0sis:
Haha thanks. Just another lazy Saturday morning of troubleshooting. :p
[Samsung Galaxy Nexus] The Gingerbread Man:
But couldn't you increase the timer rate or min sample rate to compensate?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] shawnaye:
in all honestly, is 1.7ghz really even necessary? i've never oc-ed in my life, probably due to the fact that i need my phone to last as long as possible and everything is smooth even on stock settings.

i'd just suggest max to be 1.4ghz or smth that has relatively similar voltages compared to 1.2ghz. as in, increase in performance without too much an increase in power usage.
[Samsung Galaxy Nexus] justibasa:
Bwahahahahahahahaha!

Don't like me........BITE ME!!!
[Samsung Galaxy Nexus] EddyOS:
Here you go...just as well I rename the ZIPs after I download them!
[Samsung Galaxy Nexus] kabauterman:
Ok, #13 seems to perform nearly perfect, but battery usage is a lot worse then on #12 :(
[Samsung Galaxy Nexus] Danthemanz:
Fair enough, the OC was listed right before the download link, didnt see it removed in the change logs.

Thats a pity, because i can clearly notice the difference, benchmarks aside...
[Samsung Galaxy Nexus] detritu5:
for me too. I have more deadlocks in #13 than #12. with the stock voltages

Enviado desde mi Galaxy Nexus usando Tapatalk
[Samsung Galaxy Nexus] nic85:
someone have edit conservative governor to another like interactive?

or set 350mhz minumum instead of 700mhz? for better battery life? ;)
[Samsung Galaxy Nexus] ro_explorer:
Guys, I have no issues with the battery.... it looks about the same as in #12.

// sent from my green robot //