yashsingh1/xdaforums huggingface dataset:
[X 2014 Original Android Development] adm1jtg:


I know Cm recently resolved an issue with some kind of astronomy sensor. Can you try an updated version of your rom. Or try the latest Cm nightly with stock Cm kernel to help further diagnose the issue?
[X 2014 Original Android Development] Tinchoska:
With stock cm stuff there's no problem, only happens when i flash the kernel

Enviado desde mi SM-T700 mediante Tapatalk
[X 2014 Original Android Development] joaste:
Which version of the kernel are you flashing? If V4, then try V5.2. You can find the link a few posts back.
[X 2014 Original Android Development] adm1jtg:
cm only fixed sensor issue in like the last week or so. Might have to wait till OP merges changes again.
[X 2014 Original Android Development] RenderBroken:
I should have time to merge and release tonight! Boom. . . .mic drop. . .
[X 2014 Original Android Development] adm1jtg:
Did u ever find any reason for the increased battery drain on standby? Can I provide you any more info that would help?
[X 2014 Original Android Development] RenderBroken:
Not really. Unfortunately its just tough to dig through without the phone. The logs were great though. I still have more to go through with them. I will tinker with a few things that I think it could be. Thanks.
[X 2014 Original Android Development] RenderBroken:
I think it has to deal with the new State Notifier I have implemented. What it does is turn off hotplugging and other functions while screen is off. You are having more drainage during sleep right? I think I left it disabled on accident so nothing is ever turned off like it should and certain functions will not work. To enable:

echo "Y" > /sys/module/state_notifier/parameters/use_fb_notifier

Report back any issue please good sir!
[X 2014 Original Android Development] adm1jtg:
Issued from adb shell anyway to confirm its working?
[X 2014 Original Android Development] RenderBroken:
Naw, just run that in a terminal emulator or use ES File Explorer to navigate to that file > Open it > and change the "N" to a "Y"
[X 2014 Original Android Development] adm1jtg:
Ok done I assume this will NOT survive a reboot
[X 2014 Original Android Development] RenderBroken:
You would be correct. Any change made to ramdisk (SYSFS Included) will not survive.
[X 2014 Original Android Development] adm1jtg:
Ok will do the same overnight test tonight i did previous and post a bbs log tomorrow

Logs from last night:

http://bit.ly/1JSnbPZ

Looks like the drain is back to "normal" maybe even a little improved now. GREAT WORK!
[X 2014 Original Android Development] RenderBroken:
ok that sounds like an easy fix :D

I will make sure its enabled by default in the next build. Thanks for your testing!
[X 2014 Original Android Development] blinkin:
Will test it as well, thx
[X 2014 Original Android Development] Tinchoska:
Guys synaose is the only option of tunning?

Enviado desde mi SM-T700 mediante Tapatalk
[X 2014 Original Android Development] joaste:
I think most people are using Kernel Adiutor.
[X 2014 Original Android Development] Tinchoska:
Guys, can you set any different freq (max freq) than stock?

Enviado desde mi XT1095 mediante Tapatalk

---------- Post added at 09:53 AM ---------- Previous post was at 09:52 AM ----------

Because I am trying g to set 1.9 and on every reboot it goes back to default freq.....

Enviado desde mi XT1095 mediante Tapatalk
[X 2014 Original Android Development] Aroch925:
I'm having the same issue
[X 2014 Original Android Development] bira792:
I am also having the same proplema time set any different freq .not look forward to a final correction, this kernel is highly anticipated prociga with his beautiful work.
[X 2014 Original Android Development] dictionary:
Seriously, you're in like every thread saying the same thing. Just chill out
[X 2014 Original Android Development] juangcardoso:
What is the last version avaible?

I'm on CM12 based ROM, and if you need help with tests, you can talk with me :)

Sorry for my bad english! :)
[X 2014 Original Android Development] Max94h:
Go back to page 46 there's the latest test build
[X 2014 Original Android Development] adm1jtg:
[MENTION=5438598]RenderBroken[/MENTION]

There have been quite a few kernel changes in cm since your last test build. Would it be possible for you to make a quick update that simply merges in all the latest cm changes. There are even 2 changes from today that will be in tomorrows build.

I also am getting lots of powerhal errors in the logcat on you latest test build and i believe cm made a powerhal change.

Would be more then willing to test if you can run a build.

Thanks for all the great work
[X 2014 Original Android Development] RenderBroken:
Sure , when I get some time today I will try to run one off.
[X 2014 Original Android Development] adm1jtg:
Were there issues? Or just time issues :)
[X 2014 Original Android Development] RenderBroken:
Its ALWAYS time lol.
[X 2014 Original Android Development] adm1jtg:
Ok will stop bugging you lol just was like if there was an issue other then time I would offer my help but I dont see how I can make more time :D
[X 2014 Original Android Development] RenderBroken:
lol, dont sweat it. You dont bug me. I think I have some time now.
[X 2014 Original Android Development] juangcardoso:
Downloading to test! Thanks for tour work :D
[X 2014 Original Android Development] iron maiden:
Very thanks

Rehards
[X 2014 Original Android Development] adm1jtg:
Still getting powerhal errors and a few others i dont see with cm kernel. Hope this helps:

http://bit.ly/1MTTN2m

Edit: Just checked and setting the max freq to 1958 reverts back to 2457 after a little while so still not sticking. Setting with kernel auditor and it sets properly but like before after sometime passes approx 10-15 min on my test it reverts back to 2457
[X 2014 Original Android Development] RenderBroken:
Powerhal is most likely due to not using mpdecision and its builtin touchboost. So those are annoying yes, but don't mean anything. The Max freq not sticking is most likely due to CPU Temperature Control. What happens is the CPU is being throttled and when the throttling is done it restores the max freq to the stock max freq and not policy max freq. Should be easy enough to fix.
[X 2014 Original Android Development] adm1jtg:
I hear what your saying but my max freq changed when phone was in deep sleep so I dont think its a throttling issue.
[X 2014 Original Android Development] juangcardoso:
No issues for now. The kernel is working fine! :)
[X 2014 Original Android Development] thisguy23:
First time trying this kernel out. Very nice! Haven't changed anything from stock yet, but love that I have a choice! Thank you!

Everything is running just fine. No issues to report.
[X 2014 Original Android Development] adm1jtg:
Can anyone else confirm or deny that changing frequencies doesn't stick after about 15 min or so?
[X 2014 Original Android Development] Max94h:
confirm the issue, frequency goes back to stock after a while
[X 2014 Original Android Development] bira792:
reamente after a while back to stock frequency 15 to 20 minutes as well.
[X 2014 Original Android Development] adm1jtg:
Sorry to report that on my first test with r5 idle battery drain is much higher then previous builds. Not sure why the wakelocks and such are normal bit the drain is now approx 1%/hour while on the old 54 build it was no higher then .3%/hour and many time I could get .1%/hour.

Let me know if they're is anything I can do to isolate the drain, logs or whatever.

Also can someone else confirm or deny my findings so we know this is not just some weird configuration issue on my part
[X 2014 Original Android Development] RenderBroken:
Thanks for the great info! Also there is not much that has changed from my last test build to the R4 release. So its really weird that you made these findings. Def let me know if there is any change. Thanks again!
[X 2014 Original Android Development] adm1jtg:
Just to be clear the previous version that had great idle drain was 54 which preceded your recent test builds. It was compiled by o.o and posted . I believe it was BEFORE you started playing with the hotplug stuff.

http://xdaforums.com/showpost.php?p=62528230&postcount=374
[X 2014 Original Android Development] RenderBroken:
I see. Thanks.
[X 2014 Original Android Development] adm1jtg:
Come on guys one report by me of battery drain is not nearly enough for OP to base changes on. While I dont feel it is a configuration issue or something specific to my setup who knows. We need others to report back their findings and see if they match my own.
[X 2014 Original Android Development] dogswind:
Is there any way to get double tap to wake working with this kernel? I know we have active display, but my sensors appear to be messed up. It'll wake up if I pick my phone up, but waving my hand over my phone does nothing for me anymore. Even on the stock ROM. :confused:
[X 2014 Original Android Development] nanca:
As you can see, I fully charged my phone at 03 am and now i have 78%. Calculating (now its 7 pm) it means battery drain is about 1.46%/h.

I did almost nothing to the phone and I'm using the last nightly with xposed and grenify, also stock kernel configuration. There's something else I could provide ?
[X 2014 Original Android Development] Tinchoska:
On snapshot i got awesome battery life..... maybe thedrzin came from nightlies

Enviado desde mi SM-T700 mediante Tapatalk
[X 2014 Original Android Development] adm1jtg:
What was your normal battery drain on previous versions of the kernel or with stock cm kernel?
[X 2014 Original Android Development] nanca:
This is all I have from previous build. With stock cm kernel and greenify.

So I cannot precisely tell you now, if it's better or not. It seems to be a little bit better (for me).

You take your own conclusions buddy.
[X 2014 Original Android Development] Max94h:
Battery seems fine.. These are some screenshots of what happened overnight

Inviato dal mio XT1092 utilizzando Tapatalk
[X 2014 Original Android Development] MiG123:
any plan to add fauxsound support?would help alot in solving my biggest gripe with this phone which is low, distorted audio out volume
[X 2014 Original Android Development] adm1jtg:
You could use v4a
[X 2014 Original Android Development] RenderBroken:
Yes, it is something I have been wanted to do for while now but haven't had the time to merge and test.
[X 2014 Original Android Development] igor_anta:
I have a feeling that since Fallout came out it pretty much stopped development for this phone on all fronts :D
[X 2014 Original Android Development] kraatus90:
made a build of version 5 and disabled msm_limiter on defconfig , now the clock bug is gone and clocks stick to whatever i set even after 20-21hrs , also if you have time please reply to my pm, [MENTION=5438598]RenderBroken[/MENTION] :)
[X 2014 Original Android Development] RenderBroken:
You would not be far from the truth lol

I will have to look into your source to better tell you but it does sound like you are missing commits. Also the Freq not sticking is an easy fix and will be in the next build. Can you link your source? Are you still wanting to pursue making your own kernel? I will gladly help whereever/whenever I can.
[X 2014 Original Android Development] kraatus90:
i haven't uploaded my sources yet, still figuring out git stuff. till now only things i have added are these commits for kcal

dad2af8 (HEAD, r3-t2, cm-12.1) mdss_mdp_kcal_ctrl.c: Fix missing function
7973e5c Defconfig: Enable Savoca's Special KCAL Control
9d5fd09 video: mdss: Report PCC values from pp registers
2e17759 msm: mdss: KCAL: Read values from MDP registers wherever possible
82f4a90 msm: mdss: KCAL: Apply default values on boot
e4d9959 msm: mdss: KCAL: Queue changes when panel is powered off
00b28b9 msm: mdss: KCAL: Remove MODULE_DESCRIPTION
6dbfbe2 msm: mdss: KCAL: Update Kconfig description
938887d msm: mdss: KCAL: Update according to linux guidelines and checkpatch.pl
f0ee398 msm: mdss: KCAL: Check panel power state before applying values
9db1951 msm: mdss: KCAL: Allow kcal_enable to control all post-processing features
fe7e1eb msm: mdss: Keep KCAL within its own source file
2d72aed msm: mdss: Remove deprecated __dev* markings
94c6683 msm: mdss: Add pa_v2 support to KCAL
f8c9585 msm: mdss: Replace PGC implementation with PCC for KCAL
8a795d8 msm: mdss: Add KCAL support for post processing control [v2]

and im doing this by using notepad++ , i just copy paste those changes.(all other is same as latest cm12.1) i don't know if it's right way to do this. but i have got it working . the problem is when try to add any hotplug , like this for ex -

e3c3de2 Defconfig: Enable Bricked_Hotplug
64fee33 msm: Add bricked hotplug
d7f482c Defconfig: Enable Intelliplug
1fec5e8 msm: Add Intelli Hotplug Driver

i get alot for werrors like some function is not defined or something like that. so i figured those are not the only required commits.

this is the file i used for reference http://renderserver.net/devs/RenderBroken/Moto X 2014/Changelog.txt

just so you know im totally noob at this , specially at using git. :p
[X 2014 Original Android Development] Mennpiko:
Kernel fantastic, good job, I love the color control, has designed a version for 13 cm?, Thank you very much for your work.
[X 2014 Original Android Development] LIOSam:
will this work on blisspop??
[X 2014 Original Android Development] xKroniK13x:
It should.
[X 2014 Original Android Development] AnimusVoxx:
not sure whats up but when i click the download link it just takes me to the render server, and im not sure where to go from there.
[X 2014 Original Android Development] kraatus90:
https://renderserver.net/browse?path=RenderBroken/Moto X 2014
[X 2014 Original Android Development] igor_anta:
[MENTION=5438598]RenderBroken[/MENTION] did you eventually get a Moto X 2014 unit? Still holding out hope for a stock kernel filled with delights :)

Oh, Merry Christmas and best wishes!
[X 2014 Original Android Development] RenderBroken:
Nope, never got one. I wish I did because it would make my life easier but I will continue supporting this phone blindly. Seeing how busy I have been, I will not make any promises but I would like to at least get a solid stock build out.
[X 2014 Original Android Development] igor_anta:
That's a bummer. I thought you were in line to get one soon. Still good to hear that you will continue to support the phone.
[X 2014 Original Android Development] skulldreamz:
I did mail [MENTION=5438598]RenderBroken[/MENTION] a new moto x 2014. At that point in time I had thought that the att model that i sent could be unlocked so it was a bummer for the both of us but at least his wife got a new phone out of it. Sorry guys, I tried...
[X 2014 Original Android Development] Tavisco:
Hey! Great Kernel! I liked it very much! It would be awesome if it had KEXEC Support for MultiRom, it is possible to implement it?

Thanks and happy 2016!
[X 2014 Original Android Development] igor_anta:
Nothing to be sorry about mate, you're probably the only one (someone correct me if I'm wrong please) that tried to help. Happy new year guys, cheers.
[X 2014 Original Android Development] ibphantom:
I know this kernel is for CM12, but I flashed it on CM12.1 Latest snapshot and it works great except for the ambient display going a little haywire.

I haven't figured out the cause yet, but randomly my phone(with the screen off) will flash the time/ambient display on, turn off, and then half a second later turn on again and won't stop until I reboot. So, its contstant on/off even with the phone face down on the table. Another problem is that the ambient display doesn't work at all and I have to force reboot because for some reason it reads the display as on, but its still black. Tapping the power/unlock button doesn't seem to kick it into gear.

If you need more details, let me know and I'll try to explain further. [MENTION=5438598]RenderBroken[/MENTION]
[X 2014 Original Android Development] riirezende:
Have plans to support CM13 based builds? [MENTION=5438598]RenderBroken[/MENTION]
[X 2014 Original Android Development] RenderBroken:
Hey! Thanks for the interest.

Honestly, I just don't know. I don't own the device and cannot really test. I have been trying to get a hold of one but unable to do so so far. But, I was thinking about doing some light builds. Ones where I don't rework everything but add in just the needed features. For me, I am already busy like crazy so its hard to find time and its even hard to be motivated to make time.
[X 2014 Original Android Development] BootloopedMillennials:
hope you do understand if you don't. We lack any CM13 kernels and barely any kernels total.
[X 2014 Original Android Development] RenderBroken:
oh, I understand. Nothing like having such a great device but no dev support for it. I believe this is in direct correlation with the locked bootloaders. They are major dev blocks.

For me, blind deving sux because when I test I am looking for certain things and need to make sure they pass my examination before release. I don't want to release a janky stuttering build and not even know it. Then if I need to revert a commit to fix the issue, I have to build/test many times to narrow down the offending commit. If I had to rely on testers, then the whole process is just unbearable. it would be slow, it would be unreliable because my idea of smooth may not be the same as the testers.

My thinking for future releases is to do watered down builds. Ones where I am fairly comfortable with changes I am making and feel that they are safe to make without causing unseen issues. But in these builds I will add all the major features. I will not give an ETA though it should not be long before I get started. Maybe about a week or so.

Kind Regards,

Zachariah
[X 2014 Original Android Development] Carlos_Bilibio:
Work fine in Tesla 5.1.1 high voltage.

Tanks man !!
[X 2014 Original Android Development] G4 Man2:
Are those "watered down" builds still on the table? or should I let sleeping dogs lie?
[X 2014 Original Android Development] RenderBroken:
It could be either or. All logs you can get using Syslog of this would help greatly.
[X 2014 Original Android Development] 0.0:
I think it's the ROM since I reflashed CM without your kernel and the same issue appeared
[X 2014 Original Android Development] Flamehell:
Tnx mate!!!!amazing!!and tnx for your great job [emoji4]
[X 2014 Original Android Development] Flamehell:
P.s:this monster give me a really good battery life!!!:)
[X 2014 Original Android Development] 0.0:
After a few days of testing, this kernel has been doing good with ambient display. Didn't experience any reboots yet. I'm on R2

sent from my Moto X Pure Edition
[X 2014 Original Android Development] ewalk4866:
So after a few days testing this kernel is awesome and I'm getting great battery life too. Thanks
[X 2014 Original Android Development] Flamehell:
[MENTION=5438598]RenderBroken[/MENTION] No reboots also with me.....amazing job bro :)
[X 2014 Original Android Development] bira792:
I wonder if I can use that kernel with another rom if Resurrection lollipop remix version 5.1.1 5.4.2 await response.
[X 2014 Original Android Development] skulldreamz:
We have a huge update coming out pretty soon ?
[X 2014 Original Android Development] RenderBroken:
Not sure I understood properly but yes, I believe RR uses CM as a base so you should be able to use my kernel.
[X 2014 Original Android Development] bira792:
thanks for the reply I tested it on my kernel with the resurrection remix with 5.1.1 to be working perfect you are a genius, its very good kernel thank you for making life easier people my appliance not heat up as much as before the battery lasts mais.obrigado
[X 2014 Original Android Development] ewalk4866:
[MENTION=5438598]RenderBroken[/MENTION] hey will this kernel work with CAF based roms?
[X 2014 Original Android Development] AnimusVoxx:
Whenever I tried to use a different gpu governor my phone crashes, anyone else have this issue?
[X 2014 Original Android Development] nerotix:
Not asking for an ETA, but did you check if it's even physically possible to get DoubleTap2Wake on this phone? I read somewhere some time ago that it isn't possible.
[X 2014 Original Android Development] AnimusVoxx:
Also what is the render ukm I tried to install the synapse app but it told me my device isn't supported

---------- Post added at 03:29 PM ---------- Previous post was at 03:28 PM ----------

Yes im using it on one right now. Haven't had issues.
[X 2014 Original Android Development] RenderBroken:
If you mean changing to Simple Ondemand, then that is just a bug in the stock kernel. I have a fix for it.

Well it looks completely possible to me
[X 2014 Original Android Development] RenderBroken:
So as it stands right now, things that will be in the next build: R3

Intelliplug

Bricked Hotplug (Based on MSM_MPDecision from Showp)

Underclocking to 146MHz and OC to 2.88 (If PVS Bin allow it right now, working on unlocking this as well ;) )

Vibrator Strength Control

and . . .

Wake Gestures - As of right now only Sweep2Wake is working. I am still working on DT2W and Sweep2Sleep.

I will continue to work on it with [MENTION=4542027]skulldreamz[/MENTION] to see if we can get everything functioning by end of day tomorrow and if not then I will release what we have. I feel pretty confident that we can get the rest to working.
[X 2014 Original Android Development] 0.0:
Is intellimax going to be part of the release or is that coming at a later time?
[X 2014 Original Android Development] Flamehell:
Tnx man!!!Really appreciate your job!!;)
[X 2014 Original Android Development] RenderBroken:
Yes, the governor that will for sure be added are:

Impulse

Intelliactive

IntelliMM.

Either elementalx or slim, they are similar to each other.
[X 2014 Original Android Development] 0.0:
Idk why I keep stating intellimax. I keep forgetting it's called intelliactive. anyways, that's awesome. thanks
[X 2014 Original Android Development] devoureddreams:
Oh yea!! If you add vibration strength like stated I will be unlocking my boot loader. This is the only flaw with my device is the vibration is way to strong.
[X 2014 Original Android Development] Shemploo:
My car and my Moto X don't like each other, as far as bluetooth playback, my question is:

With this new kernel, can I enable two cores always on?

Someone at some point figured out that you can fix Spotify stutter that happens about every 1 minute by turning 2 Cores always on, and this is what I'm looking to do.

Thank you for your work.

P.S. What app (if anyone knows) would give me the option to control/set that on the kernel?
[X 2014 Original Android Development] 0.0:
You can control how many cores are online when the screen is off

sent from my Moto X Pure Edition
[X 2014 Original Android Development] RenderBroken:
I am still working on the Victara Bringup for Synapse.

The new release will have two more hotplugs to chose from. Personally I love msm_hotplug. I have traveled through MANY different variants and such and the version of msm_hotplug I use is hands down, the best. But all three have an option to set the Minimum CPUs Online Option. You can use Kernel Aduitor from the Play Store. Right now I have it so only 1 core is online while screen is off. You can adjust this with the Max Cores Screen Off tunable in Kernel Aduitor.
[X 2014 Original Android Development] AnimusVoxx:
Any reason why the synapse app says it's not compatible with my device? And what is the render ukm 3.8.1.3 zip do exactly?

---------- Post added at 07:27 PM ---------- Previous post was at 07:25 PM ----------

Ooooooo what is impulse? I haven't heard of this one.
[X 2014 Original Android Development] alvareo:
It's a known bug, RenderBroken is working on it.
[X 2014 Original Android Development] orangestrawberry:
Anyone using settings that gives then good battery and performance?
[X 2014 Original Android Development] alvareo:
This is exactly what I want to know, but I guess I'll wait until there are more governors and such