yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] pattyboi:):
but only the best WOULD build so many times ;)
[Samsung Galaxy Nexus] fracama87:
You are the best many times! ;)

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] Nephilim:
So even though you had to revert AK Interactive will regular Interactive work okay for now?

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
Yes I'm using it now
[Samsung Galaxy Nexus] sym_m:
Link not work ?
[Samsung Galaxy Nexus] shockerz1z:
yea actually all the links are not working at all
[Samsung Galaxy Nexus] pattyboi:):
read the previous page.^^^^
[Samsung Galaxy Nexus] juju2011:
They down for now give Smitty abit of time
[Samsung Galaxy Nexus] bsmitty83:
go ahead and try them now .... no time required
[Samsung Galaxy Nexus] Charmacas:
Could you tell me?
[Samsung Galaxy Nexus] Nephilim:
New DirtyV Linaro is working great so far with Interactive, I'll letcha know if anything changes.

Still wondering what changed in this build that we lost 4mb of available memory/ram. It was 761mb now its 757mb.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
I built cifs support into the kernel . that's where it went . I can remove it
[Samsung Galaxy Nexus] scarcry:
I just flashed DirtyV2-SR Linaro and Vanir is upgrading.

Can't wait :)
[Samsung Galaxy Nexus] luckana:
is it worth it changing to this kernel from mpokang ??
[Samsung Galaxy Nexus] bluerez79:
I think yes. Give it a try. Smitty's work is amazing
[Samsung Galaxy Nexus] scarcry:
all depends what you expect from a custom kernel I suppose.

but with no active development to mpokang AFAIK and with 2 experienced developers active on Dirty_V I choose to go the dirty route.

Tapatalked from my maguro running vanirAOSP nightlies
[Samsung Galaxy Nexus] luckana:
how's the performance and smoothness compared to mpokang ?
[Samsung Galaxy Nexus] fracama87:
My gnex can fly again :D

Thanks smitty for the "wings" ahahaha

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] Nephilim:
Try it for yourself, we can't tell you that it's up to you to find an opinion.

Sent from my Android 4.4.2 Galaxy Nexus

---------- Post added at 03:45 PM ---------- Previous post was at 03:44 PM ----------

It's not negatively effecting anything so no need to remove. I just notice stupid little things like that so I thought I'd ask. ;(

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] marcocsh:
Same here:highfive:
[Samsung Galaxy Nexus] pianistaPL:
Omni doesn’t have Theme manager ;)
[Samsung Galaxy Nexus] michierusama:
Cm11 M5. And all fine. Too much issues with the new engine in nightlies so I will stay there.
[Samsung Galaxy Nexus] pvkiniyan95:
I have to hold my gnex for the next two or more years until I finish my college and get a job :p hope will learn to develop for this precious device

Sent from DirtyVed GNex
[Samsung Galaxy Nexus] dezful:
just converted LS to Carbon 04/25 + Smitty 04/24. No random reboots so far like in LS. I reckon there must be some bugs in LS ROM.
[Samsung Galaxy Nexus] Nemed:
I'm trying the latest smittyv, so far so good! (Cm11 m5)

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] pattyboi:):
see,thats the only problem with running custom roms and kernels at the same time,we cant always narrow down which one is causing problems :P

(excluding kmsg :P )

"the problem with innovation,is that it introduces problems we didn't have to face before"
[Samsung Galaxy Nexus] luckana:
i have a problem (dont know if it's kernel or rom related) - every time i press reboot from the reboot menu the phone gets to the google logo and then it vibrates and reboots itself again and the same thing over and over until i battery pull and then it boots normal... it doesnt make sense ?
[Samsung Galaxy Nexus] pianistaPL:
As i said, i had this on Omni.
[Samsung Galaxy Nexus] luckana:
so it's kernel related? did you fix it? it just happened one day, it rebooted normally before
[Samsung Galaxy Nexus] pianistaPL:
I didn't read well your post... My phone didn't boot anymore, i had to reinstall ROM.
[Samsung Galaxy Nexus] Atento:
What I don't understand is if the new theme manager is the root of all problems, why every developer merged it on their custom roms?
[Samsung Galaxy Nexus] DR3W5K1:
CyanogenMod merged it. The rom developers didn't merge it they are just doing repo sync's
[Samsung Galaxy Nexus] Atento:
But can't they remove this breaking theme manager from sync?
[Samsung Galaxy Nexus] DR3W5K1:
Sure they could.

They don't make the nightly builds though. They are automatically made by computers.
[Samsung Galaxy Nexus] osm0sis:
Yeah that's the only thing I don't get. Why don't the satellite ROM maintainers who aren't actively working with CM on fixing it revert it until it's ready for prime time? Then we'd all have stable ROMs in the meantime. :confused:
[Samsung Galaxy Nexus] michierusama:
Thats why im using M5. XD and by the way im not having issues with kernel in this ROM. Cm11 M5. All good. I will wait till next M/Stable release.
[Samsung Galaxy Nexus] aosp:
VanirAOSP removed the ? and problem free builds will be available in the next nightlies and no voodoo needed for 768MB vmalloc thanks [MENTION=4608636]bsmitty83[/MENTION]
[Samsung Galaxy Nexus] osm0sis:
Nice. Hopefully Carbon and the others that are simply waiting will follow suit.
[Samsung Galaxy Nexus] metalspring:
Speaking of upgrading, [MENTION=4608636]bsmitty83[/MENTION] (or anyone else running ubuntu) have you updated to 14.04 yet? I'm thinking of upgrading sometime this week but not sure if its worth it.

Btw, the one issue I have with nexus devices (even our beloved gnex) is they always seem to already be one or 2 steps behind every other major phone even right at release so towards the end of 2 year contracts you almost have to run custom roms and kernels to keep things from lagging too much. I dont think the nexus 6 will be any different since the reason they launch outdated is to make them cheaper to buy
[Samsung Galaxy Nexus] bsmitty83:
I did a few nights ago when I was bored and sick of being reminded by pop ups that a new version is out lol , its a little cleaner .

Don't matter to me what android phone I have , I'll always root and use custom ROMs . I had stock note 2 jb touchwiz ROM on my phone for 10 min . , less for my nexus I powered on , saw it turned on , then immediately unlocked it and put a new ROM on it .

You should consider kicking out at least one more omni build with my latest smittyV kernel onboard , and you could use linaro 4.9 [emoji14]
[Samsung Galaxy Nexus] pattyboi:):
the "goodbye edition "
[Samsung Galaxy Nexus] metalspring:
Yeah, those update reminders are annoying lol, as for one last rom build, I was planning on it but it would be a little while to make sure it has all the features that are likely to be added in before too long and to ensure there are as few bugs as possible, plus I may try to pull in a few things from other roms. Hopefully linaro 4.9 isnt too big of a pain to use though
[Samsung Galaxy Nexus] Rushead:
Don't pull battery. When the screen goes black, hold all 3 buttons & you should get the bootloader screen.

Sent from a flashead cracker.
[Samsung Galaxy Nexus] pattyboi:):
well,i really hope your able to pull something out of your sleeve,i always loved cmetal/omnimetal,always ran crazy smooth :good:

---------- Post added at 04:48 PM ---------- Previous post was at 04:47 PM ----------

i see something f*cking awesome in smitty's git..and if my guess turns out to be right...........

SH*T IS BOUT TO GET REAL.
[Samsung Galaxy Nexus] metalspring:
Something or some things? lol

I see a lot of f2fs commits merged in, f2fs enabled in defconfig and a new zimage
[Samsung Galaxy Nexus] pattyboi:):
multiple things lol :P

i wanted to make everyone go look and find out instead of spoiling it :3
[Samsung Galaxy Nexus] bsmitty83:
Still working on f2fs , needed to see something so its enabled . I got lazy today and did nothing lol . I added meminfo to synapse and am adding vmstats and maybe dmsg too . basically working on synapse today .
[Samsung Galaxy Nexus] Hetalk:
Vanir

---------- Post added at 10:32 AM ---------- Previous post was at 10:30 AM ----------

Same here as well.
[Samsung Galaxy Nexus] shag_on_e:
So far, the super ram kernel is the only one I've found that can handle a few services running without having low memory problems. I love it, seriously. I do wish we could maybe get some Touch Control module support though, but I can sacrifice if need be. Thanks boype!

~~~~There is no spoon~~~~
[Samsung Galaxy Nexus] Royal King:
Touch control works here..
[Samsung Galaxy Nexus] qu4nd:
I've had some issues with reboots when using touch control. Dirty flashed rom and kernel again and it worked fine afterwards...
[Samsung Galaxy Nexus] dbh369:
Now that x2 looks indefinitely delayed, I may try to nurse my cracked gnex through to g3 or nexus 6 too, S5, One just don't thrill me...
[Samsung Galaxy Nexus] infectedorganism:
Anyone.. I know you can't give a number, but what should one be seeing as the first number in /data/trimhelper? My value is 1398705825 and based on the counter, fstrim has yet to be triggered.

Sorry to be a pain, I'm just trying to understand this a bit more.
[Samsung Galaxy Nexus] spirit1002:
I have this problem too. Use CM11 M5. DirtyV 23/4 & 24/4 both have this problem. But 19/4 version seems ok
[Samsung Galaxy Nexus] osm0sis:
That's the timestamp. Totally normal (it's the date in seconds). Did you enable suspend_trim in Synapse? The 3rd number should be 1 if so. If not that's why it wasn't working. :)
[Samsung Galaxy Nexus] infectedorganism:
It was enabled via terminal command.

I am currently using your script on another kernel so I won't ask for any troubleshooting, I was just unclear as to what exactly that first number represented.

I recently rebooted and only have 2 hours of uptime. I'll give it more time to see if fstrim kicks in.

As always, thanks.
[Samsung Galaxy Nexus] osm0sis:
The script doesn't work without the kernel-side support which triggers the script run as the screen turns off. So, that's why. ;)
[Samsung Galaxy Nexus] infectedorganism:
Eh.. at least I'm learning, ha.
[Samsung Galaxy Nexus] dbh369:
34+ hours without a reboot, including my morning run, first time in awhile, smutty 4.26. :D:thumbup:

---------- Post added at 10:15 PM ---------- Previous post was at 10:15 PM ----------

Smitty! ! ! Dam auto correct
[Samsung Galaxy Nexus] cujo6801:
Yeah autocorrect..... :D

Sent from the "DOG" pound
[Samsung Galaxy Nexus] krweby:
I'm seeing this also now with DirtyV-R 4/24. I have also gone back to 4/19.
[Samsung Galaxy Nexus] bsmitty83:
I think the autocorrect version is more accurate lol [emoji14]

Gonna try to get a few builds out tonight . been working hard on f2fs , no success but I missed some thing previously that are good now . Im still working out getting the partitions flashed to f2fs from ext4 .

I haven't given up yet .......

Really getting tired of the options for kernels for the vzn note 2 I'm using , so I'll be working on a kernel for that as well .

Got a ROM source syncing now , gonna try some more f2fs when its done , but in the mean time I'll be working on DirtyV

Smutty out [emoji44]
[Samsung Galaxy Nexus] TheMan0790:
Mhhmm...love me some smut kernels....
[Samsung Galaxy Nexus] michierusama:
smutty lmao i like it
[Samsung Galaxy Nexus] cujo6801:
Move over dirty gang

Smutty's new gang is taking over.... :D

Sent from the "DOG" pound
[Samsung Galaxy Nexus] TheMan0790:
I think we need a few new tags for the thread...[NSFW] [18+]
[Samsung Galaxy Nexus] osm0sis:
:p
[Samsung Galaxy Nexus] DR3W5K1:
I dunno last time I checked this thread was all guys... No 18+ for me please.

That is unless it's some of cujo's hot biatches
[Samsung Galaxy Nexus] luckana:
ok, so like 2 people already confirmed this, [MENTION=4608636]bsmitty83[/MENTION] if you could chek this out
[Samsung Galaxy Nexus] osm0sis:
It's been ages since I've had Google logo bootloop issues on this kernel..

It seriously used to be like every kernel flash for me, and I don't see it at all now, so I'm not sure why you 3 guys are. :confused:

Edit: I see you're all on CM M5 though. Perhaps CM changed something so when I rebased it on the 20th it broke it on the M5 fork?

CM even breaks their own sh*t now, how bout that? :p

Anyway, the changes appear solid for everyone else, so maybe just try a slightly newer CM build?

---------- Post added at 02:32 AM ---------- Previous post was at 02:29 AM ----------

[MENTION=4608636]bsmitty83[/MENTION]

yo Smutty, peep dis ;)

https://github.com/bsmitty83/DirtyV_tuna/commit/09460c46a866a01366d2738d8c572812f833f356
[Samsung Galaxy Nexus] luckana:
the thing is that it happens only and specifically on DirtyV-R 23/4 and 24/4. Other kernels are fine
[Samsung Galaxy Nexus] osm0sis:
Yep, the only 2 since the ramdisk rebase using CMs newer ramdisk files. Sounds like it's fine on anything newer than M5 and every other ROM. Can you try dirty flashing a more recent CM nightly to make sure?

M6 will be using the newer changes too so really, there'd be no point in reverting them. If I had to guess, I'd say it's one of the binaries, since all the rc stuff was pretty trivial.
[Samsung Galaxy Nexus] GilGameshn1:
Again ... ROM sided bro ... Believe [MENTION=4544860]osm0sis[/MENTION] ... [emoji106]

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] luckana:
Clear enough, thanks for explaining it all :)
[Samsung Galaxy Nexus] Droiderat:
I had the same issue on DirtyV-R 24/4 (with cm-11-20140411-NIGHTLY-maguro). Moving to SmittyV-NoMeM-4.26.14 fixed it.
[Samsung Galaxy Nexus] pvkiniyan95:
[MENTION=4544860]osm0sis[/MENTION] [MENTION=4608636]bsmitty83[/MENTION] guys does this kmesg mean anything to u www.pastebin.com/ScPkPw4z

coz i got a reddish splashed screen for few minutes but every thing was working though, thought a screenshot would capture it but when it came back to normal the screenshot was also normal
[Samsung Galaxy Nexus] osm0sis:
I get red, green or blue tinted boots once in awhile lately too. Playing with the color settings once booted fixes it. Sometimes Synapse setting my color settings resolves it too. I assumed it was something weird going on with my color init.d script, but now you've got me wondering if it's something kernel-related..

Maybe something leftover from a bootsplash attempt that's conflicting?
[Samsung Galaxy Nexus] pvkiniyan95:
Eveytime I flash a new kernel I take care of clearing any kernel related initd script and also flash them after flashing ur original kk kernel be it ramdisk or anykernel so I dont think a leftover is a reason

The red screen appeared not while booting but while unlocking may be a soft reboot would have happened without my knowledge

Sent from DirtyVed GNex
[Samsung Galaxy Nexus] osm0sis:
It's my init.d script I'm talking about. Do you set colors during boot? Totally not necessary to flash a different kernel prior to anything that isn't AnyKernel, by the way.

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

Do you use Synapse? The GPU OC and OMAP Gamma Contrast settings both cause screen glitches when set, and together the way Synapse does it (even if OMAP is 0) causes a big glitch. But it usually passes instantaneously with no lasting effect. Hmm I'll make an exception for OMAP that avoids setting it when it's set to 0 (disabled). Best I can do.
[Samsung Galaxy Nexus] pvkiniyan95:
I don't set any settings to apply on reboot either in trickster or as script, I apply them manually coz I am frequently jumping between askp Franco fancy smittyv dirtyv testing them, guess what now I m in askp haste :p

Sent from DirtyVed GNex
[Samsung Galaxy Nexus] redj12:
Dirty is not compatible with jelly bean ? I am on SlimBean and can't overcome the Google splash screen. What I have to do ?

Envoyé de mon Galaxy Nexus
[Samsung Galaxy Nexus] pvkiniyan95:
I don't use synapse, its not for me, either trickster or scripts or terminal

Besides I m happy with default colour settings of all above mentioned kernel except one which should not be named
[Samsung Galaxy Nexus] cujo6801:
Like this.....

Sent from the "DOG" pound
[Samsung Galaxy Nexus] DR3W5K1:
Yes Sir!

Ok thread is now rated 14+. XD

---------- Post added at 10:40 AM ---------- Previous post was at 10:37 AM ----------

lmao he made tags
[Samsung Galaxy Nexus] bsmitty83:
You would have to split the boot.IMG apart and use the zimage with a jellybean ramdisk , or use it in an any kernel zip , or fastboot flash the zimage .
[Samsung Galaxy Nexus] redj12:
Jezz...seems complicated. I've never done that. Will try.

Thanks ;)

Envoyé de mon Galaxy Nexus
[Samsung Galaxy Nexus] klobkelosh:
I can't remember who posted this, but I saved it in case I ever needed to make an anykernel.

Just grab an any kernel zip, and extract it to your sdcard. Then take the file unpackbootimg and copy/paste it into /system/xbin and set permissions to rwxr-xr-x.

Then take the boot.img of the kernel you want and open terminal emulator.

Now just navigate to where your boot.img is and type

unpackbootimg -i ./boot.img -o ./

Now you have your zImage to drop in an anykernel zip

It sounds complicated but it's actually really easy

(If you want WiFi tethering on the new builds you'll have to actually open up the ramdisk to get the proper hostapd file).

Thanks to whoever posted it in the first place. Apologies for not writing down your name.

There's also an app on the market that will unpack for you. https://play.google.com/store/apps/details?id=com.leejonghwan.unpackbootimg
[Samsung Galaxy Nexus] krweby:
I see it also and I'm running AOKP not CM. I'm running DirtyV-R is that what everyone else having the issue is running?
[Samsung Galaxy Nexus] aosp:
apktool can repack ;)

https://code.google.com/p/apktool/

https://code.google.com/p/apktool/wiki/how_to_edit_bootimg

https://github.com/pqy330/apktool

[MENTION=4544860]osm0sis[/MENTION] ?
[Samsung Galaxy Nexus] osm0sis:
Use my Android Image Kitchen, go to Smitty's Github and download the files from the AnyKernel2 directory. Then unpack the Dirty image of your choice and grab the zImage, then copy it to the AnyKernel2 directory. Zip and flash.
[Samsung Galaxy Nexus] TheMan0790:
Doubt this is kernel related at all, but is anyone having problems receiving BBMs or emails through Gmail on their phones? Absolutely nothing goes through for either of these apps. I'm on latest Smitty and latest LS (using Neph's kernel settings).
[Samsung Galaxy Nexus] Nephilim:
Might be the newest update of the rom. I'm a few versions of Liquid behind and my settings are working fine with SmittyV.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] TheMan0790:
Maybe. Hope a new release of LS comes out soon so I can test out whether it is ROM related.
[Samsung Galaxy Nexus] michierusama:
For all the ones having issues with cm11 M5 I'm using it since a week and smutty xD 04-26 and all is good. Not a single issue. With neph's settings. Bye. :P
[Samsung Galaxy Nexus] terminal13:
Beauty on the latest. Shut off my sync and battery went from 80- 82 over night. Love having three batteries to confuse myself with. Time to calibrate I guess.....
[Samsung Galaxy Nexus] bsmitty83:
DirtyV in 3D ....[emoji6]
[Samsung Galaxy Nexus] ashclepdia:
That would make me nauseas after a bit I think lol

---------- Post added at 11:39 PM ---------- Previous post was at 11:35 PM ----------

Oh hey by the way

Just saw this in OMNI FML thread (toro)

Apologies for OT but thread is always so active and I've seen people mention having AUDIO STUTTER ISSUES before(whether kernel related or not) so if this works u may wanna mention it to your favorite ROM dev

https://gerrit.omnirom.org/#/c/6854/

I never had the issue myself(except on my droidX2 HOLY CRAP that thing skipped music just trying to look at twitter lmao) but thought some of u who have mentioned it might want to ask ur ROM dev to try that before attributing the issue to the kernel only :)

Side note: I really wanna try that omni FML build. I like mwisbest's attention to details and toolchains
[Samsung Galaxy Nexus] DR3W5K1:
If someone could point CM to this it would be very helpful.
[Samsung Galaxy Nexus] dbh369:
Ok, spoke too soon, I'm getting warn boots at night, state time still running, but fresh start notifications the morning after being left plugged in. Maybe trim is causing?
[Samsung Galaxy Nexus] DR3W5K1:
No trim cannot cause this issue. Can you provide a dmesg?
[Samsung Galaxy Nexus] büscher:
Also just got a warm reboot out of nowhere. Didn't do anything with my phone for a while, just saw it rebooting while walking by. Also first thought was trim, I have no idea what else could have been causing this...

Edit: also wifis got lost (not new but I somehow managed to keep them a little longer than just some hours)
[Samsung Galaxy Nexus] xxSAKISxx:
i am a quiet watcher of this thread almost from the "berth" of this kernel or should i say masterpiece. I just want to say only one thing. [MENTION=4608636]bsmitty83[/MENTION] Bro i dont know what you do in the last 2 builds of Dirty V but paired with Slimkat leave me speechless and as we say here in Greece ΜΠΡΑΒΟ ΡΕ ΜΑΓΚΑ. sry for the greek words. A big thanks you to you and all devs that put they knowledge in to this kernel. [MENTION=2838735]aosp[/MENTION] [MENTION=2853378]Nephilim[/MENTION] [MENTION=1143630]osmosis[/MENTION] and sry if i forgot someone.
[Samsung Galaxy Nexus] osm0sis:
You both have suspend_trim enabled in Synapse/sysfs? It defaults to disabled. I've been running it 24/7 since I added it with no issues though.. Hmm. last_kmsgs from you both (provided you haven't rebooted again) would help. :)
[Samsung Galaxy Nexus] dbh369:
No Last-K on mine, warm reboots don't leave one do they? Also, not running Synapse, using Buscher's script, with slight mods. But just for s&g, I ran lag fix, and it ran in maybe 2 sec max...
[Samsung Galaxy Nexus] osm0sis:
Warm boots that don't show the Google logo won't. No. So sounds like you aren't running suspend_trim? Probably unrelated to trim then.
[Samsung Galaxy Nexus] gabrielss:
To enable suspend_trim do we need to download the synapsed version and turn it on there. Or it is enaugh to edit "trimhelper" file (changing the 3rd row from 0 to 1) in the normal version?

Thanks!
[Samsung Galaxy Nexus] osm0sis:
Correct! suspend_trim is already in Synapse on the current released version. Synapse is just a tweaking app that allows kernel devs to build their own custom interfaces. My "Synapsed" versions have my latest fixes. So Synapse is the easy way to enable/disable but you can use the commands I posted or edit the file too if you want to do it the hard way. ;)

I just uploaded a new Synapsed version if you want my latest fixes (added Dev Tools to make bug reporting with dmesg/kmsg and logcat easy, also avoiding the glitch on boot with OMAP Gamma if it's set to 0: Disabled). They're already committed on Github, so it'll all be in the next released version too. :)
[Samsung Galaxy Nexus] infectedorganism:
Has anyone noticed any significant battery drain with trim enabled?

I'm not suggesting that it does, I'm just trying to narrow down the reasons behind the battery drain I'm currently experiencing.
[Samsung Galaxy Nexus] osm0sis:
Still sleeping like a baby here. suspend_trim could only affect sleep/idle drain (and it doesn't from what I've seen), since it runs when the screen is off. There is no way it could affect screen on drain. :good:
[Samsung Galaxy Nexus] bsmitty83:
New synapse is crazy man ......

Very cool rework .

As soon as I get some time I'll get some new kernels up .

Been going hard on f2fs , mostly just figuring out how other devices are doing it . there seems to be two ways . one uses a format script to manually format the system and cache partitions to f2fs . latest twrp and cwm should support reading f2fs. And formatting data partition

Then there's the 2nd way and that's to modify the recovery to format f2fs by choice any partition . this is the best way to do it IMHO but a lot harder for me lol . so for now I'm going the script way . just takes time to get the procedure down . sometimes I guess multiple wipes and script flashes are necessary too , so we'll see I guess .