yashsingh1/xdaforums huggingface dataset:
[HTC One S] foeti:
Odyssey rom latest stable version was 2.71...

With 3.00 I got bootloops even with latest bubba....
[HTC One S] atrus5:
I did four commits back on the kernel and no boot loops. Or the commit that fixes SD issue. It's on pac right now.
[HTC One S] phoenixita:
What about pushing these changes to cm? :) anyway rmbq if you still need the 16/09 nighlty was very stabile!
[HTC One S] Rapier:
I was using it with Odyssey latest (3.1) and I got bootloops...once or twice. Now I flashed again using Odysseys's embedded kernel to see what's happening
[HTC One S] $droyd$:
Why push to cm..? Are we getting paid like they are? I say let em sink all cm has is user commits and their getting 7 million ... No contributor will see any of that..
[HTC One S] phoenixita:
My rom is based on CM...should i fork and apply these changes on my own? :)
[HTC One S] nicknc:
Is the kernel you are using different from the provided one in PAC? Bootloops subsided dramatically for me with PAC-rom, but I still got them. The build was whatever the latest was on 29 Sep.
[HTC One S] atrus5:
I build for pac. Something in the list of commits from 3.4.60 to 3.4.62 is causing bootloops. But has been stable for me right now. Crossing fingers that they fixed it or will fix it soon.
[HTC One S] nicknc:
I have no idea how to check into this myself, but perhaps you could. I'm one of the ones that gets just tremendous amounts of bootloops, and got them with the latest nightly 10/02.

However, on a whim, I disabled KSM and disallowed purging of assets, and now have no bootloops (at least not yet). I also changed my i/o scheduler and cpu governor, but don't know why either of those would make a difference.

I know the sensation had a lot of problems with random reboots during low RAM scenarios, and that is what made me try disabling KSM and purging of assets. Could you see if that might be causing a conflict in this latest kernel?

Maybe it's nothing, but just a thought...

-------Update---------

After moving to 10/04, bootloops came back with a vengeance-- along with random reboots (new to me). This was both with the stock 3.4 kernel, and with this 3.4 kernel. Apparently KSM and purging of assets did not have the effect I thought.

I threw in the towel.
[HTC One S] $droyd$:
How is the stability on this kernel.. Reboots? Bootloops?
[HTC One S] nicknc:
I got both reboots and bootloops on CM10.2 with the 3.4 version of this kernel.

Couldn't get CM10.1 to boot with the 3.0 version (just sat on the white HTC screen and bootlooped there).

CM10.1 booted with the 3.4 version, incidentally, but would hang on the CM loading screen with the circle spinning forever if I restored my data. 3.4 kernel doesn't have enough options in it for me to push the issue further, so I just reverted to built-in CM10.1 kernel with CM10.1.

Not complaining about the 3.4 bubba kernel, please don't construe it as that. :)
[HTC One S] rmbq:
probably it's unstable / very unstable with newer versions of cm10.2 but atm i haven't got enough time to work on it
[HTC One S] $droyd$:
No problem I'm just trying to get to the bottom of it all so we can have stable ROMs again.
[HTC One S] crnkoj:
im using it with your rom, and there are occasional endless boots, that ive described in your thread and how to sort of fix those, but im not sure that is kernel related.
[HTC One S] rmbq:
Yo!

i uploaded a new version seems stable to me (no ramdom reboots or bootloop even rebooting and wipe caches)

it's based on 3.4.65 and has got major feature of my old releases.

i restarted my work to be sure i didn't put instabilities with some improvement.

can you test BLN? and write there if it's working or not and wich ROM are you using? thanks

P.S. i'll upload new sources soon
[HTC One S] mannequin:
latest CM 10.2 build here. booted (and manually rebooted later on) with no issues whatsoever.
[HTC One S] el_smurfo:
So, do you know what is causing the reboots (some had logs showing audio issues), or is just updating to 3.4.65 what fixed it? Never used your kernel, but the BLN and possible stability have me very interested.
[HTC One S] Loreane Van Daal:
I'm currently on s-on device, so did boot.img flash via flash image gui, run (as always) awesome kernel cleaner, flashed latest test kernel, and for an hour or so all is smooth. No reboots, no bootloop, BLN is unknown couse screen wasn't off, but i will leave it now. Battery life will evaluate in a day. Using Dark Jelly 4.3. and interactive/fiops, UC 1350/384 Mhz.

Востани Сербие, востани царице
[HTC One S] RichardW1992:
Just downloading the latest CM10.1 nightly along with Gapps and your 2.8 undervolt version of the Kernel to give it a good testing.

100mv for every frequency strikes me as quite a large under volt no? I will see how my phone takes it and report back.

Thanks for all your hard work on this kernel!
[HTC One S] ozzie1p:
Re: [KERNEL][S4][AOSP][4.2.x][17Feb] Bubba Kernel v2.8

I'm on hboot 1.06 and newest cm10.1 nightly and can't get this to boot. Tried flashing from recovery (latest TWRP) and flash image gui.

The boot animation has graphical glitches then just freezes. Is the GPU over clock just to much for my phone? Thanks for any input!
[HTC One S] rootrider:
Did you do your first boot before flashing this kernel and rebooting? If not do so please.

Had no problems on exactly the same configuration (1.06 + cm10.1 nightly + bubba 2.8).
[HTC One S] rmbq:
are you using the undervolt version or the normal one? in 2.8 there isn't GPU OC (this bug will be fix in next version)
[HTC One S] ozzie1p:
Re: [KERNEL][S4][AOSP][4.2.x][17Feb] Bubba Kernel v2.8

Thanks guys. I'm installing after booting and setting everything up and I'm not using the UV one.....maybe I've got one of those temperamental phones.
[HTC One S] rmbq:
have you try to flash this?

if don't try to flash and feedback because i don't know if it works xD
[HTC One S] johnwazhere:
Re: [KERNEL][S4][AOSP][4.2.x][17Feb] Bubba Kernel v2.8

Great, Video Recording works with 720p
[HTC One S] rootrider:
And please do a factory reset from within TWRP before reflashing CM10.1...
[HTC One S] ausaras:
Is call recording built into this kernel?

tks!
[HTC One S] ozzie1p:
Re: [KERNEL][S4][AOSP][4.2.x][17Feb] Bubba Kernel v2.8

Flashed the kernel then the kernel stabilizer and it did boot but still had lots of graphical glitches and once it booted apps were force closing like crazy with a lot of hard resets.
[HTC One S] rmbq:
if you set min freq to 594Mhz is stable?
[HTC One S] RichardW1992:
Undervolted version of 2.8 didnt boot for me, got the graphical glitches on the boot animation then it locked up and stayed that way... I think my phone is very sensitive to voltage levels though, I have suffered similar symptoms just by lowering by 12.5mV before, so a 100mV drop will no doubt upset it.

Rewiped and reflashed CM10.1, and this time the normal 2.8 kernel. Still had the graphical glitches on the boot animation (but only for the first boot). I thought it wasn't going to make it as the screen went black, but at the last minute it said "finishing boot" and she started up. Everything is now running fine, very smooth, lovely job with this kernel!

Noticed some weird issues though:

#1 full wiped and flashed CM10.1 and it had the stock JB wallpaper. After flashing the 2.8 kernel ontop it some how automatically restored my wallpaper that I had set on my ROM previous to CM10.1 ? How did it manage that!?

#2 was changing the governors about between the cores in kernel tuner and it locked up on me once, but haven't managed to replicate this. Although I believe AKtorontos Canuck kernel suffered issues like this at one point when CPU1 wouldn't happily except some of the governors.

For now though all seems fine.

Many thanks!

EDIT:

Just randomly rebooted playing around with frequencies in kernel tuner (not voltages) got the graphical glitches on boot animation again. Upon start up rebooted again, has settled itself down now though.
[HTC One S] ozzie1p:
Re: [KERNEL][S4][AOSP][4.2.x][17Feb] Bubba Kernel v2.8

It usually hard resets before I can get anything open to adjust.
[HTC One S] rootrider:
Again: Does it boot with the stock kernel?
[HTC One S] rmbq:
R: [KERNEL][S4][AOSP][4.2.x][17Feb] Bubba Kernel v2.8

Tomorrow I'll make a test version... It seems a voltage problem
[HTC One S] ozzie1p:
Re: [KERNEL][S4][AOSP][4.2.x][17Feb] Bubba Kernel v2.8

Ah, sorry man. Ya boots up fine with the stock kernel no problems.
[HTC One S] rootrider:
Ok, good. Did you perform a factory reset before flashing? Just to make shure there are no init.d scripts left from other installations or other perform on boot crap.
[HTC One S] ozzie1p:
Re: [KERNEL][S4][AOSP][4.2.x][17Feb] Bubba Kernel v2.8

Ya, factory reset and system 3 times (old habit).
[HTC One S] rootrider:
Thank you. Pretty uncool situation as nobody else confirms this behaviour so far. Running out of ideas atm, sorry.

You could try yesterdays 10.1 experimental, or an older version of this kernel just to see if the problem persists.
[HTC One S] ozzie1p:
Re: [KERNEL][S4][AOSP][4.2.x][17Feb] Bubba Kernel v2.8

I'll try that appreciate the help.
[HTC One S] desmolab:
on 9/10 codefire x rom the system reboot after the Android upgrade app screen.

Inviato dal mio One S con Tapatalk 4
[HTC One S] Rapier:
Kernel boots and worked fine so far with Odyssey 3.2.1 (latest). Using Interactive with BFQ scheduler. No BLN though. I've received several notifications but none triggered the BLN. Dunno if it's due to the Active Display functionality built into ROM or the kernel, but BLN does not work (at least for me)
[HTC One S] Loreane Van Daal:
No BLN here. Tested with BLN control app, too, no BLN mode installed. Peeked in /sys/class/leds/button-backlight/bln and 1 is there but BLN isn't responding.

Востани Сербие, востани царице
[HTC One S] horno46:
This kernel seems to have solved the booting problems. It works great.
[HTC One S] $droyd$:
At the risk of sounding like a dumb a** .. What exactly do you mean BLN.?
[HTC One S] mannequin:
backlight notifications aka touch keys light up etc when there's an active notification.
[HTC One S] Rapier:
Mannequin explained right...when receiving notifications, the button lights pulse every sec or so, being more visible than the tiny led we have for that. That's a kernel feature droyd and rmbq asked us to tell if it's working. Since I didn't know how Active Display interacts with the notifications, I wasn't sure if lack of BLN is due to this or kernel. But since others report it missing on other ROMs as well and I've tested it also with Active Display OFF, it's clearly something with the kernel.

Oh...and maybe the reboots are not gone for good...I had one while charging and trying to send an SMS. But could be only for me.

Sent from nowhere over the air...
[HTC One S] el_smurfo:
boots great on cm10.2 10/9 nightly, but no BLN.
[HTC One S] rmbq:
What ROM are you using? A had got a lot of reboots like this with cfx

EDIT: can someone test BLN with a CM built from 09 Sep to 4 Oct? because with bubba_11Sep_V2 BLN was working, i remember it. at now the BLN code isn't changed but it isn't working on new ROMs. the source code of 09Oct is similar to 11_Sep_V2 so i'm thinking it's ROM related.

i also think if we can get working BLN we can get s2w, the problems seems similiar, our 3 buttons are "isolated" from the rest
[HTC One S] $droyd$:
Hasn't that been moved to hardware tunables as an option in settings by cm. I thought for sure it was now an option.
[HTC One S] rmbq:
no, cm put the lightness control on buttons, 0 is off 255 is light max, but when screen is on
[HTC One S] Rapier:
I've mentioned that in my previous post, sorry I should have specified this when I said about reboots too. I'm using latest Odyssey 3.2.1

Also I found phone dead this morning. It was fully charged last night and when I woke up this morning it was dead, battery at about 11% or so. I could presume it went in an endless bootloop that devoured the battery (I saw somebody else saying something similar), but I can't be 100% sure. I'll keep an eye today on it maybe I could extract also a log. Unfortunately, when it enters into bootloops, I hear at the computer the disconnected sound, don't think I ca extract anything...to be worse now I'm on a laptop with Windows 8 and USB 3.0 ports...and my ADB/fastboot drivers don't work as they should
[HTC One S] rmbq:
it's ok. now i'm using CM 05/10 from yesterday everning with this kernel and no issues, battery from 100 to 63 in 12 hours with wifi and 3g always on and 2 hours of internet surfing with 3g so maybe the problem is that endless bootloop.

the strange thing is it should be stable, I can bet my sources are almost equal to cfX and Odyssey
[HTC One S] Loreane Van Daal:
With DarkJelly 4.3 battery life is good, around 40% down in 12 hours, with wifi/data always on, exchange, twitter, tapatalk, surfing cca 1 hour, cca 20 min talktime. No freezes, restarts or bootloop.

Востани Сербие, востани царице
[HTC One S] rmbq:
good news LoL :)

probably because dark jelly bean is based on CM, cfx and Odyssey are based on aosp

last darkjelly build is 09/12 right? didi you have BLN with bubba_11Sep_V2?
[HTC One S] Loreane Van Daal:
[KERNEL][S4][AOSP][4.3/4.2.x][09Oct Test] Bubba Kernel

Yes, that latest build from 09/12. And I had BLN with bubba_11Sep_V2, but also had random reboots on the same rom, no bootloops just 3-4 reboots daily.

Just did a soff on this device so it will make my life easier, and devices life harder :)
[HTC One S] Rapier:
I can also confirm that BLN was working for the 11 sept version with Odyssey
[HTC One S] rmbq:
thx guys, i've got enough info for make a news test build. step by step we'll get a stable kernel..

also i need some testers for some days, non CM users, if you want test to help me send a PM
[HTC One S] jrior001:
Hey man I just released a kernel build for Evita but I can't get s2w or BLN going there either. Commits all merged in fine, all appears to be in order but i t just dont work. You are not alone in this. I checked the other threads too, I don't think any of the 8960 devices using our 3.4 kernel have working s2w or bln at this point.

Edit...also I reverted the last Linux and caf updates about a week ago in the cfx kernel....that has brought the boot loop complaints to a halt since then. Still have a few random reboots like we have haf since the move to the 3.4 kernel though.
[HTC One S] rmbq:
yo!

I hoped in thy presence for our beloved 8960 kernel!

btw, sorry for not put my sources online but i'm testing and i did't think someone would have looked at it xD

as i said before (test again this morning with 05/10 CM10.2) BLN was working with my 11_Sep_V2.

11_Sep_V2 is based on version 3.4.61 (commit made by CM). 11_Sep_V2 source are on my github, just revert last 4 or 5 commits

On my new sorce i reverted all to 3.4.60 (last caf merge and 3.4.61 3.4.62) and update from 3.4.60 to 3.4.65 cherry-picking from another repo.

reverting caf merge improved stability a lot but BLN is not working... this everning i want try to build a kernel based on 3.4.61 and see if BLN is working

EDIT: i know that feel, i successfully merge s2w in my source but it doesn't work!! i spent a handful of hours lookin' in it... i tried to put printk here and there and reading dmesg, everything seems to be working without problems but screen won't turn on!
[HTC One S] jrior001:
Sounds like we are on the same path then. If you come up with anything awesome regarding bln/s2w or stability stuff let me know and I'll do the same.
[HTC One S] mannequin:
not to be any influence on the development or anything but s2w is a bit of an overkill for this phone, it *always* wakes the phone up in the pocket. the vol wake on the other hand is the most useful and under appreciated.
[HTC One S] rmbq:
of course ;)

if we get s2w i'll add "pocket detection" in order to not wake device when it's in the pocket
[HTC One S] desmolab:
if you are talking about cfx rom i can test for you, i'm on last nighlty atm
[HTC One S] el_smurfo:
Yeah...the BLN is pretty cool, but S2W never has worked properly for me (unless you consider regular "butt dialing" proper)
[HTC One S] c19932:
Dude! I'll do sexual favors for s2w and dt2w
[HTC One S] rmbq:
are you a girl?
[HTC One S] Rapier:
No, he's not...but I'm sure he will turn into one for s2w and dt2w :laugh:

I'm in for testing on Odyssey too...I'll send you a PM also
[HTC One S] rmbq:
[MENTION=2836769]jrior001[/MENTION] BLN fixed, check my last 2 commits here https://github.com/rmbq/ville_ramdisk/commits/3.4-stable

(last commit is the correction for an oversight)

you can continue to adjust button brightness (dunno the function of that line)

now i have to try s2w
[HTC One S] jrior001:
That was quick....seems odd though that all the sense/m7 kernels don't touch that file. Why do we have to change permissions/owners on that and they dont? Just something to think about...will try that later today.
[HTC One S] rmbq:
i don't know man...
[HTC One S] Loreane Van Daal:
Got my first restart and bootloop. My bad, i sticked usb drive to this phone, instead to sense one, granted usb helper permission to load drive. Got restart and bootloop. Powering down and back on resolved issue. So, do not stick usb :) .

Have to change my sig back to "don't follow me, I'm blond" :P

Востани Сербие, востани царице
[HTC One S] Rapier:
Something strange but maybe it's useful to mention...the majority of my reboots were while the phone was connected to USB
[HTC One S] jrior001:
Ditch the app, USB otg should load on its own without any app. Its a little slow to load sometimes though.
[HTC One S] br3ak:
kernel is working great using carbon rom. in times of active display notifications, bln becomes useless for me. my favourite cpu scheduler "intellidemand" is missing. thanks for the update!
[HTC One S] el_smurfo:
Just had pocket reboot. Something I didn't have on CM kernel. Booted without bootloops. Something i did have on CM. Is the working BLN version posted anywhere yet?
[HTC One S] jrior001:
Confirmed fixed mine as well. Now I'm gonna try to fix without removing it, gotta be a permissions issue I think
[HTC One S] Loreane Van Daal:
did that, same thing. Starting to mount usb otg, than freezes, reboots and endless bootloop. So, in my case, usb is not working :confused:

Востани Сербие, востани царице
[HTC One S] rmbq:
I tried to set bln owner to system but nothing
[HTC One S] yooouuri:
Installed the last CM + 9 oct bubba kernel.

Got immediately a bootloop -.-

Added my google account and was downloading some apps..
[HTC One S] Loreane Van Daal:
App download don't have anything with kernel. It's a option that You check - to backup and restore your data/apps with google.

How did You resolved a bootloop?

Востани Сербие, востани царице
[HTC One S] yooouuri:
Power off my phone, and turned it on.

Yes i did check to restore my apps with Google!
[HTC One S] thiasB:
I'm under the same impression with the CM10.2 kernel
[HTC One S] Loreane Van Daal:
thanks for the info. I have flashed native darkjelly kernel, and than latest bubba but without awesome kernel cleaning script. Got bootloop, turned device off, via bootloader, and back on resolved bootloop. Than i tried all again, with awesome , no bootloop. Also, tried with cache wipe x3, got a bootloop. In my case, awesome script is a solution.

Востани Сербие, востани царице
[HTC One S] Loreane Van Daal:
my BLN just started to work. I put device on charger, and next time i look buttons were blinking. Removed from charger, put screen off, and still blinking.

Востани Сербие, востани царице
[HTC One S] rmbq:
with my fix there's this in logcat:

E/lights ( 2932): write_int failed to open /sys/class/leds/button-backlight/currents

don't know if it's a big deal
[HTC One S] Loreane Van Daal:
Just for the record everthing works on latest, 11.10.2013., Dark Jelly and on latest 4.3.1 Carbon rom. Including BLN.

I couldn't boot Dark Jelly with it's kernel, did it with bubba.

Востани Сербие, востани царице
[HTC One S] rmbq:
do you use awesome kernel cleaning script?
[HTC One S] Loreane Van Daal:
Always. Those few steps and a few seconds more make a difference. At least in my case :)

Востани Сербие, востани царице
[HTC One S] jrior001:
What ROM was this on....I suspect that is from the button brightness controls. Can you confirm whether or not that new brightness control works while the fix is in place?
[HTC One S] rmbq:
using cm 10.2, with the fix brightness control doesn't work... but i tried right now to using stock ramdisk and BLN is working..
[HTC One S] jrior001:
you got it working with the normal ramdisk like its supposed to??
[HTC One S] rmbq:
yes, atm with stock ramdisk BLN and brightness control work without problems... the fact is i didn't changed anything :confused::confused:
[HTC One S] jrior001:
I gotta know .... Check this file. I wanna know what permmisions and owner/group it has.

In my tests set to rw-r--r-- and root as owner is the only way I can get bln to work.

Same file that ramdisk edit affects. Stock ramdisk sets it to system-system as owner group
[HTC One S] Twist79:
OCT 09 2013 TEST used in Odyssey Rom RC 3.30 works fine in the newest DarkJelly but it lacks all features which I loved on Vn6
[HTC One S] rmbq:
if you set permission to 0666 (rw-rw-rw) and change the group to "root" it'll work, if you change proprietary and group to root light brightness won't work anymore...

do you know why i've got empty folder under /sys/class/leds in my PA? do you know where the OS creates that files?
[HTC One S] jrior001:
I couldn't get any combination to work with owner/group and permissions that would work for both.

So in my next release for Evita I've got a script ready that will rewrite that line in init.qcom.rc to what I want it to be..(root root instead of system system). It will kill variable brightness but I can't see any way to have both. I don't use any ROM that has it anyways so no big loss.
[HTC One S] rmbq:
new version is up!

tests result:

odyssey: stable (it's the stock kernel ATM)

darkjelly: stable

CM: stable

PA: stable

PAC: staple

cfX: unstable (really don't know why)

take a look atm my ramdisk git
[HTC One S] b0mb:
Thx for the update! ?

The newest version works fine with my odyssey ?

Isn't it possible to get the 184 mhz back to CPU frequencies?
[HTC One S] mannequin:
sick update, rmbq. smooth as butter and and fiops scheduler!
[HTC One S] Rapier:
And BLN is working again :)
[HTC One S] rmbq:
It's possibile but it's useless, trust to me :)
[HTC One S] c19932:
Thanks for the update. I'm not seeing voltage control in kernel tuner
[HTC One S] rmbq:
i forgot it! my apologies
[HTC One S] khan.orak:
Is fast charge present?? I think not.
[HTC One S] mineIsAlreadyTaken:
I'd love to see fast charge as well.

=sent from my OneS= now Free
[HTC One S] horno46:
Thought our Qualcomm chipset already had fast charge .
[HTC One S] rmbq:
this is a xda devDB project, you can write a review if you want and also make feature request ;)
[HTC One S] Phantom Pt. II:
I made a typo in it and they don't let us edit it. :'(

But yea, my request is probably the first expected one. :)
[HTC One S] eXtatic@XDA:
Hi,

just flashed the 14Oct via Flash Image GUI on CM10.2-20130914 and get no Wifi afterwards.

09Oct works great for me.
[HTC One S] Rapier:
Try THIS and see if WiFi works. Least but not last, READ the whole thread, it was answered before to this several times
[HTC One S] 92Lucio92:
Wifi works good for me...but i have a lot of visual bugs while scrolling down and up, my camera isn't working and i can't access to security opotions (cm 10.1.3)

EDIT: forgot to say ---> last 3.4 kernel
[HTC One S] Rapier:
Maybe I'm wrong but as far as I knew, latest 3.4.66 kernel is for Android 4.3 based ROMs...like CM 10.2 not CM 10.1.x... Could this be the reason...
[HTC One S] horno46:
You are spot on.
[HTC One S] 92Lucio92:
So I'm lucky that my phone boot? LoL i have to read sometimes :D

Ty for helping guys
[HTC One S] Twist79:
your Test release used in Odyssey was stable even in Ingress...

14.10.2013 looks stable too on darkjelly but I just installed it....

Now that you made it stable I hope you will re-add all the features. :good:

keep up the good work.
[HTC One S] 92Lucio92:
Ok something must be wrong...why i can't boot with 3.0 kernel? My device is having a bootloop