yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Android Development] XDleader555:
Wakelocks keep the phone awake to do certain tasks. Sometimes these Wakelocks are unneeded or accidentally keep the phone awake when it's doing nothing. By turning the Wakelock toggle off, we don't allow the phone to stay awake per the toggle. This can help fix certain conditions where your phone won't enter deep sleep because of a Wakelock.
[X Style (Pure) Android Development] XDleader555:
05/31/17 - 12:50AM - v2.0

Merge F2FS changes up to May 20th 2016

Small updates to msm mdss

Switched to bricked_hotplug as default

This should really be 1.9.1, but I already made it 2.0. Too lazy to fix Â¯\_(ãƒ„)_/Â¯

Tested F2FS functionality by formatting my cache partition in TWRP as F2FS. Works fine afaik.

Apparently my data partition was already F2FS

/dev/block/mmcblk0p47 on /system type ext4 (ro,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p48 on /data type [B]f2fs[/B] (rw,lazytime,seclabel,nosuid,nodev,noatime,nodiratime,background_gc=on,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,extent_cache,data_flush,mode=adaptive,active_logs=6)
/dev/block/mmcblk0p46 on /cache type [B]f2fs[/B] (rw,lazytime,seclabel,nosuid,nodev,noatime,nodiratime,background_gc=on,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,extent_cache,data_flush,mode=adaptive,active_logs=6)

Downloads somewhere here: https://xdaforums.com/devdb/project/?id=20678#downloads
[X Style (Pure) Android Development] dzidexx:
[MENTION=3623188]XDleader555[/MENTION]

Hi, I don't know what is wrong, what I do wrong.

I had wheatley+bricked(1% battery by night), today morning I set zzmove+bricked - it doesn't turn off cores - still six online, set relax+bricked - freeze, force reboot and after it I saw interactive+lazy. I went back to 1st settings.

KernelAdiutorProfile.json & screenshots:

https://drive.google.com/file/d/0B9k8W8e2YrFfaHZxRm9FckdiX3M/view?usp=drivesdk

Can't upload here.
[X Style (Pure) Android Development] XDleader555:
Hey would you look at that, I'm getting that glitch too. Looks like I merged something bad in the previous build. I'll look into it.
[X Style (Pure) Android Development] dzidexx:
I'm not sure but I think that 1.7.1 & 17.05 versions work the best so far.

Compare with it. [MENTION=3623188]XDleader555[/MENTION]
[X Style (Pure) Android Development] XDleader555:
I uploaded a build (20170531-0050) which has bricked_hotplug as default. You might have to wait a little for your phone to settle for the cpu cores to unplug.

If they're still not unplugging, up the idle_freq for bricked from 384000 to 460000.
[X Style (Pure) Android Development] creeperlwd:
It might have something to do with zzmoove having its own hotplug
[X Style (Pure) Android Development] dzidexx:
I've just flashed. Will check.
[X Style (Pure) Android Development] lknnnn:
It seems that my data partition has been f2fs since I bought it.Does the newest change mean that I can change the format of system and cache from ext4 to f2fs（But I will not do this）？
[X Style (Pure) Android Development] XDleader555:
I believe zzmoove bLE (big LITTLE Edition) doesn't include the hotplug part. If you set hotplug to disabled, zzmoove by itself won't unplug cores.
[X Style (Pure) Android Development] XDleader555:
Newest change is just updated code. You could always do that. Changing system isn't recommended because it's read only anyways.
[X Style (Pure) Android Development] creeperlwd:
It seems that the bLE also does not have profiles.
[X Style (Pure) Android Development] tdg2k15:
[MENTION=3623188]XDleader555[/MENTION] - it seems or phone by default has /data partition set too F2FS, and on top of that I didnt know are recovery supported it... So now I'm rocking /data and /cache on f2fs.. Thsnks again.!
[X Style (Pure) Android Development] dzidexx:
They are unplugging but I can't change idle freq. Always back to 768(hotplug settings).
[X Style (Pure) Android Development] XDleader555:
Seems like a bug with kernel aduitor. Try a different kernel manager and see if the issue persists.
[X Style (Pure) Android Development] dzidexx:
I think I found guilty - it was too much operations and I lost busybox. Kernel adiutor didn't scream for BB.

Very sorry for panic.
[X Style (Pure) Android Development] rayparlour:
Idk if anyone else is having this problem but my Big cpus get turned off and then never comeback on even after a reboot. Even happens with hotplugging disabled and several different governors.
[X Style (Pure) Android Development] lucianogm:
YES

FINALLY F*****G YES

A custom kernel for clark, FINALLY!

Thank you so much!
[X Style (Pure) Android Development] Gulfstream 650:
I'm not seeing that problem, which hotplug driver are you using?
[X Style (Pure) Android Development] dzidexx:
It looks like msm hotplug is default for you.

Did you try performance governor?

Set f.e. wheatley or zzmove governor and lazy or bricked hotplug.

Look into Kernel Manager cpu statistics - it should be some seconds for 1824MHz.
[X Style (Pure) Android Development] Sagar_1401:
I have never flashed a custom kernal..

Just a noob question

Can i dirty flash the kernal over updated kernal?
[X Style (Pure) Android Development] creeperlwd:
If the kernel you have installed is lineageos based it will work
[X Style (Pure) Android Development] dzidexx:
Before flashing custom kernel always do full backup in twrp.

I'm sure that you can update kernel(dirty flash, f.e. ver.2.0 at 1.8).

I'm not sure that you can downgrade this way(1.8 at 2.0). Restore boot+system and than flash 1.8.
[X Style (Pure) Android Development] XDleader555:
You can dirty flash my kernel over an older version of itself. You can also dirty flash an older over a newer for now since I haven't added any init.d scripts.
[X Style (Pure) Android Development] tdg2k15:
You should keep system untouched by kernel, less of a head ache .. If anything add add scripts to ramdisk , like your own "init.handbang.rc", that applies your modifications within the kernel ... Hope you understand what I mean.
[X Style (Pure) Android Development] XDleader555:
Yeap, that's how anykernel2 works. You'll notice an empty handbag rc scipt in the root directory, which is your ramdisk.
[X Style (Pure) Android Development] mix_man:
Excellent kernel, thank you very much. This phone desperately needed a custom kernel with so many options to chose from.

I run Dirty Unicorns 10.6 and the most stable Handbag kernel version with the most battery life for me is v.1.5 (zzmoove for all cores + bricked hotplug + maple i/o), right before adding Lazyplug. Newer versions started to keep the CPU alive all the time even after turning the screen off, keep the phone hot (regardless of the chosen CPU Hotplug), kernel settings would get scrambled after manually setting them (like the CPU governor, CPU Hotplug) or after reboot. Probably all the reverts and unreverts added to the confusion.

Lazyplug helped the phone achieve higher benchmark scores, but the battery life outweighs the increased performance especially since the phone feels just as smooth without it.
[X Style (Pure) Android Development] jesful2011:
I always thought this kernel was just for 7.1.2. I wasn't aware this would work on 6.0.1
[X Style (Pure) Android Development] ismithx:
it does??????
[X Style (Pure) Android Development] Mahmoud Jamal:
Didn't anyone notice that with this kernel the big cluster is offline all the time and the cpu governer for it can't be changed ??

---------- Post added at 02:09 AM ---------- Previous post was at 02:06 AM ----------

I need help.

I flashed this kernel v1.5 and then v2.0 on RR 5.8.3 Rom.

Then I tried restoring the RR kernel using TWRP image that I made prior flashing the kernel.

Now the device keeps restarting after 10 or 20 seconds after boot.

What should I do. I tried dirty flashing the Rom again but that didn't solve the issue
[X Style (Pure) Android Development] tech_infinity:
Had a similar issue. You'll have to flash stock rom and then twrp again
[X Style (Pure) Android Development] dzidexx:
You have to do "format data" in twrp after it do "clean install".

This is a bug of HKernel(2.0 only i think).
[X Style (Pure) Android Development] mix_man:
I noticed that behavior too. With Bricked CPU Hotplug, the Big Cluster only goes online if the Little Cluster is working hard and a significant amount of workload is requested by the system or apps. I think this helps a great deal with battery life and this is exactly why I love this Hotplug. To force the Big Cluster go online you can try 1 of 2 things:

- the easiest is to temporarily switch the CPU Hotplug to msm or Lazyplug which will bring the big CPUs online quicker

- or trigger the update of some apps using Play Store and / or change Little CPU to Powersave or other battery saving oriented Governor.

While at least 1 Big core is online, change Big CPU governor and in the end change the Little CPU Governor as desired then go back to whatever Hotplug you want.

It runs just fine and the difference is felt immediately by running this kernel.
[X Style (Pure) Android Development] hellboyborn:
Bro can you link me to 1.5 version? I would like to try this combo.
[X Style (Pure) Android Development] chaostrodamis:
Just restore a previous backup before the flashing of the kernel. Other wise do a clean install of your ROM. (Wipe data *not internal*, system, dalvik and cache.) Should get you going again. Hope you made a backup or at least some titanium backups.
[X Style (Pure) Android Development] xgerryx:
Yea, this is a mess right now. The download links for the versions that cause this perma-reboot thing should be removed. I'm still losing root everytime I flash this too, but beside the point, now I cant even restore the kernel that came with the ROM without clean flashing? That's about as bad as it gets for normal problems with modding phones. Needs to be addressed. I would advise people to not flash this until more testing is done.; I flashed the second kernel posted on 05/31 when this happened.

Edit: I can't even wipe data from recovery without a reboot. What is going on???
[X Style (Pure) Android Development] mix_man:
It's in the Downloads tab, the version from 05/22/17 - v1.5 "HandBag-20170522-0237.zip"
[X Style (Pure) Android Development] Ijspegel:
I had the same problem. You need to do first in twrp format data, then factory reset, then wipe everything and clean install a new Rom without this kernel. My phone booted again, then i installeren version 1.9 again. 2.0 is not good, IT is unstable.
[X Style (Pure) Android Development] xgerryx:
Yea, without being able to wipe anything in TWRP (it kept freezing and rebooting to the logo), I had to go through the entire ADB process and restore to stock. I'm still in the middle of that.

NO ONE SHOULD FLASH THIS UNTIL THESE ISSUES ARE WORKED OUT. This is HOURS of work to get back to a working phone. Save your self the trouble for now.
[X Style (Pure) Android Development] lilcdroid:
I had the same problem as everyone else a couple days ago. What I had to do was change my file system from f2fs to ext4 for the data partition and was able to wipe that without issue. Then did a factory reset and was able to install fresh ROM from my SD card. It just sucks that you lose all your internal storage but luckily I had just done a complete internal storage backup the day before and saved it on my computer.
[X Style (Pure) Android Development] Ijspegel:
After format data You can wipe, first thing to do is format data.
[X Style (Pure) Android Development] chaostrodamis:
I'm not having these issues you guys are having. Been using version 2 with no issues at all.
[X Style (Pure) Android Development] JoshuaUB78:
Are you getting deep sleep? I reverted back to D.U. (11.4 (I think)) kernel and set Power Suspend Mode to Userspace.

---------- Post added at 03:11 PM ---------- Previous post was at 03:09 PM ----------

What CPU, Hotplug & IO settings are you running?
[X Style (Pure) Android Development] angrymexican76:
This is my big core with version 2.0 of the kernel as well as the little core ....running resurrection remix and no problems yet
[X Style (Pure) Android Development] LJM9000:
I just had the boot loop issue with 1.5. But I was able to resolve it by rebooting into recovery reflashing the kernel then wiping cache and dalvik cache. Then the phone booted up fine. Try that with the 2.0 version and see if that works for you
[X Style (Pure) Android Development] Gulfstream 650:
I didn't think I was having issues until I went to flash the newest LOS update, oh jeeze what a mess. Same as everyone else, can wipe, can't install, etc. I had to change my data partition file system to ext4 and then wipe to be able to flash anything.

**Edit** Was finally able to restore a backup I had from about a week ago so not a total loss.
[X Style (Pure) Android Development] Mahmoud Jamal:
Yeah I figured that out after sometime playing around in TWRP. I lost some data I didn't have backed up though​ bummer.

I ended up going with a completely different Rom AICP and I'm liking what I'm getting so far.

---------- Post added at 02:19 AM ---------- Previous post was at 02:17 AM ----------

Didn't backup everything unfortunately. I formated data and installed another Rom
[X Style (Pure) Android Development] chaostrodamis:
Damn that sucks, sorry for your lose. (Lol, sound like someone died lol)
[X Style (Pure) Android Development] dzidexx:
You are not alone.

Anyone who didn't yet:

In twrp you can connect to pc and copy some data to hard drive or in twrp's file manager copy it to sd card.

Ps.

Had anyone such problems with

twrp 3.0.2

& HKernel 2.0?
[X Style (Pure) Android Development] fliperpl:
should i use this kernel when i am on lineageos 14.1 7.1.2?
[X Style (Pure) Android Development] Curlyfry2121:
Yup
[X Style (Pure) Android Development] fliperpl:
im having error while instaling this kernel

invalid partition

"error executing updater binary in zip '/external_sd_handbag-20170531-0050.zip'

eror flashing handbag kernel..
[X Style (Pure) Android Development] hellboyborn:
Amazing kernel, working fine with Marshmallow as well. Using it with SLIM ROM (M Edition) no problem so far. Thanks XDleader555 for this awesome stuff and special thanks again for including KCAL :).
[X Style (Pure) Android Development] fliperpl:
okey i fixed my problem

using version kernel version from 26.05 and twrp version 3.0.2
[X Style (Pure) Android Development] mddunner:
I attempted a downgrade to 1.5 from 2.0 after seeing these reports as well as to try and get Deep Sleep back. This resulted in the boot loop issue. Restoring CR Droid kernel, dirty flash, cache Dalvik wipes, had no affect.

Following your suggestion, I re-flashed 2.0, wiped cache and dalvik cache, and have achieved a stable device.

I guess I should leave the ROM and Kernel as is until the kernel is checked for bugs around this matter. Thanks for everyone's input and reports.
[X Style (Pure) Android Development] XDleader555:
Looks like there's a little trouble with the kernel. I'll start by removing downloads with versions up to 1.7.

I'll start rebuilding the kernel with only things we need and stay as close to the lineage tree as possible.

I wont be able to work on this for another week due to school and work.

Sorry for the inconvenience this has caused.
[X Style (Pure) Android Development] mddunner:
Sometimes it hurts to be on the cutting edge. Thank you for your work and continued support!

Any thoughts on why a kernel downgrade from 2.0 to 1.5 failed resulting in the boot loop? Would downgrading to 1.7 be a better option?
[X Style (Pure) Android Development] XDleader555:
I have no Idea what could cause a downgrade issue. Perhaps it's the f2fs updates I added in 2.0. I wouldn't be able to tell without a ramoops log.
[X Style (Pure) Android Development] mddunner:
Fair enough, thanks. I'm not experiencing any substantial battery life issues with 2.0, so I will hang tight here. Thanks again!
[X Style (Pure) Android Development] GchildT:
My Handbag 2.0 configuration has been working great for me!

Ex Kernel Manager

Little - ElementalX

Big -Interactive

msm_thermal and core - disabled

no overclock

hotplugging- disabled

ROM - AICP latest
[X Style (Pure) Android Development] mddunner:
I'm still very new to android kernels and all the aspects of it. I'm curious about your hotplugging being disabled. It seems like that would decrease battery life. Do you disable for performance reasons, or do you actually achieve better results overall with it disabled?
[X Style (Pure) Android Development] dzidexx:
Can you add more info?

TWRP ver.?

Root with Magisk, Supersu? Works good?

Any operations with TWRP after HKernel?
[X Style (Pure) Android Development] GchildT:
It is better for performance when using my device. CPUs always on but at min clock until load dictates. There is no dramatic decrease in battery life for me. It's like a balanced battery mode. Plenty of performance, not optimal battery - but manageable battery life (not trying to set any records).

---------- Post added at 02:43 PM ---------- Previous post was at 02:39 PM ----------

TWRP 3.1.0-0

AICP with Magisk Root. Multiple modules installed.

I've installed zips, performed backups, used the file manager and updated my rom with TWRP.

Of course, after a ROM update I have to resinstall the Kernel, but then back to normal. If not, have to wipe Dalvik and Cache.
[X Style (Pure) Android Development] GchildT:
screenshot
[X Style (Pure) Android Development] dbolivar:
Just want to say thanks for your hard work in bringing a great kernel for our devices. We are all enthusiasts, and as such like to try cutting-edge stuff; bugs are expected, and we should all help with QA testing. :) This is a great thread btw, most people helping each other and enjoying the party.

Regarding v1.7.1, I see it has the Lazy Hotplug. Is it expected to be fully functional, turning cores off and allowing deep sleep? Really would like to try this hotplug driver.
[X Style (Pure) Android Development] GchildT:
I would also like to thank you for all your hard work. I'm too busy and lazy to try this myself. Glad you're​ still showing love for Moto X Pure (Clark).
[X Style (Pure) Android Development] branran:
How stable are you right now compared to the other versions of the kernel?
[X Style (Pure) Android Development] mddunner:
I'm fully stable, and really I always was on 2.0. I did notice that I wasn't seeing as much deep sleep in version 2.0 which is why I was considering the downgrade. I'm mostly into this for battery life and tweaks.

That being said, I'm seeing really good results after I recovered my phone by re-flashing 2.0 and clearing the caches. Phone has been up 22 hours since full charge and I'm at 75% battery life. Kernel Adiutor reports 97% deep sleep for Big, 71% deep sleep for little. zzmove governor for both big/little, touch boost disabled, Bricked hotplug.
[X Style (Pure) Android Development] branran:
I'm using the kernel for the same reason as you.

I was on 2.0, saw the post, downgraded to 1.5 no problems, tried upgrading to 1.7 since thats what the dev has downloads up till, and bootlooped. Upgraded to 2.0 using your method, it worked. But now if I were to try and clear my cache and dalvik my phone freezes in TWRP and reboots.... The phone works after flashing 2.0 again though, so I'm scared to upgrade anything now ...
[X Style (Pure) Android Development] videogmike:
I also am on 2.0 and have been fairly stable. I'm using Lionheart on both big and little with bricked hotplug.

I'm using AICP and they do nighties so when i update I have been flashing 2.0 kernel on top. After hearing about problems I tried updating AICP this morning and skipping the kernel. That resulted in bootloop. Got back into TWRP and flashed 2.0 all is good again.

I too am a little scared now I am the same as branran TWRP crahses and reboots when wiping dalvik cache. It obviously worked because it sits for 10 minutes booting but not sure why this is happening or how to fix.

Oh and I'm on newest TWRP 3.1.1.0
[X Style (Pure) Android Development] mddunner:
Forgot to mention I'm on TWRP 3.0.2.0 and still using CR Droid 3.2.
[X Style (Pure) Android Development] Sherrillface:
Yea bootlooped me and funked twrp now can only get into bootloader.
[X Style (Pure) Android Development] dzidexx:
[MENTION=4171001]Sherrillface[/MENTION] & others

If anyone still uses Handbag Kernel ≥1.8 and has any problems with install something another.

Into twrp 3.1.1(install or boot with fastboot) you should format data(yes) and advanced wipe - all partitions. Reboot twrp, repeat the same steps and I hope you will flash what you want.

To not lose the data you should first:

Working system: backup apks+data with Titanium Backup, copy all you want to PC or sd card

(Titanium Backup folder, photos etc.).

Not working: install or "fastboot boot twrp3.1.1.img", do backup of data(to sd card), connect to pc(mtp) and copy all you want from internal storage to PC or sd card. Titanium backup will restore something(not all) from your twrp backup(you cannot restore​ this with twrp).

If this won't help - you have to flash the newest stock rom(without bootloader & gpt). After it install ota update.
[X Style (Pure) Android Development] videogmike:
This sounds like a lot of work. What has happened to the phone that it needs all this? Why would you have to wipe all partitions?

Edit: 2 more questions

1 can i keep updating AICP and keep flashing 2.0 kernel without problem?

2 when kernel is updated to 2.x will it fix the problems or are we still looking at this epic phone rebuild to fix?
[X Style (Pure) Android Development] dzidexx:
I posted only what to do if will be any problems. [MENTION=3533386]videogmike[/MENTION]
[X Style (Pure) Android Development] HPAR:
For those who had doubts, the handbag 1.7.1 works perfectly in lineage 13 by Qbanin. Tested by me =)
[X Style (Pure) Android Development] ban.codrut:
Why the links for build 20170531-0050 has been removed ?

Did I missed something ?
[X Style (Pure) Android Development] Andvark:
See the second post.
[X Style (Pure) Android Development] ban.codrut:
So you too have issues with TWRP and wiping Dalvik Cache using v2.0. On my case it would instantly reboot while trying to wipe Dalvik, which makes flashing some .zip packages impossible. My workaround was renaming the /data/Dalvik-cache directory to something else ( pending a .bk). That was to be able to flash some .zips, but I couldn't get out of the bootloop anyway.

---------- Post added at 12:06 AM ---------- Previous post was at 12:03 AM ----------

Out, okay. I truly missed that. Wasn't thinking about a two posts OP^^ thank you.

Is it safe to downgrade ?

Will do it anyway as I don't want to end up with data corruption, even if it means clean installing at this point (only 1 day old this clean install).

What I'm asking is if there is any safe way to do it ?
[X Style (Pure) Android Development] Andvark:
Once you've installed v2.0, I don't believe there's any way to go back easily. Some people report that you must go back to square 1 by reinstalling the stock ROM. I have found that simply reformatting (FORMAT, not wipe) the data partition in TWRP gets things back to normal again. Just remember that you will lose your internal storage (pics, music, etc.) in the process, so best to back it up first.
[X Style (Pure) Android Development] ban.codrut:
So I'm on a death sentence basically!

Well, I'm going to continue the ride down this path and I'll report back here when my track crashes.

I'm also going to experiment and report about restoring a previous Data backup made after the device refused to boot up and wipe Dalvik (as it did on v2.0).

From what I've read so far, reflashing v2.0 will in some cases make the device boot up again. Too bad I didn't tried that before clean installing. What I did tried and failed was wiping system and reflashing the ROM and gapps, with the kernel in the queue, but the device rebooted during some final stages of the gapps flash, so it never got to the kernel flash. Touche !

We'll see what more info I can gather. I'll try and collect some logcats ? too ^^

Thank you again for fast replies !