yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] Stroky:
Hm strange!

I dont have any problems with doze!

I also use Naptime and agressive Doze but even with that i havent notice any problems with delayed messages!
[ONE Original Android Development] andip71:
I reinstalled Whatsapp again. Maybe it is better now.

Time will tell...

Thanks

Andi
[ONE Original Android Development] Pablo.x:
I have delays on notifications everytime I restore Whatsapp with TiBu, so I always reinstall whatsapp from PlayStore and then everything works fine.

You'll see that now you won't have any problem. :)

Enviado desde mi A0001 mediante Tapatalk
[ONE Original Android Development] rshbhghelani:
[MENTION=947981]Lord Boeffla[/MENTION] just asking. will you be releasing a systemless root kernel for cos 13?
[ONE Original Android Development] Manholas:
Upon entering the SuperSU tells me I have to update the binary, I can not.

PROBLEM SOLVED
[ONE Original Android Development] kryshnakishore:
Where is cos 13 for opo? Link is showing blank
[ONE Original Android Development] kryshnakishore:
Still not uploaded cos 13??
[ONE Original Android Development] hellcat50:
You can use the CM13 version, which works just fine for me!
[ONE Original Android Development] Aavion:
No problems here... When my phone sleeps for a few hours, some notifications may arrive ~3-5 minutes later, but that's still acceptable for me...

i'm facing absolutely no issues with cos13, beside some calculation errors in the battery stats (per app usage displayed wrong sometimes).. but it's just cosmetic and turns back to normal after a reboot so just a minor thing ^^

andi? quick question: is it possible to leave the phone unrooted and just pushing the kernel related files back to /data again after your cos13 kernel release? as your config app was the only root app i use and this way i could leave my phone nearly stock while still using your kernel :D just wondering... why shall i have root acces if i don't really need it?
[ONE Original Android Development] andip71:
Yes, you seem to be right.

After I installed if freshly from Play Store it seems to work fine.

Has nothing to do with the kernel.. My kernel cones unrooted, as always.

When you flash SuperSu in recovery it will automatically use systemless root (which I don't like, but currently only this one works).

Hope I can have cm in-built root soon again...

It is not yet released. That is why you also don't see a version number still.

Yes, possible.

Just copy folder /data/.boeffla over again and reboot.

Andi
[ONE Original Android Development] puunakki:
Installed cos13 over my cm13, it was a mistake :( My bluetooth car stereo worked like a champ with cm13 + boeffla kernel, and now with cos13 it's lagging sooo much. Waiting for your cos13 flavoured kernel ;)
[ONE Original Android Development] akash4357:
Did you clean flash or just flash COS13 over CM13? Both are different. You need to clean flash one from another. I have no such bluetooth issues on COS13. It works perfectly fine.
[ONE Original Android Development] kryshnakishore:
Waiting eagarly for cos 13, no i dnt want to go for cm13
[ONE Original Android Development] andip71:
COS13 - first beta kernel

Hi all,

so here we go for a first COS13 beta kernel

(for firmware ZNHOEAS26M).

Note, the kernel has all functionalities of the previous COS12.1.1 kernel. Only one exception - in-built root is not yet available. We have to wait for Cyanogenmod team to release the debuggable kernels first, then we can put that in.

This means, you need to flash SuperSu for the time being to root (SuperSu 2.71 in systemless mode was working for me).

Version

5.0-beta1

11.04.2015

Initial release for COS13.0 (Version ZNHOEAS26M)

All functionalities implemented that are also in the previous COS12.1.1 stable kernel

Exception: Built-in root can not yet enabled, you have to use latest SuperSu beta (e.g. version 2.71 in systemless mode) to gain root

Please bear in mind, you need to flash SuperSu after every kernel flash again (because of systemless mode)

Enjoy

Andi
[ONE Original Android Development] ch-vox:
I have the same issue with WhatsApp, Hangouts or FB Messenger. Their notifications randomly don't play any sound or simply don't appear until I open the app. Maybe a clean install will solve the problem, I don't have the time to test it yet.
[ONE Original Android Development] chenrp:
Hi,

is this kernel compatible with CM13 rom?
[ONE Original Android Development] andip71:
Installing WhatsApp freshly from Play Store did the trick also for me.

It seems, when restoring from a Titanium Backup, the Google push services are not getting initialized properly.

So now it looks pretty good...

You are not serious, or??

What do you think I provide a dedicated CM13 kernel for many months already for??

Mh.

Andi
[ONE Original Android Development] xdavidc:
Why U no Read OP?! LoL
[ONE Original Android Development] hellcat50:
Can I use super su 2.65 stable?

And can I flash this kernel over the CM13 kernel? (i have cos13 + cm13 boeffla)
[ONE Original Android Development] andip71:
You can flash over the cm13 kernel.

But I cannot comment on SuperSu. I only got this rom (with or without Boeffla kernel) running myself with SuperSu 2.71 in systemless mode. Every other version or approach caused a boot loop for me.

Andi
[ONE Original Android Development] thedoctor.gz:
No. Read the latest Lord Boeffla's post. Two posts before yours.

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] inzaghi89:
This is interesting. I've flashed TWRP 3.0.2.0 and SuperSU 2.65. All works well for me. COS13

Or I don't understand you properly, and this SuperSU 2.71 is for Boeffla which I didn't try yet on my OPO.
[ONE Original Android Development] hellcat50:
Yes, I flashed COS and cm13 kernel + super su 2.65 and all worked fine
[ONE Original Android Development] Leicxan:
I am using supersu 2.71 in system mode. No boot loop here. And my kernel is latest cos13 5.0 beta 1.:victory:
[ONE Original Android Development] andip71:
Well, then it was probably only an unlucky coincidence.

Anyways, hope we can enable the in-built root soon, this is a requirement for me to move to COS13 on my daily.

Question to the folks on that:

On COS12.1.1 I could configure whether the notification LED should be triggered or not when in one of the "do not disturb" modes.

I cannot find that anywhere anymore in COS13, which would be a big pity.

Did I just overlook it somewhere?

Thanks

Andi
[ONE Original Android Development] inzaghi89:
I see that this option has been removed. I'm unable to find this too.

Wytapane na Oposie.
[ONE Original Android Development] andip71:
:crying:
[ONE Original Android Development] IronJacob:
Just flashed COS13 version. Thank you for your work!

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] manudroid19:
flashing snapshot's kernel + coppying su binary makes integraated SU to work
[ONE Original Android Development] andip71:
Are you 100% sure? I tried that too.

Can you also remount system partition?

I had trouble with that, but yeah... now I realize it might have been something quite different. Bummer.

I need to try something out quickly :D

Thanks for bringing it up again...

Andi
[ONE Original Android Development] kryshnakishore:
Help me] downloaded both kernal, md5 file for cos13, rebooted to bootloader when i flash zip iy says md5 check error? What to do?
[ONE Original Android Development] andip71:
Download again freshly.

Andi
[ONE Original Android Development] manudroid19:
I didn't try to remount... I just flashed boot.img and then copied /xbin/su from snapshot's zip to my system

What's the manual command to try remount in shell?

toybox mount -o remount,rw /dev/foo /system

Could that work?

Enviado desde mi A0001 mediante Tapatalk
[ONE Original Android Development] andip71:
mount -o remount,rw /system

But you do not need to test anymore, I will release beta2 in some minutes.

Together with a flashable zip which copies the su binaries into the system to root.

It was like I said, I let myself confuse two days ago when it did not work, but the reason was something completely different. Great stuff, now this feature is back again. And even in a very clean way (without CM13 snapshop ramdisk but still with COS13 ramdisk).

Cheers, stay tuned for the update.

Andi
[ONE Original Android Development] andip71:
COS13 kernel update

Hi all,

in this new beta version, the internal CM superuser can be enabled again (just flash kernel and then the enabler script you can find in the kernel download folder).

Version

5.0-beta2

12.04.2015

Support built-in CM superuser again (flash enabler script in recovery, which you can download in the kernel folder on www.boeffla-kernel.de)

Enjoy

Andi
[ONE Original Android Development] manudroid19:
Glad it helped!!

Mount not found :( is it my fault?

Enviado desde mi A0001 mediante Tapatalk
[ONE Original Android Development] andip71:
Well, I guess you installed the full zip and did not do the OTA.

The full zip which is around is faulty!!! It does not link the commands correctly.

I had the same. Then did the update via the official OTA and all worked then.

BTW, Boeffla-Config should also complain like hell in your case after start. As this stuff is checked...

Andi
[ONE Original Android Development] Aavion:
[MENTION=947981]Lord Boeffla[/MENTION]

Andi? Just a quick question...

I wonder, if COS and CM snapshot kernel have excactly the same code base, because I always thought, COS use properitary Qualcomm drivers ect. that aren't available in open source cyanogenmod repos :o Or is it just the Libs that are closed source?

Just asking xD
[ONE Original Android Development] manudroid19:
Full zip is mine, I see... I have made a IMG directly from a upgraded phone using make_ext4fs in twrp... I think now everything is correctly working... Just a few tests and uploading... Any thoughts on it?

Is there any updater script that symlinks correctly in 6.0??

Enviado desde mi A0001 mediante Tapatalk
[ONE Original Android Development] andip71:
No. They don't have the same code base. At least not from kernel side.

Cos rom itself could have proprietary things in, as it is closed source.

But nobody knows exactly.

Andi
[ONE Original Android Development] andip71:
That would be all questions to experienced rom devs.

I am not a rom guy [emoji3]

Andi
[ONE Original Android Development] andip71:
Uff... Cool stuff.

So no need to wait for me from returning from holidays.

Glad about this.

Cheers from the island of Ruegen

Andi
[ONE Original Android Development] andip71:
Is already on my to do list for the next future.

Interesting feature request.

Usually you do not need to reset the kernel settings before flashing a new version. At least not as long as I don't mention specifically.

And if possible I try to migrate data in a reasonable way, hm.

But it is a piece of cake to do it, so I can put it into the next app version, no problem.

Please remind me in case I forget...

Andi
[ONE Original Android Development] magnamentis:
ahhh....

ein bayer auf rügen LOL

have fun
[ONE Original Android Development] Aavion:
genau, viel Spaß und lass dich durch uns hier nicht zu sehr ablenken :D

Gesendet von meinem 1+ One
[ONE Original Android Development] BrunoNRG:
- Is it safe to flash beta 9 on 44s rom?

- In case I want to go back to 44s stock kernel, where can I get it?

- I don't know if this is kernel (happens on both stock and boeffla) related or if it can even be fixed, it's probably a bit OT, but please bear with me. As most of you probably know, all camera apps alternative to the stock camera app have the problem of taking photos with a vertical / horizontal cut if the flash is on, I was hopping that this new 44s firmware update solved that issue, but it didn't... a few days ago I asked about this issue to the FV-5 app developers and this was their answer:

Hi

The problem is produced using the OnePlus One with flash. It seems

that the guys from OnePlus have introduced a bug that affects all

third party camera apps. More information on this page:

https://forums.oneplus.net/threads/proof-that-dual-led-flash-is-broken.141664/

I think they are already working on a solution, and you should get an

updated firmware that will fix the issue. On the meantime, you can

disable the flash to get rid of the problem, or reduce the picture

resolution to 3 MP, where people have reported that the problem is no

longer there.

Best regards

Antonio"

Can this be fixed? Sorry for the very long post
[ONE Original Android Development] Aavion:
1) yes, using it right now.

2) within the ota zip file there's a boot.img. just flash that via fastboot or flashify app.

3) no clue, sorry...

Gesendet von meinem 1+ One
[ONE Original Android Development] BrunoNRG:
Thank you :good:
[ONE Original Android Development] Vonnegut:
If you flashed the OTA, you already have the stock kernel...check it out.
[ONE Original Android Development] BrunoNRG:
Yes, but what I wanted to know is if, after I flashed beta 9 on 44S, for some reason I wanted to go back to the stock kernel, there was some place where I could download it, like there is for the 33R and 38R on boeffla homepage - http://boeffla.df-kunde.de/bacon/stock-kernel/ ;)
[ONE Original Android Development] Vonnegut:
Yeah, inside the OTA...i guess you want a link --> http://builds.cyngn.com/fota/incremental/bacon/cm-bacon-ac1ccf7921-to-5fa8c79c0b-signed.zip
[ONE Original Android Development] BrunoNRG:
I already have it, flashed it and also flashed boeffla beta 9 on it, thanks anyway :)
[ONE Original Android Development] Franc38:
Flashed OTA, the Boeffla beta 9, then super su...

Everything's fine but super su sort of got lost (even if the flash reportedly went OK :confused:) I eventually had to get it from the playstore.

But well, all seems to work just dandy.
[ONE Original Android Development] gianton:
After some hours on b9 and 44s, I lost the sounds of unlocking and notifications.

I had to revert to my nandroid with stock kernel to get them back.
[ONE Original Android Development] andip71:
Most likely not kernel related.

I remember there was a kind of similar issue with sound on cm for the Galaxy s3 when kernel logger was turned off.

In my s3 cm kernels I even removed the kernel logger switch due to that.

Maybe it is linked.

Definitely when I am back I will update the kernel to optimise compatibility with the new rom...

Andi
[ONE Original Android Development] BrunoNRG:
This morning, after I unplugged the battery charger, I notticed I had 3 or 4 email notifications, I pulled down the notifications tab and pressed the emails, notting happened, I tried to open gmail app, and it wouldn't open, tried to open any other app and, even though the screen detected the touch because the icons became highlighted when I touched them, no app would open. The only thing that worked was the power menu and the lock screen. Only after a reboot it went back to normal...

No idea if this is 44s rom or beta 9 kernel related :confused:
[ONE Original Android Development] Franc38:
No problem so far with notifications. I did reboot a few time and let things go for a while to see if anything happened, and still nothing. As Andi says, probably not kernel (nor rom) related.

Tried to see if I have any problem of the sort and no, all seems to be working fine here.

Might I suggest that it's possibly "new gmail" related?

Generally speaking, all seems fine with 44s and beta 9 on my device. I haven't tried giving call yet so maybe the new modem has issues in my area with my operator, but I don't think that'll be the case.

However, I've noticed that the general feel on the device, with exactly the same settings has I had when on 38R, is a bit less smooth. Possibly psychological, though.

For all it's worth, I've run again antutu and still get 42k-43k with zzmove yank battery.... as before. So it really probably is only psychological.
[ONE Original Android Development] BrunoNRG:
You might be correct, but than, how would the new gmail app affect the whole homescreen? Because, as I said, none of the other apps (phone, camera, messages, etc...) would open :confused:
[ONE Original Android Development] Aavion:
And what sources do you use for compiling your cos kernels? or doesn't it matter, if the code base (kernel side) differs between cos and cm? are there any functional or other differences between stock kernel and yours? beside your own additions and the used toolchain for compiling?

Kurz eine Anmerkung auf deutsch: Ich frage nur aus Interesse, weil ich halt gelesen hatte, dass der COS Stock-Kernel proprietäre Qualcomm-Treiber enthalten soll und deshalb "besser" laufen soll (angeblich) als die open-source Variante ^^ Mich interessiert da einfach nur mal deine "Expertenmeinung" :D
[ONE Original Android Development] andip71:
Well, in the kernel repo there is an own branch having the cos sources. This is what I use to compile the cos kernel. As simple as that.

Nothing is proprietary there, it is fully open source.

Andi
[ONE Original Android Development] manudroid19:
So you mean that COS is closed source BUT COS' kernel is opensource???

Or is there any closed sources in official kernel that are not in the base of your kernel???
[ONE Original Android Development] andip71:
Yes, exactly.

Kernel is licensed under gpl licence of the Linux kernel. So a kernel must be open sourced. There can be no closed sources in the kernel.

Closed source parts are therefore moved to rom, libraries, blobs etc.

Andi
[ONE Original Android Development] bloof:
Thanks! Does the internal superuser give full root or are we still waiting for another solution?

Also, does anyone know how to install twrp over cyanogen stock recoverg without a PC available?
[ONE Original Android Development] andip71:
Yes, it does give full root access. Should be the final solution.

If you are rooted already, you can flash the twrp image via flashify or also in Boeffla Config (donation).

Andi
[ONE Original Android Development] kryshnakishore:
Installed 5.0-beta2 kernal, then flashed su script zip, rebooted, su beta 2.71 app is asking for binary update, with reboot its updating binary script but again the message is poping up to update script in app??
[ONE Original Android Development] ch-vox:
thanks for the tip !

and just by curiosity : don't you have battery stats issue ?

I had weird values like 40% of battery usage for Google Play Services and 0% for the screen... :confused:
[ONE Original Android Development] andip71:
Did you uninstall SuperSu completely first? There is an option for complete unroot in the SuperSu app.

Looks like you still have it active.

Never checked that.

I am using my phone, not checking all sort of stats all the time [emoji3]

Andi
[ONE Original Android Development] andip71:
No, looking good so far.
[ONE Original Android Development] bloof:
Excellent for root!

For twrp, getting root is the problem:

1. Flash cyanogen recovery

2. Flash stock COS 12.1.1

3. Boot to recovery, flash COS 13 OTA

4. Get root.... That's the problem... I can't flash supersu or superuser without twrp, but i need root to flash twrp. Catch 22.

I'll have to wait for full flashable zip or a laptop.
[ONE Original Android Development] kryshnakishore:
Completely removed supersu, flashed kernal & script,rebooted, root is working well, if i install supersu beta 2.71 app it is asking for update binary, due i need su 2.71 app anymore?
[ONE Original Android Development] andip71:
No, you should uninstall it. It is obsolete when you use built-in cm root.

Andi
[ONE Original Android Development] kryshnakishore:
Oh thank u, got it..... Finally i am on cos 13 with Boeffla-Kernel, i waited more for boeffla kernal than cos 13 update, dnt know how u are doing all these stuff but for sure i will buy/recommend phones that support boeffla-kernels..... Great, Good job
[ONE Original Android Development] lynxboy:
Just tested out Beta2 with the updater script and while in built root is enabled, I'm now having issues with apps mounting system as R/W. AdAway fails to work as well as System App Uninstaller. Able to uninstall apps using Titanium however. These were working previously with SuperSu and manually updated BusyBox.

Oh and the kernel appears to have fixed the borked battery stats for me!

Regards.
[ONE Original Android Development] manudroid19:
If you have used my full zip, just go to my thread and dirty flash build 3 to fix that problems...

---------- Post added at 12:45 AM ---------- Previous post was at 12:37 AM ----------

Full flashable zip: http://xdaforums.com/showthread.php?t=3355423

(Now without bugs thanks to what [MENTION=947981]Lord Boeffla[/MENTION] said two pages ago)
[ONE Original Android Development] lynxboy:
Thanks.

All sorted on the latest version of the ROM zip.
[ONE Original Android Development] :
Can anyone please share COS 13 stock kernel ?

I flashed boeffla without taking backup of the existing kernel.
[ONE Original Android Development] andip71:
This is available in the stock kernel download on my homepage as well.

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

Andi
[ONE Original Android Development] kryshnakishore:
Do we have any whatsapp or telegram group specific for this kernal??
[ONE Original Android Development] ch-vox:
thank you for having a look at that.

I'll check when I'm back home, for now I've reverted to COS12.1 :p
[ONE Original Android Development] Orphee:
Hi Andi !

Thank you for your COS13 kernel, it works great.

Could you please make a test for me ? it has nothing to do with your kernel but I want to know if it happens only for me...

Make a nandroid backup first :D

I wiped my phone, flashed stock COS12.1.1, flashed COS13 OTA.

It worked fine, then after first boot I began to freeze unneeded apps... and after next reboot, I had a bootloop... I searched what was the frozen app making the bootloop.

A guessed very quicky it was google search box app (velvet.apk it seems)... I had to wipe again to make phone boot again, then with TiBu I completly deleted the app, then wiped again the phone to have a clean phone without google search box... So now it is OK with a clean phone...

But I wanted to know if it happens for someone else... each time I tried to freeze this app, I had a bootloop at next reboot...

Thank you !
[ONE Original Android Development] brath23:
I think it happens to everybody

http://xdaforums.com/oneplus-one/help/cos13-stuck-bootlogo-manual-ota-update-t3356817
[ONE Original Android Development] andip71:
Yes, same for me. I noticed that already in the past on CM13.

Seems there is a dependency on that now...

Andi
[ONE Original Android Development] Orphee:
Ok thank you, as I already did, if the app is completly deleted and then a data wipe is done, there is no more bootloop...

Quite strange...

But it meens all new OTA I'll have to do the trick...
[ONE Original Android Development] kryshnakishore:
Exactly the samething happened to me yestday, even i did the same thing (wipe data, making changes, bootloop, again restore) i got confused alot some thing like 12 times randomly i restored data to figure it (google voice app).......... Yes it happened to me also, i am using without disabling google app now..... Any solution seniors??
[ONE Original Android Development] kryshnakishore:
Thanks for the link finally disabled & its booting.

---------- Post added at 06:00 PM ---------- Previous post was at 05:47 PM ----------

Off topic

Go to Apps>Configure Apps>Default Apps>Assist and voice input and change it to none

G app enabled or disabled make sure it should be none then it won't bootloop
[ONE Original Android Development] DjDiabolik:
Stupid question for a probally stupid answered... i have read this from previous changelog:

Please bear in mind, you need to flash SuperSu after every kernel flash again (because of systemless mode

Every kernel upgrade the root access it's removed and we need to reflash the supersu zip everytime ?

If yes it's possibly to obtain a voice for restart to recovery after a successfully flash ( now after a success flash the opo it's been reboot) ?