yashsingh1/xdaforums huggingface dataset:
[X Play Original Android Development] yeeahnick:
That was me who said that. Be careful because I had done couple restarts before I first got the data loss. I would say data loss occured after 5-6 restarts. I am now back on twrp 3.0.2-r1 and squid 16b to avoid having the data loss again.
[X Play Original Android Development] Ebrahim Ali:
I just checked and I'm already on TWRP 3.0.2-r1 so I've just got to flash back to r16 kernel.

Thanks for the heads up
[X Play Original Android Development] dreinulldrei:
I am wondering if having been on 16d/e before means there's already damage to the data partition present, even if I haven't encountered any warnings so far. Also back to 16b.
[X Play Original Android Development] Ebrahim Ali:
Wondering this as well
[X Play Original Android Development] GtrCraft:
Look in TWRP log screen, if there are no errors you are good
[X Play Original Android Development] Ev0luti0n_:
YeahNick:my intensity does stick even after boot. I did a fresh install of the Rom
[X Play Original Android Development] yeeahnick:
With STOCK ROM?
[X Play Original Android Development] Ev0luti0n_:
No. CM 13 nightly 11/4. Everything seems ok so far. But who knows.. :)
[X Play Original Android Development] Ev0luti0n_:
Guys, is it normal for cpuZ to still display interactive as a governor with the 16d kernel?
[X Play Original Android Development] LuizHenrique91:
Unless you change the governor, it will always be interactive.

Enviado de meu XT1563 usando Tapatalk
[X Play Original Android Development] Ev0luti0n_:
But, how do we change the governor on the stock Rom. Kernel adiutor? Or the stock Rom has some stock option that I didn't see? I tried all menus...
[X Play Original Android Development] K.khiladi:
First of all you shouldn't be on 16d/e versions at all if you care for your data.

Secondly kernel adiutor can be used to change the governors.

Automated reply by JARVIS
[X Play Original Android Development] squid2:
Squid Kernel r16f

There have been reports of filesystem corruption involving the new Linux 4.6 f2fs version used in the r16d and r16e releases. This problematic f2fs version was also used in CyanogenMod 13 nightlies on April 9, 10, and 11. If you previously installed the r16d or r16e kernel, or previously installed the April 9, 10, or 11 nightlies, I would advise backing up valuable files to a non-f2fs storage volume before upgrading to this kernel version. There may be a risk of data loss when downgrading the f2fs, but it only affects some users.

This release brings back the older (Linux 4.5) f2fs. This is the same f2fs that was used from r15 to r16b. Please accept my sincerest apologies for any data loss that may have occurred. Greater caution will be exercised before any future f2fs updates are attempted in CyanogenMod or this kernel.
[X Play Original Android Development] GtrCraft:
No problem [MENTION=6485916]squid2[/MENTION], keep up the good work
[X Play Original Android Development] droider007:
Thanks for the update [MENTION=6485916]squid2[/MENTION] :)
[X Play Original Android Development] Chaotick:
Flashed april 13 with twrp r3 and squids kernel 16f. No issues. Thank you! [MENTION=6485916]squid2[/MENTION]

---------- Post added at 11:13 AM ---------- Previous post was at 10:20 AM ----------

[/COLOR [MENTION=6485916]squid2[/MENTION] => I have a question regarding the kernels - your in particular - and the battery option mode :"balanced" " power saving" "performace" etc. My question is - if i set the squid kernels governor to lionfish how will the battery options react? Will they change within the paramiters set by lionfish or will they be igonred? Another question is that there is another option in the battery settings - "set profiles for apps" or something like that. How does it effect the perviously mentioned settings and the kernel governor? Do you recommend to turn it off/on?
[X Play Original Android Development] Ev0luti0n_:
So far, everything looks and seems OK. I don't feel like re-installing or flashing everything again. What data loss is this?files on the internal memory? Pictures? SMS? App settings?

I am not going to do anything before this goes awal

---------- Post added at 10:30 AM ---------- Previous post was at 10:29 AM ----------

So far, everything looks and seems OK. I don't feel like re-installing or flashing everything again. What data loss is this?files on the internal memory? Pictures? SMS? App settings?

Is it guaranteed it I'll run into problems?

I am not going to do anything before this goes awal
[X Play Original Android Development] K.khiladi:
If you would have gone through some previous posts, you would know that the versions 16 d/e have problem and some users suffered data loss. So I was just making you aware.
[X Play Original Android Development] dreinulldrei:
[MENTION=6485916]squid2[/MENTION]: Would it be possible to elaborate a little how the f2fs thing went wrong and what might have happened? E.g. is it safe to assume that the /data partition is fine if a TWRP backup does not show any errors? I checked the logs, but the only thing I saw was a series of ongoing error for NtpServer (error code #22), which doesn't seem to be related to the file system at all.

If this was a problem of my SD card, I would just pop it into my PC and have it checked. But can't do this with internal memory, so...
[X Play Original Android Development] GtrCraft:
If twrp shows no errors after changing to twrp r3 or squid kernel 16f you are save
[X Play Original Android Development] squid2:
There are two things that the CM13 PowerHAL does when you change performance mode. One is to change governor tuning for interactive, and the other is to put ClusterPlug in and out of low power mode. The only difference between balanced mode and performance mode is governor tuning, so there is no difference between those two mode if you are using a non-interactive governor. Battery saving mode switches ClusterPlug into low power mode, which only uses the little cluster.

One thing to be aware of is that governors other than interactive lose their settings whenever a cluster is hotplugged, so if you configure lionfish right now on this device, the settings will be lost as soon as the screen turns off. Also, this behaviour causes sysfs permissions for the big cluster to be lost when the screen goes off, making switching to performance mode in the PowerHAL not work. Obviously, this behaviour is suboptimal, and I will be looking to improve it over the course of the next few weeks.
[X Play Original Android Development] squid2:
As [MENTION=5293805]GtrCraft[/MENTION] said, if the storage mounts in TWRP without any reported errors, and your ROM appears to work fine, then your filesystem is probably OK. My device actually never got corrupted despite, numerous repeated filesystem upgrades and downgrades that my device underwent, so it's evidently something that depends on a multitude of factors.

I must admit that I don't know exactly what went wrong. However, the general nature of the issue is that the f2fs filesystem is under very active development, and the on disk data structures it uses to store filesystem structure often change slightly. If you've ever done C programming, you can think of these as C structs sitting on a disk. When you want to add features and fix bugs, you sometimes need to add things to these structs or rearrange elements. The filesystem and fsck are supposed to handle this migration from older formats to newer formats, and usually they try to make newer formats backwards compatible with older formats, but this doesn't always go according to plan. Somewhere in this process, certain combinations of fsck and f2fs in the kernel and god knows what else don't get along, and some parts of this migration are not carried out correctly. This manifests itself as filesystem corruption and data loss.
[X Play Original Android Development] dreinulldrei:
Thanks squid2! That sheds some light.
[X Play Original Android Development] diazepambr:
What is the best governor for battery/performance? Interactive or Lionfish?

Thanks.
[X Play Original Android Development] Ev0luti0n_:
Somebody said interactive was not good at all, because every small thing would cause a spike on cpu usage. Although, somebody more knowledgeable than I should reply.
[X Play Original Android Development] XxMikeMasterxX:
Check out the Power Users thread here regarding different setups!

http://xdaforums.com/moto-x-play/general/power-users-post-optimal-setup-t3313348
[X Play Original Android Development] baskwo:
With Pijes settings, I have great performance and battery life :

I set the same except min and max frequency. I have big cluster min at 400 and max at 17XX
[X Play Original Android Development] xQrzy:
It seems I've got lost on last several pages of this thread and last state of the LED support on stock 6.0.1 that I remember is "not working".

Was there any change in this matter recently?
[X Play Original Android Development] Ev0luti0n_:
Mine works fine
[X Play Original Android Development] Benjamin_L:
But only because you downgraded the sensorhub firmware. Otherwise it wont

---------- Post added at 10:51 AM ---------- Previous post was at 10:43 AM ----------

Look here http://xdaforums.com/showthread.php?p=65959404
[X Play Original Android Development] xQrzy:
Excellent, that is what I was looking for. :)

Thank you very much.
[X Play Original Android Development] cute_prince:
[MENTION=6485916]squid2[/MENTION]

Dont know if this is a CPU-Z bug but idle GPU frequency is shown as just 19Mhz when using squid kernel while it is shown as 400Mhz when using CM inbuilt kernel.
[X Play Original Android Development] squid2:
It's not a bug. It's just that my kernel reports the actual frequency when the GPU is idle, because if this commit: https://github.com/sultanqasim/andr...mmit/fe2156b20079d9a63096700e7f99b15cd386a566
[X Play Original Android Development] Louis235:
One question: the loss of Settings, using another Governer than Interactive: can I prevent that using another app (not Kernel Adiutor) or is that a Kernel thing?

Thanks for all your hard work?

Greets
[X Play Original Android Development] zero995:
[MENTION=5067223]Louis235[/MENTION]

you need apply the changes while charging
[X Play Original Android Development] dreinulldrei:
[MENTION=6485916]squid2[/MENTION]: were there any changes to Bluetooth for the latest rev. of the Kernel? My Pebble keeps unpairing since two or three days and I am wondering if any change introduced might lead to this... It happens when the phone has been idle for a while. The all of a sudden my Pebble is unpaired and needs to be re-paired.
[X Play Original Android Development] ViperX85:
Hey all, I hope you guys won't mind me asking this here.

I'm running stock 6.0.1 ROM with latest squid kernel and I'm having problem with hispeed_freq settings on interactive governor, when I choose a desired frequency it won't stick to that, it always reverts to 1459200MHz. I followed a guide for interactive governor from http://xdaforums.com/nexu...0#post64279960 and the results are great except when hispeed_freq starts to screw itself up, the big CPU is then always stuck on 1459200MHz frequency which destroys the purpose of the guide. It happens also on stock based custom roms and that probably means it is ROM related. The same happens on stock and ultra kernels, the weird part is that it somehow worked normally on stock 6.0 and squid kernel even though not from the day one. Any ideas how to make hispeed_freq to stick to 533333MHz?

http://imgur.com/SS1ZWaf
[X Play Original Android Development] diazepambr:
[MENTION=6485916]squid2[/MENTION], what do u think about implement the Intelliactive governor?
[X Play Original Android Development] K.khiladi:
Does it change after a reboot or just when using the phone?

Automated reply by JARVIS
[X Play Original Android Development] kskkumar:
Ya for me too the same problem. I am using mi band to unlock. But it gets unpaird after some time and I have to start mifit app again to pair. I thought it is problem with mi fit new app. The video recording is not saving the file. No idea why. This is with cm's 15th nightly build with squid kernal. Not sure where the problem is. But cm revoked that build. So, not sure. The camera problem could be cm's. But Bluetooth yes. I think it is from the kernal.
[X Play Original Android Development] brom25:
in my case, the xiaomi miband was always a trouble to connect since MM in my case. full stock , also with other smartphones!
[X Play Original Android Development] ViperX85:
No, it happens when I use the phone, as soon as the CPU load gets higher than 533333MHz I think.
[X Play Original Android Development] Sickaxis79:
I recognize this this problem tweaking interactive governor. You must create a profile in kernel adiutor.After this go to the settings page in kernel adiutor and push "test" and before the script applies exit kernel adiutor completely and wait for the script to apply. After this restart your phone and settings will stick. Also try not to use the highest target load for the 1459200Mhz which is 88. Try to give the 1459Mhz a target value not higher then the next higher cpu speed target load values.The 1459Mhz range has the highest max target load of all cpu speeds from the big cores (88) and i think this is the reason why it always try to trigger this cpu speed and changes it back.

I had the same problem for days, but this resolved it.

Edit:

After the script applied don't launch kernel adiutor again before you have rebooted your phone.
[X Play Original Android Development] ViperX85:
Great, it works, thank you!
[X Play Original Android Development] till69:
Kernel r16f: Internet is slow (i.e. Playstore Pictures wont load, download wont start immediately) if Moto has global IPv6 address
[X Play Original Android Development] dreinulldrei:
I think it's safe to say that this is _not_ a kernel fault. I switched from 16f to 16b and back again. The problem also came back with 16b, and 16f. Since 16b worked for quite some time, my understanding is that maybe 16d/e damaged something in the file system leading to the system forgetting Bluetooth devices and connections.

I re-installed a nandroid backup from early April, installed kerne 16f and so far it's working.

I would suggest that we keep an eye on such reports. Might be that 16d/e do more damage than is visible on first sight.
[X Play Original Android Development] celoxocis:
can your squid2 kernel be ported (compiled) to other msm8939 based devices?
[X Play Original Android Development] eliday15:
Hi why moto gone down its for kernel

Enviado desde mi XT1563 mediante Tapatalk
[X Play Original Android Development] mingo_uk:
Latest kernel has my MXP stuck at the Cyanogen boot screen... Anyone has this?
[X Play Original Android Development] Benjamin_L:
What?
[X Play Original Android Development] hanakon:
This might be a little late now, but I was having issues trying to get adjusted vibration intensity to stick when setting on boot, it would keep resetting to 100% anyways; noticed some other people reported the same issue and I didn't see a solution. In my case, it was just that RR had a vibration intensity slider in the system settings under sound settings, the intensity percentages have to match both in the system settings and Kernel Adiutor or else Adiutor just goes with whatever the system settings value is. Most likely that was just me being dumb, but just in case anyone else is making the same mistake, check your sound settings. :)
[X Play Original Android Development] yeeahnick:
From my understanding vibration intensity should stick after reboot on all CM13 based roms. The problem is with stock rom since stock rom doesnt have its own vibration setting =(
[X Play Original Android Development] Aman Kathed:
A bit of problems.

I am using the latest 16 squid kernel but i'm facing a bit of problems. Firstly sometimes it unexpectedly reboots which is very unfortunate. Secondly MOTO VOICEds'nt works. And at last no response from notification LED. Please help. :confused:
[X Play Original Android Development] K.khiladi:
Regarding reboot, something else might be interfering.

Don't know about moto voice.

For LED, you will have to downgrade your sensor firmware.
[X Play Original Android Development] Benjamin_L:
For stock 6.0.1 roms you need to do this to get LED working: http://xdaforums.com/showthread.php?p=65959404

As for the reboots. Do you have big and little cores on the same governor?
[X Play Original Android Development] Aman Kathed:
It didn't work. No notification to uninstall anything after reboot. :crying:

Also the 2nd file in the link is not downloading. Please help once more.
[X Play Original Android Development] Benjamin_L:
You sure you downloaded the right files? View, Raw, Download? Right click on raw and save link as also works
[X Play Original Android Development] Aman Kathed:
Sorry

Tried everything. Downloaded from chrome,mega but nothing worked.:( :crying:
[X Play Original Android Development] Aman Kathed:
I executed these steps on Stock MM 6.0.1 but nothing happens after reboot.:( :( Tried a lot of times. Please help.
[X Play Original Android Development] Benjamin_L:
Please verify each step again as it worked for everyone else so far
[X Play Original Android Development] XxMikeMasterxX:
Exactly man. You gotta read through the entirety of the thread pages thst concern your issue. Someone offered a solution of downloading on PC then transferring to phone.

Please don't sound so helpless - just take your time and do your due diligence.
[X Play Original Android Development] The Analog Kid:
Yep, you're right. I've been reading this whole thread for about a week now (I do this every time I want to mess with my devices) and I'm currently on page 123 of about 130+... and I must say that I'm still hesitant to flash any version of squid's kernel. Somehow, threads (most of them) tend to get confusing at some point, because of people's lack of reading will; but still you can manage to find the truly reliable stuff, when you have patience and read carefully. That's why, according to my reading, going with 14b seems to be the best bet here. Perhaps 14b should be the way to go for a relatively simple, 'non highly tweaked' kernel. Personally, an ultra long lasting battery performance is not what I'm looking for; not even super smooth software behavior; instead, I would be happy enough with some extra (vibration control) and hidden features (notification led) brought to life. Usually, "one thing leads to another" and too much development usually leads to a never finished product because of this, and considering the interest lifespan of Android OS versions (indeed, Android N seems to be already lurking around), we never get to experience fully finished, reliable custom kernels or ROMS, because devs tend to happily move their efforts to the new software as soon as it officially lands. Just saying. You caught my attention. I still have some stuff to read over here...
[X Play Original Android Development] kos25k:
I also cant download the second file and didnt understand this about save etc..but I think I will manage it.so...can anyone tell is with sure if LED notif. work for him with this way?

Στάλθηκε από το XT1562 μου χρησιμοποιώντας Tapatalk
[X Play Original Android Development] Benjamin_L:
Open and save this page, will give you a textfile with exactly one line: https://github.com/TheMuppets/propr...mon/proprietary/etc/firmware/sensorhubver.txt

You could as well just create a sensorhubver.txt file and put in the line yourself
[X Play Original Android Development] kos25k:
ok I finally managed it!!!now can somehow with an app set it to blink more quick???

Στάλθηκε από το XT1562 μου χρησιμοποιώντας Tapatalk
[X Play Original Android Development] MaxlMuller:
I use an app called Light Manager, you can find it at Play Store. It allows you to control the LED flash rate individually for each app. For example, my whatsapp notifications are set to keep the LED always on.
[X Play Original Android Development] kos25k:
I found something simillar but no one of these apps can set the brightness of led...

At least with light manager I can set the frequency of led for lost calls.Thanks dude!

Στάλθηκε από το SGP611 μου χρησιμοποιώντας Tapatalk
[X Play Original Android Development] Benjamin_L:
Brightness cant be changed for now it seems, maybe [MENTION=6485916]squid2[/MENTION] could add something like pwm for that?
[X Play Original Android Development] dreinulldrei:
Really? This is something the hardware should do, but not something you want to do in software. This would mean constantly pushing data somewhere just to dim a LED. Plus the overhead for the thread that does it.
[X Play Original Android Development] drmuruga:
Please add DT2W to your kernel.
[X Play Original Android Development] kos25k:
dudes I have marshmalux v2 with this kernel.I don't know if this is kernel related,but why when my phone rings..At first 2 seconds volume is max and then immediatelly it lowers about 70%?

Στάλθηκε από το SGP611 μου χρησιμοποιώντας Tapatalk
[X Play Original Android Development] dzesiu2002:
Hi. Try that http://xdaforums.com/moto-x-play/development/mod-disable-ascending-ringtone-t3216998
[X Play Original Android Development] kos25k:
thanks dude I also flashed this!the problem occurs ONLY when my phone automatically connects with my bluetooth headset!so I must now find an app that fixes this!

Στάλθηκε από το SGP611 μου χρησιμοποιώντας Tapatalk
[X Play Original Android Development] manub2:
Led not working

Hi, I did exactly all the required steps: new kernel, root, download the two files, reboot, removed old sensor firmware, and so on.

But after the reboots no led is working.

What can I check?

I'm on MM 6.0.1 with r16f kernel.

Thanks.
[X Play Original Android Development] floid180:
i flashed 16f and got a lot of FC from Moto voice! :( any idea?
[X Play Original Android Development] manub2:
I also have another issue, Alphalt 8 is not working anymore. It crash on start.

---------- Post added at 12:07 PM ---------- Previous post was at 12:04 PM ----------

Don't ask me why, but it started working after a new installation of the kernel.

Still having problem with Asphalt 8.

Thank you.
[X Play Original Android Development] maninder singh bali:
i too have the same problem with asphalt 8

Edited: hyeeee I reinstalled the rom and the asphalt 8 runs gud.. try it..
[X Play Original Android Development] Benjamin_L:
Sometimes it happens that big frequencies are 0 for min and max and currently i have cpu3 stopped and cannot turn it back on. Don't know if this is a cm bug or a kernel bug. I don't know how to reproduce this yet
[X Play Original Android Development] dreinulldrei:
I've seen this happen when the CPU gets hot that the thermal throttling shuts down cores. If you let it cool, cores should come back.
[X Play Original Android Development] Benjamin_L:
I guess at least for core 3 this happened but the reset to 0 is strange still
[X Play Original Android Development] dreinulldrei:
To clarify... It does not come back to whatever MHz oder GHz once the core has been turned back on?
[X Play Original Android Development] Benjamin_L:
Kernel adiutor shows 0 for min and max, everything is laggy until i put in the old frequencies
[X Play Original Android Development] manub2:
Hi, what do you mean with "I reinstalled the rom"?