yashsingh1/xdaforums huggingface dataset:
[HTC One S] AKToronto:
Lol nothing wrong with "trying" to keep it alive. Some people like the new partition layout. Especially those with lots of apps. It's also the layout new devices are using... But yes lack of support makes it hard. That being said koodos to rmbq for doing such a great job with this kernel and providing frequent updates. Can't be thanked enough even if 2.16 (which I use too) makes things harder.
[HTC One S] asinglenoob:
Battery Life?

Hey guys, I'm on CM11 S-Off and I'm interested in this kernel, mainly wondering how battery life is on it compared to stock? Is it necessary to go in and do a bunch of tweaking with schedulers and governors to get better battery life or is it better than the regular CM kernel already?
[HTC One S] rmbq:
in 21 hours i'm at 52% with 1 hour of screen on for internet navigation on 3G
[HTC One S] abonec:
This result is meriot of CM11 or kernel? 21 hour for half battery for HTC one s is great result.
[HTC One S] Aeonxul:
well i think it's something definitely achievable, as for myself, i get similar results, my room is a no reception area for one s(very poor signal strength on this phone unfortunately) so and i am on wifi 24/7. i get at the very least 24 hours, or if i go out and turn off the wifi i will reach 35hrs. According to default battery stats cell standby drains 30% approximately. i tried 2 different radios still no luck with better reception, anyone knows which version below 1.09 gives the best signal reception?
[HTC One S] derkleinebroicher:
I tried latest kernel with latest cm 11 h.boot 2.15. But it's kind of laggy and I get reboots, when streaming videos. I never had this before. Am I the only one?

Gesendet von meinem One S mit Tapatalk
[HTC One S] BloodyScreen:
Also got lots of reboots since the last release. The 18th December version causes quite some trouble. Especially when streaming videos, changing my network mode (switching from wifi to 3g and back etc.) and plugging / unplugging headphones.

Gesendet von meinem One S mit Tapatalk
[HTC One S] rmbq:
i haven't got these problems, all works fine. i watched some videos with stock browser, switched wifi 3g and 2g and used headphone and my phone didn't reboots. on 16 December cm11
[HTC One S] asdfasdfvful:
Absolute noob here...

I am s-on and I am attempting to make a boot.img, but I simply did not understand VTS (despite it being the "noob-friendly" program.

I did, however, read other threads and tried to come up with an alternative. Based on this post, I tried to add a batch script to further simplify the boot.img creation process.

Is anyone willing to try and test it out?

I have never made a .bat before, and I myself am not so clear on the last few steps (what to copy etc..) so if anyone could confirm the bat or add stuff to it that would be awesome.

Thanks!
[HTC One S] Flashalot:
I could help with the bat when I have some time tomorrow afternoon
[HTC One S] asdfasdfvful:
Thanks! And forgive me if I'm wrong, but if I flash things from adb, would it work as it should with an s-off device? In that case, can I simply adb side load the bubba kernel?

---------- Post added at 10:15 PM ---------- Previous post was at 09:56 PM ----------

Additionally, if someone can link me to detailed instructions on how to make a boot.img with VTS, that would be great. I can't find one...
[HTC One S] nicknc:
I'm not getting any reboots at all.

Running the non-QV 18-Dec build on CM11 hboot 2.15. No overclocking or voltage tweaks, using kernel-default governor and i/o.

And I was a guy that used to get tons of reboots back in the bootloop days.

For those of you getting reboots, how are you flashing CM11? Are you using a kernel wipe between CM and bubba? How do you have bubba configured?

Throw up some logcats for rmbq.
[HTC One S] derkleinebroicher:
I tried the same version with default settings. I simply flashed it over my installed rom and wiped cache and dalvik. But maybe a kernel cleaner will help. Can you recommend a certain script?

Gesendet von meinem One S mit Tapatalk
[HTC One S] nicknc:
Try awesome kernel cleaning script. Is what I've used with good results.
[HTC One S] derkleinebroicher:
Same result with this script as well. But I use 1.20 radio. Can this cause the reboots?

Gesendet von meinem One S mit Tapatalk
[HTC One S] nicknc:
Not that I know of-- I'm on 1.20 as well.
[HTC One S] derkleinebroicher:
I made a logcat while streaming a video on youtube. After a short time the video stopped and the phone rebooted. Hopefully someone can get some useful information from this logcat - sadly i myself can't.
[HTC One S] Flashalot:
Can you upload it on devhost or something else media fire not working for my or send the code in a pm
[HTC One S] asdfasdfvful:
Hm. I can still download it without logging in. Try copy
[HTC One S] abracadabra11:
Reboot on 18Dec kernel while trying to hang up phone call with my pebble watch. Don't know if it's a Bluetooth or pebble app driven issue.
[HTC One S] D3LTA:
Can we aspect any updates in near future?
[HTC One S] nicknc:
lmao....do you live in Bedrock?
[HTC One S] horno46:
PMSL
[HTC One S] Irish65:
Running solid for a while now
[HTC One S] rmbq:
new version is up! merry xmas (i'm a little bit in late :P )
[HTC One S] $droyd$:
Hey rmbq I've heard about an in call backlight issue haunting the one s.. My new ROM has it but only on ville mako is fine.. Leads back to kernel related ville bug.. Any thoughts on the issue.
[HTC One S] Rapier:
I hope it isn't "placebo" but can as many of you test this latest Bubba and see if anything changed related to that backlight bug?

I've noticed 2 things:

1. The bug doesn't appear as frequent as before

2. Even if the backlight is not turning on, it's only for a short time...after a couple of seconds, display becomes fully lit. Before, if it was happening, screen was staying dark until the sensor was triggering again the screen on/off seqence

It would be great if it can be tested on as many KitKat ROMs as possible. I've checked on Twisted and Beanstalk and it's definitely an improvement as I can see.

rmbq you did something that could affect this?

Edit: I've made another 3 tests, this time I could catch 2 times in which display remained dark till I waved again across the sensor. But I still have the impression that is better than before when every time display was staying dark. Also seems like the display becomes lit quicker than before
[HTC One S] $droyd$:
Its not a ROM bug I'm using twisted on mako and ville and the bug only affects the ville.. The only difference between the two is the kernel so I know its kernel related.
[HTC One S] Rapier:
I believe you but we have only two kernels...CM11 and Bubba (the kernels from other ROMs are based on CM as I believe). And both are having the same issue. Hopefully someone will find the "cure"
[HTC One S] rmbq:
no i didn't modified anything related to this issue in my last release, i hadn't got time to look into this, i changed CPU and MB of my pc and i reinstalled linux and windows! i also compiled linaro gcc optimized for cortex-a15, i'll upload it tomorrow...

i'll take a look in backlight issue in these days ;)
[HTC One S] Rapier:
Then it is just my imagination :) Well, I was hoping...

Sent from nowhere over the air...
[HTC One S] nicknc:
You got my hopes up, but I'm experiencing no change in backlight behavior, this running the second 25Dec CM11 nightly and 25Dec bubba non-QV
[HTC One S] D3LTA:
Thanks for the effort really appreciated.
[HTC One S] cannondaleV2000:
Lagfree

Could you add lagfree governer to kernel. I find it a great mix of preformance and battery
[HTC One S] D3LTA:
+1 for that

by the way, are you running the QV version of bubba kernel or Non-QV for OC ?
[HTC One S] cannondaleV2000:
Non qv
[HTC One S] cannondaleV2000:
And 1.8ghz oc would be cool to. You can pull it from an old oc kernel
[HTC One S] D3LTA:
Still getting reboots with this kernel, both non qv and qv no oc....stock cm kernel works fine.

:(
[HTC One S] abracadabra11:
Has anyone been able to achieve stability with this kernel and CM10.2? I'm using interactive governor, 50mV undervolt, CPU and GPU overclock. Mostly stable but I get random reboots from time to time. Reboots occur even with none of the above changes using the kernel. On 25nov kernel for 4.3
[HTC One S] Rapier:
Random reboots were haunting 4.3 ROMs and below forever (from the times of 4.2.2 as I recall) . For some it was stable, for some don't. The general perception is that 4.4 proved to be more stable than previous Android versions, if I'm not mistaken. So you're not alone and there is hope...if this warms you somehow.

Sent from nowhere over the air...
[HTC One S] rmbq:
new version is up! should be more stable than 25 dec

i don't like other governor, if you want battery life use ondemand!
[HTC One S] cannondaleV2000:
ok thanks. i am about to build a version too and i saw that you added l2 overclock. and for my own personal use how would i change bus speed too
[HTC One S] rmbq:
in arch/arm/mach-msm/acpuclock-8960.c you can add BUS frequencies here:

static struct msm_bus_paths bw_level_tbl[] __initdata = {
[0] = BW_MBPS(640), /* At least 80 MHz on bus. */
[1] = BW_MBPS(1064), /* At least 133 MHz on bus. */
[2] = BW_MBPS(1600), /* At least 200 MHz on bus. */
[3] = BW_MBPS(2128), /* At least 266 MHz on bus. */
[4] = BW_MBPS(3200), /* At least 400 MHz on bus. */
[5] = BW_MBPS(3600), /* At least 450 MHz on bus. */
[6] = BW_MBPS(3936), /* At least 492 MHz on bus. */
[7] = BW_MBPS(4264), /* At least 533 MHz on bus. */
};

for example flar2 has got this array:

static struct msm_bus_paths bw_level_tbl[] = {
[0] = BW_MBPS(640),
[1] = BW_MBPS(1064),
[2] = BW_MBPS(1600),
[3] = BW_MBPS(2128),
[4] = BW_MBPS(3200),
[5] = BW_MBPS(3600),
[6] = BW_MBPS(3936),
[7] = BW_MBPS(4264),
[8] = BW_MBPS(4532),
};

my BUS is already OC, the stock is this:

static struct msm_bus_paths bw_level_tbl[] __initdata = {
[0] = BW_MBPS(640), /* At least 80 MHz on bus. */
[1] = BW_MBPS(1064), /* At least 133 MHz on bus. */
[2] = BW_MBPS(1600), /* At least 200 MHz on bus. */
[3] = BW_MBPS(2128), /* At least 266 MHz on bus. */
[4] = BW_MBPS(3200), /* At least 400 MHz on bus. */
[5] = BW_MBPS(3600), /* At least 450 MHz on bus. */
[6] = BW_MBPS(3936), /* At least 492 MHz on bus. */
};
[HTC One S] cannondaleV2000:
awesome thank you. and one last question is in your cortex a15 toolchain what file in the bin folder is the one i need to point my make file to because my set up is extract and rename to toolchain and point the compiler to toolchain/bin/arm-eabi so what is the arm eabi-gcc called in your toolchain. which extracts perfectly now by the way
[HTC One S] rmbq:
arm-cortex_a15-linux-gnueabi-

just look inside bin folder
[HTC One S] nicknc:
Working much better than 25Dec for me. Thanks! Don't forget to update the title. :)
[HTC One S] D3LTA:
4 Jan build gives me reboots just after booting, can't even get logcat.... Much more instable than 25 dec build was.... How is this possible?

I am on twistedkat ROM.. Default kernel now no issues.

But i prefer bubba.

Can you help me if i try to get a logcat?
[HTC One S] Rapier:
Which recovery have you used for flashing?
[HTC One S] D3LTA:
openrecovery-twrp-2.6.3.0-ville-selinux
[HTC One S] rmbq:
for kernel the usefull thing is dmesg not logcat, logcat is for the ROM!

BTW, i dunno why, EVERY TIME my kernel is really unstable on droyd's roms (and i never use droyd's roms)
[HTC One S] foeti:
Flashed it on Twisted Rom and boots up fine.

Get constant reboots when I change governor to on-demand.

Even it's quite laggy for me...
[HTC One S] Rapier:
Not always...or not for all. I used 25th dec version with Twisted since you've build it and I got only one reboot (I don't know why). Last night I flashed latest version with CWM (because TWRP was giving me some bad time for backups) and went into bootloops. I've restored from backup, reflashed TWRP and your latest kernel again and it's fine since then. When I got reboots using your kernel previously (and not only on Twisted but also on Beanstalk or Slim), I was watching some videos in the browser. I used intellidemand gov and BFQ or FIOPS scheduler at that time, now I use interactive with ROW...dunno if this could make the difference.

Anyway, considering the vast area of combinations, it's hard to assess why for some is stable and why for some it isn't. Maybe not all governors are stable or maybe the instability occurs only at a certain point or when doing a certain activity, while using a different governor and/or scheduler, or by not doing a particular thing might be stable as a rock
[HTC One S] D3LTA:
If i provide my dmesg file, does it help you fixing the issue?
[HTC One S] Darknites:
He said that's what he wants so go for it.
[HTC One S] asdfasdfvful:
Hm. I'm on the dec 25 QV bubba and I've gotten at least one bootloop a day... and it's with interactive & row
[HTC One S] Rapier:
What do you do at that time when getting reboots? It's replicable?

Sent from nowhere over the air...
[HTC One S] rmbq:
new version is up!

i updated interactive and ondemand governors because they are unstable... let's see now what happens !

and i wrote knock on feature (pocket detection is already integrated)
[HTC One S] phoenixita:
I've flashed it over latest beanstalk and i got reboots! with interactive governor and QV version...It reboot while i was using keyboard app...another thing is that i felt the writing slower...maybe just an impression....Anyway goodjob i'm loving knockon feature.
[HTC One S] cannondaleV2000:
Idk why evedybody get reboots on this kernel and twisted or beanstalk i run twisted and iv only got one reboot on this kernel and that from undervolting to low. I also dont get reboots on my kernel that is bassed off of bubba kernel
[HTC One S] $droyd$:
Its because all one s processors are not created equal.. We learned that long ago lol
[HTC One S] foeti:
On-demand gov now working fine. Still feels a bit laggy compared to stock kernel when scrolling through homescreens. Even writing is a bit laggy as mentioned above....

---------- Post added at 05:37 PM ---------- Previous post was at 05:34 PM ----------

Huge thanks for adding knockon feature... very appreciated!
[HTC One S] cannondaleV2000:
Later il try compileing a version with stock bus and l2 and see if it helps some people then we can go from there with raising features. I might do something like trinity kernel where he released like 3 diffrent ones stock speeds overclocked and extream oc
[HTC One S] rmbq:
knock on is under development, it probably has got some issue if you found something write here
[HTC One S] foeti:
Sometimes it isn't responding or screen turns black again directly after knock on....
[HTC One S] asdfasdfvful:
One time I did absolutely nothing (it was in my pocket). For other times I had some very light games going on like drisk.
[HTC One S] nicknc:
There your problem. Play Landrule instead. No reboots for me.
[HTC One S] Phantom Pt. II:
Flashed it on the latest CM11 nightly. s2w and dt2w stay active even though I switch them off in Trickstermod. And some random reboots, but can't test more because the phone is charging at the moment.

Might just get a Moto G.
[HTC One S] rmbq:
consider this release as experimental, but the s2w issue is strange
[HTC One S] asdfasdfvful:
There's still the times when I did absolutely nothing.. and that is inevitable
[HTC One S] Rapier:
I've flashed latest Bubba from today on Beanstalk 4.4.205 (the one from 4/01 not from 31/12). Interactive governor, ROW scheduler, no OC, no UV. Booted OK, no bootloops, stable so far (no random reboots). S2W deactivated via Kernel Tuner (it has option for this) and it stays deactivated after reboot. D2W and knock-on are both working.

I've noticed some lag sometimes and mostly when I edit one of my Zooper Widgets that has alot of progress bars and so on. I think this could be normal because it might need a lot of processor power for that. Other than that it is ok, normal apps are behaving as they should, open fast, nothing to complain about.

What I am concerned about is battery life for this version due to the knock-on feature and the proximity sensor that's always on
[HTC One S] horno46:
WTF is knock on?
[HTC One S] nicknc:
Double tap the screen to wake.
[HTC One S] Rapier:
I saw it's happening also when long pressing it or you're taking up the phone with 2 fingers from your pocket...well, maybe it's bugged or not finalized. rmbq said it's an experimental/test release
[HTC One S] cannondaleV2000:
Newest build lags really bad for me on slim and twisted
[HTC One S] asdfasdfvful:
Might I ask if anyone can make a zip for flashable boot.img (in recovery?) Something like this

I'd like to keep some rom specific boot.img available for those who need it (especially since twistedkat seems to be unstable with bubba)
[HTC One S] Rapier:
Can some of you make a small test with bubba? Not necessarily with latest version with knock-on feature, the one from 4th of Jan will be ok as well.

Have your governor set to "interactive", no OC, UV, no special settings. Open the dialer/phone and try to dial some numbers...do NOT call that number, just pop up dialpad and dial some digits even if it's not an actual phone number. If everything OK, please switch the governor to "intellidemand" and repeat the dialing test. I'm using Kernel Tuner for this but you can use whatever you want. I get constantly sudden reboots when doing this. If I am on intellidemand governor and try to dial a number on the dialpad, after a few 2-3-4 digits, phone reboots. I've tried multiple times, same result. Switching back to interactive governor, makes the dialing working again.

Note: I am on latest Beanstalk right now, but it'll be interesting to see if it's the same for other ROMs

Thank you
[HTC One S] qayba:
hi everybody! I was looking for the Jan04 version, but I've only found the newer one (Jan05 QV and non-QV) and the older ones...I'm wrong?
[HTC One S] nicknc:
Doesn't seem to affect me.
[HTC One S] Rapier:
It was good if you could specify also the kernel version and ROM version on which you were testing. Maybe it's not with all

Sent from nowhere over the air...
[HTC One S] nicknc:
Lol, sorry.

CM11 5Jan.

Bubba nonqv, 5Jan
[HTC One S] shinodoigt:
There is scroll lag since I installed the last version on CM 11
[HTC One S] nicknc:
Yeah, we've been talking about that for the past few days. Aggravating.
[HTC One S] cannondaleV2000:
Hey don't say stuff like aggravating. The dev know and will try to fix it. Because he does this on his own time
[HTC One S] nicknc:
You're right, there could be some inflection read into that statement that wasn't intended.

I know he'll fix it. It's an aggravating bug, not an aggravating developer. :)

[MENTION=4487443]rmbq[/MENTION], take your time, cm just added more to your workload with the WiFi changes. No rush.
[HTC One S] sandman303:
Hi, so I installed your kernel and its working fine except that wen evr I touch the screen the proximity sensor comes on.

Rom;: cm11 nightly
[HTC One S] rmbq:
Yes i know, it's a bug of knock on. Try to disable it or flash another version
[HTC One S] Rapier:
A bug? I thought this is the way it should work. With knock-on feature, if you have the phone in your pocket, purse, whatever and "something" knocks on it's screen, what's gonna happen? It'll wake up right? I thought that the proximity sensor starts just to sense if the phone is in a pocket and not allowing the display to turn on. And I've tested it...if you cover with a finger the proximity sensor, you can knock as you wish, the phone will stay "dead"...if you don't cover the sensor and knock the display, it'll turn on. Am I missing something? Isn't this the way it should behave?

Or is the proximity sensor turning on also when the device operates and it is awake?...that is when you touch the screen to do something on the phone. If it is this, then yes, could be a bug, proximity sensor shouldn't be on while the device is awake (I'm not on this kernel version that's why I cannot test right away)
[HTC One S] rmbq:
the second you told, the proximity sensor check the pocket when the screen is on! but now i correct a bunch of thing, the phone will wake only on double tap and not on long press, the proximity sensor works only when the device in spleeping etc etc....

i got an issue with 05Jan release and my test releases, sometimes (a lot of times :P) the phone doesn't turn on (it's knock on related) and i have to hard reboot it. do you have this issue? i didn't read anything about it until now or i'm wrong?
[HTC One S] mineIsAlreadyTaken:
Confirmed, same here. Sometimes the screen won't come on with either gestures (DT2W, S2W, knock-on) or power button, have to reboot.
[HTC One S] derkleinebroicher:
+1

Gesendet von meinem One S mit Tapatalk
[HTC One S] rmbq:
in next release there won't be knock on because of this bug, now it's working better and i can always wake up device with power button but i can't release it
[HTC One S] Rapier:
It happened only one time to have the screen not turning on and I had to reboot. But due to the bugs you've mentioned, I didn't kept this version too long on my phone and I flashed back the 4th of Jan version

Sent from nowhere over the air...
[HTC One S] rmbq:
new version is up, without knock on (and its bug of course)

use only on CM 01-06 or newer
[HTC One S] nicknc:
This due to the Wi-Fi changes?
[HTC One S] rmbq:
yes, if you use it on older CM wifi will not work, but it boots
[HTC One S] nicknc:
Thanks man. Much appreciated. Running cm for two days without this kernel wasn't much fun.

Have almost no back light issues on your kernel, but they come roaring back on cm stock kernel.
[HTC One S] cannondaleV2000:
Fixed lag issue!
[HTC One S] mikronac.ns:
which lag issue?
[HTC One S] D3LTA:
shame...

Can't use it on Twistedkat.... rom to old..
[HTC One S] Rapier:
Droyd is preparing a new release, he said that on the thread. As soon as it's out, we'll have bubba again on it. Till then stick to the 4/01 bubba

Sent from nowhere over the air...
[HTC One S] ka_55:
The kernel looks rare stable now. I'm using new version with latest nightly, no reboots no lags so far no problem at all.

Thanks [MENTION=4487443]rmbq[/MENTION]

Sent from my HTC One S
[HTC One S] qayba:
hi guys, when I was using 4.2 or 4.3 CM based roms, I had to flash this wifi fix https://www.dropbox.com/s/rzv7zcrxj7lsan7/WIFI FIX.zip I had found in the cyano thread many months ago to be able to connect to some routers. Using sense roms instead, no problem with no one router... With new wifi changes could I flash this zip again? or is there a way I can implement it in new kernel? I'm not a developer, so I'm not really sure about what this zip modify...any help will be really helpful!
[HTC One S] rmbq:
you can use it also with newer kernel
[HTC One S] qayba:
thanks for your quick answer! I really appreciate it :good: just as info,could I add it to your kernel to flash all together or it may break something?
[HTC One S] rmbq:
flash! i don't think it will break something
[HTC One S] qayba:
thanks again :good:
[HTC One S] asdfasdfvful:
Is it just me or did the bubba boot loops start when opening chrome on twistedkat?

And once again, might I ask if anyone can make a zip for flashable boot.img (in recovery? not including the boot but just the meta-inf and stuff) Something like this

I'd like to keep some rom specific boot.img available for those who need it (especially since twistedkat seems to be unstable with bubba)

I am aware of flashify as previously mentioned, but it obviously cannot do much when I can`t boot into system..
[HTC One S] cannondaleV2000:
im not haveing trouble with bootloops launching chrome on twistedkat. im not running an official bubba but a custom one i built from bubba sourc but no isues
[HTC One S] Rapier:
I use Dolphin Browser because I can have flash working but I'll try Chrome to check

Edit: No issues with chrome beta. Didn't try the regular chrome cause it was last updated somewhere in November. What governor do you use?

Sent from nowhere over the air...