yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Android Development] eDwS:
Only performance can let my phone extremely smooth?

Enviado de meu XT1572 usando Tapatalk
[X Style (Pure) Android Development] eDwS:
Download link is nor working

Enviado de meu XT1572 usando Tapatalk
[X Style (Pure) Android Development] Fast_Zombie:
Open this thread with browser, Tapatalk cannot into AndroidFileHost links.

---------- Post added at 01:24 AM ---------- Previous post was at 01:18 AM ----------

Performance governor just won't let your cores run at any frequency lower than maximum available at any given time. It is not necessary for day to day use, in fact, it will just burn through your battery without any sense.

This phone, as far as I can see, won't ever be extremely smooth, as Nexus 5 for example. And no governor will ever fix this issue. But, of course, all these tweaks and optimisations implemented by [MENTION=2400758]dirtyhank[/MENTION] work like a charm and make this phone way snappier compared to stock kernel.
[X Style (Pure) Android Development] eDwS:
Have you tried AICP Rom in this phone? It's pretty smooth.

Enviado de meu XT1572 usando Tapatalk
[X Style (Pure) Android Development] Fast_Zombie:
Not yet, I'm waiting 'till guys developing AOSP-based ROMs for this device will squish those little bugs and make their way to official CM repo. I've tried unofficial CM13 ROM, but it wasn't very stable for me. Also, I am missing couple of things from Moto Camera for example. The latest available Moto Camera for CM mod doesn't have exposure/focus point in HDR mode, compared to stock Moto Camera app.
[X Style (Pure) Android Development] eDwS:
I understand you, I'm waiting for AOSP based rom too. Until now, only pure nexus, but it's not working for dual sim, so I'm still looking for a better performance.

Enviado de meu XT1572 usando Tapatalk
[X Style (Pure) Android Development] urimevs509:
the bluactive governors work wonders... my phone is very smooth
[X Style (Pure) Android Development] eDwS:
I'm gonna try it. Thanks!

Enviado de meu XT1572 usando Tapatalk
[X Style (Pure) Android Development] gpz1100:
Many folks are missing the point of nonstock kernel. In and of itself, it won't necessarily do much to improve performance - really depends on it's default configuration. What it does allow you to do is tweak all the things that can't be tweaked on a stock kernel.

* Multiple governors - choose one based on your usage patterns.

* Governor configurables - these let you fine tune the thresholds and other parameters that the governor above uses (not all have configurable options)

* over/underclock

* hotplug options

Think of a kernel as an overbored engine. It's still up to you to choose the heads, cams, crank, fuel, ignition. Wrong set up will make that v8 big block slower than a 4cyl. Properly configured will give you mega HP + excellent fuel economy (ie newer corvettes that can get 30+ mpg on the highway).

If all you do is change kernels or governors and expect huge performance gains, you're missing the bigger picture.

IMO, default settings for this kernel as it comes are a pretty good compromise between battery and performance. If you want more, you'll have to explore the above.
[X Style (Pure) Android Development] eDwS:
Blue active seems to be smoother than interactive

Enviado de meu XT1572 usando Tapatalk
[X Style (Pure) Android Development] elite001mm:
[MENTION=2400758]dirtyhank[/MENTION] Thank you so much for this. The .9 update provided a major boost in smoothness (the normal version, the 300 version didn't work as well in my experience). I was literally unhappy with the purchase of this phone but I think this kernel will change that. Thank you man.
[X Style (Pure) Android Development] countryfolk07:
[MENTION=2400758]dirtyhank[/MENTION]. .9-300 after only a day though, doesn't seem to let the small cores deep sleep. .8 had great deep sleep patterns. I have really had no usage pattern change or app changes. I will flash the standard .9 this evening try that a day or so just to confirm.
[X Style (Pure) Android Development] jason2678:
V9-300 is sleeping pretty good for me. I haven't used it enough yet to gauge actual battery use during active use versus 100.

It's nice and smooth, but so were the earlier versions. 300 might not have quite as many occasional stutters. I've run them all with slightly modified ghostpepper settings.

And it is possible to get it down to one core under low load. It's all about governor and hotplug settings.
[X Style (Pure) Android Development] Note 3 Chicago:
What are your settings, if you don't mind me asking? I've been experimenting with Ghostpepper, Butterfly, and now Eclipse (which seems quite nice). 300 seems to play quite nicely with GPU rendering; I'm thinking I might not even try the 100.
[X Style (Pure) Android Development] somecro:
I installed the new v0.9 and I don't know if it's just a placebo or what,but it feels like my phone is extremely smooth now. Everything feels buttery smooth (except some apps like Play Store).

What are your thoughts on those profiles? I really like ButterFly because it seems really smooth and battery friendly. I tried GhostPepper but it felt like the phone was getting too hot in mundane tasks and usage scenarios,and the battery life suffered more than on ButterFly. Haven't tried eclipse though. I might stick with stock Frannkenclar settings for a bit,especially with v0.9.
[X Style (Pure) Android Development] elite001mm:
Anybody know why I can't adjust touchboost frequencies per core for this kernel in EX? It's been this what in earlier versions. It appears to work fine with the stock optimized kernel. Kernel Aduitor seems to be able to set it.
[X Style (Pure) Android Development] Note 3 Chicago:
I've gotten mixed results. I agree with you on Ghostpepper; I thought it was great sometimes so long as the phone was cool but led to bad lag on thermal throttling. Butterfly controlled heat better, but it seems to have a bit more lag on pre-0.7 versions. However, it was great great great with 0.9-300; I only stopped using it to try eclipse. Eclipse is so far quite intriguing; I'm still playing with it a tad, but I might stick with it.

I will say this, though: Eclipse is definitely faster than Butterfly, but strangely suffers from more dropped frames.

---------- Post added at 04:58 PM ---------- Previous post was at 04:55 PM ----------

@dirtyhank, now that some of us have tested 0.9-300, can you tell us what your thoughts are? I'd love to test my experience against what it's "supposed" to do...
[X Style (Pure) Android Development] jmark13:
For those of you using the Butterfly interactive tweaks, are you also applying hotplug? If so, what are your settings?
[X Style (Pure) Android Development] dirtyhank:
Fair enough. I've been going back and forth between the 100Hz and 300Hz for a week and I'm a bit disappointed, the 300Hz feels smoother most of the time but stutters every once in a while. It's not consistently smooth. The 100Hz version is probably not as smooth but haven't noticed any stutter or unexpected slowdown.

Don't get me wrong, both work fine on my device but I'd say the 100Hz is more trustworthy for now.
[X Style (Pure) Android Development] Note 3 Chicago:
I'm curious: is 300 going to be the default moving forward? It might require some per-device tweaking, but it can be really smooth. Plus, I'd hate to see all your work on it go to waste.
[X Style (Pure) Android Development] dirtyhank:
I want to do more testing/tuning and see if I can get it to behave more consistently. Until then I think it's safer to keep the default at 100Hz.
[X Style (Pure) Android Development] Note 3 Chicago:
Fair enough. Let me know if there's something I can do to help; I may not be any good with coding, but I'm happy to test and tweak. I liked the 100 more at first, but the 300 is really growing on me, and I'm hoping the bugs can be squished. :D

And thanks for all of your work on this!

---------- Post added at 07:31 PM ---------- Previous post was at 07:02 PM ----------

By the way, [MENTION=2400758]dirtyhank[/MENTION], can you confirm one more thing for me? The 300 seems to use a tad more battery than the 100 - not much, but certainly noticeable, particularly when idling. Can you confirm?
[X Style (Pure) Android Development] carlyva:
Hi
[X Style (Pure) Android Development] dirtyhank:
Correct, that's my experience too. Not a big drain compared to 100Hz but measurable.
[X Style (Pure) Android Development] Note 3 Chicago:
Thanks very much. I'm going to keep tinkering with the settings - there have to be some that would mitigate the drain but keep the added smoothness. :D
[X Style (Pure) Android Development] jason2678:
Nothing really special for my settings. I limit the clusters to their stock clock speed limits. I don't adjust anything on ghostpepper target load curves so it doesn't change much about how it runs. Then I try and tweak the idle frequency in hotplug high enough that it doesn't scale and plug/unplug cores like crazy. I think frankenclark has some really good defaults, but some of the custom roms that implement it's features have some defaults that run a little wily. You set the idle frequency too close to the cpu min frequency and the bounce from unplugging a core can kick one right back on again, and you get stuck in this wound-up, bouncy loop.
[X Style (Pure) Android Development] Note 3 Chicago:
Are you running stock rom or custom?
[X Style (Pure) Android Development] jason2678:
Stock.

I like the custom rom options, but the battery life isn't there for me. That was just a general comment on the hotplug defaults I've seen in the custom ROMs with some frankenclark features.

Stock plus gravitybox gets me most of the custom ROM benefit. I miss the notification LED, and I wish there was a slim recents or omniswitch module. Other than those minor complaints, stock on this phone with dirtyhank's kernel is really hard to beat.
[X Style (Pure) Android Development] rehpyc:
jason, this app should help you with the notification light: https://play.google.com/store/apps/details?id=br.com.itsmeton.motoledenabler&hl=en

40% and at 4hr 34m SOT w/ 1d 4h 16m off the charge so far. Looking to be in line with previous versions of the kernel w/ battery life while being a little smoother.
[X Style (Pure) Android Development] jason2678:
I tried that app. Seemed like it only lit up when I had two or more notifications waiting, never on the first. Is it working right for you?
[X Style (Pure) Android Development] rehpyc:
So far it has just fine with Textra. Make sure to select it for the "not optimized" list under android's settings > battery > 3 dot menu > optimization. If you use PowerNap, make sure it's whitelisted.
[X Style (Pure) Android Development] newHere:):
It works fine for me (since the fisrt notification).

The screen where you choose which app will turn the LED on is little bit buggy... So check if every app that you like to turn on the LED is really checked
[X Style (Pure) Android Development] Note 3 Chicago:
[MENTION=2400758]dirtyhank[/MENTION], I have a quick question. Is a 250 hz option possible? That might add some smoothness while avoiding the stutters. I know 250 is used sometimes in Linux, but I've never seen it used in Android, and I admittedly have no idea how difficult it would be here (plus I don't want to give you even more work to do on this). Just a thought.
[X Style (Pure) Android Development] Th3DaRk_Vampire:
What option must check to get missed calls?
[X Style (Pure) Android Development] Psykitt:
Camera looses focus

Hello everybody,

can somebody confirm, that the camera looses the focus

with frankenclark on objects that are 10 meters or more far away.

It's the second time that I have to return to stock kernel because of this issue.

Greetings Psykitt
[X Style (Pure) Android Development] Grafidio:
Im now on 0.9, If I turn my wifi off and on there is a '!' By it and I cannot use Google or anything, I can't load XDA forums etc. Think it messed my wifi up, everything was fine on 0.8

Xt1575 EU version
[X Style (Pure) Android Development] dirtyhank:
Tried that already and it still stutters :(

Just for fun I think I'll try 1000Hz and see how it goes.
[X Style (Pure) Android Development] Note 3 Chicago:
You have to tell us how that goes! That's the linux desktop rate, right?
[X Style (Pure) Android Development] dirtyhank:
Don't know other distros but in Ubuntu normal kernel clocks at 250Hz and the lowlatency version at 1000Hz
[X Style (Pure) Android Development] Note 3 Chicago:
Switched back to the 100 again. The 300 kept freezing, no matter what I did to tweak it.

It's really a shame, because I found it worked so much better than the 100 (much more smooth) when it wasn't freezing, if that makes sense. Does anybody have any settings on the 300 where it doesn't freeze? I'd love to try it again.
[X Style (Pure) Android Development] gpz1100:
^^What are you using as a benchmark for this smoothness?
[X Style (Pure) Android Development] Note 3 Chicago:
Admittedly, it's anecdotal. But there are fewer frame drops, and it's also faster on opening apps. I also notice there's less lag on animations, especially on keyboard animations, on 300 with GPU rendering on. With GPU rendering off, 300 is (at least for me) not as smooth as 100. I have tested the same animations on both the 100 and 300, and gotten these results, in an effort to "check my work"; so I don't think it's confirmation bias.

However, I have noticed the 300 freezes under load, and I have been able to reproduce that over and over again. Typically, it's with floating windows like hoverchat: the 100 does much better with floating windows than the 300 does.

The Nexus 5x have also noticed more smoothness, for what it's worth. http://xdaforums.com/nexus-5x/general/guide-advanced-interactive-governor-t3269557/page290
[X Style (Pure) Android Development] somecro:
What does GPU rendering do actually? The Adreno 418 GPU in SD808 is awful and the main culprit for all the lagginess AFAIK so isn't GPU rendering actually a bad thing? I mean if it forces the GPU even more?

And isn't GPU rendering embedded into most apps/Android since KitKat or JellyBean?
[X Style (Pure) Android Development] Note 3 Chicago:
In Dev options, you can force GPU rendering. That's what I was referring to. And even though the SD808 has a, shall we say, "mid-tier" GPU compared to some others, GPU rendering is still faster and less battery-intensive than CPU rendering. YMMV, of course.

More here, from a person much more well versed than I: http://xdaforums.com/galaxy-s3/help/force-gpu-rendering-t1938081
[X Style (Pure) Android Development] agam1308:
I confirm that, my camera looses the focus too.

Enviado desde mi XT1575 mediante Tapatalk
[X Style (Pure) Android Development] jason2678:
OK. So over one day off the charger. Zero time on wifi, all mobile data. Over 3 1/2 hours screen time, and I'm still at almost 40% battery. I'm not hating the 300hz kernel's stamina :D

Thanks again for all you've done for this phone dirtyhank!
[X Style (Pure) Android Development] gpz1100:
Can you take a pic or two to show what you mean?

I did some basic testing this afternoon, pics look ok to me.

https://drive.google.com/folderview?id=0B2WJL-rQeeExQWdUTl9HZVFvZTg&usp=sharing
[X Style (Pure) Android Development] elite001mm:
I'm one of those people who always checks the force gpu rendering button simply because I've never seen any adverse consequences and it just makes sense for the gpu to render the ui.

I've found though, on this phone checking the disable hw overlays button fixes a lot of frame dropping problems. At least for me. Try it.

In reply to the earlier comments about the gpu possibly being the source of lag.. It isnt, at least not directly. The gpu in the MXP isn't Samsung flagship quality but it's capable of rendering the 1440p systemUI at 60fps (this can be observed on AOSP). Motorola just didn't do a good job of optimization somewhere along the line.
[X Style (Pure) Android Development] dirtyhank:
Tested the 1000Hz version and it's worse than 300Hz, stutters like crazy.
[X Style (Pure) Android Development] dirtyhank:
I've taken a few pics with different focal points and all came out as expected (stock camera app).

Have you tried with different apps? Please send me the logcat+dmesg right after it fails to focus.
[X Style (Pure) Android Development] Psykitt:
Hello dirtyhank,

I tried stock camera and snap camera.

Please try to photograph a street sign or a building in distance.

Within the apartment all seems to be ok but it becomes blurry at about 30 metres.

Greetings Psykitt
[X Style (Pure) Android Development] iNerdBR:
always when i trying this kernel with trupurex mm i got my fast charger dead, the turbo charge dont charge fast, charge so slow, than any normal charger...

Ty, wainting in stock kernel...
[X Style (Pure) Android Development] Note 3 Chicago:
I spent (way too much) time last night on the 300 again, tinkering with the settings to see if I could get it without any stutters. I think I'm almost there! Here's what I found from lots of testing (YMMV, of course, and I am no expert on this):

- 300 doesn't seem to play very nicely with overclocking on the little cores. If you want to overclock, limit it to the BIG cores. Overclocking the little cores causes much more stuttering on the 300. Also, 300 with KSM leads to freezing.

- The 300 works much better with temperature throttling than core control.

- Keep GPU rendering on at all times. Also, [MENTION=5798026]elite001mm[/MENTION] was right about hw overlays.

- There seems to be a compatibility issue with some apps, which makes sense; I think [MENTION=2400758]dirtyhank[/MENTION] mentioned there may be certain apps hardcoded to 100. This compatibility problem is particularly an issue with background services on older apps, like sidebars, which are kept in memory. If you disable those, the problem is much ameliorated. And no, this isn't just a problem of freeing RAM: if I put the MXP under heavy load with lots of services, it has no problem on the 300; it's these particular apps that seem to be problematic. I'll see about a list later.

- Probably related to the above is an issue with live wallpapers. 300 doesn't seem to like live wallpapers. Live wallpapers slow down a device anyway, of course, and this is probably due to the background service, but 300 stutters *a lot* less without a live wallpaper, and *a lot* more with it.

- The biggest culprit seems to be, strangely, swiftkey. Swiftkey has notorious lag problems anyway, but swiftkey hangs badly on 300. Disabling "flow" helps a lot.

I've also noticed that 300, when not stuttering, uses about the same battery as the 100.

I think, after a lot of my experimenting with various settings, that the stuttering is an app problem more than a kernel problem. It is possible to optimize the 300 to remove the stuttering, I *think.* Both ghostpepper and eclipse are really smooth, now, on mine. Butterfly, not so much. Also, bluactive doesn't work that well either, for some reason. I'll keep tinkering.
[X Style (Pure) Android Development] dirtyhank:
Not related, charge control is completely stock.
[X Style (Pure) Android Development] iNerdBR:
Ok, thanks! Related with frank clark here, i try stock+ kernel and solved. Ty! :)
[X Style (Pure) Android Development] dirtyhank:
So your charger is not dead then? ;)
[X Style (Pure) Android Development] dirtyhank:
I guess you guys know we're trying to push the limits of this device, and so bugs and weird things are expected. I always try to test releases on my device as thoroughly as I can but almost everyone uses different setups in one or other way, so it's not a surprise that some of you might hit a bug.

If you happen to find a bug it'd be very helpful if you report it in a way that lets me try to reproduce it on my device, and if possible send me logcats and/or dmesg. Messages like "whatever doesn't work with this kernel" are not helpful, so please take a few minutes to report the problem in a detailed and reproducible way.

Thank you!

PS: From now on I'm ignoring one-line bug "reports" ;)
[X Style (Pure) Android Development] krohme:
Can someone test Hotspot for me? Can't get it to work - worked perfectly on stock kernel
[X Style (Pure) Android Development] CJ-Wylde:
I'll give it a try. Just came back to TruePureX after giving AICP a good stretch of testing. Will probably end up on AICP again after all the kinks get worked out.
[X Style (Pure) Android Development] krohme:
I take it no one else is having issues with Hotspot not working? Tried restoring to stock kernel - still doesn't work, flashing my stock rom on top to undo the changes
[X Style (Pure) Android Development] WelcomeToTheSkye:
Test in less than an hour currently on TruPureXMM with v0.1 and I've had the best battery ever

---------- Post added at 10:38 PM ---------- Previous post was at 10:12 PM ----------

Can confirm working on version v0.2 TruPureXMM v2.4 on my XT1575
[X Style (Pure) Android Development] jason2678:
I was able to toggle on Hotspot on Frankenclark. No other devices handy right now to test if it is actually working - I'll try this evening. Tethering is working for me on xt1575. My laptop is using wifi tethering right now.

FYI - I had some Layers applied, and I did have to disable those to get into the hotspot settings. Settings would FC any time I tried to go into the hotspot and tethering menu with Layers active.
[X Style (Pure) Android Development] WelcomeToTheSkye:
Just noticed this now but charging using this kernal seems to be massively increased. I went from 65% to 90% (25%) in 10 minutes. Using the stock kernal or even VadimTK's that would average around 35 minutes for me.
[X Style (Pure) Android Development] playenball:
Can confirm that it boots and has been running smooth on TruPure for over an hour now.
[X Style (Pure) Android Development] ffonegod:
Hitting 75k antutu score with this kernel on truepure rom.. Phone blazing fast
[X Style (Pure) Android Development] MrMeeseeks:
Running great here. Stock rooted.
[X Style (Pure) Android Development] WelcomeToTheSkye:
Damn using AnTuTu I am getting a score 76441 and I can rank ninth place. This phone can compete with flagships now it's crazy!
[X Style (Pure) Android Development] Shishir Singhal:
https://drive.google.com/file/d/0B3SUykgjhPtpTjZGdGhkSTlKMnc/view?usp=sharing
[X Style (Pure) Android Development] dmb219:
0.2 is running good on stock rooted rom, seems very responsive. Apps that were a little sluggish seem quicker, Google + for one. Thanks for sharing.
[X Style (Pure) Android Development] krohme:
Thanks for testing bro, can't figure out why on my xt1572 hotspot & wifi refused to work :what:

maybe cos I'm on stock Indian mm I should have flashed the Indian mm firmware afterwards, I'll probably try again this weekend because performance and battery is noticeably better on this kernel - compared to stock.
[X Style (Pure) Android Development] dirtyhank:
This boot.img is rooted, I'd rather use a vanilla stock one if you have it around.

Thanks
[X Style (Pure) Android Development] amit.lohar:
HERE IS THE LINK for boot.img of 6.0 xt1572 dual sim, completely stock
[X Style (Pure) Android Development] dirtyhank:
Ok, I created a new image with the ramdisk from this stock kernel. Please test and report:

http://www.mediafire.com/folder/i66lr22aautce/test_dual_sim
[X Style (Pure) Android Development] krohme:
@ dirtyhank first of all thanks for the custom kernel!

Now when I flash the xt1575 version on my xt1572 - the device boots up fine but no wifi or Hotspot, I tried the new 0.2 for xt1572 & it gets stuck @ the boot screen, is it because I'm rooted? Not sure. I see someone has kindly provided you with the stock img for xt1572, if you make a new 0.2 version can you also make it Bootable for rooted phones.

Much appreciated

:)
[X Style (Pure) Android Development] Shishir Singhal:
works thank u [MENTION=2400758]dirtyhank[/MENTION] wifi works now and device feels much smoother
[X Style (Pure) Android Development] krohme:
Are you rooted?
[X Style (Pure) Android Development] Shishir Singhal:
Yeah had to reroot after flashing kernel
[X Style (Pure) Android Development] dirtyhank:
Sorry but I can't reproduce the issue on my device. Took a few pictures outside this morning and all looked as intended. Here's an example, same location with near and far focal points:

https://imgur.com/a/mhmWS