yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] The Gingerbread Man:
I do genuinely feel bad for you about you frying your phone, that really does suck. I guess maybe you didn't know all the facts and got all excited seeing you over clock an extreme amount. That speed was only ever meant for showing crazy benchmarks scores to your mates in a 'who's got the biggest' competition. We have to be accountable for our actions and while I feel sorry for you this should be a lesson to everyone here on this thread! I have asked at another place to see if Franco will remove 1.7 & 1.8ghz speeds (I don't think anyone uses it for daily use) and I myself only ever run at 1.2ghz. This would also make these games which run like **** on gnex because they think the gnex is an s3 by seeing it has up to 1.8ghz to be used run better as the correct graphics level selection should be made by the game. Any way we will see and its Franco's call, his kernel and so on. Sorry to hear about your phone and good luck getting it sorted.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Are you using the correct stock image? You need to get the one for your device - what are you toro (if I remember from your logs correctly)?

If you are toro, https://developers.google.com/android/nexus/images#mysid - then 4.2.2 (JDQ39). The file is a .tgz (.tar.gz) but some browsers download it as a .tar, rename it to .tgz once downloaded and it should unzip fine with the recovery and bootloader I think, then there should be another zip containing the rest of the images. Unzip them all. Then fastboot flash them exactly following the commands efrant's guide I posted above. All this I just wrote is in there too, so make sure you follow it to the letter. Good luck!
[Samsung Galaxy Nexus] misterk267:
Hey man, its all good. i knew the risks when i flashed. As a wise man once told me, s*** happens. And i mean, it might just be general hardware failure. No guarantee it was the high clock speed. I only had it running at that speed for a few minutes anyways.... Regardless, i want to thank everybody on this thread for your help.
[Samsung Galaxy Nexus] svengalis:
can anyone tell me how to imput these commands?

Sound Control:

echo i > /sys/devices/virtual/misc/soundcontrol/volume_boost

Replace i with 0-3 of your choice.

Sound High Performance:

echo 1 > /sys/devices/virtual/misc/soundcontrol/highperf_enabled - to enable

echo 0 > /sys/devices/virtual/misc/soundcontrol/highperf_enabled - to disable

USB Fast Charge:

echo 1 > /sys/kernel/fast_charge/force_fast_charge - to enable

echo 0 > /sys/kernel/fast_charge/force_fast_charge - to disable
[Samsung Galaxy Nexus] llevo3:
Thanks 1024x for osmod:thumbup:
[Samsung Galaxy Nexus] osm0sis:
They are Linux terminal commands, so you can enter them with the Terminal Emulator app if you want to play around with them, or if you mean on boot, then you put them in a shell script for init.d. Lots and lots of tutorials around on xda, and init.d has been explained in this thread many times. Search around and you'll find what you need. If you need any further help post in the Q&A section since it's just general Linux knowledge you're interested in.
[Samsung Galaxy Nexus] blsrbl:
Rebootes has gone with os version :good:. But the phone still randomly freezes! :(

I'm trying the zip file. The img file is not even working (I'm changing values in governor control then flashing it, the values don't change) :confused:

Edit : The img now is just working fine (Don't know what's happening). I'll see if the phone freezes with img.
[Samsung Galaxy Nexus] osm0sis:
Sounds like a random bad flash. It happens. :)

P.S. Dayummn page 4100! This f.K thread is a beast. :p
[Samsung Galaxy Nexus] blsrbl:
Sorry for off topic and maybe noobness but are you guys like franco and osm0sis somehow like Engineers or just learners from xda? :D:p
[Samsung Galaxy Nexus] osm0sis:
Franco knows a lot about coding and also took that in school, light-years ahead of where I am at; I'm more of a spare-time scripter. I've always had a bit of a knack for that even though I've never studied it in school and hadn't done anything with it for ages, and never on Linux. I mostly just picked it all up from xda since getting my GN a year ago. That and I know how to Google. :p
[Samsung Galaxy Nexus] blsrbl:
Mm.. So a part of this can be learnt in schools and universities. I expected that. I can't understand a lot of things and no even time to google or search xda. :rolleyes:
[Samsung Galaxy Nexus] misterk267:
So guys....no need to remove those high frequencies after all. Got home, replaced the battery, and she woke up like sleeping beauty. :D Still, i'll be more careful with my frequencies in the future haha...
[Samsung Galaxy Nexus] The Gingerbread Man:
Good, I'm glad it all worked out for you in the end! Still though I don't think it would be a bad idea to remove those steps as even though it might not be Francos fault that certain game development teams choose to detect device performance by looking for the highest possible CPU speed, removing those steps should allow these games to run correctly which imo would increase Franco kernel user experience more than saying I got 6 trillion quadrant score to their friends. Also Franco put a lot of time and effort into making all gnex handle the 512 GPU over clock for gaming purposes I can only assume, so by removing the extreme over clock steps these games should work much better without lag from very high graphics level processing being automaticly selected and people might enjoy the GPU over clock more. Then there's the thermal throttling which for those who don't understand basicly the devices attempts to save its self from suicide by slowing the cpu down as to not cook its self and if the temperate reaches 110 Celsius a reboot will happen in a last ditch attempt for the device to save its self! I might be beating a dead horse (going no where) with this but its francos kernel so his choice but i think more people use these badly coded games more regularly than extreme over clock which can only be performed in a freezer for 15 minutes tops
[Samsung Galaxy Nexus] thegtfusion:
Just use trickstermod app. Its free. ( if you dont wanna buy f.k updater ofc)

Sent from my Nexus Prime
[Samsung Galaxy Nexus] kecinzer:
osm0sis:

Can you please provide source of your RAMDISK that you use for osmod? I'm building franco.Kernel with ROM and I would like to include your patches inside.
[Samsung Galaxy Nexus] Kurre:
you could also just unpack it from boot.img which osm0sis provided. In ubuntu abootimg is easy-to-use software for that :)
[Samsung Galaxy Nexus] Angelakaro:
Strange thing happened twice (unfortunately i could not collect any log) i was trying to update two apps from play store: the first one was updated automatically and without issues,the second one was updated by me and this caused a freeze. When i rebooted my phone,the app which caused the freeze was still at its old version. I tried to update it again and i got the issue for the second time. Sorry if i can't help in a more efficient way

EDIT: i was using r372 osmod

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] Jerreth:
ok I got the information from better battery stats. I don't know how to decipher them though. I did notice it went from 100% to 86% overnight on my bedside table.
[Samsung Galaxy Nexus] osm0sis:
Thanks for the interest kecinzer!

Kurre is right, and for Windows follow the link to my Android Image Kitchen since that's how I made it in the first place.

All I modded was init.rc, init.tuna.rc and /sbin/fixtunapower.sh -> /sbin/fkbootscript.sh

Happy building! :D
[Samsung Galaxy Nexus] thegtfusion:
osmosis, i am running your osmod 372 version, but sometimes my phone freezes.

it happens when I go out, then when i come back and turn on wifi, and the notifications start coming the phone freezes for some seconds then goes back to normal. i use the stock settings, only my own colors.

any thoughts?
[Samsung Galaxy Nexus] osm0sis:
Well you saw what I changed; literally nothing in the scheme of things. Wi-Fi and all that of course are part of the kernel proper, not the ramdisk, so I haven't done anything to affect that. Do you encounter this with normal f.K r372? What scheduler and TCP CAA do you normally use? Has that changed since switching to osmod?
[Samsung Galaxy Nexus] thegtfusion:
I will test with stock unmodded r372 and report in a few days. I use westwood btw ;)

Sent from my Nexus Prime
[Samsung Galaxy Nexus] kecinzer:
Thank you.

Building right now :).

Hope all will work :).

Here are changes:

https://github.com/kecinzer/device_samsung_tuna/commit/7c16e7911727f6a354d9b5a11f4d85645f00bbb8

https://github.com/kecinzer/vendor_aokpk/commit/9b53037060b4f6ab9c5dde73839f905c90bdc993

I'm not sure about busybox in fkbootscript.sh, I don't want to add busybox when its in ROM.

https://github.com/kecinzer/system_core/commit/8de151f5da4bd6a634e77f06282825337c83c754
[Samsung Galaxy Nexus] osm0sis:
Just change the bb= in fkbootscript.sh to whatever path your ROM's busybox is at.

It also could conflict with whatever init.d I see you're adding and will definitely disable the sysctl.conf you've got, if left as-is. I'd go through all of those if I were you to see what you actually need. ;)
[Samsung Galaxy Nexus] kecinzer:
Just flashed. I have to say WOW! Definitely I can feel difference. We will see reaction from czech users of AOKPK :).

Thank you for great tunables osm0sis!
[Samsung Galaxy Nexus] franciscofranco:
r374:

* Merge new kernel.org incr patches

* Merge new winning values from the usual suspects!

* Hardcode the I/O scheduler values in ROW driver. If this works fine i'll do the same in the other I/O schedulers

* Fix a wrong backport code in r372

* Merge new Interactive patches from Google

Been running this build for a few days and no issues at all. Mr. Christian been also testing it for me and no problems that he reported. Really want this one to be good so that I can mark it as milestone.

Thanks for all the help from the crew, malaroth, osmosis, joaquin, gingerbreadman and the rest :)
[Samsung Galaxy Nexus] odavans:
what about vibration control?
[Samsung Galaxy Nexus] thegtfusion:
Awesome!

Shotting a tequilla on you now! Cheers :beer::beer::beer::D

Sent from my Nexus Prime
[Samsung Galaxy Nexus] odavans:
why?
[Samsung Galaxy Nexus] Efrenjr15:
So this 374 comes with osmod tweaks/tune ?
[Samsung Galaxy Nexus] osm0sis:
Looks like it worked! I'll send you another email with some minor changes/fixes before you go Milestone on us though. :)

Yup. Pretty much everything I put in osmod is in there. :o:D
[Samsung Galaxy Nexus] The Gingerbread Man:
I don't think francos updated tunables cfq yet to the winners. Also check out his deadline values, it feels even better than what we were testing!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Nah he just did row for now, all others are still at their original scheduler driver defaults. Haha that's why I was pointing to 500/5000/2/1/4 being like "**** we've gone wrong." :p
[Samsung Galaxy Nexus] franciscofranco:
Deadline has my original tweaked values yeah.
[Samsung Galaxy Nexus] The Gingerbread Man:
Back to the drawing board then with that one then lol I defiantly noticed the difference straight away with deadline
[Samsung Galaxy Nexus] osm0sis:
E-mails sent. Watching last night's Game Of Thrones with the girlfriend and a beer now. I'll check back later. :)
[Samsung Galaxy Nexus] neo-X:
Good job with the new tuneables. 374 feels noticeable smoother, great job & thanks Franco! :D
[Samsung Galaxy Nexus] osm0sis:
Wait until you feel r375 (..M5?); Francisco forgot part of our script. ;)
[Samsung Galaxy Nexus] Efrenjr15:
374 is running so smooth with sourcery 5.1.9.2 .

Thanks again for this amazing kernel, you to os lol your tweaks have gone everywhere on the forums lol.
[Samsung Galaxy Nexus] AzzaD:
take your time man, your high standards is what's made this kernel awesome! ;)
[Samsung Galaxy Nexus] lehoule:
Had enough ?

View attachment 871214

View attachment 871222

Thanks for the great battery life!
[Samsung Galaxy Nexus] winner00:
#14 looks to be nice. Wheatley and Gpu OC. Can't wait for it!
[Samsung Galaxy Nexus] ichijin:
I flashed the kernel 13.1 on top of my stock rom and it couldn't boot, I thought that was weird. Any ideas?
[Samsung Galaxy Nexus] superbobup:
are you running a 4.0.3 rom?
[Samsung Galaxy Nexus] ichijin:
Sorry forgot to mention it, but I am using 4.0.1, Kernel Ver. 3.0.1-ga052f63. Build Number: ITL41F.I9250UGKL1

EDIT: I guess it's that then LOL, it's right in the title
[Samsung Galaxy Nexus] yyz71:
It could be the rom! Does it ask for a password? You need to configure the password on your phone. Then connect to you're laptop type in the password boom hotspot. It works on mine :) cheers...
[Samsung Galaxy Nexus] franciscofranco:
Wheatley won't be included because I decided to drop C4 state patch. This explains why:

Funny thing that after I added the C4 patch some users complained to me that they were having random reboots and they had to revert back to #12. Coincidence or no, I added C4 for #13/#13.1, so I decided to revert it completely. In another end I decided to change how conservative works in its essence and I think I came with a pretty good solution battery/performance wise. More information on that coming soon.
[Samsung Galaxy Nexus] nrgaway:
I used 13/ 13.1 for a few days since this is my preferred kernel. But I did decided to load GLaDOS 1.4 a few days ago and I have had the BEST battery life I have ever, ever had (at 24% after 2 days and 14 hours). I have never had a reboot or anything strange on that kernel except the inability to run App Protector Pro, which the kernel developer is looking into.

I was hoping you would be including it in next kernel since I would like to switch back!

EDIT. PS I have WIFI on always as well
[Samsung Galaxy Nexus] sishgupta:
So in laymans terms (if you can call it that), the C4 state which causes the Memory Protection Unit to enter a deep sleep (OSWR - Open Switch w/ Retention) causes instability. C3 state puts the Memory Protection Unit in CSWR (closed switch with retention, a lesser deep sleep) which saves 2mA less power.

Why does colin call the instability a watchdog reset? At first I thought he meant the android app.

I'm all for more stability. I had the reset on #13 but not on 13.1 though maybe it is just a coincidence that it hasn't happened to me yet. Shame about the lost 2mA savings.
[Samsung Galaxy Nexus] Manafa:
Guys, please let me know how to get rid of this stupid gtalk? I never used it in my life and I never plan to do it, but I have partitial wakeloks from GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEdnpoind
[Samsung Galaxy Nexus] mariotme:
I think that wakelock isn't just for gtalk it also includes Gmail sync.
[Samsung Galaxy Nexus] :
Uninstall it with Titanium Backup..

Dan
[Samsung Galaxy Nexus] Manafa:
Couldn't find gtalk in Titanium backup. Found only Talk and freez it, but wakeloks continued
[Samsung Galaxy Nexus] ChosSimbaOne:
Open the talk app and sign out instead.
[Samsung Galaxy Nexus] Manafa:
I never signed in. Even never open this app at all.
[Samsung Galaxy Nexus] Shetlander:
Franco

Ive been reading Morfic,s thread and there is someone on there who looses data connection when the screen switches on. I too have this problem with all your kernels, when the screen wakes up I can have full bars then over the space of about 5 seconds it goes to none and sometimes "emergency calls only".

Any idea if this is caused by radio issue or is it kernel related. Im on 13.1 and baseband UGKL1.
[Samsung Galaxy Nexus] ChosSimbaOne:
I'm always experiencing that it auto sign in after flash, so maybe that had happend to you too?
[Samsung Galaxy Nexus] clefster:
How long were the wakelocks? On my phone it's hardly anything so I doubt it's causing you much battery usage at all.
[Samsung Galaxy Nexus] dyndragon:
Maybe run a test? compile #14, one with wheatley+C4 sleep, one without? Let's see how bad the instability is?

Personally I never got any reboots on #13 or 13.1, but I'm just one person...
[Samsung Galaxy Nexus] arhung:
Can I still use the osmod-372 for the r374?
[Samsung Galaxy Nexus] The Gingerbread Man:
I hope Google them selves get wind of this **** , seriously I'd love to see this being their defaults for io schedulers from our testing! There is more to come yet!
[Samsung Galaxy Nexus] osm0sis:
No that's not how it works. You can use the init.d script though; I've uploaded a newer version (16-Apr-2013) now. Once Francisco hardcodes all our current finalized numbers the script won't be needed either, at least not for anything but deadline (until we finalize that). :)

Actually, I just took the tuna osmod down in light of all this great news.

If memory serves, the original upload from Easter had 156 total downloads, and as I removed it "take 2" had 217. Wow! Thanks folks. :D Not bad for a week each and word of mouth! ;)

**** yeah! :D As long as they give credit to Team Franco. :p
[Samsung Galaxy Nexus] The Gingerbread Man:
Seriously now, Franco has pretty much as higher rep as it can get so if these various tweaks and optimizions around the io were to find their way to say JBQ from Franco, who I'm sure would at minimum pass our findings to the relevant dept within Google possibly these crazy ass numbers could filter them selves through more devices than originally expected!

Its really cool to hear from the other guys posting here devs from other devices are using the data we have collected to use, the word really does seem to be spreading and it makes me feel special to be a small part of the big wheel turning with the stuff we as a group are doing :)
[Samsung Galaxy Nexus] franciscofranco:
Unfortunately it doesn't work like that. They will use the defaults from upstream kernel, which means CFQ and the default values. And to send them something like that, which I could do no problems, I would need strong data and tests to back it up like hell. The corporate bureaucracies are hell.
[Samsung Galaxy Nexus] Khrushy:
My dreams are crushed. Crushed I tell you.:silly:
[Samsung Galaxy Nexus] TheMysteriousOne:
I noticed you guys changed cfq group_idle from 7 to 0.

Is this one of those values which automatically get changed like 12 and 10 in row got changed to 2 and 15?
[Samsung Galaxy Nexus] osm0sis:
Nope, that's "we changed our minds." ;)
[Samsung Galaxy Nexus] Spoderman:
So, in the 374, are the winning tunables for deadline hard coded in?

I know the row ones are :)
[Samsung Galaxy Nexus] osm0sis:
There are no winners for deadline currently. Only row is hardcoded in r374.
[Samsung Galaxy Nexus] Gafanhotz:
Just a tip guys, never play of "tuning your phone" while drunk. I found that my phone was using CFQ, for a lot of days now, since I played with it while drunk. Now I've set the i/o sched to row and saw why I was feeling my phone slow... And I though it was alcohol effect! xP

By the way, r374 feels a lot more better with row hardcoded in it, feels better than stock AOSP! :good:
[Samsung Galaxy Nexus] Degrated Shadow:
Franco your kernel has always been better about smoother and rrsponsive UI.. But i fail to use it because of some games.. I tried ak kernels.. UI wasnt as smooth but Real Racing 3 worked well. I tried your 374 it lags in subway surfers and real racing 3 as well. I once again flashed ak v99 diamond. Saw that games worked well. It ensured there wasnt a probkem with the game. I again flashed r374 but its just lagging in games. Any way to tweak it so that it works well with the games. No over clocking stuff please..
[Samsung Galaxy Nexus] Bonvaz:
Guys sorry if I'm a noob but I'm using the r372 osmod version and it feels great, smooth like never!!!I just want to ask how I can use r374 with the same settings and mod.. Thanks

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] whitedragonz83:
Franco. Thanks for fixing the bug that prevented io information from being read with System Monitor. ROW tuneables are sick.
[Samsung Galaxy Nexus] blsrbl:
So is Real Racing 3 working on 374? Despite the lag.

---------- Post added at 03:00 PM ---------- Previous post was at 02:58 PM ----------

You don't need the osmod version anymore. Just flash the r374. It's smooth and great.
[Samsung Galaxy Nexus] Astug:
I tryed both AK and faux in the past week and even with the winning tunables and similar settings as f.K. on those kernels, nothing feels as smooth as f.K.

I noticed alot of sluggish animations and so forth.

Thank you franco, your's is truly the best for my phone.
[Samsung Galaxy Nexus] Degrated Shadow:
Nope.. It just entered the nenu where we choose series. Then my phone went complete black. From next time it didnt even enter the menu
[Samsung Galaxy Nexus] bigknowz:
deadline changes

osm0sis, checking to make sure the deadline tweaks in the new 950io are correct - read_expire / write_expire changes are relatively large, from 3500 / 750 to 350 / 2750.
[Samsung Galaxy Nexus] osm0sis:
Yup. We're experimenting pretty drastically right now. It would be helpful if you could tell us how they compare. That's why I keep changing them. ;)
[Samsung Galaxy Nexus] arhung:
So that the osmod and the 950 script are not needed anymore except I use the deadline schedule:confused:

p.s and how about seeder?
[Samsung Galaxy Nexus] bigknowz:
Changing deadline

I'm on it, will have thoughts tomorrow.
[Samsung Galaxy Nexus] marcocsh:
374 is super!!! Skip when listening to FLACs, cured. Lag when installing apps, cured!

I love FK!!!
[Samsung Galaxy Nexus] osm0sis:
This question about osmod/950io has already been answered by myself twice in the last 4 pages, please read back.

As for Seeder, it was never needed and is kind of artificial in its "fix"; we've increased the entropy pool by a small amount as that seems to help with rand read+write speeds. This is more like sEFix. TL;DR - uninstall Seeder, we've now got you covered for the part that matters.
[Samsung Galaxy Nexus] timbck2:
By the way, Franco, the new Holo style interface on the F.ku app is gorgeous, and I like the new arrangement of the menus! Thanks for the continual improvement of a great kernel and tuning app! I use it on both of my devices, it's the only kernel I've used in several months, and I hope you develop for my next device (whatever that may be).

Sent from my grouper or toro
[Samsung Galaxy Nexus] P30SiNa:
r374 is super smooth! :good:
[Samsung Galaxy Nexus] The Gingerbread Man:
My previous statement explains this

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

Make sure you get a nexus then ;)
[Samsung Galaxy Nexus] dipenv:
Quick Question..

Few Doubts - .. I am on Stock+Rooted+Deodxed 4.2.2

1) Can I flash the r374 nightly without doing major damage ?

2) (Generic Question, Not related to Franco)Anyone aware if I can get an Extended Power Menu Mod for Stock Rom?

Thanks in Advance.. !!
[Samsung Galaxy Nexus] Langduscher:
1 - Yes

2 - There used to be one for 4.1, search for it and try it after making a Nandroid. If you want to use it to reboot to recovery and bootloader, you might also want to check out Francisco's app Quick Reboot in the Play Store. That's what I use on my tablet (no such options in the Power Menu, this app works fine).
[Samsung Galaxy Nexus] Hatshipuh:
Franco Updater on Androidpit is still at v8.8.2 while v9.2 is out on Play Store.

It's kind of sad to see that Pirates update faster than an legit App Store...
[Samsung Galaxy Nexus] Bl4ck3urn:
Play Store = Pirate Store?? lol :eek:
[Samsung Galaxy Nexus] ChazzMatt:
I guess I don't understand your point. Nexus phones/tablets are OFFICIAL Google Android developer phones/tablets, so the official Google Android store (Play Store) should/would always have updated apps for the Nexus devices first.

Are you saying my Galaxy Nexus phone is a pirate phone or Nexus 7 tablet is pirated? :confused:
[Samsung Galaxy Nexus] Angelakaro:
He's just saying that pirates maybe update their apps faster than androidpit, not that play store is a pirate store. Come on guys, let him breath ;)

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] Sik-1:
We are letting him breath, his choice of words tho????? Not so much:p