yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Android Development] dirtyhank:
This is due to version mismatch between the modem firmware and the WiFi driver in the kernel. If you flash the 6.0.0 modem firmware you'll get WiFi back, but I don't know what side effects that might have, do it at your own risk ;)

Yep, we need at least the updated sources for the WiFi driver.
[X Style (Pure) Android Development] Spyke_:
Wifi seems to work perfectly on 6.0.1 with my device
[X Style (Pure) Android Development] dirtyhank:
It works because your modem firmware is not updated.

EDIT: Are you having any problems with 3G/LTE connectivity?
[X Style (Pure) Android Development] elite001mm:
[EDIT] Delete, sorry
[X Style (Pure) Android Development] Psykitt:
Hello everybody,

camera focus with test 2 is as sharp as the original!

300 Hz with both scripts and little 1.5 / big 2.1 is very fast

and smooth and battery friendly - I will stay with this one!

I have screen size 900x1600 and density 320.

Greetings and big THX from me!
[X Style (Pure) Android Development] dirtyhank:
I'm releasing final v0.11. I've made some minor modifications to the scripts section of the Installer. Just merged both rehpyc scripts (GPU max freq is 600MHz) and added script to start DT2W or S2W on start-up.
[X Style (Pure) Android Development] ggs2:
There is no .install.log in aroma directory

However, I hvae recovery.log in /tmp directory, below is snippet, if it helps

I:Zip does not contain SELinux file_contexts file in its root.

I:Legacy property environment initialized.

aroma/s: Initializing

Starting AROMA INSTALLER version 3.00

(c) 2013-2015 by amarullz.com

Starting AROMA INSTALLER version 3.00

(c) 2013-2015 by amarullz.com

aroma/s: Mute Parent

aroma/s: Saving Arguments

aroma/s: Open Archive

aroma/s: Initializing Resource

aroma/s: LINUXFBDR_ion_init overlay_supported

aroma/s: LINUXFBDR Init 32bit Colorspace

aroma/s: FRAMEBUFFER INFORMATIONS:

aroma/s: VAR

aroma/s: xres : 1440

aroma/s: yres : 2560

aroma/s: xres_virtual : 1440

aroma/s: yres_virtual : 5120

aroma/s: xoffset : 0

aroma/s: yoffset : 0

aroma/s: bits_per_pixel : 32

aroma/s: grayscale : 0

aroma/s: red : 0, 8, 0

aroma/s: green : 8, 8, 0

aroma/s: blue : 16, 8, 0

aroma/s: transp : 24, 8, 0

aroma/s: nonstd : 0

aroma/s: activate : 128

aroma/s: height : 125

aroma/s: width : 70

aroma/s: accel_flags : 0

aroma/s: pixclock : 1108

aroma/s: left_margin : 44

aroma/s: right_margin : 120

aroma/s: upper_margin : 4

aroma/s: lower_margin : 8

aroma/s: hsync_len : 16

aroma/s: vsync_len : 4

aroma/s: sync : 0

aroma/s: rotate : 0

aroma/s: FIX

aroma/s: id : mdssfb_90000

aroma/s: smem_len : 29491200

aroma/s: type : 0

aroma/s: type_aux : 0

aroma/s: visual : 2

aroma/s: xpanstep : 1

aroma/s: ypanstep : 1

aroma/s: ywrapstep : 0

aroma/s: line_length : 5760

aroma/s: accel : 0

aroma/s: Framebuffer Initialized (1440x2560px - 560 dpi)

aroma/s: Opening Freetype

aroma/s: INDR Input Device: qpnp_pon (event2) - Class : 1

aroma/s: VKN : 0, CALIB : (0,0,0,0)

aroma/s: INDR Input Device: sensorprocessor (event0) - Class : 1

aroma/s: VKN : 0, CALIB : (0,0,0,0)

aroma/s: INDR Input Device: gpio-keys (event5) - Class : 1

aroma/s: VKN : 0, CALIB : (0,0,0,0)

aroma/s: INDR Input Device: msm8994-florida-snd-card Headset Jack (event4) - Class : 0

aroma/s: VKN : 0, CALIB : (0,0,0,0)

aroma/s: INDR Input Device: msm8994-florida-snd-card Button Jack (event3) - Class : 1

aroma/s: VKN : 0, CALIB : (0,0,0,0)

aroma/s: INDR Input Device: synaptics_dsx_i2c (event1) - Class : 6

aroma/s: VKN : 0, CALIB : (0,1439,0,2559)

aroma/s: Starting Interface

aroma/s: aroma-config was UTF-8

aroma/s: (2) Freetype fonts loaded as Font Family

aroma/s: (2) Freetype fonts loaded as Font Family

---------- Post added at 12:54 AM ---------- Previous post was at 12:51 AM ----------

Is it not possible to install .11 without aroma?

For me even camera doesn't open.. gives camera error (on v.10)
[X Style (Pure) Android Development] dirtyhank:
I'm afraid the recovery.log is not very helpful.

I think there's something wrong with your device. I'd install the factory image making sure you format, at least, userdata and system partitions.
[X Style (Pure) Android Development] harshi1:
Hey [MENTION=2400758]dirtyhank[/MENTION], I know this is an unnecessary think to ask for, but do you think you can add the zzmoove governor. I heard a lot of really great results with battery life wise. I am trying pretty hard but still am confused and getting errors, when i try to add it, mainly with the zImage, therefore not being able to flash it.
[X Style (Pure) Android Development] note3userr:
Loving the new update. So much easier loading a profile from flash rather than trying to run scripts
[X Style (Pure) Android Development] ilovemeow:
thanks mate, installed 0.11 and testing :)
[X Style (Pure) Android Development] beefgoat:
I had to go back to version 1 of the .11 test kernel. There were issues with loading times of apps and overall smoothness when used without any app installed for adjusting kernel settings installed on my device.
[X Style (Pure) Android Development] rehpyc:
Would you guys prefer scripts to run like last time or a zip to flash?

If some of you could provide BBS logs after each day's use, it'll help me with further enhancing the script (just pm me them). Input is helpful in whether you guys would prefer more performance or battery.
[X Style (Pure) Android Development] screech:
I am a sucker for battery ;)
[X Style (Pure) Android Development] EarthboundHero:
I think a ZIP is better, no extra app needed. I'll always pick battery over performance, with this phone at least. Also, if I don't have BBS, would screens of my stock battery stats be okay?
[X Style (Pure) Android Development] dirtyhank:
That's weird because kernel images are exactly the same, just changed the version string. Have you tried wiping cache after installing?
[X Style (Pure) Android Development] beefgoat:
I wiped both caches after installing every time. One thing I did see after installing Kernel Aduitor on the v2 test kernel was that cores 1-4 had a touchboost of 756mHz. I've also experienced a similar decrease in performance when setting such a high number of cores with a touchboost setting.
[X Style (Pure) Android Development] ggs2:
Did clean format, and flashed stock and .11 kernel again. things are working now...would be able to update more on abttery in a day or two.. Thanks :)
[X Style (Pure) Android Development] dirtyhank:
That's normal if you applied the rehpyc script. Don't apply any script and tune it to your liking ;)
[X Style (Pure) Android Development] dirtyhank:
Tried but it's not a direct port so some recoding needs to be done. Will try in the future but don't hold you breath ;)

You can achieve pretty good battery life with some of the current governors. It's more about how you tune all parameters than the governor itself...
[X Style (Pure) Android Development] dirtyhank:
I've just updated to 6.0.1 and can confirm that flashing 6.0.0 modem will get WiFi back. 4G seems to be working fine too. Will test more and let you know.

It might be a placebo effect but the ROM seems a bit snappier.

For the record, my device is a XT1572 and I'm using the ROM XT1572_CLARK_RETEU_6.0.1_MPH24.107-58.
[X Style (Pure) Android Development] dribr:
Can I dirty flash 0.11 version on TruPure 2.8.2 with 0.10 kernel version?

Enviado de meu XT1572 usando Tapatalk
[X Style (Pure) Android Development] newHere:):
Yes.

There is no problem.
[X Style (Pure) Android Development] dottat:
Anyone else seeing an issue where the screen doesn't wake on ring?
[X Style (Pure) Android Development] unitz0mbie:
happens to me too, but no problem for me, saves battery and u can just press the sleep button and it works fine
[X Style (Pure) Android Development] dirtyhank:
Happens all the time? What version? Are you running any custom settings? Do you have DT2W/S2W enabled?
[X Style (Pure) Android Development] dottat:
I don't have either enabled. Just noticed it today and flashed .11 last night. Haven't done any troubleshooting
[X Style (Pure) Android Development] ffonegod:
My screen doesn't wake on ring as well
[X Style (Pure) Android Development] dirtyhank:
Guys, you need to be more specific. If you don't give more details it's very hard for me to reproduce or find a pattern. I need to know: version, selected install settings, any other custom settings, ....

The more info the better.
[X Style (Pure) Android Development] btafoya:
No wake on ring was common with version 10, even with no tweaks.

Wakes correctly with version 11 with stock settings (no tweaks at all!).

TruPureXMM 2.8.2 ROM.
[X Style (Pure) Android Development] dirtyhank:
Can you send me dmesg and logcat dumps right after a failed wake on call?
[X Style (Pure) Android Development] Optimusman:
That is odd because I've never had the issue using version 10 or 11. Just wonder if others have never had the issue as well. Using true pure 2.8.2 on the xt1575
[X Style (Pure) Android Development] ggs2:
Even for me, no wake on ring.

Stock settings

Test version1 , kernel .11
[X Style (Pure) Android Development] browcantor:
working perfectly in my xt1572 Brazil, aroma installer is great, no bugs, thank you friend
[X Style (Pure) Android Development] donrojo:
Anyone experiencing non responsive touch screen with latest 0.11 kernel? It's been 24hrs since flashed it with all stock options and 100hz version (which I've always used), and I've had three occasions coming from sleep mode and screen was not responsive for a few seconds. I mean I hit many icons, the clock and a couple of widgets but non responded. I had to push off button twice ti try successfully.
[X Style (Pure) Android Development] dribr:
I don't know if it is a ROM or kernel... Maybe the dev can clarify this to me... Is it possible to add HI RES audio output support for Moto X Style?

Enviado de meu XT1572 usando Tapatalk
[X Style (Pure) Android Development] browcantor:
lol resolution? https://plus.google.com/u/0/+carlosvinicius3607/posts/UYNN86gGnNm?pid=6278996617152688130&oid=108561095064429469826
[X Style (Pure) Android Development] HikingMoose:
My phone wakes fine ring as well. I'm on the first test version .11. I'm on stock 6.0, February update.
[X Style (Pure) Android Development] countryfolk07:
Occasionally I to get an unresponsive phone. It's pretty random. Tried to open the camera a couple times with the twist motion after picking the phone up off the table and everything was very sluggish. It took several attempts to get the phone responsive. It seems mostly, if not all the time, it's when it's locked/asleep. I had it VERY seldom, but did have it, on V.10. It's happened more on V.11. I'm running stock ROM. No Xposed. It's happened with no kernel mods as well as with script.
[X Style (Pure) Android Development] somecro:
Happened to me also,both things. I got touch screen issues twice and I had to lock/unlock my phone to resolve te issue. Slugginess only happened once but it was severe,like my phone was running CPU at 302 MHz.

Frankenclark v0.11 300Hz with rehpyc script.
[X Style (Pure) Android Development] elite001mm:
Well, I didn't want to say anything because I assumed I'd done something to my ROM to make it become unresponsive but it appears other people are having it too. I'll do my best to describe the issue and when it happens.

The issue: The phone will become unresponsive (usually upon wakeup). It will drop to something like 0.3fps for a short bit, then it will either totally lock up or it will eventually recover. If it does recover it can take a full minute or two. All touches seem to be registered and then they all come in at once when it recovers (for example if you are typing something and it freezes, you can keep typing, and then when it recovers, all the letters will be typed out really fast).

When it happens: It usually happens when I wake the device and then doing something CPU heavy or camera-related, and Snapchat makes it happen a lot (at the most inconvenient times, lol). The twist camera gesture while the screen is off has made it happen too.

I might add that my chop gesture for the flashlight is really laggy. Like 10 seconds. It works fine if the screen is on before doing it. Let me know if you need any info. I'd get a log but it's hard to get it to do it when you actually *want* it to.

Edit: kernel version is .11 test 1 with the script modified it 600mhz with ondemand for GPU.
[X Style (Pure) Android Development] dirtyhank:
The sluggishness upon wake some of you experienced is due to ZRAM. If you try to open an app that's swapped out, the kernel has to probably free RAM (by killing some apps and/or swapping out apps) and then decompress requested app. Normally this is a fast and smooth operation but when both swap and RAM are very crowded it takes longer, and more importantly, if this happens on wake there are probably a lot of activities that trigger on this event (especially if the device was asleep for a while and Doze kicked in) and all are trying to get CPU time. You can check that in such cases all cores are working like crazy.

There are basically two "solutions" to this problem, and none is perfect but a compromise:

Disable ZRAM altogether. In such a case you lose some multitasking abilities as apps will have to reload more often.

Reboot the device more often so ZRAM doesn't have a chance to get close to full. I've noticed I only get the sluggishness when I haven't rebooted for a few days.
[X Style (Pure) Android Development] dirtyhank:
Update on the 6.0.1 upgrade. I've been using it for a couple of days now and all is good, the downgraded modem seems to work fine and I haven't noticed anything weird. For those of you who might want to give it a try you have two alternatives:

Flash the 6.0.1 factory image but omit the modem part (wherever you see the modem string). This is what I did and I used the XT1572 factory image from Prazaar's. You have flashscripts there for full flash or just upgrade.

If you upgrade via OTA then you need to downgrade the modem. Basically get a 6.0.0 factory image (XT1575 or XT1572) and flash the modem with this command:

fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
[X Style (Pure) Android Development] tiis:
With the rehpyc.sh applied I have this extremly laggy lock screen and this über slow winter sleep wake up, too (15s until I can use home screen).

If I apply my favourite ButterFly profile for Interactive governor on top of rehpyc, wake up is fine again!

Also couldn't get ButterFly.sh to get applied by Frankenclark, I put it in the "scripts" folder and named it 02butterfly.sh but only 01rehpyc.sh gets applied..?

Moreover, the 600 MHz GPU causes the phone to get 45C hot, 450 MHZ runs "cooler" at 42C max and it seems to me the sweet spot between noticeable smoothness and temperature!

I'm on the XT1572 EU.
[X Style (Pure) Android Development] dirtyhank:
Can you send me this script to test?
[X Style (Pure) Android Development] somecro:
I just switched back to v0.11 100Hz without rehpyc.sh script to test things out,regarding the battery life and overall performance (including the slugginess and the touch screen issuses).

Also, in a few days I've been using v0.11 300Hz and rehpyc script I didn't notice any noticable battery gains. Still getting around 3 - 3.5h SOT but thats without using Amplify,Doze Settings Editor (or Greenify Aggressive doze) so the blame is basically on me. But I'm wondering, do you guys use Moto Display or WhatsApp? I tend to check wakelocks with WakeLock Detector and those two are getting a bunch of wakelocks (hundreds of them in a day).
[X Style (Pure) Android Development] dirtyhank:
Amplify is a must for me. I don't use very aggressive settings but I like being able to tame wild wakelocks :)

I'm working on an update to the installer that will let the user enable/disable more parameters (ZRAM for one) and include a couple of new popular scripts. Stay tuned ;)
[X Style (Pure) Android Development] countryfolk07:
I noticed also that I couldn't get some of those 5x scripts that I had been using to apply. I tried using ghost pepper to no avail. Also noticed that I couldn't change any parameters for the big cluster anymore.
[X Style (Pure) Android Development] HikingMoose:
How do you disable zRam? Just set swappiness to 0? I noticed the only complaint I have started after the zRam stuff.
[X Style (Pure) Android Development] dirtyhank:
That would reduce swapping but won't completely disable it. It's better to disable it at boot because once the ZRAM is in use it can take quite a long time to disable (vía swapoff /dev/block/zram0).

I suggest you wait until tomorrow, I'll be releasing the installer update and you'll be able to disable ZRAM at boot time ;)
[X Style (Pure) Android Development] HikingMoose:
If anyone wants to try some different settings, here's what I'm running:

I applied rehpyc's profile and made a few changes. It's been a week or so so I might forget some of my chances.

Small cores: conservative governor but change the down differential to 40 or 45. Change the up differential to 70. It will ramp up the cores very fast and make your phone smooth and responsive, yet ramps down quickly when not touching the screen or in use. It's given me better battery life and better performance than rehpyc's settings. But everyone's phone is different.

Touch boost I have n both sliders at about 40%, but I'm not sure if they even work.

GPU: I raised to 600 max and left it simple on demand. But I used to run cpufreq, and will probably switch back today for comparison.
[X Style (Pure) Android Development] revolagoy:
Does the rephyc script override the high frequency selected in the aroma installer?
[X Style (Pure) Android Development] HikingMoose:
I don't believe it does. I'm pretty sure I set my max from the installer and it stuck.
[X Style (Pure) Android Development] HikingMoose:
How long have you been in 6.0.1? How do you think it compares? I've read that at least a dozen or more people say it seems a little smoother and has better battery life. I tried the flashable zip a few weeks ago, but couldn't get signal. I didn't try flashing the 6.0 modem though.
[X Style (Pure) Android Development] ban.codrut:
With that res does Moto Display still misbehave ?

Inviato dal mio XT1575 utilizzando Tapatalk

---------- Post added at 12:54 AM ---------- Previous post was at 12:43 AM ----------

[MENTION=2400758]dirtyhank[/MENTION] Just for my curiosity, how did you managed to improve the camera focus ?

Inviato dal mio XT1575 utilizzando Tapatalk
[X Style (Pure) Android Development] revolagoy:
Thanks! I think you are right. I downloaded a EX Kernel app and it showed that the high frequencies were being used. Oddly, the same app showed the high frequency limit lower than the highest frequency used. Weird.
[X Style (Pure) Android Development] middleearth1010:
Why are we downgrading the modem? Wouldn't it be better to use the updated modem
[X Style (Pure) Android Development] newHere:):
Because the new modem doesn't play well with frankenclark kernel... (WIFI not working).

When the new kernel's source will be released i guess we will see new version of the kernel and we won't need to downgrade the modem
[X Style (Pure) Android Development] dirtyhank:
It's definitely smoother and I'd say battery life is a bit better too but it's too early to tell.
[X Style (Pure) Android Development] Artizle:
Can confirm kernel works fine on 6.0.1. I'm on Verizon and kept the 6.0 modems.
[X Style (Pure) Android Development] Psykitt:
Hello ban.codrut,

yes unfortunately Moto Display is the only downside when changing size and density.

Also with my values but all other things are fine.

Greetings Psykitt
[X Style (Pure) Android Development] dirtyhank:
I've just uploaded v0.11.1. Kernel images are exactly the same as v0.11, this is just an Aroma installer update.

I've tried to rearrange the start-up scripts screen and while I was at it included a bunch of new scripts. The most interesting stuff is probably the governor tuning scripts I've borrowed from [MENTION=4752299]Alcolawl[/MENTION] and [MENTION=5886947]soniCron[/MENTION] (see this post).

I've included the butterfly, ghostpepper and redhawk scripts, which in my opinion cover a pretty wide spectrum. Read the linked post above to find detailed description for each script.

I encourage you guys to test them all and let us know which one works best for you. To install a new script the easiest route is launching the installer again.

Have fun!

PS: Thanks to [MENTION=5391589]tiis[/MENTION] for the help with the scripts
[X Style (Pure) Android Development] countryfolk07:
[MENTION=2400758]dirtyhank[/MENTION] thank you for the update! I can finally run ghost pepper. I want to ask you this though. I'm running the modded kernel audiutor, why can't I change values on the big cores? I've tried using ex, regular kernel auditor, and the modded version to no avail. Any ideas, suggestions? Thank you for an excellent kernel and you your time.
[X Style (Pure) Android Development] dirtyhank:
Maybe because both cores are offline? Have you tried disabling hotplug while you try to change CPU settings?
[X Style (Pure) Android Development] countryfolk07:
I have NOT. I just changed governor to performance. That used to be the trick. I'll do that next time. Thank you. Also, eclipse is another great script by [MENTION=4752299]Alcolawl[/MENTION].

Edit: Disable hotplugging did the truck, thanks again!
[X Style (Pure) Android Development] elite001mm:
I just installed 11.1 and booted up. I wanted to let you know that on mine, all the thermal options were disabled by default (at least according to EX). I selected 300, ghostpepper.
[X Style (Pure) Android Development] dirtyhank:
Well, that's what the script does:

#Disable Core Control and Disable Thermal Throttling allowing for longer sustained performance
echo Disabling Aggressive CPU Thermal Throttling
echo 0 > /sys/module/msm_thermal/core_control/enabled
echo N > /sys/module/msm_thermal/parameters/enabled

Butterfly and Redhawk follow other approach:

#Disable Core Control and Disable Thermal Throttling allowing for longer sustained performance
echo Disabling Aggressive CPU Thermal Throttling
echo 0 > /sys/module/msm_thermal/core_control/enabled
echo Y > /sys/module/msm_thermal/parameters/enabled
[X Style (Pure) Android Development] HikingMoose:
I'm fairly new to Motorola and fastboot, but I"ve been getting by just fine for the last 6 months. I don't quite know how to flash 6.0.1 on my phone though. Do I type out a fastboot command for every line in that file? Is there a faster easier way? I'm asking this in public in case the answer can help others.
[X Style (Pure) Android Development] MrMeeseeks:
I have flashed both 6.0.1 versions. I recommend using the EU version because it doesn't have the dual sim stuff. But all you need to flash is the boot.img and all the system sparsechunks. I would then boot straight into TWRP and root with SuperSU then flash frankenclark. Then boot into the system.
[X Style (Pure) Android Development] lafester:
I just copy the commands I want into a text file and save as .bat file. Put that in a folder with your files and fastboot/adb files, then execute the .bat.
[X Style (Pure) Android Development] dirtyhank:
Download the factory image and flash script from Prazaar website. Unzip both to same directory and edit the Flash-all.bat file to remove all lines except these:

fastboot flash bootloader bootloader.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot erase cache

Then:

Boot into bootloader

Connect device to computer

Run the Flash-all.bat

Boot into recovery

Flash SuperSU

Flash Frankenclark

Reboot