dany20mh wrote:Any update on the M build?!
Not yet, not sure what exactly to do ... will have a look if I can spare some time whis WE.
JP.
Sent from my Nexus 6 running Yank555.lu SlimLP 5.1.1 on Yank555.lu v1.1 kernel.
dany20mh wrote:Any update on the M build?!
tinydynamite00 wrote:Hi Yank555! Finally getting about to post in your forum. Alas, distractions everywhere.
I've been really fond of your Slim builds, running them since early May without issue, until now. Back to stock temporarily as the 26.06.2015 build seems to be cause of my device overheating. I run the stock kernel as is and the only "mod" I use is a Layers theme. Apologies for not providing logs rather than suppositions. I understand little help can come from guessing. Just curious whether I'm the only one with the heating issue, 50°~C generally.
tinydynamite00 wrote:I was using active display without adaptive mode, color calibrating to a Night hue as I always run brightness at 0%; sans ambient or adaptive control for battery life. I'm usually screen on & multitasking more oft than not. While on the 26.06 build, I noticed my screen "rippling" black/grey tones neath the surface, and although screen tearing upon app switching is largely reduced if not altogether gone, the GPU is notably stressed so I have to shut off the device for it to cool.
tinydynamite00 wrote:BTW, I'm using Slim mini GApps and auto-restored a relatively condensed amount of user apps from Play. 127 total system/user apps while optimizing.
tinydynamite00 wrote:Some last question that will likely sound dense: How is it debugging mode is automatically enabled even though Dev Options, from my perspective, is not visible nor user activated from tapping the build number? Is it due to SELinux being set permissively by default?
tinydynamite00 wrote:Sorry, I have security concerns, am awfully green with Linux, and been watching too many DefCon vids Trying to find the best means of securing against remote shell injections & unsolicited client - e.g. ssh, telnet - tunneling. Reduced to one device and I can't read/learn fast enough. Can't remember the 2-3 lines right now but I'm sure the "?? debugging=disable" + "setenforce=1" can be init scripted to persist across boots.
May flash your updated kernel with a few config changes. See if it helps. Thank you for sharing your work and time!
>rm user verbose (poor syntax; going for humor)
tinydynamite00
frankymix wrote:Keep us updated if you have anything planned for Android M!
frankymix wrote:Yank my friend, i will be getting the nexus 5x when it releases.
I was wondering if you will be getting that phone as well?
Your kernel is still thus far the one to beat imo.
Sent from my LG-H811 using Tapatalk
Users browsing this forum: No registered users and 9 guests