yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Angelakaro:
My heapminfree default value is 512k, i've never touched it. (I'm using odexed 4.2.2 by bigxie)

Edit: unfortunately, we are on the wrong way: i experienced a systemui memory leak just some minutes ago with the "right" dalvik VM settings (64/256/0.75 + heapminfree already set to 512k and, since it was already 512k before starting to tune these values, both the configuration, 96/256/0.75 and 64/256/0.75, are wrong) i'm not very familiar with these things, for me are just numbers but i'm sharing with you my feedback. Just my personal opinion, i think that maybe going on with dalvik won't fix the issue.

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] DoesntPostAThing:
I have heard reports that bigxie already changes it to 512k. I believe this is the correct one. Also, about the SysUI leak, how much does it leak to? On AOSPA/Rubik it sometimes goes up to 60.
[Samsung Galaxy Nexus] Raijin:
What I will never understand is why Franco added the vibration control to Nexus 4, and not in the Galaxy Nexus.
[Samsung Galaxy Nexus] Angelakaro:
I never cared about that. When everything starts to lag, i use the trick that someone posted in the main discuss of system ui memory leak, in general section: open recent apps, rotate screen, back to home and the leak is (temporarily) fixed. Someone may like to use live wallpapers to completely avoid this leak, but everyone already know how much frustrating graphic performance is, on galaxy nexus

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
That's your ROM interfering. Here are the Galaxy Nexus JB 4.2.2 defaults on stock ROM:

u0_a136@android:/ $ getprop | grep dalvik
[dalvik.vm.dexopt-flags]: [m=y]
[dalvik.vm.heapgrowthlimit]: [96m]
[dalvik.vm.heapmaxfree]: [8m]
[dalvik.vm.heapminfree]: [512k]
[dalvik.vm.heapsize]: [256m]
[dalvik.vm.heapstartsize]: [8m]
[dalvik.vm.heaptargetutilization]: [0.75]
[dalvik.vm.stack-trace-file]: [/data/anr/traces.txt]

Franco added it on the N4 because he felt it actually needed it, whereas he didn't here.
[Samsung Galaxy Nexus] DoesntPostAThing:
I see, nevermind then.
[Samsung Galaxy Nexus] Raijin:
Maybe in Nexus 4 is really needed, but in Galaxy Nexus a smoother vibration can be more pleasant. I feel it rough.

It's a thing that require only to copy and paste a code, and many have been long time asking for.
[Samsung Galaxy Nexus] Charmacas:
I am not really sure but I think you mix things up here. General smoothness is improved by tuning the dalvik settings. The System UI memory leak is just another topic. So if you got slowdown with the new settings then I think it's only related to the System UI because here is everything running sooo smooth. :)

(Just my thoughts. This does not have to be true!)

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] hotrodwinston:
Live wallpaper fixes system ui memory leak?

Also I'm testing 96-256-0.75 with minfree set to 1024k and it's buttery smooth
[Samsung Galaxy Nexus] osm0sis:
Apparently so. Works around it somehow?

The leak must have something to do with rotate since 2 workarounds involve it. Not sure how wallpaper could factor in but hey, good to know.
[Samsung Galaxy Nexus] Charmacas:
What are you exactly testing here? These are the default 4.2 values except MinFree. The tuned values are 64/256/0.75/512k

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] Raijin:
My phone always have Phase Beam, but a few times I put a static background and my phone seems to run smoother.

When it awake from deep sleep, runs super soft. But after 3-5 minutes, it shows a slight lag. Another person can not notice it but I do. I understand this is what you all are talking. :confused:
[Samsung Galaxy Nexus] osm0sis:
Maybe. Try turning off rotation in accessibility and see if it helps with the static background.
[Samsung Galaxy Nexus] Raijin:
Rotation is always disabled. I will try static wallpaper and will comment later.

Thanks osm0sis.
[Samsung Galaxy Nexus] ciprianruse88:
Tried it and tried also every tweak and fixes but I think that only google will fix this.I reverted to 4.2.1 based rom due to this problem.sorry for OT but I saw you guys talking about this problem.there is a thread in general for more discussion.Good luck guys !:)
[Samsung Galaxy Nexus] Angelakaro:
Oh, sorry! I didn't know that dalvik tune up was only supposed to increase performance! I just made a bit of confusion :P

However new settings are good even if i can't see any noticeable improvement

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] evil_penguin:
Stock+ franco = Best combination!:good:

Thanks Franco!
[Samsung Galaxy Nexus] agritux:
any miui 4 user? what is the performance, battery drain and stability with miui4 ?
[Samsung Galaxy Nexus] hotrodwinston:
Testing how long it stays smooth with the stock settings plus a tweak to min free 12 hours up so far and smooth as silk
[Samsung Galaxy Nexus] JBNex:
Any optimal color settings to get rid of the dark purple hue on low brightness?
[Samsung Galaxy Nexus] mpokwsths:
Trinity contrast: -24

Gamma profile: 4 (in Trickster mod)

Gamma

R: 3

G: 0

B: 5

Multipliers

R: 200

G: 190

B: 210
[Samsung Galaxy Nexus] osm0sis:
Try some of these:

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

My new panel is much better than my old so I'm good with Franco's (new) defaults now, no purple, just using them to get rid of the yellow. There's lots to choose (and tweak) from on there though, try some of my old ones - I had the worst purple on my old panel. :)

And please, everyone take the color settings discussion to that thread as well if you all feel compelled to share. ;)
[Samsung Galaxy Nexus] Raijin:
Tested with static wallpaper. Seems that live and static doesn't make a difference.

After a few minutes, the phone doesn't work with the same softness that when is awaked after long time. It's hard to say, because it's only a subjetive reaction that maybe is not correct, but like I said before, I can feel it. The best way to test it would be to have one TV camera of superfast shots, to catch all frames and compare.
[Samsung Galaxy Nexus] osm0sis:
Is it like you have to push harder for an effect? You might have the touch panel sensitivity bug.. screen off -> on was always the main workaround for that. Also omap gamma to 1.2 or above.

Read my post at the top here, it's the best run-down outside of the OP: http://xdaforums.com/showthread.php?t=1576739&page=67

(Another thing which my new panel fixed. It's freaking awesome being able to use a tempered glass SP now like it isn't even there. :D)
[Samsung Galaxy Nexus] CyanoBacteryMod:
mhl works with this kernel?
[Samsung Galaxy Nexus] Khrushy:
Yep. I use it all the time.
[Samsung Galaxy Nexus] shawnaye:
Hey os, I wanna ask, must I have a Linux environment to build a kernel. I kinda bought an Asus fonepad and wanna start development.
[Samsung Galaxy Nexus] osm0sis:
Never tried to set up a build environment myself, but I'd imagine anything you can get the toolchains and makefiles working on would do. Cygwin for example should be able to compile things for Linux from what little I know about that end of things. I could be mistaken though.
[Samsung Galaxy Nexus] :
As far as I know you should be using linux for compiling and building. I'm using Ubuntu 12.10 64bit for compiling my own ROM builds.
[Samsung Galaxy Nexus] Kurre:
Yeah, I'm also compiling kernels in my x64 Ubuntu 12.10 environment. Using cygwin might work, but I'd be prepared for a serious incompatibility issues and problem solving.. :) also windows environment doesn't support case-sensitive file names..I mean that file.c and FILE.c are same in win, but not in linux. I encountered this issue when I cloned my repo to my win7 pc at work.

So, I'd strongly recommend installing ubuntu/mint linux/etc as a dev platform. Second best option could be installing secondary OS as a virtual box environment, but that also could bring some compatibility issues (for example, to use 64-bit OS, your processor must be compatible). Also virtual OS would be significantly slower when it comes to compiling stuff.

dual boot ubuntu/win7 x64 with SSD..killer solution to handle all upcoming situations :)
[Samsung Galaxy Nexus] mono28aug:
I looked all over the forums but could not find codex rom even heard that the developer stopped working on that rom and now he is back with a bang :) so I wanna try out his codex rom and feel lucky....

Would anyone help me with the link :( thank u
[Samsung Galaxy Nexus] madhavs:
check pm or my signature
[Samsung Galaxy Nexus] arhung:
My colour setting is not stick on boot and I set it to 185-165-265 but after reboot it change to 178-164-262, I try it many times but no fixed....
[Samsung Galaxy Nexus] timbck2:
I've compiled an Android ROM on both an Ubuntu virtual machine running under Windows and natively on Mac OSX. Getting the build environment working was much easier on the Ubuntu VM.

Sent from my grouper or toro
[Samsung Galaxy Nexus] osm0sis:
That's not even Franco's defaults.. You using an init.d script you forgot about? Use my emergency reset zip.
[Samsung Galaxy Nexus] arhung:
I haven't use any script, after flashing your zip, still not fixed the problem and now the setting change from 185-165-265 (that's my setting) to 190-168-215.
[Samsung Galaxy Nexus] osm0sis:
Update f.Ku to v9.3.1, there was a color settings bug fixed with the N4 that was perhaps affecting us too.
[Samsung Galaxy Nexus] arhung:
Oh, I see. Thx Os:)
[Samsung Galaxy Nexus] famewolf:
This is from http://code.google.com/p/android-wired-tether/wiki/FAQ

"Why do I get the message "Unsupported Kernel" on startup?

This means that the Linux kernel on your device does not have the features (CONFIG_NETFILTER/CONFIG_IP_NF_IPTABLES and/or RNDIS) required for tethering."

Is there any chance these features could be enabled so android wired tether would work with the franco kernel? I ask because the android wired tether app is supposedly less prone to trigger carrier tethering checks.
[Samsung Galaxy Nexus] hotrodwinston:
1 day 19 hours and still smooth as silk - what's the current uptime record?
[Samsung Galaxy Nexus] Khrushy:
Something ridiculously huge probably. I'm currently at 78 hours, and it's not like I'm purposefully keeping the phone on - I just don't bother rebooting unless I notice something that justifies it (or I flash a kernel, or a ROM, or whatever - which tends to happen 1+ times a week anyway).
[Samsung Galaxy Nexus] wasdf:
hi, does anyone know how to edit kernel default.prop?

I want to make changes to franco kernel to the following settings in order to run an app which enforce those "cheating" settings

ro.secure=1

ro.debuggable=0

persist.service.adb.enable=0

is it possible to change it ?
[Samsung Galaxy Nexus] Pume:
Mine was on conservative.
[Samsung Galaxy Nexus] sishgupta:
Thanks for the new release. I am very excited for the CIFS module support!

Is this not going to negatively affect people that like to clock down to 350Mhz?

Lets say one really likes to listen to music on their phone. This means a lot of awake time. To me then it would make sense to actually run ones phone at a 350Mhz awake. I think someone (ro_explorer?) had produced test examples confirming this at some point previously.

With this change it is then 350 or 1200? Thats kinda harsh is it not? No inbetween for the medium sized tasks for people with long awake periods?
[Samsung Galaxy Nexus] bradm23:
+1 on performance default. Never used performance before, flashed over from 13.1.
[Samsung Galaxy Nexus] Felixpau86:
Hrm... nope still defaults back to perf on mine after reboot. On bigxies 9.2 if that matters
[Samsung Galaxy Nexus] bradm23:
You could always switch to interactive
[Samsung Galaxy Nexus] franciscofranco:
Nah, I've read ro_explorer tests and from 350mhz to 700mhz listening to music on screen off produces no extra drain.

Sorry it's really booting as performance, uploading it now with conservative as default, my mistake.
[Samsung Galaxy Nexus] sishgupta:
True there is both interactive and ondemand but have these been tweaked like franco's conservative? AFAIK both these are significantly more aggressive than 13.1 conservative.

Ah cool thanks for letting me know!
[Samsung Galaxy Nexus] esoomenona:
Franco, love the kernel. I have a suggestion. Would it be possible to include the MD5 of the kernel download in the Updater so that we can compare it with what we have downloaded to make sure it's all good to go?
[Samsung Galaxy Nexus] ellesshoo:
Uploaded yet?
[Samsung Galaxy Nexus] franciscofranco:
Yes, planned for next updater patch. Still it will take a little while, got to do almost a full re-write.

Yes.
[Samsung Galaxy Nexus] darrendm:
Repeating boot animation after installing #14 from app. Will try a reflash before I restore an old backup :(
[Samsung Galaxy Nexus] loudaccord:
Interesting NenaMark2 bench is a little better... highest before was 25, getting 27.8 now. I bet I can get 28pfs :) lol
[Samsung Galaxy Nexus] slg60:
Running fine so far! Will test next days! Thanks for oc'ing the GPU again franco!
[Samsung Galaxy Nexus] ro_explorer:
I have no idea what's the deal here but after flashing #14 (first release) my phone would reboot like crazy (every 5-10 minutes or so and there is no data connection on HSDPA .... only on wifi.

I've reverted back to #13.1 waiting for the next patch.
[Samsung Galaxy Nexus] yungboss22:
The last kernel is not so good. After 2 min, my screen close by itself and i cannot reboot my phone until i remove the battery. And i have a huge battery drain while screen is on because it stays at 1200mhz .
[Samsung Galaxy Nexus] franciscofranco:
Ok thats not good. I'll revert the voltage changes and re-upload.
[Samsung Galaxy Nexus] aron7awol:
Did you see his latest tests? Playing music with screen off used 10% more power at 700MHz than at 350MHz.
[Samsung Galaxy Nexus] danielvc:
Don't have any problems yet. Going to check in again after a few days. Feels a bit smoother.
[Samsung Galaxy Nexus] Mondfahrer:
My GN is also not rebooting anymore.

After the Rebot animation it crashes all the time.

Mileston 2 running.
[Samsung Galaxy Nexus] franciscofranco:
Ok re-uploaded. Try again.
[Samsung Galaxy Nexus] osm0sis:
/data/local.prop might work to override without modifying any system or ramdisk stuff. Failing that, use my Android Image Kitchen to edit the ramdisk and repack.
[Samsung Galaxy Nexus] wasdf:
Thanks and done :good:

I read about this thread before but it is quite complicated for Windows

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

Thumb up for your handy tools :good::good:
[Samsung Galaxy Nexus] osm0sis:
Yeah that's not mine, that's something different. Mine keeps it nice and simple. Link in my sig. ;)
[Samsung Galaxy Nexus] bigknowz:
One week in

After running 376 for a few days, my phone started acting strange. Battery went from lasting at least 30 hours to about 24, similar usage patterns. Also, a few things occurred that I never experienced before - starting day 5, my music player would close on screen unlock; yesterday was 1 week - music continued to play after headphones unplugged and screen rotation toggled on. Reboot and back to normal.
[Samsung Galaxy Nexus] whitedragonz83:
Though this is not kernel related, I was experiencing high Android System RAM usage when looking at the system monitor. It would be ~80mb on a reboot and was as high as ~170mb when my system became very sluggish and things were closing weirdly. Maybe this is similar to your problem as for me it was a RAM issue being at ~600mb usage always or more.

Was this one of the longest periods you went without rebooting your phone?
[Samsung Galaxy Nexus] bigknowz:
RAM

I usually try to go at least a week without rebooting to get a better feel for things. Kernels always look good the first couple of days. I have to agree with you on RAM. Typically after swiping away open apps, RAM usage drops into the mid 400s. On 376, it was consistently above 500.
[Samsung Galaxy Nexus] myepicyear:
You know, I think I experienced a very similar thing last weekend. I didn't give it too much thought then, but looking back now, I'm certain that I was running Franco's 376 at the time (as opposed to the CM stock kernel, which I use primarily).

My whole extended battery drained overnight, and I was clueless as to why.

What happened was, I had been listening to music on headphones before going to sleep. Eventually, someone was trying to talk to me, so I turned the volume all the way down, exchanged words with a relative, and then decided I was ready to sleep. I unplugged the headphones, turned on the phone screen, did a swipe to unlock, and then Google Play Music seemed to completely close itself out. I assumed that the culprit was a low memory force close since I'd been heavily multitasking while listen to the music; and while it is annoying, random force closing is something that almost never happens to me, so I wasn't concerned. There wasn't any "Now Playing" status bar widget like there usually is when Play Music is active. All signs indicated that music was off.

When I woke up the next morning, the battery was completely drained. When I turned the phone back on, the media volume was all the way down, so it was streaming music all night long, I just didn't hear (or see) any indication.

I've not attempted to look into the origin of the problem yet, so this could happen for several different reasons. It only just dawned on me, after reading Bigknows' post. Maybe it's a CM/FK compatibility issue, don't know yet--but I thought I'd mention my similar experience.
[Samsung Galaxy Nexus] dmourao:
Sorry if this has already been asked, but what would be the equivalent, in Trickster, for your Governor Tunables settings? Thanks in advance!
[Samsung Galaxy Nexus] exzacklyright:
My ram usage is always under 100mb :(
[Samsung Galaxy Nexus] The Gingerbread Man:
Generally unused ram is wasted, android works different than windows

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] metalspring:
You should just be able to add those to /system/build.prop, save and reboot and they should work fine

To check if they work, open terminal emulator

su

getprop ro.secure

getprop ro.debuggable

getprop persist.service.adb.enable

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

Android keeps previously opened apps in memory so if you launch an app you previously used it should work just fine

However you still need enough ram free to open new apps so you do need at least some ram free
[Samsung Galaxy Nexus] akash3656:
True but if the ram is hogged by system processes because of a ram leak, it doesn't let user apps to be cached and then we get often app redraws. :(

And android doesn't seem to handle severe ram leaks as efficiently as everyone claims it does. The whole system ends up redrawing for every app.
[Samsung Galaxy Nexus] Sik-1:
I think the problems with ram is that it doesn't read fast enough when things are loaded into it, its not necessarily how android processes them but more how fast it can get to the data at the back of the ram thus eventually using less CPU and holding things longer and without ree draws....

I'm gonna see if I can tweak some values that I have learned through the forums to the max and work on battery life from there
[Samsung Galaxy Nexus] Khrushy:
People need to identify what their RAM "problem" is a bit better before posting, because most of these posts lately are not Franco issues.

1. My RAM is constantly low: This is normal - android keeps very little memory unused and that's fine.

2. Everything slows down and redraws after my uptime gets a bit long: Welcome to the 4.2.2 systemui memory leak. This is a Google problem, not a Franco one. Either start rebooting at least once a day to refresh things or switch to the more recent builds of AOKP or CM, both of which have patched this. Honestly, rebooting regularly is not that hard.

3. I've been testing XXXXX VM setting. I found it does YYYYY to RAM usage and causes tiny flying weasels to orbit my phone: Cool, carry on testing and let us know - this useful info for optimising the VM settings associated with Franco kernel. Also, flying weasels are cool.

Cheers
[Samsung Galaxy Nexus] Sik-1:
Lol funny guy krushy
[Samsung Galaxy Nexus] stick1300:
I knew it! Since upgrading to 4.2.2, my phone gets gummed up after only a few hours and a reboot is the only way to fix it. I reboot first thing in the morning, but still end up having to reboot at least two more times throughout the day.
[Samsung Galaxy Nexus] Antob125:
Just open recent and clear them all. Ram clear. Problem solved.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] exzacklyright:
But there is a definite performance slow down when close to no ram
[Samsung Galaxy Nexus] blueren:
I'm running the latest pa along with 376. Having micro stutters ever every now and then. Any settings changes required?
[Samsung Galaxy Nexus] AndyGnex:
Using latest 376 with cm10.1 build 20130319. Hadn't had any hiccups whatsoever. Been ages since i restarted the phone and everything still runs fine. Haven't got any urges to update cm version as well since everything seems just fine now.
[Samsung Galaxy Nexus] Unzitron:
I have been running Mmuzzy's 4/26 test build and have been experiencing great performance. He made some VM heap changes. Try these!

dalvik.vm.heapgrowthlimit=64m

dalvik.vm.heapsize=384m
[Samsung Galaxy Nexus] whitedragonz83:
Are these RAM VM complaints possibly from over tuning the IO schedulers for read?
[Samsung Galaxy Nexus] Unzitron:
Is that what ROW scheduler does?
[Samsung Galaxy Nexus] The Gingerbread Man:
The settings were chosen for overall best performance, each schedular works differently though so they have different tendances as to how they behave. Trust me alit of time has gone into makimg sure each performs pretty much as well as it can over Francos suported devices

ROW just means Read Over Write. In my own opinion cfq and deadline are best. Cfq is always silky smooth all over and deadline process data faster
[Samsung Galaxy Nexus] whitedragonz83:
Maybe I should just try CFQ some. Or deadline for a bit. Thanks.
[Samsung Galaxy Nexus] osm0sis:
These are I/O schedulers, so like deletions, moves, installs, data reading for games, etc. Shouldn't affect anything like free RAM. ROMs changing minfree and lowmemorykiller, and vm settings are much more likely to be the problem there.
[Samsung Galaxy Nexus] wasdf:
Just something strange... I can't use wifi tethering, don't know if it is rom or kernel problem (honestly, just lazy to test and find out at this moment:silly:) When I start the wifi hotspot, my computer can find the SSID but the connection is limited.
[Samsung Galaxy Nexus] Gafanhotz:
Guys, sorry for my disappearing, finally I've came with the result of some tests. That Bluetooth trouble I've reported a while ago here, only really happens with Franco Kernel. I've tested Fancy Kernel, AK Kernel, and some others and the deadlock never happened. The thing I'm fully scared is that nothing (yeah, NOTHING) happens in the logs. So I decided to leave it to someone move capable of doing these researches, since I'm working on maintaining the AOSPA3 rom to GTab 2, I don't have enough time.
[Samsung Galaxy Nexus] The Gingerbread Man:
I spent the weekend away in hotel and Bluetooth was fine in the car journey there and back. WiFi tethering worked fine, the place I stayed had no internet so I used my gnex to get WiFi on my WiFi only nexus 7. I blame rom stuff in both your cases because stock rom so far as I can tell everything works and if stuff were really broken then there would be more than just 1 person saying stuff is broken
[Samsung Galaxy Nexus] The Gingerbread Man:
6 Million Views! Woohoo

Sent from my Galaxy Nexus