yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] abalam:
Same problem here, up to 80c
[Samsung Galaxy Nexus] SahilC:
Does this happen to anyone else? How about you, os?

---------- Post added at 03:54 PM ---------- Previous post was at 03:53 PM ----------

Hey guys, is it alright to Overclock our Gnex to 1.5 or something?
[Samsung Galaxy Nexus] The Gingerbread Man:
I think a certain degree depends on your local climate. My gnex gets warm but its getting colder in the UK now. In the summer in a car I was using my n7 and it was so hot I could hardly touch it and the display was giving major artifacts of loads of star things white dots in rows everywhere that was scary but no permanent damage. As for over clocking everyone can take at least 1.5 as this chip set native speed is that just Google down clocked it for battery life. Although if your complaining about heat issues over clock will only make it worse, unless you learns to under volt which will lower the temperature a bit
[Samsung Galaxy Nexus] SahilC:
You know what, you could be right about that. It's October here in India, retreating monsoon. So it's really hot. :P That could be the issue.

And yeah, I don't want to undervolt and stuff. :P

The thing is, I AM getting lag here and there. Especially on the notification tray (as I said before, sorry for reiterating) and on Hangouts. But that is probably an app thing, so I'm not gonna blame it on the kernel.
[Samsung Galaxy Nexus] The Gingerbread Man:
Some of the lag could be from thermal throttling as your phone is trying to save it's self from incineration so lowers clock speed. Undervolting is safe just don't set on boot till you have thoughlly tested stability. Personally I can't be ****ed and just keep to stock settings. An option for is try under clock so your device is not running at high speeds and you run in to less throttling. Go for say 1.0ghz
[Samsung Galaxy Nexus] osm0sis:
You want me to keep changing the date even though the settings are the same? Come on..

If they're there, they're current. Like I clearly state in the post.
[Samsung Galaxy Nexus] The Gingerbread Man:
Can I tempt anyone here?http://swappa.com/listing/MUL808/view (no international postage outside uk)
[Samsung Galaxy Nexus] aeroxr1:
In this kernel the battery consumption is very high . Are there the solution ?

I correctly set up the high_freq at 729000 , but the consumption still elevate . What can I do ? However the performance is amazing !
[Samsung Galaxy Nexus] thegtfusion:
Weird, check if one of your apps isnt draining the battery. Its perfect on my device. (Latest purity build)

Setup:

Deadline [MENTION=330550]512[/MENTION]k buffer

Interactive 1.2 ghz max 384 min, 729 hispeed freq.
[Samsung Galaxy Nexus] SahilC:
But that "thermal throttling" is happening because my phone is running too hot? Or is there some other reason? Does this affect you as well?
[Samsung Galaxy Nexus] osm0sis:
29.0 idle. 43.0 after gaming. ~55 at most if I'm both charging and gaming. I use 1305 MHz as my max, but I do have things undervolted, shouldn't make that drastic of a difference though.
[Samsung Galaxy Nexus] SahilC:
I'm just browsing Tapatalk and Google plus, and my CPU is at 50 degrees. :P

Is that okay? It seems high compared to yours.
[Samsung Galaxy Nexus] motorazrv3:
+1

Using fixed r392. Long time fancy user and decided to try this version because of the extra 50 MB free memory and touch control support.

Tried a few franco versions before but they didn't get me so I always went back to fancy again.

But this version is fantastic. Great smoothness and battery life. The.
[Samsung Galaxy Nexus] SahilC:
Sir, I'm a little confused. You +1'd his post saying that the battery life isn't that good, but then you say battery life is great?

Which is it? I'm curious. :P
[Samsung Galaxy Nexus] motorazrv3:
You are right. Quoted false. Wanted to quote post #43663 from thegtfusion.

Gesendet von meinem Galaxy Nexus mit Tapatalk-4
[Samsung Galaxy Nexus] osm0sis:
Yeah I'm "so important" because I expected you to read, comprehend and not act entitled.

Guess I ask too much sometimes.

Edit: Kinda out of context now that a mod deleted the abusive post.. :p
[Samsung Galaxy Nexus] namtombout:
Some people are so disrespectful. You're appreciated and important.

I know you and the gingerbread man both do stock, how do you guys get tethering to work
[Samsung Galaxy Nexus] osm0sis:
Worked fine last time I tried out at the cottage with my family, using the Nexus 7. What sort of problems are you seeing?
[Samsung Galaxy Nexus] The Gingerbread Man:
Huh I missed something here.... Anyways, osmosis has kept this kernel up to date and adding fixes for sometime now so if someone is blaspheming then they are chatting literal ****

As for tethering I also connected to my n7 through gnex via WiFi hotspot today and it worked perfect. I know it works on stock, haven't tried any other roms. If you have already connected to it already then try "forgetting" the network and reconnect again after entering the password again
[Samsung Galaxy Nexus] namtombout:
I'm on sprint

(not for much longer though). I was hoping you guys used an app. Works fine on custom stock roms so I'll be alright
[Samsung Galaxy Nexus] The Gingerbread Man:
If you could add a logcat to a post it would be helpful. That way those so inclined can read exact error messages and perhaps point to a cause. Off the top of my head first steps in trouble shooting would be

Double check your provider actually allows tethering

Get yourself to stock rom and kernel and check it

Try with your chosen rom and kernel supplies with it

Then with Franco

Identify the point it stopped working and post the logcat. If its not using this kernel post in rom thread.

Failing all that fast boot yourself to latest factory image and start clean on restoring anything you absolutely need.

(Tip back up photos using picasa uploader and store your music with Google play music or keep mp3 files on PC)
[Samsung Galaxy Nexus] namtombout:
My carrier sprint makes you pay for it. Sprint has all sorts of issues, latest factory image is 4.2.1 I thought all carriers blocked tethering on stock and an app allowed tethering to work on stock. Looks like I was wrong
[Samsung Galaxy Nexus] The Gingerbread Man:
Ah so its as a case of the carriers had their wicked way with it. I think there might be an app by Koush you might be able to use to perhaps enable it although I'm not certain. I know on orange (EE) uk it works fine. This rules out kernel issue. Get googleing as to how you can make it work, I'm sure you aren't alone with this issue on said phone and provider
[Samsung Galaxy Nexus] namtombout:
OK. Thanks gb man. Before I put up my bib and rubber tipped spoon, is this correct:hard reboot is kernel related and soft reboot is rom related
[Samsung Galaxy Nexus] aeroxr1:
What should I do for see if an app drain my battery ? :)

Inviato dal mio Galaxy Nexus con Tapatalk
[Samsung Galaxy Nexus] The Gingerbread Man:
No not really and without seeing any logs its impossible to tell. Go to proc/last kmsg it shows exactly what's happened in the code to cause the error to force a reboot. In some cases they can't be helped, something to do with some kind of watch dog which I don't think anyone really understands that I have seen and in other causes it can be pin pointed to a specific thing

---------- Post added at 01:09 AM ---------- Previous post was at 12:57 AM ----------

Install wake lock detector or batter battery stats and then Google search the service or application at the top of the list as to why they could drain it. Just about anything with a push notification will hold wake lock (keep device from deep sleep)
[Samsung Galaxy Nexus] rmcsc:
Franco: Nothing new after 393?
[Samsung Galaxy Nexus] Sik-1:
Wow you're way in the future

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

Opps wrong person that was for the guy asking for 393 and beyond, xda on my phone is showing a lil buggy atm
[Samsung Galaxy Nexus] SahilC:
Alright, my phone is literally getting too hot now. I'm gonna have to go to another kernel. I don't want to though. :(
[Samsung Galaxy Nexus] The Gingerbread Man:
Its so hot because you are over clocking. Use 1.0 / 1.2 GHz you really don't need more.
[Samsung Galaxy Nexus] SahilC:
Nope, I'm not Overclocking. 1.2 only.
[Samsung Galaxy Nexus] The Gingerbread Man:
Your screen shot shows 1.3 1.4 & 1.5 are being used. Make sure you only have one CPU management app and uninstall any others. Clear its data, reboot and set up your settings again to only use up to 1.2. Personally I'd recommend the Franco app but I understand some people can't buy apps so trickster is OK I guess
[Samsung Galaxy Nexus] SahilC:
I'm so sorry, I should have mentioned.. I went Overclock for just a few hours the day I posted about.. But later that day I quickly went back to 1.2.

That's why 1.5 and all show up.

This heat thing has been going on well before I overclocked.
[Samsung Galaxy Nexus] The Gingerbread Man:
You don't have to be so sorry lol Tbh bud if you don't want to under clock or undervolt I don't really know any other way to keep temperature down other than keep you phone turned off. Maybe a hardware component is worn and over heating, I don't know. Other than the advice I've already provided I don't think there's anything else I can suggest other than trying another kernel or ROM to see if your phone prefers those softwares and runs cooler.
[Samsung Galaxy Nexus] sd3993:
Hey bud. I think maybe it has something to do with the Indian climate. I live in Kolkata and it gets pretty hot too :/

I've undervolted my phone heavily but phone doesn't run much cooler. :(
[Samsung Galaxy Nexus] thegtfusion:
yes, that is possible. i lived in the tropics till august, and yes, the phone got hot too. now i live in europe, and the heating problems are gone. ;)
[Samsung Galaxy Nexus] ad astra:
ambient temperature is an important variable indeed. temperatures over 25°c tend to make my phone warm... beyond the 30°c its like having a portable electric frying pan! and this is for web surfing, not even gaming.
[Samsung Galaxy Nexus] rmcsc:
I am, I guess. Did he stop working with maguro after 4.3?
[Samsung Galaxy Nexus] metalspring:
392 is for 4.3... And was released not too long ago, but he did shift focus to newer devices

I am sure he will update if and when 4.4 is released for the nexus and maybe even if someone can get a Linux 3.4 kernel to boot for us
[Samsung Galaxy Nexus] ChazzMatt:
I'm also on 4.3.1 and I get deep sleep...

Slim Bean 4.3.1

Franco R392- FIXED by Osmosis

Deep sleep screenshot from Franco app.

Yeah, it's great, isn't it? :)

And it does go into deep sleep on 4.3.1.
[Samsung Galaxy Nexus] dracon6ai:
One last option could just be the kernel. Franco has always ran hot for me, never knew why but it does. Done Lean, AK, Golden, Franco, Os's Fixed Franco, and MPOKang and anything Franco just heats up quicker. Even if I set the freq's, voltages, governor, and scheduler tweaks the same between all of them. It'll make no difference, Franco just heats up quicker and higher than the rest. In the end though, all the kernels I've listed above are amazing in their own right and just play around and find one that you and your phone likes the most. Franco as of now just might not be one of them.

***Laziness is nothing more than the habit of resting before one gets tired!***
[Samsung Galaxy Nexus] gpzbc:
As discussed several pages ago, Franco stock settings has always run hot for me too. I eventually had to switch to a different kernel. All of the kernels I tried did not run hot for me, but I eventually settled on Tiny kernel.
[Samsung Galaxy Nexus] osm0sis:
I wonder if the thermal throttle is higher than stock or handles things differently...

My best guess is that Franco's GPU OC just doesn't agree with humid climates.
[Samsung Galaxy Nexus] gpzbc:
Maybe, but I live in an arid climate.
[Samsung Galaxy Nexus] osm0sis:
Okay, heat in general then. :p

UVing your GPU/CORE might be the best thing to try. Unfortunately it's also one of the more difficult ones to do since it's difficult to assess what frequency it's at and how to ramp it to try and test methodically.
[Samsung Galaxy Nexus] Edward Stanbury:
Oh yes our GPU uv testing days haha got there in the end though, but those iva voltages/frequencies still make me wonder why it sticks to the lowest ahh well performance is still amazing :D
[Samsung Galaxy Nexus] ashclepdia:
Lol, maybe I'm alone, but 58°C seems status quo for my gnex whenever I use it for more than 15mins and it is 65°F+ outside...that's one reason I like the fall/winter hahaha
[Samsung Galaxy Nexus] abalam:
You used to have pocket warmers for the winter. Now at this time is used GNEX with Franco. Well meant as a joke hey people. Kernel runs great on my stock device and so called a tuned computer is also hot. Maybe an option, water cooling haha :D:D:D
[Samsung Galaxy Nexus] skizofrenic:
Maybe i m wrong but it's 60c° for stock and 70c° for franco
[Samsung Galaxy Nexus] sd3993:
Ok i got a question.

Does undervolting the CORE too much(but keeping it stable though) cause weaker signal strength?

---------- Post added at 08:42 PM ---------- Previous post was at 08:40 PM ----------

You're correct. I've tested it out. Throttling does start at 70C.
[Samsung Galaxy Nexus] skizofrenic:
Undervolt no

BUt i found (cannot remember where)that someone noticed a frequency intrference with GSM and CPU when it run at 380mhz.

Like router frequency with some tv repeater.

Hard to test... But reason to put low freq to 190 ;)
[Samsung Galaxy Nexus] ashclepdia:
Lol I had to post this after you reminded me of it (found it in another thread not long ago) :D
[Samsung Galaxy Nexus] namtombout:
One year ago...

http://xdaforums.com/showthread.php?p=33161912

Great read for newer users. This stuff still valid?
[Samsung Galaxy Nexus] osm0sis:
Valid on stock kernel interactive governor, but not on the AOSP interactive we've been using for awhile; that's when we retooled the "magic" tunables into the "winning" tunables.

Here's all the low-down:

https://docs.google.com/spreadsheet/ccc?key=0AoUO8XSpvKCfdFVGMm5IRTgtLVptQ1FnNk5HR3djeFE#gid=2

Ignore cubic being there, we were recording Franco's default at the time. Gladly he saw the light lately and we're on westwood. :)

And a LOT more reading from some of our more feverish work:

https://groups.google.com/forum/#!forum/francosdevteam ;)
[Samsung Galaxy Nexus] The Gingerbread Man:
If I find my self a lot of free time it could be interesting to re visit that subject on my flo.

My n7 had great speeds in the benchmarks we did, I think the 32gb performed faster than 16gb if I remember. Will be interesting to see how the better hardware does in androbench
[Samsung Galaxy Nexus] hdoraemonk:
Kernel's not work (com.android.phone force close) on CM10.2 since 22/10 nightly :(
[Samsung Galaxy Nexus] AutomaticFailure27:
The issue is with CM and the Ramdisk changes.
[Samsung Galaxy Nexus] The Gingerbread Man:
EBay buyer closed case in my favour, no refund for that guy. Awaiting funds. Edited prev post
[Samsung Galaxy Nexus] mangusZen:
[MENTION=1143630]osmosis[/MENTION] hi ,Im using your last kernel and its perfectly fine for me. I only miss the tun/tap module for my vpn..any info about this? Thanks and cheers

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] MightySashiman:
****, was working on 20/10 nightly. Switched to 24/10 nightly, had the bug. Am trying to flash 23/10. Damn damn damn.

edit: bug on 23/10 confirmed too. switching back to 21/10 nightly.

edit2: strangely, even after flashing the franco kernel 292 over 21/10 CM nightly, and having cache/dalvik wiped, I still got the same bug, but only once (instead of an infinite loop), and then it just shut up and worked fine.

no comprendo...
[Samsung Galaxy Nexus] phishn:
Same issue going on with Vanir atom nightlies since 10/21.
[Samsung Galaxy Nexus] osm0sis:
Google disabled modules for security reasons in 4.3 and Francisco hasn't decided whether to turn the functionality back on for us yet. It's a config thing set pre-compile so there's nothing I can do.

CM/Vanir guys: I'll grab the latest ramdisk and see what changed. Probably have something for you this afternoon.
[Samsung Galaxy Nexus] greyhd:
I am on Vanir 1024 and no issues. Try using the stock Vanir kernel and see if you have the same issues. If you still have issues, I suggest do a clean install.
[Samsung Galaxy Nexus] The Gingerbread Man:
Can we not just say cm is not supoorted anymore? I follow Franco on gnex, n7, n7 2013, n4 and littetally all you hear about is stuff going wrong with cm or cm based roms. If these users want the refined product of Franco then they should use aosp rom or stock rom. Cm just keep going off doing things in ways that don't work in compatible ways, starting with colour control last summer I believe. Since then it has gone on to them using completely different drivers for certain Qualcomm chips and frankly if everyone moves to keep things compatible with cm then there won't be time for new development. So I propose you make your bed and lay in it if you choose cm based roms or be happy with aosp. Its splitting android into further fragmentation. Cm are now a buissness, they have gone corporate leaving bed room devs behind
[Samsung Galaxy Nexus] Fenvarien:
If someone wants or needs to leave CM/CM based ROMs but wants more features and flexibility than stock, I can recommend Purity ROM.

It's based on JWR66Y, very reliable, stable and not too overwhelmed with features.

I use it with my N4 and now with my GNex also. ;)

http://xdaforums.com/showthread.php?t=2012706
[Samsung Galaxy Nexus] The Gingerbread Man:
Or even just stock rom with xposed framework will add just about any tweak you want and you can turn it off and still enjoy ota updates etc provided no other system changes have been made (or you know how to change back)
[Samsung Galaxy Nexus] osm0sis:
Not much in the way of changes.. the only thing I can think might cause it is something they added to the BOOTCLASSPATH variable.

CM guys, give this a try and let me know if it works: http://d-h.st/9Eb

[MENTION=2501618]phentex[/MENTION] Dirty flashing the newer nightly and then older ones on top likely left something behind.

Once I get confirmation it works :fingers-crossed: then I'll email the new ramdisk to Francisco.
[Samsung Galaxy Nexus] The Gingerbread Man:
Kudos to you for doing a great job maintaining this in Franco's largely vacant position here for some time. You have just read my opinion on all this cm malarky and if i had the knowledge and know how wouldn't have bothered personally. Hopefully Franco will give my post some consideration I have spammed his threads all 4 with it lol He is on vacation with his gf atm. Does anyone else remember what happened Franco took a vacation ;)
[Samsung Galaxy Nexus] MightySashiman:
Switching back to CM 10/24, wiping and then i'll try installing your kernel.

edit : after reflash of 10/24 + wipe dalvik/cache, no more problem. Strange.

edit 2 : flashed your fixed kernel. Seems to be working atm. => thx a million :)
[Samsung Galaxy Nexus] osm0sis:
Ah good to know! That explains why he didn't answer my grouper fixes email earlier in the week. :good:

Yeah, I'm a sucker. ;) Simple change really, not a big deal, but I hear you on their dev practices being a bit self-centered.
[Samsung Galaxy Nexus] MightySashiman:
There's a missing value after "85"

(the "input_boost_freq" I think it is
[Samsung Galaxy Nexus] osm0sis:
Thanks for pointing that out! input_boost_freq is new as of r392 I think? :)

Edit: Updated. So.. does the new fixed work?
[Samsung Galaxy Nexus] MightySashiman:
Yes it seems to be working (see my edit in my previous message :) )

Actually input_boost_freq, timer_slack and boostpulse_duration are missing.

Maybe the best would be to actually write down : "setting name : setting value" instead of a list of values ? :)

Thx anyway :)

---------- Post added at 06:49 PM ---------- Previous post was at 06:44 PM ----------

Sorry to ask, but where do you find the following settings ?

Read Ahead Buffer: 512; NR Requests: 512

It's a pity there is no quick "save / restore" franco setting... :p
[Samsung Galaxy Nexus] osm0sis:
Maybe, but that'd be enormous, so it's been reasonably straight-forward to this point to just have them in the order they show in f.Ku. :good:

Those two settings in particular aren't in f.Ku, though I've requested them a number of times. You can change them in Trickster but don't worry about it, those are the defaults for f.K so they're already set. :)
[Samsung Galaxy Nexus] MightySashiman:
Thanks so much for the help. :)
[Samsung Galaxy Nexus] osm0sis:
Latest r392-fixed:

http://d-h.st/users/osm0sis/jb4_3/tuna/

Changes:

- Fix CM nightly compatibility.

- Latest busybox 1.21.1 binary.

- Other minor changes.

Note: I reverted the charger binary to that of r391 since CM's new percentage overlay for powered off charging is opposite to the minimalist design aesthetic Google was going for (and I prefer. ;))

420 downloads of the previous fixed.
[Samsung Galaxy Nexus] abalam:
osm0sis man!! Because of you we do not get to turn on the n4 or n5. Through your modifications the gnex remains a top device
[Samsung Galaxy Nexus] thegtfusion:
true dat!!

ps, haal jij ook een nexus 5? :P
[Samsung Galaxy Nexus] marpipro:
Seems work well on latest carbon nightly.

Thanks man :thumbup:
[Samsung Galaxy Nexus] MightySashiman:
Strange thing about your freq settings, the 192MHz as min and the 1305MHz as max don't seem to stay set. At reboot, the settings seem to get back to min=384MHz and max=1228MHz. (although I have "set CPU settings on boot" and "set governor control on boot" enabled)

Did I do something wrong ?

(the max screen off frequency on the other hand stays set at 537MHz OK)

edit: actually the IO scheduler got set back to default CFQ, scheduler settings, color profile too. Maybe it's xprivacy or some other xposed module interfering

edit2: it was. (bootmanager)
[Samsung Galaxy Nexus] The Gingerbread Man:
Just to confirm it will work still on stock with ram disk changes? I don't wanna soft brick with 3 hours left at work
[Samsung Galaxy Nexus] osm0sis:
Haha. Yep. Been running on both of my stock devices all afternoon (first thing I test ;)).
[Samsung Galaxy Nexus] abalam:
Just wait until FKU get root permission. Here he just switched to 1305 to
[Samsung Galaxy Nexus] phishn:
Works with vanir atom nightlies now. Thanks!
[Samsung Galaxy Nexus] MightySashiman:
I seem to encounter one hell of a strange problem. Combining CM nightly 10/24 and kernel r392 fixed, it seems the messaging app (for sms) and phone call feature stop working. I can no longer send out messages (they stay at "sending..." stage, and a couple of people tried to call me and went straight to answer phone. Didn't get any ring at all. I can't make calls my self. When calling, it just makes no waiting tone, plain silent).

Is there a way to diagnose where this could come from ?

edit : tried put on then off aeroplane mode. The aeroplane mode never goes on fully, must stall a some point in the process (in the extended powermenu "aeroplane mode on" stays grayed out, and the airplane icon never shows up near the clock in the top bar...
[Samsung Galaxy Nexus] osm0sis:
Anybody else seeing that on CM or Vanir? I definitely have no problems with stock.
[Samsung Galaxy Nexus] mangusZen:
Thanks for the answer. I probably missed some talks about this in the past, but how much overhead should bring the tun/tap support if compiled in the kernel and not as module? It's a very (common) used feature....

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] MightySashiman:
you're a poweruser. How come you use stock rom rather than a custom rom ? :) Do you enhance the stuff with xposed ?
[Samsung Galaxy Nexus] pkgnex:
Probably because stock ROM meets his needs without adding a bunch of "features" that always seem to either drag down performance or are otherwise in a state of disrepair.
[Samsung Galaxy Nexus] The Gingerbread Man:
Pkgnex got it in one. Stock rom us fine for my needs, no buzz words no BS, less messing around to get latest ota. I use xposed framework with gravity box module, that with this kernel meets all my needs and expectations from a 2 year old phone