yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] netreign:
where can i download last smittyL kernel
[Samsung Galaxy Nexus] Noeljunior:
Is the beta3 compatible with CM-12.0 by [MENTION=2633638]Ziyan[/MENTION]?
[Samsung Galaxy Nexus] rajputrajat:
No, it's not...

There is another compatible kernel build a few pages back..
[Samsung Galaxy Nexus] osm0sis:
[MENTION=2853378]Nephilim[/MENTION] since SmittyL/Full_Auto has init.d support on FML you should post your updated settings as a script file. :)
[Samsung Galaxy Nexus] dbt816:
Oh yeah.... 21,268 benchmark with Beta 3, latest FML and [MENTION=300441]nephlim[/MENTION]'s udated settings :D
[Samsung Galaxy Nexus] Nephilim:
So what're you thinking of the minfrees? Have you tried them?
[Samsung Galaxy Nexus] osm0sis:
Currently I don't have a tweaking app installed since there's no Synapse support yet, which is why I was hoping you could maintain an init.d script for everyone to make it easier. ;)
[Samsung Galaxy Nexus] applerulez1:
It will be worth your time to try just this once. I promise you won't regret his settings. Also I shot you a pm. Please reply.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Yeah, you're right, I never try anything. :rolleyes::p

Sorry, I don't respond to technical question PMs. :good:
[Samsung Galaxy Nexus] applerulez1:
I'm not sure if that is sarcasm or you being genuinely open to trying it xD Just reply dude it would mean a lot.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] tiagofernandex:
Noob question, i have cm12 and just downloaded the test2 for non fml roms.

I have to do a clean install or just get to recovery and flash the test2 kernel?
[Samsung Galaxy Nexus] applerulez1:
No need for a clean install, just make sure to follow all of the directions.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] tiagofernandex:
What directions..?
[Samsung Galaxy Nexus] applerulez1:
The directions in the post for the lollipop compatible kernel. It was a few pages back. Neph posted it.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] pkgnex:
1520 Issues

[MENTION=4608636]bsmitty83[/MENTION],

Even after clean flashing the new 1/4/2015 FML (wiping cache, dalvik, system, and data) and the beta-3 kernel, I still can't get the 1520 slot to be usable. I tried different batteries and voltage levels above and below stock, but it always freezes really bad when I set the max frequency to the 1520 slot. Incidentally, setting the max to 1500 on the FML stock kernel did not cause me any issues.

When I take a dmesg immediately after trying to set the max to 1520, I see this over and over (there are more instances the longer I leave it hung up in the 1520 slot):

<3> [xxxx.xxxxxx] clock: dpll_mpu_ck failed transitioned to 'locked'

Note that using stock or Neph's setting doesn't matter, and per your advice, I continue to leave the frequency lock in Trickster "off".

This is really frustrating, because I've never had this problem with any over-clocking before - on your kernel or any other.

That said, leaving it maxed at 1350 is actually fine for me... and the kernel works really well at this level. I just hope this might help you correct a bug or something.

Thanks, as always, for all your hard work!
[Samsung Galaxy Nexus] bsmitty83:
I opened a new thread for the lollipop kernel , head over there

http://xdaforums.com/showthread.php?p=57974343
[Samsung Galaxy Nexus] cartman333:
Exactly the same thing happens with me every time, when i try to go above 1350mhz. But im fine with that too, u guys made amazing work, my phone is has never been so fast!
[Samsung Galaxy Nexus] applerulez1:
Well my battery made it through its first whole day on lollipop, I have mad respect towards everyone who made this beast possible. Thanks c:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] sodas43:
help !!

Hi, After installing FMLv3(clean flash: wipe /data, /cache, /dalvik-cache and /system) and pa nano gapps on my maguro, everything is working fine but I lost my root permission !! Now I am unable to reboot into recovery to flash the full auto kernel !! :crying:

Please help !! Thanks in advance !!
[Samsung Galaxy Nexus] Rushead:
Impossible. Power off. Hold both volume buttons and power button. Select recovery. Bam.

Flash supersu in recovery. Boom.
[Samsung Galaxy Nexus] sodas43:
yuuuuhhuuuuuu !!!! Thanks a ton !!! You made my day !!!! Actually I thought if superuser is built-in why do I need SuperSU? :confused: Thanx again !! :D
[Samsung Galaxy Nexus] sodas43:
backup a/c

[MENTION=4648519]Rushead[/MENTION]

I am also unable to set backup a/c. :( I found that [MENTION=4825779]Schneewitzchen[/MENTION] also faced similar problem. [ http://xdaforums.com/showpost.php?p=57969565&postcount=2469 ]. Is there any solution for it ??? I used pa nano gapps from this link http://xdaforums.com/paranoid-android/general/gapps-official-to-date-pa-google-apps-t2943900

. Thanx again for your reply !! :o :)
[Samsung Galaxy Nexus] Rushead:
Give it time. [MENTION=3390093]MWisBest[/MENTION] will have everything working at some point (being the boy genius he is), but he's probably focusing on more dire issues.
[Samsung Galaxy Nexus] applerulez1:
Yeah I agree, plus he's been really busy lately. This is important to him but he has a life. :p

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Nephilim:
Moved to new thread..
[Samsung Galaxy Nexus] xaifer:
F2FS compatibility

Is DirtyV-SR-Ak2-Final-11.9 compatible with F2FS? I don't find Unified or Ramdisk final version :(
[Samsung Galaxy Nexus] varadparulekarofficial:
This question may sound outdated but any help will be really appreciated..

I want to flash Dirty V kernel on CM11 4.4.4 maguro ..

Which one should I choose??
[Samsung Galaxy Nexus] bsmitty83:
Yes , its compatible with both , flash away
[Samsung Galaxy Nexus] bsmitty83:
Not that outdated [emoji3] . to answer your question , its up to you but the final version should be sound . also the op has links to all the old versions zipped up in one archive . so mess around .
[Samsung Galaxy Nexus] varadparulekarofficial:
I flashed the DirtyV kernel.. Successfully booted..

I saw the highest maximum freq. set to 1.8GHz and couldn't resist myself..

Switched the maximum to 1.8GHz using trickster..

Suddenly phone started making continuous loud noises and unusual vibrations and became too hot to handle..

I did a battery pull and reflashed M12 snapshot to restore stock kernel..

Is that 1.8GHz really safe???
[Samsung Galaxy Nexus] bsmitty83:
Probably not , some hardware can handle it , but really its not that effective anyways , 1.5ghz or 1.6ghz is usually high enough
[Samsung Galaxy Nexus] sodas43:
I don't think so. It's there in the settings but 1.8GHz will drain your battery very quick. and also some users say 1.8 Ghz has no problem with their ph and others faced problem like you(me also :p) so i think it varies from ph to ph. Better to down it to 1.5 GHz. Also use [MENTION=2853378]Nephilim[/MENTION]'s setting for maximum smoothness/performance and battery life . Hope this helps !! :D
[Samsung Galaxy Nexus] osm0sis:
Moving over to the Full Auto thread myself. :good:
[Samsung Galaxy Nexus] SirOch:
Hi,

With dirtyV final and the last carbonrom, sometimes when I reboot my phone, it stays in google logo loop.

Anybody has this issue ?

Cheers

Envoyé de mon Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
It was the one bug I couldn't squash ........

If it happens , hold all three buttons down on the google logo loop and it will kick you to the bootloader , from there power off your phone and power back on and the loop will be gone
[Samsung Galaxy Nexus] bsmitty83:
I haven't yet but will eventually .
[Samsung Galaxy Nexus] cujo6801:
Have you tried the bionic revert zip

Mine was getting crazy hot before I flashed it..

sent from the DOG pound
[Samsung Galaxy Nexus] KJW979:
Not sure if ROM, kernel, or phone issue so posting here because last change made was DL and install of v3sr kernel. But sometimes not every time when wake phone up all my apps on home screen and in drawer are completely gone, all I can see is my wallpaper. I can access navigation bar, status bar, which include recent apps opened, which do open when pressed. Only way to see apps again is by reboot. Currently on liquid 1/25 build with v3sr kernel using neph settings except changed interactive to hype. Anyone else have this happen?
[Samsung Galaxy Nexus] bluerez79:
I have. My icons disappear for 5-10 second and then re appear. I haven't had to reboot. Using nova launcher. Also on liquid 1.25
[Samsung Galaxy Nexus] KJW979:
Mine disappear until I reboot. Using Google launcher, can't swipe Google now over either but halo works, weird not sure of cause. Hopefully screen isn't starting to go bad but since wallpaper there and other things work don't think so. Start by resting kernel settings to stock and work my way up.
[Samsung Galaxy Nexus] @jmorosky:
Just flashed the latest AOKP 012514 and it won't let me flash a kernel over it using CWM. Any ideas?

Edit* It let me flash DirtyV V2 Linaro. Going to try SmittyV3 again.

Sent from my AOKP 20140120 SmittyV3
[Samsung Galaxy Nexus] Nephilim:
Sounds like a systemUI force close. It plagues alot of 4.4 roms but its become very rare lately so you dont see it often. I get them too sometimes. Quite annoying.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] KJW979:
But don't get any pop up indicating a force close, there just gone. First time came across this on any ROM/kernel. Yea definitely annoying.
[Samsung Galaxy Nexus] bsmitty83:
Just updated the Op , all three kernels .

I think I finally got fixed the dsscomp error , interactive seems better , giving proper dmsg again .

Also been working on hotplug , haven't tested yet . I threw in some more commits from AK and mpokang , if you wanna know what, my github is current :thumbup:

IMHO this is my best build so far for me . hope you guys have the same luck .

I only tested SmittyV , so let me know if something isn't right .
[Samsung Galaxy Nexus] lazydognet:
Thanks..... Will test now.

LDN
[Samsung Galaxy Nexus] KJW979:
Can't seem to DL latest from your drive.
[Samsung Galaxy Nexus] Blackcrx:
If you're trying to download it from your phone make sure your browser is "requesting desktop version"
[Samsung Galaxy Nexus] fracama87:
Well but at 1,6ghz you can't compare with a test with cpu speed at 1,2 o 1,4ghz... ;)

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] metalspring:
Btw, what is that Joe's rcu or whatever you use on your smittyv version? Like what does it do exactly?
[Samsung Galaxy Nexus] Nephilim:
Smitty, I suggest you make a main DirtyV folder in your drive and then subfolders in that for each version then link the DirtyV drive folder. For some reason it doesn't let you properly download the kernel with the correct name when you link the zips directly.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] cujo6801:
I ****ing hate Google drive

sent from the DOG pound
[Samsung Galaxy Nexus] KJW979:
V4SR using interactive screen opening immediately, lag seems to be gone.
[Samsung Galaxy Nexus] bsmitty83:
Dropbox it is ......lol

sorry bout that :good:
[Samsung Galaxy Nexus] Nephilim:
Drive is epic but for some reason XDA directly opens it in the browser rather than giving you the option to open it in your own drive app like on G+ which is lame.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] hepi_hape:
I didnt se link update ??

Opend spoiler link just show older version uploaded 25 jan... Not 30 jan update
[Samsung Galaxy Nexus] SirOch:
Ok thank you.

Now instead of doing a reboot I did a power off/on [emoji12]

Envoyé de mon Galaxy Nexus
[Samsung Galaxy Nexus] ptmax13:
Incoming newbe question...

You guys, is the latest version compatible with the latest stock 4.3?

I tried to flash but I got stuck during boot. I mean before the boot animation.

I was on latest Franco. I had to flash the stock kernel to boot again in android.

What should I do to flash that badass SR version?
[Samsung Galaxy Nexus] bsmitty83:
did you dirty flash your rom or flash a stock boot.img first ? if you tried installing on top of Franco's thats probably why it bootlooped

let me know if you still have a problem installing even after doing one of the two options above

:cowboy:
[Samsung Galaxy Nexus] ptmax13:
Oops.... Yeah, I flashed dirtyV over Franco. I didn't know.

I flashed it again over the stock kernel and everything worked out fine.

Thanks for taking the time to reply to my silly problem...
[Samsung Galaxy Nexus] bsmitty83:
It would only be a silly problem if you asked a million times before .

That is what XDA is for , asking questions and getting help . now its become a social hierarchy site where all that matter to people are titles and thank counts (smh for those who have a "if I help hit the thx button " in their signature) . or its about telling someone their a noob , to google it .

I got zero problems helping anyone out on here . if I don't respond to a pm or post in one of my threads , its for a possible many different reasons , but never because I just don't want to answer .

Feel free to ask questions (ANYBODY) , most of the people here in my thread feel the same as I do .
[Samsung Galaxy Nexus] ptmax13:
Amen to that man...

I'm constantly afraid to ask noob questions, especially in threads like this, with so many people following.

I'm happy to find people willing to help a beginner, especially when they are the kernel creator.

My sincere thanks sir.

I'm off to play with Nephilim's settings...
[Samsung Galaxy Nexus] cujo6801:
Sent from the "DOG" pound

Can I get some helps with her?
[Samsung Galaxy Nexus] jnever1:
Recovery Problems

Hello,

I have a toroplus that was running liquidsmooth 3.2 on a full f2fs conversion. (That I was able to pull this conversion off should be testament to my meager, yet capable skript-kiddie qualifications.) Well, it recently took a poo on me. Not a big deal - normally - but this time it took out my data/media partition.

I'm trying to recover and am having a TERRIBLE time getting ADB to play nice with the 2.8.0.0 custom TWRP recovery. I cannot push files and I cannot sideload. ADB simply refuses to recognize that my device is connected.

CWM recovery, phillzTouch., twrp 2.7.0.1? All fine.

TWRP 2.8.0.0, 2.8.3.0, 2.8.4.0? No dice.

I'm also having SleepOfDeath problems with it... Blows my mind to have SOD probs @ recovery level! lol

Is there a particular version of the f2fs enabled recovery, or perhaps a custom driver that I need to be using?

I inquire of drivers because I noticed that windows 7 device manager shows "AOSP on toroplus" instead of "Galaxy Nexus". ADB works when it identifies as Galaxy Nexus (such as on TWRP 2.7.0.1).

I have a work-around procedure, but it requires multiple flashings, multiple files system formattings, and is generally a long, drawn out, excruciatingly destructive PITA.

ANY help, even a pointer to a more appropriate forum, is appreciated. :)
[Samsung Galaxy Nexus] EAK128:
Sounds like you need to turn off the screen time out/off feature for TWRP in settings. Sorry don't remember where exactly, but it's easy to find.
[Samsung Galaxy Nexus] jnever1:
For me, disabling screen off (Home -> Settings -> Screen | Enable Screen Timeout ON/

OFF

, Screen Timeout in seconds:

300

, Brightness:

50%

) only serves to reduce the frequency of occurrence. I can usually accomplish my goals within 5 mins anyway. T/O during backups can be a problem though.

Thanks!
[Samsung Galaxy Nexus] christianpeso:
When I had this issue, I completely erased ALL Samsung related drivers from my PC. Under Device Manager in Windows. Once opened I would open the "View" tab and check the "show hidden devices" option. I would then proceed to completely delete all Samsung related drivers and Android related drivers such as anything labeled "ADB", "Galaxy Nexus" or "Android". Open all tree lists and look at them, especially under "Universal Serial Bus Controllers".

I would then download Koushs "Univeral ADB Driver": http://www.koushikdutta.com/post/universal-adb-driver

I was running Windows 8 at the time so I ended up restarting my PC in "Driver signature check" disabled mode. I then installed the Koush ADB driver that I downloaded and then "ADB Sideload" would work fine.
[Samsung Galaxy Nexus] Dirty_Jerz:
Here's my suggestion. The newest version of twrp has much better mtp support. Grab that on your PC and fastboot flashh recovery. Then move the files you need to the root......wait, you wont be able to mount it. Hmmmm....let me think about this for a second.
[Samsung Galaxy Nexus] jnever1:
Sound advice. I did a primary strip and 'stall, not a true purge. I'll try again tomorrow. I'm up and running again as of 30 minutes ago. The point now is to identify the path of least resistance. Thanks!
[Samsung Galaxy Nexus] Rushead:
I can help.

Step one: don't let her speak. Either close her mouth or fill it with something......
[Samsung Galaxy Nexus] cujo6801:
Always sound advice... :D

Sent from the "DOG" pound
[Samsung Galaxy Nexus] DeadMetaler:
How can i use these presets?
[Samsung Galaxy Nexus] bsmitty83:
Download the free kernel tuning app called "synapse" from the google market , the profiles are only for that app .
[Samsung Galaxy Nexus] amd_h4x0r:
You will also need BusyBox installed to use the profiles.
[Samsung Galaxy Nexus] CoDe LaZaRuS:
[MENTION=4608636]bsmitty83[/MENTION] how do I get touch control to work with your last dirtyV SR kernel
[Samsung Galaxy Nexus] Airlibik:
try to run the other modules...I don't remember if it worked with ponury stok or franco kernel module...

but i think it worked with franco if i remember good.
[Samsung Galaxy Nexus] amd_h4x0r:
Does anyone know how to mitigate these kernel wakelocks? My BetterBatteryStats log is attached.

modem_usb_suspend_block

modem_usb_gpio_wake

nfc

I don't even have NFC enabled, so I'm curious why it shows up.
[Samsung Galaxy Nexus] bvsbutthd101:
I have problem that doesn't just happen on this kernel. On others as well. I've only ever noticed it not happen on one kernel, (the ASKP r430 kernel). When I'm in a skype call and I minimize to go to the homescreen or another app the call begins to stutter like it's cutting in and out pretty fast. The person on the other end of the call also experiences me cutting in and out. I'm wondering if it's a setting in the other kernel since it doesn't happen on that one. Would love to figure out what it is because my phone seems to be fastest on this kernel. Also I'm running Slimkat build 9.0 (toro).

Thanks,

Brian
[Samsung Galaxy Nexus] taylerdurden:
Hello, I will try this kernel in my CM11 Maguro. But I have a question, what is the difference between SmittyV and DirtyV?

I understand SmittyV is the same, but DirtyV is not optimized (I have to optimize it with Nephilim setting for example), and SmittyV is already optimized?

:confused:
[Samsung Galaxy Nexus] Iced-Earth:
thanks for the F2FS recovery for maguro!

are you planning to fix usb-otg mount someday? Would be much more comfortable with working usb-otg.

thanks in advance
[Samsung Galaxy Nexus] bsmitty83:
The only difference between the versions is the amount of ram available to the system. SmittyV = least , dirtyV-sr = most
[Samsung Galaxy Nexus] taylerdurden:
Thanks in advance. I mean DirtyV (not SR)
[Samsung Galaxy Nexus] Rushead:
It's the middle choice:

Smitty V - - > Dirty V - - > Dirty V-SR
[Samsung Galaxy Nexus] taylerdurden:
So, if there are no differences except the RAM, is DirtyV-SR always the best option?? Why SmittyV and DirtyV exist?
[Samsung Galaxy Nexus] Rushead:
"Best Option" is a relative term. Some people have bad experiences with sr versions. Smitty V is actually [MENTION=4608636]bsmitty83[/MENTION]'s personal build. He stripped it down somewhat catering to what he preferred.
[Samsung Galaxy Nexus] bsmitty83:
If you use the super ram version , you lose the ability to play/record 1080p , which is OK for some. Also weather or not the reclaimed ram actually helps is also debatable , there no question the ram gets reclaimed , but I never saw any increase in performance or any benefit at all.

Really smittyV doesn't need to exist, it was a personal build I put out that kinda caught on for some . for me it was a kernel with stock ram to test if I could make memory management better. My goal was to show no matter how much ram the system has it should be able to run smooth . not sure if I accomplished that but look at it this way , now you have 3 different kernels to try . [emoji6]
[Samsung Galaxy Nexus] CYoung234:
On my gnex, I seem to only be able to run the smittyV version, so I am happy that you still have it. It looks like my gnex may have some sort of memory management issue. I am attaching a kmsg that I took while I was trying the dirtyV version out. My phone would boot, but would lock up and reboot shortly thereafter. I was using the nephilim settings with Trickster. I commented on my phones issues over in the Lollipop thread, as I could never get your Lollipop kernel to boot.
[Samsung Galaxy Nexus] pvkiniyan95:
Suddenly went back to vanir 4.3.1 with this kernel and felt home....
[Samsung Galaxy Nexus] Dirty_Jerz:
I think neph's voltage settings are a little aggressive for some. Try backing off towards stock a bit on them see if that helps.
[Samsung Galaxy Nexus] CYoung234:
The voltages do not seem to be the problem. Here is a last_kmsg running DirtyV-SR at stock voltages. My gnex reboots randomly in thus configuration. SmittyV seems to run well with nephilims settings, however.
[Samsung Galaxy Nexus] seriousia:
No kernel after smitty80.30.14 runs properly on my maguro.

Phone starts to lag alot and application starts to force close. :confused:

Any solution?
[Samsung Galaxy Nexus] Rushead:
Stay on 8-30?
[Samsung Galaxy Nexus] seriousia:
Well thats exactly what i'm doing :D
[Samsung Galaxy Nexus] elnoo:
Hello,

first of all thanks for all your hard work, you make a great phone even greater :D

My phone slowed down and crashed a lot with CyonogenMod so i took som guts and redid everything:

I converted System, Cache and Data to F2FS and installed ShinyRom 4.4.4 (http://xdaforums.com/galaxy-nexus/development/rom-6-4-14-shiny-rom-ota-stock-android-t2642375)

I want to use the DirtyV-SR-Ak2-Final Kernel but i have some problems:

If i use the Final Version from the first page i got stuck on the Google Logo booting, waited for 10 min nothing happens. I read it should work on F2FS based phones.

My GNEX is able to start up when i use the alternative Kernel cwm-DirtyV-SR-6.15.14-2-Unified.zip - modified by [MENTION=4544860]osm0sis[/MENTION] from the Converter Tool Thread (http://xdaforums.com/galaxy-nexus/development/tool-galaxy-nexus-ext4-to-f2fs-rom-t2794702).

With this kernel i'm not able to watch any video that is 1080p so basicly i am unable to use youtube/vimeo. I guess this is because its an older Version of the kernel (i know i wont be able to record 1080p videos but not even watching them...thats a bummer :D )

I tried checking and not checking the "AnyKernel" option in the Converter Tool, both times i get the same result after flashing the kernel.

Did i do something wrong?
[Samsung Galaxy Nexus] osm0sis:
Same issue I had with all the subsequent kernels, which is why my last osmod/Unified2 release was of it. http://v.ht/osmods :good:

Edit: Attached my final osmod/Unified release below for posterity since BasketBuild appears to be dead again. :rolleyes:
[Samsung Galaxy Nexus] uconnpat:
I'm on aokp 4.2.2 because that is the newest rom I can use and not have data/4g hangups.... What do I have to do to flash this kernel? Do I have use this twrp and do I have to use an older kernel? Thank you
[Samsung Galaxy Nexus] bsmitty83:
No any recovery should work fine to flash the kernel , as for which version to use , many have found the last version to be unstable . personally I never had much of a issue with it , beyond the occasional random reboot , but try the version mentioned in the last few posts if you have any issues with the final version .
[Samsung Galaxy Nexus] motorazrv3:
I am thinking of going back to good old jb to. Currently I am on vanir 4.4.4 and fancy r60.

Could you share the download link to vanir 4.3.1?

Has vanir 4.3.1 already active display implemented?

Greetings from Germany