yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] osm0sis:
SuperSU binary updates in the future might put it back. Not sure. Only down-side would be if you switch to a kernel that doesn't have the native service you would lose root, but any smart kernel dev who's got a custom ramdisk should be including the service, and if you go back to stock kernel which definitely doesn't have the service, you could always just reflash the zip. Not really a big deal either way in my opinion. A service is how custom ROMs will likely by doing it as well.

Edit: Haha whoops! Just noticed I uploaded the wrong img/zip, it was of a test version that uses the install-recovery.sh instead of the service. Reuploaded v4 with the proper native daemonsu service. Please get it again if you've downloaded it already. :good:
[Samsung Galaxy Nexus] cmstlist:
Downloading the hybrid kernel fails for me. The page just stalls out for a while and then on desktop I get "Problem loading page". On mobile I get "Download unsuccessful".

EDIT: Dev-Host has hinted at some server trouble on their Twitter feed. That would explain it. Are there any mirrors available?

EDIT #2: A few hours later it was working again.

I was coping just fine on stock kernel until I tried streaming an MP4 from my desktop network share in BSPlayer. It was extremely jerky. I installed the hybrid kernel, set it to row scheduler, and now it's buttery smooth again. Yay!
[Samsung Galaxy Nexus] :
Hello,

Sorry for the stupid question,

But is this kernel ION-Enabled?

Thanks,

Rinse
[Samsung Galaxy Nexus] bigknowz:
busybox

Do mount / remount / chmod need busybox prefix as well? Setting up init.d scripts.
[Samsung Galaxy Nexus] shreddintyres:
[MENTION=4544860]osm0sis[/MENTION] [MENTION=3292224]franciscofranco[/MENTION]

Is the 4.3 hybrid you have posted based off the 4.3 JWR66V or is it off of JSS15J, the reason i ask this is that there is enough of a difference between the two firmwares especially on the kernel side of things that Kernels from JWR66V will not play nicely with JSS15J, they will boot and what not but they will appear choppy and otherwise laggy when if used on the proper base they will fly. Do we know if Franco intends to use the Stock Base (JWR66V) or the AOSP base (JSS15J, newer). I'm hoping that going forward he decides to stick to AOSP since it has many kernel and gpu improvements to start over the Stock Base.

Source of information: http://xdaforums.com/showthread.php?t=2382880
[Samsung Galaxy Nexus] bunnahabhain:
Seems that franco is going for JWR66V:

http://xdaforums.com/showpost.php?p=44054622&postcount=41235
[Samsung Galaxy Nexus] shreddintyres:
Hmm this will be interesting to see how things develop as the new N7 is being released with Stock as JSS15J. (shrug) o well I can't complain I'm just coming along for the ride :)
[Samsung Galaxy Nexus] blipp:
JSS15J is just for the new N7. The guy who makes my gnex ROM (Shiny ROM) used JSS15J as the base at first but JBQ (Goole AOSP guy) said that version just contained new N7 specific changes and all other devices should use the other version.
[Samsung Galaxy Nexus] sui785:
The GPU commits are for N4 and N7, nothing for GNex so I don't see any reason as to why we should install JSS build.
[Samsung Galaxy Nexus] Pkt_Lnt:
It appears there may be benefits, at least for wifi.

http://xdaforums.com/showthread.php?t=2382880
[Samsung Galaxy Nexus] JohnstonF:
Off topic

Is usb otg support a kernel or Rom thing?
[Samsung Galaxy Nexus] osm0sis:
You don't need the init.d scripts. It's all done correctly in the ramdisk.

The hybrid I posted is based off neither since it's the JDQ39 zImage with a modified JWR66V ramdisk.

Like Franco said, they'll sync it up sooner or later.
[Samsung Galaxy Nexus] e753:
I don't find anymore the gpu settings on Franco kernel apk. Is it normal?

Thank you
[Samsung Galaxy Nexus] ChazzMatt:
Long time now (8 months?), Franco kernel is locked to 512 Mhz scalable. Meaning it will use UP TO 512 Mhz depending on your graphics needs. You don't need to adjust anything. Franco figured out how all the GNex could run at 512 Mhz GPU if necessary. (With other kernels, some Galaxy Nexus have display "sparkles" at 512MHz).

But it doesn't stay red-lined at 512Mhz, so it doesn't burn battery. So, no need for different kernel versions and no need for anyone to manually adjust GPU speed.
[Samsung Galaxy Nexus] e753:
thx
[Samsung Galaxy Nexus] sui785:
Flashed latest hybrid kernel and am having wakelock. Previous one didn't have it.
[Samsung Galaxy Nexus] The Gingerbread Man:
Thanks Os finally got round to flashing the hybrid kernel after running completely stock 4.3 since release day. 4.3 didn't feel laggy for me in fact I noticed a fair improvemnet in terms of smoothness but I also noticed the rather aggressive back ground killing of apps at times and a notable amount of apex launcher restarts. There's certainly an improvement in terms of feel over stock kernel but haven't had proper chance to test lmk value yet. Thanks for getting something out for us on 4.3, appricaited :)

---------- Post added at 01:36 AM ---------- Previous post was at 01:35 AM ----------

Android os is apps, so an app you have or haven't closed is keeping you awake
[Samsung Galaxy Nexus] akash3656:
I don't know if this would help, but try getting a GPS lock then turn GPS off. It may help out with the wave locks.
[Samsung Galaxy Nexus] bigknowz:
init.d in 4.3

Trying another kernel and failing to get init.d working again on 4.3. run-parts/etc/init.d failed too. busybox run-parts /etc/init.d works. Any and all thoughts appreciated on what commands now require a busybox prefix.
[Samsung Galaxy Nexus] Pkt_Lnt:
ignore me
[Samsung Galaxy Nexus] osm0sis:
init.d support will always work if you've got the correct call in the .rc files and permissions on the files/folders.

Either init.rc or init.tuna.rc needs this call added:

# Execute files in /system/etc/init.d before booting
service run-parts /sbin/bb/busybox run-parts /system/etc/init.d
class main
oneshot

Francisco puts it at the bottom of init.rc. Obviously he also includes his own busybox binary at /sbin/bb/busybox to make that work. You could also change that to /system/xbin/busybox if you want to rely on the system one being present. If it doesn't have that and you're trying to do this you need to edit the ramdisk with my Android Image Kitchen.

Then from Terminal Emulator, make sure your init.d scripts are in /system/etc/init.d/ and then set the perms all at once: su -c chmod -R 755 /system/etc/init.d

As for busybox prefixing, it depends. renice only needed busybox because the toolbox version doesn't work the same anymore. Simple remounts as rw or ro would be fine with toolbox's mount, but for more complex operations where you're using mount flags and you might want -t auto you'll probably want to use busybox mount (that's why it's always been that way in 875mntsettings). I've updated 975experimental and uploaded it the other day to reflect busybox being necessary for renice.
[Samsung Galaxy Nexus] sui785:
I reflashed older build of hybrid kernel and everything is back to normal.
[Samsung Galaxy Nexus] angourakis:
osm0sis, I heard Francisco is pretty busy with Nexus 4 kernel and don't have the patience to maintain two different kernels right now. I really appreciate your work, always improving what is already considered a great job! Why don't you ask him permission and continue his work releasing new versions with new features, etc etc?
[Samsung Galaxy Nexus] osm0sis:
Coding kernels is well beyond my expertise. If I did ever fork it, I wouldn't be able to do much other than merge other people's work. That said, I don't have time to figure out how to build kernels right now, let alone maintain one. I'm just spare-timing it between full time work right now.
[Samsung Galaxy Nexus] h1ghland3r:
Hi guys,

Yesterday I updated the franco.kernel, and after that the app doesn't open anymore. I've already rebooted my GNex.

I'm with r384/4.2.2.
[Samsung Galaxy Nexus] abalam:
Just delete and install it again

sent from my ???❎//?
[Samsung Galaxy Nexus] h1ghland3r:
Thanks. =]
[Samsung Galaxy Nexus] Ladaga:
When the new kernel?
[Samsung Galaxy Nexus] Seraz007:
Please do stop asking for ETAs -__-
[Samsung Galaxy Nexus] ChazzMatt:
Today at 4pm.

Oh, wait. No, that's just when I get off work.

Asking an ETA on volunteer dev work is like asking for future lottery numbers. Any answer you may get is just a guess, so don't go bet money on it. :) The good devs don't even try to answer. It's done when it's done.

___________

Sent from my Galaxy Nexus I9250
[Samsung Galaxy Nexus] Ladaga:
It's only a question, I'm user of franco since r15.

They are all brave in front of a screen...
[Samsung Galaxy Nexus] Seraz007:
lol wut!>?

you've been around from 2011 and should know better that

if you're asking for ETA, you're gonna have a baaaad time ;)
[Samsung Galaxy Nexus] creeve4:
What's the big deal about asking for an ETA? So many people act like it is a sin next to murder...

I understand that it could be annoying if EVERYONE is ALWAYS asking, but what does it hurt to ask? We have already seen that most Devs don't answer questions that they don't have an answer to or don't want to give an answer to.

A saying that I live my life by: "if it doesn't apply, let it fly"
[Samsung Galaxy Nexus] shreddintyres:
I think overall, the sentiment is not so much the question as it is the potential sentiment underlying it. Not saying that the individual who asked is like this just giving my two cents.

But that question gets perceived as whoever is asking the question has some sense of obligation as if the devs owe him or her something. While often this is not the case and people are just merely curious, it has happened enough times where it came with a sense of entitlement which rubs devs the wrong way when most if not all devs do this in their free time on their own accord expecting nothing in return.

The other part comes from the general respect that many feel (myself included) that devs have earned for dedicating their times and efforts towards various modifications which they share with us irregardless of their motivation that lead them to develop in the first place. Many see the asking for ETA's as a sign of disprespect going back to the sense of entitlement. Generally speaking it has become the mantra that asking for ETA's is taboo as devs generally dont give one on account that they prefer to put out a quality product for which there will be minimal errors or a quick product which can be wrought with problems.

Either way the unspoken rule is not to ask, but there is merit to the notion that devs will only answer questions that they are inclined to answer. But there comes a point where one person asking will result in a cascade of individuals asking which can ultimately piss off the dev and incline them to stop development or discontinue release of their work.

Again i just want to be clear this was not directed at the quoted individual or the individual who had originally asked, this is just my personal opinion take it as you may.

- Cheers
[Samsung Galaxy Nexus] creeve4:
One more point, the "E" in ETA is for estimated. I think of it as: approximately when do you expect to have something.

Answers can range from "August 5 at 5pm" to "mid-September" to "maybe by the end of the year."

I do understand the negative connotation towards asking for an ETA due to those who ask out of entitlement. I can also see not asking as a way to site respect to the Devs.
[Samsung Galaxy Nexus] thegtfusion:
It comes when franco wants to download the new source, and integrate all the new features, then he compiles it. Then he flashes it, and if he thinks it's good enough to be released he releases it. THAT's when it comes. :)

;)

Sent from my Nexus Prime
[Samsung Galaxy Nexus] tragulus:
Deleted, sorry accidentally typed on tapatalk :(
[Samsung Galaxy Nexus] abalam:
[MENTION=4544860]osm0sis[/MENTION] You have compile a kernel for 4.3 (franco.kernel-r384-hybrid. My question for what version can I use your kernel, for JWR66V or JSS15J??

TNX
[Samsung Galaxy Nexus] thegtfusion:
for both. both are 4.3 ;)
[Samsung Galaxy Nexus] abalam:
Okay thanks man. Now I have a problem the last of osm0sis and now have no root in purity. This wont solve by flashing SU??

Edit: flashing latest SU problem resolved
[Samsung Galaxy Nexus] Pkt_Lnt:
There are kernel differences that cause screen / graphics issues.

http://xdaforums.com/showthread.php?t=2382880

Please read the OP, there is far more to it, but this quote is the summary:
[Samsung Galaxy Nexus] osm0sis:
Mine is based on neither sources.. :p

It's not even a compile, just a 4.2 zImage repacked with the 4.3 ramdisk. So it may work fine on either 4.3 ROM build. Let me know how it goes!
[Samsung Galaxy Nexus] detritu5:
I have issues in #14.1 with data conection. When I turn off the screen, data conection lost and never wake up anymore.( Only putting the phone in airplane mode)

I´m with AOKP bulid 20 with rom control energy enabled, but didn´t have this issue with #13.1 build. (GPRS connection enabled when screens off, and go back to 3G when unlocks phone)

Back to 13.1.

Thanks for your work
[Samsung Galaxy Nexus] ljwnow:
And this version makes my phone hotter than before...I mean the temperature.
[Samsung Galaxy Nexus] IINexusII:
Have you tried it with power saver disabled?

Working fine here with AOKP 20. Left it overnight with 1125 1025 925 800 and 350-1200mhz and no reboots :)
[Samsung Galaxy Nexus] detritu5:
But, I don´t want to disable it, that´s the reason to back to #13.1
[Samsung Galaxy Nexus] IINexusII:
Just try it to see if it fixes the problem, so that you can let francisco and the others know lol..

Edit: enabled switching to 2G at screen off but it seems to switch alright, no problems.

What modem are you using?
[Samsung Galaxy Nexus] detritu5:
XXKK6!

To late! haha. But I confirm that this issue never happen in previous versions
[Samsung Galaxy Nexus] samizad:
Just to report that with AOKP Build 20 and #14.1 kernel, I am getting noneof the problems reported above. No data drops on screen off, no bootloop, wifi and data come back on when screen on.

I have hotplug enabled, AOKP Power Saver enabled (data and wifi off when screen off), default kernel undervolts, 700 - 1200 MGhz.

It has now stabilized at drawing 9mA (Battery Monitor Widget).
[Samsung Galaxy Nexus] HRodMusic:
happy to report that i am getting no issues, milestone 2 and 14.1
[Samsung Galaxy Nexus] trixnrice:
also had issues with signal dropping down to one bar after screen on and then 2 min later back to typical 3-4 bars in my apt. not much of an issue, but unfortunantely i just ran into boot loop with 14.1 after a random reboot.

tried flashing older versions of the kernel, but still got stuck after the bootanimation. had to nandroid back to a set up from 3 weeks ago. going back to 13.1 until things get figured out.
[Samsung Galaxy Nexus] Mrc527:
The signal lost problem still here. When i lock the screen, my phone lose the network segnal.

That's bad...:( Reverted to 13.1, now it works!
[Samsung Galaxy Nexus] kabauterman:
+1 had this problem too at first (signal lost completely and just comes back when screen on) but I flashed baseband again and not it works, I will take a look.

but anything else in this Kernel is great! best performance since I'm testing Kernels, good Idle battery usage... thanks a lot!
[Samsung Galaxy Nexus] detritu5:
So, It´s not only my problem.

Maybe there are a relationship between this #14.1 and the radio. (don´t think its a ROM problem, because I think franco test his kernel with AOKP lastest builds)

I have XXKK6.

Have you the same? I need to be sure, to report the problem to franco with the report option in his app.
[Samsung Galaxy Nexus] kabauterman:
Ok, now its back again, seems to be a Kernel bug coz I'm on AOKP too had no problem with LeanKernel and #13.1

Baseband is XXKL1
[Samsung Galaxy Nexus] inffy:
This might have something to do with you UV settings if you have setted any of those
[Samsung Galaxy Nexus] agligoros:
can i put this kernel to 4.0.2 stock rom?

or it is only for 4.0.3?

ps

supanoob:D
[Samsung Galaxy Nexus] danielvc:
Please search the thread. Answered like 1000 times.
[Samsung Galaxy Nexus] SomeGuyDude:
Welp. After I flashed, I got a random reboot, and now my phone sticks at the boot animation. Even with other kernels. I don't know WTF happened but my phone's pretty rocked now.
[Samsung Galaxy Nexus] kabauterman:
No custom UV setted up here.

Just choosed Minimum Clock 350 MHz and Max 1350 MHz

gov is still conservative
[Samsung Galaxy Nexus] lupick:
Me too using AOKP b20!

back to 13.1

L.
[Samsung Galaxy Nexus] WillyWonka23:
I am on AOKP 20 and 14.1 screwed my phone up as well. Lots of reboots and programs not working on startup. The first time I flashed it looked fine until I went to sign into my Google Voice. Immediate reboot and problems started up again.

13.1 still works beautifully though! lol
[Samsung Galaxy Nexus] Pkt_Lnt:
I had no deep sleep and some wifi issues with it on a stock rooted JWR66V 4.3 ROM.

http://xdaforums.com/showthread.php?t=1882248

I know that using a 4.2 kernel on 4.3 ROM may have issues, but I had to try. We will see if franco does a 4.3 GNex kernel for both JWR66V and JSS15J builds.

I am using the stock 4.3 kernel with Cataclysm JWR66V now.
[Samsung Galaxy Nexus] osm0sis:
No problem here on stock. Deep sleep is fantastic. 0.3%/h. :confused:

Francisco has stated he'll only be developing for JWR66V, since he has the wider user base to think about. He said Google will sync things up sooner or later.
[Samsung Galaxy Nexus] abalam:
Damn so we can not use this fantastic kernel for most custom ROMs?

Sent from my ???❎//?
[Samsung Galaxy Nexus] Pkt_Lnt:
I know, odd. Tried it a few times, flash rom, flash kernel, flash Ssu 1.51 & your fix permissions zip, restore apps only from Play Store and set them up manually. Tried flash rom, Ssu, fix permissions, then boot, reboot to bootloader and fastboot flash kernel.

Even ran it for a couple days with only four other essential apps besides GApps, still no deep sleep, so could not get through my typical 15 hour days away from charger with less than two hours screen on. BBS gave me nothing gone rogue. I have no clue, shrug, other than **** may break when you tweak it. ;)

I'll wait for a real 4.3 build.
[Samsung Galaxy Nexus] osm0sis:
Up to Francisco in the end.. Here's what we've seen him say so far, via the linked post here:

http://xdaforums.com/showpost.php?p=44075260&postcount=42799

And another tidbit of news here:

http://xdaforums.com/showpost.php?p=44054147&postcount=7619

Who knows, maybe some intrepid dev will write code to include both GPU drivers but make which it loads contingent on ROM base (ie. JWR66 or JSS15).
[Samsung Galaxy Nexus] cmstlist:
With the hybrid kernel on stock 4.3 - I am finding that wi-fi doesn't sleep when I'm out and the phone is in my pocket for extended periods. I've taken to toggling it off, which is now a bit less onerous in light of the new feature where it can use wi-fi geolocation even with wi-fi off.
[Samsung Galaxy Nexus] abalam:
Too bad! 've Always been a fan of Franco. But boype now enter into his footsteps. Kernel are supported him both versions.

Sent from my ???❎//?
[Samsung Galaxy Nexus] cmstlist:
Another issue with the hybrid kernel: I enabled the Scanning Always Available feature and disabled wifi, only to discover three hours of battery drain later that in the battery usage, it showed wifi as being ON solidly the whole time. I guess that 4.2.2 kernels don't support this feature properly?
[Samsung Galaxy Nexus] otaku91:
Thanks for all the work on this! I have happily purchased the app.

I have one question. I am running the CM10.1 nightlies. The only thing I prefer with the stock kernel is the brightness levels on automatic brightness. Is it possible to adjust the Franco Kernel to match?

Thanks in advance.
[Samsung Galaxy Nexus] osm0sis:
Makes sense. Wi-Fi works fine if you leave it at the defaults, can't guarantee anything else, especially on custom ROMs since they always had the 4.2 Wi-Fi drop bug more than stock.
[Samsung Galaxy Nexus] shreddintyres:
OFF-TOPIC

To anyone's knowledge, do we know if Franco intends to support the new 2013 Nexus 7? I'm curious as he presently supports the 2012 Nexus 7 and it doesn't make much sense to me that he would support both. This is not an ETA request, this is just a question of idle curiosity.
[Samsung Galaxy Nexus] osm0sis:
He's said only Nexus devices from now on, but at this rate I guess that could get out of hand.. Especially if the new N10 and N4 come out later this year.
[Samsung Galaxy Nexus] ChazzMatt:
JWR66V or JSS15J -- doesn't matter for GNex

You guys are talking about this issue raised over in the Nexus 4 thread, where it was stated you have to use a kernel based on whichever ROM (JWR66 or JSS15):

[INFO] Android 4.3 JSS15J vs. JWR66V, Custom Kernels and Screen/Graphic issues

http://xdaforums.com/showthread.php?t=2382880

Well, boype -- developer of Fancy Kernel -- says this is a Nexus 4 issue only and does not affect the Galaxy Nexus (a.k.a. Nexus 3). They were discussing it over in that thread:

So, whatever 4.3 kernel -- if any -- Franco releases for the Galaxy Nexus should work, no matter what 4.3 ROM we are on, IF this information is correct. THIS is why byope has kernel supporting "both versions". He's not doing anything differently. It just doesn't matter for the GNex, he says.

_________________________________________________

DIFFERENT TOPIC

What he did with the Nexus phones was support the current device wholeheartedly (Nexus 4), have sporadic updates for the previous release (Galaxy Nexus), and totally drop the ones in the past (Nexus S). When the Nexus 5 comes out, our Nexus 3 is toast. Of course, I'm moving to the Nexus 5, so I don't care. ;)

That's very reasonable to give support for a full year, until the next hardware is released and then give limited support for a 2nd year. Very generous of his time as a developer.

He may do that same blueprint for the Nexus tablets?
[Samsung Galaxy Nexus] Neejay:
Good point...I forget that the galaxy nexus is coming up on being 2 years old.
[Samsung Galaxy Nexus] stevensoaj:
Yeah, it's hard to tell when you have amazing devs developing custom ROMs/kernels for us all the time. My maguro still feels brand new. Thanks guys!
[Samsung Galaxy Nexus] shreddintyres:
I'm forgetting where i read this, but supposedly a samsung exec came out and said explicitly that the next generation N10 was going to be coming from them, it wouldnt surprise me if it dropped mid to late Q4 to early Q1. I'm patiently waiting for the refresh for the N4 will be interesting to see what goes into it since the N7 got a new underclocked s600 we can expect at bare minimum that, but i dont see google using the same SOC for the N4 which is by far the flagship of the Nexus devices (or atleast that form factor is)
[Samsung Galaxy Nexus] cmstlist:
This is the new stock Android 4.3 "Scanning Always Available" feature, not a custom ROM. When it's left on with the hybrid kernel, apparently wi-fi remains powered on even when wi-fi is disabled.

And as far as I can tell, even after disabling Scanning Always Available, wi-fi never ever sleeps. I have it set to "Never when plugged in" and if the phone sits in my pocket for an hour, it still doesn't sleep the wi-fi.

EDIT: Just to clarify, wi-fi will time out in the sense that it disconnects from my home wi-fi when the screen is off for more than X minutes; however on the Battery screen it shows that wi-fi is still powered on the whole time despite not being connected.

EDIT: Also the backup/restore no longer works in Franco updater. I tried flashing back to stock and it stayed on hybrid. Had to use fastboot. I'm going to stick with stock over the course of the weekend as I need the battery life. :)
[Samsung Galaxy Nexus] osm0sis:
f.Ku Backup and restore works fine with latest SuperSU. Scanning is off by default, and WiFi always on by default, so like I said.. works fine on defaults. ;)
[Samsung Galaxy Nexus] cmstlist:
I do have the latest SuperSU but a restore of the stock kernel failed.

Unless maybe the version of SuperSU I had at the time of the backup was not doing the trick properly.