yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] DjDiabolik:
Hi boys&girls........... in this four or five days i'm stay to have some trouble whit my OPO whit cm12s but i'm absolutely no sure if the cause of this trouble it's this fantastic kernel but i try (whit my unslessical english) try to explain the situation to your for obtain some supports from other members.... start from beginning.

I have a CM12s whit last OTA (installed by full wipe) and during normal usage i don't have stability problems or other similar things (whit boeffla 3.0beta5 and latest config app... but i already sayed i'm not sure if the problems it's this kernel and i'm here to ask to you)........... but in this last four and five days whit my OPO i have some problems whit the BOOT of my cm12s:

During the night i turn off my opo... and sometime the next morning when i try to re-turn on my OPO the CM12s never bootup............ it's like still blocked on "Cyanogen" logo (some seconds before normally they disappering for appears the lock screen). It's very strange because it's not a BOOT LOOP but it's like a fail boot......... at this point i need only to maintain pressed the button on/off for about 5 seconds and on screen it's been reappears the 1+ logo and at this point finally the cm12s boot successfully.

At this point i have tryed to reboot my opo........ turn off and re-turn on my opo whitout any problems and apparently i have this problems only after my opo still turned off from lot hours during the night............

Sorry for my english but i don't know if i can explain......... i want to know if it's possibly to read a .log about this fail boot, it's possibly to activate a debugger or logged mode for know what's appened during this trouble boot ?? On my OPO i can only watch the logo cyanogen and nothing append :)

I already sayed... after i force the reboot my opo and my cm12s it's correctly boot and it's perfectly stably (example no spontanius reboot during days at work or similar things).....

You can help me to investigate about this problems ?

Again:

Sorry for my dislessical english and thanks in advance for some support............
[ONE Original Android Development] broke86:
Are you using a CM12 theme?

If yes, try this:

- Boot into recovery

- Open Recovery File manager

- goto Data/system/

- Delete theme folder

- Reboot

I was stuck in a bootloop and this procedure has fixed everything. Or, if you booted up correctly try disabling every custom theme and use the default one.
[ONE Original Android Development] indian84:
Hi,

You can flash stock COS 12 Kernel to check if the problem can be reproduced.
[ONE Original Android Development] andip71:
Major kernel updates !!!

Good evening,

all CM kernels get an update now.

The following kernel are now released as stable and final versions, development for these kernels has hereby ended: CM11s, CM11 and CM12.0.

CM12s and CM12.1 kernels are there as new betas for you.

CM12.1 -- Version

4.0-beta13

13.05.2015

Updated with latest official CM kernel commits as of 12.05.15

Added 3 new governors: pegasusq, lionheart and nightmare

Updated wifi drivers to LA.BF.1.1.1_rb1.20

Updated with latest official CM kernel commits as of 13.05.15

CM12s/COS12 -- Version

3.0-beta6

13.05.2015

Added 3 new governors: pegasusq, lionheart and nightmare

Updated wifi drivers to LA.BF.1.1.1_rb1.20

CM12.0 -- Version

3.3 stable (final)

13.05.2015

Added 3 new governors: pegasusq, lionheart and nightmare

Updated wifi drivers to LA.BF.1.1.1_rb1.20

Fixed scheduler hardlimits for external sd card (not used in OPO, but nevertheless fixed now)

Updated with latest official CM kernel commits as of 13.05.15

CM11s + CM11 -- Version

2.7 stable (final)

13.05.2015

Added 3 new governors: pegasusq, lionheart and nightmare

Updated wifi drivers to LA.BF.1.1.1_rb1.20

Enjoy

Andi
[ONE Original Android Development] DjDiabolik:
Yes.... but i'm not completely sure if it's the kernel cause this problems..... i need to know if exist a mode to debug this spordadic boot fail.....

Yes and not.... because i have the stock theme but i have applied some customization like custom icon downloaded from theme app and custom fonts instead the default stock.... it's great suggestion otherwise.... a boot fail caused by a corrupted theme it's a great suggestion.... i will remember this suggestion :)

Ah.. a question.... the "Theme" folders it's been recreated at boot when i deleted it ? or i need to recreate some file manually before to reboot system from recovery ?
[ONE Original Android Development] broke86:
Yes, every folder in /data/system/theme will be recreated automatically after a normal boot.

In my case it was a custom font from this theme to cause the bootloop! https://play.google.com/store/apps/details?id=com.quantum.impress.material (check the description!)

Sorry if I went OT :)
[ONE Original Android Development] alexbk66:
Auto-Root by kernel possible by request

Hi Andy, I just noticed these comments about root, not sure exactly what it means. I always flash su in TWRP (currently UPDATE-SuperSU-v2.48-BETA), don't have any issues.

Can you please clarify, if I don't flash su, how do I root?

And what issues I might have by using TWRP?
[ONE Original Android Development] mp3deviant721:
What he means is that you should not use TWRP's built in rooting function (like it'll ask you if you want the device rooted if it doesn't detect a su binary on /system). Since you already flash SuperSU, you are fine, just continuing doing what you are doing and you won't have issues.

OnePlus One | Powered by EuphoriaOS x Boeffla
[ONE Original Android Development] aznflawless:
I installed the latest nightly (20150514) and it booted fine. THen I flashed the latest beta 13 cm12.1 kernel and I keep getting system UI has stopped working. Might be because of the kernel not compatible yet :(
[ONE Original Android Development] ethanon:
Using latest beta my games started crashing.
[ONE Original Android Development] davebugyi:
It's a dev thread - please specify which version of the kernel, which ROM and post Crashlog/Catlog/kmsg - and it'll be much easier to find the root cause ;)
[ONE Original Android Development] ogrillion:
I tend to not blame the kernel. I went on a flashing spree today. Flashed the kernel on cm12s, cm12.1, new pa ROM, and oxygen (using the oxygen version of course) no issues at all with crashing in any ROM

Edit: played clash of clans, and downloaded a few games - looking for a good monster collector game- but no crashing in any game
[ONE Original Android Development] ethanon:
Vector crashes every time I try to play
[ONE Original Android Development] lessthanzach:
Yes, you said already. Use an older version then or at least get a logcat.
[ONE Original Android Development] lallolu:
UI is crashing on cm12.1 nightly 14/05/2015

Just to inform you that UI is crashing on cm12.1 nightly 14/05/2015
[ONE Original Android Development] andip71:
Flashing latest SuperSu zip is fine.

Just, when a device is not rooted, TWRP offers to install root itself (it is a swipe you need to do). This should NOT be done, as this installs an outdated root.

Flashing SuperSu by Chainfire is ALWAYS ok :)

ALL: CM team put a change in latest nightly that breaks all not-updated custom kernels (same also on the Galaxy S5 btw).

I already have a new version up and running, will release very soon.

Cannot comment, I am not gaming. Try with stock kernel, then again with Boeffla. See if you have a difference.

However, even if the game crashes with Boeffla and not with stock, do not expect anything please. As stated in the OP, there are two things I do not really care about: benchmarks and gaming.

Andi
[ONE Original Android Development] andip71:
Update to work with CM12.1 nightlly of 14.05.15 again

Hi all,

latest CM12.1 nightlies of 14.05.15 have significant changes in their ramdisk which requires an updated kernel.

So here we go (ONLY use for nightly 14.05.15 or higher !!!):

Version

4.0-beta14

14.05.2015

Fix compatibility with latest CM12.1 nightly of 14.05.15 (ramdisk update)

Enjoy

Andi
[ONE Original Android Development] Berth666:
Hi Andi,

got bootloop with Beta14, Beta12 works.

Rom is BlissPop, newest release

regards,

Stefan
[ONE Original Android Development] beany>:
BlissPop isn't based on 14/05 CM12.1 yet. See post above yours.
[ONE Original Android Development] Setting.Out:
Tested and working on:

Paranoid Android

Paranoid Saberdroid

Heisenberg

Nameless

Vanir

... Thanks. ;)
[ONE Original Android Development] AES256thetic:
Hi Andi,

Your kernels kept my S3 awesome for years and now power my shiny new Oneplus One.

Thanks so much for all your hard work, hope my donation helps you buy some nice beers or something :good:
[ONE Original Android Development] Franc38:
After a few hours I've realized that with beta4, albeit wifi shows as working, it's really not operational. Or super-slow... I'm not sure which. I get the wifi icon showing reception (but not as much as it should given that I had two or three bars just mere inches from my wifi emitter) but the speed was rather poor making me suspect it actually was in H/H+...

So I flashed back the CM wifi firmware and all is back to working order.
[ONE Original Android Development] ahac85:
Hi does this kernel fix the mic issues when making calls, im really considering selling my opo if the mic issue cant be resolved when making calls
[ONE Original Android Development] andip71:
Very interesting report indeed!

I had that also once, but that was long ago when I was still on stock kernel.

That made me believe it could be a rom issue. But not sure, we need to see how this is for more people.

What is the "mic issue"?

The answer is already no, as I have not changed anything in the mic control so far (not knowing there is a "mic issue", can you pls elabourate what you mean?)

Andi
[ONE Original Android Development] ahac85:
Hi when making calls the other party cant hear me properly, voice sounds muffled and tiny like im a couple of feet away from phone, loudspeaker on and all is fine
[ONE Original Android Development] andip71:
Interesting. First time I hear about that.

Ok, I never really use my phone for phone calls, but when I did some testing I did not have this as you described.

Are you sure it is a general issue, are there other reports somewhere?

Or maybe you just got a defective device or it is related to side effects with you specific mobile phone operator?

Very insteresting indeed...

Andi
[ONE Original Android Development] ahac85:
Its a known issue, hear take a look at this

https://forums.oneplus.net/threads/microphone-problem.91832/

https://jira.cyanogenmod.org/plugins/servlet/mobile#issue/BACON-289
[ONE Original Android Development] amg83:
Not sure if it helps, but I recall another kernel for the Nexus 5 that included Intelliactive and if you switched from that governor, it would trigger a reboot. I just experienced it myself while using your app. I had changed the governor and thought I long pressed on Default profile, but must have hit it causing it to apply and revert back to interactive causing a reboot. I'm sending you the debug info in the hopes it helps in some way.
[ONE Original Android Development] andip71:
Hi,

found the hot reboot to be a memory allocation failure in your specific case. Have already answered you via mail as well.

Andi
[ONE Original Android Development] acuicultor:
No wifi issues here with beta4. Good reception and download speed like with stock kernel

sent from my crispy bacon
[ONE Original Android Development] Setting.Out:
No signal issues here... Liquid Smooth rom also works well with your kernel.. ;)
[ONE Original Android Development] jgcaap:
What's your configuration to get such high speed on 4g?
[ONE Original Android Development] Setting.Out:
Luck... lol.. Most of the time my signal is less than impressive.. ;)
[ONE Original Android Development] jgcaap:
Here my operator gives 300mbps of speed but with this phone I was only able to get 50. An iPhone got 240mbps. The test was done in front of me so no lies there
[ONE Original Android Development] Setting.Out:
I'm on Free Mobile in France, but I haven't checked what speed is available, as there is always a signal issue where ever you go in Paris.. I'm usually just happy to see signal as I'm often traveling by metro... ;)
[ONE Original Android Development] Huntation:
Reboot

Had a reboot just now when I tapped on the either the sunlight readability toggle or the other colour toggle in the cyanogen settings under "display". (cant remember which one)

Here's the link to the debug file:

https://drive.google.com/open?id=0B218Z7GI-4F-Wjc4RG5jLWFsakE&authuser=0
[ONE Original Android Development] Dima_2005:
Running your kernel now and working good till now.

Which governor do you suggest using for best battery/performance?
[ONE Original Android Development] andip71:
Will check on Monday again... Weekends are free of kernel stuff, they are dedicated to my family...

Cu again on Monday

Andi
[ONE Original Android Development] Huntation:
Sure man, no problem.

Enjoy your weekend. :)
[ONE Original Android Development] Berth666:
oh ok, thank you :)
[ONE Original Android Development] andip71:
Blisspop needs to get updated first. Beta13 is the best choice for you now.

Andi
[ONE Original Android Development] DjDiabolik:
In my case it's a boot fail..... blocked on cyanogen logo but i can try instead :) Boot loop it's not a different situation ? For Boot Loop i thinks the 1+ logo has been reappered on screen continuously right ? or not ?
[ONE Original Android Development] andip71:
Hm, I saw your posts yesterday and today.

Fortuntely I never had an issue with the device not starting. Unfortunately there is no log to look into, as the kernel is not even loaded (or broke during loading).

My best guess is:

- either there is some firmware incompatibility, so I would personally install factory images to make sure all is in sync (but this means you will lose all data!!)

- or a hardware issue, let's hope it is not

Andi
[ONE Original Android Development] wahuka:
Bootloop beta 14 on CM12.1
[ONE Original Android Development] ZaneZam:
on which cm12.1? beta 14 is only compatible with newest nightly as of 14.05 and upcoming (hopefully *g*)
[ONE Original Android Development] wahuka:
ok, thanks for the advice.:good:

i am on nightly 13
[ONE Original Android Development] fjsferreira:
Touchscreen is fixed with new synaptics driver today! And I already bought a g3! Fml
[ONE Original Android Development] ragnarokx:
I searched this thread but don't see anything about synaptics that's recent. Is this fix in the latest Boeffla kernel? CM12S I hope?
[ONE Original Android Development] ogrillion:
Newest cm12.1 nightly coming tonight. There's unofficial builds floating around with the new kernel for it
[ONE Original Android Development] ragnarokx:
Ah ok. I ask because someone on Reddit asked if that fix could be used in CM12S, and someone replied only if a kernel is built with it, and they said to wait for it to be included in Boeffla. Was this mentioned here?
[ONE Original Android Development] ogrillion:
I haven't seen that yet in this thread. But I believe it is some thing that can be done. Just have to wait until Lord boeffla gets some time. He usually does update fast
[ONE Original Android Development] alexbk66:
Off topic, I'll never use Blisspop again: HAHAHAHA I can't stop laughing at how these fools fell for it!
[ONE Original Android Development] andip71:
Well, I have written that specifically in the change log.

I would really love people would do more careful reading :cyclops:

Good to know, they are officially merged now as I see (early morning in Germany here).

So, looks like I should do new builds for CM12.1 and CM12s today, right? ;)

No, it is not yet in any of my kernels. I just woke up an hour ago and yesterday evening, these new drivers were not yet merged.

Guess, I should do some work in the next 2 hours :)

Andi
[ONE Original Android Development] funkstylez:
Yes!!! :thumbup::p
[ONE Original Android Development] lou2s:
I a using Euphoria 1.1 and there will be no update in the next few weeks. Though the config app says beta 14 is available I will be staying in beta 13...

Sent from my Boeffla-ised Euphoria 1.1 A0001
[ONE Original Android Development] andip71:
That is sad... and would be reason to switch to another rom which gets more frequent updates.

This is why I never use anything else than original CM, to be always up-to-date.

BTW for all, sorry for making you itchy, but new touch drivers really feel good. Think you will get it soon with a new kernel updates, hehe.

Andi
[ONE Original Android Development] lou2s:
I know...I read from one plus forum how nice the new synaspe driver is... but euphoria is alright, the dev [MENTION=4593553]Mahdi786[/MENTION] deserves a 3 weeks vacation, hehe.

Sent from my Boeffla-ised Euphoria 1.1 A0001
[ONE Original Android Development] andip71:
New CM12s and CM12.1 betas

Good morning,

after the new touchscreen driver seems to be really good and fixes the known touchscreen issues for many, I quickly put that into the CM12.1 and CM12s/COS12 kernels for you.

CM12s/COS12 -- Version

3.0-beta7

15.05.2015

Touch screen driver updated to version 14001227 (backported from official CM12.1 kernel branch)

CM12.1 -- Version

4.0-beta15

15.05.2015

Note: Only for CM nightlies of 14.05. or newer (and custom roms having these new changes in)

Touch screen driver updated to version 14001227 (official CM commit)

Updated with latest official CM kernel commits as of 14.05.15

Ramdisk updated to official CM12.1 version of 15.05.15

Enjoy

Andi
[ONE Original Android Development] Orphee:
7SU06399P6487993J

Thank you
[ONE Original Android Development] Hexxer:
Just a question about that "what is what".

Im on Slimkat-Latest 5.02. Cm12 ist EOD. Do i have to use 12s beta7 ? Im a little confused about that.

Thanks
[ONE Original Android Development] Orphee:
12s in ONLY for Cyanogen OS offical stock rom... Not CyanogenMod manually flashed
[ONE Original Android Development] andip71:
Well, honestly spoken: It is a shame Slim still has not made the jump to 12.1. Because this means, there is no updated kernel for you anymore with the new touch drivers.

I now why I only use original CM :)

And no, you cannot use Cm12s kernel on slim, ramdisks and even kernel code is quite different.

But as I am a nice guy, I will compile a last stable CM12 kernel for you with the new drivers.

If these driver are really as good as the rumors say, I might even do the same exceptionally for CM11s and CM11 again.

Hope it is appreciated.

Andi
[ONE Original Android Development] andip71:
CM12 final kernel updated

Hi all,

as an exception (due to the importance of the new touch screen drivers), I gave the already out-of-development kernel CM12.0 another final update:

Version

3.4 stable (final)

15.05.2015

Touch screen driver updated to version 14001227 (backported from official CM12.1 kernel branch)

njoy

Andi
[ONE Original Android Development] Hexxer:
Danke, bist der Beste ;)
[ONE Original Android Development] andip71:
LOL, ... stimmt :)

For the non-German speaking people here:

Hexxer said: "Thank you, you are the best".

And I just replied: "LOL, this is true :)"

(I know I can be cocky sometimes, haha)

Andi
[ONE Original Android Development] Stroky:
Dem schließe ich mich an.

Or

Copy that [emoji2]
[ONE Original Android Development] beany>:
I'm only using 12.1 but think it is great you went back and rebuilt those other variants. :)
[ONE Original Android Development] andip71:
Yeah, wanna create a ****load of work for ZaneZam :)

I am already over in his thread, monitoring when the first chaps ask for his versions :D

Andi
[ONE Original Android Development] davebugyi:
Haha, nice one :D
[ONE Original Android Development] beany>:
Haha. I was going to say that in my post above, but didn't want to "go to far" with my humour.
[ONE Original Android Development] andip71:
Why not? I really like the black british humor :D

Andi
[ONE Original Android Development] beany>:
I would hate someone to not see the joke and get upset, or everybody to jump on me thinking I'm being pushy not humorous.
[ONE Original Android Development] Jeggu:
Boeffla, you really need to slow down. I've been itching to try ZaneZam's unofficial UberTC builds. But you always release a new version before I get to it.
[ONE Original Android Development] andip71:
Jaaaaa. I promise to not provide an update again in the next 3 days unless CM breaks some things again.

As you know, I try to avoid developing during weekends, so chances are good Zane can catch up and you have the chance to try it :)

Andi
[ONE Original Android Development] lou2s:
How abt an update for custom rom which is not up to 15 May 2015 firmware? Just for the new touch driver? :P

Sent from my Boeffla-ised Euphoria 1.1 A0001
[ONE Original Android Development] andip71:
Everyone is encouraged to do that.

I will not do it, sorry. No time to also support custom roms now which I personally never use (yeah, I recommend people to stay on CM directly to always be state of the art, I am not a big fan of custom roms which I tell all that want to hear it)

:)

Andi
[ONE Original Android Development] lou2s:
Just hoping... XD

Sent from my Boeffla-ised Euphoria 1.1 A0001
[ONE Original Android Development] magnamentis:
for those on pre 14th cm based roms i made firmware zip with the new touch firmware included. working well here on blisspop 3.2 12th nightly

to make this available for as many as possible i'll crosspost this in a few threads so please no complaints :) :angel:

NEW LINK AFTER DROPBOX SUSPENSION IS UP: http://magnamentis.com/FW_CM12.1_150514_TOUCH.zip

V
[ONE Original Android Development] lou2s:
Thanks a lot! I see it also comes with a modem, is it the 241 one?

Sent from my Boeffla-ised Euphoria 1.1 A0001
[ONE Original Android Development] andip71:
Interesting... as the firmware is stored in a header file in the kernel code, I wonder how this plays together here... in my opinion, the kernel loads the firmware from the kernel image every time it boots up (without having that checked in depth however).

In short, I am surprised this would lead to the same results? (but I stand corrected if am not 100% knowledgable on it)

Andi
[ONE Original Android Development] ZaneZam:
thx my lord, much appreciated [emoji4]
[ONE Original Android Development] magnamentis:
i put my phone into plain sunshine for 10 minutes which usually rendered it useless ( no unlocking possible anymore ) and now it works. so if this is a placebo i honestly like that kind of LOL. since you're much more tech savvy than i am i tend to believe that it might be placebo but a nice one ;)
[ONE Original Android Development] andip71:
Boeffla Boot Animation !!!

Hi all,

quite late, but better late than never (was too busy in the past 2-3 weeks).

Hardcore fans that like to have a Boeffla-Kernel boot animation can now be happy.

User "mateepunkt" created two boot animations which you can flash in recovery. One for 720p and one for 1080p devices.

On the OPO, I run the 1080p one.

Please find everything in a new download section on the homepage called "Downloads General".

http://www.boeffla-kernel.de/index.php/downloads-general

Sneak peak how it looks like:

https://www.dropbox.com/s/utu72jdozs1kjtn/VID_20150515_123512_rotated.mp4?dl=0

Thanks to mateepunkt for these boot animations, as well as for your recent Galaxy S5 Boeffla-Kernel fan trailer :good::good:

Cheers

Andi
[ONE Original Android Development] magnamentis:
latest modem but not different from the one before, the modem did not change in this firmware as much as i could see in gerrit.

perhaps a more savvy person can tell more.
[ONE Original Android Development] HaTrED_:
Nice one! :good:
[ONE Original Android Development] Mrwargod:
Really good one :good:

Thank you both.