yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] shawnaye:
Noobs come in here and think oh, i've got an Android phone, i must UV the crap outta this chip. But when they do so without even know the consequences, it's just plain retarded.

Yes, we can see it from another point that this allows them to learn from their mistakes. But seriously... UV~ing doesn't make that much of a diff.

I honestly hope for genuine improvements in franco's kernel and from now on, if i were to test new kernel releases, i'd use em for at least a day with stock settings and see if anything messes up.

I FEEL EVERYONE SHOULD BE DOING SOMETHING SIMILAR AS WELL PLEASE.
[Samsung Galaxy Nexus] osm0sis:
There is a standing rule in some other kernel threads: If you report a problem you better be using stock voltages and say so or the dev will simply ignore your post. Perhaps the same policy should be added to the OP here.

I proved that app is useless since I can run it with known borderline voltages on my device and it doesn't force a freeze. Yet I was later able to freeze it with those same borderline voltages just web browsing and through normal use.
[Samsung Galaxy Nexus] kecinzer:
Raised min freq from 192 to 384 and no sod since then. I done many things with phone and it seems to be stable.

So my problem on 356 kernel was min frequency.
[Samsung Galaxy Nexus] malaroth:
Zip. Back to the sidelines for me. Thanks for your help osm0sis

JBSourcery 4.1 Franco 356 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] yellowdie:
Good to know. What was your 192MHz voltage at? :)
[Samsung Galaxy Nexus] llevo3:
Thanks for letting me know, though r356 running smooth w/o SODs and freeze :o
[Samsung Galaxy Nexus] kecinzer:
I never touch voltage settings. So it was default.
[Samsung Galaxy Nexus] Ridho1:
Franco, will you add 384MHz of GPU in the next version?
[Samsung Galaxy Nexus] allgsmnetwork:
I did not ask anything, I ask that you read? I just expressed my opinion of the first events I noticed that the new kernel does not support UV I was the least I tested it and I told the truth do not get mad too ... in a democracy, no freedom of expression !!!
[Samsung Galaxy Nexus] malaroth:
:LOL:

JBSourcery 4.1 Franco 356 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] yellowdie:
Bro, nobody can understand you. I'm not trying to be mean, but your posts are getting kinda annoying. Honestly, I don't want to come across as angry, but you should be using http://translate.google.com so that you can write in your language and we can figure out what you're trying to say. Most of your posts are just getting skipped over or making people confused/annoyed. I'm sorry to have to tell you that. And by the way, this is NOT a democracy. It's a development forum. Very different.

:)
[Samsung Galaxy Nexus] malaroth:
Before he has to say yet again.... NO. 512 is it.

JBSourcery 4.1 Franco 356 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] allgsmnetwork:
I use google translate is that the Italian language has too much grammar I will try to write more succinctly I hope he understood...if you wrote in Italian who knows what I'd understand :)
[Samsung Galaxy Nexus] llevo3:
even the kernel development forum can be funny :)
[Samsung Galaxy Nexus] ethraza:
OTG?

Hi everyone!

Is USB HOST working with franco.Kernel #356 on JB 4.2.1?

When I got my Galaxy Nexus with ICS I remember that I plugged my mouse and it just worked. But since I'm running Bigxie JB with franco.Kernel I never saw it working again.

Am I missing something?

Thx
[Samsung Galaxy Nexus] malaroth:
I dunno... osm0sis is in canuckland but I don't know if it's the Frenchie part. But that's close to eyetalian isn't it? :P

JBSourcery 4.1 Franco 356 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] joaquinf:
Post edited
[Samsung Galaxy Nexus] Paragon_X:
Look I'm not going to even try and interpret this post, but I'll wish you good health lol
[Samsung Galaxy Nexus] allgsmnetwork:
To test I flashed 356 kernel with the same settings UV 348 with set on boot and so far no reboot and I found myself obviously the same settings as voltages 348 with UV osm0sis + 25mV I had before hope nothing happens ... are already about 30 minutes, 3 benchmark with antutu always 9500 point, web, phone calls and other ... before UV immediately restart maybe SR has done its job as 348 :eek:

Setting frequency 384/1536.

I hope you understand, I will write updates with UV stable if it is...
[Samsung Galaxy Nexus] Angelakaro:
D: are you keeping icy bottles of water in December?? God may save you
[Samsung Galaxy Nexus] franciscofranco:
OTG works fine.
[Samsung Galaxy Nexus] Ridho1:
Is there a reason? I mean I see some mecro lags in games. Which not happened on trinity. :(
[Samsung Galaxy Nexus] joaquinf:
They come really handy if you take them out of the freezer a couple of hours before serving. Weather can get very hot in this time of the year in my city, plus reusing plastic bottles is very ecofriendly :)
[Samsung Galaxy Nexus] franciscofranco:
Define micro lags. Lags you can see and nobody else does, or lags even a elderly person can see?
[Samsung Galaxy Nexus] rolear8:
I added 25 mV to the 192 MHz and so far no SODs.
[Samsung Galaxy Nexus] Ridho1:
Okay, I just read at some previous pages that says the 512MHz makes some games like NFSMW detects Gnex as an high-end phone. Tested few games and compared with other kernel and just I feel there are micro lags. Actually I am afraid if it is only placebo so forgive me if I am wrong and correct me. Let me know why will not you create the 384MHz version? Sorry for asking franco.
[Samsung Galaxy Nexus] osm0sis:
NFS does that even with 384. It's not the GPU, it's the CPU OC slots its detecting. Nothing else in the world does that or does it like that; NFS is just a poorly written app.
[Samsung Galaxy Nexus] mikeandjaimie:
There was a 384 previously, and there was almost no difference in power consumption, yet stability and performance are the same or increased. The problem with lags in that and other games is because of theoc'd cpu steps as has been explained before.
[Samsung Galaxy Nexus] teriemer:
I love you mann ;) LOL
[Samsung Galaxy Nexus] malaroth:
...define elderly?

JBSourcery 4.1 Franco 356 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] drnejo:
I'm trying to write without Google Translator or similar, sorry if it doesn't like you but this is a development forum not a grammar class.

Btw, I know the difference between freeze and freezer, only was a typo error.

Enviado desde mi Galaxy Nexus usando Tapatalk 2
[Samsung Galaxy Nexus] osm0sis:
It was a joke bro. Chill out.

... see what I did there? :p ;)
[Samsung Galaxy Nexus] Angelakaro:
I think that noop I/O scheduler reduces most games lags. Try and see yourself,maybe i'm wrong

Inviato dal mio Galaxy Nexus usando xda premium
[Samsung Galaxy Nexus] drnejo:
Maybe but I don't like that kind of jokes.

Enviado desde mi Galaxy Nexus usando Tapatalk 2
[Samsung Galaxy Nexus] Vybramo:
356- low call volume >< older one work best
[Samsung Galaxy Nexus] vrehenriqu:
Just a feedback on r356. Running it since available and so far no issues to report. Music, navigation, Facebook, flipboard, tapatalk, everything running fine.

No SODs to report.

Very good battery life!

Kernel is running with default settings, with 192mhz min frequency and slight uv at this frequency.

Just one issue that bugs me but could be related with the rom: Bluetooth is not working properly with the car hands free. Sometimes is not even pairing...
[Samsung Galaxy Nexus] malaroth:
NFSMW is not Franco's app. The lags aren't even necessarily the kernel. Check your background app, cache. I just played 25 mins straight with no hiccups deadline i/o 1306/384 and guess what...

It barely jumps above 729. So maybe criterion has a forum to post on? Great work Franco. Loving the reliability of your kernel!

JBSourcery 4.1 Franco 356 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] sajty:
"heats up" - how many degrees?
[Samsung Galaxy Nexus] malaroth:
Thermal throttle keeps your phone from frying the chip. If you turn it off it will heat up and lag MORE

JBSourcery 4.1 Franco 356 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] yellowdie:
lol. But we thought it was funny. :p ;)
[Samsung Galaxy Nexus] knightmedz:
Yes though I agree that this is a development forum and not a grammar class, I think we still need to put a little effort on how we convey things here. As they say, "communication" is the key. Same as you, english is not my first language but I always try to make my posts clear to others as I can. For me its another way of showing respect to other forum users.

Getting back to topic... Been running r356 for a few hours now without any issues. Stock franco kernel settings running on stock takju. Had a few freezes with the same configuration in r355. Will report back in the next few hours.
[Samsung Galaxy Nexus] Edgarngg:
Poweramp 320kbps mp3

No underv.

Min 537 max 1612 dyinteractive deadline

After a while of listening.

Besides that no modification. What else info do you need man? :)

thank you for you excellent kernel! I'm loving it thank you very much Francisco.
[Samsung Galaxy Nexus] calinoii:
About 65~68. In fact this is not only when it heats up...
[Samsung Galaxy Nexus] sajty:
68 is quite a lot.I think,that slowdowns are normal behaviour of phone to prevent some damage.
[Samsung Galaxy Nexus] lsv-1:
Something particularly strange happened to me a few days ago with version r348, a friend if mine borrowed my phone to play cut the rope, the battery was at 30% or so, the battery drained normally until the phone died. As soon as I got home I plugged the phone, let it charge for a while then I turned it on, when it was starting apps the phone rebooted by itself and got stuck at the nexus boot logo, tried to flash a different kernel, clear the caches, reflash the rom, nothing, only a factory reset could bring my phone back.

I do not know if this had to do with trickster mod (someone mentioned it a few posts back) or the kernel or the combination of both (something tells me that maybe the fsync being off by default along with trickster mod boot could've caused this) just be careful guys, and do not let the phone run out of battery.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] sajty:
Cut the Rope is strange game.Sometimes crashes,with any kernel or ROM,doesnt matter.No app doing this for me.
[Samsung Galaxy Nexus] drnejo:
I agree with you, I'll try to make my post as clear as possible but don't kill me for a little mistake :good:

I also back to topic, the kernel is working perfectly after a few hours, no failure to report. Battery consumption similar to r348 (1,5%/hour in idle)

Regards
[Samsung Galaxy Nexus] joaquinf:
I apologize, i didn't mean to offend nor "kill" you and i wasn't trying to teach you a grammar lesson either. It was a joke, simple as that.

You need to chill (see what i did there :p .. nah i'm just kidding) I'll take down the post, no worries :)

EDIT: the post is gone for good, you might want to edit yours where you quoted the previous one with the pic
[Samsung Galaxy Nexus] ffgf:
Hey wait I thought he was talking about this freezer

View attachment 1596649

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Khrushy:
Errrr . . this is going to sound weird, but is there any way to disable the new volume boost? :p

I have to listen on the lowest two settings to keep my eardrums intact. My headphones were always pretty loud though (which is why I liked them). :-p

Also, side note, but I realised I've only ever suffered a SOD when I've been using 192 min. Since i switched back to 384 min I've been SOD free.

Oh, and yeah, Not a problem with 356 in the ~12 hours I've been using it. I approve.
[Samsung Galaxy Nexus] calibachrome:
r356 is running great. Fastest one yet. However I've had a few freezes since install.
[Samsung Galaxy Nexus] shreddintyres:
I had 2 freezes recently on 356 otherwise since release it has been perfect. Im only overclocking to 1305 otherwise all settings are stock (exceptions: TCP algorithm and color settings). I had to do a battery pull to restore device functionality, as such was not able to pull logcat or last_kmsg. I am about 99.99% sure the freeze is attributable to the NFS game that everyone here has agreed to was buggy, the interesting part or the part i think is interesting any way is that it happened not while running the game but rather while downloading the extra install package while on wifi. Wifi was on 2.4ghz band, WPA2 personal full strength using Linksys 4200v2 router, and TCP algorithm set to westwood.

Im fairly certain that the cause was the game but nonetheless because it happened twice in successive reboots i thought id mention it.

Keep up the fantastic work franco have to say this is the only kernel i run any more. 356 seems perfect otherwise.

- Cheers.
[Samsung Galaxy Nexus] drnejo:
Only a Super Sayan can beat this Freezer :p

Enviado desde mi Galaxy Nexus usando Tapatalk 2
[Samsung Galaxy Nexus] dandyqb:
i think im lucky enough not to encounter this SODs in r356 even with 192 as my min and 1305 as max, all in default voltages and SR enabled :D
[Samsung Galaxy Nexus] superbobup:
yup, i know it's because of my DPI but other apps (XDA for example) still allow me to download/update without the "device is not compatible" error. i will check out the density app and market fix though, thanks
[Samsung Galaxy Nexus] kecinzer:
That is interresting, because, if I try Glados or Lean Kernel, I don't have any lockscreen lag with auto brightness, so on my side, it's kernel related.

But this is only one thing as cons of this kernel. Everything else is great. This is the fastest kernel that I ever test (speed, battery life, features).
[Samsung Galaxy Nexus] eriksengh:
Thanks, but still not working here. Anyone else on bigxie rom experiencing this?

OC and governor works, but are reset on reboot...
[Samsung Galaxy Nexus] slg60:
Hey Franco, can you please answer?
[Samsung Galaxy Nexus] jhericurls:
I managed to get mine down to

1150, 1025, 875 and 775

from the default:

1200, 1100, 1000 and 900

Note: I'm not using the 1350 slot.

I ran a stress test, played a game (GTA) and a bit of web browsing and its rock solid.
[Samsung Galaxy Nexus] franciscofranco:
I'm sorry, it must be a rom issue, I don't have that problem whatsoever and I tested it like 10 times before I made this post.

I can. GPU is stock clocked, no difference performance wise between OC or stock and I couldn't create a sysfs interface with the limited time I had, but it's something I'm looking forward to try again in the near future.
[Samsung Galaxy Nexus] incomer:
Try to set remove mnt for sdcard.. That fixed it for me..

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] jan-willem3:
Anyone problems with init.d I just cant find out why it is not working. Init.d is kernel related right as far as I know I checked the permissions then times even created an sh script in the system/etc folder wich gives the instruction to run the files in the init.d folder.
[Samsung Galaxy Nexus] connexion2005:
$20.00 Donation Sent. Amazing work buddy I love the kernel and have used it from day one getting my Nexus S...

0DC40419DL328940A
[Samsung Galaxy Nexus] Roman-Kumori:
Francisco, thank you for your kernel, nightly #13 is f*cking great!

First time I set a live wallpaper and don't experience lags. First time. And this is awesome. Thank you very much.

I liked darker interface of your app more than light one though.:rolleyes:
[Samsung Galaxy Nexus] dpaine88:
Heya Franco, do you personally use the hotplug option?

Are there any drawbacks we might experience from enabling it? I have not seen any posts about Sleep of Death, unlike the Imoseyon kernel which they seem quite common.
[Samsung Galaxy Nexus] dyndragon:
Im down to:

1225, 1125, 1025, 875, 750 and still going to test to see how far down I can go.

Edit: I'm not overclocking, so I'm not using the 1300mhz slot
[Samsung Galaxy Nexus] tristan202:
I hope you haven't forgotten about the cifs module. Hope you are well settled in your new house.
[Samsung Galaxy Nexus] illcat2000:
Great job thank you again runs great on every from I use no deep sleep issues others blame on the kernal.
[Samsung Galaxy Nexus] eriksengh:
Thanks for trying. Will flash another rom to test.
[Samsung Galaxy Nexus] pa.pn2:
how does the undervolting feature work in the app?

if i type in a different voltage at for example 1200mhz its not shown somewhere

i can type it into the box but cant see the new voltage in the box

isnt it shown somewhere?will it just be saved into the init.d folder?
[Samsung Galaxy Nexus] Felixpau86:
Feels like consumption is up. Anyone else draining quicker?
[Samsung Galaxy Nexus] versd:
no issues so far, deep sleep mode active. i dont use the overclock setting.

youre right there is a lag when applying undervolt settings, i undervolted 50mv across the board and 100 on the lower end. seems stable so far. probably wont go too much more aggressive on the undervolt. just got my new gsm extended battery so will see how it goes before i start undervolting more.
[Samsung Galaxy Nexus] Stretlow:
How do you check if it goes into deep sleep mode?
[Samsung Galaxy Nexus] Vangelis13:
I think so too, screen off consumption seems to have gone up a bit. Ach, let it settle & we'll see.
[Samsung Galaxy Nexus] apratomo:
Smooth kernel on r356, haven't got any reboots or sod so far since installed.

I'm a bit concern about the heat generated, I was only going through Google Reader and xda app for roughly half an hour, but the temp rising up to 68 Celsius.

I did checked cpu spy, usage was normal. I'm using 384-1024 freq with CFQ - interactive combo, no uv or whatsoever.
[Samsung Galaxy Nexus] alfiemenace:
I'm on r348, uv'd -100mV on all frequencies and I'm fine. Is it bad or not? In the long run I mean

Stock ROM, custom user.
[Samsung Galaxy Nexus] sruel3216:
Franco, just curious did u do something to sound? This is blasting after i came from 355 to 356
[Samsung Galaxy Nexus] _chanstar_:
Check Post #36400.
[Samsung Galaxy Nexus] threev:
No challenges at all on 356 at 1.4ghz. Running Xylon 14.
[Samsung Galaxy Nexus] malaroth:
Yes... the screen seems to lock up if you don't keep it active. I found tabbing home them back to download worked around that on download

JBSourcery 4.1 Franco 356 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] joaquinf:
yup. It happened to me on 348

What a crappy game. We have to do all sort of tricks to have it running at a decent fps and now this.
[Samsung Galaxy Nexus] markop90:
FSync off? I understand.. Maybe when the phone died your data were corrupted..

So you must say "don't set FSync off" not "don't let the phone run out of battery" :P
[Samsung Galaxy Nexus] Khrushy:
*Ignore this ****, I was a dirty noob and messed up a ROM setting*

Errrr. . . ok, weird, apparently 356 is giving me random reboots. According to my battery I've restated 3 times in the last 4 hours. I didn't notice (wasn't using phone at all).

I'm going to flash back to 342 for now - I'm in transit to Europe for the next 20 hours or so and want a stable phone, but after that I could potentially reflash 356 and run a logcat on it if that helps. No chance of pulling a kmsg till I get back in a week or so though.
[Samsung Galaxy Nexus] haxor:
Thank you so much for this wonderfull guide for noob like me :D pressed thanks
[Samsung Galaxy Nexus] mikeandjaimie:
Hey people who are getting SoD I think I found a way to not need to batt pull.. Try plugging in your phone... It makes screen come back.. At least when I thought I had 2 sod today I unplugged it and the screen woke up when it wouldn't respond to button presses.. Maybe I just lucked out or it was just not completely dead.. But give a test and report if works or not. I'm gonna try anytime I get it.. Could just be me imagining things lol
[Samsung Galaxy Nexus] osm0sis:
Yup sometimes plugging it in will work, sometimes not, in my experience anyway. With these JB4.2 SODs sometimes doing multitouch actions on the screen while pressing the power button works too. Let's hope all this **** gets sorted in Feb. with 4.2.2. :good::)
[Samsung Galaxy Nexus] pranavhooda:
[Help]

I flashed franco milestone 4 using the "franco kernel updater free app", I used auto-flash and now I m stuck at boot logo screen....

need urgent help!!

Thanks in advance.....!!!
[Samsung Galaxy Nexus] galakanokis:
What version of ROM are you using? There are no milestones for 4.2. Perhaps you have an incompatible kernel and ROM?

Boot into recovery, wipe and flash again. Make sure you have the proper files before flashing again.
[Samsung Galaxy Nexus] pranavhooda:
I m on stock 4.2........[ok now I know what I did:eek:]

and i m a n00b in flashing a kernel, can you guid me how to flash it using fastboot or adb.......
[Samsung Galaxy Nexus] SpecRek9:
My gf had two reboots with r356 today.
[Samsung Galaxy Nexus] allgsmnetwork:
Nothing to do three restarts in the evening, I changed the voltage to + 25 mV and all night during charging 4 restarts the text with the stock voltages leave work SR.
[Samsung Galaxy Nexus] galakanokis:
The command is

fastboot flash boot /path/to/<boot>.img

With the path being where you have the kernel living on your pc and the .img is the name of the kernel file.

Or if you have a custom recovery you can flash the zip.
[Samsung Galaxy Nexus] SpecRek9:
I just realized GN clock doesn't updates every minute :confused:, could this be kernel related?
[Samsung Galaxy Nexus] galakanokis:
Let me get this straight, you are over clocking and under volting and are still complaining of stability issues?

356 is rock solid, no issues whatsoever. Have you put voltages back to stock? What app are you using to control the kernel? Have you cleared the apps data before a kernel flash?

A few steps to take to trouble shoot on your part. The problem is not the kernel.

G
[Samsung Galaxy Nexus] haxor:
Learned lot of thing about UVing an all from this thread my question is if I am not using 192 mhz as min frequency so should I UV of this frequency too ? and should I leave SR enable if I am manually putting UV ?
[Samsung Galaxy Nexus] prembox:
@Franco- All of us using your kernels are safe on the below issue posted by Atl4antis??? is this issue taken care of in our Kernels?? I'm presently on FKU controlled R348. Or we need to take some precautions??? flash a patch etc???
[Samsung Galaxy Nexus] allgsmnetwork:
Maybe I expressed myself badly, I'm not complaining I had a 348 with UV and I flashed the 356 and the values ​​have remained the same because I had set on boot and I was lasting without reboot, then began restarts and I put 356 all stock and I'm testing how it goes :)

I using F.K.U.
[Samsung Galaxy Nexus] Khizar:
using r356 with the default settings and it works great.. no issues whatsoever
[Samsung Galaxy Nexus] haxor:
Anyone ?
[Samsung Galaxy Nexus] Khizar:
you could try but i dont recommend it.. and wait for some time before bumping your own post ;)
[Samsung Galaxy Nexus] galakanokis:
Ok, that makes more sense. Have a read back and you will see that some have noted a slight difference in the stable voltage levels on this version compared to previous versions.

If I recall correctly it is only certain higher voltages that are having issues.

G

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

If you are not using the frequency don't worry about setting the under volt on it, your phone won't use it.

You can leave SR on. If you manually under volt be sure to set it under what SR calibrates to or else you are not really doing anything.

G
[Samsung Galaxy Nexus] haxor:
Thanks Bhai jaan but should I leave SR enable if I am manually putting UV ?
[Samsung Galaxy Nexus] Khizar:
you can leave it on
[Samsung Galaxy Nexus] allgsmnetwork:
In Italy have the gnexus sold below cost price to 269 euro and also have problems with the proximity sensor does not all have S/N C8 and C9.
[Samsung Galaxy Nexus] Khrushy:
Interesting, I'd never read about that before, but I have a safe chip apparently. I wonder if some of those suffering the slowdowns can check too.
[Samsung Galaxy Nexus] Syfer_Fever:
guys am i right this is the UV settings by sir osm0sis? http://xdaforums.com/showpost.php?p=34951507&postcount=34564
[Samsung Galaxy Nexus] allgsmnetwork:
My Gnexus 12/11 all test passed :good: