yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] :
Hi,

_motley will hate me :D

And another thing from Franco's thread:

Source: https://github.com/franciscofranco/mako/tree/android-msm-mako-3.4-jb-mr1

Wat do you think?

Thanks ;)

PS: I do not ask that this be implemented, I'm just asking your opinion and possibly if you think it would be useful, in this case yes it would be great to implemente it, yes somehow it is a request (like the GPU overclock) :D

I think some things can be nice...

I stop with the requests, I'm going out otherwise _motley will ignore me :silly::p:D, but it does not hurt to ask :);)

Have a nice day ;)
[Nexus 4 Original Android Development] thunderger:
@_motley:

Did you see https://android.googlesource.com/kernel/common/+/experimental/android-3.8 ?

Perhaps you can grab some stuff from this exp. kernel regarding memory usage, smp and perhaps F2FS. :)
[Nexus 4 Original Android Development] :
Hi,

Yeah, thanks for the link ;)

androidcentral

:)
[Nexus 4 Original Android Development] karanrajpal14:
Re: [KERNEL][Feb 25][b40] _motley kernel for the N4 (smp patches back for 4.2.2)

Can you tell me how I can apply this? I have no idea on how to use these scripts. Thanks in advance!
[Nexus 4 Original Android Development] azrash:
Re: [KERNEL][Feb 25][b40] _motley kernel for the N4 (smp patches back for 4.2.2)

read the second post in this thread. A good documentation there. Run them as a script in terminal first, and once you are sure about the settings, put them in init.d / userinit.d

Flowed from my Nexus 4
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Feb 25][b40] _motley kernel for the N4 (smp patches back for 4.2.2)

I would generally advise putting scripts in /data/local/userinit.d, that way they will survive a rom update. (well they do on cm anyway :p)
[Nexus 4 Original Android Development] azrash:
Re: [KERNEL][Feb 25][b40] _motley kernel for the N4 (smp patches back for 4.2.2)

True! And another reason why I stick with cm is the addon.d feature! Just modify the gapps script and you'll be able to make those apps you put in /system to survive a nightly flash. Works for other tweaks that you want to survive a nightly / update too!

Sorry for the hijack motley

Flowed from my Nexus 4
[Nexus 4 Original Android Development] chrone:
Re: [KERNEL][Feb 25][b40] _motley kernel for the N4 (smp patches back for 4.2.2)

I'll try to write my guide on pc later.

:)

Whoa nice! I didn't' know the kernel will look into that path. Will this work on stock rom with busybox?

Btw, will there be anyharm to disable hw overlays and enable force gpu rendering?

I found it's much smooth this way.

Sent from my Nexus 4
[Nexus 4 Original Android Development] _motley:
Thanks for all the suggestions and links guys. I'll take a look at this stuff.

That path won't work on the stock ROM unfortunately, just CM and some other custom ROMs. Perhaps we can look into it giving support since we have control of the ramdisk anyhow. That would be a nice feature for AOSP/stock.

I doubt those options will hurt anything. I often toggle force gpu rendering on several devices and have never had any issues with it. It will typically give higher Quadrant scores with it on, which is a bit telling about some of their tests.
[Nexus 4 Original Android Development] :
Thanks, thanks... and thanks ;)

It's true that this is a lot to look at here :D, maybe you'll find some interesting things that are worth...

Anyway thank you again to take a look in all this stuff it's really nice from you ;)

:)
[Nexus 4 Original Android Development] chrone:
Here you go:

create a txt file on your pc using notepad++, go to edit and select EOL Converstion set to Unix/OSX format

copy, paste all the codes, save and delete the .txt extension

copy the script to your /sdcard

using root explorer, copy the script to /system/etc/init.d, make sure to mount the /system as writeable

profit

oh okay. haha i'm asking too much. :D
[Nexus 4 Original Android Development] Crisisx1:
Re: [KERNEL][Feb 25][b40] _motley kernel for the N4 (smp patches back for 4.2.2)

So I just flashed motely kernel cm with trail razers cm10.1 bionic ROM..I first flashed the 37 version... Did a kernel reset as mentioned in op. 100% clean flash...

Question..am I now free to flash the newest any kernel over the 37 build
[Nexus 4 Original Android Development] chrone:
yeap, go straight ahead since you're already on 37 build. :D
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Feb 25][b40] _motley kernel for the N4 (smp patches back for 4.2.2)

Don't disable hardware overlays

http://rootzwiki.com/topic/28977-disable-hardware-overlays/

And force rendering can cause issues, leak memory, and make things slower.

Also, quadrant sucks, and anyone using it as any sort of test sucks, antutu is a bit more representative, still not that great due to all the fluctuations, but thats life.
[Nexus 4 Original Android Development] :
It's me again :D,

About the sounds enhancements from Faux123 I just see that her app is out on the Play Store with this comment:

Play Store Link

Maybe it's much easier for you...

It would be awesome to have this patch in _motley kernel :)

It boosts also the volume:

:)
[Nexus 4 Original Android Development] Crisisx1:
Re: [KERNEL][Feb 25][b40] _motley kernel for the N4 (smp patches back for 4.2.2)

Thank you. Just updated and everything was fine.

We'll see how battery life is with this kernel. I hope its better then the stock cm10.1 kernel...didn't really get great battery life.

Best battery life I've experienced was with the stock pa3.0 kernel by moles.
[Nexus 4 Original Android Development] chrone:
i'd like to know regarding this overlay and force gpu rendering, seems there's no legitimate documentation on this.

checked "disable hw overlays" on galaxy nexus slowed down performance like a lot, everything seemed so laggy. but checked "disable hw overlays" on n4 made everything way way smoother. i also didn't notice heavy ram usage on nexus 4, still 1.3-1.5gb available each time i checked.

i googled around and found contradict report on checking the "disable hw overlays". it fixex screen flickering and compatibility with hdmi display, mx-player choppy playback with hw accelerated, and some games compatibilities.

and as for "force gpu rendering", checking the option make scrolling on some apps even system apps smoother.

my two cents are current smartphone with advanced gpu will benefit from checking the "disable hw overlays" and "force gpu rendering".

resources:

http://forums.androidcentral.com/sp...-graphics-issues-since-jelly-bean-update.html

https://groups.google.com/forum/?fromgroups=#!topic/mx-videoplayer/jLO_Q-ybBYs

glad you like it. love the geeky tweaks from this kernel. hahaha command line rules the world! :good:

due to been doing lots of testing, i can't report battery life on this kernel. hope tomorrow i can also report with logs on 3g battery life.

quick take on the msm_hsic_host still over 5% on b40 build, though.
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Feb 25][b40] _motley kernel for the N4 (smp patches back for 4.2.2)

Force gpu rendering is more of a mixed bag, on newer phones with enough ram to eat the hit that it causes, and newer faster GPU's and better drivers it properly won't be a issue. So yeh, turning it on can be helpful, but may break some older apps, or apps that do optimisations about which bits are drawn by the GPU or not.

http://developer.android.com/guide/topics/graphics/hardware-accel.html

Top of this page lists some issues that can happen if you force it on.

As far as overlays, any performance improvement due to turning then off really should just be a placebo, as doing so will eat more ram, and cause more work, in some cases you may have to, but that should only be on devices which have had aosp ported to then, rather than being native, and where the blobs have issues (think the s2 had that issue early on).

If an app is having issues with it on, then that app is broken, are you using hw+ on mx? As that's supposed to help.

But really, developer options are just that, options for devs to use when testing or developing apps, to see where the issue exists, and you shouldn't need to change them for normal usage.
[Nexus 4 Original Android Development] chrone:
Re: [KERNEL][Feb 25][b40] _motley kernel for the N4 (smp patches back for 4.2.2)

Very well put. Thanks! :)

I don't do benchmark, but when i do on first hand on, i only go for androbench, glbench and vellamo just to make sure i get the same performance as on anandtech review.

Yeah, i used hw+ on mx. It gets choppy sometimes. Hehe

Sent from my Nexus 4
[Nexus 4 Original Android Development] Kocai:
From my experience, the msm_hsic wakelock is volatile albeit _motley has added the patch on b39. It should exist though since it somewhat keeps the modem "alive."
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Feb 25][b40] _motley kernel for the N4 (smp patches back for 4.2.2)

As long as the radio interface and hsic wakelocks are about the same, you are fine, it will never be zero as it will be held while mobile data is working.

I just do an antutu run from time to time to see how things are, thanks to the krait stuff I normally get 21k ish, not that I noticed the phone feeling any faster once they where merged, but thats benchmarks for you, mostly hitting small subsystems that don't actually have much impact on the overall feel.
[Nexus 4 Original Android Development] mundixx:
Re: [KERNEL][Feb 25][b40] _motley kernel for the N4 (smp patches back for 4.2.2)

Guys, is there undervolting right out of the box? Like, if my fast binned n4 has specific voltage tables? Last time i used the kernel was still at b20++..

And thank you chrone for posting PA's colors. :D

Sent from my AOSPA Nexus 4
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Feb 25][b40] _motley kernel for the N4 (smp patches back for 4.2.2)

Yes, yes, yes (10 chars) :p
[Nexus 4 Original Android Development] starscream92:
Finally able to do a medium daily usage on b40!!! Lately had been forced to reboot my phone a couple of times due to CM10.1 being retarded, in addition to voltage testing. Here's what I have so far today (will post screen pics later at the end of the day!):

Configuration:

- GPS on

- HSPA+ on (little to no WiFi)

- Screen on auto-brightness

- Undervolted by -37.5 mV from Motley's fast-bin pre-UV

- Interactive, Westwood, Row, 2048 look-ahead, FSYNC and DYN-FSYNC on

- 304 MHz / 1512 MHz

- Greenify to hibernate Maps and Facebook :p

Battery consumption:

- Remaining %: 75%

- Current stand-by time: 8 hours

- Screen-on time: 1+ hour

- msm_hsic_host held my phone awake for 12 minutes

- radio-interface held my phone awake for 17 mins

Usage/Notes:

- A little bit of Maps on the way to work

- Google Talk, Reddit, Twitter, Facebook (though not super heavy on Facebook)

- No music/media playing (which is weird for me since I usually always listen to music while commuting)

- No data drops at all.

I'm loving B40! Thanks Motley!
[Nexus 4 Original Android Development] Kocai:
Re: [KERNEL][Feb 25][b40] _motley kernel for the N4 (smp patches back for 4.2.2)

Yes. That's what I'm trying to say. I didn't want him to worry too much about it because I notice that if you're on 3G, the hsic wake lock is greater than if you're on 2G and or using WiFi.
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Feb 25][b40] _motley kernel for the N4 (smp patches back for 4.2.2)

Aye, i quoted the wrong person :D :p
[Nexus 4 Original Android Development] chrone:
Re: [KERNEL][Feb 25][b40] _motley kernel for the N4 (smp patches back for 4.2.2)

Thanks guys. :) I'm not that worry and i do know what the msm_hsic_host is for. Hehe

Coming from thracemerin's kernel which is stock with caf patches, under same usage the wakelock in average was around 2-3%. He did a great job on the patching side. :thumbup:

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

[Kernel][GPL][anykernel] msm_hsic_host wakelock fix (4.2.2 sources!)

Used to have 10% wakelock on stock kernel, so 5% on _motley, no worries. :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] mundixx:
Re: [KERNEL][Feb 25][b40] _motley kernel for the N4 (smp patches back for 4.2.2)

Hey chrone.. Do you have other popular presets aside from the PA ones? Like a spreadsheet or compilation perhaps? :D

Sent from my AOSPA Nexus 4
[Nexus 4 Original Android Development] volty500:
Just for grins and chuckles, how much are people underclocking past stock? I've been running -75mV now for a couple of weeks (on the various builds) with no issues. It helps Ingress last slightly longer lol battery suck.

And motley, I cant help but rave about the kernel. Battery life, performance, stability... I've tried most of the kernels out there, keep coming back to yours. Seriously good work, very very much appreciated.
[Nexus 4 Original Android Development] thracemerin:
At one point I managed to get to -150mV on my fast binned chip and it passed a stability test, then a few days after it started SoDing on me randomly and I've been too scared to UV it again :p
[Nexus 4 Original Android Development] IAmAN00bie:
I'm able to run at 600mV on every CPU step < 1026MHz. How? Not really sure. I've tested those steps in all sorts of benchmarks to be sure, and not a single reboot has happened.
[Nexus 4 Original Android Development] th3xeroeagle:
Re: [KERNEL][Feb 25][b40] _motley kernel for the N4 (smp patches back for 4.2.2)

Wow b40 is amazing! Just look at these!

Great work sir.
[Nexus 4 Original Android Development] chrone:
Re: [KERNEL][Feb 25][b40] _motley kernel for the N4 (smp patches back for 4.2.2)

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

Nexus 4 Color Settings [spreadsheet]

It's all there. Need to reverse the gamma sheet to init.d script, run it, and take the gradient value from trickster mod beta or faux display.

Kind of time consuming though. Been switching back and forth between faux stock LG, PA brighter, and PA contrasty lately. Hehe

Am looking for the most natural colors with 6500k warm white.

Sent from my Nexus 4
[Nexus 4 Original Android Development] jassycliq:
Try these :P

I tried converting it to Faux's interface but it didn't translate them correctly. The blues were overpowering compared to the way they're suppose to be.
[Nexus 4 Original Android Development] thracemerin:
They should translate directly to motley's init.d, i'm not sure how faux does his conversions.
[Nexus 4 Original Android Development] jassycliq:
Oh, I'm aware of that, but I wanted to use Fauxs kernel with those colors but it wouldn't work out for some reason :(

I know exactly how the colors look with the phase beam live wallpaper and when converted to Faux's gamma they weren't the same.
[Nexus 4 Original Android Development] thracemerin:
I had the initial thought that if you plugged them into motleys interface and then looked in the sysfs files that control faux's interface it would show you the values, but I dont think that's true unfortunately.

I'm not totally familiar with Faux's interface, but I'm assuming that you could figure it out by looking at the same preset from Faux and from Motley and figure the math out, or is that what you tried to do?
[Nexus 4 Original Android Development] jassycliq:
Ah, that was the issue then. I plugged in Francos settings then just looked in Fauxs app to try and save the settings but they weren't correct :l oh well, not gonna spend a ton of time trying to figure it out honestly, maybe someone else will :)
[Nexus 4 Original Android Development] thracemerin:
It's sort of unfortunate that these color control interfaces got developed separately and that a consensus couldn't be reached so they all worked the same way, but that's the way things go sometimes. I don't want anyone to think I'm complaining, it's just an observation, and it's not the first and only time something similar has happened.
[Nexus 4 Original Android Development] jassycliq:
Yeah sad thing really. Don't want to start a flame war but I don't understand why Franco won't use Faux's code even though Franco has admitted that his interface is flawed. :(

Anyways, hope that one of these days, those developers forget the beef and just work together. More would be achieved that way :)
[Nexus 4 Original Android Development] chrone:
b40 interactive 3g report

Dear _motley,

Here's my highlights on b40's interactive governor settings on 3G battery life with autosync for 2 gmail and 1 contacts enabled:

TCP congestion Westwood

SIO 512 but later changed to CFQ 512

Set max core to 2

Fsync on

Dynamic fsync off

Highspeed_freq 810000

Temp limit freq 810000

Min cpu freq 304000

Max cpu freq 1350000-1512000

Vibrate 70

Battery life : 9 h 17 m 53 s (95% to 25%) [7.5% drain/hour]

Screen on time: 1 h 22 m 59 s

"radio-interface": 1 h 6 m 17 s (3977 s) Cnt:(c/wc/ec)2740/0/0 11.9%

"msm_hsic_host": 52 m 48 s (3168 s) Cnt:(c/wc/ec)10713/3188/0 9.5%

All essential bug reports as per attached, screenshots included. Hope this helps. :)
[Nexus 4 Original Android Development] hospital349:
Hey folks.

I added _motley Kernel to [Directory] MAKO: ROMs & Kernels. I recently completed the thread and would love to expand/improve on it in the future. If anybody has any ideas, feel free to throw me your insights. :)
[Nexus 4 Original Android Development] Kocai:
@chrone: I may be wrong about this but that high count of radio-interface wakelock means you're in an area with unstable or poor reception. Possibly the 3G connection your area is not good? The signal strength in status bar may not report the actual reception. AFAIK, -90 dBm will show as full bar.Try see your signal strength in about phone - status.

1 and a half hour screen on time is not good at all. Have you tried switching to 2G? Just to test if you can get longer screen on time.

To be honest I think the mobile internet connection in Indonesia is so poor. But hey what can you expect from $6/month for 2GB quota?

I'm sorry if this post unrelated to the kernel.
[Nexus 4 Original Android Development] chrone:
yeah, i guess you're right. thanks for the info. :)

high gprs-stall occured 137 times. at office i usually get -79dB 3G, full 4 bars right now. the screenshot was taken at the parking basement, thus displayed only 3 bars. at home, i usually get -90 to -101dB 3G, roller coaster mode from 2 bar to 3 bars. lol :D and only at home i switched to 2G or 2G+WiFi (-70-89dB 2G).

switching to 2G, WiFi, WiFi+2G, or WiFi+3G did improve screen time, reaching 4-5 hours screen on time as i recall, i forgot the uptime though. the bad 3G battery life didn't happen when i was still on galaxy nexus, stock lover here (stock rom/baseband/kernel/recovery), same usage pattern and location. so here i am in a journey to find which kernel is the best for 3G battery for my n4. :)
[Nexus 4 Original Android Development] _motley:
Another couple things to help with battery. Have you tried using "GSM auto (PRL)" instead of the default "WCDMA preferred"? You can use the app "Phone Info" to change it, but it doesn't survive a reboot. I think someone mentioned some other app to make it permanent.

WCDMA preferred - The GSM phone is capable of using both 2G and 3G data communication and when signal strength is low 3G is favored more.

GSM auto (PRL) - The GSM phone is capable of using both 2G and 3G data communication and when signal strength is low 2G is favored more.

Also, if you are on WiFi all the time, you can check your build.prop to see what the wifi scan interval is. I have mine set as below permanently, but I can't recall what stock is. It should also help with battery. System Tuner will also allow you to set it.

wifi.supplicant_scan_interval=180
[Nexus 4 Original Android Development] chrone:
Re: [KERNEL][Feb 25][b40] _motley kernel for the N4 (smp patches back for 4.2.2)

Nice info! Will try the gsm auto prl. :thumbup:

Sent from my Nexus 4
[Nexus 4 Original Android Development] jassycliq:
Re: [KERNEL][Feb 25][b40] _motley kernel for the N4 (smp patches back for 4.2.2)

Can also dial *#*#4636#*#* in dialer to get there =)
[Nexus 4 Original Android Development] chrone:
dear _motley,

sorry for the noob question, but what is the difference putting "" and no "" on init.d script?

also, does my init.d tweak below from various sources have the right syntax?

#!/system/bin/sh

#enable fsync
echo 1 > /sys/class/misc/fsynccontrol/fsync_enabled

#disable dynamic fsync
echo 0 > /sys/kernel/dyn_fsync/Dyn_fsync_active

#read ahead
echo 1024 > /sys/block/mmcblk0/queue/read_ahead_kb

#TCP Congestion
echo "veno" > /proc/sys/net/ipv4/tcp_congestion_control

#Disable Fast Charge
echo 0 > /sys/kernel/fast_charge/force_fast_charge

#stock vibration intensity
echo "70" > /sys/class/timed_output/vibrator/amp

#Eliminate unnecessary debug
echo 0 > /sys/module/lge_touch_core/parameters/debug_mask

#set max core to 2
echo 2 > /sys/module/auto_hotplug/parameters/max_online_cpus

#set min-max cpu freq to 304-1350MHz
echo "304000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo "1350000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

#set scaling governor interactive or ondemand
#echo "interactive" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo "ondemand" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

#set highspeed to 810MHz (interactive governor only)
#echo "810000" > /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq
#set boostpulse duration to 50ms
#echo "50000" > /sys/devices/system/cpu/cpufreq/interactive/boostpulse_duration

#enable io_is_busy (ondemand governor only)
echo 1 > /sys/devices/system/cpu/cpufreq/ondemand/io_is_busy

#set thermal throtle cpu freq to 810-1134MHz (4-8)
echo 4 > /sys/module/msm_thermal/parameters/min_freq_index
[Nexus 4 Original Android Development] :
Hi,

Normally both echo "something" or echo something (so without " ")works. I already tested and it works for the values. Why put " " or not, I don't know... Some init.d scripts have them, some haven't them :D

I don't put " ", I'm too lazy :D

It seems good, you can verify with a file explorer for example if it works by following the path of your script and check the value or by doing cat /sys/***/****/ etc... in a terminal emulator.

:)
[Nexus 4 Original Android Development] chrone:
Re: [KERNEL][Feb 25][b40] _motley kernel for the N4 (smp patches back for 4.2.2)

Thanks dude. Reboot and profit. All my settings still there. Haha

Sent from my Nexus 4
[Nexus 4 Original Android Development] jarayn:
Does this kernel need all these scripts to perform? I just put it on there and it seems good,I just feel I'm missing out lol
[Nexus 4 Original Android Development] thracemerin:
Stock settings are pretty good, the scripts are just to tweak things for more battery, more performance, different colors, etc..., if you're happy with stock, there's no reason to change. I personally run this kernel with the stock settings practically all the time and I'm very happy with it.
[Nexus 4 Original Android Development] lbtc777:
Re: [KERNEL][Feb 25][b40] _motley kernel for the N4 (smp patches back for 4.2.2)

Agree with this info. Also very helpful if you are regularly in a place where mobile data signal is low. Not only does it improve your battery life but you will have more stable data. Its a lifesaver for me at work.
[Nexus 4 Original Android Development] PoisonWolf:
I can get 6 hours screen on time out of mine all on WIFI and web-browsing using a dual-core setup. I think the tweakability is what makes this kernel so awesome.
[Nexus 4 Original Android Development] thracemerin:
That's what makes custom kernels awesome, everyone gets what they want out of their devices :D
[Nexus 4 Original Android Development] csunny95:
hi, I am using motley kernel. Can I disable the thermal throttle? when I go to the /sys/module/msm_thermal/parameters/enabled. It has already set to N before I setting it. Then, How can I turn this feature off? As the cpu frequency keep going down when I playing intense game