yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] shreddintyres:
if youve been issueless for so long i highly doubt its the kernel, id suggest doing a clean flash, cuz its probably somethign rom related or one of your apps misbehaving and consuming too much cpu runtime. otherwise sorry, i really dont know

- Cheers
[Samsung Galaxy Nexus] smileyanz:
I would say there are more still holding out on 4.1.2 then actually moving permanently on to 4.2.1. And also there is a more polite way of putting over a genuine concern over to another fellow on our forum concerning to many questions been put forward, wouldn't you agree!!!!,,it will only put people off coming to this forum who are not so clued up!!
[Samsung Galaxy Nexus] yellowdie:
Sorry you feel mistreated. r300 is near perfect--there is nothing Franco can do to improve it. So there's really no reason at all to push new builds. With the Nexus 4, the GNex took a back burner, so Boss Man couldn't do releases for 4.2 AND 4.1 so he focuses just on the new stuff (that still needed improving). So yeah, r300 will be 4.1.2's final build. Which is nice because r200 was 4.0.4's final build. lol. Just a random coincidence.

:):D:laugh::good:
[Samsung Galaxy Nexus] calinoii:
I think that my problem is related to the Beats+Xlouder patch...since I flashed that my device is so sluggishbthat I can't recognize it anymore,I also tried other kernels like faux's ,leanKernel,trinity and ak's and got the same problem...the only reason I can find is the Xlouder patch...did someone else had this issue?
[Samsung Galaxy Nexus] osm0sis:
r200 was unstable though, so r196 was really the last stable ICS build. ;)
[Samsung Galaxy Nexus] eng.stk:
Not a coincidence, bossman does everything for a reason :laugh:
[Samsung Galaxy Nexus] osm0sis:
No I leave SR on just for the cosmetic of having Device Monitor show the corresponding voltage rather than 0mV like it does when SR is off. All of my voltages are below the SR calibrated voltages for my device anyway, so they aren't in SR's control anymore.

CyanogenMod have their default settings technically overdriven at 400 400 400 so they're some kind of hypocrites I guess? :p "Waste" isn't the right word though; the concern people have, at least in theory, is that anything over 200 can cause burn-in of that color. In practice, however, you're going to probably replace your phone before you'd ever see the effects of it. Much like BLX set to 96. It only makes sense if you plan on owning your phone for 5 years or more. That's why BLX is 100 by default on f.K.

Only thing I've ever gotten minor burn-in from was ClockworkMod Recovery when I forgot and left it over night when I was backing up my sdcard through adb pull. The blue bar being at the top that whole time left a mark. That's completely outside of my color settings though, since it's in the recovery, so I can safely say my colors haven't caused me any burn-in.

That is one hideous poodle. :p
[Samsung Galaxy Nexus] shivasrage:
delete
[Samsung Galaxy Nexus] jorge89:
I have 4.2.1 JOP40D stock but rooted and just flashed kernel #344, I'm not sure where to get the apps to oc and uv. Where they supposed to be installed when I flashed the kernel?
[Samsung Galaxy Nexus] shivasrage:
There is nothing installed with the kernel..for setting values...

You can use Trickster Mod from playstore or

better purchase Franco Kernel updater app.

S.R.
[Samsung Galaxy Nexus] lippol94:
Just 5 pages back.. -_-

Laziness ain't a virtue :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
That's why xda has a search bar at the top of every thread...
[Samsung Galaxy Nexus] natezire71:
That's CNA. It's really laggy and stuff on 3.8. I suggest switching to another ROM.
[Samsung Galaxy Nexus] calinoii:
It worked like a dream for like 5 hours...then I installed Facebook and the inferno began
[Samsung Galaxy Nexus] galakanokis:
I used CNA 3.8 and Franco's r300 for a long time with absolutely zero issues. In my mind r300 was/is the best kernel out there for speed, responsiveness and battery and 3.8 is a rock steady ROM. Your issue is probably a mod or add on you have added and nothing to do with Franco and or CNA. Did you re-flash without adding the louder mod? Facebook is a crappy app but it does not kill phones, I used it with no issues.
[Samsung Galaxy Nexus] calinoii:
I did,but no luck for me:(
[Samsung Galaxy Nexus] Khrushy:
I also rolled back to 342 again. No issues on 344 other than the high idle drain.

It wasn't as outrageous for me as a few people seem to be claiming, but still, 12% over a 7 hour sleep is too high and I need my phone to survive the day.
[Samsung Galaxy Nexus] RayGarden:
+1

Rolled back to Stock Kernel
[Samsung Galaxy Nexus] dyndragon:
I too am noticing slightly higher idle battery drain with r344. Back to r342 for me. Both equally smooth in terms of end user experience though.
[Samsung Galaxy Nexus] galakanokis:
Have you re-flashed just the ROM and kernel with a full wipe and not adding any apps/data back? Or go back to stock and start over. Find it very hard to believe this could be ROM or kernel related.

As far as 344 goes I don't think the battery drain is too bad. Easily 13-14 hours with 3 hours screen time the past two days. I charge over night so don't notice the idle drain too much. But if Franco can improve all the more power to him.
[Samsung Galaxy Nexus] bradm23:
I just wanted to report that i also reverted to 342 and along with idle drain being better i also noticed my phone running cooler and smoother scrolling.

Can't wait for next nightly with cfq....:)
[Samsung Galaxy Nexus] cchhat01:
I would like to report that I was on r328 and it worked fine.

I tried to do a fresh install on AOKP Unofficial Dec 6 JB4.2.1 using r342 and r344 and both ended up giving me problems.

Problems usually manifested when as part of my install process, I would wipe data/cache/dalvik and format system, then install ROM+GAPPS and then franco kernel.

After bootup, i would sync with my gmail installs.

As soon as play store started syncing my apps, i would get a random soft reboot (i start seeing the AOKP bootanimation all of a sudden and my phone tries to give me an impression that it just booted up, even though it didn't)... this would happen right in the middle of installation of play store apps.

I should also note that there were no kernel customizations done. I just synced my gmail acct and let is install my apps and then BAM... bootanimation all of a sudden.

This does not happen in r328. Smooth sailing on r328 (knock on wood).

c
[Samsung Galaxy Nexus] Khrushy:
I've been using Fitsnugly's AOKP nightlies for a while now without issue. I would suggest NOT installing the kernel at the same time as ROM install. Install ROM + GApps, boot up, update everything, then reboot to recovery and install Kernel.

Although, maybe it's something to do with the Google restore - I restore my apps with Titanium, not through Google, so maybe that's triggering it.

Edit: I'm about to update to the newest nightly actually, so I'll install it your way and see if I can replicate the problem ^^

Edit 2:

Updated using the same methodology as you, flashing the 342 kernel. No problems so far. Not sure what the issue you're having is.

Which flavour of AOKP nightly are you using?
[Samsung Galaxy Nexus] osm0sis:
Just tested to see how big the difference is... I get 0.4%/hr on r342, and 1.8%/hr with r344. So 4.5x the drain. ;)

Guess I'll roll back too though I usually don't.
[Samsung Galaxy Nexus] thegtfusion:
Same here :eek:. R342 is a masterpiece!!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] KGrinols:
I had 15% (93-78) of drain last night on just under 10 hours of sleep with r344.

Reverted back to r342 today, since I was already clean installing Xylon v12 anyways.
[Samsung Galaxy Nexus] AutomaticFailure27:
It's an issue with CNA. 3.8 is not the most stable build out, even though it is the newest. I have similar issues with as well.

If I were you, do one of two things. Switch over to another rom or do a full wipe and reinstall.

And for further information, do this:

1) Try and figure it out yourself. Do as much as you can. Wipe / Restore / Install / Etc

2) If that doesn't solve it, figure when did this happen? What did I change recently?

3) Post into a relative forum with more than "OH NOEZ I'Z PROBLEMZ! FEEEEX IT"

4) PATIENCE.

5) ???

6) Profit
[Samsung Galaxy Nexus] skinnypupp:
If it helps, I can confirm that 344's idle battery isn't good, I had 20% battery drain over night just sitting there doing nothing (airplane mode on). Usually the battery doesn't drop more than 5% if that.

I checked and deep sleep is working

If I can help fix this let me know!
[Samsung Galaxy Nexus] bush2088:
No probs here

Running hoang81's akop with this excellent kernel and all is good in the neighborhood!! deep sleeping well, and battery is good to go.
[Samsung Galaxy Nexus] SpecRek9:
Peruvian
[Samsung Galaxy Nexus] Khizar:
ok i can say something is wrong.. i am guessing its a rouge app , idle drain was bad for me but it was never more than 7-9%
[Samsung Galaxy Nexus] allgsmnetwork:
light sensor is not working?

like never happens to me that the light sensor is not working? was due to a bug in v4.2 / 4.2.1? I think it does not work even with the stock with the screen automatically ... in fact both at home and in the light outdoors I have to adjust the screen :confused:
[Samsung Galaxy Nexus] n-0-s:
Battery Drain

Yeah last night when i was in bed i updated from r342 to r344.

I put my phone on charge via usb on my laptop and woke up with only 88% battery then went to work and watched my data network drop out constantly and the battery drain was horrible.. barely use my phone today and driving home it was on 18% instead of the usual 75% after a proper 100% charge...resorted back to r342 where its beautifully stable.
[Samsung Galaxy Nexus] afraaa:
Re: [KERNEL][GPL] franco.Kernel-r344 -> 4.2 | r300 -> 4.1

I guess ppl should test kernel on

Lot of various situations for instance When wanna put phone to sleep can underclock it to 1 ghz or 760 . if idle status suffer over-draining that mine is normal even with wi fi on and no airplan-mode . me myself flashed lot of 4.2 then i could solve my taking-long time to charg battery and finnaly with modaco problem solved .

And we should remember that gpu in overclock drains alot of battery /edited / in gaming case ofcource .

Try refresh your ROm and then kernel

Flash various roms and test it . thats what i am doing . and then we can confirm something in my book
[Samsung Galaxy Nexus] >stylz:
Just a question:

Is there any possibility for app profiles like:

- playing shadowgun -increase gpu and mpu

- playing music -lower GPU and mpu

- low battery plug in to USB -autoswitch USB fast charge on

- etc etc

-...

If you give me the permission and the source of the kernel updater I will try my best to implement those things... I will try at least because it is a neat idea in my opinion : )

Gesendet von meinem Galaxy Nexus
[Samsung Galaxy Nexus] gikoche:
as GPU can lower from 512 Mhz to 384 Mhz in kernel 344. Or there will be a kernel version with GPU of 384 Mhz?
[Samsung Galaxy Nexus] allgsmnetwork:
return r342

I also went back to 342 to see 3 minutes of you tube on wifi the battery has fallen by almost 10% :confused: 344 is downgrade...
[Samsung Galaxy Nexus] aR_ChRiS:
Installing a 384/512Mhz kernel does not mean that the GPU is always clocked at those frequencies, it just means that the GPU is allowed to take those frequencies...

So if we flash 512 versions of the kernel it means that the GPU is able to run at stock/384/512 MHz, depending on load.
[Samsung Galaxy Nexus] gikoche:
and how it is possible to limit then the maximum limit in 384 Mhz, instead of in 512 Mhz?
[Samsung Galaxy Nexus] skinnypupp:
What's the point of being defensive?

If there is a problem, it needs to be resolved, not blindly defended.

Otherwise the kernel will never improve.
[Samsung Galaxy Nexus] DriftGT:
I have Stock 4.2.1 + franco kernel 342

But I have a lot of fps drop with GTA VC, what is the GPU speed in this kernel? 384 or 512? How can I overclock it to test? I want a better performance. I cant play right this, to slow.

Help please

Thanks :good:
[Samsung Galaxy Nexus] calinoii:
I tried the kernel on AOKP and it does the same thing...it has lag spikes and short freezes all the time...I also tried LeanKernel and it does the same,but when i flashed Faux's kernel,everything was ok:-/ what's the problem? What is causing me all these problems? I mention that i did clean wipes when changing the roms,I want franco's kernel so baad!
[Samsung Galaxy Nexus] joaquinf:
it's 512 already. It's not recommendable to go any further. Try to decrease the images quality within game options if possible
[Samsung Galaxy Nexus] ChazzMatt:
Not to pick on this guy, but why all the sudden silly questions about the GPU?

People BEGGED for upgrade to 512MHz and for awhile Franco did two versions -- 384MHz and 512MHz. Some people's phones couldn't handle 512MHz and they had to go with 384MHz.

But Franco found a way to stabilize it and EVERYONE can have 512MHz. Also, since he now has a Nexus 4, he's made the decision to do only 512MHz -capable versions for Galaxy Nexus to simplify his life. If we beg for complications, Franco will just drop development of the Galaxy Nexus entirely.

Everyone should just say THANK YOU instead of wanting to go backwards.

THANK YOU for bringing some sanity to the discussion.
[Samsung Galaxy Nexus] Fenvarien:
+1

I'm really thankful because Franco's stabilization measures made 512 MHz GPU for my phone finally possible. :)
[Samsung Galaxy Nexus] DriftGT:
I have 342 version. Did you recommend to upgrade to 344?
[Samsung Galaxy Nexus] alfiemenace:
Not to be harsh or anything, but I recommend reading. ;)

Stock ROM, custom user.
[Samsung Galaxy Nexus] Khizar:
that isnt harsh that is a very good answer... wish more ppl answered question like that, rather than spoon-feeding lazy ppl answers :good:
[Samsung Galaxy Nexus] whitedragonz83:
No
[Samsung Galaxy Nexus] timbck2:
I agree, it's for peoples' own good to read for themselves rather than be spoon-fed.
[Samsung Galaxy Nexus] Infernus-cz:
Hi folks,

I installed franco kernel updater (free) from Google Play Store.

The app says last nightly kernel version is r196. Where is the problem? How can i get the correct nightly version and install it?

I am using Samsung Galaxy Nexus with AOKP 4.2.1 ROM

Thank you very much for help
[Samsung Galaxy Nexus] whitedragonz83:
His free app is outdated. Links in the first post lead to the nightlies for 4.2+. You can obtain image files for use with fastboot pushing, or zip files for use with CWM/TWRP.
[Samsung Galaxy Nexus] smileyanz:
Yeah but what one recommends the other disagrees. People have dif views and some of us have issues and sometimes the answer needs putting on a plate for them and being polite instead of making them feel like as if they have done wrong. It doesn't cost nothing to be polite to anyone who's not on the ball!!! Me old man always said to me down at his gym if ya got something to say in a manner of rudeness at least face it off with the guy!!!
[Samsung Galaxy Nexus] cchhat01:
I there... I used the one created by Roman... from goo.im: http://goo.im/devs/roman/aokp_maguro/aokp_maguro_unofficial_Dec-06-12.zip

I prefer the builds come directly from the devs... It shouldn't matter what flavor of AOKP I used, because it is constant between all the the kernels I tried. The problems only happen with r342 and r344, and not with r328.

A new AOKP has been built as of Dec 12, so I will give that a shot with r342 and see if it works for me.

Thanks for your input.

Zoiby
[Samsung Galaxy Nexus] rye&ginger:
For me r342 has been stable and performance is good as well on AOKP fitsnugly nightlies.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] sk8oldschool74:
What is dead line for???
[Samsung Galaxy Nexus] KaiZ51:
Hey there, I'm currently on stock kernel, but I'm thinking of flashing this kernel if it has a fix for this problem.

Does anyone know if the kernel includes a fix?
[Samsung Galaxy Nexus] Controvrsy046:
Getting stock launcher redraws on r344 and random slowdowns. Have the min free settings been increased to kill off more apps for more ram?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] farazjk:
Reverted back to version 342 from 344. After upgrading to 344 started getting data/WiFi drops and failed to reconnect to WiFi networks. Also battery was not that good and some UI lag. Back on 342 and all is good!
[Samsung Galaxy Nexus] skinnypupp:
I lost 17% battery overnight, in airplane mode. I took some screenshots using BBS, maybe someone can point to what is causing the problem:

http://imgur.com/a/iLjRr#0

(the MediaServer and Mortplayer apk was from 30 minutes of listening to a podcast before falling asleep)

Using stock 4.2 with r344.
[Samsung Galaxy Nexus] osm0sis:
The problem is franco said there was a problem in r344 that causes excessive battery loss. ;)

Most of us have rolled back to r342 while we wait for a fix. :)
[Samsung Galaxy Nexus] KGrinols:
I have a dumb question, that searching only slightly answered.

After battery issues I went back to r342 yesterday. I did a full cycle to check battery life, and measure how much I lost to 'idle' while I slept, to measure the difference between the two kernels. I went to sleep with 6% Battery Life(Airplane Mode, Wifi/GPS/All Apps OFF/Closed) and when I woke up, my battery had gone UP to 10%. I used it for a solid amount of time, and the battery rate went down to 1% at a normal rate, that indicated it wasn't a false reading of 10%. Based on what I found searching XDA and google, this is rather implausible, and most likely an inaccuracy within the battery reading. What I'm wondering is if A: Anyone else has had this occur and B: Does this issue lie within the Kernel, Rom, or potentially other component. C: What's an average or expected level of variance?
[Samsung Galaxy Nexus] skinnypupp:
I don't know why information like this doesn't get posted on the first page...
[Samsung Galaxy Nexus] alfiemenace:
Franco is not a robot you know. He maintains several devices + personal life and I think he deserves a break every once in a while. Instead of whining, accept what he can offer us at the moment or if you want compile your own kernel. Jeez

Stock ROM, custom user.
[Samsung Galaxy Nexus] shreddintyres:
because most of this information can be gleaned from a simple search
[Samsung Galaxy Nexus] Wynnded:
If you wish to use this kernel, then it's really up to you to keep up to date. Franco has done his part, do yours.:p
[Samsung Galaxy Nexus] timbck2:
Or even just read back a couple of posts, no need to even search!
[Samsung Galaxy Nexus] nikosrs4:
How many do you have problem with idle drain when on WiFi only? It drains a lot :( I tried stock 4.2 and it's definitely better.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] smileyanz:
If someone has had this auto updated then its suppose to be stable and it then deserves an explanation! , normally people who PAY for this don't know much about images and rely on auto updates.

.Its like being rude to someone shouting from a ten story building with security doors fitted. .Franco has a mouth and is busy like the rest of us and will voice his opinion if he feels he needs to.
[Samsung Galaxy Nexus] shreddintyres:
Only the app auto updates, if you are auto flashing every kernel update with out doing your research then that's your own fault. Also the nightlies are considered to be experimental and unstable, if you want something that is SUPPOSED to be stable wait for a milestone, otherwise kindly quit whining Franco owes you no explanation as he is offering his time and efforts free of charge. If you think you are owed something because you purchased the updater app then you are sorely mistaken. the number of hours and work that Franco puts into this kernel while maintaining several devices must be immense. Show some respect to the dev and do the research yourself.

i personally havent experienced much idle drain when on wifi only, but i did notice a fair number of data drops while on 344, tho im not 100% sure it wasnt my own fault, so i rolled back to 342 seems much better, but for most 328 seems to be the sweet spot for battery life.

- Cheers
[Samsung Galaxy Nexus] F_T_B:
This is a slow smartphone which needs a the help it can get. I'm down with speed.
[Samsung Galaxy Nexus] The Gingerbread Man:
I'm still rocking 344 :thumbup:

Because no f****r would read it even then :p

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] malaroth:
We hope so too... both 342 and 344 have been amazing especially in the short time you've had with the new job and n4 and holidays. There's a reason you're top of the top 100 paid apps. Thanks Franco

JBSourcery 4.0 + Franco 344 FTW. Keep the Magic alive!
[Samsung Galaxy Nexus] gaich:
Franco, finally I managed to get some time to make the correct Russian translation for FKU. Being a profesional interpreter in the past, I tried to do my best releasing it from fact, syntax, orthographic, linguistic and other errors present in current application.:D Please use it in your next FKU version. Thanks.

View attachment 1566678
[Samsung Galaxy Nexus] KaiZ51:
Anyone know?
[Samsung Galaxy Nexus] Angelakaro:
r344,just confirming huge idle battery drain and good performance/smoothness
[Samsung Galaxy Nexus] yellowdie:
Thanks, Gaich. I just emailed this to Franco because I didn't want it to get missed in craziness of the thread. He'll get it put in when he can and let you know. Thanks for the work! :):D:laugh::good:
[Samsung Galaxy Nexus] nikosrs4:
performance is top notch, battery too in 99% of the kernel releases but now drains a lot..the weird thing is when I'm on data it doesn't spend so much battery..I can't explain..I thought if it's an application but I haven't changed anything, all the apps I'm using, I'm using them for a long time.
[Samsung Galaxy Nexus] shreddintyres:
revert to 342 , Franco has previously acknowledged that 344 has some weird battery drain issues. i reverted back to 342 and my idle drain is back to something between 0.8 and 1.1% depending on how the phone feels like acting.
[Samsung Galaxy Nexus] carberoz:
hello..

is minooch sites down?

i want to download the kernel but the site is dead...
[Samsung Galaxy Nexus] yellowdie:
Nope, works perfectly fine for me: http://minooch.com/franciscofranco/Galaxy%20Nexus/JB/JB-4.2
[Samsung Galaxy Nexus] peteus:
#342 & #344 RAM management and Thermal Throttling problems

I am back on #335 because of two things. First, there is something wrong with RAM management in #342 and #344 where I am not able any more to run two big apps interchangeably. For example I can switch between Google navigation and Ingress with #335 but if I try to do this with last two kernel version, whichever app is in background (mostly ingress) will always close and needs to load again. This is not happening with previous kernel versions. Second issue in last two versions is in custom Settings - Turn Thermal Throttle off. I turn it off, run e.g. titanium back up and while looking at Franco's in app Device Monitor, temperature will not go over 75c (and will step down to lower frequencies for a second or two) while in #335 it will hit 90c and keep OC frequency stable. Can anyone confirm this? I am on latest Paranoid Android nightly ROM.
[Samsung Galaxy Nexus] carberoz:
oh yes.. a couple minutes ago i cant open it..

thank you very much sir
[Samsung Galaxy Nexus] haxor:
@Franco can you do something with this http://www.xda-developers.com/android/linux-kernel-3-7-stable-released-with-arm-support I don't know is this useful or not but I saw this and I thought that you can do something with this.
[Samsung Galaxy Nexus] sk8oldschool74:
If I backup a kernel on your app will trickster changes be included??? So I don't have to keep setting them on boot???
[Samsung Galaxy Nexus] 5pace:
@osm0sis: Holy sh** your colors look fantastic on my device! I think we both have almost the same production batch device. As I can run same settings (undervolt and overclock) as yours and the color saturation using your script is awesome. Making color script as init.d gives out an notable difference, maybe this was the problem that I didn't feel much difference when I tried using your color values in the app itself before. :p