yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] ashclepdia:
Once you've used dev-host to download, you'll remember it's always under the "long ad" and above the "square ad" halfway down page. (Picture attached for clarification ;D )
[Samsung Galaxy Nexus] supernova_00:
Thanks, finally got it after updating my Chrome Canary build.
[Samsung Galaxy Nexus] Soy_Filipo:
So can anyone tell me please if this kernel is working with the latest cyannogen mod snapshot?
[Samsung Galaxy Nexus] daniil1410:
You must install @osm0sis ' fixed version, otherwise the phone app will force close. The flashable works with TWRP too, I don't know why did he put CWM in the name.
[Samsung Galaxy Nexus] Soy_Filipo:
Thanks mate!
[Samsung Galaxy Nexus] osm0sis:
Because it's a simple nomenclature a lot of people use to denote "flashable zip."

Almost any zip that works in CWM works in TWRP, they both use EDIFY scripting language. Occasionally there's something shell command-wise or feature-wise that TWRP doesn't support, but otherwise, a flashable zip is a flashable zip. :)
[Samsung Galaxy Nexus] Vekhez:
Hey osm0sis, have you ever though about making your own kernel? I mean you modify FK's (and AK's once!) and they always turn out nice, I mean, if you ever do, I would love to test it out!

Cheers!

-Vekhez
[Samsung Galaxy Nexus] nec_d:
i'm trying to overclock my gnex, running franco r392 and the updater app, but the overclocking is lost after a lock/unlock :confused: any ideas?

running 4.3 / JWR66Y stock...
[Samsung Galaxy Nexus] Edward Stanbury:
Got busybox installed correctly ? I had the same problem
[Samsung Galaxy Nexus] nec_d:
and how did you solve this?

i've busybox installed in /system/xbin and it seems to be OK (installed with stericson busybox installer.

* daemon not running. starting it now on port 5037 *
* daemon started successfully *
shell@maguro:/ $ busybox
busybox
BusyBox v1.21.1-Stericson (2013-09-26 14:33:26 BST) multi-call binary.
BusyBox is copyrighted by many authors between 1998-2012.
Licensed under GPLv2. See source distribution for detailed
copyright notices.

Usage: busybox [function [arguments]...]
or: busybox --list[-full]
or: busybox --install [-s] [DIR]
or: function [arguments]...

BusyBox is a multi-call binary that combines many common Unix
utilities into a single executable. Most people will create a
link to busybox for each function they wish to use and BusyBox
will act like whatever it was invoked as.
[Samsung Galaxy Nexus] osm0sis:
Ramdisks, scripts and tinkering with commits I can do but the real coding work Fransisco and the other brilliant kernel devs do is way out of my league unfortunately. Maybe some day..

Francisco's been doing this since he was like 15 though, so I'd have a lot of catching up to do. ;)
[Samsung Galaxy Nexus] bat0nas:
Post deleted.

Problem solved.
[Samsung Galaxy Nexus] metalspring:
You could give it a try just for fun. Just start off with Franco's source as a base and play around with different settings, trying to merge source from other kernels, etc

I've never tried building just a kernel but I have compiled a few roms trying to see what I can change and add in and it's definitely a good learning experience

Also it helps a lot looking through gihub and gerrit at recent changes and commits to see how the different code works and what it controls

(Btw, on a decent PC kernels should only take 30 minutes or so to build if not less)
[Samsung Galaxy Nexus] osm0sis:
I've got his source cloned and I've been learning about git and everything lately so I can help out directly with minor changes Francisco's given me permissions to push to his repos, and definitely a good learning experience so far. :)
[Samsung Galaxy Nexus] RW-1:
Wow, deleted right as I was posting, did you go grab 1.65 ?

---------- Post added at 01:40 PM ---------- Previous post was at 01:39 PM ----------

What you have learned has certainly been of benefit, running your kernel on shiny Kit Kat! Thank you.
[Samsung Galaxy Nexus] metalspring:
Nice, I was just wondering if it worked on shiny 4.4 since it used slims ramdisk rather than shinys
[Samsung Galaxy Nexus] osm0sis:
Should be pretty generic for KK, only non-stock differences were in init.slim.rc which was basically init.cm.rc renamed.
[Samsung Galaxy Nexus] osm0sis:
For those sticking with 4.3.x for now, you can sideload your way into a pretty decent KitKat-like experience, totally stable:

http://d-h.st/users/osm0sis/krt26m-kk4_4-apk/

I've uploaded the ones that aren't already out on the Play Store (e.g. TTS and Keyboard are out). Read the descriptions and look in the system-lib folder for dependencies.

Works like a dream on stock! :D

I also switched back to stock yakju and started stripping system apps I didn't want out of it, since takju disables certain apps by region and I know there won't be any more OTAs. ;)

Clearly disabling alone didn't quite do the job before, since now my idle drain is at an all-time low. :good:
[Samsung Galaxy Nexus] pkgnex:
Thanks for putting all this in one place, Os!

I had gone this route prior to flashing Shiny 4.4, and it was OK... had a few weird launcher lags / hiccups and inconsistent Google Now performance but it wasn't too bad. Flashing the full 4.4 ROM solved all that and made everything unbelievably smooth... except for the dreaded graphics glitches and occasional random reboots. I was actually OK dealing with the 4.4 issues until on one reboot I couldn't get past the boot animation no matter what I did. Ended up reverting to my 4.3.1 nandroid, and I'm still there for now. I REALLY hope some combination of luck and genius in the dev community can figure out how to get the graphics stuff straightened out on G-Nex... it showed so much promise! The GEL runs much better in the full 4.4 framework than it does side-loaded into a 4.3 ROM.
[Samsung Galaxy Nexus] osm0sis:
I was actually reading up on the Shiny forum the other day, and apparently it's just a waiting game for Google Glass to get KitKat at this point, then we should be good to go and devs can run with it: :D

http://rootzwiki.com/topic/36706-ro...ke-stock-android-44-krt16m-no-bugs/?p=1520914
[Samsung Galaxy Nexus] pkgnex:
I really hope something like that pans out!
[Samsung Galaxy Nexus] RW-1:
Let's keep our fingers crossed...

Metalspring, yes, Os's kernel has been running great on Shiny 4.4 (11/10 build), far better than I have had prior so far. Others are running the included kernel, Tiny 5.3.1 and (I was running) golden as well.
[Samsung Galaxy Nexus] shawnaye:
I would like to thank all the guys that made franco kernel on the Galaxy Nexus so amazing especially the franco dev team, but not forgetting those silent helpers =)

I've been using this device for 1.5 years and i finally made the move to the Nexus 5.

I wish everyone the best and hope to see you guys soon!

Really thank all of you for making this kernel so great.
[Samsung Galaxy Nexus] sd3993:
Could you give us a list of apps you stripped? I have my exams coming up in a week and i prefer not to experiment too much right now :P

---------- Post added 13th November 2013 at 12:10 AM ---------- Previous post was 12th November 2013 at 11:56 PM ----------

[MENTION=4544860]osm0sis[/MENTION] i've set hispeed_freq at 729 and input_boost_freq at 537.

Could you please explain to me what bootpulse_duration does? And which would save more battery 250000 or 500000? I've got it at 250000 currently and have no lags.

Thank You! :)
[Samsung Galaxy Nexus] osm0sis:
It's the amount of time it stays at input boost freq before considering moving again.

I just removed the usual gapps I don't use, like G+, Gmail, Earth, Talkback, Play Magazines + Videos, Video Editor, News & Weather, then just some minor system stuff like any keyboards that aren't in my language and live wallpapers I don't care about.
[Samsung Galaxy Nexus] ChazzMatt:
One commentator thinks Google will just replace older Google Glass with newer versions that have different chipsets.

http://www.phonearena.com/news/Google-executive-discusses-wider-rollout-of-Google-Glass_id49217

Can't find the specific article right now, but this is what he was referring to below. Google is allowing owners to swap for hardware upgraded versions -- and that might include chipsets for 4.4 updates?
[Samsung Galaxy Nexus] osm0sis:
Sh*t, that would be bad news.
[Samsung Galaxy Nexus] ChazzMatt:
Hope I'm wrong. In fact, I may be. Look at this... Does this mean the upgraded hardware is still running the same TI chips? :confused:

http://www.geek.com/android/google-glass-2-offers-minor-but-important-hardware-updates-1576039/
[Samsung Galaxy Nexus] osm0sis:
Funny they would mention the board but not the graphics chip. Anyway, still seems hopeful!
[Samsung Galaxy Nexus] mangusZen:
Im not into it very much but how can possibly google release new glasses based on a unsupported board? Is it a nonsense? Quite weird to me...
[Samsung Galaxy Nexus] osm0sis:
Anyone using the Kit Kat APKs I uploaded, here's a nice trick to fixing the icon size slightly and keeping the launcher from restarting when you swipe Google Search away from Recents using the App Settings module for Xposed:
[Samsung Galaxy Nexus] supernova_00:
Osmosis, thanks for getting the kernel to run on kit kat! My only request is could you please look into figuring out what causes the lock-up that requires a battery pull? The other kernels that "work" with kit kat reboot instead of locking up completely.
[Samsung Galaxy Nexus] osm0sis:
I think I've only seen you report this issue here and in the SlimKat thread, so I have a feeling it's not that widespread and may be particular to something in your setup.

As for looking into it, no, all I can do is fix the ramdisk. Those kinds of issues unfortunately will need to be fixed in the source. Anyway, we are still all shoehorning 4.3 kernels onto 4.4, so I wouldn't expect too much movement until some kind of 4.4 kernel sources drop for OMAP4; perhaps the Google Glass ones will be of use, for example.
[Samsung Galaxy Nexus] supernova_00:
I've seen it mentioned a few times, I think once in this thread and a couple in the shiny rom thread on rootzwiki. But anyways, ok it was worth a try to ask. thank you!
[Samsung Galaxy Nexus] RW-1:
Hi Osmosis,

I respectfully disagree, only in part that that is not more widespread.

I can attest from the Shiny KitKat thread at RW, plus using it myself with no mods (I only manually replaced my softkeys within /system/priv-app/systemUI) that when the phone freezes, that I require a battery pull, whereas before on golden (for example) it would reboot, or freeze and if left alone for a minute or so it would reboot on it's own.

Although I have to batt pull, the number of times I have the issue (one or two times within a 48 hour period depending on what I'm doing with it) is WAY far less on your experimental kernel than any other I have used with shiny so far.

I myself don't expect you to fix it for reasons above that you mentioned, though if you could look at anything on it that could be a slight improvement, I'd be a happy camper.

So far reports of the new hardware for Glass still show an OMAP with a version 4 vice 3, but didn't list the GPU in those reports, so there's still hope I suppose.

You still have my utmost thanks for what you have accomplished thus far, on 4.3 and 4.4.
[Samsung Galaxy Nexus] dracon6ai:
Add me to the battery pull list. On Franco it'll freeze and stay there till you pull the battery. MpoKang and TinyKernel it'll freeze and reboot itself after 5sec or so. Running Shiny 4.4 11/10 build.

***Laziness is nothing more than the habit of resting before one gets tired.***
[Samsung Galaxy Nexus] osm0sis:
If there was some way to get a kmsg, that could help, but battery pulls make sure there is none. :confused:
[Samsung Galaxy Nexus] RW-1:
Totally with you there, but like I said, I enjoy yours more in the overall picture ... :good:

I guess that now we'll be guestimating when GG may get KK ? It's tough when you have to wait ...

Oh yes, one other thought, has anyone pulled apart the N5 GE Launcher for the differences between it and the AOSP Stock Launcher?

The reason I ask is because since google isn't "giving" it out to anything besides the N5 yet, I wonder if that may or may not have related issues contributing to the reboots/graphics/OS/Kernel.

I don't think anyone right now is doing a KK ROM without it ...
[Samsung Galaxy Nexus] osm0sis:
It's a whole different animal from the old/AOSP launcher. The new Google Home launcher apk is really just a frontend for Google Search/Now. Shouldn't really make any stability difference though. A launcher is still a launcher.
[Samsung Galaxy Nexus] sd3993:
[MENTION=4544860]osm0sis[/MENTION] okay i changed above_hispeed-delay to 50000(from default 15000) and min_sample_time to 50000. It made my battery a little worse. Aren't they supposed to increase battery life?

Could you please post a screenshot of your Governor settings screen please? Thank You! :)
[Samsung Galaxy Nexus] osm0sis:
Don't touch those. They're perfect. :p

And no, no screenshots, the winning tunables have been posted so many times in this thread you could throw a stone at the search bar and find them.

They're also in my GN settings post, linked in my sig. ;)
[Samsung Galaxy Nexus] sd3993:
Oh sorry. Overlooked those in your settings page. Back to stock values! :)
[Samsung Galaxy Nexus] osm0sis:
Hehe no worries. Default settings in r392 have hispeed_freq at 1228 where the proper winners have it at 729, so that's the only thing you might want to change.

We could also use a few more opinions in our hispeed/inputboost/boostduration testing if you feel like tinkering. :D
[Samsung Galaxy Nexus] Godra:
Are those settings fixed in your osmod? Im on latest r392 and I know I can change it easily with Trickster for example but Im trying to get most of my battery so I have almost no apps installed but few that I use most ( and they are greenified ) :p :good:
[Samsung Galaxy Nexus] osm0sis:
Not fixed on my -fixed version, no, since it's a kernel-side change. Francisco has fixed it in the source for the next build though.

https://github.com/franciscofranco/Tuna_JB_pre1/commits/nightlies-4.3
[Samsung Galaxy Nexus] Godra:
So this kernel is still being updated?
[Samsung Galaxy Nexus] RW-1:
But of course ...
[Samsung Galaxy Nexus] pkgnex:
First... listen to Os and set them to the winning tunables for the best battery/performance balance.:D

That said, if you really need to tinker, I think increasing above_hispeed_delay should theoretically increase battery life a little (neglecting and possible race-to-idle trade-off), while increasing min_sample_time should worsen battery life (with the same caveat).

My understanding is that:

Increasing above_hispeed_delay should keep the frequency lower longer under high-load conditions before the cpu ramps up beyond hispeed_freq.

Increasing min_sample_time should keep the frequency at higher levels longer before a load reduction will allow the cpu to ramp down.

Also, if you happen to have hispeed_freq equal to your max_frequency setting (as I know a few people do), above_hispeed_delay does not come into play. However, in this case, it is almost as if you are using OnDemand.
[Samsung Galaxy Nexus] daniil1410:
Thanks. i really needed this fix for FC.

PS. I don't want to start a new thread, but do you guys know a way to use the new immersion mode in 4.3. And I'm talking about the hiding nav bar.
[Samsung Galaxy Nexus] Mevordel:
adb shell cat /proc/kmsg

will update in realtime as long as you leave it plugged in.
[Samsung Galaxy Nexus] osm0sis:
Yep, you're right. If someone can do that until it freezes.. ;):good:
[Samsung Galaxy Nexus] RW-1:
He's asked us on the RW thread to do that, however my question is, you cant plug in and run it after it has frozen, right?

I take it as you would have to run this whilst connected to the computer and run your phone until it froze requiring the batt pull ...

Let me know and I'll append at RW ...
[Samsung Galaxy Nexus] osm0sis:
Yes that's exactly it, and you can put > log.txt on the end of the command to make sure you have it saved for later.
[Samsung Galaxy Nexus] RW-1:
Gotcha. :good:
[Samsung Galaxy Nexus] sd3993:
I don't know if any else noticed this but when the phone freezes(4.4 kitkat with franco kernel obviously), it doesn't COMPLETELY freeze. The phone still vibrates if i receive a notification and i tried calling my phone from another one and it vibrated like it does when i get a call. So basically the phone keeps function properly in the background. It's just that the screen doesn't update/change for some reason and also doesn't recognize touches! Hope it helps. :)
[Samsung Galaxy Nexus] daniil1410:
I have a problem. Today while watching videos in YouTube through the android app, the screen turned off like the old tvs, I heard a atrange pop and the phone rebooted and was stuck on Google logo. The only way to fix this was to wipe dalvik cache and cache. This happened yesterday and a couple os times last week. Yesterday the cache wipe didn't work, so I needed to wipe /system(without /data) and it worked again. I can't provide logacats, because this behavior is very unpredictible. I'm using CM 10.2 snapshot and osmosis's franco kernel fix. No crazy undervolting and overclocking.

I will now reflash to PAC and see if there are problems there as well.

And about that [MENTION=4544860]osm0sis[/MENTION] , can you make a version for pac: http://xdaforums.com/showpost.php?p=44702327&postcount=2 .
[Samsung Galaxy Nexus] AutomaticFailure27:
[MENTION=4544860]osm0sis[/MENTION] Thank you for your UV settings. I imputted them just for shizz and giggles but, to my surprise, they have been running flawlessly on my device.
[Samsung Galaxy Nexus] osm0sis:
Already done.
[Samsung Galaxy Nexus] ad astra:
enable fsync. it may make your phone a tad less responsive or snappy (i don't even notice) but data doesn't get corrupted or lost when a crash occurs while an app or the system is writing to any of your drive partitions. at least that's what i've traced down the problem. it happened to me on a battery pull.

all this is assuming that FK has fsync disabled by default, which i think is true.

my 2c.
[Samsung Galaxy Nexus] daniil1410:
Yeah, I thought so too. But it didn't work.
[Samsung Galaxy Nexus] osm0sis:
Nope fsync is enabled by default, but sometimes I get the feeling something goes wrong and resident data gets lost.
[Samsung Galaxy Nexus] SuperSalvo:
[MENTION=876324]osim[/MENTION]0sis: Have managed to get your kernel booting on CM11? I'm stuck on bootlogo :crying:
[Samsung Galaxy Nexus] osm0sis:
The KK hybrid ramdisk isn't working? I'll take a look.
[Samsung Galaxy Nexus] bigknowz:
Nexus 5 Payment

Heads up to anyone holding off on buying their N5 from the Play Store. If you buy and have to wait for shipment, you won't be charged immediately. Looks like they might be waiting for ship date to charge. I think that's pretty cool.
[Samsung Galaxy Nexus] RW-1:
Osmosis, someone posted this yesterday on our RW Shiny KK thread, just been busy but wanted to copy it here for you guys"

"This is from a last_kmsg that someone sent me. [ 3497.677307] PVR_K:(Fatal): Debug assertion failed! [694, drivers/gpu/pvr/sgx/sgxutils.c] [ 3497.677368] kernel BUG at drivers/gpu/pvr/pvr_debug.c:206! [ 3497.677490] Unable to handle kernel NULL pointer dereference at virtual address 00000000 "

I hope it helps in some small way. The poster didn't say what kernel he was running however, but I thought it might give you guys insight to the issues.
[Samsung Galaxy Nexus] osm0sis:
SGX video drivers, so no surprise there, unfortunately.

Also that virtual address is basically blank. Too bad, might've pointed to where the problem was.
[Samsung Galaxy Nexus] ChazzMatt:
But they will put a hold on your credit card for the amount.

Also, their ship dates are faster than the website says. I just ordered a 2nd 32GB Nexus 5, this time in white for my wife for Christmas. Ordered it Tuesday November 12. Said it would ship by November 26. OK.

BOOM. Shipped 10 hours later, got tracking number, arrived early Thursday afternoon. :eek: What happened to Nov 26? Now I have to hide it from her for 6 weeks...
[Samsung Galaxy Nexus] vlasis_myr:
Had the same with fancy r44 pre 3 with fsync enabled...

Στάλθηκε από το Galaxy Nexus μου χρησιμοποιώντας Tapatalk 2
[Samsung Galaxy Nexus] g@u55:
Hi osm0sis thanks for the changes that you have done, I read also your tutorial to apply the changes on the boot.img using unpackimg and it works. Is there a way to apply the change in the franco.Kernel sources before compile it.

I'm building CyanogenMod from sources and I want to replace the standard kernel with franco.Kernel, so I need to modify the sources.

Thanks for your work,

Alberto
[Samsung Galaxy Nexus] osm0sis:
That's all ramdisk stuff, so there is no source for it really.. Some people do have githubs for ramdisk changes, not sure if CM does.

Also some things cannot be done in the source, since they act recursively on sysfs files.
[Samsung Galaxy Nexus] g@u55:
Thanks for the answer. I'll write a script to make the change after the built process... because i'm lazy ;)

Alberto
[Samsung Galaxy Nexus] metalspring:
There are some options in source when building a rom for ramdisk

You probably have to edit the def_config that the rom points to for the kernel configuration

(ungziping coping/pasting and renaming the config.gz in found in /proc after flashing the kernel and renaming it to overwrite the default def_config the rom uses to build the kernel inline would be the easiest way)

btw osmosis, do you know if all the issues are fixed in francos source now, like what you added to your fixed versions?

I was planning on trying to add franco kernel to build inline with pac rom
[Samsung Galaxy Nexus] osm0sis:
With my ramdisk and the commits in there it should have everything we were missing and be potential milestone! :)

There are also a couple extra things I wanted that I threw in, like exporting the IVA frequency to userspace. And Francisco said he'll put us up to 3.0.101 when he gets around to release. He just got his N5 in the mail and has been busy trying to get them up to feature parity, and he's also got a lot of stuff exciting stuff going on in real life right now, but I'll leave those potential announcements to him. ;)

Only other things that could go in would be direct register in-call + loud speaker volume boosts, Francisco's auto-tune interactive developed on mako and also in use on grouper + flo, and probably hammerhead by now. high performance sound Francisco said was a no-go since it was kind of an ugly hack and caused a lot of problems in other places. I'd be curious to see if we could get smartreflex behaving too, but I'm not really sure it's worth the effort.
[Samsung Galaxy Nexus] metalspring:
hmm, i'm trying the kernel build separately right now to see what changes apply when built directly with the franco_defconfig

if it builds and works properly with all the needed fixes I may ask franco if I could post it as a pre-milestone release test or something like that

(good thing i tried the kernel by itself first, i forgot i needed to edit a few files when using the linaro toolchains lol)

Edit: Well got it built and flashed it and all seems good except cfq i/o scheduler read ahead buffer size was at 256 instead of the 512 I think you figured out it should be. However that might just be from the rom I'm on, everything else seems fine though

If you want to just give it test osm0sis, just let me know and i'll get you the zip
[Samsung Galaxy Nexus] metalspring:
Also, just noticed something but correct me if im wrong... couldnt you edit the source used to make the ramdisk in /device/samsung/tuna /toro /toroplus /maguro ?

I havent taken apart too many ramdisks before and looked around but some of these files seem to be the same as the ramdisk

(just look at the githubs to see, tuna has the most files since its common to all variants)

https://github.com/CyanogenMod/android_device_samsung_tuna

https://github.com/CyanogenMod/android_device_samsung_maguro

https://github.com/CyanogenMod/android_device_samsung_toro

https://github.com/CyanogenMod/android_device_samsung_toroplus