Database Develop

Share your N5 Performance tips! - Nexus 5 General

All benchmarks aside the N5 is in my opinion the best and the fastest
I've been trying to make it as fast as possible using different ROM / kernel / tweak combos.
Currently satisfied with Carbon ROM , Elemental X .34 , various build.prop tweaks , and custom sysctl / ram management tweaks using trickster mod & ROM toolbox pro.
Does anyone have any performance tweaks that can help me make my phone even faster ? Is there a way to use "fastboot" option like HTC devices ?
My fastest cold boot to lock screen time is 15.3seconds but I want shorter boot times xD
In using latest carbon ROM nightly, minimal gapps, dalvik opt zip. Latest GPU drivers.
Here are my build.prop tweaks :
debug.sf.nobootanimation=1
debug.composition.type=1
debug.egl.hw=1
debug.sf.hw=1
debug.performance.tuning=1
video.accelerate.hw=1
windowsmgr.max_events_per_sec=300
pm.sleep_mode=1
ro.ril.disable.power.collapse=0
ro.ril.fast.dormancy.rule=0
persist.sys.shutdown.mode=hibernate
ro.config.hw_quickpoweron=true
ro.max.fling_velocity=30000
ro.min.fling_velocity=20000
ro.kernel.android.checkjni=0
ro.kernel.checkjni=0
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
ro.config.nocheckin=1
dalvik.vm.execution-mode=int:jit
ro.mot.eri.losalert.delay=1000
debug.sfbootcomplete=0
persist.sys.purgeable_assets=1
persist.sys.use.dithering=0
ro.wmt.blcr.enable=0
dalvik.vm.debug.alloc=0
Can anyone provide me with anymore ?
And so far the most free ram I've been able to come up with -.- on my old galaxy nexus with slim bean I had only 112mb being used but I forgot how I achieved that.
Removable apps :
All live wallpaper!
Live wallpaper picker
Com.lge.update
Update device
Calendar
Calendar storage
Sim toolkit
Voice+
Sound recorder
cLock widget
Certificate installer
Dev settings
DSP manager
Email
Exchange services
Face unlock
Picasa uploaded
Pico tts
Google tts
Google search
Stock launcher (you must have a replacement installed or bad things will happen >:])
VPN dialogs
TalkBack
Tags
Print spooler
AOSP any keyboard (must have a replacement!)
*list will be updated, I use ROM toolbox pro for all this stuff with the built in app manager. You can use any root explorer and go to /system/apps and manually delete or use titanium backup etc.
Your mileage may vary depending on what you use and what you don't. I've had 0 force closes with these removed!
I'd like to know your setups , and tips, and tweaks if any

im just curious, do you know what the build.prop lines that youre using do?

simms22 said:
im just curious, do you know what the build.prop lines that youre using do?
Click to expand...
Click to collapse
Some do nothing , some drain the battery, some actually force the GPU to do what's accessible via Dev settings. And others help my phone boot faster , stock boot time for me is 25seconds. Carbon boot time for me is 19seconds, with all the settings and stuff I've changed its now 15 seconds, some people call it placebo, but if you actually time it , and test them individually you can see effects whether negative or positive

simms22 said:
im just curious, do you know what the build.prop lines that youre using do?
Click to expand...
Click to collapse
Which BTW, is there anyways to implement a "hibernation" mode like the HTC fastboot option ? On the nexus 5 or other non HTC devices ...
Is your device stable at 3.0ghz? I can only get mine up too 2.88 without any random reboots. -.- I don't think a change of kernel will help would it ? I'll try trinity which is what you're using correct?

tadgerloks said:
Which BTW, is there anyways to implement a "hibernation" mode like the HTC fastboot option ? On the nexus 5 or other non HTC devices ...
Is your device stable at 3.0ghz? I can only get mine up too 2.88 without any random reboots. -.- I don't think a change of kernel will help would it ? I'll try trinity which is what you're using correct?
Click to expand...
Click to collapse
stable at 3014mhz, not quite. ill use it for several hours, then itll just lock up and reboot. try playing with your voltage at 3014mhz, mayne you can get your phone to run it. and yea. trinity is what i use

simms22 said:
stable at 3014mhz, not quite. ill use it for several hours, then itll just lock up and reboot. try playing with your voltage at 3014mhz, mayne you can get your phone to run it. and yea. trinity is what i use
Click to expand...
Click to collapse
Is yours on the stock voltage for that freq? Would you mind sharing the voltage if its not .
And my favorite prop tweaks are the min/max fling + window mngr because they make scrolling oh so smooth!

tadgerloks said:
Is yours on the stock voltage for that freq? Would you mind sharing the voltage if its not .
And my favorite prop tweaks are the min/max fling + window mngr because they make scrolling oh so smooth!
Click to expand...
Click to collapse
my voltage is at the default voltage for my phones binning. but i do play with it a occasionally. it can run fine within a small range at 301hz. its at 1150mV, 1140-1165mV is what itll range.

simms22 said:
my voltage is at the default voltage for my phones binning. but i do play with it a occasionally. it can run fine within a small range at 301hz. its at 1150mV, 1140-1165mV is what itll range.
Click to expand...
Click to collapse
Alright just got latest trinity , will test it for a few hours against elemental, rolling back to .29 due too boot times lol xD

tadgerloks said:
Alright just got latest trinity , will test it for a few hours against elemental, rolling back to .29 due too boot times lol xD
Click to expand...
Click to collapse
B10 is the latest trinity kernel

simms22 said:
B10 is the latest trinity kernel
Click to expand...
Click to collapse
Yes just flashed it, got nothing but fc's on carbon rom nightly 4/05 ... what roms is the trin kernel designed for.? Restoring backup right now as flashing elemental didn't save it... guessing trinity changed the ramdisk ?

tadgerloks said:
Yes just flashed it, got nothing but fc's on carbon rom nightly 4/05 ... what roms is the trin kernel designed for.? Restoring backup right now as flashing elemental didn't save it... guessing trinity changed the ramdisk ?
Click to expand...
Click to collapse
Search the trinity thread for a anykernel release of B10. I believe that release will work fine on carbon.
Sent from my Nexus 5 using Tapatalk

akash3656 said:
Search the trinity thread for a anykernel release of B10. I believe that release will work fine on carbon.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I'll have to check the thread then , trinity B10 didn't work for me on Latest Carbon nightly , maybe I either roll back to a previous nightly or previous trinity build
Edit : just found the hybrid anykernel T5B10 build. Will give trinity another go with carbon and see how things pan out over the next few hours ?

tadgerloks said:
I'll have to check the thread then , trinity B10 didn't work for me on Latest Carbon nightly , maybe I either roll back to a previous nightly or previous trinity build
Edit : just found the hybrid anykernel T5B10 build. Will give trinity another go with carbon and see how things pan out over the next few hours ?
Click to expand...
Click to collapse
That's the one I'm talking about!
Sent from my Nexus 5 using Tapatalk

tadgerloks said:
Yes just flashed it, got nothing but fc's on carbon rom nightly 4/05 ... what roms is the trin kernel designed for.? Restoring backup right now as flashing elemental didn't save it... guessing trinity changed the ramdisk ?
Click to expand...
Click to collapse
not at all. try redownloading and reflashing.

simms22 said:
not at all. try redownloading and reflashing.
Click to expand...
Click to collapse
I tried the normal b10 again, same issues. Just finished flashing carbon and the hybrid version of b10, and I can confirm it's working! Carbon ROM has traces of both AoSP and CAF , so normal trinity b10 was causing problems. This one is working though I can say I'm really missing the "cooler colors" of elemental ...

tadgerloks said:
I tried the normal b10 again, same issues. Just finished flashing carbon and the hybrid version of b10, and I can confirm it's working! Carbon ROM has traces of both AoSP and CAF , so normal trinity b10 was causing problems. This one is working though I can say I'm really missing the "cooler colors" of elemental ...
Click to expand...
Click to collapse
ahh.. the caf thats why.

Hi,
I would say... delete all the additional lines on your build.prop (I mean the ones you added). Most of them does nothing at all or they are worse or have side effects. Search on Google for each line and see the first/second page and you will see for what device it is made for (and the date of the threads...) then you will understand. remember you are on Kit Kat, thes tweaks were good (at least) on Gingerbread, maybe ICS but that's all... There are also some threads about these lines, tested and examinated in Android code source.
You will have better results by tweaking the CPU governor and i/o scheduler you are using. VM settings are good too but you will need a few days of tests to see what is right or wrong.
I tested a lot of build.prop edits (and like you I added a bunch of them), like the ones you posted and other ones floating around on XDA in some threads in the General Android forum..., I always delete all these lines, there is always something wrong at some time.
Keep your build.prop clean (well one or two are useful, I speak mainly about all the "performance" tweaks like all the "debug about the GPU/dalvik...." lines, same thing for the scrolling tweaks )
You will see if you really tested that, at least, all is same as before even without all these tweaks in general UI. In fact, like you said, one line does the same thing as the "Disable HW overlays" in Developer options.
Even some "devs" add these lines in their roms..., but well, urban legends and placebo effects are "solid"...

Yeah some lines do nothing , and I will clean up my build.prop but I'm keeping a few lines , like fling velocities, power collapse, nobootanimation.
And yeah I know what you mean about them being outdated, had those exact lines since 4.0.3 on my vzw gnex especially then I noticed big differences in over all performance. Whether they apply now or not, just got used to it I guess.

Revised build.prop :
debug.sf.nobootanimation=1
windowsmgr.max_events_per_sec=300
pm.sleep_mode=1
ro.ril.disable.power.collapse=0
ro.ril.fast.dormancy.rule=0
ro.max.fling_velocity=30000
ro.min.fling_velocity=20000
ro.kernel.android.checkjni=0
ro.kernel.checkjni=0
ro.config.nocheckin=0
ro.mot.eri.losalert.delay=1000
Edit: reusing the quick power on line
Without it carbon booted in 20.3 seconds
With it carbon booted in 18seconds.
Will see if hibernate line has any effect. Or the sf.bootcomplete line (which is supposed to show lock faster) Little to no difference is still a difference after all !

My Nexus 5 boots in 10 seconds without any build.prop modifications

Related

Hi all,
since knzo have decided to stop developing Nova v7 despite certain little bugs, I've decided to create my own post to share with you a package to solve all the solvable bugs until the date.
In this first version, the flashable package contain/solves:
- SmartassV2 governor Issue (with modified nova script).
- Updates Superuser 3.0 from Beta3 to Beta4 and /system/bin/su permissions set to 7777.
- Autoset I/O Scheduler on boot (with modified 11nov init.d script).
http://dl.dropbox.com/u/4629711/nova opt/huexxx-nova7-twk-v1.zip
(MD5: 004bedbdd3cec21779af2538d32f75c4)
Problems with Superuser? Try some of the following packages. First mantain 3.0 Beta3 and second contains the latest stable version. Both with su permissions set to 7777.
http://dl.dropbox.com/u/4629711/nova opt/huexxx-nova7-twk-v1-beta3.zip
(MD5: 3e93990b79bf8c2d70001c4d3f72babf)
http://dl.dropbox.com/u/4629711/nova opt/huexxx-nova7-twk-v1-stable.zip
(MD5: 4373fb38d9f8fac857ed77b046285ffe)
Instructions: Put it onto sdcard root and flash it whrough CWM.
I tried the package and working ok but I am not responsible for any damage that may result in your devices.
So many thanks to Antonio1475 and knzo, good work dudes! ... and thanks to all who have helped into Nova project!
I hope this thread will please everyone involved.
Regards!

Meh, even though I know the bugs are there and I can fix them, I just said it wasn't worth a new version.
For now at least. If more appear, I can release another one.
I'm tired.
You could rename it to v7.1 patch by the way, I'm fine with it. It's more of a bug-fixer than optimizer!
P.S. It's the I/O sched autoboot feature that was fixed, not governor.

which i/o is best? what are the differences between them?
thank you, all is going well so far

No need to new versions IMHO. The work is done.
Relax and rest for 2.3 arrive...
Feel free to take it, rename it and post onto nova's thread, it's in your hands.
Optimizer is not the word i guess too... i'll rename it.
I hope to release new versions with true opts or enhanced existent features.
Regards.
Sent from my LG-P970 using XDA App

IMHO InteractiveX is the best, but i don't mind lower performance but better battery last.
There are explanations inside nova's thread. Use the search...
Sent from my LG-P970 using XDA App

Huexxx, he was talking about I/O Scheduler, not governor.
Sent from my LG-P970 using xda premium

do i have to wipe all data? and install this?

memeru said:
do i have to wipe all data? and install this?
Click to expand...
Click to collapse
no men
just flash it

whats the different between the two

memeru said:
whats the different between the two
Click to expand...
Click to collapse
read 1st post plz

Sobralobo said:
Huexxx, he was talking about I/O Scheduler, not governor.
Sent from my LG-P970 using xda premium
Click to expand...
Click to collapse
Ops... I'm not used to tapatalk!!!
v(r) seems to be the best overall but with ups and downs in performance while sio is more consistent performance.
Try them for yourself... if you don't see the difference... both are good for you.

From what I've read on the main Nova ROM thread, on v7 for Froyo, WiFi meter readings do not correspond to true signal strength. This is due to the more important tweaks knzo did.
Just a thought, if those tweaks weren't in older versions (such as v4.5, which is imho, already a fast version, but WiFi signal readings are true), is it possible to modify Nova v7 (meaning, ditch the tweak or tweaks that make signal readings erratic) so that WiFi readings are true without ruining the performance?

It's possible... when I know which tweak has generated it and where is it...

After applying this patch has increased the power consumption of the system (in Тутор the System process and the Kernel). In a Terminal at one and the same Governor SmartassV2. Returned to made a backup.

PaulBort said:
After applying this patch has increased the power consumption of the system (in Тутор the System process and the Kernel). In a Terminal at one and the same Governor SmartassV2. Returned to made a backup.
Click to expand...
Click to collapse
Aha,
then:
- modify a caracter at nova in order to operate well with SmartassV2 (the same if you had applied the smartass patch, and you had already applied it because you are using it before according to your probes)
- modify a caracter at 11nov in order to set iosched on autoboot (if the same iosched is set, its the same)
- change superuser beta3 to beta4 (in your case you already have beta4 because freezing with beta3)
makes a difference in power compsumption at your OB...
You have different power comsumptions at different moments, I'm sure it isn't by the patch itself... because you had all implemeted yet!

Huexxx said:
Aha,
- change superuser beta3 to beta4 (in your case you already have beta4 because freezing with beta3)
Click to expand...
Click to collapse
Yes, I do patch SU yesterday, today - do your patch, but freezing (black screen when the application is started) sometimes present.

PaulBort said:
Yes, I do patch SU yesterday, today - do your patch, but freezing (black screen when the application is started) sometimes present.
Click to expand...
Click to collapse
Certainly the included versión (Beta4) is not the same as knzo's version (the date soesn't match) so i've created an alternative package for all who have problems with su.
Regards.

ajcantonio said:
From what I've read on the main Nova ROM thread, on v7 for Froyo, WiFi meter readings do not correspond to true signal strength. This is due to the more important tweaks knzo did.
Just a thought, if those tweaks weren't in older versions (such as v4.5, which is imho, already a fast version, but WiFi signal readings are true), is it possible to modify Nova v7 (meaning, ditch the tweak or tweaks that make signal readings erratic) so that WiFi readings are true without ruining the performance?
Click to expand...
Click to collapse
Hi there, I've already tried that method, modifying Nova v4.5 with kernel v7. first time try, I don't get overclock, still the same 1 GHz, and the WiFi signal still the same. But I notice that actually it work (even on Nova v7), the signal update in minutes. I've test it, if the phone connected to AP, wait for a minutes, and the signal will full. Then, go a little far away from AP, then the signal updates to low signal also in a minutes.. Well I don't know what's the problem.
Second try, I include overclock_p970_22.ko from Nova v7 (which I don't include it at first try), but it hang/freeze after come to "desktop". Well, it mean that v4.5 and v7 are not compatible
So I release battery, start it again, and go to recovery mod, and apply Nova v4 and v4.5 to have normally system. And when I came back to this forum, I see post that contain fix for Nova v7. Well, I have to try it
Thanks Huexxx, will trying it... Here we go with another night flashing and flashing again
Huexxx said:
IMHO InteractiveX is the best, but i don't mind lower performance but better battery last.
Click to expand...
Click to collapse
Well the same as i was.. I use InteractiveX that I think had more battery..

First post modified again...
The su fix from knzo only repush the program and set different permissions.
I've created three posibilities: beta4, beta3 ans latest stable.
I'll look into wifi problem.
Regards!

No wifi problem here.
And superuser works fine
Sent from my LG-P970 using xda premium

Hi folks,
There seem already many AOSP builds for NS, but I'm just pleased to share my personal build with you. I took the Google source and CM kernel/vendor as a base and have done lots of optimization work. My changes for NS after forking CM vendor were listed in the changelog of the initial build. Devs can check out commits on my github. It may worth a note that it's AOSP so never request extra features. No doubt I will keep it as stock as possible.
Credits:
clearly go to CM Team and all worked for our NS
steven676 for SurfaceFlinger and other patches
Download:
Final Build | MD5: 47af680bd273732d751de65656f62f7e
I don't hold the Nexus S any more, so if something in the final build does stupid for you, fall back to Build 6. And at last thank you again for your support.
Issues:
panorama preview. Check out CataHd's reply for the fix.
android-4.4.3-r1.1 build can be found in this reply. Panorama issue has been fixed.
You can find out all changes on my Github. Remember that AOSP ROM doesn't include Gapps, you have to install/flash it yourself.
Cheers,
Changelog:
Final Build
android-4.4.2_r2
merged some fixing patches from CM etc
Build 6
fixed random rebooting issue
saved about 3MB memory from the Kernel, thanks to pawitp
Build 5
android-4.4.2_r1
added swipe the pull-down panel to switch between Notifications and QuickSettings, thanks to CM/Slim
speed up statubar/notification drawer, thanks to kufikugel
changed dalvik heap parameters to reduce memory footprint (CodeAurora)
used double buffering instead of triple buffering
disabled hardware Vsync completely
fixed Screen record function, but in landscape only
increased the extra free memory to 12MB (you can change it in build.prop at any time.)
alpha 4
increased EGL cache size
switched to SW-based Vsync implementation by Google
fixed Keyguard layout for some languages
added a workaround to suppress the SU binary deprecated warning
few patches in Kernel and other minor fixes in SurfaceFlinger
alpha 3
merge in AOSP 4.4_r1.2
WebView black square issue was gone. Thanks to klusark for the wonderful porting work.
fixed app to sdcard function
enable low RAM feature in 4.4
root access fixed in Superuser with ART enabled
add Emoji support
Changes from init alpha Build:
merge the extra free kbytes patch from 3.4 Kernel
enable Swap for zRAM and KSM in Kernel side
Kernel 3.0.101

I will test this tomorow !

It's working fine. Very stock-ish feel. No FCs whatsoever (except for apps that are yet to be updated to fully support 4.3)

excellent rom thanks !!!!
only problem with superuser..I must install zip from recovery !!
then all ok !!

leap_ahead said:
excellent rom thanks !!!!
only problem with superuser..I must install zip from recovery !!
then all ok !!
Click to expand...
Click to collapse
Thanks for trying. But Superuser was fixed for weeks and works for me.

cn.fyodor said:
Thanks for trying. But Superuser was fixed for weeks and works for me.
Click to expand...
Click to collapse
no my friend .. I flash 3 times to make it sure and no work
if you go to settings superuser then u will se that u cant change anything in superuser settings..
also check with root checker..
but don't worry !! this is nothing for this super rom !! I try all aosp 4.3 rom and this is the best for me !!

leap_ahead said:
no my friend .. I flash 3 times to make it sure and no work
if you go to settings superuser then u will se that u cant change anything in superuser settings..
also check with root checker..
but don't worry !! this is nothing for this super rom !! I try all aosp 4.3 rom and this is the best for me !!
Click to expand...
Click to collapse
I tried changing settings in Superuser, every option works like charm. I always chased the changes of Superuser by Koush and the hack in that Superuser zip was included in my ROM. Afaik the tweak is just to run '/system/bin/su --daemon' for the root requirement.
OK, anyone else got superuser issue? xD

leap_ahead said:
no my friend .. I flash 3 times to make it sure and no work
if you go to settings superuser then u will se that u cant change anything in superuser settings..
also check with root checker..
but don't worry !! this is nothing for this super rom !! I try all aosp 4.3 rom and this is the best for me !!
Click to expand...
Click to collapse
cn.fyodor said:
I tried changing settings in Superuser, every option works like charm. I always chased the changes of Superuser by Koush and the hack in that Superuser zip was included in my ROM. Afaik the tweak is just to run '/system/bin/su --daemon' for the root requirement.
OK, anyone else got superuser issue? xD
Click to expand...
Click to collapse
Works fine here.

cn.fyodor said:
I tried changing settings in Superuser, every option works like charm. I always chased the changes of Superuser by Koush and the hack in that Superuser zip was included in my ROM. Afaik the tweak is just to run '/system/bin/su --daemon' for the root requirement.
OK, anyone else got superuser issue? xD
Click to expand...
Click to collapse
I don't know ..is not work here for that I flash the zip ..
sorry but is ok to flash the zip ? or I must try again without the zip ?
*now I remember that I get notification that su is out date and I forget to click ...
Downloaded and installed the latest superuser.zip and the su binary out of date notification is gone

Very good job. So happy to see the deveopment for our old phone continues.
Now, I can confirm Superuser doesn't work. Flashing SuperSU from recovery fixed the issue pretty fast.
Other than that the ROM is very solid and smooth. I tested SMS, Location services, Wi-Fi, left phone without a charge for a night. No problems so far. Will test bluetooth streaming later today in my car.
I have the same issue with calendar like any other non google build has, I have two of them, one is AOSP build another is Google's from the play store. That doesn't bother me.
Also, I still want to know what kind of "optimization" was done. Also, can anyone test MTP for me? I turned it on using USB Switcher, but my computer didn't recognize the device.
Great job, I hope the project continues.

@leap_ahead, velishka:
Let's rule out some exceptions about Superuser issue. Did you do factory reset before flashing? I hope the old Superuser app didn't make noise. Although you guys have fixed it manually, I still hope someone can paste the output of command 'getprop persist.sys.root_access' and check if the /system/xbin/su is running when you can't get root permissions. Thank you.

Hey,
just had a closer look at your build and found the interesting property 'ro.sys.fw.bg_apps_limit' in your build.prop which is set to 8. Are you sure this works in your build ? (I only ask because this was seen only in CM until now)...
Greetz

lagloose said:
Hey,
just had a closer look at your build and found the interesting property 'ro.sys.fw.bg_apps_limit' in your build.prop which is set to 8. Are you sure this works in your build ? (I only ask because this was seen only in CM until now)...
Greetz
Click to expand...
Click to collapse
Yeah, CM merged that commit from Codeaurora afaik. Bet you haven't checked out my github yet. xD

velishka said:
Very good job. So happy to see the deveopment for our old phone continues.
Now, I can confirm Superuser doesn't work. Flashing SuperSU from recovery fixed the issue pretty fast.
Other than that the ROM is very solid and smooth. I tested SMS, Location services, Wi-Fi, left phone without a charge for a night. No problems so far. Will test bluetooth streaming later today in my car.
I have the same issue with calendar like any other non google build has, I have two of them, one is AOSP build another is Google's from the play store. That doesn't bother me.
Also, I still want to know what kind of "optimization" was done. Also, can anyone test MTP for me? I turned it on using USB Switcher, but my computer didn't recognize the device.
Great job, I hope the project continues.
Click to expand...
Click to collapse
I connect the phone to car radio so it ok !
for root you can flash the superuser from koush too ...
use marmite kernel for mtp ...
I use other gapps so I don't have the problem with two calendar ..only one I get the green one ...
---------- Post added at 05:26 PM ---------- Previous post was at 05:25 PM ----------
cn.fyodor said:
@leap_ahead, velishka:
Let's rule out some exceptions about Superuser issue. Did you do factory reset before flashing? I hope the old Superuser app didn't make noise. Although you guys have fixed it manually, I still hope someone can paste the output of command 'getprop persist.sys.root_access' and check if the /system/xbin/su is running when you can't get root permissions. Thank you.
Click to expand...
Click to collapse
yes I make full wipe and ofcource factory reset ! with twrp recovery !

cn.fyodor said:
Yeah, CM merged that commit from Codeaurora afaik. Bet you haven't checked out my github yet. xD
Click to expand...
Click to collapse
Indeed, i didn't check it out yet. Link ?

lagloose said:
Indeed, i didn't check it out yet. Link ?
Click to expand...
Click to collapse
link :https://github.com/Juansheng
I can just say, very nice work, I'll try the rom soon

cn.fyodor said:
[*]Superuser fails (Workaround is to run '/system/xbin/su --daemon' via adb shell, then go to Superuser settings -> allow root access. Then it'll be fine even after a reboot. Thanks to leap_ahead for bug report)
[*]Gesture typing not working?
[/LIST][/HIDE]
Click to expand...
Click to collapse
or you can flash via recovery the superuser zip from here :http://download.clockworkmod.com/superuser/superuser.zip
for gesture I use other gapps that gesture is working without any problem

Wanna try this Rom, seems great..
Sent from my Nexus S i9023 using Tapatalk 4 Beta

Used this baby for 3 days now and have to say that it has the best memory management for 'low-memory' devices i've seen until now. Whatever you did cn.fyodor, very good work. !
I've noticed that CM has already reverted the commit for property 'ro.sys.fw.bg_apps_limit'. You should take care that this is not reverted in your sources because IMHO this is one of the essential things which gives us this better memory management. The relevant part can be found in line 105 of https://github.com/Juansheng/androi...s/java/com/android/server/am/ProcessList.java in your github.
Greetz

lagloose said:
Used this baby for 3 days now and have to say that it has the best memory management for 'low-memory' devices i've seen until now. Whatever you did cn.fyodor, very good work. !
I've noticed that CM has already reverted the commit for property 'ro.sys.fw.bg_apps_limit'. You should take care that this is not reverted in your sources because IMHO this is one of the essential things which gives us this better memory management. The relevant part can be found in line 105 of https://github.com/Juansheng/androi...s/java/com/android/server/am/ProcessList.java in your github.
Greetz
Click to expand...
Click to collapse
Thanks for your suggestion. Actually I once changed MAX_HIDDEN_APPS back the default value in Gingerbread for low memory devices nine months ago. Check this commit. ro.sys.fw.bg_apps_limit was just introduced by Codeaurora recently. And yeah CM have already reverted this prop and added a new prop for high memory (> 1.5GB) devices since more CM supported devices hold more memories nowadays. I'll ignore that commit.
Cheers,

Hi guys...i'm moving all discuttion of MK kernel for stock 4.1.2 from Sami OS thred to here so that Developemnt therad of SamiOS remains clean
Kernel & link
latest version with No teraing and almost bug free... here are some changes/review
#version3Latest Version Download
#version4One more version it should work for i9070P & some more features
NOTE : This is not my work , @mkaluza initiated it for CM and @PolishVodka made it available for Stock 4.1.2 you should thank them both
Below is Older version with some bugs mentioned below...so not recommended !
PolishVodka said:
Here is mkaluza's kernel for stock JB, working:
Click to expand...
Click to collapse
http://www.mediafire.com/?x6gw3cg833x8k51
To install Flash zip in cwm or twrp
Personally I use smartassv2 (more smooth than default dynamic which is more battery friendly ! )
1.2GHz OC
And some init.ds to make UI more smoother...which you can find here
You guys should check mkaluza wikis in github too . Lots of useful info there, especially this:
https://github.com/mkaluza/project-zen/wiki/Janice-performance-settings
and Dynamic governor related wiki:
https://github.com/mkaluza/project-zen/wiki/Dynamic-governor
To all
some more info about MK stock kernel
Ram available for user was 647 MB for me ( 650 i n latest ! )
multitasking and app loading was exceptionally better !
to newbies plz don't blindly follow cocore commands/ init.d here bcz there are some changes here..[B].if you don't understand or used to with kernel commands and things , I advised you to stay way from this kernel for little while till final build comes[/B]
you can go for it now
and keep one thing in mind nandroid back up created by phillz recovery won't work with simple CWM ( atleast it didn't work for me) though it works with phillz
so if you use this kernel and you need to take backup... flash cocore and do it ...or use temporary CWM
Some discussion
1st one here is about 1st build...so if you wasn't aware of it you can skip this one and go to review directly
hastalafiesta said:
Try to extract 4.1.2 ramdisk and put it in /efs, then flash mkaluza kernel.
I have followed this simple step to make it bootable on cm 10.1.
You can find the guide to extract it on mkaluza thread.
Click to expand...
Click to collapse
it won't work like that in stock 4.1.2 but
anyway @PolishVodka made one more build and it booted ..i tested it...there are some minor bugs in it which i reported and he will make final build and publish it... ( though i didn't get reply yet... may be this is because of time difference and when i reported there should be night
here is copy of my final review which i send to him
PSS : you got my reply about kernel booting right ?
Click to expand...
Click to collapse
Yes, yes I got your previous message.
No problem I can wait till tomorrow for your review. Thank you.
Click to expand...
Click to collapse
good stuff 1st
performance is exceptionally good ...i mean very very good especially with smartassv2
battery life is decent with smartassv2 & dynamic
no random reboot at all with OC @1.2
overall very stable
now some bugs
i alreay told yesterday about faint horizontal lines ( though they are not hurting much but still if they can be removed it'll be great ) & Jumpy UI
now one weird bug and it must be fixed ...is when we rotate screen it flickers very badly and turn offs this problem is lesser in smartassv2 & excessive in dynamic
see videos below
smartassv2
dynamic
you can see smartass v2 can open COC without waking screen while in dynamic i have to wake it ( actually screen doesn't look it self but it turns off so to wake it i hve to lock it and unlock it again ) ...and while seeing such Turned off scrren in complete Dark i can see screen on/off faintly which means process of loading is there but don't know why screeb offs
one more video...i'm not sure you can see it properly but whole track of tamplerun 2 is little bit jumpy
i'm hoping you can fix this bugs and make more smoother...you can ask cocafe for help in both of these or you can check his github for help to make UI smooth ( see master branch bcz in refresh version UI is not that smooth )
and don't abandon this kernel without fixing because it has really good potential , support this kernel as long as you can
and finally you should change default governor to smartassv2.. it's more resopnsive than dynamic , better performance and not much battery drain ... Newbies will like it more and experience user can chance if they want to use Dynamic and see difference by them self
Finally Thanks for this kernel
Click to expand...
Click to collapse
buffer overflow said:
Yes, is working but without boot animation.i chose Pegasusqplus and Sioplus. UPDATE:CRT Off animation not working even if it is checked.
Click to expand...
Click to collapse
isaak said:
Maybe you were using a custom boot animation?
Then there is no kernel support.
Click to expand...
Click to collapse
stock boot animation was working for me
yah it doesn't support CRT but i don't care. and IMO this feature is now worth to waste time
Cassiusss said:
Have you noticed that with Mk Kernel on JB, the screen seems to be a bit brighter than usual?
Click to expand...
Click to collapse
yah it's more brighter this is because you are comparing it with cocore not stock kernel ...in cococre auto brightness was lowered !
.

@PolishVodka please put something on github, or at least tell us what have you changed in the kernel, if we collaborate we could have a bugless kernel! @ChronoMonochrome can you help us to fix the errors mentioned in the op?

jineshpatel30 said:
it won't work like that in stock 4.1.2
Click to expand...
Click to collapse
This is not true.
Official Mk Kernel works with no problem on stock 4.1.2. I've used JB-4.1-stock-CoCore-cwm-6.0.3.4.boot.cpio.gz ramdisk, renamed to boot.cpio.gz and placed in the efs folder. Then installed the kernel 5.4.0 no swap.
jineshpatel30 said:
it's more brighter this is because you are comparing it with cocore not stock kernel ...in cococre auto brightness was lowered!
Click to expand...
Click to collapse
I'm comparing it with stock kernel... and it's brighter. I have no doubts.
Boot animation working for me too.
Camera opening makes the screen tearing. (on both PolishVodka and official versions)

Cassiusss said:
This is not true.
Official Mk Kernel works with no problem on stock 4.1.2. I've used JB-4.1-stock-CoCore-cwm-6.0.3.4.boot.cpio.gz ramdisk, renamed to boot.cpio.gz and placed in the efs folder. Then installed the kernel 5.4.0 no swap.
Click to expand...
Click to collapse
i was talking about 1st release by PolishVodka. not any other official build
and official versson wasn't suppose to be used with stock rom..it may work but there is chance you end up with something bad
I'm comparing it with stock kernel... and it's brighter. I have no doubts.
Boot animation working for me too.
Camera opening makes the screen tearing. (on both PolishVodka and official versions)
Click to expand...
Click to collapse
if you have no doubt then check with some brightness and illumination test app and you will see stock & this kernel have same brightness level !
Not only camera opening any rotation to screen makes it tears most of times ...
& this thread is not about official MK if you still using it have some problem then you should report it in official thread

@jineshpatel30 : How much free ram you have ?

Force said:
@jineshpatel30 : How much free ram you have ?
Click to expand...
Click to collapse
647 MB...i wrote is in OP as well
Why ?

jineshpatel30 said:
i was talking about 1st release by PolishVodka. not any other official build
Click to expand...
Click to collapse
You have answered to Reinkaros here http://forum.xda-developers.com/showpost.php?p=59215110&postcount=804 and Hastalafiesta here http://forum.xda-developers.com/showpost.php?p=59255043&postcount=821
They have suggested to use official MK Kernel but you instead have tried to use the ramdisk with the first release of PolishVodka... so that's why your phone failed to boot. First release of PolishVodka will never boot. And that's why he released a second version.
And this second version seems to be nothing else than the official Mk Kernel with included stock ramdisk and some more zram.
Both official and PolishVodka versions act the same.
Ah, and that brightness levels are the same means nothing if the screen is still brighter...
Anyway now i'm using PolishVodka version and i'll be glad to help.

jineshpatel30 said:
647 MB...i wrote is in OP as well
Why ?
Click to expand...
Click to collapse
Sorry,i didn't see it. 647mb free ram ?! I think i never had more than 320-350 free ram and now is double. That's a big change. Did you try to open 2 games or open a game and a chat app or browser? The other app in background close?

647 MB is total ram, not free ram.

I fix screen tearing and flickering in my Kernel using this commit by mkaluza. Hope it works for PolishVodka :good:
display-s6e63m0: revert "remove DDR_50_OPP requirements for screen on"

Force said:
Sorry,i didn't see it. 647mb free ram ?! I think i never had more than 320-350 free ram and now is double. That's a big change. Did you try to open 2 games or open a game and a chat app or browser? The other app in background close?
Click to expand...
Click to collapse
Oh i though you asked about how much ram is there for user to use sorry

Cassiusss said:
You have answered to Reinkaros here http://forum.xda-developers.com/showpost.php?p=59215110&postcount=804 and Hastalafiesta here http://forum.xda-developers.com/showpost.php?p=59255043&postcount=821
They have suggested to use official MK Kernel but you instead have tried to use the ramdisk with the first release of PolishVodka... so that's why your phone failed to boot. First release of PolishVodka will never boot. And that's why he released a second version.
And this second version seems to be nothing else than the official Mk Kernel with included stock ramdisk and some more zram.
Both official and PolishVodka versions act the same.
Ah, and that brightness levels are the same means nothing if the screen is still brighter...
Anyway now i'm using PolishVodka version and i'll be glad to help.
Click to expand...
Click to collapse
Gald that you ate willing to help
Zram enabled in polishvodka verson ?
I don't think so

Epirex said:
I fix screen tearing and flickering in my Kernel using this commit by mkaluza. Hope it works for PolishVodka :good:
display-s6e63m0: revert "remove DDR_50_OPP requirements for screen on"
Click to expand...
Click to collapse
@PolishVodka
Check this...

Force said:
Sorry,i didn't see it. 647mb free ram ?! I think i never had more than 320-350 free ram and now is double. That's a big change. Did you try to open 2 games or open a game and a chat app or browser? The other app in background close?
Click to expand...
Click to collapse
You got very very excited boy !!!!

You guys should check mkaluza wikis in github too . Lots of useful stuff there, especially this:
https://github.com/mkaluza/project-zen/wiki/Janice-performance-settings
and Dynamic governor related wiki:
https://github.com/mkaluza/project-zen/wiki/Dynamic-governor

Reinkaos said:
You guys should check mkaluza wikis in github too . Lots of useful stuff there, especially this:
https://github.com/mkaluza/project-zen/wiki/Janice-performance-settings
and Dynamic governor related wiki:
https://github.com/mkaluza/project-zen/wiki/Dynamic-governor
Click to expand...
Click to collapse
Added to OP

hastalafiesta said:
@ChronoMonochrome can you help us to fix the errors mentioned in the op?
Click to expand...
Click to collapse
Why asking me? I'm not a stock user and don't have janice too. Never had mentioned bugs. I can only suggest to use Interactive/ZenX to make some games lagless.
P.s. original thread of the tweak for increased RAM http://forum.xda-developers.com/gal...jb-kk-lp-ram-repartition-to-691-1-mb-t3043437 .

ChronoMonochrome said:
Why asking me? I'm not a stock user and don't have janice too. Never had mentioned bugs. I can only suggest to use Interactive/ZenX to make some games lagless.
P.s. original thread of the tweak for increased RAM http://forum.xda-developers.com/gal...jb-kk-lp-ram-repartition-to-691-1-mb-t3043437 .
Click to expand...
Click to collapse
Just because I know you have a great knowledge about kernel and so I thought about asking you.:good:

hastalafiesta said:
Just because I know you have a great knowledge about kernel and so I thought about asking you.:good:
Click to expand...
Click to collapse
Just wanted to say that mentioned bugs maybe not a kernel fault. It's difficult to advice anything especially because it's just reports about lagginess in some games. I'm not a hard gamer too. Maybe you can compare same things on various ROMs.

ChronoMonochrome said:
Just wanted to say that mentioned bugs maybe not a kernel fault. It's difficult to advice anything especially because it's just reports about lagginess in some games. I'm not a hard gamer too. Maybe you can compare same things on various ROMs.
Click to expand...
Click to collapse
Well i'm also not hard gamer..and i gave the examples where bugs was most clear
I took Dolphin browser to show screen tearing while rotation
Then COC for screen goes off during loading ( perhaps this happes in landscape apps only )
And finally TR2 to show jumpyness
But these bug weren't only in this things specifics...one can see jumpy UI in setting also , screen tearing in other apps like one person said in camera on/off
So it's not just about game and rom related bcz with same Rom and cocore any of given bugs is not there !
Anyway i didn't get any reply from PolishVodka since last build so may be he's too busy or may be this is it for this kernel !
@hastalafiesta
If you have some knowledge about kernel and you wants to continue you should start it from MK kernel Github bcz @Cassiusss was able to boot it directly on stock by boot.cipo.gz and you can ask PolishVodka if you stuck on boot , about how to fix it

Code:
***WARNING***
-READ CAREFULLY!!
YOU FLASH THIS KERNEL AT YOUR OWN RISK.I TAKE NO RESPONSIBILITY FOR ANY DAMAGE THAT MAY OCCUR DUE TO THE FLASHING OF THIS IMAGE.
I WILL NOT BE RESPONSIBLE FOR LOST DATA,BRICKED PHONE,OR ANYTHING OF THE SUCH.(PHONE EXPOLDES,OVERHEATS ETC)
THIS KERNEL IS ONLY FOR THE S5 MINI SM-G8OOF (Exynos) DO NOT FLASH THIS ON ANY OTHER DEVICE!
EOL (End of Life) ​
I will be creating a new thread for my N kernel - Stay tuned!​
UPDATED Linux kernel to 3.4.113 on 27-10-2016​UPDATED to v2.5 on 13-10-2016​
Code:
Changes in version 2.5
*Unlocked CPU frequencies 1500,300 and 200MHZ
*Switched to self built Linaro/Sabermod toolchain
*Added many more optimization flags
*Added DriveDroid support
Features
-Now supports Many different ROMS for the G800F
-Compiled with self built optimized Linaro/SaberMod toolchain ("LinaroMod")
-Unlocked CPU frequencies: 1500MHZ,200MHZ and 300MHZ
-Updated Linux kernel from 3.4.39 to the latest 3.4.113
-Added many optimizations (You can see all of the optimization flags in the makefile on the kernel source page)
-enabled graphite
-Added Drivedroid Support - http://softwarebakery.com/projects/drivedroid
-Fading LED's
-Added I/O schedulers
-zen
-sio
-fifo
-fiops
-tripndroid
-vr
-Added CPU governors
-zzmoove
-hyper
-alucard
-darkness
-nightmare
-wheatley
-smartassv2
-dancedance
-pegasusq
Click to expand...
Click to collapse
You will need Kernel Adiutor (free from the play store) or similar app capable of allowing you to switch I/O schedulers and
CPU governors in order to be able to change and set those.
I can recommend this.
http://forum.xda-developers.com/android/apps-games/kernel-adiutor-mod-singularity-kernel-t3333549
Click to expand...
Click to collapse
Known Issues
Let me know and I will try to fix them
Click to expand...
Click to collapse
Installation
I HIGHLY recommend that you do a full backup before flashing this kernel.I am not responsible if you lose any or all of your data.BACKUP!!
1.Download the "Spookcity_Kernel-MM"
2.Place the zip onto your phones storage
3.Reboot into recovery (Volume-Up + Home + Power button)
4.Select install
5.Flash the downloaded kernel
6.Go back a few times in TWRP.Select wipe -> Advanced wipe and wipe Dalvic/Art cache and the cache partition
If you do not do this you are very likely to experience strange issues.You have been warned.Do not report problems if you did not do this.
7.Reboot and hopefully enjoy.
Click to expand...
Click to collapse
Downloads
Spookcity_Kernel-MM
Click to expand...
Click to collapse
Sources
Toolchain - https://github.com/Spookcity/Android-Toolchains
Kernel - https://github.com/Spookcity/android_kernel_samsung_kminilte
Click to expand...
Click to collapse
Code:
CHANGELOG
[U]18-06-2017[/U]
-Switched to anykernel2
[U]31-10-2016[/U]
-Added zip for Bliss Rom
[U]13-10-2016[/U]
-Unlocked CPU freq 1500,200,300MHZ
-Switched to my self built toolchain
-Added many more optimization flags to the build
-Added DriveDroid support
-Added zip for Zephyr-OS
[U]24-07-2016[/U]
- Added zips to support more custom ROMS
[U]V2 - 23-07-2016[/U]
-Fixed RAMDISK to make it compatible and actually work with newer builds of CM13
-Changed SELinux from disabled to permissive to be in line with the "stock" CM kernel
-Added I/O schedulers
-fiops
-tripndroid
-vr
-Added CPU governors
-pegasusq
[U]V1 - Initial Release[/U]
Thanks to
-hennymcc and CTXz for bringing CM13 to our device! I used their kernel sources to build this.Without them I never would have been able to attemp this.
-DJ_Steve for his custom kernel.Without being able to look at his sources and cherry-pick some things I would also not have been able to do this.
-CurtisMJ Ditto same thing here.His kernel build and sources were very helpful to me.
-frap129 for his amazing toolchains!
-ArchiDroid
Anyone I may have left out sorry.I appreciate you all!
Click to expand...
Click to collapse
I hope you enjoy and please say thanks if you find this at all useful
XDA:DevDB Information
Spookcity_Kernel, Kernel for the Samsung Galaxy S5 Mini
Contributors
spookcity138
Kernel Special Features:
Version Information
Status: Beta
Created 2016-05-26
Last Updated 2017-06-18

Nice, finally some new development for our phone =)
I will test the kernel right away...
One thing that I would really love would be if you have the time to look into adding DT2W :angel:
Thanks for your work so far :good:
*edit*
booting went well. However WiFi doesnt work for me :/ I uploaded the logcat-output filtered for "wifi" to hastebin. If you need anything else for debugging let me know. Thanks to dual boot I will keep your custom kernel on one ROM
log

zaworka said:
Nice, finally some new development for our phone =)
I will test the kernel right away...
One thing that I would really love would be if you have the time to look into adding DT2W :angel:
Thanks for your work so far :good:
*edit*
booting went well. However WiFi doesnt work for me :/ I uploaded the logcat-output filtered for "wifi" to hastebin. If you need anything else for debugging let me know. Thanks to dual boot I will keep your custom kernel on one ROM
log
Click to expand...
Click to collapse
Thanks for trying out the kernel. That's weird about the WiFi. I have never had that happen in the bunch of times I have flashed it. I will def look into it.I'll have a look at the log, although at this point I'm also not that great at interpreting those, so it may not help. I'll see what I can do though
Sent from my SM-G800F using Tapatalk

can you tell me someone what is kernel?

br3acker said:
can you tell me someone what is kernel?
Click to expand...
Click to collapse
http://www.makeuseof.com/tag/linux-kernel-explanation-laymans-terms/

zaworka said:
Nice, finally some new development for our phone =)
I will test the kernel right away...
One thing that I would really love would be if you have the time to look into adding DT2W :angel:
Thanks for your work so far :good:
*edit*
booting went well. However WiFi doesnt work for me :/ I uploaded the logcat-output filtered for "wifi" to hastebin. If you need anything else for debugging let me know. Thanks to dual boot I will keep your custom kernel on one ROM
log
Click to expand...
Click to collapse
OK,well after looking at the log and trying to decipher it and then thinking a bit I have only come up with one possibility.Maybe somehow your wpa_supplicant.conf file located in /data/misc/wifi/wpa_supplicant.conf has the wrong permissions for some reason.If you want you could try to check and possibly change the permissions.If you decide to try this I would backup the file because you never know.
The permissions should be: Owner - wifi Group - wifi...
Owner read and write/Group read and write/ others none.
If your permissions are correct on that file the only other thing I could possibly think of to do if you wanted would be to delete that file,wpa_supplicant.conf.Only after you back it up it though because you will lose all of your passwords,and reboot.It should recreate it.Do that at your own risk though.This is all I have come up with because I have never had that problem,so it's a bit difficult.

I am sorry, I think the error was my fault and not a bug of the kernel. I think the build that I am running at the moment is one I build myself and used sabermod toolchain. I remembered that I had the same problem using DMPKernel on that build. I thought I was using one of hennymmc's builds by now - so, sorry for reporting but thanks for looking into anyways.
Unfortunately I tried both and didnt solve the issue ,the permissions were set correctly btw.
I just installed the CM13 on another partition but - unless I have a flashable zip file - I can not install your kernel on that one. Would it be possible to provide the kernel as .zip?

zaworka said:
I am sorry, I think the error was my fault and not a bug of the kernel. I think the build that I am running at the moment is one I build myself and used sabermod toolchain. I remembered that I had the same problem using DMPKernel on that build. I thought I was using one of hennymmc's builds by now - so, sorry for reporting but thanks for looking into anyways.
Unfortunately I tried both and didnt solve the issue ,the permissions were set correctly btw.
I just installed the CM13 on another partition but - unless I have a flashable zip file - I can not install your kernel on that one. Would it be possible to provide the kernel as .zip?
Click to expand...
Click to collapse
Sure thing.I updated the download section above and added a flashable zip.I think it'll work.

spookcity138 said:
Sure thing.I updated the download section above and added a flashable zip.I think it'll work.
Click to expand...
Click to collapse
Nice, that worked! Thanks for the effort :good:
Will test it over the next few days :fingers-crossed:

zaworka said:
Nice, that worked! Thanks for the effort :good:
Will test it over the next few days :fingers-crossed:
Click to expand...
Click to collapse
Good,I'm glad that worked.You thoughts and feedback are most welcomed.

Any chance this kernel hits the G800H for cm 13 too ?
I can be your tester

sasukesama said:
Any chance this kernel hits the G800H for cm 13 too ?
I can be your tester
Click to expand...
Click to collapse
Hey, I appreciate the offer. That is something I can look into at some point. No promises. In still trying to learn all of this stuff.
Sent from my SM-G800F using Tapatalk

spookcity138 said:
Hey, I appreciate the offer. That is something I can look into at some point. No promises. In still trying to learn all of this stuff.
Sent from my SM-G800F using Tapatalk
Click to expand...
Click to collapse
Sounds good
I think you can do the same (using the cm13 kernel and DJ_Steve kernel stuff) as he has a G800H version of his kernel

I use your kernel , you can repair the wifi ?

Abde77 said:
I use your kernel , you can repair the wifi ?
Click to expand...
Click to collapse
What's the problem with the WiFi exactly? I need to update this anyway. I will at some point.I've had no WiFi probs though.
Sent from my SM-G800F using Tapatalk

spookcity138 said:
What's the problem with the WiFi exactly? I need to update this anyway. I will at some point.I've had no WiFi probs though.
Sent from my SM-G800F using Tapatalk
Click to expand...
Click to collapse
Conducted any work on the development of the kernel? About sound problems and headphones like DJ_Steve , initially had no problems, and then there., maybe it depends on kernel version? Is there a chance to make all the improvements in version 3.4.39 ? (Google translation)

Oleggluk said:
Conducted any work on the development of the kernel? About sound problems and headphones like DJ_Steve , initially had no problems, and then there., maybe it depends on kernel version? Is there a chance to make all the improvements in version 3.4.39 ? (Google translation)
Click to expand...
Click to collapse
I actually haven't touched this recently at all.I've been spending too much time on the mess that is my AOSP build [emoji2]
I give up on that for now though.It's giving me a headache.
I will try to get back to this soon,as I don't even think it works with any of my builds.I don't know.I'm not even using this right now.
I never actually had any real audio issues with this however and I did use if for awhile,so that's strange.
Sent from my SM-G800F using Tapatalk

spookcity138 said:
I actually haven't touched this recently at all.I've been spending too much time on the mess that is my AOSP build [emoji2]
I give up on that for now though.It's giving me a headache.
I will try to get back to this soon,as I don't even think it works with any of my builds.I don't know.I'm not even using this right now.
I never actually had any real audio issues with this however and I did use if for awhile,so that's strange.
Click to expand...
Click to collapse
Also does not have wi-fi access in the new Assembly СМ13 from ayke with this kernel. I took apart your kernel and replace the ramdisk from the new build, wifi now works. (Google translation)

Oleggluk said:
Also does not have wi-fi access in the new Assembly СМ13 from ayke with this kernel. I took apart your kernel and replace the ramdisk from the new build, wifi now works. (Google translation)
Click to expand...
Click to collapse
I kinda remember this issue as well.Good to know about the ramdisk.
Its such a strange thing how only some experience the robotic voice...and you have no microphone problems with ayke's build either? Like it stops working after a phone call?
Sent from my SM-G800F using Tapatalk

spookcity138 said:
I kinda remember this issue as well.Good to know about the ramdisk.
Its such a strange thing how only some experience the robotic voice...and you have no microphone problems with ayke's build either? Like it stops working after a phone call?
Sent from my SM-G800F using Tapatalk
Click to expand...
Click to collapse
Robot voice I have never had. And mute has the same problem that error camera. If you kill the mediaserver, the microphone performance is restored. You can use the long-known app Mediaserver Killer. (Google translation)

Hello guys just wanted you bring to your attention the Exceed Kernel built by @kairi_zeroblade for us Verizon users, check out the thread here:
http://forum.xda-developers.com/note-4/snapdragon-dev/kernel-xceed-t3344742/post69474753
#######PLEASE FLASH KERNEL FROM INTERNAL STORAGE AND MAKE SURE THAT "SYSTEM" IS CHECKED UNDER "MOUNT" OPTIONS IN TWRP###########
#######All builds are based on the supersu 2.76 boot.img if you have supersu 2.78 and above, you will probably run into app permissions issues!!!##########
The Exceed 4F "V" varient is based on verizons latest PG2 kernel. It has been highly optimized by Kairi_zeroblade and includes:
All of the latest note 4 kernel sources so you have all of the most current fixes and optimizations from Samsung
Wakelock fixes
Exploit fixes
Ramdisk optimizations
GPU calibrations
It is compatible with note 7/s7 ports and stock TW Roms
Fully SELinux permissive(helps with installing viper4android and other mods)
And much more that I can't remember!
Kairi_zeroblade has all of the kernel settings pre tuned for amazing battery life and fast stable performace.
It is NOT recommended that you adjust the kernel settings EXCEPT for the ones available in Synapse.
Just flash and enjoy!
Do not forget to also flash the latest gpu drivers here:
https://drive.google.com/file/d/0B_3BNlXOVtO5bHp2MS12b291TjQ/view
These are based on the most current 805 adreno source (ph4 sprint I believe)
///////This kernel may give you the Volte and cloud (wifi calling) icons in the notification bar) see post 3 for my tip to disable Volte
Any questions or feedback, please post in the original Exceed thread^^^:good::good:
Side note........
///Kari_zeroblade does not like to add experimental features because they risk breaking the stability and battery life on the kernel. He keeps it simple and highly optimized. If there is a performance benefit you can be sure he will try to incorporate it though
Post#2 changelogs
Post#3 Volte icon
Post#4 UnderVolt/UnderAmp

######## BUILD 4M #######
2/2/17
http://forum.xda-developers.com/note-4/snapdragon-dev/kernel-xceed-t3344742/post70357447
Camera Improvements
Updated to the latest DPL2 source
SETCPU partially implemented(should give nice battery life improvements.)
Built in anykernel format so that should solve Supersu issues:good:
######## BUILD 4K ########
12/4/16
http://forum.xda-developers.com/note-4/snapdragon-dev/kernel-xceed-t3344742/post69924893
New Nightlies guys!!
As promised I did bring a solution to the fts_wakelock and some security updates from Google..
Grab the test builds for your device here
#######PLEASE FLASH KERNEL FROM INTERNAL STORAGE AND MAKE SURE THAT "SYSTEM" IS CHECKED UNDER "MOUNT" OPTIONS IN TWRP BEFORE YOU FLASH###########
#######All builds are based on the supersu 2.76 boot.img if you have supersu 2.78 and above, you will probably run into app permissions issues!!!##########
Thank you, and for your issues, just attach a log on your post and we will see what we can do for you.. :good:
Another Thanks to those who helped me get my build laptop fixed.. Merry Christmas to you..
######## BUILD 4F ########
Kairi_zeroblade:
Grab it from here
FG = is for F and G variants
V = is for Verizon
T = is for TMobile version
P = is for Sprint version
As promised, these builds can now be flashed on both NOTE 7 ports floating around here and at the same time with STOCK rom's too..if you ever find any issues do report with logs..else as usual I don't give a damn..I don't know why you're using a stock source compiled kernel with nothing and yet scores are lower than usual stock samsung kernel and you're like an Angry Bird jumping happily, when you have this project to "help and improve" (just my 2 cents) which has shown great potential (and worth IMHO)..
I'm sure you're aware you only now have a handful of devs supporting your device and if in the process you loose them all due to users being disrespectful and uncooperative then its your loss and not ours..
F Variants wifi needs testing though the necessary measures to make it work are already in place and has been checked..
Some patches to fix some Exploits were already added in, same thing goes with some upstream fixes from Google and CAF..Ondemand crashing is also been fixed (in my case) as I have tried to replicate the issue and grabbed something to ponder on..
Again for those who are supporting the project, Thank you very much!!
######## BUILD 4E ########
http://forum.xda-developers.com/note-4/snapdragon-dev/kernel-xceed-t3344742/post69363834
kairi_zeroblade said:
This test is specifically for the Verizon Note 4 running stock MM (latest, I forgot the build..lol) as this uses the updated ramdisk from that OTA update..this build also uses the Verizon Samsung Config so this is the proper kernel for your variant..please make sure you are on the latest MM Bootloader and Baseband for things to properly work (though @joemill tested this out and he had no issues to report)..this build also incorporates important kernel updates from the DPH2 (if I remember it right!!) from the N910P (Sprint, which will be supported once I get the laptop fixed, thanks to @joemill again for the boot.img dump)..I'll also include a GPU driver update package from the same update..
Enough with the chit-chat let the games for Verizon begin..
Grab the build here..
and GPU Drivers here..
Thank you very much to those who take time to read and enjoy my posts..
Click to expand...
Click to collapse
The kernel is based on the latest Verizon build PG2 I believe. As long as your bootloader is unlocked and on PD1 PD3 or PG2 (any marshmallow Verizon bootloader) then this should work for you
If you are still on 5.1.1 lollipop follow this guide to upgrade:
http://forum.xda-developers.com/not...firmware-safe-upgrade-to-marshmallow-t3402727
This kernel was tested on the latest paulpizz rom release.

I personally do not use VoLTE or WiFi calling and have never activated them or set them up on my phone. I never had either the cloud icon or the VoLTE icon with Paulpizz kernel, or Oscar kernel. When I flashed exceed the VoLTE icon appeared even though it is not enabled in the settings, "advanced calling" section.
I BELIEVE that those icons appear from flashing a modified kernel, more specifically a selinux permissive kernel(since this is the only kernel I've found that is permissive). Jasmine rom 6 had the icons appear with its selinux permissive kernel so in version 7 he left the kernel selinux enforceing.
Since I do not use VoLTE I went to others.Xml in the system/csc folder and edited this line:
<CscFeature_IMS_EnableVoLTE>TRUE</CscFeature_IMS_EnableVoLTE
To
<CscFeature_IMS_EnableVoLTE>FALSE</CscFeature_IMS_EnableVoLTE
Now the VoLTE icon is gone! and the 4glte icon is gray when connected to wifi instead of white all the time(I believe this means that 4glte radio is In a power save mode when not needed because you have a WiFi connection, also this improved my battery life quite a bit)
I personally would much prefer a kernel like exceed that has far better battery life and a selinux permissive kernel(so you can easy install vipers Android mods) even if it displays those icons.
I haven't had time to do anymore research but I would ask other verizon kernel developers(Paulpizz or Oscar since kari_zeroblade doesn't have a Verizon phone to test on) if there is a trick to remove those icons or if it is truly because the kernel is selinux permissive.

I would not mess around with any settings in kernel auditor or other kernel tweaking apps EXCEPT for synapse.
(Don't bother under clocking. The phone barely ever hits those top frequencys and when it does its better to complete the process fast and quick rather then hanging at a lower clock speed for a longer time. )
Undervolt and under amp in the synapse app can help your phone run cooler which will keep it from throttling cpu and gpu.
I personally run -45 uv and -12ua with zero issues in stability. If you undervolt you should always under amp to compensate for the drop in voltage. If you go to low your phone will just become unstable and probably lock up or reboot.
EVERY time you boot you will need to re apply those settings for safety.

Reserved~

The Synapse app days No UCI?
"Crack flashing is better than crack smoking"

Matthenson20 said:
The Synapse app days No UCI?
"Crack flashing is better than crack smoking"
Click to expand...
Click to collapse
Did you flash from your internal storage or external sd card? Also make sure that "system" is checked under the "mount" menu in TWRP
If it doesn't install then send us a twrp log after you make the attempt to flash the kerenl.

joemill said:
Did you flash from your internal storage or external sd card? Also make sure that "system" is checked under the "mount" menu in TWRP
If it doesn't install then send us a twrp log after you make the attempt to flash the kerenl.
Click to expand...
Click to collapse
Did all that, had synapse installed and did tweaks to voltages and amps, had a random reboot then synapse quit working
Will this work with N7 ports on? I'm running Chevy 2.7.3 build based on N5 port I believe
"Crack flashing is better than crack smoking"

Matthenson20 said:
Did all that, had synapse installed and did tweaks to voltages and amps, had a random reboot then synapse quit working
Will this work with N7 ports on? I'm running Chevy 2.7.3 build based on N5 port I believe
"Crack flashing is better than crack smoking"
Click to expand...
Click to collapse
That's strange. The reboot could be because you under volt or under amp too much. How far did you adjust them?
It should work with all ports but you might be the first person to test on that rom my friend. L

joemill said:
That's strange. The reboot could be because you under volt or under amp too much. How far did you adjust them?
It should work with all ports but you might be the first person to test on that rom my friend. L
Click to expand...
Click to collapse
I'll retry, I went -40 and -12, I'll try 30 and 8
"Crack flashing is better than crack smoking"

Matthenson20 said:
I'll retry, I went -40 and -12, I'll try 30 and 8
"Crack flashing is better than crack smoking"
Click to expand...
Click to collapse
Every phone is going to be different, some may not undervolt at all, don't worry too much if it doesn't. It will not save very much battery life at all and will only make the phone run slightly cooler. The kernel should run really cool and have great battery life by default

joemill said:
Every phone is going to be different, some may not undervolt at all, don't worry too much if it doesn't. It will not save very much battery life at all and will only make the phone run slightly cooler. The kernel should run really cool and have great battery life by default
Click to expand...
Click to collapse
Yes probably my fault, saw a new kernel abs started foaming at the mouth lol, going to reflash tonight and give it a go, will report in 24 hrs and let thread know
"Crack flashing is better than crack smoking"

Matthenson20 said:
Yes probably my fault, saw a new kernel abs started foaming at the mouth lol, going to reflash tonight and give it a go, will report in 24 hrs and let thread know
"Crack flashing is better than crack smoking"
Click to expand...
Click to collapse
Haha I don't blame you. It's hard to resist the temptation to tweak. Just flash let it settle and enjoy

joemill said:
I.
Since I do not use VoLTE I went to others.Xml in the system/csc folder and edited this line:
<CscFeature_IMS_EnableVoLTE>TRUE</CscFeature_IMS_EnableVoLTE
To
<CscFeature_IMS_EnableVoLTE>FALSE</CscFeature_IMS_EnableVoLTE
Now the VoLTE icon is gone! and the 4glte icon is grayed out
Click to expand...
Click to collapse
I'm sorry for the off topic comment, but thank you for this fix. I've been looking for a way to gray out that 4g icon while connected to wifi for awhile. :good: @joemill

kevintm78 said:
I'm sorry for the off topic comment, but thank you for this fix. I've been looking for a way to gray out that 4g icon while connected to wifi for awhile. :good: @joemill
Click to expand...
Click to collapse
I think the battery life is better with it disabled too

Still a no go in Chevy's 2.7.3 build. Must be because it's a Note 5 port, Synapse app just says no UCI. I installed from phone memory with system mounted. Cleared caches and everything
"Crack flashing is better than crack smoking"

I have been using this kernel successfully for the last week on the Note4 Grace Note7 based ROM v2. It has not had any crashes, or problems that I have been able to notice. I have not tweaked any of the kernel settings in the synapse app.
I have not specifically paid attention to the battery life after flashing, as I have not underclocked yet.
Is there an undervolt and underclock baseline that all Note 4s should be safe to start at?
Thanks.

signupstuffid said:
I have been using this kernel successfully for the last week on the Note4 Grace Note7 based ROM v2. It has not had any crashes, or problems that I have been able to notice. I have not tweaked any of the kernel settings in the synapse app.
I have not specifically paid attention to the battery life after flashing, as I have not underclocked yet.
Is there an undervolt and underclock baseline that all Note 4s should be safe to start at?
Thanks.
Click to expand...
Click to collapse
Don't bother under clocking. The phone barely ever hits those top speeds and when it does its better to complete the process fast and quick rather then at a lower clock speed.
You can adjust the undervolt and under amp though, this will help your phone run a little cooler so it shouldn't throttle the cpu as quickly. It will not really help battery life though and you need to manually set it again after each boot.
Start with -45 under volt and -12 under amp (you need to under amp to compensate for the under volt) if the phone runs smooth (no lag or reboots for a few hours) then push it a little more.
You won't do any damage to the phone. If you push it too far it will just reboot and you'll be on default exceed settings.

I hope this isn't too dumb of a question, but I was wondering if I should flash the gpu drivers on my verizon Note 4. Thank you

dhplap said:
I hope this isn't too dumb of a question, but I was wondering if I should flash the gpu drivers on my verizon Note 4. Thank you
Click to expand...
Click to collapse
Yes they should work on all Note 4s. I run it on mine