yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Android Development] unitz0mbie:
Does anyone know if app loading depends on kernel? Sometimes I feel like it takes a bit long to load
[X Style (Pure) Android Development] ffonegod:
More got to do with ram management
[X Style (Pure) Android Development] dirtyhank:
It depends of several factors, to name a few:

Free RAM: if there's not enough free RAM the kernel needs to swap out some of the apps and maybe even kill a few

File system fragmentation: F2FS isn't very prone to file fragmentation but if there's not much free space and there are tons of apps installed you can still get some fragmentation

I/O scheduler: Some favor read over write, some random access, etc... you have to find the right one for your setup. For app loading probably FIOPS is best

Read Ahead: Usually app loading involves a lot of sequential read operations so a high RA value should perform better

Multitasking: The less apps running in the background, especially if they try to access disk, the better

CPU speed: Usually the faster the CPU the sooner some of the init tasks are finished
[X Style (Pure) Android Development] gavsi:
this kernel work custom rom ?

dirtunicorn or cm mod ..
[X Style (Pure) Android Development] rehpyc:
There's the CPU side of things (freq and number of cores) that handle the loading of the app into memory/other apps out of memory if necessary (if you use zRAM, it uses the CPU to compress the app data). Then there's also the RAM side of things, where it depends if enough RAM is available to load the app w/o having to release apps to free RAM, how many apps you want to keep in RAM, if you use zRAM or not, etc. These things work in tandem with the kernel, so the kernel itself can affect things, but it's primarily how you've configured the CPU and RAM management.

Edit: lol dirtyhank was replying at the same time, so everything he detailed
[X Style (Pure) Android Development] unitz0mbie:
Thank you very much for the replies, ill try the FIOPS configuration, how high can i go in RA, i have both set to 2048 now? i can max it out?
[X Style (Pure) Android Development] dirtyhank:
2048 is high enough, I doubt anything higher will perform much better. Actually a very high RA can make things worse, especially at small random reads.
[X Style (Pure) Android Development] rehpyc:
RA is a tricky thing.. The ideal value to use will be different between different types of usage of your phone and apps you use as well as the scheduler you use. Noop is good for battery, sio/sioplus/fiops are typically regarded as best for balance, and then deadline best for performance. There's quite a few guides available that break them down, but just don't worry much about synthetic benchmarks comparing them.

I tried doing some benchmarking of my own, and I think dirtyhank had when he and I discussed it, and couldn't find much performance difference between 1024 and 2048. Some things like LSpeed and other 'tuning' apps/guides will actually set things lower.
[X Style (Pure) Android Development] unitz0mbie:
so you recommend not using any of the LSpeed apps?
[X Style (Pure) Android Development] rehpyc:
There's definitely benefit to the app, but I would read up on each setting. Without too much detail, there's settings that will make your phone smoother at the expense of battery life (much the same as changing cpu/ram management settings), but there's also a lot of settings that are kinda archaic from older versions of Android (they'll work, but not really provide any noticeable benefit). Overall, it is a nice app that provides you some more control over the feel of your phone, for those that don't know how to change the settings manually and use an init.d script.
[X Style (Pure) Android Development] unitz0mbie:
thanks a lot, i would love to learn the manual way to do it. but i have no idea where to start, is there any video or tutorial?
[X Style (Pure) Android Development] omaralkha99:
can i install this on dirty unicorns, i just got this phone and this is my first rom
[X Style (Pure) Android Development] unitz0mbie:
No
[X Style (Pure) Android Development] dirtyhank:
Ok guys, 6.0.1 testing time :)

In the past few days I tried to merge/rebase v0.14 with new stock 6.0.1 branch but didn't work very well, too many conflicts. I ended up porting all frankenclark specific stuff on top of a clean 6.0.1 branch, which although it required more work I think it'll be much better in the long run.

I decided to bump version up to 1.0 just so it's easier to know which versions are for 6.0.0 and which for 6.0.1, but feature-wise v0.14 and v1.0 are identical. Only differences are those introduced by Motorola between 6.0.0 and 6.0.1.

IMPORTANT: Don't flash v1.0 unless you're on full stock 6.0.1, and even if you are keep in mind this might be unstable. If you're on 6.0.0 or 6.0.1 with a downgraded modem you'll need to flash the 6.0.1 modem. You can do it by downloading a 6.0.1 factory image (XT1572 for reference) and running these commands from flashboot:

fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2

https://www.androidfilehost.com/?fid=24694152805484885

Please, give it a try a let me know how it works for you. I won't be pushing it to the OP until we're sure it's safe.

EDIT: I forgot to mention that, besides the right modem version, proper root is still mandatory for the WiFi to work.
[X Style (Pure) Android Development] ilovemeow:
cant wait for test,

thanks
[X Style (Pure) Android Development] unitz0mbie:
I have a xt1575 will it work? I'm using 6.0.1 with the modem of truepure
[X Style (Pure) Android Development] chris_dis:
I'm on 6.0.1 and have never done anything to the modem but Wifi doesn't work. Going to try out your method and see if it works. Cheers for your great work :)

Edit: Flashed the modem, still no wifi :( It always changes to off
[X Style (Pure) Android Development] unitz0mbie:
same, just gonna do a clean wipe and start with a fresh rom
[X Style (Pure) Android Development] ilovemeow:
i flash 6.0.1 kernel straight from stock rom...work fine with wifi
[X Style (Pure) Android Development] dirtyhank:
If WiFi won't work on v1.0 please report the exact ROM build and modem version.

For the record mine are MPH24.107-58 and 29.01.88.02R EMEA
[X Style (Pure) Android Development] chris_dis:
Mine is MPHS24.107-58-1 and 29.01.88.02R CLARK_EMEA_CUST, it is the odexed and rooted version from this forum. Mobile data is working btw
[X Style (Pure) Android Development] unitz0mbie:
same, data works. not wifi
[X Style (Pure) Android Development] ilovemeow:
for your reference
[X Style (Pure) Android Development] dirtyhank:
Can you guys give a try with this modem? It's the one I'm currently using and works fine on EU 6.0.1 ROM.

https://www.androidfilehost.com/?fid=24591000424964058

EDIT: This is not a flashable ZIP, you have to unzip the modem and flash from fastboot as instructed in the release notes
[X Style (Pure) Android Development] ilovemeow:
might be rom version?

ours MPH

and theirs MPHS?
[X Style (Pure) Android Development] dirtyhank:
Could be, a logcat+dmesg right after trying to switch WiFi on might help.
[X Style (Pure) Android Development] unitz0mbie:
After I tried the 6.0.1 kernel I decided to try stock kernel and it performs really well like app switching and loading, what settings do I need to put into frankenclark to get the same fluidity
[X Style (Pure) Android Development] chris_dis:
I made a logcat and dmesg, was my first time so hopefully I did it right. Seems like I can't attach it here, should I send it to you directly?
[X Style (Pure) Android Development] unitz0mbie:
Went back to .14 didn't use any scripts to see how it works, still no luck with 6.0.1
[X Style (Pure) Android Development] volldez:
Working fine here!:) Build: MPH24.107-58-1. Had to install modem as per Dirtyhanks instructions (no wifi) booted and all is well! Seems a little smoother and faster upgraded from v.13.
[X Style (Pure) Android Development] ban.codrut:
Works great here, using build number MPHS24.107-58-1 and baseband 29.01.88.02R EMEA

Thanks [MENTION=2400758]dirtyhank[/MENTION] for rebranching it!
[X Style (Pure) Android Development] dirtyhank:
I've just had the chance to take a look at your logs and looks like you're using an old modem. Here's the error from dmesg.log:

Hash Mismatch
wlan: [3719:F :VOS] db 75 c1 85 cc 50 1a ae a2 cf e5 de 94 17 35 86
wlan: [3719:F :VOS] dc 1e ca 6b 56 09 91 c7 97 c1 c7 9f c3 b5 4d 67
wlan: [3719:F :VOS] 47 9b ea a3 66 8e 3a ab 35 54 8d aa f6 e5 a5 d6
wlan: [3719:F :VOS] 85 7c 3d e7 eb 0d 9a a0 27 b9 fb 16 25 41 47 a4
Hash Check failed for file:qwlan30.bin

As you can see on this commit that hash matches the one from dmesg.log so you're using modem 2.0.5.18. Latest is 2.0.5.22.

I suggest you try flashing the modem I posted yesterday and let us know.
[X Style (Pure) Android Development] chris_dis:
I flashed the wrong modem yesterday :crying: Everything is working now, thank you for your help :D
[X Style (Pure) Android Development] mort_subite:
Unless I'm missing something, I just have to flash this through TWRP, correct? The kernel has definitely flashed properly, but I wasn't given an Aroma installer screen... any ideas?
[X Style (Pure) Android Development] kadopt:
No aroma? Then it didn't flash properly, re-download the file and flash again.
[X Style (Pure) Android Development] dirtyhank:
If you mean the modem file I posted yesterday it's not a flashable ZIP, you have to unzip it and flash the modem file from fastboot (see release notes).

Sorry for the confusion
[X Style (Pure) Android Development] mort_subite:
Super weird... I flashed this file

frankenclark-0.10-300hz.zip

from the download page, and it definitely flashed properly, but gave me no Aroma installer.

Looking at the download page now it seems the version I flashed is an older version than the current version, which is definitely my bad for not noticing, but why is the download section of the OP so confusing? Why is the main, most obvious link a link to a page full of deprecated versions? Even the page it takes you to is confusing because it has two versions older than the newest version on that page stickied to the top with no explanation why or what their differences are aside from file name and obvious implication (100hz vs 300hz). I mean, yeah, I should have checked the release notes for the download page for the current version, but Im just saying that's super confusing. It makes it seem like it's just a link to the release notes and not a totally separate page necessary to access the download for the current version.

I definitely got my current issue sorted, but whoever's in charge of managing that post might want make that part of the original post a little clearer unless theres some kind of technical reason why it is the way it is.
[X Style (Pure) Android Development] SpasilliumNexus:
How much clearer does it need to be? Even if you didn't read the release notes, it says right in the thread title "v0.14."

I'm going to guess the link to the whole folder is easier to use rather than cluttering up OP with additional links to old and new versions.

Also, AFH defaults sorting to A-Z, in which you have to manually sort by newest on the page. Nothing can be done for him to change that behavior.
[X Style (Pure) Android Development] dirtyhank:
My time is limited and I'd rather spend it developing than tidying up a post almost nobody reads anyway. As for the androidfilehost default sorting method I know alphabetical by default is weird but there's always the magic button :p
[X Style (Pure) Android Development] unitz0mbie:
for you guys what you have found to be the smoothest setup with this kernel
[X Style (Pure) Android Development] volldez:
Stuck between Fairpark and default francenclark, both quick and smooth! Francenclark a little quicker, Fairpark a little smoother.
[X Style (Pure) Android Development] dirtyhank:
Guys, I need some help with the v1.0 modem version situation. Those of you on 6.0.1 could you run the following command on a root shell (it doesn't matter whether it's from ADB shell, terminal or TWRP):

sha256sum /firmware/image/qwlan30.bin

Compare the output against the following list and let me know which modem version you are running (I'm omiting most of the SHA256 bits for simplicity):

2.0.5.22: 479bea...a4

2.0.5.20: a5b2f0...6d

2.0.5.19: fef120...be

2.0.5.18: db75c1...67

2.0.5.13: 80fe94...4e

For the record, you must be running 2.0.5.22 for v1.0 WiFi to work.

Thanks!!!
[X Style (Pure) Android Development] unitz0mbie:
With default scripts the phone doesn't get as hot anymore and it is fast
[X Style (Pure) Android Development] ilovemeow:
mine one

479.......47a4 /firmware/image/qwlan30.bin
[X Style (Pure) Android Development] volldez:
Running version 2.0.5.22: 479bea...a4 here! working great!

Thanks!
[X Style (Pure) Android Development] unitz0mbie:
does anyone know if the i/o/ misc/gpu settings by [MENTION=3004396]rehpyc[/MENTION] are faster than the default ones? or are they meant for smoothness?
[X Style (Pure) Android Development] volldez:
I think it's meant for battery saving mostly.
[X Style (Pure) Android Development] ryansc375:
Flashed the updated modem file with latest TWRP on 6.0.1 stock and wifi works on kernel ver. 1.0! However, if I go to display under settings and I try to enter color mode the settings app crashes. Don't know if it's kernel related. Clearing data didn't help. Also, under CPU-Z, it's lists that's cores 4 and 5 are "stopped". Don't know if that's normal. Thanks for the hard work!
[X Style (Pure) Android Development] dirtyhank:
Oops, I get that crash too, gotta take a look.

As for the stopped cores it's the hotplug, normal if you're not doing CPU intensive work. Go into Play Store and install an app, or even better update a few, you should see big cores ramp up while apps are "compiling"
[X Style (Pure) Android Development] volldez:
Did a clean install to check color mode of 6.01 with FC v0.13 kernel and it crashed right away. Hope this helps.
[X Style (Pure) Android Development] chris_dis:
I think the color mode settings crashing is a common bug, it's there for quite some time
[X Style (Pure) Android Development] ban.codrut:
I'm running the .22 version. Those files get updated with the NON-HLOS right ?

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

ANNOUNCEMENT

In a few weeks I'm going to share some governor tweaking bash scripts and as well some Kernel Adiutor profiles in which I'm gonna do the same tweaks as the scripts but as well as tweaking the hot plugging system in base of the profile ( I will also try to copy the two colour profiles in KA for those who have crashes and find the usefulness of them)
[X Style (Pure) Android Development] dirtyhank:
Yep, all files mounted under /firmware come from the NON-HLOS image
[X Style (Pure) Android Development] MrMeeseeks:
[MENTION=2400758]dirtyhank[/MENTION] Color mode crash is a known xposed bug.
[X Style (Pure) Android Development] dirtyhank:
I've been reading about Magisk and it sounds very promising stuff.

Anybody tried it already? Does Xposed work fine systemlessly? It'd really cool if using Magisk one could get Xposed and SafetyNET getting along.
[X Style (Pure) Android Development] SpasilliumNexus:
Been running 0.14 of your kernel with Magisk, Phh's Superuser, and the Magisk version of Xposed, on my own semi-stock 6.0 for almost 3 weeks now, and have had no problems with any of it whatsoever.

The only (very minor to me) inconvenience I have is for me to use Android Pay, I have to disable Xposed and then reboot, followed by disabling root. Since I have Tasker set to disable root upon opening any SafetyNet enabled app, automatically, I can skip that extra step of using the Magisk app to disable it.

As for Pokemon GO, which supposedly has SafetyNet in the recent build, still works by simply using the Magisk app to disable root, or have Tasker set up to disable it automatically.
[X Style (Pure) Android Development] dirtyhank:
The Tasker task is a neat trick. Besides Android Pay all other SafetyNet enabled apps work? My goal is getting my bank's pay app to get along with Xposed.
[X Style (Pure) Android Development] SpasilliumNexus:
The other two that I know of are the Helper Sample and Playground apps, both which pass even with root disabled, but Xposed enabled, which shouldn't.
[X Style (Pure) Android Development] MrMeeseeks:
I'm using magisk with phh's superuser and magisk systemless xposed. Everything seems to work fine. You don't have to disable xposed this way. Just turn off root with magisk. Android pay and PoGo both work this way. I think I'm just going to leave root turned off until I need it this way.
[X Style (Pure) Android Development] ilovemeow:
pgo still not working sad lol

using 2.62-3systemless root
[X Style (Pure) Android Development] stigers:
pls instruct me how to use phh's superuser, now my device is rooted via superuser 2.62-3.zip, which seems is a systemless root. I have tried all xposed version, including magsik(topjohnwu 86.5), all stopped the xstyle 1752 during bootanimation to a black screen. thanks. I will try phh's root with xposed.

By the way, frankenclark 1.0 works great on my device for over 100 hrs.
[X Style (Pure) Android Development] SpasilliumNexus:
Update: It turns out I can use Android Pay with Xposed enabled, only if I use the Magisk app to disable root. For some reason, the Tasker method can disable it, but AP still fails as early as trying to add a card. However, the Tasker method works perfectly with AP without Xposed enabled.

If only the Magisk app had intents built in for the use with Tasker, and the switches in the app was reliable...
[X Style (Pure) Android Development] unitz0mbie:
I'm for some reason on the 100hz version my phone won't wake from sleep mode unless I tap it a lot of times sometimes I even have to reboot, I'm going back to 300hz
[X Style (Pure) Android Development] kadopt:
Why you guys still use supersu V2.62-3?

If you want systemless with V2.78 or later just do the following:

Download supersu V2.78 or later, reboot into twrp, go to advanced and open terminal then input this command:

echo SYSTEMLESS=true>>/data/.supersu

then flash supersu, that command forces systemless install.

Cheers
[X Style (Pure) Android Development] ilovemeow:
already done with it :) thanks dude :D
[X Style (Pure) Android Development] rrat:
Awesome,
[X Style (Pure) Android Development] killa408shark:
Question guys currently I'm on stock rooted previously i was on Tru pure with Franken kernel. So I wanna flash this it seems my phone runs better with franken on the aroma should I just leave it on default or what you guys recommend
[X Style (Pure) Android Development] Droc1983:
Is there a way to get an updated stock rooted rom?
[X Style (Pure) Android Development] SpasilliumNexus:
Completely wrong place for this. And there's a thread that has one.
[X Style (Pure) Android Development] Cowbell_Guy:
I'm getting lots of random reboots on latest version. Any ideas?
[X Style (Pure) Android Development] shopealope:
Are you overclocked? At least for me, my phone is not very tolerant of overclocking.
[X Style (Pure) Android Development] gemtin92:
About q&a:

Nothing changed in terms of downgrading modem before flashing on stock rooted 6.0.1 xt1572? I have to do this before flashing 0.14 version of this kernel?

Tapatapatap Moto X Style
[X Style (Pure) Android Development] Naddict:
No, you should not have to do anything out of the ordinary to flash the new version.
[X Style (Pure) Android Development] ban.codrut:
Any news on a possible v1.1 6.0.1 kernel ?
[X Style (Pure) Android Development] dirtyhank:
You mean v0.14 or v1.0?
[X Style (Pure) Android Development] dirtyhank:
I've got myself a OnePlus 3 this week and in the process of testing as much stuff as possible I've installed Magisk+Xposed+Automagisk. This setup is pretty cool, my bank's NFC payment app works beautifully and I don't even have to do anything, Automagisk takes care of disabling/enabling root whenever I open/close the app. Let's hope it stays this way for a while.

Thanks for putting me on the right track :)
[X Style (Pure) Android Development] MrMeeseeks:
How are you liking the Oneplus 3? I just ordered one myself. So will I be seeing you over in that forum as well?
[X Style (Pure) Android Development] dirtyhank:
I'm loving it, what I like the most so far:

CPU is fast, no lag or stutters

6GB of RAM make multitasking experience great

Fingerprint sensor is insanely fast. Not 100% accurate but quite close

The not so good stuff:

Speaker volume and sound quality is so-so, gonna miss the front facing speakers

WiFi range is a bit on the short side, I've had to tune the hell out of my router to get decent WiFi speed at home

I thought I'd miss the QHD screen but 1+3 screen is pretty good and very crisp for a FullHD, default color calibration sucks though, fortunately there's a sRGB mode. Some people complain of pentile artifacts but it hasn't bothered me so far.

Overall it's a great device for the price :)
[X Style (Pure) Android Development] MrMeeseeks:
I'm glad they have the sRGB mode since I like to change the color on this phone. It's too yellow for my taste. It's nice that you don't have to have a custom kernel to change it because I'm honestly considering not unlocking/rooting it. It's too much of a hassle trying to stay ahead of SafetyNet for root and xposed. Hopefully the Wifi range won't be a problem because I live in a small house and the router is pretty close to the living area/master bedroom. But I will probably miss the front facing speakers. They are awesome on this thing. But anyways, thanks for the really helpful review.
[P3300, MDA Compact III ROM Development] rickgillyon:
Does anyone know if there is any way to make the volume changes in smaller steps in HTC Audio Manager? I'd rather change it 1% at a time rather than 5%. Couldn't find anything on search, maybe there's a registry setting available?

Thanks!
[P3300, MDA Compact III ROM Development] beatjost:
volume step

Does noone know an answer to reduce the volume steps from 5% to 1%? This would be very usefully for listening with headphones...
[P3300, MDA Compact III ROM Development] handofcode:
http://xdaforums.com/showthread.php?t=395695&highlight=hermes
[P3300, MDA Compact III ROM Development] fredezzz:
This doesn't really answer the question...

I've got a HTC Touch Diamond and feel the same problem.

When I press the volume hardware buttons, the volume increases / decreases by steps of 3 bars. I also would like to modify it by single steps (or even less)

Isn't it a registry settings for that?

Thank's
[P3300, MDA Compact III ROM Development] neotarum:
Possible work-around?

Hi,

What I do with my MDA compact 3 is this:

Main Volume icon (next to battery on top bar) works independently to my volume control in WMP.

If you have max volume on icon indicator, and have 50% on WMP, then you will have 50% volume.

But if you change the icon to 50% of volume, and have 50% on WMP, then you have halved the volume...ie 25%...

So you can fine tune using both volumes..

I hope it makes sense...!! :)
[P3300, MDA Compact III ROM Development] fredezzz:
I'm not really interested in WMP.

Anyway, in my HTC Touch Diamond, hardware buttons and main volume icon (as you described) are the same.

So thank's for trying, but it doesn't solve this issue ;-)
[P3300, MDA Compact III ROM Development] neotarum:
I tried at least, sorry it was no help. :(

Best wishes
[P3300, MDA Compact III ROM Development] theosoft:
Me too ! 3bars each time! 15%!

Can anyone help?
[P3300, MDA Compact III ROM Development] sheennick123456:
you can try the volume controller on headsets
[P3300, MDA Compact III ROM Development] fredezzz:
Exactly the same behavior with the headset.
[P3300, MDA Compact III ROM Development] nicky-xda:
it's disturbin me as well that it's not possible to change the volume in single steps.

Who can help?
[P3300, MDA Compact III ROM Development] MusX:
still no any sollution?
[P3300, MDA Compact III ROM Development] Diamond_Mike:
There is a program, it`s called volumex. It does exactly what you want but it's not free.

It costs around 10$ but there is also a trial version to check if it fits your needs.