yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] martin0285:
Kernel Panic's for Days!!

I've been having serious "reboot" issues with my gnex lately... It seemed to have started on nightly 194... Now it is happening even on M4... I have tried to poke around in IRC's and can't seem to come up with a solution...

KMSG during the SOD/Reboot/Shut-down--- http://pastebin.com/ZxSFQRVa

LogCat during the SOD/Reboot/Shut-down-- http://pastebin.com/CT31aG4t

Last_kmsg after reboot from SOD/Reboot/Shut-down-- http://pastebin.com/7LE0wBHE

I am just concerned it maybe a HW related issue and not kernel/software... Can someone look at these logs and give me some pointers?? I plan to re-lock/flash-stock right now, and go from there...

Thanks in advance!
[Samsung Galaxy Nexus] TEK112:
I wouldn't flash to stock. I would wipe data/factory reset and reload the ROM and kernel.
[Samsung Galaxy Nexus] martin0285:
I've done that... I was on 1.4 Liquid when it started... Then wiped/flashed AOKP build 40... Tried liquid 1.5... Everything and it keeps happening...

Anyway, it's to late as I just finished... Going to relock and try stock for a couple of days to rule out HW....

Did you happen to notice anything in the logs as to why you suggested just a wipe/flash?? I'm not an android "noob" but I'm not very smart either :) I can pull logs, but I can't read em!! HAHA

EDIT: Seem this "(PRM_RSTST=0x8)" with "=0x2" and "=0x4" and "=0x6" have been giving a bunch of people issues... Evidence by a quick google search... Anyone have any idea what any of them mean?
[Samsung Galaxy Nexus] mike216:
I've got this weird bug. When I turn my data on my CPU maxes out until I turn the screen off then back on then it immediately throttles down. Weird, don't know of this could be the cause of your heat. Just letting you know.

You can see this with an app called (system panel)

Take care
[Samsung Galaxy Nexus] sway40:
still getting incredible battery life and no bugs...

On 180.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] I Am Marino:
Is 180 a bug free nightly? I'm new here, excuse the potentially dumb question.
[Samsung Galaxy Nexus] Grandroidster:
No problems here. .just excellent battery life and amazing performance ..

Only got one gripe. .my multitasking app takes a while to register after I touch it. .I don't know if this is because the rom,my Max cpu our whatever it is I didn't do that before ..

refuseSent from my Galaxy Nexus using xda premium
[Samsung Galaxy Nexus] Grandroidster:
My bad I forgot to say I am running the latest nightly add well :)-
[Samsung Galaxy Nexus] kimboinatl:
196 is working well for me so far. I flashed it yesterday, and I haven't had any problems. 729/1651 and using Wheatley.
[Samsung Galaxy Nexus] gaming09:
franco i <3 u please dont yell, I read that your latest nightly has linaro based changes i was trying to see the validity of this comment? and if so what changes were made. If this comment is false and the latest nightly does not contain these changes are there plans to adopt them?
[Samsung Galaxy Nexus] EDNYLaw:
Franco has said a bunch of times he has not and will not incorporate linero toolchain. Rogersnm on the GSM thread has compiled franco.kernel with linero but since Franco didn't make it, if there are bugs your in your own

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Samsung Galaxy Nexus] kimboinatl:
I do seem to notice a few hiccups today - like sometimes I'll click or swipe and it'll take a fraction of a second for it to register. Not sure if this is the governor (Wheatley) or the build.
[Samsung Galaxy Nexus] infazzdar:
What rom are you using? On AOKO B40 my battery life is sub-par.
[Samsung Galaxy Nexus] TEK112:
It is the governor. Try interactive.

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

I think it is too soon for you to tell. ROM/kernel break-in is about three days and possibly longer depending on usage. Possibly longer if you did a full wipe. If you flashed dirty that very well could be your problem.
[Samsung Galaxy Nexus] sway40:
I agree too many people judge battery too soon, you have to give a few days for processes to stop that you don't use and other stuff.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] kimboinatl:
Does anyone do any sort of battery calibration after flashing a new ROM + kernel?
[Samsung Galaxy Nexus] Gahh Its Lee:
Yea I charge my phone then I use it :P.

But really any battery calibration I've ever heard of is actually just killing the battery quicker.
[Samsung Galaxy Nexus] TEK112:
This^
[Samsung Galaxy Nexus] fclifton:
Running nightly 196. The governor setting and the Colors Multipliers are not sticking through a reboot. I have Set CPU settings on boot checked. Governor always goes to wheatley. Colors Multipliers always go to 200. Sorry if I have missed something about getting them to stick. ROM is IMM76K.
[Samsung Galaxy Nexus] anton2009:
Is franco.kernel-r200-384GPU.zip functional with the CDMA version of the GNex?
[Samsung Galaxy Nexus] theboo7:
Yes Sir. Well if youre running JB
[Samsung Galaxy Nexus] anton2009:
Ah great. Good to know. Thanks. Flashing now.
[Samsung Galaxy Nexus] m0b1l3:
Ahhh the app. It force closes. It's worse now that I flashed a new rom and kernel because now the colors are all off. Please fix the app.
[Samsung Galaxy Nexus] foueddyf:
Yeah the app doesn't seem to be JB ready yet.
[Samsung Galaxy Nexus] sytech55:
Has anyone tried this kernel (Milestone version) on ICSourcery's ROM?
[Samsung Galaxy Nexus] kennyp987:
The r200 kernel on jdkorelclipses jb build is amazing
[Samsung Galaxy Nexus] Thadrow:
Theres a r201 build too. Safe for cdma too?
[Samsung Galaxy Nexus] scott62185:
Where you find the r201? thanks...
[Samsung Galaxy Nexus] Gahh Its Lee:
Should be safe.

http://xdaforums.com/showthread.php?t=1367341
[Samsung Galaxy Nexus] BFirebird101:
What exactly does the boot image help out with and is there any way to just flash it on the phone
[Samsung Galaxy Nexus] larkhillv:
I haven't tried the milestone version, but I have done several of the nightlies. I started experiencing pretty bad battery life with any of the nightlies past 186 from my recollection (I also tried Popcorn Kernel with similar results). I am back on Franco r180 using wheatley governor. Yesterday I went from 100%-0% battery with about 3 hours of screen time, varying wi-fi/data connections, and I think around 11-11.5 hours since unplugged.

Right now, I have 57% battery left with 1 hour 55 mins of screen time. Five and a half hours since unplugged, using the same kernel and settings (ICSourcery 3.4.2) So unless you're getting better stats than that, I would recommend playing around with Franco r180-186 nightlies and different governors. I hope this helped.
[Samsung Galaxy Nexus] ZeppelinJ0:
I tried it out and it stuck me in a bootloop and I had to reinstall JB. Not suggested for CDMA based on my trials.
[Samsung Galaxy Nexus] spectrumfox:
Is the default governor for this kernel On Demand or Interactive?
[Samsung Galaxy Nexus] Thadrow:
I flashed jb then 201. Running great for me.
[Samsung Galaxy Nexus] Moonkae:
Franco, just want to say thanks for your JellyBean kernel packed into Team Vicious 4.1! I was happy to see that disclaimer.
[Samsung Galaxy Nexus] 2010gt:
After flashing v2 of the ROM and rebooting, it hung at the Google screen for quite some time before finally booting into Android.

I installed the latest Franco Kernel for JB (now looks to be #207) and set the governer to ondemand and it appears to run much smoother and no longer hangs on the Google screen at start up.

Thank you to all the devs that have made this possible!!!!!!!!! :good:
[Samsung Galaxy Nexus] revolt1:
where would I find 207jb
[Samsung Galaxy Nexus] Gahh Its Lee:
The GSM thread for this kernel. Look there since the kernels work for both phones.
[Samsung Galaxy Nexus] avlfive:
http://minooch.com/franciscofranco/Galaxy Nexus/JB_test/Jelly Bean/
[Samsung Galaxy Nexus] revolt1:
which is better 200 or 207 for sleep and battery if 200 any link for that
[Samsung Galaxy Nexus] TEK112:
There is no way to know yet. JB is only a day old and Franco's kernel is even younger. You need about 3 days to fully test any ROM/kernel combo.
[Samsung Galaxy Nexus] Dakota0206:
You got to just see what works for you. Every phone is slightly different and by the time someone was to test everything for you a new build would be out.

Build R210 is available

http://minooch.com/franciscofranco/Galaxy Nexus/JB_test/Jelly Bean/
[Samsung Galaxy Nexus] nvrMind:
I've tried 200, 207, and 210. I can't seem to get force fast charge to work. It may be my app, though. I've tried incredicontrol and galaxy nexus fast charge apps. Any ideas?

I'm cdma, as well. Everything else appears to be working well.

Swyped from my BAMF'd Nexus on the Franco kernel...
[Samsung Galaxy Nexus] notoriousB:
I'm running M4 on ICSorcery 3.4.2 and it's working beautifully!
[Samsung Galaxy Nexus] EDNYLaw:
Franco pulled fastcharge to try something else that, I'm assuming, has not been merged yet. Give him time, he'll get it working and no doubt amaze us in the process. By the way, check the GSM thread, they are way more active over there and this was covered :D

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Samsung Galaxy Nexus] raphenucleus:
For anyone on ICS r196 or r200 that doesn't like the new morfics contrast interface or just wants to set a different value than -24 on boot, I made a simple init.d script to do that. It should work on Jelly Bean as well, but I think franco changed the default value to 0 in those releases, so the script wouldn't be necessary unless you want to change the value and he hasn't made it stick on boot yet. I'm sure he'll add this functionality to his app in the near future, but in the meantime this will have to do.

Download the attached file. Remove the ".txt" extension in the file name. Use root explorer or adb to place it in /system/etc/init.d. Change the permissions to rwxr-xr-x (Owner: Read, Write, Execute; Group: Read, Execute; Others: Read, Execute). Reboot and your screen will return to the way it looked before the contast interface was implemented. If you want to change the value of the contrast, simply edit the "0" in the script to whatever value you want (-24 is the kernel default).
[Samsung Galaxy Nexus] cj1896:
So I saw the change log on the app update and thought I would report that none of my settings are holding through reboots still. Cpu goes back to default settings and color settings aren't applied. Running milestone 4 and cm9 nightlies.
[Samsung Galaxy Nexus] TEK112:
Just to confirm, CPU frequency and governor not sticking with AXI0M JB and 210 with the latest app update.
[Samsung Galaxy Nexus] stick1300:
So, which of the latest batch of kernels would be considered the bee's knees? I'm still on 180 and, while it's GREAT, I wouldn't mind getting a little more with the times. I'm guessing 196 would be the "safe" bet, since it's still completely ICS based. My big hangup is I'm seeing a lot of people having issues with settings not sticking on reboot, which I'm not having at all (thankfully).
[Samsung Galaxy Nexus] EDNYLaw:
I believe, though feel free to correct me if I'm wrong, the settings not sticking was a problem with Franco's updater app and not the kernel as I've been using r196 since it came out and the settings not sticking happened when the app was updated from 5.5 to 5.6. R196 is great though, no issues, I'm running 192-15xx and with the 1.5 slot undervolted to 1300mv with no problem. Currently testing governors to determine battery life. While ondemand is snappy as hell, i think it hits my battery kind of hard. Interactive sucks for me, too laggy, wheatley is very fast and pretty decent in battery life and I'm trying conservative right now and i get zero lag so far. Hope that helps

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Samsung Galaxy Nexus] stick1300:
Ok, I guess I'll give 196 a shot then! Thanks!
[Samsung Galaxy Nexus] I Am Marino:
Trying 180 as everyone kept saying it's great on battery, is there another nightly I should try for good screen on times, only using 3G, no games.

What governor as well?
[Samsung Galaxy Nexus] sway40:
I miss 180, since im on jb. Use wheatley as your governor. was getting over a day and 3hrs screen on time with that nightly...not anymore. I get horrible battery now but jb is worth it imo.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] I Am Marino:
Using Liquid and 180, unless something seems horrible, I'll give it two days to see what my battery is like.
[Samsung Galaxy Nexus] BlakeDC:
Pardon my ignorance but where is 180? On his index the oldest I saw was 185 :-(
[Samsung Galaxy Nexus] raphenucleus:
The link is in the OP under Downloads/Nightlies, but here you go for simplicity: http://minooch.com/franciscofranco/Galaxy Nexus/nightlies/

The links that show up first are for the 512 MHz GPU versions. For the links to the 384 MHz GPU versions, click on the link at the bottom of the list.
[Samsung Galaxy Nexus] TheDoctor1177:
Have people been running 210 with any JellyBean ROMs? Just wanted to hear a few opinions on the kernel, like does it help battery life, and does the Franco App work with JellyBean and the kernel.

thanks!
[Samsung Galaxy Nexus] TEK112:
All yes.
[Samsung Galaxy Nexus] blackhand1001:
Any chance for a 512mhz gpu 210 build. Everything else the same.
[Samsung Galaxy Nexus] nosit1:
Thank you so much for that. Was trying to lookup the command. This shall help!
[Samsung Galaxy Nexus] StormCell:
Pardon my ignorance, but where are you getting 210? The highest release I see is 196. I just flashed JellyBelly and I'm curious to know if Franco's Kernel plays nice with JB.

Thnx.
[Samsung Galaxy Nexus] laureanop:
His GSM thread and yes 215 plays very nicely with jb

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] StormCell:
Thanks for the link, but is this for GSM, not CDMA? I'm confused, a little, because this is the Verizon thread. I wasn't aware Franco was on GSM.

Thnx.
[Samsung Galaxy Nexus] TEK112:
It's all the same for kernels. ROM's and radios are a different story.
[Samsung Galaxy Nexus] TEK112:
What?

franco.Kernel-r216-384GPU.zip

franco.Kernel-r216-512GPU.zip
[Samsung Galaxy Nexus] impulse101:
What? These are the jelly beans kernals
[Samsung Galaxy Nexus] Upstreammiami:
Yes I flashed one and now I have no status bar and navigation bar wtf?
[Samsung Galaxy Nexus] thelowend:
After installing 210 and rebooting, I got an update to my phone -- the "Android is updating" message. Normal?
[Samsung Galaxy Nexus] TEK112:
Happens everytime you wipe dalvik cache.

You probably should have noticed that by now. Have you flashed ROMs or just kernels?
[Samsung Galaxy Nexus] thelowend:
Just flashed the kernel and I didn't wipe a thing -- I never do when flashing those. I've flashed both wiping each cache and this has never happened. No big deal though, it didn't harm anything
[Samsung Galaxy Nexus] wonger007:
hope fast charge comes back soon ><
[Samsung Galaxy Nexus] tacosrdelicioso:
U need to b on a jb rom
[Samsung Galaxy Nexus] PARick:
I purchased the Franco app awhile back, and know that it was updated today. Where are the JB kernels located in the app? Thanks!
[Samsung Galaxy Nexus] sway40:
The jb kernels are not in the app yet, it's been said a million times already.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] PARick:
Sorry. I thought last night's update put them there.
[Samsung Galaxy Nexus] sway40:
I believe they won't be there until the source is released for jb.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Dakota0206:
R216 512GPU is the best kernel I have used on Jelly Bean so far. Great work!
[Samsung Galaxy Nexus] sway40:
I agree totally, im not using the 512 gpu but so far it's the best kernel for jb.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] laureanop:
Agreed

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] tacosrdelicioso:
I've used both 216 512 and 384....both wonderful.....will add another post with my battery shots....you'll be impressed just saying
[Samsung Galaxy Nexus] tacosrdelicioso:
OK this with 2100 vzw battery.....and 216 384
[Samsung Galaxy Nexus] tacosrdelicioso:
Wjoops...the graph one is a different time...this is the right one...sorry..
[Samsung Galaxy Nexus] I Am Marino:
Which JB ROM?
[Samsung Galaxy Nexus] impulse101:
You are correct they are in the app now
[Samsung Galaxy Nexus] impulse101:
Yes they are in the app
[Samsung Galaxy Nexus] cj1896:
So the latest update broke my color multipliers not persisting at boot. Frequencies,governors and gamma settings haven't persisted for some time. I think I read that you can't duplicate the problem. Is there a way I can get you a bug report of the problem.

Running milestone 4 and cm9 nightlies

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] tacosrdelicioso:
That was vicious v3...with beats delete of course. Now I'm on bamf you jelly v5 or whatever lol
[Samsung Galaxy Nexus] impulse101:
Still works for me
[Samsung Galaxy Nexus] sway40:
Everything works here too

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] apaxi:
Very helpful guys. Can you at least post your ROM? I too have experienced settings not persisting on reboot but was told to shut up and accept that this is the case with CM builds.
[Samsung Galaxy Nexus] Cadillac Johnson:
The color and gov settings haven't been sticking after reboot with the last couple app updates. I'm running Hybryd, AOKP base, and I had an older version of Franco's app backed up which does stick after a reboot.

My guess is the changes in the app not playing nicely with the init.d scripts. This has been the case on 3 different ROM's I tried over the weekend. All AOKP based. Tried tweaking the kernel mod script, and even removed it altogether but still no dice.

Finally un installed the app, and used a script to set the color and gov tweaks.

*edit* gramer

composed via cellular telephone
[Samsung Galaxy Nexus] TEK112:
lol

Anyway, Franco released another update which supposedly fixes the boot issues. It's worth giving it a shot.
[Samsung Galaxy Nexus] TheDoctor1177:
Where? Not on the download site unless its 217, which i'm still having the boot issue.
[Samsung Galaxy Nexus] raphenucleus:
An update to the app to fix the boot problems, not the kernel.
[Samsung Galaxy Nexus] Cadillac Johnson:
Most recent update seems to have fixed it for me. Thanks for the heads up.

We were talking about Franco's app not keeping the cpu and color tweaks through a reboot, not the kernel itself.

I don't think we'll see JB kernels on his app until there's something more stable to work off of.

composed via cellular telephone
[Samsung Galaxy Nexus] mike216:
There already there

sent from my precious nexus
[Samsung Galaxy Nexus] mcampbell:
I've gone to 3g and didn't notice a change in battery (over a couple days). Granted, I'm in a suburb of Atlanta which was one of the first cities to get LTE, so it could be that my area just has really good 4G coverage.
[Samsung Galaxy Nexus] Timdor:
I live in woodstock and work in atlanta. I usually have great 4g coverage. I don't use it though, only to preserve battery. Speed is good but I don't need it all the time
[Samsung Galaxy Nexus] b33zu:
Once this kernel is polished and doesn't make the camera not work and gets better battery life then imo's 1.6.6 kernel. I will look into this. Hoping......
[Samsung Galaxy Nexus] crupp:
It may be time then. No problems with the Camera or Video Camera, I have used both, battery is as good as any kernel out there.
[Samsung Galaxy Nexus] TEK112:
You need to let it sit for an hour with the screen off. Everytime you kick on the screen it hammers the crap out of the battery.
[Samsung Galaxy Nexus] Timdor:
I'm going to charge it back to 100% and do another wifi/3g graph and hopefully it's either fixed or helps me figure out what's going on.

I've gotten over a day before but my Android OS was still up there. Like 60%. Mostly sleep/wifi/standby.
[Samsung Galaxy Nexus] dcoy82:
Been using this kernel for a few days now, figured I would purchase the app off the market but it's giving me an error when I try to download it. Have tried several different times now.
[Samsung Galaxy Nexus] dawiseguy77:
Hey Franco I'm not big on this kernel tweaking governer stuff all because I'm not too knowledgable, and don't understand all of it, but I a wanted to let you know #12 left they way it is upon install is awesome! Keep up the good work.
[Samsung Galaxy Nexus] kichard:
Afternoon force stop camera at reboot do I need to continue to force stop the app as on use it?
[Samsung Galaxy Nexus] dobo84:
OK maybe this has been covered but should I leave the stock setting on the kernel alone or change the min to 350 idk I just want the best possible battery life with the best experience
[Samsung Galaxy Nexus] sway40:
I set my min down to 350 I was getting pretty bad bat life with it at 700

Sent from my Dell Streak 7
[Samsung Galaxy Nexus] sinik420:
try moving it up higher instead
[Samsung Galaxy Nexus] denpad2010:
I flashed this kernel and same ****y battery I just turned on my phone and in about 10 minutes my battery went from 99% to 92% damn I love this phone but I hate the battery life
[Samsung Galaxy Nexus] SomeGuyDude:
Why on earth would he move the minimum up higher?
[Samsung Galaxy Nexus] sinik420:
because the cpu would spend a longer time out of the c4 state on a lower frequency, causing a higher battery drain. follow ezekeel on this. I can post what he wrote if you'd like
[Samsung Galaxy Nexus] dobo84:
OK so sink you think bumping the min will help the batt than? I love this kernel but want the best result . This kernel is smoother than any other I've tried
[Samsung Galaxy Nexus] SomeGuyDude:
If this were in any way the case, they'd just make the phone sit at max freq perpetually.
[Samsung Galaxy Nexus] sinik420:
he did =]

10 charr

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

it just depends what changes dev made to the kernel, try glados 1.2 100-100 out

he keeps it on rootzwiki but allows the link to the thread to be posted just no links to the zips

http://rootzwiki.com/topic/14703-kernel17-jan-glados-v12/
[Samsung Galaxy Nexus] combatmedic870:
Any way for you to make it so grand theft auto will work like apex did with his kernel?
[Samsung Galaxy Nexus] pvspencer22:
I was having AndroidOS battery drain problems and following franco's point in OP tried starting the camera and closing it at startup. This didn't stop the issue for me, but I went with the assumption that it could still be Google Talk causing the issue. This afternoon I froze Google Talk using Titanium Backup and the issue has gone away.

I'll keep you posted if anything changes, but for now I would say if you're experiencing the AndroidOS issue - freeze Google Talk.
[Samsung Galaxy Nexus] yami951:
Woke up this morning to my phone stuck in a boot loop. Was on it all day yesterday without a problem, but the night before I nandroid restored back to aokp m6 and franco r196. Don't know if it going into a deep sleep did it, or its because I didn't wipe. Any advice?
[Samsung Galaxy Nexus] impulse101:
jb kernals are in franco's app
[Samsung Galaxy Nexus] rgoyena:
I agree. My settings are not holding.
[Samsung Galaxy Nexus] blackhand1001:
On 196 on cm9 every time I reboot the trinity contrast setting are set all the way to the lowest -24. It makes everything greenish. All the other settings restore fine. Its just trinity contrast. Really annoying.
[Samsung Galaxy Nexus] jamor414:
Team liquid just pulled this kernel from their recommendation list for being unstable...

Is the JB kernel unstable?
[Samsung Galaxy Nexus] BrandT90:
I haven't had any problems with it when using it with any of the JB ports.
[Samsung Galaxy Nexus] dp92180:
I agree and furthermore the best battery life I've had on any ROM/Kernel combination I've ever run, JB or ICS.
[Samsung Galaxy Nexus] timbck2:
Neither have i.
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
There have been issues because fsync is disabled by default, which can cause corruption on JB and leads to long boot times and/or bootloops. This happened to me every time I used r217, but now I am using LK, I have had no problems.