yashsingh1/xdaforums huggingface dataset:
[One (M9) Android Development] Alcolawl:
Just in case anyone had any doubts about how awesome this kernel is, here are some stats I've gathered over the last two weeks. Realize that there have been many builds since September 30th, and the current R34 and R35 builds are the best yet. Much more even usage of the little cluster. Battery life is fantastic.

Screen: Max Brightness (Adaptive Brightness enabled)

I/O Scheduler: Noop

Big Cluster Governor: Interactive

Little Cluster Governor: ElementalX

Minimum Online Cores: 2

Maximum Screen-Off Cores: 2

Screenshots! (not sure what happened to the battery graph but I went to work at 1 PM and definitely had the phone on the entire time)
[One (M9) Android Development] epedrosa:
How about Bluetooth performance?
[One (M9) Android Development] Alcolawl:
Works flawlessly. Running the latest Candy5 ROM and Kernel build R35. Just tested it in my car.
[One (M9) Android Development] epedrosa:
Thanks ... Think is time to come back for some Candy ... Also what kernel manager are you using?
[One (M9) Android Development] Alcolawl:
Candy has Kernel Adiutor built into it. Which is one of the best Kernel Management apps out there. My personal favorite.
[One (M9) Android Development] epedrosa:
Good...
[One (M9) Android Development] HsHTCsen:
Hi, so will this work on ViperOne M9 3.5.0?
[One (M9) Android Development] chadouming:
it only works on aosp.
[One (M9) Android Development] HsHTCsen:
I know that means Android open source project but in terms of compatibility, I'm guessing that's a no?
[One (M9) Android Development] chadouming:
indeed. AOSP roms are roms build from open source stuff. Sense is not open source, therefore, sense roms are not AOSP. Same goes for touchwizz, etc.
[One (M9) Android Development] HsHTCsen:
Gotcha.. thanks
[One (M9) Android Development] chadouming:
Working on new hotplugging algorithm.

The concept is to use the full advantages of big.LITTLE architecture.

What it will do is simple. When screen is on, we use the big cluster. When the screen is off, we use the little cluster. This mean we'll have a maximum of 4 cores on all the time. And it also mean we'll use best of both world. I don't really understand why anyone would need 8 cores on at the same time, and why we should use the lagging A53 cores.

Eventually though, I will try to figure out if we are in low activity (i.e. reading a web page or an ebook) and switch to the little cluster even if the screen is on. This would need to happen seamlessly and go back fast to A57 cores if needed.
[One (M9) Android Development] Alcolawl:
That's actually really interesting. My only concern would be heat. The phone usually gets pretty warm when the big cluster gets going, but that was always with the LITTLE cluster pegged at like 100% usage. So it'll be interesting to see how cool the phone stays when the LITTLE cluster is completely offline and the big cluster is crunching instructions instead. I assume that's what these recent "hotplug" builds have been?

EDIT: R50-Rebase causes a pretty severe bootloop. HTC logo to black screen to HTC Logo, etc. (2.10 Firmware, GSM)
[One (M9) Android Development] chadouming:
Try R51.

So far I think the little cluster get simply disabled. But i'm not sure. Some times, it seems to work correctly, but when that happen, it stop display cpu frequencies usage. (Which i suppose is normal since it offline the main cpu core)

Also, if you could tell me if the default settings cause you problem with keyboard typing it would be nice. Thanks.
[One (M9) Android Development] throcker:
someone said some thread management is bounded with cpu0, so you can not turn off all a53 without encountering issues....but, I'm not a kernel dev, just what I read sometime ago
[One (M9) Android Development] Alcolawl:
Buttery smooth. Kernel Adiutor doesn't seem to like whatever you've done, so I can't really see anything as far as the Frequency Table, CPU governors, CPU usage, etc. Using a different app, DevCheck, I'm able to see that the phone is utilizing the big cluster instead of the LITTLE. No keyboard lag or any other weird issues to report so far.
[One (M9) Android Development] chadouming:
So far, the only issue is that once the cpu0 is put to sleep, it can't be turned back on. But honnestly, i think we are better with 4 a57 than 4 a53 then 4 a57.
[One (M9) Android Development] throcker:
hahaha ok, let's get a pentacore cpu! have you tried a just-quad-A57 configuration?
[One (M9) Android Development] skulldreamz:
You'll probably be correct but in 2017, lol
[One (M9) Android Development] throcker:
can't get your joke, sorry haha
[One (M9) Android Development] n3m35155:
R52 lost ability to set min cores active. i.e. CPU/Hotplug area in Auditor.

Love the kernel BTW.. Battery life is twice what I got on sense based ROMS..
[One (M9) Android Development] Alcolawl:
I'm not sure what the hell is going on but I flashed the newest unofficial version of Candy5 (v4.0-20151020) and kernel R52 and now my phone is ... crashing? When laying dormant for an unknown amount of time. I flashed the ROM and kernel last night before I went to bed. I made sure it boot and that everything went smoothly, then fell asleep. I woke up a few hours later and decided to check my phone and noticed it was off. I tried the power button... Nothing. I plugged the phone in thinking maybe it ran out of battery... Nothing. I tried the power button again for 10 seconds. Nothing. I gave up and left the phone plugged into the AC adapter for a while and went back to sleep. About an hour later I woke up and tried to turn the phone on again, this time unplugged. It took about 15 seconds of the power button being depressed for the phone to turn on. The battery was at 49%. I then plugged the phone into a different charger just to make sure it wasn't a charging issue and went back to sleep. I finally woke up, having gotten a sane amount of sleep, and checked my phone once more. Off. I had to disconnect it and press the power button again for 15 seconds to get it to turn on. Sitting here, just now, while typing this, the phone did it again. Seems if I let the phone sit with its screen off for a minute or two it does this.

In the past, when I've had these issues, it was the kernel not playing nice with the ROM. I'm not sure what could've changed from October 13th's Candy5 build to Today's build, but Kernel release R51 was rock solid for me before. So I really don't get what's going on lol. Gonna flash a different combination of things to see if I can get to the bottom of this.

EDIT:

Disregard. The problem has been rectified. It was a mixture of a broken phone charger (heard it hissing in the outlet) and unofficial software. now running the Official 4.0 October 20th build of Candy5 with the latest R52 kernel build and it's butter smooth. Also, Kernel Adiutor mostly works again with this build.
[One (M9) Android Development] rc420head:
Depends on when he synced, there is new Bluetooth commit and some camera/video recording stuff added.

Did you try the official build I post on candy thread? https://www.androidfilehost.com/?w=files&flid=36941

------------------------------------

CandySiX coming soon
[One (M9) Android Development] Alcolawl:
Sorry I just edited my post. I fixed the issue doing pretty much exactly what you just suggested.
[One (M9) Android Development] chadouming:
New build is up in downloads section. Currently, it has a maximum of 4 cores on all the time (either 4 LITTLE cores when screen is off, or 1 LITTLE and 3 big cores when the screen is on.) There is no configuration possibility in kernel adiutor yet, I will try to contact [MENTION=4443334]Grarak[/MENTION] soon so he'll probably be able to add a hook for the tuneable. Honnestly though, I don't think it really needs config.

When screen is on, core 0 and 4 are always on so it is not lagging at all. When screen is turned off, profile is automatically changed so it takes more load to hotplug cores, but it can run with up to 4 cores at the same time so music playback should not be a problem.

Waiting some feedback.

On another note, can't wait for the final camera fix for aosp roms. I think this phone will be simply amazing.
[One (M9) Android Development] Alcolawl:
Will give it a test drive over the next day or two and report back with results. I have no doubt it'll perform well, the last few builds have been butter smooth and gave me great battery life.

On another note, I meant to post earlier suggesting that you should update the OP with more current information (as well as an updated explanation of how the kernel works, for people that are curious) and perhaps a download link.
[One (M9) Android Development] chadouming:
Updated.
[One (M9) Android Development] donmarkoni:
What was the latest version of kernel using all cores, like R22I was, for example?
[One (M9) Android Development] fix-this!:
nice kernel on candyrom but i do notice it has some lag still. what settings are recommended?
[One (M9) Android Development] s7icky.com:
fav config so far was 1 big w/ screen on... battery life was insane.
[One (M9) Android Development] fix-this!:
Care to share the full config you used? Battery life has been terrible for me today.
[One (M9) Android Development] s7icky.com:
wasnt really a config was more the kernal build he had on his temp website.

was 52 im pretty sure. only 1 big core waas online with screen on.
[One (M9) Android Development] fix-this!:
for some reason both slimrom and candy run better on their kernels than with this one. it just seems very stuttery and bad battery life. kinda of shocking with the option to have the elementalx governor.
[One (M9) Android Development] Alcolawl:
So I've been running the latest build for a few days now and I've had the chance to really get a sense of how it performs. Battery life is impressive as always. But I've noticed lag while typing on Google Keyboard. It's a bit more subtle than the keyboard lag we were experiencing with the earlier builds but it's still noticeable. Lag opening Google Now is absolutely insane. It's been this way for a while but I didn't complain about it because I figured it was because of the hotplugging and whatnot. I figured maybe Google Now really just needs more than one or two cores to be online when first launching the app. But with the latest build it almost seems worse than before. After tapping the Google Search bar on my home screen, the keyboard takes approximately 2 seconds to pop up and the app itself takes a full 5 or so seconds to completely load. I've noticed that I actually started avoiding the app and using the browser when I have to Google something really quick. Google Messenger also falls all over itself from time to time. Conversations take a few seconds to load sometimes and other times it doesn't load at all and I have to close the app and open it back up. Performance seemed better when it was the A57 Core(s) online with the A53 cluster only jumping in when loads got really heavy, but I understand this screwed some things up with the phone. I wish I could tweak the kernel more and figure out if there's a better combination of settings to mitigate this, but none of the kernel tweaking apps out there work with this kernel. I also really prefer Kernel Adiutor.

All in all, I'm willing to sacrifice raw performance for battery life. What I'm not willing to accept is choppiness, interface lag and apps taking years to start up. I'm not sure why it's like this now with the latest build but it's frustrating. That being said, I absolutely love this kernel and I'm hoping my feedback over the past weeks has helped, if even a little, to improve this much needed kernel. I'm a bit disheartened to say that I'm moving to a new phone, a Nexus 5X on Tuesday, and will be selling my M9. Regardless, I'm excited to see how development of this kernel and Candy5 continues.
[One (M9) Android Development] chadouming:
I've started back from scratch. I'm also willing to sacrifice a little for battery life, but not if it's to make the interface lag as f***. I'll keep progress record here. New beta will start from build 01 rebase. So far it's not booting so don't flash it yet.
[One (M9) Android Development] chadouming:
Ok, you can try the 01-rebase rom, it is back to big cluster when screen is on, little cluster when screen if off. Let's try with that and hope for the best.
[One (M9) Android Development] fix-this!:
Am i missing something? Wheres this rebase you speak of?
[One (M9) Android Development] Alcolawl:
He hosts most of his builds off-site here: https://temp.bbqdroid.org. Rebase R02 is the latest build.

I can confirm, although I've only been running it for 6 hours now, that Rebase R01 is a bit snappier. The phone runs cooler, there's no keyboard lag to speak of and interface lag seems to have gotten better but it still exists. Google Messenger still gets choppy at times. Opening Google Now is still a nightmare but I'm really starting to think it's the app because I tried it before I flashed your kernel, meaning all 8 cores were firing, and the app still seemed to redraw constantly.

EDIT: R02 causes reboots when the phone tries to go to sleep (the screen goes off). R01 worked well, however.
[One (M9) Android Development] chadouming:
Is that :

https://youtu.be/MXWIdBzdFLo

What you consider much lag ?

Also, no problem here about screen off. Could you send me a last kmsg after it crashes please.
[One (M9) Android Development] Alcolawl:
Yep. I guess it isn't really lag though. I just reflashed Candy5 and loaded the Google Now app with the stock kernel (all 8 cores online) and the app took just as long to load up. So it's an app problem, not your kernel by any means. I apologize.

I've been trying to grab you a kmsg for the last few minutes and after having reflashed R02, the reboots don't seem to occur anymore. What I've noticed, however, is that when I first flashed this kernel, I was able to tune everything in Kernel Adiutor, including selecting an interesting Governor called "Impulse". Now, however, nothing appears on the CPU tab in Kernel Adiutor. There's also no CDG or Westwood TCP congestion algorithms to choose from. Just Cubic or Reno. Is this a result from the rebase? If so, I think the kernel didn't properly flash before and that's why I was able to mess with those settings before, even though they weren't a part of the kernel. This is probably what lead to the reboots.
[One (M9) Android Development] Alcolawl:
Keyboard lag still exists. Nothing else running in the background and attempting to type up a text on Google Messenger is sometimes butter smooth and sometimes annoyingly laggy. Watching the CPUs it looks as though the text correction and suggestions is too taxing on the 1 or 2 CPUs running. The other cores seem just a little too reluctant to wake up. Perhaps a value tweak is needed to make them a little more eager? Idk.
[One (M9) Android Development] chadouming:
I've slowed them in the last release, however, it should be boosted to a minimum of 2 cores online when the screen is touched. And yes, i've not ported everything back into the rebase, working on it. I'll get cdg back soon.
[One (M9) Android Development] chadouming:
Uploaded new version labelled as R10-rebase. This should be back to smooth. Enjoy it.

(2 cores max when screen is off, 5 cores when screen is on. CPU0 stays always on, big cluster goes off when screen is off.)
[One (M9) Android Development] law16:
Impulse governor?
[One (M9) Android Development] Alcolawl:
I'll flash it on my M9 and report back in terms of smoothness. Won't be able to comment on battery life because I'm running an N5X as my daily driver now.
[One (M9) Android Development] fix-this!:
That site seems down at the moment.
[One (M9) Android Development] chadouming:
Fixed
[One (M9) Android Development] fix-this!:
Still down for me. Says internal server error.
[One (M9) Android Development] jsaxon2:
It's working for me. https://temp.bbqdroid.org :good:
[One (M9) Android Development] Tikerz:
Which release should we be using? Rebase R13-wifi?
[One (M9) Android Development] chadouming:
Yep
[One (M9) Android Development] xunus:
I'm getting internal server error now. ):
[One (M9) Android Development] Rogi1997:
I am getting it too
[One (M9) Android Development] chadouming:
Should be fixed now.
[One (M9) Android Development] fix-this!:
Random reboot on r13. Gonna try the r14 test.
[One (M9) Android Development] xunus:
Yes the website is back on

But i only saw 2 downloads is this normal?

Smoocha-M9-R1.1.zip 9,660,159 Nov 7 2015 7:20 PM

candy5-release.v4.1-20151107-UNOFFICIAL-himaul.zip 349,342,264 Nov 7 2015 5:03 PM
[One (M9) Android Development] Tikerz:
Anyone having choppy video playback?
[One (M9) Android Development] piterdemon:
Where is link to R13 ? I cant find.. :/

Wysłane z mojego HTC One M9 przy użyciu Tapatalka
[One (M9) Android Development] n3m35155:
Does anyone have a copy of the last version with the option to select # of cores?

I think it was some where around 42-46. It would be the last one without the "hotplug" in the name.

Thanks
[One (M9) Android Development] Tikerz:
Which one should we be using now?
[One (M9) Android Development] chadouming:
v1.3
[One (M9) Android Development] clever_man:
Can you fix problem with BT on official nightly?

http://xdaforums.com/showpost.php?p=63868541&postcount=424
[One (M9) Android Development] djsubtronic:
Latest v1.3 still causes random hard reboots on the official nightly... I'm not sure how to retrieve kernel logs else I'd post one.
[One (M9) Android Development] AirwolfUK:
Also random reboots on Candy
[One (M9) Android Development] KnightStar:
Has anyone tried v1.4? I got hard reboots from v1.3 as well on CM12.1 Nightly.

EDIT: I still get hard resets.
[One (M9) Android Development] Asselalf:
Since sunday on 1.3 with official CM 12.1. After flashing i got 2-3 random reboots. Now its stable and no reboots. Maybe you can pull last kmsg and the dev can look into it
[One (M9) Android Development] Tikerz:
How come the CPU governor is Interactive? I thought it was using ElementalX?
[One (M9) Android Development] chadouming:
You can change it . . .

On another note, v1.5 and 1.5-test should be bugless. If you guys want to try both and tell me which one you feel is more responsive/"better"(for lack of a better word), I'd appreciate feedback. Thanks.
[One (M9) Android Development] Tikerz:
When I tried to change it ElementalX wasn't an option.
[One (M9) Android Development] Asselalf:
I'm on 1.5. No lags or random reboots.

Gesendet von meinem HTC One M9 mit Tapatalk
[One (M9) Android Development] johnandbodhi:
on candy5.1 himaul 11/23 running 1.5 and no problems..
[One (M9) Android Development] eminembdg:
Same exact setup here and also no issues
[One (M9) Android Development] 123421342:
Where did you get the 11/23 build?
[One (M9) Android Development] johnandbodhi:
same directory as the kernel builds.
[One (M9) Android Development] 123421342:
FYI 1.5-test seems great, regular 1.5 was really laggy and generally awful
[One (M9) Android Development] Rogi1997:
Is there a chance to get dt2w working?

Gesendet von meinem HTC One M9 mit Tapatalk
[One (M9) Android Development] 123421342:
I am on the unoffical 11/23 build, running 1.5 test. Kernel auditor shows that only 1 big and 1 little CPUs are on even under load. Is this intended?
[One (M9) Android Development] Jhonys:
Was running 1.5 and 1.6 on latest candy rom and the phone just felt sluggish. Had to press multiple times to open stuff, keyboard not so responsive. Reverted back to candy's kernel and phone is much snappier.

Kernel auditor showed that only 1 small and 1 big CPUs were on, or only 1-4 small. I assume that is the reason for my findings.
[One (M9) Android Development] Rogi1997:
Is Smoocha-M9-R1.6-Android-M.zip fully working with cm13?

<<<<<<<<<<

Edit:

OK it is working

Thanks for this nice kernel
[One (M9) Android Development] rc420head:
Nice

Sent from my LG-H811 using Xparent Red Tapatalk 2
[One (M9) Android Development] eminembdg:
[MENTION=5066258]rc420head[/MENTION] do you know if the M Version of this work's on your candy six build?
[One (M9) Android Development] rc420head:
I personally haven't tried but was told it does work

Sent from my LG-H811 using Xparent Red Tapatalk 2
[One (M9) Android Development] jsaxon2:
I'm running 1.7 m kernel on Verizon candy6 build with no problems.
[One (M9) Android Development] Rogi1997:
for some reason my phone becomes very hot ( 70 °C cpu in Kernel Auditor ) on kernel 1.9, when I watch a 5 minutes video on youtube app.

on 1.6 I don't have this problem.

have you changed something that can be a reason for this problem?
[One (M9) Android Development] IxBUSTERxI:
Hello,

I tried version 1.7m and 1.9 of your kernel and both break front facing camera on candySix (12/7 gsm).

Maybe you know where to look ;)
[One (M9) Android Development] piterdemon:
Weird, I dont get more than 55°C on cm, stock, candy kernels and with smoocha too

Wysłane z mojego HTC One M9 przy użyciu Tapatalka
[One (M9) Android Development] 123421342:
Can confirm 1.9 broke front camera for me. Not a big deal, I am trying out the unoffical candy6 12/16 build with the new 2.0 kernel
[One (M9) Android Development] ahrion:
2.0 works perfectly with camera.
[One (M9) Android Development] ahrion:
Can anyone post the links for the download?
[One (M9) Android Development] dom_mnml:
:confused: :!?!?!:
[One (M9) Android Development] 123421342:
Look on the OP post... its right there

If anyone is wondering I am running the 2.2beta kernel with the 12/19 build and it is pretty good. Mostly stable but it will hot restart if you try to manage app data (uninstall clear data etc), security settings makes the settings app crash, and android remote control crashes immediately. Other than that, rom is pretty awesome
[One (M9) Android Development] Rogi1997:
Is it possible to get wake gestures working?

Gesendet von meinem HTC One M9 mit Tapatalk
[One (M9) Android Development] colorprint:
Is it works with android 6.0?
[One (M9) Android Development] liam_davenport:
"Smoocha-M9-R2.3-beta-M" Latest kernel I believe is for CM roms only not Sense ;)
[One (M9) Android Development] Abaddon:
just saw there's R3.0. gonna try it in a bit and report back :)

is it only on dual core mode? only 1 core per cluster running all the time?
[One (M9) Android Development] ferreinf:
Working fine on latest aicp, thanks

Droidlab.pt
[One (M9) Android Development] Rogi1997:
May I ask, what the problem is, to get dt2w working? :confused:
[One (M9) Android Development] rc420head:
See Ethan chen's comment here. http://review.cyanogenmod.org/#/c/122709/1/drivers/i2c/chips/CwMcuSensor.c

Sent from my HTC One M9 using Xparent Red Tapatalk 2
[One (M9) Android Development] Rogi1997:
Thanks for posting this link

now i know where the problem is

:fingers-crossed:
[One (M9) Android Development] dsg2003:
I flashed Smoocha-M9-R3.1 with latest candy six today. Unfortunately camera does not work..... Someone can confirm or help?

*edit* i installed Google Camera from playstore. Same Error. Does not work

*edit2*flashed some earlier versions of smoocha... Same error :(
[One (M9) Android Development] liam_davenport:
Tried with stock kernel?
[One (M9) Android Development] dsg2003:
I installed HTC camera pack..... Now all works
[One (M9) Android Development] Rogi1997:
With 3.2 and 3.3 I have problems with touchscreen (does not react). On 3.3 I am not able to enter the pincode
[One (M9) Android Development] jbfountain:
[MENTION=1986924]chadouming[/MENTION], any plans on updating to MM, or have you stopped all development for this rom?
[One (M9) Android Development] chadouming:
Version 2.3+ are for android M.
[One (M9) Android Development] Rogi1997:
Do you build more smocha builds or do you switched the phone, and no builds anymore for hima?
[One (M9) Android Development] Black_Eyes:
Can this be used on latest CM builds (CM13) ?
[One (M9) Android Development] Black_Eyes:
Hello [MENTION=5823687]liam_davenport[/MENTION] can you please share this 2.3 kernel? i'm not able to open that bbqdroid.org
[One (M9) Android Development] liam_davenport:
Not loading for me either sorry mate :crying:
[One (M9) Android Development] 3's&7's:
Curious too, do we have any CM 13 users out there w/this kernel?