yashsingh1/xdaforums huggingface dataset:
[One (M8) Android Development] munkyvirus:
It's happening! But where's the download?! Newest Hypernova for GPE is from May!
[One (M8) Android Development] piyushkohli97:
Checking ur website every sec now for marshmallow updates.......
[One (M8) Android Development] thelangosta:
Did you really just ask when????
[One (M8) Android Development] MassStash:
Didn't even read that as an Eta question, we shall let him live..... For now..... Haha

~m8whl on the Always Solid ViperOneM8 Latest

Hypernova mako_hotplug kernel at 2.572 Max ¦ 300 Min ¦ 1.190 Sleep

interactive (Franco tweaked)*

row
[One (M8) Android Development] i'mrunningoutofusernames:
Hi, is jan 3 one the latest? You have jan 6 in the thread title
[One (M8) Android Development] MassStash:
Whatever latest file visable to you is the latest. Dates are when I do something to whatever I put the date on. So when I made the kernel, it gets dated then. When I update thread, it gets dated. I don't match dates
[One (M8) Android Development] eriknors:
Just wanted to report hypernova is running great on S.ROM JW4.4.0 [MENTION=1238555]MassStash[/MENTION] excellent work bud
[One (M8) Android Development] buddwm:
I'm attempting to install the latest MM GPE Hypernova kernel (which for me has a date of Jan 3rd, not 6th), and I am getting this error. Using latest TWRP on Verizon variant:

Checking device...

script aborted: assert failed: getprop("ro.product.device") == file_getprop("/tmp/anykernel/anykernel.sh", "device.name1") || getprop("ro.build.product") == file_getprop("/tmp/anykernel/anykernel.sh", "device.name1") ||
getprop("ro.product.device") == file_getprop("/tmp/anykernel/anykernel.sh", "device.name2") || getprop("ro.build.product") == file_getprop("/tmp/anykernel/anykernel.sh", "device.name2") ||
getprop("ro.product.device") == file_getprop("/tmp/anykernel/anykernel.sh", "device.name3") || getprop("ro.build.product") == file_getprop("/tmp/anykernel/anykernel.sh", "device.name3") ||
getprop("ro.product.device") == file_getprop("/tmp/anykernel/anykernel.sh", "device.name4") || getprop("ro.build.product") == file_getprop("/tmp/anykernel/anykernel.sh", "device.name4") ||
getprop("ro.product.device") == file_getprop("/tmp/anykernel/anykernel.sh", "device.name5") || getprop("ro.build.product") == file_getprop("/tmp/anykernel/anykernel.sh", "device.name5")
assert failed: getprop("ro.product.device") == file_getprop("/tmp/anykernel/anykernel.sh", "device.name1") || getprop("ro.build.product") == file_getprop("/tmp/anykernel/anykernel.sh", "device.name1") ||
getprop("ro.product.device") == file_getprop("/tmp/anykernel/anykernel.sh", "device.name2") || getprop("ro.build.product") == file_getprop("/tmp/anykernel/anykernel.sh", "device.name2") ||
getprop("ro.product.device") == file_getprop("/tmp/anykernel/anykernel.sh", "device.name3") || getprop("ro.build.product") == file_getprop("/tmp/anykernel/anykernel.sh", "device.name3") ||
getprop("ro.product.device") == file_getprop("/tmp/anykernel/anykernel.sh", "device.name4") || getprop("ro.build.product") == file_getprop("/tmp/anykernel/anykernel.sh", "device.name4") ||
getprop("ro.product.device") == file_getprop("/tmp/anykernel/anykernel.sh", "device.name5") || getprop("ro.build.product") == file_getprop("/tmp/anykernel/anykernel.sh", "device.name5")

Installer Error (Status 7)

EDIT: I was able to workaround the error by disabling the device check in the anykernel.sh script. Installs fine after that. Looks like you don't have all the M8 variants in your script?
[One (M8) Android Development] MassStash:
Hmmmmm thanks heads up nate, take a look soon as I can. Should be good to go.
[One (M8) Android Development] TheKnux:
Will this kernel work with CM13 (BlissPop Beta)?
[One (M8) Android Development] hdorius:
Nope..this kernel is for sense or gpe only.
[One (M8) Android Development] Roma80:
I'm confused. I can't download the hypernova for sense rom - want it for the new viperone 5.0.0. - no permission on server...

Is this right?
[One (M8) Android Development] playguy1:
yeah because there is no sense 6.0 kernel yet , the link is not meant to be working , Wait for the verizon firmware to be released by HTC.
[One (M8) Android Development] Kristian2018:
Hypernova 2.01 gpe working great on new s.rom 6.01 sense rom ..... Awesome work [MENTION=1238555]MassStash[/MENTION]

sent from m8 rocking S.Rom 6.01
[One (M8) Android Development] clippy83:
So it will work on the jw version as well?
[One (M8) Android Development] Kristian2018:
Jw is just s.rom without the china stuff and aroma installer so yes it should.....

sent from m8 rocking S.Rom 6.01
[One (M8) Android Development] cdfreak:
Thnx for this brilliant Kernel, it makes me and my phone realy happy with the very good battery life! Using it now for 2 weeks!
[One (M8) Android Development] mbwambo:
Can you giving me the hints how you costumized it on installation??
[One (M8) Android Development] cdfreak:
I dint do anything special beside installing the kernel and change the read to 1024 and set max gpu to 465. Also using Greenify donate and Amplify donate for that extra Jouce :). Aim also using SkyDragon- GPE as my daily rom.
[One (M8) Android Development] MassStash:
Much appreciated [MENTION=3650716]cdfreak[/MENTION]! Spread the word please

~m8whl on the Always Solid ViperOneM8 Latest

Hypernova mako_hotplug kernel at 2.572 Max ¦ 300 Min ¦ 1.190 Sleep

interactive (Franco tweaked)*

row
[One (M8) Android Development] Gamesoul Master:
I am intrigued. And a little skeptical, since this seems to have everything I'm looking for in a kernel. Hmm... I'll have to try this one out :D
[One (M8) Android Development] MassStash:
eh, I heard a couple people like it... lol Let me know what you think mang
[One (M8) Android Development] Gamesoul Master:
Still early of course, but I like it so far. Performs well, we'll see how the battery holds over time of course.

Question though. In the governor settings (Interactive of course), I see Target_Loads is set as "85 1497600:90 1728000:70" (well, it was 1500000 and 1800000, but I changed them to frequencies actually on the table). I'm not sure why the target load for above 1700000 drops to 70 when normal behavior would be to have it much higher (at least 95). I'm wondering if that's intentional or not. If so, I can see the logic of it, though I'd wonder how battery life is affected by it (though time will tell on that part).
[One (M8) Android Development] MassStash:
14976 and 1723 are the actual frequencies in the freq table so that's why those are there, not just random numbers. Nah, I don't think I would remove 1723 even if it was negated tho, so then change it to what? Those are just the settings that I've dialed in to get things runnin how I like it, so lemme know what results you're seein after playing with the settings a bit.

~m8whl on the Always Solid ViperOneM8 Latest

Hypernova mako_hotplug kernel at 2.572 Max ¦ 300 Min ¦ 1.190 Sleep

interactive (Franco tweaked)*

row
[One (M8) Android Development] Gamesoul Master:
Well yeah, I changed them to the actual frequencies. By default, they were 1500000 and 1800000, which aren't real frequencies. Still works fine that way, I'm just picky like that... lol.

But yeah, I just found it unusual to see target loads increase with frequency (which is normal) and then drop drastically to 70 at the end, so I wasn't sure if that 70 target was intentional or meant to be a higher number. Could work pretty well, although it'll jump from 1724000 to max freq pretty fast that way. There's arguments for that being a good thing, finishing tasks faster to sleep sooner. I'm gonna leave it like that, see how it works out. Maybe tweak it a bit after a while to compare results.
[One (M8) Android Development] Gamesoul Master:
I ended up tweaking the governor and hotplug settings last night after all to try to achieve the best battery life without sacrificing performance. Been running great today so far, and better battery life than I had before, which was already pretty decent. Could probably go a day and a half with pretty moderate use, without using any task killers or greenify type apps.

All in all, I really like this kernel, gotta say it's probably gonna be my new favorite for as long as I have this phone. Still planning to do a Sense MM build eventually?
[One (M8) Android Development] MassStash:
Nice, that sounds dope bro. Post some settings you're messing with, maybe we can get some other kids playing around too haha. Lost my settings guy for beta testing and then rollout, so I'd love some input. I actually don't toy with the settings too much as I can never find time to document and switch **** all the time. Need like a good 3 to 5 days of use on a setting profile to get solid settled in stats. Oh yea, just waiting for some source. Right now you can flash gpe on sense, but wifi and exfat formated SD card may not function, I notice flar's sense build is literally the gpe kernel with sense in the version title in defconfig. Also, gpe kernel gets Viper 5 booting, but you have to **** with **** to get service up, and still couldn't get data, so I wait for sprint ota to get sprint support working for Viper 5 again. And then when source drops, ill most likely be basing off HK source, and adding in GSM and vzw support. Soooooo, week from now sprint rom... I'll be all over sense then so I'll get some sense flashables built up, then the wait for proper source to drop, and rebase off proper sense code. Like it matters? Yea idk... If I get time before then I'll try to get sense packed up but just not a priority currently.

~m8whl on the Always Solid ViperOneM8 Latest

Hypernova mako_hotplug kernel at 2.572 Max ¦ 300 Min ¦ 1.190 Sleep

interactive (Franco tweaked)*

row
[One (M8) Android Development] Gamesoul Master:
No worries dude, Sense will come when it comes, I'll just stay on GPE until then.

As far as my settings, here's the important stuff I've set so far:

above_hispeed_delay = 20000

go_hispeed_load = 95

hispeed_freq = 1728000

min_sample_time = 20000

target_loads = 85 1728000:97

timer_rate = 20000

I set it that way to keep the phone responsive and ready to scale quickly at the lower frequencies, which is where almost all the action is on a phone, while still being responsive at higher frequencies if needed. The main ones I will eventually tweak first (to test) is go_hispeed_load and target_loads.

For the hotplug, all I did was up the all core threshold to 90% and raised unplug frequency to 2265000. Wasn't much to mess with there anyway.

And yeah, I'd be down for helping with testing settings or whatever you need.
[One (M8) Android Development] fen0m:
Hi I'm trying to install the MM gpe kernel on my Verizon HTC running srom jw4.4.0. I've d/l it several times and flashed multiple times and it fails. Last lines of the log are:

cpio: cwkeys not created: newer or same age file exists

cpio: charger not created: newer or same age file exists

11336 blocks

rm: can't remove '/tmp/anykernel/ramdisk/init.elementalx.rc~': No such file or directory

rm: can't remove '/tmp/anykernel/ramdisk/sbin/elementalx.sh~': No such file or directory

about to run program [/sbin/sh] with 3 args

script aborted: called abort()

called abort()

Installer Error (Status 7)
[One (M8) Android Development] MassStash:
What version kernel name

What version twrp

~m8whl on the Always Solid ViperOneM8 Latest

Hypernova mako_hotplug kernel at 2.572 Max ¦ 300 Min ¦ 1.190 Sleep

interactive (Franco tweaked)*

row
[One (M8) Android Development] JohnHorus:
Hey [MENTION=1238555]MassStash[/MENTION]! You might recognize me from the Sprint thread, I posted there by accident as it came up by itself on Google search and the title looked the same from the results. Apologies, I can mark the posts for deletion if you would like!

I found that the init/su.d boot settings problem persisted all over the place with different ROMs and kernels... Quality Google Work, as usual. I since reinstalled Skydragon with Hypernova, and that time the read-ahead started sticking! After like 2 identical installs that did not... headphone gain still does not set on boot, assuming that can be set through init.d. Either way, forget about it. I saw a much more problematic issue that seems like it must be HN-related.

Essentially, the hotplugging seemed to be working correctly (with the first 2 always on, and the 3rd and 4th switching off,) but the first two cores would ALWAYS alternate between minimum and maximum, and when the 3rd and 4th came on, it was straight to max, then back offline. Not only would the first and second constantly switch from min to max, but when one went to minimum, the other would go to maximum, meaning one core was ALWAYS running full throttle. Judging by the battery drain, 50% in 2 hours with screen off, with only some music playing for maybe half an hour, this happened with screen off too.

I don't remember changing ANY CPU settings, but I did install GoldenDroid init.d tweaks. I wouldn't think that would cause this though, it certainly wasn't normal as I definitely didn't see this in the past. I restored the backup I made after installing this setup, and the problem is gone now.

I have a screen recording of it saved somewhere, I can upload it to clarify if you would like.
[One (M8) Android Development] Kristian2018:
Yes please post. And let us know....,?

sent from m8 rocking S.Rom 6.01 sense rom and hypernova kernel

---------- Post added at 11:29 PM ---------- Previous post was at 11:27 PM ----------

Do u mind sharing your setting to test out ....

sent from m8 rocking S.Rom 6.01 sense rom and hypernova kernel
[One (M8) Android Development] MassStash:
THe not chillin at min is by design, it kind of bounces around in prep to ramp up. Tweaking with settings may limit how much the jump and often it is as well, but the way it's set hasn't rendered any ill effects that I have noticed. The init.d stuff kind of died with lolli. THat's why the kernel script isn't an init.d script any longer, and has moved to the ramdisk, which is why it's not edit/saveable, so you have to change settings with an app, dirty flash, or adb pull script, make edits, then push the file. Or copy in recovery to internal, make edits, copy back over in recovery sometimes works as well if you don't wanna use a pc.
[One (M8) Android Development] JohnHorus:
No, it was a serious battery drain issue, it was not by design. One core was always at maximum. 100% of the time. I just reinstalled and they're both sitting at 300 all the time.

I'm not sure about the init.d stuff as I've heard of su.d scripts now in MM too, but I'll try not installing any scripts and see if it goes to 2048 this time.

https://youtu.be/TvEzaN1kyew

double edit: Nope, init.d is still the only way to set my read-ahead to 2048 without using an app to set on boot. If you're doing it in a ramdisk script or w/e, it's not working.
[One (M8) Android Development] Kristian2018:
Well its alittle early to tell but your settings have now given me screen off idle drain at 0% ...... I always had at least 2 to 6% drain according to exkm and it seems alittle snapper ..... Thanks for sharing

sent from m8 rocking S.Rom 6.01 sense rom and hypernova kernel
[One (M8) Android Development] JohnHorus:
Sweep2Sleep Broken

In addition to the above frequency bug, Sweep2Sleep is constantly reset to 0.

I've tested this multiple times and it happens anytime I use Hypernova, with any GPE rom.

It's incredibly annoying, as I far prefer the hotplugging in Hypernova, but I'm pretty sure it's inherent to Hypernova. So I have no idea how I can work around it without losing Hypernova altogether.

I wish I'd just bought a Moto X. Sigh.
[One (M8) Android Development] rakkkar:
So I haven't seen a changelog for the latest version of hypernova and I am wondering what has changed compared to 2.0.1? Just interesting to see what has happened since last flashing 2.0.1 and I enjoy your work a lot.
[One (M8) Android Development] Gamesoul Master:
Let me know if anything changes. I'm still slowly testing changes to see if I can squeeze more battery out of my phone without hurting performance... lol.
[One (M8) Android Development] Kristian2018:
Pretty good so far.... But yea better battery life and running smooth[emoji54] [emoji1] [emoji1] [emoji1]

sent from m8 rocking S.Rom 6.01 sense rom and hypernova kernel
[One (M8) Android Development] D@vIcHoJD:
All very good, good battery life, smooth, no lags with Hypernova 2.0.3 in S. ROM 5.1.0 JW. Thanks a lot MassStashh. Regards.

Enviado desde la Luna con mi HTC One M8
[One (M8) Android Development] MassStash:
Glad to hear things are working, glad to hear you may be getting some more battery life without degrading performance gamesoul! Eh not much different, mainly zip install structure. Think I added or tweaked something and recompiled but can't recall anything super significant.

~m8whl on the Always Solid ViperOneM8 Latest

Hypernova mako_hotplug kernel at 2.572 Max ¦ 300 Min ¦ 1.190 Sleep

interactive (Franco tweaked)*

row
[One (M8) Android Development] MassStash:
What! Never talk about regretful should have got anything other than this sick m8! Haha. If that is getting set back to 0,something isn't flashing/loading correctly bro. Are all the files where they should be? What is out putted in

hypernova_CONF="/system/etc/hypernova.conf"

hypernova_LOGFILE="/data/local/tmp/hypernova.log"

?

~m8whl on the Always Solid ViperOneM8 Latest

Hypernova mako_hotplug kernel at 2.572 Max ¦ 300 Min ¦ 1.190 Sleep

interactive (Franco tweaked)*

row
[One (M8) Android Development] MassStash:
Just tested setting read_ahead_kb to 2048, ticked on boot, and it sets. Have to wait for app to load and change it, so maybe give a second after rent testing to check. Also, Sweep2sleep can be edited in app, set on boot, and should be operational testing different features with the app. If it isn't, then that can be another sign of bad flash something not copied over to device or being read correctly. The contents of those 2 files should help us further troubleshoot this **** ?

~m8whl on the Always Solid ViperOneM8 Latest

Hypernova mako_hotplug kernel at 2.572 Max ¦ 300 Min ¦ 1.190 Sleep

interactive (Franco tweaked)*

row
[One (M8) Android Development] JohnHorus:
Nah, I hate it. I mean, I love the custom work done on it, (and am so grateful! if only I could afford to donate :() if I could get it all working perfectly it would be amazing! But that's no thanks to HTC. Even their bootloader unlock "assistance" is only a bone to get you to tell them you're voiding your warranty for good.

I mentioned over in the EleX thread, I've found that a shell script in skydragon's /sbin folder is probably causing the sweep2sleep problems. I downloaded Lyapota's latest ROM, and HN's sweep2sleep seems to work on that. Which is confusing, because read-ahead and headphone gain are still having the same problems! But those are also with ElementalX. Which is some good news, because I find Hypernova to have just the few things I desired in EleX! Also, sweep2sleep is the most annoying by far.

As I mentioned in the EleX thread, GoldenDroid Init.d scripts are the only way I've been able to GET read-ahead to stick, without using the kernel app. The kernel app absolutely works, there is no problem with it. I apologize if you asked before and I forgot to answer. I don't know how to set headphone gain through init.d(I did try, but it never modified the value I see in the EleX app.)

The sweep2sleep was really frustrating me as I could get it to stick sometimes, but now I'm pretty sure it's just due to skydragon's extra shell script, which I only found when looking for Hypernova's script, so I could check the logs, as you mentioned. The SD thread openly points out shell scripts in /system/su.d/, so I thought those were the extent of them. The shell script in /sbin/ actually *references* the .conf file in /system/su.d/, but in the event it can't find the values it defaults everything to 0. =/

I tried editing it, deleting it in recovery (/sbin is TOTALLY different in recovery,) even putting in a 0 byte placeholder with an identical name was ineffective, /sbin/ is always restored on boot. Because of this, I'll probably just switch over to Lyapota's GPE. It kind of sucks because Skydragon has SQLite and Zipaligns and all that goodness that I don't really understand built in, but GoldenDroid has a zip for flashing those 2, and ultimately, I guess it's time I pull my pants up and learn some more! I asked in the thread if HolyAngel knows how to get rid of it, so I don't think there's a single thing more you can do to help with it than you already have! :highfive:

I'll keep posting in the ElementalX thread about the other issues, see if I can offer any more info! Apologies for taking your time over something that wasn't your fault, I *REALLY* appreciate all your help bro! The other bug I mentioned above, with CPU frequency dancing around at maximum all the time, has not resurfaced since I wiped it away, so as I figured, that must have been corruption of some kind. I hope it didn't damage my CPU! I'm stuck with this thing for at least a year before I can afford anything else.
[One (M8) Android Development] CrazyCypher:
Is there any changelog available for the latest version? :)
[One (M8) Android Development] MassStash:
Redid install zip, love how flar2 has setup his anykernel ramdisk editing scripts. Removed wifi module so this should flash on sense for the time being without breaking wifi. Slimmed down dtb's and updated dtbToolCM in order to lessen zIamge size and thus hopefully never fukin see that repack fail in aroma ever again. That **** pissed me the fuk off so much it's indescribable.... So dt.img is only 4mb now, zIamge I got squeezed down to only 8.4mb now, from like 10, so 12.4mb is siiiiick. Max boot.img partition is like 16 somethin, so we got plenty of room to add **** to kernel or whatever. Like there's time to do that... haha
[One (M8) Android Development] MassStash:
update>?
[One (M8) Android Development] JohnHorus:
I would love to give you one! I'm just getting around to reinstalling my phone at the moment, and trying to get everything set up like I want, at which point I can see if anything persists still (hopefully not!)

I will probably not be able to post for a day or two, as my college-age roommates are partying at all times and leaving messes around to try to force me out. I found a place, but now they refuse to return my last-month's rent so I can move for February, so unfortunately I am being forced to document it all, and that is more urgent, as I'm sure you understand! = )

Once I know how it's going, I'll let you know ASAP! Sorry again to take your time on an error that was not yours.
[One (M8) Android Development] mykenyc:
Is there anything specifically wrong with F2FS? I see a lot of Kernel devs either not supporting it or dropping support.