yashsingh1/xdaforums huggingface dataset:
[Moto G Android Development] jonas210678:
Want to use this version, but when i flash this Version. In settings is stated that the kernel is from 21.04. So i think the kernel dont flash, only the normal v11
[Moto G Android Development] hurtsky:
place the kernel.zip in /mnt/sdcard.. and try reflash..
[Moto G Android Development] Dr. Brawler:
Latest "experimental" build is running great on mokee 5.1.1
[Moto G Android Development] antarix:
Working great with me on bliss pop too.

Does mokee has rro layers or themes?
[Moto G Android Development] Dr. Brawler:
It has themes =(

I'm just playing with roms while I wait for brokenOS 5.1.1 tbh. They use layers
[Moto G Android Development] antarix:
Ohhh :( I'm waiting for it too.

I thought mokee might have layers as you use only layers rom.
[Moto G Android Development] Dr. Brawler:
I'll use any rom that's aosp. I just prefer layers. I never use themes on cm theme engine. Since kitkat days I always see users complain of bugs when they apply themes. I don't like bugs lol
[Moto G Android Development] hurtsky:
wow you guys change alot of ROMs, i just stick to CM12.1 nightlies only.. btw if the experimental version got some problem.. let me know ya :D and as always, drop me a log if that happen, thank you for test it :fingers-crossed:
[Moto G Android Development] mangesh511:
v11 giving fc on new blisspop v3.2 (5.1.1)
[Moto G Android Development] Dr. Brawler:
At least I'm not changing kernel lol. I always drop a log if I have a problem. Logs or it didn't happen. Ryte? xD
[Moto G Android Development] SirTobsen:
Anybody also facing this error or is this normal?

once proximity sensor is covered dt2w isn`t working (as intended), but no matter weather I uncover the sensor or not it`s never working again until I wake the phone with hardware power button.

Maybe this is intended too, but I think normally dt2w shouldn`t work with covered sensor and should work again as soon sensor is uncovered...

thanks in advance :angel:

Rom: Ressurection v5.4.2

Kernel: Hurtsky dt2w v11

Model: XT1032
[Moto G Android Development] Silver Droid:
Yea it's an issue everybody is facing I think so including me

....thesilverdroid....
[Moto G Android Development] antarix:
My basic concern in past was customization but when I came across layers my demands changed.

Now I feel like finding a rom with layers support. BTW your kernel is rock solid.

At least I don't see my phone in panic mode. Dr. Brawler recommended a good flavor.
[Moto G Android Development] hurtsky:
do clear cache and dalvik cache

yeah, youre right :D

it is normal, and it is always will be like that because i had not enough knowledge to repair that. :rolleyes:

btw if got any changes or repair for it, it will be notify in future changelogs :fingers-crossed:

i see, i think i also need to feel those layers feel.. maybe it will change my mind ;)

yea, still no warning in log for now, next experimental version will be upload in 4 hour :fingers-crossed:
[Moto G Android Development] antarix:
Yes, you need it. Even I'm waiting for it.

Using exp3 version and got no problems yet but https://docs.google.com/file/d/0B-HfcNHadXOgSkdHYTJqNGxvM00/edit?usp=docslist_api is the log.

Edit: waiting for 4 hours to flash latest [emoji6]

---------- Post added at 06:42 PM ---------- Previous post was at 06:28 PM ----------

Bro if you getting system ui fc and com.android....phone fc than it is bliss pop bug. If it's something else than I'm sorry to interrupt.
[Moto G Android Development] hurtsky:
logs looks good.. thanks for that :)
[Moto G Android Development] antarix:
You insisted for logs while showing curiosity towards layers [emoji12] the reason behind clean log, else I wouldn't post [emoji23]
[Moto G Android Development] SirTobsen:
Want to point to this app http://xdaforums.com/google-nexus-5/themes-apps/tips-dt2w-proximity-sensor-t2787024/page4. It seems to work like a charm regarding dt2w + proximity sensor (DraguSystem.2.93alpha.apk, activate dt2w profile in app).

Maybe we get some more reports on that, but after my tests dt2w is working as long as sensor is uncovered and stopping while being covered. So as wanted!
[Moto G Android Development] hurtsky:
after uncovered back the dt2w will working back? if it working back, than this maybe can done as a workaround for dt2w problem.

:D it is okay.. thanks for that
[Moto G Android Development] hurtsky:
update experimental build V11 exp4

changelogs:-

- configs: update to V11 exp4 (credits to hurtsky)
- msm: limiter: The necessary evil (credits to Pranav Vashi)
- PM / sleep: unregister wakeup source when disabling device wakeup (credits to Zhang Rui)
- cpufreq: limiter: update driver to v3.6 (credits to hurtsky)
- SELinux: Reduce overhead of mls_level_isvalid() function call (credits to Waiman Long)
- selinux: conditionally reschedule in hashtab_insert while loading selinux policy (credits to Dave Jones)
- selinux: conditionally reschedule in mls_convert_context while loading selinux policy (credits to Dave Jones)
- selinux: no recursive read_lock of policy_rwlock in security_genfs_sid() (credits to Waiman Long)
- selinux: fix a possible memory leak in cond_read_node() (credits to Namhyung Kim)
- selinux: simple cleanup for cond_read_node() (credits to Namhyung Kim)
- SELinux: possible NULL deref in context_struct_to_string (credits to Eric Paris)
- SELinux: use ARRAY_SIZE (credits to Himangi Saraogi)
- selinux: call WARN_ONCE() instead of calling audit_log_start() (credits to Richard Guy Briggs)
- PM / cpuidle: System resume hang fix with cpuidle (credits to Preeti U Murthy)
- sched: Improve scalability via 'CPU buddies', which withstand random perturbations (credits to Mike Galbraith)
- sched: Fix select_idle_sibling() bouncing cow syndrome (credits to hurtsky)
- sched: Remove stale power aware scheduling remnants and dysfunctional knobs (credits to Peter Zijlstra)
- sched/fair: Improve the ->group_imb logic (credits to Peter Zijlstra)
- sched/fair: Revert sched-domain iteration breakage (credits to Peter Zijlstra)
- sched/fair: Propagate 'struct lb_env' usage into find_busiest_group (credits to hurtsky)
- sched/fair: Add some serialization to the sched_domain load-balance walk (credits to Peter Zijlstra)
- sched/fair: Let minimally loaded cpu balance the group (credits to Peter Zijlstra)
- sched: Change rq->nr_running to unsigned int (credits to Peter Zijlstra)
- sched/fair: Implement fast idling of CPUs when the system is partially loaded (credits to hurtsky)
- SELinux: use deletion-safe iterator to free list (credits to Jeff Vander Stoep)
- msm_limiter: tune value for falcon (credits to hurtsky)
- cpufreq: Add Frequency limiter driver (credits to hurtsky)
- drivers: Add state notifier driver (credits to hurtsky)
- msm: mdss: Adding lcd notifier (credits to Se Hun Kim)
[Moto G Android Development] methuselah:
Well I think it's good dev is helping people here with the themes stuff. But I don't think people should bother him about these themes . I mean why should he give a dam about themes. Most of the kernels are always supported when you keep them with recommend settings but you can tweak for sure. But themes stuff is 3rd party related so i don't think we should ask him this theme don't work Can u look at log !!! But being human he definitely going to get sick. Fermasia left coz of this. So please beware.. Happy flashing
[Moto G Android Development] jonas210678:
This experimental build is working really good, no issues so far. It seems that accu performance is better in the experimental builds. I love your kernel, keep up the good work :good: :highfive:
[Moto G Android Development] SirTobsen:
Yes! tested now for some hours. with earlier recommended app dt2w is working like intended --> sensor covered = not working; sensor uncovered after that = working again
[Moto G Android Development] Pinktank:
Hey hurtsky, any chance of throwing westwood tcp, it works better for those of us with imperfect signals :)
[Moto G Android Development] Silver Droid:
Yeah I'm also deliberately looking for a ROM with layers commits pls do PM me if in case you find

....thesilverdroid....
[Moto G Android Development] drsiddique5700:
soon we will get broken os up to date with 5.1.1
[Moto G Android Development] Pinktank:
XDA sure is the home of thread crappers, go the Glade Rom thread and talk it out there peeps, it has rro
[Moto G Android Development] Dr. Brawler:
[MENTION=4723408]hurtsky[/MENTION]

I had a boo boo in exp3

https://docs.google.com/file/d/0B9J9UwU3X2oQQ3JxWUpVMUNVbTg/edit?usp=docslist_api

I'm confused. I had 17hrs up time no problems. I also tried to reproduce bug and failed. Not sure if that's good or bad lol. This may be silly question but do min free values or launcher effect stability?

Edit: I'm about to flash exp4. I'll let you know if any problems
[Moto G Android Development] lmulli:
Glade rom has RRO layer support but is currently only version 5.1.0, hence why I stopped using it and switched to Alberto's 5.1.1 build (I don't use layers). Nice rom though - http://xdaforums.com/moto-g/development/rom-glade-rom-t3084767
[Moto G Android Development] miguelAr52:
about battery: i have not measured it, but it seems battery is lasting a lot (i'm on v11 release over blisspop 3.2, not exp versions)
[Moto G Android Development] Pinktank:
seriously people, this is a kernel thread, has nothing to do with themes or roms, why don't we let people report kernel related things properly and let the developer have some sanity? 5.1.1 just came out a day ago, glade will have it in their next weekly, take a breath, your phone will not die.
[Moto G Android Development] lmulli:
It's already dead Barry but thanks for your input.
[Moto G Android Development] Pinktank:
My condolences.

[MENTION=4723408]hurtsky[/MENTION] v4 with zzmoove default is the fastest yet, haven't tested battery much
[Moto G Android Development] hurtsky:
it should, optimize many thing and disable some config that reduce the latency of the kernel

thanks ! i will add it in the OP

yeah, next stable version :D

weird, seem no errors/bug/warn in the log... hmm.. i don see why launcher will effect the kernel, because the kernel did not panic.. min free values, means youre adjusting it by software?

try exp4 version, you will surprise with deep sleep on night :o
[Moto G Android Development] Dr. Brawler:
I can adjust minfree values via synapse
[Moto G Android Development] mato_d007:
Does it work on aosp 5.1.1?
[Moto G Android Development] Aguys:
Use this kernel with Blisspop 3.2(5.1.1), very good performance...:good:
[Moto G Android Development] antarix:
Yes it does.

You Defy-ed rugged circumstances in the past and now you are a G [emoji13]
[Moto G Android Development] hurtsky:
minfree no longer adjustable in my latest stable kernel it just intended to read-only file and not adjustable for user.. maybe you can remove it on boot, and give a restart.. i also read your log many audit complain.. not really know because of what, some of them is because of synapse..

[ 14.259818,0] type=1400 audit(1429748423.551:18): avc: denied { write } for uid=0 pid=519 comm="rm" name="busybox" dev="mmcblk0p34" ino=31352 scontext=u:r:init:s0 tcontext=u:object_r:system_file:s0 tclass=file permissive=1
[ 14.260126,0] type=1400 audit(1429748423.551:19): avc: denied { write } for uid=0 pid=519 comm="rm" name="xbin" dev="mmcblk0p34" ino=31349 scontext=u:r:init:s0 tcontext=u:object_r:system_file:s0 tclass=dir permissive=1
[ 14.260348,0] type=1400 audit(1429748423.551:20): avc: denied { remove_name } for uid=0 pid=519 comm="rm" name="[" dev="mmcblk0p34" ino=31420 scontext=u:r:init:s0 tcontext=u:object_r:system_file:s0 tclass=dir permissive=1
[ 14.260639,0] type=1400 audit(1429748423.551:21): avc: denied { unlink } for uid=0 pid=519 comm="rm" name="[" dev="mmcblk0p34" ino=31420 scontext=u:r:init:s0 tcontext=u:object_r:system_file:s0 tclass=lnk_file permissive=1
[ 22.039340,0] type=1400 audit(1429748431.331:22): avc: denied { unlink } for uid=0 pid=1704 comm="rm" name="busybox" dev="mmcblk0p34" ino=31352 scontext=u:r:init:s0 tcontext=u:object_r:system_file:s0 tclass=file permissive=1
[ 22.060859,0] type=1400 audit(1429748431.351:23): avc: denied { add_name } for uid=0 pid=1706 comm="cp" name="busybox" scontext=u:r:init:s0 tcontext=u:object_r:system_file:s0 tclass=dir permissive=1
[ 22.061117,0] type=1400 audit(1429748431.351:24): avc: denied { create } for uid=0 pid=1706 comm="cp" name="busybox" scontext=u:r:init:s0 tcontext=u:object_r:system_file:s0 tclass=file permissive=1
[ 22.105206,0] type=1400 audit(1429748431.401:25): avc: denied { setattr } for uid=0 pid=1707 comm="chown" name="busybox" dev="mmcblk0p34" ino=31241 scontext=u:r:init:s0 tcontext=u:object_r:system_file:s0 tclass=file permissive=1
[ 22.112213,0] type=1400 audit(1429748431.411:26): avc: denied { create } for uid=0 pid=1709 comm="busybox" name="[" scontext=u:r:init:s0 tcontext=u:object_r:system_file:s0 tclass=lnk_file permissive=1

are you using some other tweaks? i did not have this kind denial in my logs, my suggestion is to dirty flash your ROM and do wipe dalvik cache and reflash the kernel, try use kernel adiutor only as kernel control apps,

yup it work.
[Moto G Android Development] Dr. Brawler:
Other tweaks: Busybox on Rails for Synapse. SELinux mode changer for Viper4Android. I have Walkman flashed as well. I will try kernel audiutor instead but V4A and Walkman r a must lol
[Moto G Android Development] antarix:
Agree with the music choice you made there but I didn't find an option to selinux status in kernel adiutor for v11exp4.
[Moto G Android Development] animeshdinda:
http://xdaforums.com/showpost.php?p=60133165&postcount=182
[Moto G Android Development] hurtsky:
yeah, you could try that.. but dirty flash is necessary.. :D
[Moto G Android Development] Dr. Brawler:
Understood xD
[Moto G Android Development] Silver Droid:
For me V11 is best ever kernel I have seen I get nearly 6hrs of screen on time with at least 4hrs of WiFi... And about performance it really flies

....thesilverdroid....
[Moto G Android Development] jonas210678:
You dont need to change selinux state. It is permissive already! So v4a is working perfect without anything
[Moto G Android Development] hurtsky:
selinux actually is in enforcing, i did not change it to permissive because i like to see how it behave, because during this experimental version, many changes in selinux had been done.. And most of user now, know how to change the selinux, so no need for me to set default as permissive.. i'm right ? :D
[Moto G Android Development] Aguys:
Any recomended setting bro? For better multitasking...:)
[Moto G Android Development] hurtsky:
no recommendation setting for multitasking FOR NOW, i had plan changing the lowmemorykiller sources to make it less aggressive but it become soooo less aggressive thus make the system becomes lags so i need to test first how it will be.. since changing the minfree in lolipop not really give effective effect (i got read it somewhere forgot where the sources)
[Moto G Android Development] jonas210678:
For me it was enforcing since v4 vor v5 i didnt change anything. Normal flash this kernel and it is permissive :good: so nothing to change for you. You habe done a good work
[Moto G Android Development] hhp_211:
what kind of issues do you experience?

I would recommend this app:: Servicely 1.1.2 By Francisco Franco

grab it here::

http://www.apkmirror.com/apk/francisco-franco/servicely/servicely-1-1-2-android-apk-download/

or at play store ::

https://play.google.com/store/apps/details?id=com.franco.servicely
[Moto G Android Development] hurtsky:
Update to V12 stable version

Changelogs:-

- updated timers subsystems

- sync with google 3.4.x sources

- update msm_limiter to V3.6

- updated selinux

- mount tweaks

- add more oil to performance profile for zzmoove

- decrease the aggresiveness level of intellidemand

- others patches :- see at 2nd post in OP

thank you:-

Note: Dirty flash for ROMS is highly recommended for this version due to updated tweaking script :D
[Moto G Android Development] miguelAr52:
[MENTION=4723408]hurtsky[/MENTION] don't forget this, please
[Moto G Android Development] hurtsky:
aauwww, im forget to add this for V12. sorry, i will add this in next version.. :(
[Moto G Android Development] NeoPreacher:
coooool :D
[Moto G Android Development] Dr. Brawler:
What hotplugs kernel has now? I only see intelliplug in kernel adiutor. I miss bricked hotplug
[Moto G Android Development] Dr. Brawler:
Reboot on V11exp4. Not sure if this will help since 12 is out. I did dirty flash and use kernel adiutor like you suggest. I also ran ukm uninstall zip before dirty flash

https://docs.google.com/file/d/0B9J9UwU3X2oQLUdseEZHMnpRVXc/edit?usp=docslist_api

Will try v12 now
[Moto G Android Development] Pinktank:
[MENTION=4723408]hurtsky[/MENTION] touching the screen causes Qcom powerhal failed to acquire lock to fill the logcat with any of the governors/hotplug settings

(also, mpdecisions does not come on using synapse, the checkbox tick disappears when you hit apply)
[Moto G Android Development] sharath_babu:
[MENTION=4723408]hurtsky[/MENTION] .... screen flickers at low brightness , it exist since lollipop 5.0.2 stock!! , isn't there any solution for this?? is this bug because of kernel? ROM? bootloader??

ty
[Moto G Android Development] aouerfelli:
It's an Android bug. Turn off ambient display if you don't want it.
[Moto G Android Development] Dr. Brawler:
What bootloader u have? Also I don't think this is for stock if you're on stock rom. I have lollipop bootloader. I don't have this issue
[Moto G Android Development] hurtsky:
i remove all hotplug and left for only intelli plug as intelli plug had all profile, so user no need to confuse with settings

you had mount failure here, why.... i still try to figure it out why this happen..

could not find any commits that relate to this problems.. hmmm i will build one experimental for you later to test it out.. during what condition your phone rebooted?

anyone else got sudden reboot problem?

that normal, i removed completely mpdecision.. ROMs in default they depend on qcom powerhal, if we use others hotplugs than those errors will appers in system log.. it already been discussed long time ago.. and it is okay to let those log but it is annoying spam if we always look into it.. ;)
[Moto G Android Development] Dr. Brawler:
I hit home button from Lucid Browser. Opened Tinfoil for Facebook. Screen became unresponsive then it reboot. Do you think it has anything to do with busybox version I use? Busybox on Rails

code.google.com/p/busyboxonrails/source/checkout
[Moto G Android Development] hurtsky:
can you do me a favor, can you dirty flash back your rom, and reflash back kernel and do not install any tweak for 2 days...i means.. let your ROMs+normal gapps and this kernel only for 1 or 2 days... normal apps should be okay, just try not to install your selinux mode changer, busybox on rail and your fav Viper sound for 24 hours or 48 hours..
[Moto G Android Development] sharath_babu:
I'm on lollipop bootloader 41.18 , blisspop 3.2 n hurtsky v12.... flickers when cell is in low brightness (note- make sure ur surrounding is bit dim too as this won't appear in bright surrounding)
[Moto G Android Development] Dr. Brawler:
Install same version or version 12 which I am on now?
[Moto G Android Development] hurtsky:
i had no kind of problem with CM12.1, i believe this is ROM behavior.

yes my friend.. thank you so much
[Moto G Android Development] Dr. Brawler:
Do u have ambient display turned on? Other user suggest that is a bug. I use my phone in the dark all the time when I'm in bed lol

---------- Post added at 03:30 AM ---------- Previous post was at 03:29 AM ----------

Yes same version or yes V12? Lol
[Moto G Android Development] hurtsky:
yes, with V12 stable.
[Moto G Android Development] Dr. Brawler:
Okay. I got u
[Moto G Android Development] miguelAr52:
hi. i'm back on v11 from v12, i like it more.

i don't use ambient display.

i have never seen flickering in mid to low brightness in the last 15/20 or more days.

checked it: right now with current (blisspop) rom.

roms i test: blisspop, euphoria, flexos, sokp, xperience. neither one have had this screen flickering.

perhaps ambient display has trouble..

---------- Post added at 01:50 AM ---------- Previous post was at 01:44 AM ----------

my bootloader: 41.18

when i changed bootloader to this current one the screen flickering ended
[Moto G Android Development] hurtsky:
when i re-read back your reply and from what that i can conclude with your statement, it seems system problem (guessing) because kernel did not panic in log, it just stated phone going to reboot*

[29545.801686,0] Restarting system with command ''.
[29545.801945,0] Current task:init(1) Parent task:swapper/0(0)
[29545.802913,0] Going down for restart now
[Moto G Android Development] antarix:
[MENTION=4723408]hurtsky[/MENTION] v12 working pretty fine.

Have no bug with dt2w as well
[Moto G Android Development] hurtsky:
nice ! good to hear that :o
[Moto G Android Development] miguelAr52:
my lack of problems has these features too:

i don't know what Lucid Browser is (mine es UC, secondary Dolphin), and overall: i don't use the Facebook app nor nothing related with it.

as for busybox, i use the free stericson from a long time ago because that was recommended in these forums by one of our heroes, don't remember whom

---------- Post added at 02:34 AM ---------- Previous post was at 02:27 AM ----------

i agree with v12 working fine.

i got back to v11 only because personal feeling, i think it is faster but i have no measure of that

---------- Post added at 02:36 AM ---------- Previous post was at 02:34 AM ----------

about dt2w: i can't say, i don't use it
[Moto G Android Development] Dr. Brawler:
I think that busy box caused the problem. However I did clean install rom and flashed v12 without any tweaks. I will run like this for a couple days and let you kno how things go
[Moto G Android Development] Pinktank:
You can rename power hal so it doesn't spam logcat apparently [MENTION=5438598]RenderBroken[/MENTION] knows the fix I believe
[Moto G Android Development] hurtsky:
Did you already try rename it?
[Moto G Android Development] hurtsky:
thank you for that experiment.. i will glad to hear you after 24 hours how it will go ;)
[Moto G Android Development] Pinktank:
no I didnt know which file
[Moto G Android Development] hurtsky:
i see, i will try do something about it ;)
[Moto G Android Development] hurtsky:
i tried remove power.default.so, seem nothing done.. the log still producing same error.. if you can find me the exact file, i can do next implement about this qcom powerhal.
[Moto G Android Development] Flashhhh:
You need to remove touch boost from powerhal file to remove log spams.

For example

https://bitbucket.org/yank555-lu/sl...mits/23173f8ec2a351909e1108ff182cc93370654f3e
[Moto G Android Development] Pinktank:
/system/bin is supposed to have a mpdecision binary that you can delete is what I was told but flashhhh probably know better as above
[Moto G Android Development] hurtsky:
thanks :) but i already know about this way. But this way but you need to cook it during ROM compilation not from kernel compilation because it is hard coded or did you already success removing this qcom powerhal failed to acquire lock in log? can let me the proper way? thank you :D

yup, that mpdecision binary, since this kernel script already disable it and that make systems barking "qcom powerhal failed to acquire lock", it happen because qcome powerHal try to boost freq during touch event (depend on mpdecision) but the mpdecision is disabled.
[Moto G Android Development] Pinktank:
Yeah, I know, just a dev told me to delete the binary after disabling, but you know better, I am not a dev :)

"If i rename /usr/bin/mpdecision to /usr/bin/mpdecision.bak so it doesn't get autostarted "
[Moto G Android Development] hurtsky:
not really know :( still lack of knowledge thou.. btw thanks for the information, my friend :o
[Moto G Android Development] mangesh511:
hey [MENTION=4723408]hurtsky[/MENTION]

can i use u r kernel with SONIC OPEN KANG rom or mokee rom ?

is there any tweaks added for sound in your kernel ?

currently i am using your v12 with default setting currently with blisspop.

thanks.