yashsingh1/xdaforums huggingface dataset:
[HTC One X+] :
v1.1 is here: http://d-h.st/WOi

CoreManager.apk is here: http://d-h.st/R5l

-after rebooting, remember to open/save+exit to restore your preferences

-Please grant super-user permissions

Version 1.1 Notes

Sweep to wake [or slide to wake or s2w] is working, but still needs enhancement, but I believe everything else is working fine.

My kernel config

-Slide to Wake [S2W]

-Hotplugging with a user defined limit (using the above app)

-The low power core is prevented when awake, and the high-power quad-core is forbidden when the screen is off. This is to ensure performance when the screen is on, and power-saving when it is off (+ there is a two core minimum when device is awake)

-smartmax governor by maxwen

-added fast-charge to kernel (thanks maxwen)

-added BLX (thanks ezekeel)

-Available IO Schedulers: BFQ, CFQ (as default), Deadline, NOOP, SIO, ROW, and V(R).

-Miscelaneous tweaks: ticket based rwsem algorithm; Google's tcp proportion rate reduction algorithm; cifs; zcache with latest LZO; SLUB
[HTC One X+] adamkaye:
I'm new to this whole kernel flashing thing. I just flashed it and installed CoreManager. I'm currently on Elegancia 5.2, De-sensed. I'm looking to get the best battery life I can. So I have some questions about the settings:

1) Hotplugging Limit: Leave it at 5?

2) Charging limit: I set it to 95% percent. I figure this gives me a good combo of long-term battery life and per-charge life.

3) Fastcharge: On. This allows me to charge faster over USB, no?

4) GPU coupling: I have no idea what this is.

5) What have been people's experiences with schedulers? It's defaulted to CFQ.

Thanks for any and all help for this newbie.
[HTC One X+] :
The hotplugging shows 5 the first time you run the app. You should change it to 4 or less. It limits the cores that are allowed to come online, so you can save some juice. If two is all you need and everything runs great, use two.

I currently recommend cfq, but feel free to play around. maxwen recommends bfq.

Turn off GPU coupling and your GPU will run in performance mode. I found it good for eliminating some lags, but will use more power when the device is awake obviously!
[HTC One X+] adamkaye:
Thanks for everything, bedalus. You rock! Fast charging is already working great. I'm gonna start at 2 with hotplugging and give cfq a shot, then maybe try bfq in a few days.
[HTC One X+] towelboy:
I remember that you did a comparison for these two schedulers back in the Nexus S days! What's the difference again?
[HTC One X+] :
On the nexus s bfq was rubbish!

On this device it performs well. Bfq assigns a time budget for each io request, cfq allocates equal time. I've seen demos of bfq running on desktop and it's very impressive compared to cfq. But phones don't multi task in quite the same way, so it's worth doing your own testing
[HTC One X+] towelboy:
Will be testing bfq today then :D
[HTC One X+] scarletbaron:
This Kernel is pretty good thanks for it!

But just got one question, is it me or does this kernel cause the phone to heat up with just basic use. I came from Eleganica 5.2.0 kernel and that didn't heat up the phone.

Is there anything i should tweak to avoid the heating issue?
[HTC One X+] :
It doesn't for the international version. Can anyone else confirm this heat issue?
[HTC One X+] towelboy:
I also came from the included elegancia kernel and I have always had the heat issue. The phone usually gets hot from long periods of screen on time or with heavy usage like games and videos.

But I have no heat from this kernel at all after limiting the cores to 2 and under clocking to 1.3Ghz. I turned off gpu coupling and power saver, this device still flies without getting hot and it lasts 1.5 days! :D

Btw for me, BFQ made the phone less 'buttery' but gaming performance was very good
[HTC One X+] mat3usz:
Kudos

thanks for the sweet kernel bedalus. really appreciate it, especially since the att variant doesn't seem to have as much spot light as the international variant. nonetheless, kudos and keep up the great work.

running on two cores, underclocked, and it purrs. little to no heat and the s2w is an awesome feature! :good:
[HTC One X+] deeznuts:
How do you guys underclock? I just use battery sage mode to get to 1.3ghz, another way?

---------- Post added at 10:42 AM ---------- Previous post was at 10:16 AM ----------

I can. First time using a custom kernal for this device and noticed right away more heat. Even when my device is off sitting in my pocket for an hour then I wake it up the temp is 95 degrees F, that's damn hot to be Idle!

Using eleganica latest colored Rom and in this situation it should he idle around 80 degrees F so a 15 degree jump in temp just using this kernal.

Maybe help debug I have it set for 2 cores, gpu coupling ON, and fast charge ON.
[HTC One X+] :
It shouldn't be getting hot. If anyone feels their device is hot for no reason please reboot then send me a copy of /proc/last_kmsg so I can see what's going on
[HTC One X+] :
Turning off gpu coupling will use more power as it will run in performance mode!
[HTC One X+] towelboy:
Is it a significant difference in battery life and performance?
[HTC One X+] :
I don't know yet, I haven't tested it both ways for long enough to tell.
[HTC One X+] towelboy:
I'll be testing GPU coupling off for two days and then the other for two days then. I'll report my screen on and battery life etc. after today!
[HTC One X+] deeteroderdas:
Thanks for the kernel, Bedalus! Looking forward to trying it out.

ViperXL
[HTC One X+] deeznuts:
How could I send a copy of this to you? Never done anything like that before so not sure how or what you need a copy of. Thanks
[HTC One X+] :
You need a file manager app with root access. Copy and paste the file in the folder 'proc' called 'last_kmsg' to your sdcard folder then upload it anywhere.

You have to reboot first, so wait until you experience unexplained heat from the device first, then reboot asap
[HTC One X+] :
I think I'm starting to understand the heat issue. I think for a lot of atnt users the alternative kernel availability was low, and most users have got used to stock.

I've not used stock in ages, and I'd forgotten that it runs quite cool, even if it runs quite laggy!

I'm going to work hard to bring in power-saving features, but try to keep the performance as high as possible. I'm using a version now that runs on just one core and allows the low power cpu even with the screen on (like stock). It's proving difficult to tune, but I'll try to get a release out soon
[HTC One X+] joey-pagan:
Hey man! Just tried out your Kernel and I must say I'm very glad you've taken it upon yourself to improve the user experience of regular Sense users via Custom Kernel. Anyway, I wanted to report my experience with it.

First off, I'm using stock HTC Sense 4+ ROM (AT&T version, running latest firmware/software update installed via RUU), Unlocked and Rooted with the latest TWRP recovery installed. After installing your Kernel I noticed:

-S2W worked perfectly and I did not experience any of the reported problems with the capacitive buttons.

-I tried (through the Core Manager) several Governors [Edit: Not Governors, I meant IO Schedulers] and still I found performance issues (namely, skips/pauses while playing music).

-I don't think the Fast Charge option is functioning properly. I didn't notice a difference in charging speed and a third party Fast Charge app does not detect the fast charge feature in the kernel.

I don't know if there's a workaround to the issues I reported or if I'm doing something wrong... I was hoping you could shed some light on these. Either way, I'm looking forward to further developments on this kernel! :good:
[HTC One X+] iggdawg:
Depending on your battery level it may or may not charge any faster, since the battery will charge slower as it gets closer to full. The way I can tell it's doing its thing is by opening up my monitoring app (I use Android Tuner), I can see it switch from "USB plugged" to "AC plugged". Not all USB ports can supply more than 500ma. I've tested every version of this kernel and so far I've never had issues with fast charge when enabled in Core Manager.

Now that you mention it I did notice streaming radio skips when I was using the kernel, but I chalked it up to bluetooth issues... namely that my device was on the other side of my head from the earpiece, my head is full of goop, and goop attenuates bluetooth. But repositioning it didn't make it go away. I should retest this.
[HTC One X+] reaper90:
This is not really a performance issue i think. This can happen due to your phone being locked down to low power core only when screen off. So if you've got many apps/processes running in the background there can be sound stuttering because low power core can't handle all thist. At least this is how it is on international version. Turning off WiFi seems to help a lot against this music stuttering.

Also i read about some other users fixed this music stuttering by using 3rd party player apps with an option to increase music buffer size, but since i'm happy with stock player i didn't test it myself.
[HTC One X+] joey-pagan:
That would make sense. If that's the case then the 1 Core limit when the screen is off is actually a problem for me because if it was having trouble with simple playback of locally stored music, then Pandora or general music streaming will most definitely be a no-no (given the fact that when listening to music, most of the time the screen is off).

---------- Post added at 05:35 PM ---------- Previous post was at 05:32 PM ----------

I was using an iPad charger, so yeah, it had the full 1000ma and 2.5 watts. But ok, I guess I'll have to monitor it more closely and at different charge points. Either way, any idea of why the other app didn't recognize the kernel feature?
[HTC One X+] deeznuts:
Same here as far as the skip issue goes.

I really appreciate the work in doing this as well but honestly don't notice any "faster" nor "smoother" experience while using this device with this kernal. It is my first time using a real custom kernal so figured I would notice something? For regular apps opening and closing speeds are the same, my apps run the same, some like facebook actually opens a little slower since using this kernal.

Having gpu coupling ON or OFF makes no difference for me on FPS when running graphic intense games or apps such as the epic citadial benchmark tool, still get around 44.1 fps consistently and again with gpu coupling ON or OFF so this feature more no difference in this respect.

My settings have been 4 cores, bfq, fast charge on and gpu coupling on for the most of my testing. I also have the HTC sense battery save mode ON if that makes a difference in my testing? Figured it would just keep the max cpu at 1.3ghz.
[HTC One X+] reaper90:
On international version of this Kernel, bedalus is already testing some options to allow high performance cores when screen off. I think if it works well, he will definately implement this in AT&T version too. This should solve any lag/stuttering while listening to music, but also increase battery drain while doing so.
[HTC One X+] scarletbaron:
Seriously thank you so much for your dedication man!

Sorry i didnt reply sooner, but i reflashed your kernel and the heat issue seems to have reduced.

I did notice a few performance lags on and off.

But as requested ive got "last_kmsg" file u wanted. Shall PM it to you, cant seem to post it here

Hope it helps
[HTC One X+] :
Yeah, I'm not going to do that now, I posted about it already in the other thread. I'll find another solution to the music issue when I've got higher priority stuff sorted first
[HTC One X+] skeppley:
There must be something else going on there.

I run pandora with the screen OFF almost all day, and i get no lag/stutter with it at all.

I am also set to 4 cores and coupling off, but just tried it with 2 cores, and it still worked fine.
[HTC One X+] reaper90:
Low power core is definitely capable of playing music, but there may be lags/stuttering when there are too many other processes/apps running in background. I recommend Greenify to prevent apps you don't want to run in background from doing so when screen is off.
[HTC One X+] :
I'll build a version with stock cpu governor and stock hotplugging when I get back and we can see if this resolves the issues
[HTC One X+] skeppley:
LOL, thats probably why mine works so well...i DO use Greenify :)
[HTC One X+] :
Hmm. Nope, that didn't resolve anything. With the stock code I have horrible lags in Asphalt 7. I'll stick with smartmax for now, and I'll have a look at resolving the music bug some other way.
[HTC One X+] towelboy:
Hey guys, some guys are talking about how adaway is causing the music skips, check the Elegancia5.2.0. thread
[HTC One X+] marceloalvarez:
Charging limit does not work, every morning when I wake up

the indicator is one hundred percent, this happens to someone else
[HTC One X+] :
Cool, thanks for the info, I'll check it out
[HTC One X+] deeteroderdas:
The charging limit does work for me, however. Gotta love the randomness...
[HTC One X+] :
If the code is working fine then the issue is probably that the app needs to be granted super user permissions
[HTC One X+] iggdawg:
I suspect that the app is doing its job, bit doesn't hard cut charging at the limit? Rather it trickles in at a few mA after the limit is reached. And leaving it plugged in overnight gives it the time it needs to slowly keep charging the battery. Or something like that. Just my best guess from what I know about how lithium batteries and their charging circuits work. I could be totally wrong since I don't know how the app interacts with it all.
[HTC One X+] :
I leave mine plugged in over night too, and it works as intended
[HTC One X+] iggdawg:
Interesting. I just came off my on-call week so I can test again. I'll re-install the latest and test charging specifically.

For those with and without issues, out of curiosity, are you using USB fast charge or not?
[HTC One X+] :
I always use fastcharge, and have no issues. But again, we're not on quite the same device...

But anyway, I've just released an update for the international version that I'm very pleased with. I'm going to merge those changes in here too, so there will be a new version up in maybe an hour or two (depending on how demanding my daughter gets...)
[HTC One X+] :
v1.2 is here: http://d-h.st/Tmz

CoreManager.apk is here: http://d-h.st/R5l

-after rebooting, remember to open/save+exit to restore your preferences

-Please grant super-user permissions

Version 1.2 Notes

In the last release I accidentally fixed a config mistake. Since then I've built many versions making tweaks and adjustments to the smartmax governor, and basically went around in a giant circle! But here's a little run-down of the changes since 1.1

-increase the default s2w distance a little

-increase the VM read ahead size from 128kb to 512kb

-brought the VM swappiness down from 60 to 10

-brought down the htc performance target from 1.7GHz to 1.3GHz (for the sense interface)

-add a new mode for 1 core operation and a mode for multicore operation with the screen off

-make hysteresis polarised (any change of direction resets the pointer to 0)

>>> i.e. Core down - - - 0 + + + + + + + + + Core up
^
>>> The pointer might get up the the eighth up request,
then start getting down requests. Previously, this meant
moving the pointer down eight times then a further three
times before unplugging a core. Now, any down request
immediately brings the pointer straight back to 0. The
same principle applies to up requests too.

The big change brought in is to the smartmax governor. Great big thanks again to maxwen of course! His work on this has been absolutely brilliant, and something I certainly don't have the talent for!

On top of the updates to the governor I have worked extremely hard in making this version as power-saving as possible without sacrificing any performance. The system load must reach 95% to scale up, and drop below 40% to scale down. This means the frequency is much less likely to scale up, and much more likely to scale down. I've reduced the time that it takes to scale down by 25% and increased the time it takes to scale up to the 1.7GHz max by 125% (to prevent spurious max frequency spikes) but this does not apply if the current frequency is below the ideal of 1.3GHz. This keeps everything running nice and smooth.

I've also switched IO_IS_BUSY to 0 and IGNORE_NICE_LOAD to 1, to help keep the frequency low, as I noticed maxwen had followed this course himself. This will also help keep the CPU frequency low.

Sorry about the long notes! :p

My kernel config

-Slide to Wake [S2W]

-Hotplugging with a user defined limit (using the above app)

-The low power core is prevented when awake, and the high-power quad-core is forbidden when the screen is off. This is to ensure performance when the screen is on, and power-saving when it is off (+ there is a two core minimum when device is awake)

-smartmax governor by maxwen

-added fast-charge to kernel (thanks maxwen)

-added BLX (thanks ezekeel)

-Available IO Schedulers: BFQ, CFQ (as default), Deadline, NOOP, SIO, ROW, and V(R).

-Miscelaneous tweaks: ticket based rwsem algorithm; Google's tcp proportion rate reduction algorithm; cifs; zcache with latest LZO; SLUB
[HTC One X+] deeteroderdas:
No issues using fast charge, 95% limit.
[HTC One X+] deeznuts:
Awesome, sounds like a huge update!

Quick question. Coming from version 1.1 to now 1.2 do unjust flash the kernal or with each update is the core manager apk config app also need to be updated? Wasn't sure if the core manager app is universal to any of your kernals or if u make changes to this also so also needing to update? Thanks

---------- Post added at 08:45 AM ---------- Previous post was at 08:44 AM ----------

Curious why people choose the fast charge limit to under 100%? What is Tue reason for this? Does your phone only charge up to 95% with your setting? Why not 100%? Thanks
[HTC One X+] :
You don't need to update the app unless I say it's been updated too.

To find out more about the charging limit, click on blx (it's a link) in the download post
[HTC One X+] towelboy:
Have you thought about making a 'version matrix' for hXORe like the nexus s?
[HTC One X+] starfox5194:
Any chance we can make one of the four main cores active during screen off? Whenever the screen is off, n7player thinks it's fun to "skip" (pause and play kind of like a dirty Audio CD). This happens more often with your kernel I assume because you only allow the low powered core to be active when the screen is off.

Can we prioritize music playing apps? This is my one gripe about the phone! happens on stock kernel and I just really hope we can fix it with a custom kernel.

I don't want to **** around with greenify. I like to get my facebook messages instantly like texts. And I like to have the gps running when the screen is off.

Thanks for all of your work regardless. The phone does run smoother with the screen on.
[HTC One X+] :
Version matrix? I suppose I could...
[HTC One X+] :
You could try allowing multi core with screen off. Echo 5 into /sys/class/misc/cpusallowed/cpusallowed
[HTC One X+] NasaGeek:
Long notes are best notes. It's neat to see the nitty gritty stuff.
[HTC One X+] pradeepd:
[MENTION=4128576]bedalus[/MENTION]. Just flashed 1.2 and it's all buttery smooth. 1.1 was kind of laggy. Thanks for the excellent update.
[HTC One X+] joey-pagan:
Ok, just flashed version 1.2 and played around with it a little. Here are my experiences so far:

-Just like ver.1.1, no issues with capacitive buttons or S2W.

-Tested the music streaming which exhibited problems in ver.1.1 (lots of skips and pauses). Using IO Scheduler CFQ still exhibited problems, however, using BFQ seems to do the trick (so far).

-I'm still testing out Fast Charge. So far other Fast Charge Apps do not recognize the Fast Charge Feature on the Kernel (just like ver.1.1) (Why is that?). Also, I put my phone to charge for a few minutes on an iPad charger, but when i checked on it, it hadn't charged much at all. I then checked on the power monitor and it said it was connected to USB power source, it wasn't until I checked again a little later that it said connected to AC power source.

That's it for now. I'm going to keep testing it and report back.
[HTC One X+] towelboy:
Seems like fast charge isn't working for the device
[HTC One X+] :
That's weird, a few people have said it's working fine. I'll need to look into it.

I'm working on fixes for the music issues, and I've made good progress. There'll be an update soon
[HTC One X+] joey-pagan:
OK, so after a full day of usage, I've got a few more things to report:

-General phone performance is slower than usual (Apps take long to load/react. Animations are choppy). Could be a thing with the IO Scheduler I'm using (bfq) even though that's the one that "fixed" the audio streaming issue. I did manage to improve the overall performance by decoupling de GPU, though... But still, it shouldn't have been that much of a dramatic difference in the first place.

-Got a random reboot.

-BLX seems to work as intended.

-Haven't noticed any noticeable improvements in performance, battery life or charging speed.

That's about it for now.
[HTC One X+] towelboy:
I think it may be the BFQ, I experienced similar results with it and the choppiness and random reboot disappeared with CFQ
[HTC One X+] :
Performance should be better in v1.3

This kernel really ought to drain the battery faster due to the way the low power CPU is forbidden with the screen on, and the two core minimum. But how much faster? I don't know, but I don't think much, since the screen is the main problem.

You also mentioned a reboot.

I already re-added all my patches again from scratch, and cleaned out all the international code... so... there's nothing to do! I've doubled checked all my tweaks for sanity. This kernel isn't that far removed from the original source. In the future, if you get a reboot, grab the /proc/last_kmsg file for me as soon as the OS is back up. :)
[HTC One X+] :
v1.3 is here: http://d-h.st/c2P

CoreManager.apk is here: http://d-h.st/R5l

-after rebooting, remember to open/save+exit to restore your preferences

-Please grant super-user permissions

Version 1.3 Notes

This version mainly contains tweaks to the cpu frequency governor that allows for better music playback with less glitches (like hardly any now!)

The behaviour with the screen off is changed slightly, so that the frequency now rests at 204MHz with the screen off, and this seems to solve the majority of glitches, as well as saving power.

I've also tidied up some of my messier efforts to wrestle with the hotplugging code that help to prevent unnecessary up requests that may also have been causing demand spikes that interfered with audio.

Feedback would be appreciated from anyone who listens to music on their device and who previously had audio quality issues.

My kernel config

-Slide to Wake [S2W]

-Hotplugging with a user defined limit (using the above app)

-The low power core is prevented when awake, and the high-power quad-core is forbidden when the screen is off. This is to ensure performance when the screen is on, and power-saving when it is off (+ there is a two core minimum when device is awake)

-smartmax governor by maxwen

-added fast-charge to kernel (thanks maxwen)

-added BLX (thanks ezekeel)

-Available IO Schedulers: BFQ, CFQ (as default), Deadline, NOOP, SIO, ROW, and V(R).

-Miscelaneous tweaks: ticket based rwsem algorithm; Google's tcp proportion rate reduction algorithm; cifs; zcache with latest LZO; SLUB
[HTC One X+] joey-pagan:
Alright, downloading ver.1.3. If I get a reboot, I'll be sending you the kmsg file.
[HTC One X+] hastings101:
Same for me, no reboot though, using BFQ. I reflashed stock to compare and it's much faster. Going to try 1.3 with CFQ for a few days to see if it does better.

*Also, when it comes to fastcharge status I'm clueless: Tegra Overclock, my go to utility, shows it working. Fast Charge does not. Not really sure if either of those are accurate when it comes to this - it feels much faster to me but I haven't timed it or anything.