yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] franciscofranco:
Answering a few questions:

1 - I don't use any apps on my Galaxy Nexuses, just the stock 10 or something preloaded apps

2 - I use Apple products, I have 2 MacBooks (company gave me one) and I have an iPad 3. crApple is crApple, but they make good hardware

3 - My personal device (the N4) has few apps as well, only the one I really need
[Samsung Galaxy Nexus] cryingrock:
I think Apple just makes good combination of hardware and system which runs on it.
[Samsung Galaxy Nexus] allgsmnetwork:
r360 is ok only 2 problems with info F.KU device does not report mV and the battery heats up quickly I use ROW
[Samsung Galaxy Nexus] chickentuna:
It will not report mV under fku app as the voltages are hardcoded now

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] allgsmnetwork:
after 1 minute with wifi and web and immediately to 45 ° the battery drops to the eye :(

---------- Post added at 07:46 AM ---------- Previous post was at 07:34 AM ----------

it is normal not to see the voltages?
[Samsung Galaxy Nexus] franciscofranco:
You can see the voltages in the voltages tab into Frequencies tab, just not in the Device Manager because that info came from SmartReflex. If you are seeing bad results with ROW change back to deadline, ROW is just experimental stuff.
[Samsung Galaxy Nexus] NinjaMic:
Probably a dumb question that has already been answered but:

Since this is where the 4.2 kernels are instead of the Verizon forum....will these work on my Verizon Galaxy Nexus?

Thanks
[Samsung Galaxy Nexus] calinoii:
Unfortunatelly the freezes are back:( I only disabled the MPU,IVA and CORE SmartReflex and I want to overvolt a little,just to test if my phone have that tiny little freezes because the quite low voltages franco uses in his kernel.Something close to stock voltages.What voltages should I use on IVA and CORE to be close to stock?

P.S: I have no apps installed,so it can't be an app that messes around,just got a fresh rom install with google image.
[Samsung Galaxy Nexus] Charmacas:
I would like to report something I noticed in comparison with 357 and 358. I switched back to 357 because of high partial wakelocks caused by AudioOut 2 and 3. With 357 they are there but never went so high. :)
[Samsung Galaxy Nexus] franciscofranco:
What kernel version are you running?
[Samsung Galaxy Nexus] calinoii:
r300 among with AOKP milestone 1
[Samsung Galaxy Nexus] franciscofranco:
I don't know about old 4.1, I don't give support for that anymore. You should leave that and upgrade to 4.2.1, its kinda pointless to stay behind :eek:
[Samsung Galaxy Nexus] Khizar:
Saw the post has been edited.. can you tell me what you changed exactly?
[Samsung Galaxy Nexus] calinoii:
You will say that I'm crazy,but that crt animation in 4.2 makes me sick...I also have delay when I press the power button,until the screen turns off and locks...If i will get this done i'll move to 4.2 xD

Edit: I'm going to flash aokp mr1 wich is 4.2.1 and r360,will report if I have that many little freezes on 4.2.1 aswell.Anyway,thanks for your great job with the kernel,really impressive.
[Samsung Galaxy Nexus] tribaleps:
Phone shuts down during phone calls

Flashed r360 this morning. On ROW and Westwood. Phone shuts down all of a sudden during phone calls. Anybody experienced this?
[Samsung Galaxy Nexus] Fenvarien:
No, everything is running rock stable here with r360. Try to clear f.KU data+cache and reflash the kernel to make sure that you are using stock settings.

GNex with franco.Kernel r360 / CM10.1
[Samsung Galaxy Nexus] neo-X:
r360 running super fast!!! Thanks Franco :good::D
[Samsung Galaxy Nexus] tribaleps:
Thanks...let me have a go at it.
[Samsung Galaxy Nexus] Khrushy:
This isn't important, just for my interest mainly.

Maybe I missed something about the phrase "hardcoded", but my voltages with 360 seem to still be set where I previously had them (I didn't bother clearing f.Ku).

Or is that just a reporting thing because 360 isn't reading its voltages from the standard files anyway, and is using internal values?
[Samsung Galaxy Nexus] Khizar:
if you dont clear FKUs data then your old settings will stick..
[Samsung Galaxy Nexus] calinoii:
Unfortunately Franco,the little freezes are messing up my device even on 4.2.1 with r360 interactive/row 1228/384 , 1036 hsf,with SR enabled,no undervolt or whatsoever. It slutters like hell on browser or when switching through desktop pages or appdrawer pages...no apps installed,just the gapps.
[Samsung Galaxy Nexus] Khizar:
just turn off crt animation if it annoys you
[Samsung Galaxy Nexus] Khrushy:
Normally, yes, and I purposefully don't clear most times to have it work that way.

My question is how that works with "hard coded" voltages, as mentioned about 360, because "hard coded" voltages that read your settings anyway don't seem, you know, hard :-p
[Samsung Galaxy Nexus] calinoii:
The animation is not the main issue here...but the sluttering and the freezes I have with any of franco's kernels :(

By the way,how I can turn off that animation:p
[Samsung Galaxy Nexus] Puzzlegirl:
Turn down the animator duration scale in Developer Options.

Stuttering and freezes? What's that then? ;)
[Samsung Galaxy Nexus] calinoii:
I set that animator duration off but nothing really happen,it's like before...and for example when I was scrolling down in settings,I had 2 tiny freezes,like for a blink and then another one. Many,many little freezes,i think those are called "sluttering"
[Samsung Galaxy Nexus] Puzzlegirl:
Sluttering? Lol. The GNex is so snappy, I sometimes think it reacts quicker than my N4 and there's no lag or freeze anywhere whatsoever.
[Samsung Galaxy Nexus] The Gingerbread Man:
Wow that's cool you find the gnex performs so well against the n4, I guess key lime pie will make better use of quad core.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] calinoii:
I know,right? Mine should be like that too,but seems that I have a problem with this kernel,which seems the best,I can't understand why I have this issue
[Samsung Galaxy Nexus] Puzzlegirl:
I know and the GNex now belongs to my teenage daughter who immediately installed all the crApps like Facebook and other battery suckers and plays games with it all day. I used to get over 5 hours screen time and she gets 2 - 3, but it's such an amazing, responsive device.
[Samsung Galaxy Nexus] Fenvarien:
The new magic sauce in r360 is just amazing, thank you Franco :) I had my GNex running with 1420 but now I use 1228 and it's as fast and smooth as before! Zero issues and perfect stability too :good:

GNex with franco.Kernel r360 / CM10.1
[Samsung Galaxy Nexus] osm0sis:
I keep rewording that ****ing warning nobody appears to pay attention to. :laugh: That and what it says in the edit reason at the top.

Update to JB4.2 and try r360-test. If you don't want to stick with it that's fine, but please do so for the sake of troubleshooting. :good: We're pretty much out of options otherwise.
[Samsung Galaxy Nexus] calinoii:
But I did,I just said in my last post :( I'm waiting for Franco,hope he will find a solution for me
[Samsung Galaxy Nexus] osm0sis:
Okay.. We're still pretty much out of options. :(

This is something that only happens on your device, which leads me to believe there is perhaps something wrong with your device. SR has never calculated wrong before...
[Samsung Galaxy Nexus] Angelakaro:
I'm very happy with r360! Just a question: i see that is possible to enable "boost" setting the value from 0 to 1. I notice also a noticeable performance boost,also in games,and a higher battery consumption. Can someone explain me how this boost value works? Thanks in advance

Inviato dal mio Galaxy Nexus usando xda premium
[Samsung Galaxy Nexus] The Gingerbread Man:
Have you tried a fresh clean install yet? As in wipe your entire phone including SD and start fresh, restore nothing.

Flash Google stock rom.IMG with fast boot, lock and unlock your boot loader then install your rom again but don't restore any apps or data (your SMS should be OK and call history and WiFi passwords titanium has an option for these).

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] calinoii:
I'll try to overvolt a little,could you suggest me some voltages for iva and core ?

---------- Post added at 02:27 PM ---------- Previous post was at 02:23 PM ----------

I did this a million times I think. I just flashed the image from google last night with fastboot oem lock/unlock also and now I flashed AOKP mr1 and franco's r360 kernel...no apps installed, only MX player to watch a movie :D
[Samsung Galaxy Nexus] The Gingerbread Man:
If your using 360 leave the voltage alone at least for the sake of testing which is what Franco wants, if you want to play voltages use 358 and even then I'd just leave smart reflex to do it for you. If you really insist you want to potentially have an unstable device then check out the link in osmosis' signature where he has put some info together which you might find useful

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] calinoii:
I want to OVERvolt not UNDERvolt :D I might found that my device doesn't really like low voltages:-/
[Samsung Galaxy Nexus] The Gingerbread Man:
I would just do a little a at a time, very small increments as you could fry your phones internals. Over volt is much more dangerous as you could cause damage with to much heat and electricity. With under volt the worst will happen is boot loop. Proceed very carefully

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] calinoii:
But the default voltage for 1200 MHz freq is like 1375mV :-/ and franco's using 1225 mV for the same freq. Would be dangerous to set that freq?
[Samsung Galaxy Nexus] The Gingerbread Man:
Over volt is anything over what smart reflex would use

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] whitedragonz83:
r360 feels great. Smooth and I think no noticeable battery life changes although, not your fault, I had a random case again with a"gps-lock" wakelock killing my battery overnight. The battery display just shows it as an Android System usage. Add normal, a reboot fixes it.

Also using ROW and like it a lot. Keep up the hard and great work Franco!
[Samsung Galaxy Nexus] osm0sis:
I don't know for sure but I think the stock nominals would be safe though. Which is why I suggested turning off SR. I wouldn't overvolt much more than that though. Definitely can be dangerous.
[Samsung Galaxy Nexus] calinoii:
So,would it be dangerous to set the default voltages ?

Ok,ill try this,how could I overvolt core and iva?
[Samsung Galaxy Nexus] The Gingerbread Man:
Probably not, probably being the key word, you'll find increased battery usage. I'd also image the same tolerance applies for too much voltage as for too little. I don't know if anyone less than than a texus instruments enginier could answer better than what me and os have said.

You'll find the voltage panel in francos app. Have fun but be very careful

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] calinoii:
I really don't know what voltages to use with the core and iva,i'll better wait for an answer from franco before overvolting them.
[Samsung Galaxy Nexus] shreddintyres:
Hey y'all,

I know back in the day mention of PGM was tantamount to heresy (reason i cant recall i think it held an inordinate amount of partial wake locks), but after the updates to the module i was wondering if anyone would care to comment on its use and affect on this kernel. I'm starting to test it for my personal use but just wanted to see what others might have to say .

- Cheers

p.s. i was hoping someone could tell me what the values for cpu voltages y'all are seeing on 360. I cleared fku cache and data and rebooted and still show voltages in fku>frequencies/voltages>voltages to be the same as they were in previous versions. otherwise with 360 i have noticed considerably less idle drain and a noticeably more responsive phone.
[Samsung Galaxy Nexus] allgsmnetwork:
exactly why risk it? back 348 is stable!
[Samsung Galaxy Nexus] Oscuras:
How do I flash this ? Through TWRP ? First timer here :D
[Samsung Galaxy Nexus] bigbiceps:
Yes brother. twrp or cwm...both will do.

Clear cache and dalvik before flash.

Then flash zip or image from SD card...

Sent from my ″®@$b€@Πj€\\y″ §Π€×

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

Fku app shows 358 is the latest....

How exactly did u guys get 360? :confused:

Thanks!

Sent from my ″®@$b€@Πj€\\y″ §Π€×
[Samsung Galaxy Nexus] Fenvarien:
R360 is stable enough and so is r358, the latest official nightly. Osm0sis tried to help another user with his advice, you don't need to overvolt :cyclops:

Please stop referring to r348 all the time, this doesn't help and it gets annoying!

GNex with franco.Kernel r360 / CM10.1
[Samsung Galaxy Nexus] joaquinf:
Wiping cache and dalvik when flashing kernels is totally pointless. There is no need to do that.

360 is a test version and it hasn't been released as a nigtly. That's why you don't see it on the FKU app. Francisco posted it here. It should be ten pages back

EDIT: here it is. I forgot to mention that all downloads are linked on the OP too
[Samsung Galaxy Nexus] prembox:
Yes, you can use TWRP or CWM to flash the zip from here....the highest number is the latest one. You'd wanna stick to R348 for time being...
[Samsung Galaxy Nexus] osm0sis:
malaroth actually reposted a write up from a TI engineer not that long ago. The effects of overvolting are mentioned if I recall correctly. calinoii should definitely hunt that down before messing around too much.
[Samsung Galaxy Nexus] allgsmnetwork:
As he wrote franco ROW stuff is experimental and should not use it .. r360 is as good as all the franco kernel but temperatures too high and no one sees in FKU as if SR does not work ...
[Samsung Galaxy Nexus] supernova_00:
That is the reason why we should use it, to test it out since it is experimental...that is why most of us follow the thread and install nightly versions of Franco's kernel :confused: The temperatures show up for me.
[Samsung Galaxy Nexus] bigbiceps:
Hmm.. I don't know what clearing both does. Someone had Told me to for it.....

What exactly does doing that do??

Sent from my ″®@$b€@Πj€\\y″ §Π€×
[Samsung Galaxy Nexus] rcazador:
What're the preferable settings for color multipliers, and gamma control to get away from the washed out look?

Will enabling the following cause damage to the hardware(even a small risk): Sound High Performance; USB Fast Charge; Thermal Throttle?

What do wifi_pm, OMAP Gamma interface, BLX, Trinity's contrast and Fsync?

These maybe noob questions but they aren't common in the roms I've seen so far. Thanks.
[Samsung Galaxy Nexus] TEK112:
I wouldn't say it is totally pointless. Wiping cache and Dalvik can allow a bootlooping device to boot, has helped in the past with no data after flashing a new kernel and other random issues. While the cache and dalvik cache do not directly impact the kernel they directly impact the programs that use the kernel.

The analogy would be saying that an oil change is pointless when upgrading the firmware on a vehicle's ECU. True, but an engine without its oil being changed eventually won't start.
[Samsung Galaxy Nexus] irminsul:
Dalvik cache is app related. Kernel is zimage and ramdisk, doesn't involve any app related stuff.

Rules of wiping:

When changing rom: data and cache (factory reset)

When updating ROM: dalvik + cache (although maybe not necessary)

When updating kernel: nothing

After taking a dump: your butt (for personal hygiene and happiness of your girlfriend)
[Samsung Galaxy Nexus] TEK112:
Don't forget to wipe system when changing a ROM. Orphaned data has the same negative impact as not wiping.

When updating a ROM a data and system wipe may also be necessary like so many of the AOKP builds.

There are no hard fast rules, you need to check the zips and changelogs to see what has been changed.
[Samsung Galaxy Nexus] Khizar:
+1 most ppl dont wipe system but i think its better to wipe it cuz not all roms have a script to wipe system before flashing the rom

actually it is useless i use to wipe cache and dalvik cuz it was pretty much a habit for me but... i stopped a while ago and have never had any issues
[Samsung Galaxy Nexus] rossrogers:
I've used PGM for longer than I can remember now. Sometimes causes horrible issues if you dirty flash a ROM and then try to use it. Recommend uninstalling before flashing a ROM update, then re-installing it again afterward. Avoids lots of potential headaches.

Other than that, I've only noticed issues with carrying the phone in thin pockets, the phone will rub on your leg and possibly register screen input keeping the device in a semi-wake state (I don't want to claim it is a wakelock or anything as I do not know). But this will eat battery like no other.

Long story short, PGM works fine for me and I've only had intermittent issues with unresponsive screen (after a dirty flash). And for me any battery life loss isn't a big deal as I don't notice it at all.
[Samsung Galaxy Nexus] bombadier:
On the 360 test build the new scheduler ROW is working fine for me but spoke too soon about the wired headphone levels,the ringer volume is fine but the in call volume still needs boosted,well at least for me

Tapatyping from my Nexus
[Samsung Galaxy Nexus] Sveke:
Why don't you guys just install the xlouder mod. It works perfect and my volume is totally fine.
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
Why don't you guys just get hearing aids??? :p everything sounds fine

Sent from my Nexus 7
[Samsung Galaxy Nexus] The Gingerbread Man:
I would be interested to see that if it can be dug back up again

Exactomondo, that's how progress is made

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Oscuras:
So guys I flashed version 358 over stock rom but there's absolutely no difference in my phone :eek: , also there's no new settings or anything, how do I use all those toggles and switches mentioned in the OP's post ?
[Samsung Galaxy Nexus] TEK112:
You have two choices:

1.) Buy the app

2.) Read
[Samsung Galaxy Nexus] Sveke:
You read and do some research first. Then you simply install a kernel control app or use term emulator. But since you asked this question I assume you aren't comfortable with term emulator so Franco kernel app or trickster will do the trick.
[Samsung Galaxy Nexus] Khizar:
what toggle? what switches? this is a kernel not a widget or app... the app to control it is on the playstore franco kernel updater, but i recommend you read and understand what you are doing before messing with settings
[Samsung Galaxy Nexus] apratomo:
R360, just wow! Google now loads up instantly. Trying with max freq 1036, row scheduler on cm10.1
[Samsung Galaxy Nexus] Oscuras:
Oh I'm such a blind idiot. It's in the second post. Sorry guys :silly: I'm gonna try volume boost now.
[Samsung Galaxy Nexus] whitedragonz83:
Almost no need to under clock. The patches keep the bulk of the speed below 1GHz anyways. Watch a CPU spy app and see for yourself.
[Samsung Galaxy Nexus] Sveke:
Yeah 360 with row is great over here. No sod no lags no issues.

Thanks Franco, this is a winner.
[Samsung Galaxy Nexus] Khizar:
+1.. it seems to be working great for me as well
[Samsung Galaxy Nexus] osm0sis:
No. Franco said it's experimental so try it out. If it's causing you problems then don't use it. r360 is faster than all the recent kernels, temperatures are normal, and the voltages not showing in Device Monitor has been explained at least 15 times including by Franco himself. Voltages are hardcoded in r360 so SR isn't enabled, meaning they won't display correctly and you can't adjust them yourself despite what the app says.

Searching the thread for malaroth posts should find it in no time. Definitely worth the read.
[Samsung Galaxy Nexus] jeetS:
360 working great so far. Super fast, like others have said google now loads much faster than before

had a good laugh at the script while flashing in CWM franco.:laugh::laugh:
[Samsung Galaxy Nexus] Tito2007:
Still getting the music pauses on r360 with 100% volume using Google play music.. Cleared f.k.u app data before flashing r360. Stock settings ..only changed color , enabled WiFi, and fast charging.

Bixies ROM

4.2.1

192-320 music
[Samsung Galaxy Nexus] Fenvarien:
Here you go :) http://xdaforums.com/showthread.php?p=34155147

GNex with franco.Kernel r360 / CM10.1
[Samsung Galaxy Nexus] gzub:
Possible Entropy Patch?

I was looking into this, and found an interesting kernel patch that was submitted to fix an issue with entropy disappearing: https://patchwork.kernel.org/patch/1745611/

Your kernel source still has the old get_random_bytes in binfmt_elf.c (not sure if the Android kernel uses this or not) but it appears to possibly be the source of the large depletion of entropy as every program that is launched would gobble some up.

Thought I would post it in case it could be solved in the kernel.

Geoff
[Samsung Galaxy Nexus] franciscofranco:
Thanks for that, I'm gonna test it!
[Samsung Galaxy Nexus] calinoii:
Why the hell does it stutters from time to time? Even when scrooling,switching desktop screens,watching a vid,playing a game...I tried many versions from franco's kernel,clean rom flash from google images,with full wipe and it still stutters. It's the only kernel that I have this issue with :( I want to get this done so baaad!
[Samsung Galaxy Nexus] mrdevil_25:
would it be possible that you have too many apps open that is eating up ram? so whenever the new apps need more memory it stutters trying to kill off other apps?
[Samsung Galaxy Nexus] threev:
360 running perfectly for 18 hours. Great battery and performance. Using Xylon 14 with interactive/ROW.
[Samsung Galaxy Nexus] calinoii:
No apps,just Mx Player,Subway Surfers and franco's app.I think those are 100% safe.
[Samsung Galaxy Nexus] xDARKFiRE:
R358 working great for me, no SOD, no problems so far :D
[Samsung Galaxy Nexus] UK_Wildcats_Fans:
I am using r360, and it seems to be doing really well.

I know that ROW is experimental, but just wanted to point out an issue with Franco Kernel Updater. I select ROW and then reboot. The Franco App says Deadline (default) is the IO Scheduler, yet if you click IO Scheduler ROW is shown as the selection. To select ROW, you have to choose another scheduler and then come back to ROW to get it selected.
[Samsung Galaxy Nexus] Wynnded:
I've noticed that the same thing happens when I reboot (Apply on Boot unselected) and use the app to reapply my preferred frequencies. FWTW :)
[Samsung Galaxy Nexus] doomed151:
I thought my fKu was up to date but when I checked, the latest version is 8.2.5 while the one in AndroidPIT app store is 8.2.2. Franco, can you give it a look? Thanks.
[Samsung Galaxy Nexus] irminsul:
R360, just wow!!!

This is so smooth and fast (testing ROW) it's the perfect kernel for now. Until Franco comes up with again something fresh and new for our Tuna :)

Thanks for the constant renewal of this device Francisco.
[Samsung Galaxy Nexus] osm0sis:
Yeah something funky going on in the app with selection at times.. f.Ku does that on my N7 with governor. I think it does select it, just doesn't display correctly until you select another first and then go back.
[Samsung Galaxy Nexus] The Gingerbread Man:
Honestly I don't know why your performance isn't so good, I'm using 360 and minco v6 192-1228 interactive with row and it's great, I guess you gotta find what works for you by experimenting and playing with stuff, try different roms or kernels and then playing with settings again to find what works best

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] UK_Wildcats_Fans:
Thank you. I was searching malaroth and couldn't find it. Now, I know why. It is JokerAce. It is a good explanation.
[Samsung Galaxy Nexus] osm0sis:
JokerAce on that forum, I think it was malaroth who reposted it here for us though. You're right though, I can't seem to find it in the search results either! Thanks Fen!
[Samsung Galaxy Nexus] Charmacas:
I can also say that 360 works so nice. No problems by now. I will report about battery life later. Thank you francisco for this great release! I am wondering what may be your next surprise. ;)
[Samsung Galaxy Nexus] osm0sis:
Works so nice that I forgot I was running fully default settings! I thought I must have had my max up at 1536, but nope, 1228. :) Truly impressive.