yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] creeve4:
I tried using SW decoding, which was much better than HW and HW+, but it was still somewhat choppy.

Where did you find the custom codecs?
[Samsung Galaxy Nexus] pagratios:
I use TCP westwood, I/O sioplus with 768 buffer and ondemandplus governor
[Samsung Galaxy Nexus] ashclepdia:
yea i have been using MX for a LONG time now, and it can also depend on what files you are playing.

i have it set to prefer to use HW decoding when streaming videos if possible ( hw+ seems to not cache/buffer the stream at ALL...where as HW or SW will.) and I've also played with many of the other settings also(like allowing two cores... it's in decoder settings)

just go into decoder settings, all the way on bottom of that screen there is a button that links to the xda thread with instructions/info on a custom codec download&use. gnex needs the armV7neon one I'm pretty sure
[Samsung Galaxy Nexus] thomstrack:
After making this change (in the quote above) and restart my Gnex was tavado the boot animation. I tried to flash the stock kernel but nothing worked. I had to reinstall the rom (in my case, the stock). I do not know what happened, I'm just bringing the story here.

Anything done in custom recovery (TWRP), even a backup before restarting it alerts the user root permições were lost and asks to fix, then everything works perfectly.

But my question is: Is this normal? It is a problem of SuperSU? It is a problem of the kernel? Or something alien?

Now, everything working perfectly, no any app crashes.

The extra RAM greatly improved the performance in general and especially multitasking. :laugh:

The best kernel for Galaxy Nexus! :victory:
[Samsung Galaxy Nexus] Ashtrix:
Yep, but vlc's decoder's giving me choppy 1080p playback...:(
[Samsung Galaxy Nexus] motorazrv3:
Members, as already mentioned not every 1080p is the same. The x264 codec offers so many options how to encode a video. If you use heavy settings while encoding you need heavy power for encoding.

Keep in mind.

Gesendet von meinem Galaxy Nexus mit Tapatalk 4
[Samsung Galaxy Nexus] coolek33:
What kind of problem with 1080p playback do U have guys? Im on r42 big and it works with build in player and with mx (hw+) on slimbean.
[Samsung Galaxy Nexus] amd-dude:
With r42 BigMem I am getting heavy battery drain with SlimRom Build 1. Deep sleep is working as indicated by cpuspy, but the phone is always warm to the touch and even with screen off, battery drains as if in use. Did clean flashes along with wiping every single thing besides the SD card.
[Samsung Galaxy Nexus] -Jesco-:
trust me you don't have to pull logs , chrome 30 is known to restart devices a fix is already in place by the chrome team
[Samsung Galaxy Nexus] Blackcrx:
Same setup as you and it seems to be good for me. 9hrs up time, 2:15 screen time. 42% remaining.

But I'm also underclocked to 192-1036
[Samsung Galaxy Nexus] amd-dude:
Hum, did you flash the kernel after the ROM loaded up, I think that maybe a mistake I made. Flashed ROM, then Gapps and Kernel all at the same time. Maybe I should flash ROM and gapps, let the phone settle then clear the caches and flash the kernel. I know it's not the ROM cause right now I just flashed Build 1 with stock kernel and it is working normally.
[Samsung Galaxy Nexus] Blackcrx:
Flashed it exactly the same as you. ROM, GApps, extras, fancy.

Might want to give it a few battery charge cycles.
[Samsung Galaxy Nexus] coolek33:
Same here. No heat up. Great kernel. Flashed: rom, gapps, photosphere and fancy.
[Samsung Galaxy Nexus] amd-dude:
Looks like my phone went wacko for a while, just flashed fancy again and it seems to be working :S No heat up and battery is not draining as it was before. With that being said, Fancy r42 BigMem and Slimbean Build 1 (4.3) is a sweet combo, really smooth and I have never seen my phone with 340mb of free RAM, pretty sweet.
[Samsung Galaxy Nexus] wavedashdoc:
O...

Anyone know why cfq io scheduler on Fancy crashes the phone?
[Samsung Galaxy Nexus] Pkt_Lnt:
[MENTION=4615478]boype[/MENTION] fixed it, or at least tried, in a couple releases of test kernels back from current ones. It works fine for me in r42-ext and r42-big. Pretty sure that is old information.

http://xdaforums.com/showpost.php?p=45235154&postcount=5696

http://xdaforums.com/showpost.php?p=45551729&postcount=6100
[Samsung Galaxy Nexus] fux0r99:
I'm getting 560mb free ram with fancy r42 ex kernel on pac-man rom.
[Samsung Galaxy Nexus] akash3656:
Sounds pretty normal for a clean flash. The phone is doing is syncing up with Google, performing TRIM and other background task right after a clean flash. Just give your phone a reboot and charge it up. It should be fine after that. Or the ROM is at fault.

Edit: Might also be the fact that your signal is poor and the phone is using more power to cling on to the weak signal. Something my phone does all the time when I'm not at home.
[Samsung Galaxy Nexus] boype:
It is possible that your camera subsystem crashed (that's what may happen with bigmem...). You can tell if you open an app that uses the camera and it doesn't work. In that case, The phone gets warm and stays that way. Reboot solves this, of course.

I acknowledge there's a problem with cfq. However, the issue is caused by something else than cfq itself... It's kind of hard to track down, but I'm on it
[Samsung Galaxy Nexus] amd-dude:
[MENTION=4615478]boype[/MENTION] I did not launch the camera or even an app that calls the camera and I did do multiple reboots. For some strange reason it is working well now, even when I launch the camera. I just changed the order of flashing. Did ROM, gapps let them start up first and settle then rebooted and flashed the kernel, all seems fine now, really weird. Thanks for the awesome kernel.
[Samsung Galaxy Nexus] creeve4:
When using the headphone volume boost, every music app I have tried stops playing every 15 to 30 seconds. Is this a known bug?
[Samsung Galaxy Nexus] corwin42:
This is a known problem with volume boost. Try to set it to 2 or 1 as maximum.

Gesendet von meinem Galaxy Nexus mit Tapatalk 4
[Samsung Galaxy Nexus] Pkt_Lnt:
I listen to music for over an hour each, morning and night on my bike/bus commute, with boost at 3 with no issues.
[Samsung Galaxy Nexus] ophidia:
Going to try this one out and see if it fixes up my laggy-as-hell phone.
[Samsung Galaxy Nexus] :
if You flashed lot of Roms, cleaning with toolkit (factoy image) and then flash new rom can solve this lags... ,-)

----------

gonna try 42 tomorrow, finally :fingers-crossed:
[Samsung Galaxy Nexus] masteryx:
Volume boost +3

Regarding the volume boost, I noticed this:

- with my headphones I can turn the volume all the way up (past the safety warning) and there's no problem, ever, with volume boost set to 3.

- with a pair of external speakers, or with the phone connected via 3.5mm jack to my car's stereo AUX IN, the music always cuts for volume boost set at 3 if the volume goes past a certain value (approx. 50%). With volume boost set at 2 I can reach about 80% max volume and with volume boost set at 1 I can go all the way up.

My conclusion is that this must have something to do with the output power of the stereo plug. The bigger the power draw through the plug, the lower the volume threshold at which the music stops.

Also, not strictly a Fancy kernel problem. I had the same on Lean, so this is definitely hardware related.
[Samsung Galaxy Nexus] Utkarsh-ezzo:
yes when you set boost to 3 and connect headset it works good but when you connect speaker system, the music playback stops randomly
[Samsung Galaxy Nexus] fayosi:
This kernel is soo frustrating, can't even cope with the camera this happens frequently. With the minimum times of twice a day.
[Samsung Galaxy Nexus] thomstrack:
No any issues here with stock rom.

Rom maybe?
[Samsung Galaxy Nexus] Pkt_Lnt:
I am running the same ROM he is with no issues on any of [MENTION=4615478]boype[/MENTION] kernels. I did have camera issues on the test bigmem kernels that were not built by boype.
[Samsung Galaxy Nexus] mrdevil_25:
dont use the bigmem version.....
[Samsung Galaxy Nexus] nitsua98:
It could be a hardware problem with your camera connector.
[Samsung Galaxy Nexus] abhishek93:
try different kernel then.. ;):rolleyes: if the problem is still there than it is hardware which is not working right..
[Samsung Galaxy Nexus] JohnstonF:
Psx v6 + fancy r42 bigmem = working like a boss!!

No issues whatsoever
[Samsung Galaxy Nexus] pcphobic:
Can share the download link to PSX ROM for Galaxy Nexus?
[Samsung Galaxy Nexus] Seraz007:
http://www.androidfilehost.com/?a=show&w=files&flid=7409
[Samsung Galaxy Nexus] JohnstonF:
It's mainly dev'd for N4 but the dev also built for Gnex

http://xdaforums.com/showthread.php?t=2392624
[Samsung Galaxy Nexus] pcphobic:
[MENTION=4982044]Seraz007[/MENTION]

thanks for sharing :)
[Samsung Galaxy Nexus] boype:
New release soon

Hi everyone,

Linux Kernel 3.0.70 is currently being reviewed and will hopefully soon be merged to the kernel.org repo.

I have been spending quite some time to smooth-out the user experience for the next release even more :good:

Also, the permission problem with the /sdcard/fuss directory has been sorted out.

So stay tuned :>
[Samsung Galaxy Nexus] iferlive:
Re: [KERNEL][4.2.x] Fancy Kernel (r10) (MAR-15-2013)

Boype could you try to implement verbose boot? It would be a great feature..useless but great for eyecandy.
[Samsung Galaxy Nexus] jjhrrsn:
Re: [KERNEL][4.2.x] Fancy Kernel (r10) (MAR-15-2013)

Oh boy I can't wait
[Samsung Galaxy Nexus] boype:
r11 up

Hey everyone,

r11 is available from the OP. Changes are as follows:

updated Linux version to 3.0.70

tweaked ondemandplus for more smoothness and modified downscaling logic a bit

added custom lowmemorykiller values for better multitasking

reduced readahead kbytes to 896 (snappier feeling but same i/o performance)

enabled sync options in kernel config

moved fuss / reflash to /data/fuss so they won't mess up the /sdcard/fuss folder's permissions. Also created symlinks for fuss and reflash (all you need to type in terminal is 'fuss' or 'reflash')

For those still having problems with the /sdcard/fuss folder's permissions (can't delete or write to it) because r10 screwed it up, here's a permission fix which has to be flashed from CWM / TWRP:

http://boypetersen.de/fancykernel/sd_fuss-folder_permission_fix.zip

Best regards
[Samsung Galaxy Nexus] jjhrrsn:
Re: [KERNEL][4.2.x] Fancy Kernel (r11) (MAR-21-2013)

Thanks
[Samsung Galaxy Nexus] mpokwsths:
Nice work dude!

r11 feel good.

For better multitasking have you consider adding ZRAM? It is certainly effective (as I have seen from other kernels).
[Samsung Galaxy Nexus] jv2543:
does this kernel use anykernel, so it can work with all custom roms?

I keep getting bootlooped when trying to use this kernel on the new BAMF rom and someone posted that this might be the issue
[Samsung Galaxy Nexus] pageniao:
Re: [KERNEL][4.2.x] Fancy Kernel (r11) (MAR-21-2013)

+1
[Samsung Galaxy Nexus] 123egg:
Re: [KERNEL][4.2.x] Fancy Kernel (r11) (MAR-21-2013)

Loved the performance of r11. Thx for the amazing work.

BTW just a little suggestion: WiFi drivers from 3.4 kernel is quite good imo, you might want to take a look and try adding them to the extended version?

And Zram is a good idea too
[Samsung Galaxy Nexus] pageniao:
Re: [KERNEL][4.2.x] Fancy Kernel (r11) (MAR-21-2013)

boype thanks your good job

new kernel so far so good

and could you add zram support in ext version?:)
[Samsung Galaxy Nexus] momomok:
weird, the first boot after flashing r11 the buffer is still at 2048...?
[Samsung Galaxy Nexus] pageniao:
Re: [KERNEL][4.2.x] Fancy Kernel (r11) (MAR-21-2013)

896
[Samsung Galaxy Nexus] gwindlord:
Remember that zram helps on devices with a lack of memory - and I cannot remember if I ever had any lack of memory on maguro (I do not check digits of free memory and care of them). But I do remember synthetic tests, which

always

became lower with zram turned on without any visible effect (if you know any operations, where zram gives some gain, could you please share your experience?..). It's up to boype for sure, but I just do not understand, what for zram could be used on our device.
[Samsung Galaxy Nexus] Hoochie_Coochie:
Re: [KERNEL][4.2.x] Fancy Kernel (r11) (MAR-21-2013)

Mine too, just done a fresh clean install on vanir
[Samsung Galaxy Nexus] bolanrox:
maybe it is in your vanir config file? were you on Vanir prior?

---------- Post added at 07:40 AM ---------- Previous post was at 07:34 AM ----------

People running kernels with the 3.4 drivers are liking them, but the one downside I know of is that it kills WEP log ins. (you would need to update your security to WPA etc) is anyone still using WEP? I know i needed to update everything when i got a windows 7 because it did not support WEP any more..
[Samsung Galaxy Nexus] sebby d:
Flashed r11 last night. First time using this kernel and I have got to say so far I'm loving it. Very smooth, no lag at all. Time to see how it handles on a full day usage. Hoping my phone likes it. Thanks dev!
[Samsung Galaxy Nexus] gwindlord:
Maybe TricksterMOD with enabled "Set on boot" or some scripts?..
[Samsung Galaxy Nexus] boype:
About zRAM: I am not very fond of the whole concept. What I dislike is that the part of the RAM that is reserved for the compressed RAM is not available for uncompressed stuff anymore. So even though without zRAM there might be still be some RAM left to store stuff in, with zRAM enabled the stuff has to be compressed now. Due to the CPU load caused by the compressing / uncompressing processes, energy consumption may increase. Of course, with zRAM, there's a little more RAM available - but in my opinion RAM is no bottleneck on the Galaxy Nexus.

Anyhow: If I enabled zRAM support in the kernel, would it be possible to switch it on/off from within the ROM? I'm asking because I don't have much experience with zRAM.
[Samsung Galaxy Nexus] gwindlord:
Trickster and CM ROMs (and maybe some CM-like ones) should have these performance options.
[Samsung Galaxy Nexus] boype:
So I guess it won't hurt to have the option to enable it if you want to. Of course it will be disabled by default :)
[Samsung Galaxy Nexus] madhavs:
Amazing battery life with r 42 big and it's very snappy as well
[Samsung Galaxy Nexus] pcphobic:
Have not seen the Dev's Galaxy Nexus thread around here.
[Samsung Galaxy Nexus] TnK8iD:
Did you calibrate the battery with some app??
[Samsung Galaxy Nexus] JohnstonF:
He doesn't maintain separate threads, just one in the N4 forums

check the download links for the Rom and PSX gapps
[Samsung Galaxy Nexus] madhavs:
No neither kernel too all default settings
[Samsung Galaxy Nexus] fayosi:
I didn't use the big memory version, I was on the normal one with ext.

I'm on Franco kernel now and my camera is working perfectly...
[Samsung Galaxy Nexus] abhishek93:
which rom?
[Samsung Galaxy Nexus] madhavs:
it's BeanStalk 4.3.07 dated 20130831
[Samsung Galaxy Nexus] SoftWord:
[MENTION=4615478]boype[/MENTION] can you tell new which toolchain have you used? And eabi or androideabi version?

Inviato dal mio Galaxy Nexus usando Tapatalk 4
[Samsung Galaxy Nexus] kevtrysmoddin:
Could someone tell me if 720p recording works with the bigmem version of this kernel? TIA
[Samsung Galaxy Nexus] andreas__:
works perfectly fine :)

sent from my nexus
[Samsung Galaxy Nexus] boype:
pre43-1 (bigmem)

Hi again,

I just uploaded pre43-1. I am optimistic I found the reason for the freezes and eliminated it. But let's see. Here's the changelog:

defconfig: disable RCU boost again (I figure this was the cause for the reboots)

re-introduce 'ARM: 7746/1: mm: lazy cache flushing on non-mapped pages' (as it was not the cause for reboots)

a couple of WiFi driver updates from Google repo

many, many, many SYNC-mode updates from Google repo

enabled SW_SYNC in defconfig (enables a framework for synchronization between multiple drivers; may improve smoothness)

a couple of interactive governor updates from Google repo

opp4xxx_data.c / ABB: fix OPP_TURBO's ABB type

ARM: 6998/2: kernel: use proper memory barriers for bitops

a few other updates from Google repo

http://boypetersen.de/fancykernel43/tst/fancy_kernel-tuna-4.3-pre43-1-big.zip

Have fun and please report if the reboots are gone
[Samsung Galaxy Nexus] stuffynet:
Testing now. TWRP asked for root fix. Looks like there is no problem with root after fix and reboot.

THX
[Samsung Galaxy Nexus] ahmedsaber20005:
What is the difference between Bigmem Version and normal version and Pre Version ??
[Samsung Galaxy Nexus] elia222:
Everything seems to work fine on crDroid build 10.

TWRP didn't ask to fix root for me, I'll report if I find issues.
[Samsung Galaxy Nexus] kevtrysmoddin:
I think a flash is in order lol
[Samsung Galaxy Nexus] sajty:
"normal" should be stable,"pre" is like beta version before "normal" version.But all versions are stable,so it doesnt matter.
[Samsung Galaxy Nexus] boype:
For differences between std, ext and big versions, check the OP.

The pre-versions are just versions that are uploaded for testing before (=previous) the next major is released (=release)
[Samsung Galaxy Nexus] kevtrysmoddin:
Wow just flashed the Big version and my phone is like a new device again great work [MENTION=4615478]boype[/MENTION]
[Samsung Galaxy Nexus] Pkt_Lnt:
Does this address the CFQ instability do you think? I'll try anyway, just wondered.
[Samsung Galaxy Nexus] boype:
Yes, exactly. There have also been reports of instabilities with other i/o schedulers - I hope this fixes them too.

I myself could only reproduce instabilities with CFQ.
[Samsung Galaxy Nexus] xxSAKISxx:
Just a silly question. i am running r42-big atm. the pre43-1 will bring back the 1080hd recording if i flash it? ty for the grate kernel.
[Samsung Galaxy Nexus] 1haumann1:
no....pre43-1 is bigmem also

swyped from my maguro
[Samsung Galaxy Nexus] wavedashdoc:
With cfq, interactive and OC 1536 I got a freeze right away while in Trickster.
[Samsung Galaxy Nexus] Sik-1:
Maybe your phone can't handle oc1536, try cfq on stock first and see if u still get a freeze

U can also try +50mv on oc1536 voltages
[Samsung Galaxy Nexus] wavedashdoc:
I was thinking the same thing but I got a random reboot before with 42 on stock settings. Plus I ran over clock up to 1.6 on Franco. Ran 1.5 daily for months.

To keep testing I've changed everything to Franco settings (governor control, OC CPU, Fsync off, GPU 512 and SR off) except using cfq. So far so good.
[Samsung Galaxy Nexus] boype:
pre43-1 is supposed to fix the already known and acknowledged reboots of r42 and earlier. Have you tried it? And if no, please try without overclock.

And if the phone freezes right away when you put on a high overclock, that's pretty obviously a voltage thing IMO. Franco has set up higher voltages for overclocking steps, which is why you could run those frequencies stable.
[Samsung Galaxy Nexus] Blackcrx:
Awesome work as always. But I've never had reboots with r42 or any of your kernels. I'm also underclocked 192-1036 and under voltaged
[Samsung Galaxy Nexus] nikosrs4:
Is this something that I have to worry about? :p

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] agritux:
Hey boype! r42 is great for me. Thanks.

One idea: maybe you can add an update checker for fancy updater in it? Not only kernel but also apk?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] romeyjdogg:
Are you guys seeing a tangible difference between bigmem and regular kernals? My regular extended version is flying pretty solid. Didn't know if it would be worth switching over to big
[Samsung Galaxy Nexus] BOY_:
Yes.
[Samsung Galaxy Nexus] Pkt_Lnt:
The no or unknown or poor signal, yes.
[Samsung Galaxy Nexus] Culex316:
Dude, the bigmem version (plus fancy kernel's overall snappiness) has made me want to stick to my current phone much longer than originally intended, that extra 60+MB of free RAM makes a TREMENDOUS difference in overall performance, I can now use the Chrome browser and other memory-hungry apps without having the phone lag due to killing/reloading processes in the background.
[Samsung Galaxy Nexus] flybass:
I think the extra ram has helped fix the log uptime lag issues with the device. I can't rave enough about this kernel.
[Samsung Galaxy Nexus] pkgnex:
The "bigmem" fancy kernel is the first kernel that has ever equaled franco's kernels performance on my phone... and the extra RAM makes a huge difference in app-switching fluidity and overall performance, as others have also noted.

If you're not on the bigmem version yet... DO IT!
[Samsung Galaxy Nexus] Doublewise:
I think, imho, we need a procedure and isolate every user preferred setting to test kernel. First, try kernel with stock setting for at least 2 days. Report result found in this stage. Then change one setting as user preference. Only one. Especially the one that usually responsible for freeze or crash e.g. governor, clock speed etc.Try it for 2 days. Then continue change other setting but revert the first changed to stock and so on. Maybe this need a long time or shorter if support by few testers. This will easier for dev to track down the culprit.
[Samsung Galaxy Nexus] ashclepdia:
I've been trying this kernel a lot lately. been having lock up issues but haven't reported anything cuz im the type that tweaks the heck outta it lol.

i use my device like crazy too. i think I'm gonna run with your advice here. I'll report back with anything i find. this has become one of my fav kernels to run straight stock actually, can't recall any issue until i try to tweak it some :D
[Samsung Galaxy Nexus] Ci-Fi:
+1

I'm considering sticking with the GNex another year because this BIGMEM kernel has made my phone so quick and smooth.
[Samsung Galaxy Nexus] wavedashdoc:
Awesome work. Been running this for the last 6 hours with OC no crashes! Amazing performance. 43 is stable
[Samsung Galaxy Nexus] pkgnex:
I agree 43 seems at least as stable as 42. I was having some reboots on 42, but after I turned off Smart Reflex, left all voltages otherwise unchanged, and changed to the tuned Deadline scheduler rather than CFQ, Noop, or SIOplus, I had no more problems with 42. Still no problems with 43... but I haven't tried any undervolting or non-Deadline schedulers yet, either. I do overclock to the 1344 slot, and have had no problems at that level with the stock voltages in either 42 or 43.

IMHO, the G-Nex should be stable to the ~1500 slot if the voltage is set right. I was able to run faster than this with Franco (but rarely did), and if my memory serves, the processor was actually designed for 1.5 GHz, but was down-clocked to 1.2 GHz in the G-Nex. I've never heard of anyone having a G-Nex that wouldn't run at 1500 MHz unless they had screwed up their voltages or something else was going on.
[Samsung Galaxy Nexus] BOY_:
Boyle, pre43 is running great but I noticed I'm using more RAM than on 42. Not sure what changed. Still kickin butt though!
[Samsung Galaxy Nexus] rene_r:
Maybe a dumb question, but how can I disable smart reflex?

Thx in advance
[Samsung Galaxy Nexus] Pkt_Lnt:
Get Trickster, slide from ON to OFF.
[Samsung Galaxy Nexus] Jar3112:
Well, in my case I actually CAN reach 1500 Mhz, but at that clock my phone overheats much faster, leading to reboot.

On 1400 it heats much, but not enough to reboot, only stable clock for me is 1344 step

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Utkarsh-ezzo:
one more noob ques,,

what is smart reflex???
[Samsung Galaxy Nexus] wasdf:
automatic lower voltage by a algorithm

(For algorithm details, Google is your friend)
[Samsung Galaxy Nexus] Pkt_Lnt:
LMGTFY
[Samsung Galaxy Nexus] Utkarsh-ezzo:
you are so smart, I am jealous,

P.S.

sorry for not searching before posting...
[Samsung Galaxy Nexus] TnK8iD:
:laugh::laugh::laugh::laugh:
[Samsung Galaxy Nexus] pcphobic:
Here is a very good explanation - http://xdaforums.com/showthread.php?t=2211675

---------- Post added at 04:46 PM ---------- Previous post was at 04:40 PM ----------

[MENTION=4778385]lightingcloud[/MENTION]

Here is a very good article about what is Smartreflex and how it works. Long story short, we should just leave it to ON (enabled).

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