yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] poo706:
Those steps look right to me. My tool would be needed if you have /system formatted as F2FS. And it would be needed if you have /data formatted as F2FS and /data is mounted during the ROM installation. Yesterday I added a couple of prompts to my tool. It'll ask you if you plan to use an AnyKernel kernel, and if so, it won't replace boot.img with Fancy. And it'll ask you if /system is formatted as F2FS for those that have kept it as EXT4.

[poo]
[Samsung Galaxy Nexus] gautam_nexus:
I am kinda confused. :eek: I think i will still use your tool. :D
[Samsung Galaxy Nexus] poo706:
Might as well just play it safe.

[poo]
[Samsung Galaxy Nexus] bsmitty83:
Maybe . it could be many things , which is what I'm hunting down lol . since I use this phone everyday again , I've noticed a lot of $h!t I'm not happy with.

I'm thinking the the freezes could be data relates because it seems like it only happens when I'm heavily multitasking with apps that use a lot of data and ram . like chrome and spotify and YouTube . I've noticed it happens when something is loading in an app like a webpage loading , then hitting the recents button and switching to say spotify will do it .

So it can also be mm related , how information is being moved around and accounted for . like i said could be a myriad of causes .

Fear not and hang in there hopefully I'll get it sorted out . feel free to play with the tunables to try to get it to stop . if anything works or dosent , post it . this thread is bonkers cause everyone helps [emoji106]
[Samsung Galaxy Nexus] Jar3112:
Great news man. I'll try and report back.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
Anybody wanna try out a kernel ?

https://www.dropbox.com/s/6o1ibk3z752iym8/personal19.zip?dl=0
[Samsung Galaxy Nexus] sergialess:
Sure. Testing. So far it's working pretty well on Poo's LS. Want to try something in particular?.

BTW, a polish guy re-flased remotely nv_data and restored my IMEI. I'm happy. Impressive work, may I add...
[Samsung Galaxy Nexus] cujo6801:
I'm in

Dling

Sent from the "DOG" pound

---------- Post added at 09:25 AM ---------- Previous post was at 09:07 AM ----------

So far so good on poo's LS..

Sent from the "DOG" pound

---------- Post added at 09:49 AM ---------- Previous post was at 09:25 AM ----------

Check out these settings

Fast ...

Sent from the "DOG" pound
[Samsung Galaxy Nexus] Nephilim:
Does it have ramdisk?

Sent from my Android 4.4.4 Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
No [emoji17] still need to figure out what's up , ramdiak builds are not working on my phone ATM , but its a local issue with me , just need to figure it out

Try it and see if you get bootloops on charging , its an attempt to fix that as well
[Samsung Galaxy Nexus] Nephilim:
Sounds good, I'll give it a go shortly.

Sent from my Android 4.4.4 Galaxy Nexus
[Samsung Galaxy Nexus] 7175:
Thanks man, testing now.. No bootloop on a reboot with usb plugged in. :)

Also I saved a dmesg from the last time I got a screen freeze on 9-10. Thought I'd go ahead and post it. Kind of funny, plugging the phone into usb and taking the dmesg over adb unfroze the screen.
[Samsung Galaxy Nexus] Jar3112:
Installed v6 supercharger on top of 9-14 version, will report improvements. Among the other things it changes vm heapsize and heapgrowlimit, so we can check out if it is the problem of the freezes

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] KreNtal:
Youtube problem

Found a really weird bug that I think it's related to this kernel.

Sometimes (occasionally) when I open a youtube video on the official YouTube app, it says "There was a problem while playing. Touch to retry."

If it happens I can't watch video anymore even on the youtube site and on every other youtube app out there. Really weird.

If I reboot my phone everything goes back to normal; I can play videos again but whenever that message appears I can't play videos anymore on youtube only.

Some time ago I took a logcat and I think it is something related to ExoPlayer.

What I'm doing now is to test if it happens on the original cm kernel, if it doesn't happen I'm sure that is something kernel-related 'cause I've already done lots of test.
[Samsung Galaxy Nexus] Punkiderma:
[MENTION=4608636]bsmitty83[/MENTION]

Here

http://xdaforums.com/showthread.php?p=55484007

[MENTION=3292224]franciscofranco[/MENTION] talks about a patch from CM to reduce battery drain due to the Bluetooth chip powered even if Bluetooth is off.

Tought could interest :)
[Samsung Galaxy Nexus] osm0sis:
You on SR? I think that's a known issue on SR. Camera might still ragequit occasionally if you take a video, watch it, and try to take another immediately after as well.
[Samsung Galaxy Nexus] bsmitty83:
Yea i think he's on regular dirtyV , but I think I know the issue , my camera got a workout last week when the blue angels were around my house . dirtyV camera would fail on hard use .

See above [emoji39]

Yea , I can pick that . I never checked to see if Bluetooth was still powered even tho its off
[Samsung Galaxy Nexus] kansasboy001:
Are the nephilm kernel settings still needed?
[Samsung Galaxy Nexus] KreNtal:
Yeah I'm on SR and I can confirm that it doesn't happen on stock cm kernel, now I'm testing on normal dirty-V and then I will try to take a good logcat on dirty-V SR.

Hope it can be fixed :(
[Samsung Galaxy Nexus] osm0sis:
That's always been a preference thing, so it's up to you. I personally run SR with defaults and it's great. I think Smitty does the same with SmittyV.
[Samsung Galaxy Nexus] bsmitty83:
I've been messing with things so I haven't been using nephs tunables , but they do work well .

As for the camera issue its a simple fix if it fixes it [emoji106]
[Samsung Galaxy Nexus] pianistaPL:
Don't you have problems with video playback, like Youtube HD videos or videos on websites?
[Samsung Galaxy Nexus] osm0sis:
Once in a long while, but generally nope. :)
[Samsung Galaxy Nexus] kansasboy001:
I have been having random lockups with the latest sr versions using nephilms settings. Even when I just oc the CPU and don't touch anything else I have problems. Everything uses to work fine
[Samsung Galaxy Nexus] Nephilim:
I'm using Nephilim's settings on the 8/30 SmittyV build, it's running pretty decent. About to try that test build Smitty put out the other day. :P
[Samsung Galaxy Nexus] mrgnex:
Huh you are using his settings? I thought you said they were crap and you hated that guy. XD
[Samsung Galaxy Nexus] Nephilim:
Shhhh.
[Samsung Galaxy Nexus] osm0sis:
[MENTION=4608636]bsmitty83[/MENTION] TWRP 2.8.0.1 sounds like it might fix the screen off touch response failures. :good:
[Samsung Galaxy Nexus] Nephilim:
Personal Test build seems to be working well. Trying it out with stock settings with only my colors changed for now. So far no lag on keyboard and no random reboots.

Sent from my Android 4.4.4 Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
If you get some freezes , you can turn zram off , or if u wanna deal with it if it totally locks , holding all 3 buttons down will reboot it
[Samsung Galaxy Nexus] osm0sis:
Really?! I couldn't get the oh****button service to work! You some kinda voodoo master? You bring it over kernel-side from that repo [MENTION=2838735]aosp[/MENTION] found?
[Samsung Galaxy Nexus] bsmitty83:
Honestly I think its ROM side with vanir , I tried a while ago to add that but I dont think it ever worked . my kernel is closer to ozoom than stock tuna so maybe I did and forgot about it . I've probably added thousands of commits by now
[Samsung Galaxy Nexus] Nephilim:
Zram was turned off on the personal build.

Sent from my Android 4.4.4 Galaxy Nexus
[Samsung Galaxy Nexus] Jar3112:
I keep receiving already read messages in whatsapp, does anyone else have the issue?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] büscher:
somehow my post was not posted here...

I wanted to thank you guys for all your effort and time you put in our Gnex.

As you may already read I'll change my phone. It has become too much of a hassle dealing with all its problems. I already wasn't very active anymore because of me getting tired of my phones s**t.

I can't mention everybody that helped me in this thread but thank to you guys I learned a lot about android and its kernels.

A special thank goes out to [MENTION=4608636]bsmitty83[/MENTION] for creating such a great kernel that attracts so many talented devs and contributors.

Anyway, because I can't just abandon such a great community I'll sneak around from time to time, I also need a working backup-device.

so once again THANK YOU for a great time :highfive:
[Samsung Galaxy Nexus] motorazrv3:
No. Why should this be kernel related?
[Samsung Galaxy Nexus] Jar3112:
I got some friends reporting to have this problem ONLY on Dirty-V, o fancy (for example) the issue is gone.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Punkiderma:
I have that, but I can't say is only on DirtyV.

However, since I had the Gnex, it never happened, and started some months ago.

Still trying to understand if wiping dalvik solve this (apart from deleting the conversation)
[Samsung Galaxy Nexus] Jar3112:
Barking up measages, uninstalling the app and restoring only app using titanium backup works.

Except from OT, I've been testing the use of v6 supercharger on 9/14 and it seems to solve the memory leak problem (I suppose now that was the cause of the freezes). When I'll be sure I'm posting my solution to the issue.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Punkiderma:
sorry for this little OT, but I think only here I can find some help...

Again, my data partition got corrupted.

Wanted to try another rom, so I did a backup (successful) and then I wipe system(ext4), cache (f2fs) and data (f2fs). Wiping data takes a lot of time, usually it took some seconds more but not minutes.

So i try do to "repair filesystem", and data is the only partition where this fails.

Now I'll try to flash my backup from fastboot...

[MENTION=4544860]osm0sis[/MENTION] , could the cause of this be the fact that slimrom (the rom I'm using) has that additional line to mount /data inside updater-script? Obviously, I modified it to mount /data as f2fs, but maybe, since it isn't officialy supported, still cause problems.

The phone worked normally, the only issue I've got is this, started when I wanted to wipe from recovery.

Thanks a lot

EDIT: I also noticed that TWRP created a data.f2fs.win000 and a data.f2fs.win001 files, instead of a .win files like it should? Anyone has idea why?
[Samsung Galaxy Nexus] mrgnex:
I have this issue too and I'm using fancy.
[Samsung Galaxy Nexus] osm0sis:
Filenaming is normal, data is huge and files can't be larger than 1gb so it splits them. Editing the script in Slim should be sufficient. No idea what repair does, formatting should fix/skip any corrupt/bad sectors if they somehow exist so that's all I'd bother with.
[Samsung Galaxy Nexus] Reinvented:
Gotta say dude, I'm impressed.. but also not surprised at these stats because your work, by default, never disappoints.

(and yes, I know.. only ~1 hour of screen-on time :P)
[Samsung Galaxy Nexus] Ashtrix:
I'm also on slim and no probs so far regarding the wipe/repair FS using full f2fs OR /sys on ext4 and rest f2fs...:good:
[Samsung Galaxy Nexus] Jar3112:
So, here I am, after a week testing 9-14 version in conjunction with the v6 supercharger. No problems so far, never had a sigle freeze or lockup, everything is smooth and fast!

I suppose the issue is to be located in dalvik.vm.heapgrowlimit and dalvik.vm.heapsize. By default, cm11 m9 build.prop has 64/256, now after using the superchanger i set 74/148. Maybe that caused the memory leak?

If someone with cm11 is willing to test and confirm this do the following:

-Make a backup (just in case, only system is good to go)

-Open system/build.prop with root explorer's text editor

-Change dalvik.vm.heapgrowlimit value from 64 to 74

-Change dalvik.vm.heapsize value from 256 to 148

-Save changes and reboot.

Then report back so that we can confirm or not the cause of the memory leak!
[Samsung Galaxy Nexus] Punkiderma:
I'll try! Let's see :)
[Samsung Galaxy Nexus] osm0sis:
So that tells us it's a memory issue.. And what you've done could be a good workaround, but it's still something that appeared between 8.30 and 9.4, so it should be able to be fixed. [MENTION=2853378]Nephilim[/MENTION] did the test version resolve anything?
[Samsung Galaxy Nexus] Nephilim:
I haven't had a single reboot or freeze. Just the usual lag on Chrome and Google Navigator. Test build is running great, only changes from stock I've done so far is bump the cpu max freq to 1.3ghz and change the gpu freq to 512.

Sent from my Android 4.4.4 Galaxy Nexus
[Samsung Galaxy Nexus] Punkiderma:
Ok, after almost a day of normal usage, I can say that 9-14 withe the vm tweaks is the smoothest kernel I've tried so far. Even if I have an additional app in memory(started using GMD gestures), is very smooth.

No more lags, freeze or needs to reboot.
[Samsung Galaxy Nexus] Jar3112:
Yay! We did it! :p:p:p

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] kansasboy001:
Could you please list all kernel settings that you changed including the VM tweaks. Because 9-14 has been nothing but freezes for me with nephilms settings or stock.
[Samsung Galaxy Nexus] cujo6801:
While you're waiting

:D

Sent from the "DOG" pound
[Samsung Galaxy Nexus] Punkiderma:
Here! ;)
[Samsung Galaxy Nexus] Punkiderma:
---sorry, triple post! problem with tapatalk. I can't delete it, if someone know how to do it please tell me!
[Samsung Galaxy Nexus] KreNtal:
I have problem with tapatalk too, I'm unable to quote. However is impossible to delete posts on xda, only a moderator or an admin can.
[Samsung Galaxy Nexus] kansasboy001:
What is the v6 superchanger?
[Samsung Galaxy Nexus] Punkiderma:
http://xdaforums.com/showthread.php?t=991276
[Samsung Galaxy Nexus] pianistaPL:
Only for me TWRP 2.8.0.0 unofficial is laggy as hell?
[Samsung Galaxy Nexus] Oehr:
[MENTION=4608636]bsmitty83[/MENTION],

the default voltages are too low for my nexus. i get crashes/reboots from time to time unfortunately. Guess my model isnt as stable as yours.
[Samsung Galaxy Nexus] cmoG530:
It's really laggy for me as well, but it's okay enough to get the job done.
[Samsung Galaxy Nexus] kansasboy001:
What model do you have? Because I have toroplus and also have stability issues with the new voltages. My friend also has issues with his toro.
[Samsung Galaxy Nexus] Oehr:
ive got the regular GSM model maguro. i increased the cpu voltage by 25mV and so far, its stable (no crashes in the last 48 hours)
[Samsung Galaxy Nexus] bsmitty83:
Op updated - all 3 kernels

--updated cleancache and frontswap to linux 3.10

--fixed up a few build-time warnings

--a few minor updates to ARM , mm , futex , interactve , scheduler , oom killer , and ion

I'll be sticking to anykernel2 releases , im not sure what is causing my ramdisk to not boot anymore on certain roms .

I think its because the tuna device tree got refactored , so i think some things are not correct anymore

anyways hope they work ok .

i also left the voltages the same , still a bit underclocked , so if you have issues with reboots , try increasing the voltages and all should be well

I've actually been able to u/c more without issues .

let me know if/how they are working :silly:
[Samsung Galaxy Nexus] osm0sis:
What ROMs? They work on Carbon which uses a CM-tree base, so generally if there are going to be problems I should be seeing them. :confused:

Edit: Okay I take that back.. 9.22 is not working on Carbon (hangs at the Google logo), at least not when combined with the ramdisk which does work on 9.14.. [MENTION=4608636]bsmitty83[/MENTION] this sort of rules out the ramdisk as being the actual problem, though. :eek:
[Samsung Galaxy Nexus] pianistaPL:
Thank you for the update :) I'm just curious - are you using the newest version of Hyper governor? I'm asking because i like this gov and if there are any updates for this, it would be nice :)
[Samsung Galaxy Nexus] omniatic:
Just flashed the 9.22 Dirty, and it hung at the Google logo. Had to pull the battery, so I can't get you any logs. Back to 9.10 for now...
[Samsung Galaxy Nexus] Unzitron:
Same issue. Back to the personal build. OmniRom, dirtyvak2.
[Samsung Galaxy Nexus] Unzitron:
Sorry, Tapatalk f***in up. 2x post.
[Samsung Galaxy Nexus] aliesz:
Which version of these 3 versions of DirtyV kernel is better to use?!
[Samsung Galaxy Nexus] osm0sis:
SmittyV is less stable right now as Smitty continues to work on zram. DirtyV or -SR are both good choices.
[Samsung Galaxy Nexus] bsmitty83:
SmittyV is quite stable again as I fixed cleancache .
[Samsung Galaxy Nexus] bsmitty83:
And I am going to redo the dirtys , smittyV boots for sure , but the other 2 I need to recompile . gimme a few [emoji106]
[Samsung Galaxy Nexus] osm0sis:
Ah good to know! What ROMs were you seeing issues with though?
[Samsung Galaxy Nexus] bsmitty83:
Vanir , none else that I know of
[Samsung Galaxy Nexus] osm0sis:
Thanks for letting me know. I'll figure out why by this evening. :good:
[Samsung Galaxy Nexus] gabrielss:
I'm also having freezes and reboots on maguro. Which voltages have you increase to solve it? MPU?

Thanks!
[Samsung Galaxy Nexus] Oehr:
only cpu voltages at their different states. nothing else. though keep in mind, no SoC is identical. some are more stable than others.
[Samsung Galaxy Nexus] msli:
hello guys!!thnx for all the efford you put in our 3 years old baby :)i wanna ask you if busshers and nephilims settings are still viable in our phone or after all the updates i should try new governor/scheduler etc..thnx
[Samsung Galaxy Nexus] bsmitty83:
OK I updated the op again , lol , all 3 should be good to go now . there were 2 commits I needed to revert . give em a try .
[Samsung Galaxy Nexus] GilGameshn1:
Wow ... Thanks man . smooth . buttery . ????
[Samsung Galaxy Nexus] cujo6801:
Make Me!!! :mad:

Sent from the "DOG" pound
[Samsung Galaxy Nexus] Punkiderma:
do we still need to do changes in build.prop about vm memory management?
[Samsung Galaxy Nexus] bsmitty83:
I don't think so , I think I fixed that problem , so I'd say no , but if its working ok for you there's nothing wrong with tweaking those settings . I really don't mess with tunables on the releases . I think its more personal preference than anything .
[Samsung Galaxy Nexus] sgspluss:
So just as newbe about this kernel...

If i flash DirtyV-Ak2-9.22.14 don't need to change anything, just flash and be happy right?
[Samsung Galaxy Nexus] bsmitty83:
Right . should be ok out of the box
[Samsung Galaxy Nexus] sgspluss:
Perfect, then let me try out your kernel.

Changes looks pretty interessting ;)

Soon will give an feedback...

EDIT:

First impression, fast as expect... :good:

It's recomended to set the min cpu fequenz lower (from 350Mhz to 230 Mhz) for saving more battery in standby?
[Samsung Galaxy Nexus] bsmitty83:
A lot of people do , but how much savings it gives setting it to 230mhz is questionable to me .
[Samsung Galaxy Nexus] sgspluss:
Yeah thats true... let try out 350Mhz if not enought then will try 230Mhz.

Just thought it was any recomanded value, but looks like governor or scheduler, everyone have his own favourite ;)
[Samsung Galaxy Nexus] osm0sis:
Someone on Vanir try this to see if it'll boot?

[ Attachment removed ]
[Samsung Galaxy Nexus] montbazon:
Is there no one experience the boot problem?

I'm on cm11. My gnex stuck at Google boot image.
[Samsung Galaxy Nexus] sgspluss:
No Problems on CM11 M10!

Flashed DirtyV-Ak2-9.22.14 and it works pretty good :good:
[Samsung Galaxy Nexus] GilGameshn1:
Dirty flash ROM and flash kernel . could help .
[Samsung Galaxy Nexus] Oehr:
boots for me. try this: go in recovery, shut down phone and then try booting it again.
[Samsung Galaxy Nexus] sgspluss:
[MENTION=4608636]bsmitty83[/MENTION], just one quick question again...

Saw your DirtyV offers 738MB of Ram while franco.Kernel offers 744MB (6MB useable Ram more), i know it's not the world but is it possible to get also here the 6MB of useable Ram more?
[Samsung Galaxy Nexus] omniatic:
No problems on CM11 M9. Only hitch was I had to downgrade (sigh) Touchcontrol to 1.8.5. Otherwise, very smooth and fast.

Sent from my SM-P605V
[Samsung Galaxy Nexus] dbt816:
Having issues on 9-22 with the screen not turning back on when I try to unlock with the power button. The device seems to be running fine, but dmesg is totally packed full of these:

<3>[ 7586.901336] omapdss DISPC error: SYNC_LOST, disabling LCD

<3>[ 7586.901367] omapdss DISPC error: First SYNC_LOST.. ignoring

The "disabling LCD" part sounds bad ;)
[Samsung Galaxy Nexus] bsmitty83:
Sometimes I find that happening and I clear trickster mod or synapse , and if that doesn't clear it , a cache wipe in recovery usually dose it . it seems to happen when something borks the kernel settings . I haven't seen any sync errors on my phone yet , ive seen it in the past but nothing with this kernel yet .
[Samsung Galaxy Nexus] playenball:
Im on Vanir Nightly from 09202014 and it is booting just fine. I dirty flashed the rom and then the kernel.
[Samsung Galaxy Nexus] osm0sis:
[MENTION=4608636]bsmitty83[/MENTION] seems like it's just you still, brother. Nothing wrong with the ramdisk. :confused: :eek:
[Samsung Galaxy Nexus] bsmitty83:
Strange right ? I couldn't get it to boot on vanir for anything , I tried many times , many different ways . idk
[Samsung Galaxy Nexus] montbazon:
I always did that when i update kernel.

I tried to delete and redownload zip.

Now It works.

Thanks for info, guys.

Btw damn mosquito woke me up too early.
[Samsung Galaxy Nexus] szale9001:
Not to add to the list :p but I have been having a new problem in 9-22. I use the GNex pogo dock to charge my phone so when it's in there it daydreams the clock app. On 9-22, if I leave it in there for more than about an hour it hard locks and I have to pull the battery.

Leading up to that I can tell when it is going to happen because the clock slows down by a minute or two before the device freezes completely. Definitely a new problem for me and one that used to happen on some of the recent Fancy kernels I tried. Anything that might be causing this? I can't get any decent logs because of the battery pull but I tried clearing cache/dalvik just to cover my bases with no luck. Definitely didn't happen on 9-14, but I am going to revert now and try it to be sure.
[Samsung Galaxy Nexus] bsmitty83:
Wow someone actually owns a pogo ? Lol I wanted one but couldn't find one for under 100$ . I'm sure its something , without a dmsg , its basically I best guess on what it is

I'll look at some things and see if I can fix that for you . if you feel like it , can you pull a dmsg while its on the dock for like 5min ? I'm curious what it even looks like in a dmsg .

No worries on the growing list , this is DirtyV for a reason [emoji6]
[Samsung Galaxy Nexus] szale9001:
Lol yes, we do exist and yes, it was crazy expensive. But I got so used to using my phone as my alarm clock with my OG Droid and then my T-Bolt that I had to do it heh heh. I will try out 9-22 on the dock again and pull a dmesg for you. Hopefully it'll turn something up, and thanks for the help! Toro, running Shiny 4.4 on F2FS btw.
[Samsung Galaxy Nexus] krweby:
Been getting a lot rebooting on 9/22 when the screen is off for long periods. I've bumped the voltages up by two increments and it still hasn't helped.
[Samsung Galaxy Nexus] szale9001:
Ok, went back to 9-22 and set her on the dock for 10 minutes. I can post the entire dmesg if you want, but the entire thing I pulled was one line over and over.

This:

<3>[ 1248.373626] omap_temp_sensor_enable:get sync failed

Obviously the time code changed but it is that line over and over. In fact, as I am typing this, I am refreshing dmesg on the shell and it is still spamming that line again and again.

Sooo, lol, not really sure what to do next so I will wait to hear from you. Also, worth noting, I lowered the thermal throttle to 70C (I usually do this so its not new), but even still the phone feels warmer than usual after being in the dock.
[Samsung Galaxy Nexus] bsmitty83:
Interesting .. That's definitely new and I really think I know what it is . thanks dude , you'll be receiving a test kernel shortly [emoji6]