yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] playabigfoot:
No problem here either with cab checked
[Samsung Galaxy Nexus] franciscofranco:
Because I forgot to enable it.
[Samsung Galaxy Nexus] yellowdie:
Grrr.... lol, thanks.

Specifically the three people who marked that they were getting the rolling reboots: @shawnaye, @garuhhh, @SailorSaucy. Can you check what I posted on the last page?

EDIT: So there were pages and pages of people reporting issues with the r32x kernels, but over half of the people in the chart are reporting no issues. lol
[Samsung Galaxy Nexus] Puzzlegirl:
Yes, I thought it might be PGM, which I uninstalled before flashing r328, so I'm just reinstalling to see what happens. At the moment, everything is running great! I've used this phone exclusively today, leaving my poor N4 still awaiting a new Franco Kernel flash! Still love this phone... :)
[Samsung Galaxy Nexus] The Gingerbread Man:
Same here yellow, just had over 5 minutes deep sleep and phone woke up fine. I didn't have any problems either before.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
I'm adding a PGM column.
[Samsung Galaxy Nexus] The Gingerbread Man:
How about a hw version one? The info that can be found on the fast boot screen.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] tuemdeluxe:
For me, disabling PGM before flashing r328 solves the problem. No more reboots directly after entering sim lock!
[Samsung Galaxy Nexus] :
I thought it was kernel related which is why I posted it here...

I realized afterward it was an AOKP thing. However did not have these issues with stock or Trinity kernels with AOKP, so FYI.
[Samsung Galaxy Nexus] zephiK:
Personally for me the reboots came from the Franco app, after I froze it. Uninstalled it and reinstalled the app, all of my reboots went away. Now r328 + Xylon works great.
[Samsung Galaxy Nexus] ÜBER™:
Everything was running great for a while. Then got a random reboot. WiFi wouldn't work afterward had to reboot. http://db.tt/dzlsfRSF last_kmsg

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] galakanokis:
I have had no issues with 325-328, no SODs or bootloops until I activated PGM. I normally don't use it but it is installed. Bootloops galore with PGM activated. Had to wipe cache and dalvik to end the loops. Something for people to check if you are having issues.

SODs galore now to. Activating PGM definitely did something to the phone, no issues for two days before this.
[Samsung Galaxy Nexus] KJW979:
Yellowdie, comparison chart was great idea. No SOD or bootloops for me so far with r328, stock values except max/min of 1536/384. But last time posted everything was fine had a SOD, see if jinxed myself again.
[Samsung Galaxy Nexus] kunalwanvari:
i think yellowdie i right .. at times when screen dims .. it just shuts down .. and noin happens den .. pressing the volume rocker just toggles phone frm vibration to silent ! sorry cant provide ksmg log .. but whenever iv had an sod ( at times for many boots ) its only when i leave screen unatended fr half a min ! and dont unlock it as soon as its booted .. franco ur the man .. u know bettwr .. may b this info helps
[Samsung Galaxy Nexus] finesse:
What is PGM please?
[Samsung Galaxy Nexus] gianton:
r328 on AOKP 1126 is rock stable since this morning, applied osm0sis UV settings.
[Samsung Galaxy Nexus] zephiK:
https://play.google.com/store/apps/details?id=net.ponury.pgm2&hl=en that's PGM.
[Samsung Galaxy Nexus] Kurre:
PGM Nexus aka slide2wake. Gives you an option to lock/unlock your phone with slide etc. Found from xda and playstore.

Sent from my slimbeaned GNex :)
[Samsung Galaxy Nexus] finesse:
Thanks for the reply.

Many thanks to franco for his hard work.
[Samsung Galaxy Nexus] Puzzlegirl:
I uninstalled PGM before I flashed r328, but after reinstalling and using it a lot in the past couple of hours I haven't had a problem, even after rebooting.
[Samsung Galaxy Nexus] franciscofranco:
So PGM's ****ing everything up... how am I not surprised.
[Samsung Galaxy Nexus] lparcshinoda:
I hope you're not thinking about not supporting PGM anymore :( It's a very usefull tool
[Samsung Galaxy Nexus] galakanokis:
Haven't tried this as I really don't use it or find a need for it. Only activated it to see what it would do to the phone on these new kernels. From the past I know install order of PGM vs. kernel can have a big impact on how your phone runs.
[Samsung Galaxy Nexus] androo45:
PGM works flawless on r315.
[Samsung Galaxy Nexus] gianton:
PGM working great here on r328.
[Samsung Galaxy Nexus] alex999999:
for me wifi-thetering isn't working on r328

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] Master94ga:
I'm using your kernel 328 with stock rom and work very well. ;)

I installed also your app but don't show the last version of kernel but very old one:
[Samsung Galaxy Nexus] dyndragon:
sad to report that r328 + CM10.1 skank builds end up with the phone and NFC process crashlooping at phone start up.
[Samsung Galaxy Nexus] Savant:
Yeah I found that out earlier I uninstalled everything was fine and installed it again after a clean install and everything went haywire. Its probably not 4.2 yet or the Dev is still working out the kinks.
[Samsung Galaxy Nexus] franciscofranco:
I know... Will be fixed soon.

I haven't updated the free, and yes thats a very old kernel.

I know, current ramdisk is not compatible with CM yet.
[Samsung Galaxy Nexus] punkeroso:
Here PGM si working flawlessy on r328...
[Samsung Galaxy Nexus] franciscofranco:
Yes, thats not my problem.
[Samsung Galaxy Nexus] Craxx:
After restore a backup with 318, i wipe cache and data from fku and flashed stock kernel and after reboot i flashed 328 with disabled pgm app. After reinstalling pgm app all works fine;)

Craxx;)

Send from my Galaxy Nexus with Tapatalk :)
[Samsung Galaxy Nexus] Master94ga:
Why? :(
[Samsung Galaxy Nexus] yellowdie:
Well the free version of the app doesn't have all of the features of the paid version, and it's probably a much lower priority. So I would image that he wants to finish up the paid version first, then he'll fix up the free one. :)
[Samsung Galaxy Nexus] :
I'm a couple pages ahead of you :P
[Samsung Galaxy Nexus] :
Has the paid one been updated yet? Mine still says its not compatible with 4.2 still.
[Samsung Galaxy Nexus] pele78:
:eek: Closes tab
[Samsung Galaxy Nexus] giannisgx89:
Would be nice if franco could add this governor https://plus.google.com/109078966818501160423/posts

Users report massive battery drain improvements.
[Samsung Galaxy Nexus] :
Seems pretty sick sounding. Would be nice for sure. :good:
[Samsung Galaxy Nexus] kCelsius:
Using r328 on Xylon 006 and things are pretty goood - everything seems to run a tad smoother and snappier than r327...not sure why but thigns are definitely snappier.
[Samsung Galaxy Nexus] yellowdie:
Not yet. Franco doesn't feel like it's fully 100% stable yet. Once he does, he'll update it.

Uhhh... "Intellidemand 4.0 completely takes over the management of quadcore and cpu frequencies!"

Now where did I put those darn other two cores for this phone? I know I had them laying around here somewhere... :rolleyes:
[Samsung Galaxy Nexus] giannisgx89:
Hmmm... Did you read anywhere that it completely takes over the management of "only" quadcore cpu frequencies!

I guess not. Trying porting it if possible isn't bad idea.;)
[Samsung Galaxy Nexus] franciscofranco:
That governor is not for Tuna and I don't use any of faux's stuff, period.
[Samsung Galaxy Nexus] giannisgx89:
Got it big man! Relax, i was just asking :)
[Samsung Galaxy Nexus] franciscofranco:
And I was just answering :)
[Samsung Galaxy Nexus] Phoenix Wright:
I used his kernel for a lot of time and it was very snappy but I've never got it to be stable, maybe my phone is allergic to it :P Yours has never crashed on me... I value stability over smoothness. And with Fsync off there's not a very noticeable difference in the latter either.:good:
[Samsung Galaxy Nexus] yellowdie:
lol. And I was just giving you a hard time, while waitin' for Franco's response. I was intrigued because I like new things-- like dyninteractive, and whatnot. :D
[Samsung Galaxy Nexus] Khrushy:
BAM! I checked the disable CAB box and rolling reboots are a GO! Exactly as you described, if I don't unlock the phone upon boot, it'll reboot after about 1 minute with the CAB box checked.

Nice work Sherlock!
[Samsung Galaxy Nexus] :
Thanks for the heads up man.
[Samsung Galaxy Nexus] eng.stk:
That's it, PGM is the problem for me too on r328. Once I disabled it on OGM free app, installed kernel and no more reboots.

Although, once I enable PGM it reboots again, so until francisco can check this, I'm staying on r327.

With both CAB enabled and disabled, no more reboots as long as PGM is disabled. So for me the issue really is PGM.
[Samsung Galaxy Nexus] Phoenix Wright:
Did you try disabling it, uninstalling it and reinstalling it? I don't use it anymore, but when I did, I had to do this for some kernel updates.
[Samsung Galaxy Nexus] Khrushy:
I don't, and never have used PGM, so it's clearly not the cause of the CAB check box reboots in my case at least.
[Samsung Galaxy Nexus] ttabbal:
This worked for me on 328, looks like there's something in the re-install that fixes it... Different kernel module version getting installed perhaps?
[Samsung Galaxy Nexus] eng.stk:
Yeah thanks guys, looks like troubled kernel module... I uninstalled the App, then reinstalled root and busybox (just to be sure) reinstalled the App and all goes smooth (disabled auto startup, just if trouble comes again).

Looks like until r327 forced/cleaned module on install, it works just fine. Maybe francisco changed something particular to this, don't know ( my ROM is the same with both kernels)
[Samsung Galaxy Nexus] nikulogical:
Not using pgm but I can confirm r328 fixed the sods which I had in previous versions.
[Samsung Galaxy Nexus] Phoenix Wright:
Yup, seems that the fK app and pgm were causing these issues... can't wait to update and enjoy the added smoothness, as soon as tethering is fixed:fingers-crossed:
[Samsung Galaxy Nexus] mariachi202:
Been using PGM and franco since forever. No issues whatsoever.
[Samsung Galaxy Nexus] kyokeun1234:
Never had sod with this kernel in my life. Not only that, it ID the fastest kernel for my Galaxy nexus :)

Since Franco is supporting also nexus 4, I can have that Franco's awesome magic when I get my nexus 4! Thanks
[Samsung Galaxy Nexus] Necrolust:
Am I the only one who is experiencing low fps swiping between home screens in Nova launcher with any kernel apart from stock? This happens on any home screen animation apart from 'none'.

Like I said, its not specific to this kernel but any apart from stock

---------- Post added at 02:58 AM ---------- Previous post was at 02:56 AM ----------

Actually its only with a live wallpaper
[Samsung Galaxy Nexus] joaquinf:
Awesome kernel is awesome
[Samsung Galaxy Nexus] osm0sis:
You notice how it says "Not charging" instead of "Discharging" now? Not sure if that's a f.K thing or a 4.2 thing.
[Samsung Galaxy Nexus] Piccles:
Looks like PGM has been updated

Paranoid Gnex
[Samsung Galaxy Nexus] joaquinf:
Lol I did not. Have you checked English uk?

Edit: what I'm sure though is that it has to be android thing. Not kernel related at all
[Samsung Galaxy Nexus] aimcr7:
I think its 4.2 thing, checked 4.1.2 it says discharging :rolleyes:
[Samsung Galaxy Nexus] osm0sis:
Even on 4.2 stock kernel? Kernel could make a difference since it can affect the charging (eg. USB Fast Charge). If that is the case then just add it to the list of things Google messed up in 4.2 ;)
[Samsung Galaxy Nexus] joaquinf:
So batt status is read from the kernel instead of the user interface?
[Samsung Galaxy Nexus] Wynnded:
I still have the stock 4.2 kernel and when it's unplugged it shows "Not Charging".
[Samsung Galaxy Nexus] osm0sis:
4.2 it is. Garbage Google. Garbage.

I dunno. Likely just a change Google made where it displays "Not charging" both when in discharging and "on charger but not charging" states. Not sure if it's a mistake or intentional. The UI being less informative than before sounds like an error to me. :p
[Samsung Galaxy Nexus] aimcr7:
Lol, it should be user interface thing. :confused:

Looks like they are drunk when building 4.2, so much thing messed up. :D
[Samsung Galaxy Nexus] yellowdie:
I am one of the weird ones but I really like 4.2!! I think the fonts (especially the clock) make it look so much smoother and classier. :D And the only "bug" that affects me personally is that the quick setting panels really should have been toggles and customizable from the beginning. None of the other reported issues have impacted me at all. That's just my random opinion though.

:) :D :laugh: :good:
[Samsung Galaxy Nexus] joaquinf:
Fast Charge app is reporting things the way it should be. So blame Google :p
[Samsung Galaxy Nexus] osm0sis:
I agree. They pretty much **** the bed. The UI is slowly moving away from Holo as can be seen starting with the new notifications in JB, now quick settings and the Clock app (red accent text? really?), which I think is a bad move. Holo looked futuristic and cool like Tron or something plus the most amazing thing about ICS was the unity of theme across all the system apps and UI. Right now it's disjointed, and what they seem to be moving toward is all text-based, sort of like Metro design language. Hopefully they come to their senses or Key Lime Pie might be as hideous as Gingerbread again.

Yup so I am right then. They just used the "Not charging" string for both of those states for whatever reason.. Crazy people.
[Samsung Galaxy Nexus] joaquinf:
I agree on that one. They are making some moves that I can't figure out yet, like the red text in the Clock app or the quick settings tiles.

They should stick to the original sketch and improve it following their guidelines, I was expecting more of polishing over the design flaws they've carried throughout the previous versions (like a non standard icons size ughh). However, 4.2 is an acquired taste. I'm actually liking it and I find it as good as 4.2.1 now. Thanks to our beloved developers who are doing a great job fixing and improving Google *****

Pretty much, I remember a similar story with htc going from sense 3.0 to 3.6. They changed so many things between English us and English uk. For example wifi policy in English us was: never for never go to sleep while screen off and in English uk the same never meant never keep the wifi on when the screen is off. So much failure /facepalm
[Samsung Galaxy Nexus] lpglam:
r328 wifi ap not working :(
[Samsung Galaxy Nexus] joaquinf:
I'm on the same boat, I like 4.2 now :p
[Samsung Galaxy Nexus] kCelsius:
Just curious but what freq. and other misc. settings are you running at?
[Samsung Galaxy Nexus] joaquinf:
Wifi ap?

Is your wifi network security set to wep? If so, try changing it to wap2 its more secure and it'll work with the newest wifi drivers
[Samsung Galaxy Nexus] aimcr7:
I agree, i hope they redesigned the UI in KLP, so we dont get bored. :)

They forgot december in birthday, not charging on battery stats. :banghead:
[Samsung Galaxy Nexus] rrohanjs:
how do i use the .img file ? or flashing the zip file is the same thing ?
[Samsung Galaxy Nexus] Khizar:
+1 i think 4.2 is pretty good.. i dont even care about the quick settings tbh

---------- Post added at 09:55 AM ---------- Previous post was at 09:54 AM ----------

its the same thing.. img file can be flashed in fastboot or you can put it in the kernel apps backup folder and restore
[Samsung Galaxy Nexus] osm0sis:
Haha well it looks like they're leaning towards a redesign. I'm just worried that the new Clock app is how it's going to be system-wide. And to change things incrementally makes the whole thing look foolishly ununified/unprofessional. Maybe the Clock app is them testing the waters. I guess that would make sense. But generally if you're going to change the UI you should do it all at once.

I like 4.2 as well, especially on my N7 with the multi-user support. But I still kind of liked ICS the best visually.

Check out the progression through my screenshots here: http://xdaforums.com/showthread.php?p=23618405#post23618405. Notification pane is just getting worse. ;)
[Samsung Galaxy Nexus] ShensMobile:
I'm having an issue. Everytime I flash this in fastboot, my computer freezes and BSOD's. Anyone else have this problem?
[Samsung Galaxy Nexus] osm0sis:
I'd make sure you're using the latest naked driver.
[Samsung Galaxy Nexus] ShensMobile:
I'm using whatever's included with the Nexus Toolkit. Where would I get the latest naked driver?
[Samsung Galaxy Nexus] Khizar:
they are posted in the dev section.. "universal naked drivers" latest is 0.97 i think
[Samsung Galaxy Nexus] osm0sis:
0.72 :)

http://xdaforums.com/showthread.php?t=1379875
[Samsung Galaxy Nexus] aimcr7:
Yes i like the feature but the design is just getting worse. I agree with you they should do it all at once.

For franco sorry for OT mate. :)

Back to topic, i dont know whats wrong, but looks like i hardly getting the same battery life as 4.1.2, i used to be easily get 16-19hours and 3.5hours of screen on. But on 4.2 it just 12-14h and 3h screen on. But i'll give it sometimes hope it'll get better.
[Samsung Galaxy Nexus] AndAllThingsWillEnd:
Quick question... Has Franco stated whether or not he was going to stick with this newer Wi-Fi driver? I unfortunately am stuck with wep in multiple places and remember when he implemented these drivers a while ago.

Back then he stated that he didn't want to stick with something that didn't work for everyone, just hoping it would be the case again.
[Samsung Galaxy Nexus] aimcr7:
Looks like he will be stick with this driver and try to fix wifi hotspot issue.
[Samsung Galaxy Nexus] ahse0w:
which kernel version has a working wifi hotspot? for android 4.2?
[Samsung Galaxy Nexus] kecinzer:
#328 for day and half, no SODs or reboot. Only thing that I miss is WiFi tethering.
[Samsung Galaxy Nexus] osm0sis:
I'll see you and raise you. ;)

Honestly I think this is the best I've ever seen it, especially epic considering 4.2 started out worse than 4.1.2 for drain. If I wasn't going to bed right now I'd frig around for an hour to see if I could make the 4 hour club, but it's looking pretty optimistic that I could! :cool:

[Removed images - 1d 0h 18m on battery with 30% left. 2h 47m Screen Time on.]
[Samsung Galaxy Nexus] marshy73:
My office router is on WEP and I have no problems connecting to it and going online throughout the day.

I'm on 328.
[Samsung Galaxy Nexus] AndAllThingsWillEnd:
Just tried 328 and it's a no go for me. Are you sure you're using wep?
[Samsung Galaxy Nexus] marshy73:
Yup... It's on WEP.
[Samsung Galaxy Nexus] playabigfoot:
Hi! I have a weird problem when playing NFS: most wanted. It's running really slow the sound is normal but the game and clock are like slow motion. Tried with stock kernel works fine. I'm on latest rasbeanjelly with r328
[Samsung Galaxy Nexus] sherincal:
Known issue, it's caused by the game thinking your device has a more powerful GPU than it has. Something to do with the kernel and it's been raised one hundred million times already.
[Samsung Galaxy Nexus] playabigfoot:
So no fix for that?
[Samsung Galaxy Nexus] aimcr7:
No fix for now :)
[Samsung Galaxy Nexus] playabigfoot:
That sucks
[Samsung Galaxy Nexus] franciscofranco:
Use Performance governor when playing NFS, change it back to interactive when you're done. I don't really care about badly written game apps, sorry, the kernel will run as good as it should and not cater for specific apps that break because they like to play funny with the code. ;)
[Samsung Galaxy Nexus] gummie:
But it would be really great and quite a feat if that would be solved. Like you said its only a specific app. I'm trying to locate how this Kernels code is any different on morfics as it doesn't break that specific game. Trying to solved it and if luckily might compile something that does not break apps.

PS: I'm sorry for discussing other Kernel here but like I said I'm trying to solve this on my own. I hope some could help. I like saying this Kernels name on my accent so I'm really into it :laugh:
[Samsung Galaxy Nexus] joaquinf:
Nice! That's impressive buddy. I think this is the best performance - battery balance I've found so far. :thumbup:
[Samsung Galaxy Nexus] tetrakinitis:
From yesterday no sods or random reboots with r328 on xylon 006. Default kernel settings, cab disabled. The smoothest xperience on 4.2 till now. Thanks Franco. The only think i'm noticed is redraws in the app drawer of stock launcher after some usage, something that i didn't had with the latest releases (r300 e.t.c) in 4.1.2. Keep on. :thumbup:

Sent from my SmoothCriminal™
[Samsung Galaxy Nexus] Khizar:
yeah i used r328 overclocked to 1536 with xylon 006 yesterday no issues and updated to xylon 007 today still overclocked to 1536 and no issues whatsoever
[Samsung Galaxy Nexus] psxsnake:
franco kernerl updater does not recognize 4.2 so to load kernel 328, is possible only in CWM?
[Samsung Galaxy Nexus] Khizar:
what do you mean? its possible to restore the img file using FKU
[Samsung Galaxy Nexus] Roscopcoletrain:
I think what he means is 328 isnt in the free version of the kernel updater, so how else does he flash it.
[Samsung Galaxy Nexus] MontAlbert:
francisco,

Loving your kernel so far.. have it clocked to 1.4 and undervolted at each step by about 25mV...

Is there any chance at all we could get it as an insecure boot image that allows us to adb into it -

eg:

E:\Android\Inspire\ICS>adb push Launcher2.apk /system/app/Launcher2.apk
failed to copy 'Launcher2.apk' to '/system/app/Launcher2.apk': Read-only file sy
stem

E:\Android\Inspire\ICS>adb remount
remount failed: Operation not permitted

thanks
[Samsung Galaxy Nexus] h1o:
delete this file, before or after the flash kernel?
[Samsung Galaxy Nexus] inffy:
after flashing the kernel
[Samsung Galaxy Nexus] mike1986.:
Doesn't matter at all :)
[Samsung Galaxy Nexus] Epedemic:
I get the same issues... Reverting to stock kernel to see if that helps.
[Samsung Galaxy Nexus] franciscofranco:
I guess some devices can't handle the CPU and GPU OC. I'll have to deliever a kernel without OC I guess.
[Samsung Galaxy Nexus] jeezus:
Hmm, cpu spy is showing only 1400mhz, 700mhz and deep sleep for the latest kernel (did not try it before). 0% running on 700mhz and seems to get a bit warm.
[Samsung Galaxy Nexus] franciscofranco:
Undervolt it with the values in the OP and see if it improves.
[Samsung Galaxy Nexus] GchildT:
Compare SetCPU vs NoFrills.

There may be a difference....

I stopped using SetCPU on the first kernel because, for some reason, that was causing Lag. After i uninstalled, everything started running smoothly again. I then installed NoFrills.

only problem No UV editing capability via the app.
[Samsung Galaxy Nexus] Shetlander:
I too had an episode of corrupt screenusing the 07/12/11 kernel. Couldnt get into SetCPU to change anything but I think the CPU was running at 1400mhz instead of 1200mhz which it should have been set at.

I would prefer a kernel with everything as is now but the 1400mhz speed removed if thats possible.
[Samsung Galaxy Nexus] franciscofranco:
Thanks everyone for the feedbacks. I'll make sure I'll release two different kernels, one with OC and another one without, don't worry. I'm a little short on time and without having the device is quite difficult to handle every request/suggestion in a fashionably good time, but work is being done. I'm currently in contact with the creator of jRCU and he's going to port his work to the 3.0 kernel so we use it in our device :)
[Samsung Galaxy Nexus] Shetlander:
Dont know if this has anything to do with this kernel but the last day or too my network signal has been up and down like a yoyo. Im also using the baseband XXKK6.
[Samsung Galaxy Nexus] DDM123:
Excuse me if this has been answered, but I'm using the LTE version with my Verizon Gnex. There doesn't seem to be a /system/lib/egl/libGlES_android.so file and the kernel doesn't allow the phone to boot. I'm running Revolution HD 1.3.1 and the phone doesn't get past the Google logo when I try to boot it. I must be doing something wrong.
[Samsung Galaxy Nexus] franciscofranco:
I'm still a little unclear about the LTE version. I don't know if the kernel is different to be honest.