yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] DjDiabolik:
Hi boys.... it's very strange but i need to report:

I have installed on my OPO the 3.1 beta12 on my CM12s and sometime when i turn on my phone it's locked on "CYANOGEN" logo:

1) It's appears the 1+ logo and after disappears

2) The logo "CYANOGEN" it's been appears on screen and the animation it's started

3) When all it's normal after about 2 or 3 seconds this logo need to disappears and immediatelly the lock screen it's on screen. But rarely on my case i can reach the lock screen... my OPO remain whit logo on screen and i need to force turn off (remain press down the power button) and usually this happens only one time as ever, at the seconds boot all it's ok and i can use my phone usually and whitout any problems.

I'm not sure the problems it's caused by this kernel because i have this same problems for about two days.... after that disappears and reappers without notice....... i can try to back to stock kernel

but I would need to do extensive testing for days or week, at this point it's possibly to check what's appened on my phone when i obtain this bootfail ??

It's the second time i have reported this same problems here....... and since I follow often releases beta i can't says if a version of the problem is in relation to another....... for example according to changelog of 3.1beta3:

Version 3.1-beta3

12.06.2015

Kernel start script optimized again (apparently was too aggressive for some phones)

it may be that this "script" it's the cause of my problems ??
[ONE Original Android Development] andip71:
All I can say is: I never ever had that behaviour.

Andi
[ONE Original Android Development] andip71:
CM12.1

Hi all

pure maintenance update on the CM12.1 kernel.

Version

4.1-beta19

18.08.2015

Updated with latest 2 official CM kernel commits as of 13.08.15

Ramdisk updated to official CM12.1 version of 18.08.15

Have fun

Andi
[ONE Original Android Development] daringsmart:
I resetted my opo to stock lollipop. Can I flash this using stock recovery I don't have PC to install twrp
[ONE Original Android Development] kalapapa:
Nope that's not possible using stock recovery. What you should do is download flashify and use it to flash twrp And then flash it through twrp
[ONE Original Android Development] DjDiabolik:
You thinks it's no a kernel problems ? we can exclude that 100% is the kernel cause this trouble on my opo ? You have some suggestion ? In addition to the kernel i no use other mod like framework module or similar things........ you thinks it's a software problems ?

*EDIT*

For example... I haven't the slightest idea if you can do it:

it's possibly to disable the CYANOGEN logo (or disabled it or put a empty logo) to read the boot information like bios on a pc ? Or read a bios log when obtain this fail boot ? Only in this mode i can try to find how it's very my problems......

*EDIT 2 only for my purpose :)*

I need to better understand how it works...... under this CYANOGEN logo....... the cm12s it's already boot ? or the boot appened only when logo it's disappears ?

*EDIT 3*

In the pass someone has suggested to me this:

http://xdaforums.com/showpost.php?p=60713503&postcount=4572

I have reboot and deleted this folder 5 seconds ago from TWRP.... at reboot no problems but the main stock cm12s theme it's not been reinstalled and i need to reset it manually ?? I can try anythings for moments but i thinks it's all OT...... tomorrow i try to open a thread on main section and tryed to explain all the situation..... :)
[ONE Original Android Development] bloof:
Do you use themes? Changing/applying themes can lead to that behavior.
[ONE Original Android Development] daringsmart:
[MENTION=1470009]boeff[/MENTION]la is ur site is down I'm I can't get in. Is anyone having kernel link for stock cm12s ?
[ONE Original Android Development] andip71:
Site responding fine here.

Maybe you should try again in a few minutes.

Nevertheless, here a direct link:

http://boeffla.df-kunde.de/bacon/boeffla-kernel-cms/cm12.0s_download/Test/Series 3.x/

Andi
[ONE Original Android Development] rahulrai:
Site is fine. Downloading as I write
[ONE Original Android Development] daringsmart:
Download and gonna flash right away. Thank u lord :beer:
[ONE Original Android Development] DjDiabolik:
Yes... i have tryed in this days to back to stock cm12s theme............ i need some days or weeks or months for know if it's this the problems :) Or i need to wait when this bootfail become very frequent :)
[ONE Original Android Development] bloof:
Switch to "system" theme, reboot to recovery, delete everything in folder data/system/theme

Reboot.

That should clear your themes.

You can then switch to stock (hexo) theme.

Then reboot.

Always reboot/soft reboot after applying a theme. You might get back into a "stuck at boot" situation, then just reboot with hardkeys and if it happens again boot to recovery and delete things in data/system/theme
[ONE Original Android Development] DjDiabolik:
Great suggestion... I have make this:

1 - Preferences -> Themes. Inside it i have reset the Hexo themes marked as customized.

2 - After that i have applied the System theme....

3 - Reboot into recovery and delete the Theme folder...

4 - Reboot to System...

The boot it's been completely whitout problem... At this point whit es file manager i have reached the theme folder and all subdirectory it's be recreated but now all folder it's empty. I thinks simply because now the default theme of lollipop it's been used... Right?

For now i have choose to continue to use the system theme... At the end it's similar than how i customized the hexo theme previously.... Now i need to wait and hope for not obtain any more this stuck at boot situation...

For the moment thanks for all suggestions... And sorry me for this ot :)
[ONE Original Android Development] andip71:
OnePlus Two

Good morning,

you know, I am not giving anything on benchmarks. But as I heard so many rumors (negative ones) about the OnePlus Two being slower by default than the OPO, I decided to run an Antutu.

And all these rumors are truly rubbish, as you can see yourself.

This is OP2 stock, with unlocked bootloader and rooted. No modifications regarding speed, no tweaking, nothing.

So it is around 50% faster than the OPO. And also it just got hand-warm during the test, I could not feel any overheating.

So far I like it, the fingerprint reader is very convenient. Although I am not yet sure whether it was running better before I unlocked the bootloader and rooted the phone. Will verify this, as it does not make lots of sense, but you never know.

The phone is very snappy, reacts to every action very fast. No touchscreen issues, just the home button (which is also the fingerprint reader) could be more sensitive. Ok, this is complaining on high level.

Memory performance is also quite nice, 5.1 GB backup in 81 seconds is not bad. Just "bad" the 64bit OS creates such kind of big backup files.

Now I am waiting for OnePlus to give us kernel sources as my fun is quite spoiled without my own kernel :D

Andi
[ONE Original Android Development] kalapapa:
That's nothing, I'm sure when you add your kernel it'll rise a couple thousands
[ONE Original Android Development] andip71:
Let's see. First we need kernel sources, and of course - as expected - no answer so far by OnePlus on my request.

Andi
[ONE Original Android Development] andip71:
CM12.1 kernel maintenance update

Hi all,

quick maintenance update for the cm12.1 kernel to stay on top of the latest official CM kernel commits.

Version

4.1-beta20

20.08.2015

Updated with latest 8 official CM kernel commits as of 19.08.15

Ramdisk updated to official CM12.1 version of 20.08.15

Enjoy

Andi
[ONE Original Android Development] abhibnl:
Poor oneplus. They don't know they are losing many customers just because boeffla kernel is not avaiable yet! [emoji16] [emoji16]

Sent from OnePlus One
[ONE Original Android Development] thedoctor.gz:
Hi Lord, every time I try to perform a benchmark with AnTuTu my OPO reboots at 22% (CPU integer test).

Here some info:

CM12.1 Nightly 20150819

Boeffla Kernel 4.1 beta 19

Power extreme profile test failed

Power profile test failed

Battery saving profile OK

The ROM is installed as secondary with latest version of MultiRom.

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] andip71:
First you should know - I do not care a sh**t about benchmarks like Antutu :)

See OP, I stated it even there.

However, your phone can most probably not take the overclocking of the two mentioned presets. This is common, and explained in the FAQ on the homepage why.

So, nothing wrong.

Andi
[ONE Original Android Development] thedoctor.gz:
Ok Lord, I understand. It was just a curiosity to push the performance of the phone at maximum with your settings ;)

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] andip71:
No problem. These settings unfortunately cannot work for everyone, due to manufactoring tolerances etc.

I mean, if you are willing to play around, there are many ways. When you overclock, you also can overvolt the overclocking frequencies which makes them more stable. For some that is enough to successfully overclock.

But it requires time and efforts to find the right balance for your phone.

Andi
[ONE Original Android Development] beany>:
Exactly, and the same can be said in the other direction of chasing battery life. We have to spend time and effort to find what works for us and our individual device.

Thank you, as always, for all you do for us.
[ONE Original Android Development] abhibnl:
Just out of curiosity, is the default setting not working fine for you? 2.5Ghz processor, and 5XXMhz GPU, and you still want to overclock? I'm using 19XXMhz step from day 1 on this phone and it's snappy as hell.
[ONE Original Android Development] andip71:
Same for me, I use 1900 always as well...

Andi
[ONE Original Android Development] Han-Droid:
Hey Andi....just fyi.... OxygenOS 2.0.1 is starting to roll out today.

https://forums.oneplus.net/threads/oxygen-os-2-0-1-first-ota-for-oneplus-2-rolls-out-today.345915/
[ONE Original Android Development] andip71:
Aah, thanks for letting me know.

Maybe it makes Aquamail working again, because without that, I cannot use the phone realisticly (yes, Oxygen 2.0 indeed breaks Aquamail app, unbelievable but true)

Andi
[ONE Original Android Development] hp13:
Nice Lord Boeffla. I am still using your 4.4. Stable kernel with touch fixes. I really appreciate for all your hard work and contribution to the XDA forum.

Gives us your feedback for the device :)

Sent from Bacon
[ONE Original Android Development] andip71:
Please also do support me by posting in my thread on the OnePlus boards about releasing the kernel sources for the OnePlus Two.

https://forums.oneplus.net/threads/kernel-source.343335

Thanks for your support

Andi
[ONE Original Android Development] thedoctor.gz:
I don't want to overclock, simply playing with my OPO when I'm at the beach, the babies are sleeping and I'm annoying myself :)

Inviato dal mio A0001 utilizzando Tapatalk

---------- Post added at 08:42 ---------- Previous post was at 07:54 ----------

Just FYI with the default setting is OK ;)

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] andip71:
Good morning guys,

OnePlus Two kernel sources were released.

But now I have to create some disappointment unfortunately - I am starting to a business trip soon. So unfortunately it will have to wait a bit.

Bad timing :)

Andi
[ONE Original Android Development] andip71:
Guys,

I will be going on a business trip to UK again tomorrow morning, coming back by Tuesday night.

So, I will follow the thread, but please expect some delays in my answers.

And... Of course no kernels in the next 3 days.

Cheers

Andi
[ONE Original Android Development] Pablo.x:
Have a good trip Andi,

We will be here waiting for your come back [emoji14]

Sent from my Bacon con huevos. Euphoria's ROM + Boeffla Kernel
[ONE Original Android Development] kantjer:
[MENTION=947981]Lord Boeffla[/MENTION] I'm building your kernel for SlimSaber by replacing boot.img-ramdisk.gz in ramdisk_original with the version extracted from the SlimSaber build.

The kernel seems to work fine but I noticed the following error when building:

>>> apply Boeffla kernel patches and copy files

patching file ramdisk/default.prop
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file ramdisk/default.prop.rej
patching file ramdisk/init.rc
Hunk #1 succeeded at 345 (offset -4 lines).
Hunk #2 succeeded at 651 (offset -4 lines).

The default.prop.rej looks like this

--- default.prop
+++ default.prop
@@ -1,8 +1,8 @@
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
-ro.adb.secure=1
-ro.secure=1
+ro.adb.secure=0
+ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
ro.zygote=zygote32

do you have an idea why this is happening and how to fix it?
[ONE Original Android Development] andip71:
Yes, of course.

The patch file in question modifies the default.prop file, which is part of the ramdisk.

As you replace the ramdisk by the slim one, the patchfile does not work properly anymore 1:1. You would need to adjust the patch file to match the original ramdisk file again to make it not fail.

Hope it is clear enough.

Andi
[ONE Original Android Development] suaverc118:
Hey Lord I saw that the kernel source was put out for the OP2
[ONE Original Android Development] andip71:
Yes, this is true.

However this will take quite good time.

1. I am on a business trip at the moment

2. It is 64bit architecture

3. Different toolchain completely (4.9.x)

4. 3.10.x kernel

Points 2-4 are completely new for me.

So. Exciting and challenging at the same time.

Andi
[ONE Original Android Development] Stroky:
Maybe you will get some new input for our lovely one Device :)
[ONE Original Android Development] andip71:
Maybe.

Hardware is quite different, Linux kernel versions even more (3.4. vs. 3.10).

So, I would not expect too much.

Andi
[ONE Original Android Development] Stroky:
I´m interested in your opinion in terms with the topic of hot plugging.

The Linux Kernel should be an improvement like in the Nexus 6 a i think a all time min. quad core solution will be really great.
[ONE Original Android Development] kantjer:
Your answer is clear but I really don't understand how the .patch files are suppose to work.

I compared the stock and patched default.prop files for both the CM and SlimSaber versions and that made the confusion only bigger.

The only difference I see is that the original CM default.prop contains ro.adb.secure=1, that's removed in the CM patched default.prop.

Loking at the patch file I would expect it to be replaced by ro.adb.secure=0 and also would expect ro.secure=1 to be changed to ro.secure=0, but it isn't.
[ONE Original Android Development] ZaneZam:
maybe your used default.prop has the changes already in, then the patch will fail on that part. just create a new one by making the needed changes manual in the default.prop of your ramdisk and by using diff or git at the end
[ONE Original Android Development] suaverc118:
Good luck and have fun.
[ONE Original Android Development] kantjer:
Thanks, but Its still clear to me what needs to be changed.

Like I mentioned if I compare the CM patched (from released ROM) and unpatched (from source) default.prop versions and look at the patch file In "ramdisk_boeffla/patch" I'm still lost.

I will try to Google my way through it.
[ONE Original Android Development] andip71:
This is basic handling of patch or diff files.

Once you understood it, it is really simple. However, you need to read and understand first.

Maybe that helps to start:

https://en.wikipedia.org/wiki/Diff_utility

Andi
[ONE Original Android Development] kantjer:
Thanks, it's clear now.

Made a new patch file using diff :good:

Edit: this is looking much better

>>> apply Boeffla kernel patches and copy files

patching file ramdisk/default.prop
patching file ramdisk/init.rc
Hunk #1 succeeded at 345 (offset -4 lines).
Hunk #2 succeeded at 651 (offset -4 lines).
[ONE Original Android Development] andip71:
Yep. This looks perfect from the log perspective.

If the resulting file is even having the content you wanted - you are complete.

Andi
[ONE Original Android Development] kantjer:
+

yep default.prop is now changed and containing the following changes.

ro.secure=0

ro.adb.secure=0

Thanks for your patience ;)
[ONE Original Android Development] andip71:
You are welcome.

Just a bit a stretch to watch and answer during the business trip. But finally you made it. Great!

Andi
[ONE Original Android Development] fradbari:
Hi,

for 25r which version is recommended?
[ONE Original Android Development] andip71:
I think I never had a kernel for this super old firmware.

How comes you don't upgrade? [emoji15]

Andi
[ONE Original Android Development] fradbari:
Because the oldest versions are the most battery friendly ever.

So kernel for 30 or 44 version are unusable for 25r?

Inviato dal mio One utilizzando Tapatalk
[ONE Original Android Development] andip71:
You can only try. I think when I got my Opo there was already 30 installed.

But trying is not wrong, take the 1.x series kernel which was made for 30/33r.

If it doesn't work you can always go back to stock again.

Andi
[ONE Original Android Development] fradbari:
I don't find the stock kernel for 25r in your release....

Maybe is correlated to your first modded version [emoji20]

How can I come back to stock working kernel?

Inviato dal mio One utilizzando Tapatalk
[ONE Original Android Development] andip71:
Yes, as said. I never had 25 installed, so I do not have the stock kernel.

You can only go back to the stock kernel by:

- either taking a full nandroid backup of your phone which you then restore (that is the simplest way)

- flash a full 25r rom over again

- find 25r stock kernel somewhere

Andi
[ONE Original Android Development] kalapapa:
When l tried flashing 25r on the weekend I got my efs corrupted so I would be careful
[ONE Original Android Development] andip71:
Ouch... could you recover from it?

Andi
[ONE Original Android Development] kalapapa:
Yah I had a backup of my efs and I tried to restore it but for some reason it had an error and I figured out it was due to having an additional partition from a later version of cm11s. It was the oppostanvbk partition which is not there in the earlier versions of cm11s so it corrupted my efs. I had to update to a newer rom version and then fastboot flash my efs files. In short never try it
[ONE Original Android Development] kurtextrem:
There it goes, COS 12.1 and guess what... our Lord is not at home! :D

I called it last time and I say it again... when you leave germany, they decide to release. Better watch your back, they're watching you!! :D
[ONE Original Android Development] ZaneZam:
plus: one plus 2 sources released, Murphys Law has to be supplemented with this pattern or its really some kind of conspiracy :D

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] andip71:
And even worse... Murphys law managed to apparently get me on business trips also the next two weeks.

So hopefully I can at least do the new cos12.1 kernel.

Op2 Kernel takes anyways much more time, so this is nothing for short-term.

Andi
[ONE Original Android Development] andip71:
Btw... Anyone having a link to a full zip of the new cos12.1 version?

Andi
[ONE Original Android Development] Promez:
Should be this

http://builds.cyngn.com/cyanogen-os...c535cd450/cm-12.1-YOG4PAS1N0-bacon-signed.zip
[ONE Original Android Development] bombadier:
http://www.androidpolice.com/2015/0...ow-available-to-download-for-the-oneplus-one/
[ONE Original Android Development] abhibnl:
For some reasons, it seems CM has pulled the latest update. Same old drama by them.c

Sent from OnePlus One
[ONE Original Android Development] kalapapa:
I downloaded straight from their servers right now

Maybe try again

If your waiting for ota, then stop because it's a waste of time
[ONE Original Android Development] EasyGoingXD:
[MENTION=947981]Lord Boeffla[/MENTION]

Latest Cm12.1 News
[ONE Original Android Development] thedoctor.gz:
http://www.tuttoandroid.net/oneplus...bile-via-ota-per-oneplus-one-download-300167/

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] andip71:
Hi all,

so I am back.

Interesting and foggy situation.

Is the COS12.1 update now officially pulled or not? Need to research for some more info.

Andi
[ONE Original Android Development] abhibnl:
My post that you quoted was sent from cos12.1. So i'm using it already. But the update has been pulled and i guess i have found a serious bug in this update. It's with the gpu frequency. Here are the logs.

Andi, please look at the logs and let me know if you find the reason for this bug.
[ONE Original Android Development] thedoctor.gz:
I've updated the ROM using the zip file by recovery and everything is ok. If you need I can post a screenshot.

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] andip71:
I am sorry and I do not want to sound harsh... but I really have no time to analyze COS bugs in a default installation :)

Have already too much work with my kernels in between my business trips at the moment, cannot spend enough time there.

Andi
[ONE Original Android Development] andip71:
Hi,

can you please point me to the source or app for this information?

Thank you

Andi
[ONE Original Android Development] Promez:
I personally can't find any official statement...:confused:
[ONE Original Android Development] akz1x1:
I can confirm... Cos12.1 is out and is official...

But ota is rolling out slow... (just 2% of the peeps got it... I used the cyanogen ota tracker app from play store).

But I've managed to downlaod and flash the cos12.1.zip file from the cyanogen website...

Everything is working fine... No bugs were noted http://builds.cyngn.com/cyanogen-os...c535cd450/cm-12.1-YOG4PAS1N0-bacon-signed.zip

Downlaod link ⤴

Referred android police �� ⬇ http://www.androidpolice.com/2015/0...ow-available-to-download-for-the-oneplus-one/

Hope you'll make one asap :)

EDIT : There are rumours which says, cyanogen pulled the ota for adding something. But I do think that this is the final one.

EDIT 2: https://play.google.com/store/apps/details?id=com.arjanvlek.cyngnotainfo

Unofficial cyanogen update tracker app.
[ONE Original Android Development] kurtextrem:
They only pulled the ota, not the full rom it seems.
[ONE Original Android Development] andip71:
But seems nobody knows. Hm.

Anyways, my personal schedule is like that with priorities:

1 - CM12s kernel will become stable (no further updates expected)

2 - CM12.1 kernel will become stable (new updates = new betas)

(3 - not for here, but do the same for the Galaxy S5 kernels)

4 - start work on COS12.1 kernel to a first beta

5 - start work on the OnePlus 2 kernel

Andi
[ONE Original Android Development] suaverc118:
Thanks Lord. I'm thinking about flashing the new ROM. Anyways how is the OPT so far?
[ONE Original Android Development] abhibnl:
None offence taken Andi. :)

Let me explain to you what is the chicanery here by Cyanogen to make the UI smooth as many are reporting. Those guys there have played with gpu frequencies and now the gpu is constantly staying at 330MHz. I have changed the governor to msm-adreno and it still stays at 330. I change the governor to simple_ondemand or powersave and the gpu comes down to 200Mhz and bam!! reboot. The default gpu governor is performance now. And we both know, keeping gpu at 330Mhz all the time means, bye bye battery! I would love to know your views about it. Also i'm totally stock. No funny mods, xposed or anything else.