yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] himzz0007:
the quality profile in sound has been removed....can u put it back...i don"t see then in the sound in synapse.
[Nexus 4 Original Android Development] defconoi:
ah good find, I guess I could switch default min to 384
[Nexus 4 Original Android Development] 0.0:
You are awesome! So many kernel updates, it's beautiful :)
[Nexus 4 Original Android Development] defconoi:
Thankyou :)
[Nexus 4 Original Android Development] himzz0007:
like i said u r truelyyyyyyyyyy awsomisttttttttttttttttttttttt:D:laugh::good:
[Nexus 4 Original Android Development] d9ny:
I'm on Liquidsmooth 3.2 which should i flash? the AOSP or CM version?
[Nexus 4 Original Android Development] 0.0:
I think that ROM uses caf, so use the CM version

Sent from my Nexus 4
[Nexus 4 Original Android Development] defconoi:
After you switch to the motox I'm gonna have to find a new ROM. Any suggestions on features & performance close to CM11 and temasek? I'm holding off until a 64bit nexus.
[Nexus 4 Original Android Development] 0.0:
I'll keep the temasek one updated :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] shadeMe:
Hmm, the r4 release didn't cause a crash (thusfar) while watching videos (tested by playing back regular h264 content for an hour) but I still had a paging error. Was trying to start reddit news. It FC'd the first time, with the crash reporter mentioning that exception was raised by native code (saw SEGV_MAPPER mentioned). The second time caused the kernel panic.

Edit: There were multiple mentions of userspace processes being killed at the behest of a kswap thread (iirc) in that log. Am I correct in assuming that this is due to my setting the swappiness tunable to zero (as per faux's personal settings, I don't use the Zram - didn't notice any perceptible difference in performance when I did)?

And on the same note, how do I stop the kernel/OS from killing processes so frequently?
[Nexus 4 Original Android Development] defconoi:
this is weird, i just played 4 tv shows h264 with no issues, not denying their is one, but what rom are you using and what settings

exactly

UV at all? gpu UV? What im gonna do next tomorrow is revert those commits I reverted earlier and revert a few others that may be it, now the crash is saying the adreno driver crashed. Will take a look at this more tomorrow. If you dont use swap, dont adjust the swappiness tunable, there is no need to.
[Nexus 4 Original Android Development] gorilla p:
I added Synapse profiles for 87uR4 on bit.ly/makostuff

Battery

Bat-Bal

Balanced

Performance
[Nexus 4 Original Android Development] Benjamin_L:
From time to time autobrightness works the wrong way and the screen is always too dark, like an offset as the brightness still changes. Is this a kernel or rom bug?
[Nexus 4 Original Android Development] montbazon:
I don't have any trouble with mx player hw+ mode. Even those are 1080p. I did CPU OC/UV and gpu oc.
[Nexus 4 Original Android Development] shadeMe:
I'm on paranoid android 4.6 beta 1. Im undervolting my Faster binned CPU by 125mV across the board, with 650mV being the lower limit (81 and 162mhz are at 650mV and the rest in line with the global setting). Min frequency is at 81 and max is at stock frequency. Gpu voltages are at 925,1000 and 1100; interactive governor and frequency. range 128-400mhz.

I just got 2 more hours of video playback without any crashes, although the phone did freeze up for 10 seconds once. That being said, r4 has been the most stable of the u87 releases.
[Nexus 4 Original Android Development] Sacob:
i can't use synapse. it says "No UCI support detected". Any help?
[Nexus 4 Original Android Development] whatthefish:
Flash UKM brother.
[Nexus 4 Original Android Development] gorilla p:
650 is pretty low. I'm fast binned and things get shaky below 700@81mhz. I'd recommend upping to 675@81mhz/25 across the board for better responsiveness
[Nexus 4 Original Android Development] shadeMe:
Hmm, but that configuration is rock steady on u84. [MENTION=1316336]defconoi[/MENTION], does voltage have any bearing on responsiveness, other than affecting stability?
[Nexus 4 Original Android Development] Almayce:
Hey there defconoi, the new version ship shapes very well. The performance is good while the battery has improved a tad. I have been seeing like half hour of sot more on 3 consecutive charges. I would suggest keeping whatever made the change happen and just polishing the kernel :) anyways, good job!
[Nexus 4 Original Android Development] defconoi:
Voltages can effect performance if too low and stability randomly between different kernels and configurations. I can UV more for instance running a CM rom compared to L. I'd like if others could test HD video for more than an hour today if possible.
[Nexus 4 Original Android Development] manueltts:
Look at "gamma" options in Synapse, at the bottom you can choose between linear and exponential mapping. Choose linear.
[Nexus 4 Original Android Development] Benjamin_L:
You don't understand the problem. The screen goes darker without doing anything, auto brightness works fine most of the times but sometimes it gets darker and only a reboot helps.
[Nexus 4 Original Android Development] BelzIgoh:
I don't have auto brightness problem. I'm sure this is not kernel related. Maybe ROM brightness settings?

What ROM are you using?
[Nexus 4 Original Android Development] Benjamin_L:
I'm running latest mahdi
[Nexus 4 Original Android Development] BelzIgoh:
I found that few people in Mahdi thread also had the same problem as you. Maybe you can search there. :good:
[Nexus 4 Original Android Development] Benjamin_L:
Thank you, I thought all sensor stuff is kernel related so I started asking here first
[Nexus 4 Original Android Development] xenyz:
It's a software problem. Kill the process /system/bin/sensors.qcom to get the light sensor (and auto brightness) going again.
[Nexus 4 Original Android Development] CamoGeko:
Excellent kernel and thread mate. Is there anything specific I need to do if I'm coming from Hellscore?

PS. Have any of the wake features been added yet?

Sent using Android L
[Nexus 4 Original Android Development] defconoi:
New kernel incoming with multicore power saving. It will help save battery even more, once the alpha version of the new version is complete upstream I will be importing that as well.
[Nexus 4 Original Android Development] defconoi:
Just dt2w since sweep 2 wake has some battery draining and stability issues. Make sure u flash your stock romkernel over hellscore and remove any conflicting settings for a good experience.
[Nexus 4 Original Android Development] defconoi:
ion-storm - update version to 87u-r5
Richard Zhao - ARM: add cpufreq transiton notifier to adjust loops_per_jiffy for smp
Vincent Guittot - ARM: 7011/1: Add ARM cpu topology definition
ion-storm - Bring back CPUPOWER, this was long ago depreciated in favor of: https://lkml.org/lkml/2014/8/11/188 but it is currently in an alpha state and is not ready yet, once it is adopted and bugs are fixed, we'll import the new power savings, right now there is no power aware scheduling, so lets do this for now -defcon/ion-storm
franciscofranco - sched: set sched_mc_power_savings to 2, which is the highest power saving possible value for this tunable. Basically according to http://elinux.org/images/1/1d/Comparing_Power_Saving_Techniques_For_Multicore_ARM_Platforms.pdf this tunable provides serious power saving improvements close to the power savings of hotpluging cores. Since in this Kernel we're using always a minimum of 2 cpus online at any time during screen off we might actually benefit from this because this feature packs tasks together and try to bind them to cpu0, which in theory will let cpu1 idle longer, thus improving battery life.
hellsgod - Update ARM topology and add cpu_power driver
ion-storm - sched: Remove stale power aware scheduling remnants and dysfunctional knobs It's been broken forever (i.e. it's not scheduling in a power aware fashion), as reported by Suresh and others sending patches, and nobody cares enough to fix it properly ... so remove it to make space free for something better.
ion-storm - sched: Remove stale power aware scheduling remnants and dysfunctional knobs
ion-storm - Revert "sched: Remove stale power aware scheduling remnants and dysfunctional knobs"
ion-storm - Revert "cpupower: Remove mc and smt power aware scheduler info/settings"
Alucard24 - Trying to fix rr. Use single workqueue allocation for rpm_smd.
ion-storm - Revert "Revert: rb_tree updates causing instability"

AOSP/L

CM11
[Nexus 4 Original Android Development] defconoi:
Dupe post
[Nexus 4 Original Android Development] ijustzeke:
I can't seem to use Synapse too. Its saying the same thing. "No UCI Support detected.

What's a UKM? Where can I find it?

Edit: And oh, I've been using this kernel for 2 days now. And I noticed something. My notification light always is always showing red when the phone is getting hotter. How can I remove this? Is this kernel related or is this a problem in the ROM?
[Nexus 4 Original Android Development] manueltts:
UKM is needed for Synapse. You can find it in the synapase+UKM thread on xda (Google would find it easily).

The red light could be deactivated on "misc" section, inside Synapse.
[Nexus 4 Original Android Development] CamoGeko:
Thank you mate, I'm just about to flash the latest version of Android L so that should take care of the cleaning job. Then I'll flash the latest r5 afterwards.

Looking forward to running it.

Sent using Android L
[Nexus 4 Original Android Development] defconoi:
The red led is a feature, it let's you know when the phone is about to get throttled due to heat, you can disable it in synapse led options. Download UKM 3.4.3 link in op
[Nexus 4 Original Android Development] CamoGeko:
Flashed r5 zip but it still says r4.

Sent using Android L
[Nexus 4 Original Android Development] defconoi:
i forgot to change the version string in the AOSP one ;) lol good catch though, the CM11 one is changed
[Nexus 4 Original Android Development] cfrank38:
Its now very cold like a freezer the phone .... Very gooooood many thanks

Will it be much work when Android l is officialy released yo get it working with your kernel ?
[Nexus 4 Original Android Development] CamoGeko:
Ah cool, I thought I made the mistake by flashing the r4 zip but then I double checked and it was the r5 one lol

It's already working with Android L lol
[Nexus 4 Original Android Development] cfrank38:
I know, im using L, but what i was thinking that L will come with a new kernel...... or not ?
[Nexus 4 Original Android Development] CamoGeko:
Most likely, but then the source will be released anyways so what does it matter. ;)
[Nexus 4 Original Android Development] defconoi:
Kernel Update 88u

88u: Unleashed

hellsgod - readahead: Fix an error (thx ramgear)
hellsgod - Readahead: Optimize divide/multiply by power of 2 using L/R shift (thx ramgear)
hellsgod - Increase max readahead value
Lee Susman - mm: change initial readahead window size calculation
Tejun Heo - scatterlist: atomic sg_mapping_iter() no longer needs disabled IRQs
Tomasz Stanislawski - scatterlist: add sg_alloc_table_from_pages function
Jan Beulich - lib/vsprintf.c: improve standard conformance of sscanf()
Andy Shevchenko - lib/vsprintf: update documentation to cover all of %p[Mm][FR]
George Spelvin - lib: vsprintf: fix broken comments
George Spelvin - lib: vsprintf: optimize put_dec_trunc8()
George Spelvin - lib: vsprintf: optimize division by 10000
George Spelvin - lib: vsprintf: optimize division by 10 for small integers
Andy Shevchenko - vsprintf: add support of '%*ph[CDN]'
Andrew Morton - lib/vsprintf.c: remind people to update Documentation/printk-formats.txt when adding printk formats
Andrei Emeltchenko - vsprintf: add %pMR for Bluetooth MAC address
Denys Vlasenko - vsprintf: further optimize decimal conversion
Grant Likely - vsprintf: correctly handle width when '#' flag used in %#p format
Pierre Carrier - lib/vsprintf.c: "%#o",0 becomes '0' instead of '00'
Al Viro - switch the protection of percpu_counter list to spinlock
Mandeep Singh Baines - lib/scatterlist: do not re-write gfp_flags in __sg_alloc_table()
faux123 - ARM: 7593/1: nommu: do not enable DCACHE_WORD_ACCESS when !CONFIG_MMU
Will Deacon - ARM: 7592/1: nommu: prevent generation of kernel unaligned memory accesses
Rob Herring - ARM: 7492/1: add strstr declaration for decompressors
faux123 - arch/arm/Kconfig: enable unaligned capability for ARM
Linus Torvalds - word-at-a-time: make the interfaces truly generic
ion-storm - kernel: Move REPEAT_BYTE definition into linux/kernel.h
faux123 - ARM: 7493/1: use generic unaligned.h
Raymond Golo (intersectRaven) - Use pgprot_writecombine in ion_system_heap_map_kernel for optimization.
MyungJoo Ham - PM / QoS: Introduce new classes: DMA-Throughput and DVFS-Latency
faux123 - tmpfs: fix mempolicy object leaks
Subhash Jadavani - mmc: msm_sdcc: check for pending_resume in SDCC system suspend
FlyFrog - int_sqrt: Improve 3x faster integer sqrt.
ramgear - int_sqrt.c: Correction square root algo with naming
Sujit Reddy Thumma - PM / QoS: Fix deadlock during PM QoS vote to default value
Syed Rameez Mustafa - lib: spinlock_debug: increase spin dump timeout
Vikram Mulukutla - lib: spinlock_debug: Avoid livelock in do_raw_spin_lock
Jan Beulich - lib/decompress_unlz4.c: always set an error return code on failures
Pranav Vashi - staging: binder: Do not debug failed transactions
Karthik Nayak - Staging: Android: removed an unnecessary else statement
Lucas Tanure - staging: android: Clean up else statement from binder_send_failed_reply
ion-storm - defonfig: Enable HIDRAW for wiimote pairing support

AOSP/L

CM11
[Nexus 4 Original Android Development] sykopompos:
The general idea is that L will come with a lot newer kernel version and there will be tweaks to be done to make it work even with up to date kernels so most gen kernel will probably work but won't be the most efficient optimized ones until they are patched with the new official L version
[Nexus 4 Original Android Development] defconoi:
I can pretty much guarantee L will stick with android 3.4 and not much changes unless they have incentive for doing so, highly doubt it.
[Nexus 4 Original Android Development] CamoGeko:
Cheers for the clarification mate, you got your fame already though.

I'm loving L, and I feel that its all because you put the time and effort to bring it to us in its current form! :good:
[Nexus 4 Original Android Development] sykopompos:
You really think so? With all the new APIs and everything else, there would be enough reason to upgrade. I think android wear is even using 3.10
[Nexus 4 Original Android Development] manueltts:
Maybe project volta could be an incentive to upgrade.
[Nexus 4 Original Android Development] defconoi:
I really dont see any upstream development being done for mako, it reached end of life, as in incentive I meant money. I believe L could be the end for the nexus 4. I may be wrong, I'd love for them to update the nexus 4 to android 3.10, its certainly possible, just not that confident that they will do so. There is a better chance that us devs here can port mako to android 3.10.
[Nexus 4 Original Android Development] sykopompos:
Oh, I don't really think they will update mako but I meant in general they will update the kernel for L
[Nexus 4 Original Android Development] defconoi:
oh, yea most definitely other devices will, us devs are pushing android forward though with our upstream linux patches, honestly I think the more people that backport and update the kernels the better, it will keep google devson their toes and help them out a bit as well. Their is a TON of arm/msm patches hitting LKML(linux mailing list) and allot of new stuff for 64bit arm. The future looks great for linux/android mobile.
[Nexus 4 Original Android Development] sykopompos:
Keep doing what you are doing bud, I'll keep at it as much as possible
[Nexus 4 Original Android Development] defconoi:
hey [MENTION=1050103]sykopompos[/MENTION], have you noticed that there is a 3x speed increase in write/read speed in android L? Test with androbench, any idea why such an increase in speed for L compared to kitkat? My last kernel 88u got a 30mb read speed slow down from hellsgod's readahead patches fyi, i reverted them and now its faster. I benchmark between releases lol
[Nexus 4 Original Android Development] defconoi:
Here is 88u-r1, only change is 4 reverted readahead speed tweaks that are readahead speed killers

AOSP/L

CM11
[Nexus 4 Original Android Development] sykopompos:
That's because android L is awesome and the work on it is pure awesomeness :p
[Nexus 4 Original Android Development] defconoi:
I dont think this is the work of L google, I think its the work of L [MENTION=1050103]sykopompos[/MENTION]
[Nexus 4 Original Android Development] sykopompos:
I might have done something, idk. The phrase ignorance is bliss fits the bill when I was just out to fix issues as I saw them :p
[Nexus 4 Original Android Development] shadeMe:
:laugh:[MENTION=1316336]defconoi[/MENTION], an update on my situation - I've had the kernel crash on me once more. However I've been getting a lot of app crashes where the error occurred in native code. I'll try out the latest build.

Edit: Had a watchdog reboot just now, attached log. By the way, I've got a feature request - would it be possible to implement the following? Repeatedly tapping the screen during the Google log to enter recovery. Some kernels from the FreeXperia project have this feature.
[Nexus 4 Original Android Development] Almayce:
They have it because it's pain to get there in the first place. At least that's what I found out on xperia M. The timing had to be precise and it took me a while to get it right :D in our nexuses it's really easy, I think it would be unnecessary.
[Nexus 4 Original Android Development] shadeMe:
Well, as someone whose phone has barely functional hardware/volume keys, I beg to differ.
[Nexus 4 Original Android Development] CamoGeko:
To be honest, I think even google would be impressed with the work you've done on Android L so far!

Btw this kernel sleeps like a baby. Very nice!

Sent using Android L
[Nexus 4 Original Android Development] christiano88:
Felt like sharing my setup with which I get much better battery life, especially during standby:

CPU Min Freq: 81mhz

CPU Max Freq: 1728mhz (can be 1512, if OC is not wanted)

CPU Max Screen Off Freq: 594mhz

CPU Governor: pegasusq (no further tuning made)

Intelliplug 5.0 enabled with the following settings:

Profile: Balanced (4)

CPUs boosted: 2

Min CPUs Online: 2

Max CPUs Online: 4

Max CPUs Screen Off: 2

CPU Global Voltage: -125mv (extra -25mv on 1728mhz, if you plan to OC)

I/O Scheduler: fiops

GPU Min Freq: 128mhz

GPU Max Freq: 325mhz

GPU Governor: interactive

UKSM enabled

Hit thanks if it helps you.
[Nexus 4 Original Android Development] Almayce:
Well the way I do it I invoke power menu and choose recovery, that is if your room supports advanced reboot. I think most roms do except stock. So I actually used the volume down and power button like 20 times in a year or so I own the device
[Nexus 4 Original Android Development] Defferex:
CPUs boosted: 2

Min CPUs Online: 2

Are you sure? Wouldn't it drain more battery during usage?

---------- Post added at 02:50 PM ---------- Previous post was at 02:43 PM ----------

And what should I do to uninstall this kernel? I want to flash stock for a while.
[Nexus 4 Original Android Development] christiano88:
As I tested, it's better to have 2 active cores working at lower freq than 1 core at higher freq. So if you use only 1 for Min CPU Online, there will be one core that will struggle at higher speeds while keeping the others offline on low resource-consuming tasks. If you force 2 cores to be active, they will split the load. I also analyzed the possibility of having all 4 cores active at all time when screen is on, but that actually hurts the battery because even though they are all active, only 2 will be used properly most of the time (90% of the apps are dual-core optimized, while only 10-15% are quad-core optimized), so it's a waste of battery power to keep them all active.

Another advantage is that the device is snappier because it always has 2 active cores, so from 0 to 100% load it will go a lot smoother (it's a paradox that the device can save battery and be faster with the same tweak, but it's real).

CPU boost I think it was 3 by default, so having 2 instead according to the above theory is better. This might decrease smoothness on paper but I haven't noticed a real difference.
[Nexus 4 Original Android Development] CamoGeko:
Just dirty flash your ROM.
[Nexus 4 Original Android Development] Defferex:
Understood, thanks for explanation.

Will try your profile.
[Nexus 4 Original Android Development] christiano88:
If someone is curious about the idea of 1 core vs. 2 cores active, do this:

1. Install a stability test app from the playstore, e.g. https://play.google.com/store/apps/details?id=com.into.stability&hl=en

2. Lock the device at 2 cores max active at ~702mhz max frequency, set governor to performance (to always have max freq) and run the above app, while checking max CPU temp with this app: https://play.google.com/store/apps/details?id=org.alldroid.apps.tempmonitor&hl=en

3. Now lock the device at 1 core max active at 1.45ghz (to match the same performance, 2x702mhz from above), and rerun the above test while checking the temperature. Don't forget to leave the governor on performance.

4. See which temp is higher, temperature is directly proportional to the power consumption.

This can actually be tested even without using a stress test app, just by doing the above settings and watching the cpu temp in idle (even though it's not very accurate because some installed apps might spike in the background in the first test, and stay calm in the 2nd, or the other way around).
[Nexus 4 Original Android Development] defconoi:
In my small test, it seems this is correct, this is very informative, thank you.
[Nexus 4 Original Android Development] Defferex:
Just saw that CPU frequency doesn't go down when charging.

It stucks on 1.4 GHz.

I am using profile by christiano88, is it normal?
[Nexus 4 Original Android Development] christiano88:
Did you perform the above experiment and set the governor to performance? Make sure to change it back to your previous one, or pegasusq (what I use).
[Nexus 4 Original Android Development] CamoGeko:
I like the default Governor - HYPER. :good:
[Nexus 4 Original Android Development] christiano88:
Well, I'm not sure how my settings work with other governors, since I use pegasusq (which I stated in the post containing my settings).
[Nexus 4 Original Android Development] CamoGeko:
True, you could always give it a try since you stated that you do use the Governor unmodified.
[Nexus 4 Original Android Development] Defferex:
No I didn't perform any governor changes.

It's not your profile related problem.
[Nexus 4 Original Android Development] montbazon:
Hi, defconoi. Could you make the synapse settings keep on after every new kernel flashing? I'm exhausted...
[Nexus 4 Original Android Development] The Tox:
Use backup/restore option on synapse

Envoyé de mon Nexus 4
[Nexus 4 Original Android Development] ivanich:
Yeah, this is realy annoying, after each rom/kernel reflash it's need to restore settings then restart synapse and press cancel button to apply settings. It would be nice to have an option in synapse for "flashogolics" to automatic settings restore even if rom or kernel was changed.
[Nexus 4 Original Android Development] defconoi:
Synapse goes bonkers if u change one feature and settings aren't cleared, one new setting will make everything messed up, I got tired of answering why is this setting red and now have my cleaning script clear synapse. Even if u use the backup/restore feature in synapse after a new thing is added synapse is wack.
[Nexus 4 Original Android Development] sykopompos:
That's the way to do it, starting with L b7 (the pre-test) I added in that it wipes the dalvik-cache and cache in the updater-script because of people who don't and then complain about issues so that is just one less thing to hear about