yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] EnricoTFYKD:
Just came here from franco because I was intrigued about bigmem, and knowing that this kernel is as stable as his, I wanted to give a go. Right now everything looks perfect and smooth on pre-r43... Awesome! I will report back later if something goes weird.

BTW, I am using my old, trusted settings: franco's default interactive settings, disabled SR, OC to 1344 and slight UV (voltages that I have been running for 6+ months with no hiccups nor reboots).
[Samsung Galaxy Nexus] mtallon:
FSYNC settings

Hi!

To solve lag problems on my GNEX, FSYNS must be set ON or OFF???

Thank you,

Marco
[Samsung Galaxy Nexus] abhishek93:
i know it have been discussed earlier but i am facing this problem again with google services.. any solution?? :confused::(
[Samsung Galaxy Nexus] qu4nd:
In general, FSYNC off increases IO speed. But I don't think this may solve overall lags...
[Samsung Galaxy Nexus] mtallon:
Thank you!

actually I use LagFix but it doesn't solve my problems, so I decided to try Fancy Kernel that has FSYNC option. Anyway the only solutions that solve temporarily the problem (about a month) is to periodically do:

su

mount -o remount,discard /data

dd if=/dev/zero of=/data/tmp.bin

rm /data/tmp.bin

as described here: http://xdaforums.com/showthread.php?t=2029246
[Samsung Galaxy Nexus] boype:
Update your ROM... In CM10.2, the problem appeared too, but they fixed it some weeks ago.

There's no need to use the lag fix app anymore in Android 4.3, since a similar mechanism is already implemented.

Also, I do not recommend mounting partitions with the discard flag. It slows the system down. If you are not filling / emptying your whole memory once a day or more, I recommend you should neither use lag fix nor discard.

Just a wild guess: Is your file system really full? Because you should leave at least 10% free to avoid slowdowns
[Samsung Galaxy Nexus] mtallon:
Ok so I disable LagFix (it was scheduled to run every night!!!).

Now it seems fast and stable since I did the procedure I wrote before. If lags return, I will try to set FSYNC to OFF.

My file system has always at least 3.5 GB of free space.
[Samsung Galaxy Nexus] 7175:
:laugh:Man this latest test kernel is wicked f***in fast with some great battery on carbon and my max sketchyness fa02-ek01-02 radios I mixed a couple hours ago. Ondemandplus frequency response is really optimized. Using stock settings with mps =0, vaux3=2500. LTE was staying locked on pretty nice even at 110dBm. Really impressed.

Leave fsync ON!! Turning it off has caused data corruption for me so many as well as many times, basically if you crash or your phone 'halt' reboots with fsync off, there's a good chance you'll be doing a factory reset and a clean install.

If you're getting lag, make sure you got "force gpu rendering" enabled in system settings>>developer options. Much more efficient opposed to CPU rendering and you'll get better battery too most likely. Also make sure you don't have any left over sysctl.conf or init.d kernel scripts from other kernels, i.e. 950iosettings, io queue scripts. I forgot who put it in their signature, but basically you want to flash your ROM again and then kernel each time you flash a different kernel because there are hundreds of settings deep in the sysfs that don't really mix and match well. I've learned this the really hard way spending hours trying to figure out why battery sucks and system is laggy to find out later after browsing /sys/block for hours that rotation=1 and io tweaks tagged along from a previous kernel.. hell
[Samsung Galaxy Nexus] nikosrs4:
That must be false by betterbatterystats cause I have 100% signal strength. I work in the building of my mobile service provider :p

Maybe rom related?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] abhishek93:
i am on cr droid latest build 10, still i am having this issue..
[Samsung Galaxy Nexus] kevtrysmoddin:
What gapps are you using as I too am using this kernel and crdroid 10 using p.a gapps and have no such issue

sent from a pie in space
[Samsung Galaxy Nexus] mtallon:
Ok I leave FSYNC ON :) but in this case is not better to go back to stock kernel? I installed fancy kernel only to try fsync settings....

Anyway, my lags are due to bug of EMMC chip, that's because I told you about lagfix and discard options.
[Samsung Galaxy Nexus] abhishek93:
using CM gapps 20130813..
[Samsung Galaxy Nexus] Jagoflax:
Let's test that famous Kernel ... :cyclops:
[Samsung Galaxy Nexus] kevtrysmoddin:
Try the latest p.a. gapps see if that helps

sent from a pie in space
[Samsung Galaxy Nexus] Gynlemon:
The last crDroid uses the latest sources cyano, so the problem had been fixed earlier ..

My current configuration : crDroid + kernel Fancy (latest test version: pre43-1-big) + Gapps PA no problem .. rather try to check if you have a weather widget in continuous sync with Google services .. check with Better Battery Stats ..
[Samsung Galaxy Nexus] Seraz007:
sorry to quote such an old post :o

but will this work on the latest MIUI v5? :confused::):fingers-crossed:
[Samsung Galaxy Nexus] chinarobin:
to Seraz007

at least on mine. v5 latest.
[Samsung Galaxy Nexus] Seraz007:
thanks :)
[Samsung Galaxy Nexus] sajty:
IMHO "force GPU rendering" will eat more battery than standard CPU processing.
[Samsung Galaxy Nexus] creeve4:
According to the MX Player Dev, the HW video decoding problems on 4.3 for the GNex are kernel related. Also, I still cannot play 720p x264 encoded video with HW decoding using the pre43-1 bigmem version of your kernel (all video players that I have tried say HW decoding not supported). I can play 720p x264 encoded video with HW decoding using the standard and ext versions of your kernel, but playback is very choppy.
[Samsung Galaxy Nexus] Taomyn:
Some apps don't like the setting either with anything from weird display effects to no display at all.
[Samsung Galaxy Nexus] flybass:
for those who were on r42 without any problems, is it worth trying the newest test release?
[Samsung Galaxy Nexus] kevtrysmoddin:
I would say so

sent from a pie in space
[Samsung Galaxy Nexus] madhavs:
yes absolutely no problem what so ever
[Samsung Galaxy Nexus] Prasad:
Pre43-1 working great on my end. Thanks again, [MENTION=4615478]boype[/MENTION]! :)
[Samsung Galaxy Nexus] abhishek93:
Yup just flashed pa.gapps did a clean install.. It might help :thumbup:

I know its on latest cyano sources.. Bdw I'll try to check it with better battery stats :) thanks
[Samsung Galaxy Nexus] Pkt_Lnt:
The ROM does not usually affect the radio, but it is possible; see #5. http://t.co/JYkjnOa7gw
[Samsung Galaxy Nexus] dirtygoldfish:
I think you can ignore the "no or unknown signal" reading in BBS if you were using Wi-Fi the entire time. As far as I've noticed that's indicating whether you're connected to mobile data, so it'll count the entire time you don't have data turned on as having no/unknown signal.
[Samsung Galaxy Nexus] Charmacas:
Hey guys,

I only reported directly to boype so far but this starts to annoy me. I had reboots all the time the last two days. The last_kmsg doesn't give proper information.

My settings were the same as mentioned in my signature but ZRAM activated. I will now test how it's going without ZRAM. Because the reboots did appear with every setting I tried before. Interactive/OnDemandPlus, various RAB, SIOplus/Deadline and also underclocked to 1 GHz.

Did anyone else in here had reboots? Could you please tell me than what settings you had configured? Especially ZRAM should be interesting.

And I am cool with the guys who does not have this issue. But please no comment like: "I don't had it with all the last versions.". ;)
[Samsung Galaxy Nexus] ErivShadow:
Is there any chance to get rid of the update notification? This one often pops up during the day even if there is no update available.
[Samsung Galaxy Nexus] movelbit:
Press and hold in the notification. And select application settings. There you can disable all notifications from that app.

Enviado do meu Galaxy Nexus utilizando Tapatalk 4
[Samsung Galaxy Nexus] zofox:
love this kernel :P it allows me to uv mpu settings to -75/100 but.... has anyone having trouble with 3g connection? i mean it uses lots of battery :silly::silly: and i can't make the phone last more than 5 hours if i connect it to 3g and use it a bit :(
[Samsung Galaxy Nexus] AutomaticFailure27:
I have noticed that screen on and 3g tend to drain faster than other kernels. Something changed from 4.2.2 to 4.3 and my battery life / screen on is almost half of what it used to be
[Samsung Galaxy Nexus] christopherrrg:
I thought I was going crazy, didn't post but those are my symptoms too!
[Samsung Galaxy Nexus] bigknowz:
Battery

Do any of you connect to WEP wifi prior to battery drain. I'm working on that problem.
[Samsung Galaxy Nexus] christopherrrg:
I do normally while at home & leaving to switch to 3G, I find I get disconnected a lot. (While screen off WiFi kicks off, but when I turn it back on it takes forever to reconnect.) Sometimes have to mess with the toggle or reboot.

I've been reading a lot about the nexus 7 factory images having issues with wifi and I know cm likes to add all of the aosp stuff. So I just figured it was that.
[Samsung Galaxy Nexus] Castro27:
No, you're not alone. I've been having reboots ever since r41 when running pcphobic's settings, stock settings (both with ZRAM off) and other I/O - Governor combinations (all that I could try with stock frequencies), with ZRAM both on and off. All of them ended up in random reboots, where some of'em even ended in a bootloop-like state, rebooting the phone a couple of seconds after booting from a previous crash.

Im back on r40 for now with no reboots so far. Is this similar to your situation?

PS: One other thing that is bothering me is that any time that I try to generate the last_kmsg all I get is a "no log found" message.
[Samsung Galaxy Nexus] Culex316:
I'm using a special version of r36 with bigmem and I have undervolted my gpu and this shows up in the dmesg log, should I be worried? (see attached text file)
[Samsung Galaxy Nexus] bigknowz:
Battery

I have bad idle drain (> 5% / hr) after initial connection to WEP even though the phone is in deep sleep ~ 90%. It seems like WEP is borking the cell radio, so I am testing a Tasker fix that toggles Airplane mode after initial WEP connection. Waiting a few more days before drawing conclusions. No such issue when connecting to WPA2.
[Samsung Galaxy Nexus] Charmacas:
Good to hear that I am not alone with this strange problem.

Hmm... After I deactivated ZRAM I got no reboots so far. But we will see what happens.

I got nearly the same experiences as you had. Reboots directly after reboots and sometimes even right after the boot animation appeared. The problem got so big that I had to make my phone new from the scratch because the phone did not want to boot at all.

So another thing I noticed with these reboots is that sometimes after the reboot something seems to go wrong with the mounting I think because I loose my wallpaper and Android just sets it's default one. Also the launcher icons etc are gone for a minute or so. That's just an experience... I don't know if that helps.

If anyone else have problems we described it would be nice if you step into the discussion and write down your own experiences.
[Samsung Galaxy Nexus] Castro27:
Your kernel version and settings are the ones in your sig? I'd like to try your settings to see what happens. As for the mounting, no problems here for now.
[Samsung Galaxy Nexus] Charmacas:
As described in my previous posting I tried various settings. Actually I am using the ones in my signature. The difference to the setting before is that I deactivated ZRAM for now.
[Samsung Galaxy Nexus] Castro27:
OK, I have everything up and running. I'll post the results in a few hours
[Samsung Galaxy Nexus] Charmacas:
So two new reboots while not using ZRAM. Now I try not to undervolt. My settings never caused problems before. I am now using default voltages. Even I don't think it's a voltage problem because the reboot happens also while the booting process.
[Samsung Galaxy Nexus] Castro27:
Could it be rom related?
[Samsung Galaxy Nexus] Charmacas:
Yes it 'could' be.
[Samsung Galaxy Nexus] d0ge01:
report

In r41 row cause me reboot

now in pre43 i'm using interactive / row , undervolted due SR , no one problem, 30+ hours uptime without any single reboot
[Samsung Galaxy Nexus] Technical:
Fancy Updater is just crashing while opening.

I'm tried to delete the data (Applications settings of the phone) but it did not help?

I have internet connection and seems I'm using the latest Fancy Updater version.

The kernel is the 42-big (latest).
[Samsung Galaxy Nexus] cmoG530:
I've kept it stock, besides bumping it up to 1.3. I've never had any reboots with any of the 40 versions so far and I have Z ram on always. Carbon ROM.
[Samsung Galaxy Nexus] AutomaticFailure27:
Nope I got nothing that has WEP, all are WPA2 or whatever it is.
[Samsung Galaxy Nexus] justen7723:
Is bigmem version also ext version??

Edit: nevermind

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] pcphobic:
Ensure that your WiFi is turned off when u are away from any WiFi hotspot.. Or else the phone is constantly trying to search for next available hotspot and not letting your phone go into deep sleep.

Also ensure "Scanning always available" is disabled in your WiFi - Advanced settings. By default this feature is enabled in Android 4.3.
[Samsung Galaxy Nexus] fux0r99:
Fancy updatr app has always crashed unfortunately .
[Samsung Galaxy Nexus] Jar3112:
First of all you should lower your OC (I'm using 1344 as a maximum, which works good). As thermal throttle keeps scaling down the frequency you won't have benefits from keeping it that high.

Then, what frequency are you using for your gpu? It usually isn't a good idea to lower "core" voltages.

And what modified version are you using?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Culex316:
I was using 1228 as a maximum, I was just getting throttled because at the time, I was running a Nintendo DS emulator that always maxes out the CPU.

As for GPU frequency, I am using 384Mhz and using trickstermod, I lowered all voltaged by -25mv as a test and then I started getting those messages.Why shouldn't I undervolt the GPU?

I'm using boype for 4.2.2. (yes, outdated), but a special version that another user posted on this thread that had BIGMEM support, giving me 73MB extra RAM.
[Samsung Galaxy Nexus] gamerman123x:
Pre 43-1-big is really smooth and the performance is great with slim bean stable build 1 and I don't touch my kernel settings I just kept it the way the kernel came and it's really smooth no lag and I uninstalled trickster mod because I don't need it and its fine for me :) :thumbup:
[Samsung Galaxy Nexus] boype:
To those experiencing crashes: are you using the kernel profiles feature in Trickster? Charmacas brought up the idea that this might be related.
[Samsung Galaxy Nexus] Jar3112:
It was my version. I posted another one some days ago, search for it, I made some fixes. If you are using 384 mhz gpu just enable smartreflex

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] cmoG530:
Little off topic,but are there any advantages or disadvantages between using 2.4GHZ or 5GHZ frequency bands?
[Samsung Galaxy Nexus] sajty:
5GHz is newer frequency and not so much used by another electronics.So there should be less possible disturbance.

---------- Post added at 09:10 AM ---------- Previous post was at 09:09 AM ----------

I use profiles and i have never ever had any random reboot on Fancy kernel,never.
[Samsung Galaxy Nexus] Charmacas:
It should only happen if you have saved a profile which had additional frequencies like the normal 900th which is not inside Fancy.
[Samsung Galaxy Nexus] sajty:
Why you are doing this? :D
[Samsung Galaxy Nexus] boype:
Any update on that from your end? Everything stable all of a sudden? This stuff is really bugging me ;)
[Samsung Galaxy Nexus] Fenvarien:
pre43-1-big is running completly stable here. I don't have Trickster - I just use the performance options of CM to set the scheduler to Deadline. Thanks for your hard work boype! :)
[Samsung Galaxy Nexus] bartolinio:
I have the same

I threw out this application
[Samsung Galaxy Nexus] Charmacas:
I would not say it disappeared because I am only running the new configuration since 3 hours.

But so far everything runs great.
[Samsung Galaxy Nexus] _yaz_:
negative! for me, wifi and sync(!) is always on and wifi advanced settings is the stock but the phone goes to deep sleep always when it should. those settings have no such direct and proportional relation to drain as you described.

typical drainy settings are keeping always on the location access and the mobile net in areas where the signal strength is weak a/o not stable. i'd rather suggest to taking care of these settings; turn on if you really need them and use them if the connection is stable and reliable, especially on mobile net. otherwise you may expect sudden extreme drain. compared to these, the consumption of the wifi on/off itself is insignificant.

(i can clearly observe these effects by leaving the town, when i forgot to switch those settiings off before ;)
[Samsung Galaxy Nexus] Bosio91:
[MENTION=4615478]boype[/MENTION] are you still using Cyanogenmod as your ROM?
[Samsung Galaxy Nexus] ReMuSeR:
I stoped usimg cyanogen until a stable version comes out
[Samsung Galaxy Nexus] parthipanramesh:
The Updater doesn't support the xy-big versions yet.

Sent from my Paranoid Nexus running Fancy Kernel
[Samsung Galaxy Nexus] boype:
r43

Hi again,

here's r43:

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

revert 3g/4g tcp buffersizes to CM default (modified values were maybe cause for reported high 3g battery drain?!)

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

many, many, many SYNC (drivers/base/sync) 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

a few patches that largely improve swap performance (and therefore improve zRAM; backported from 3.4 / 3.6 and 3.11 kernels)

speed up sync() by 7-8x on busy filesystems (backport from 3.11 kernel)

patch that greatly reduces network latency in some workloads (backport from 3.9 kernel)

small OMAP MMU idle fix

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

a couple of WiFi driver updates from Google repo

a few other things (among them some more minor updates from Google repo)

As you can see, I have been looking for patches across the newer kernel versions which can further enhance performance.

Have fun
[Samsung Galaxy Nexus] abhishek93:
Bgmem is extended + big?
[Samsung Galaxy Nexus] madhavs:
yes the regular ext with additional memory

all 3 available from OP
[Samsung Galaxy Nexus] motorazrv3:
Yes, bigmem is ext based.

Gesendet von meinem Galaxy Nexus mit Tapatalk 4
[Samsung Galaxy Nexus] AbhishekS:
Is this Smart Reflex thing for MPU?

Currently I have SmartReflex Control activated for Core and IVA, but not for MPU. Shall I activate it for all three of them, or only MPU, or is my current set-up good?
[Samsung Galaxy Nexus] nikosrs4:
What are the mipi_link and PowerManagerService.wakelocks?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] jeff5347:
Just installed 43. I am getting constant flashes of a snow like screen. Also everything feels super sluggish. Was on 43-1 and that was working great
[Samsung Galaxy Nexus] flybass:
The benchmark scores are certainly higher for me. my performance so far seems about the same as r42. i'll have to wait to comment further.
[Samsung Galaxy Nexus] jeff5347:


---------- Post added at 12:23 PM ---------- Previous post was at 12:21 PM ----------

Had to revert back to 43-1. Was getting constant freezes and lag. Oc to 1300s, UV -50, changed color a bit and cubic- deadline. I always change to this every update. For some reason 43 was not good for me
[Samsung Galaxy Nexus] mick.li:
Why don't you try the big instead of the ext version? 43-1 was big as well.

Mick
[Samsung Galaxy Nexus] pcphobic:
There is no wrong or right. But for me, I leave smartreflex On for all 3
[Samsung Galaxy Nexus] jeff5347:
OK so correction. Was on 43-1 big not ext. Tried 43....and it froze my phone, had to reboot then ultimately go back to 43-1. went back to 43-1big and just now am on 43 big. So far it is OK I only had one freeze that lasted about 10 seconds. Added all my tweaks and so far so good
[Samsung Galaxy Nexus] FutureGamerz:
No idea for mipi_link. It appears sometime but not for very long time so never cared about it.

PowerManagerService.wakelocks are actually a sum of all wakelock in your Partial Wakelock. Guys, please correct me if I'm wrong. That's what I see so I guess it is :D

After flashing Fancy, I suggest you to do a reboot. I tried once after flashing and I didn't reboot then this wakelock took my deepsleep time, causing my phone to awake for 4 hours. The culprit is "Android System" (can't remember whether it's Google or Android). Everything went fine after rebooting the phone.

My suggestion, for your reference only :D
[Samsung Galaxy Nexus] jeff5347:
Weeellll I'm back on 43-1 big. Got screens freezes both black and frozen. Sat for 2 min then rebooted itself. I guess its just something in the general area of the kernel
[Samsung Galaxy Nexus] KeithLing1115:
Can someone link me to pre 43-1? It's not in test folder.
[Samsung Galaxy Nexus] FutureGamerz:
Boype removes tst versions when stable version is released.
[Samsung Galaxy Nexus] thomstrack:
I flashed r43-big about 30 minutes and the first impression is: WOW!!

This release appears to have a performance much much higher than the r42-big.

Much smooth, fast and the multitask is running very well! :)

(ROM: stock 4.3)
[Samsung Galaxy Nexus] BOY_:
I had some weirdness/freezes on first load so reverted back to pre43. I u installed a couple of mods and reloaded and things seem OK now. Weird.
[Samsung Galaxy Nexus] madhavs:
Very unusual

This is the very first time ever my phone got freeze with a fancy kernel with r43 big

reverted back to pre r43 -1 big everything is fine now
[Samsung Galaxy Nexus] boype:
Problems are duly noted!

I should probably consider building milestone releases (completely bugfree ones) every once in a while.
[Samsung Galaxy Nexus] ReMuSeR:
[MENTION=4615478]boype[/MENTION] u still using cm rom or :D
[Samsung Galaxy Nexus] creepinm3:
I read your OP, it says you're running 3.11 kernel. May I try this?

Sent from my Galaxy Nexus.
[Samsung Galaxy Nexus] bigknowz:
Screen pixelated

My screen also gets multicolor snow every few minutes, but I just have to touch it and normal screen returns. On r43-ext, CAB on.
[Samsung Galaxy Nexus] jeff5347:
That's what I was getting. Cab off. Mine wouldn't stop
[Samsung Galaxy Nexus] Starsream88:
With 43-big my phone is very hot and i have huge battery drain (very low bench score also).

Back to pre43 for now
[Samsung Galaxy Nexus] Ci-Fi:
r43-big is working perfectly for me. No issues so far. I'm getting significantly improved battery life compared with r42-big.
[Samsung Galaxy Nexus] AutomaticFailure27:
For the people having issues with r43, what ROM are you on?
[Samsung Galaxy Nexus] jeff5347:
I'm on vanir/atom
[Samsung Galaxy Nexus] stevensoaj:
I'm also rockin r43-big. Zram off, MPU -100 and vmmc at 2600. Everything else stock. No issues at all. Slim build 1
[Samsung Galaxy Nexus] AutomaticFailure27:
AFAIK Vanir/Atom use a few inti.d scripts. Those could be causing issues.
[Samsung Galaxy Nexus] pnut22r:
Do you guys like zram?
[Samsung Galaxy Nexus] Starsream88:
Pac man 4.3 nightly
[Samsung Galaxy Nexus] jeff5347:
Really..! Did not know that. Was running LS. Any known scripts i n there