yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] Mecca EL:
Which sentence? There are quite a few in my comment.

I posted a log of the past 12hrs of use on stable version s2 kernel build. It's been running well, but maybe there's some useful information in the log.

---------- Post added at 10:06 PM ---------- Previous post was at 10:05 PM ----------

Of course we are! :)
[ONE Original Android Development] DerRomtester:
Ah ok. Thats why i did not got it. Just post a log when a random reboot happens or the device freezes and you have to shut it off.

You can find it in /sys/fs/pstore/console-ramoops

We need logs from users who notice problems or any weird behavior :)

So here is a new kernel compiled with linaro differences to erorcuns base:

* upstreamed binder from linux mainline kernel

* bfq I/O scheduler

* compiled with linaro gcc 4.9

* made it compatible with more recent toolchains

http://tinyurl.com/hzf4hft
[ONE Original Android Development] Miksel12:
Is bfq default?
[ONE Original Android Development] Mecca EL:
[MENTION=4804871]DerRomtester[/MENTION]

Got a random reboot, and recharge is doing weird again. Other than that, it's running smooth.
[ONE Original Android Development] idprophecy:
I think that it randomly reboots because ramdisk changes aren't applied properly. "replace_string_multiline" is not defined in your anykernel.sh.

Here are my builds, copy it from there if you want. :)

https://mega.nz/#F!rZtQHJDI!dzi7ekhC1uiu_Wx3j2obKQ

(also if is somebody intrested, they are in uber compiled from sources located in linaro's repo like gcc and binutlis).
[ONE Original Android Development] DerRomtester:
thank you my friend i am gonna check that.

edit:

you are right. where have you picked your ramdisk base from? I thought i am using the latest version from osmis.

i need console-ramoops. Fixed next version.

yes
[ONE Original Android Development] idprophecy:
Great. I am on osm0sis one too. replace_string_multiline is not in original one. These 3 lines that changes ramdisk are from [MENTION=4633983]nikhil18[/MENTION]. When I was checking if it changes ramdisk properly the same happened to me, I needed to define that command, so I copied that from somewhere (I don't remember from where).

Here it is rewritten to work with replace_section (it is in the latest osm0sis anykernel):

## 3.10 ramdisk fixes

# fstab

if [ -f fstab.bacon ]; then
fstab="fstab.bacon";
backup_file $fstab;
elif [ -f fstab.qcom ]; then
fstab="fstab.qcom";
backup_file $fstab;
fi;

if [ -n $fstab ]; then
replace_string $fstab "/dev/block/platform/msm_sdcc.1/by-name/userdata /data f2fs nosuid" "/dev/block/platform/msm_sdcc.1/by-name/userdata /data f2fs noatime,nosuid" "/dev/block/platform/msm_sdcc.1/by-name/userdata /data f2fs nosuid";
replace_string $fstab "/dev/block/platform/msm_sdcc.1/by-name/cache /cache f2fs nosuid" "/dev/block/platform/msm_sdcc.1/by-name/cache /cache f2fs noatime,nosuid" "/dev/block/platform/msm_sdcc.1/by-name/cache /cache f2fs nosuid";
fi;

# init.recovery.bacon.rc

if [ -f init.recovery.bacon.rc ]; then
qcomrecovery="init.recovery.bacon.rc";
backup_file $qcomrecovery;
fi;

if [ -n $qcomrecovery ]; then
replace_string $qcomrecovery "cpubw.47" "cpubw.40" "cpubw.47";
fi;

# init.qcom.power.rc

if [ -f init.qcom.power.rc ]; then
qcompower="init.qcom.power.rc";
backup_file $qcompower;
fi;

if [ -n $qcompower ]; then
replace_string $qcompower "cpubw.47" "cpubw.40" "cpubw.47";
fi;

# init.bacon.rc

if [ -f init.bacon.rc ]; then
qcomdevice="init.bacon.rc";
backup_file $qcomdevice;
elif [ -f init.oppo.common.rc ]; then
qcomdevice="init.oppo.common.rc";
backup_file $qcomdevice;
fi;

if [ -n $qcomdevice ]; then
replace_string $qcomdevice "group gps inet" "group gps qcom_oncrpc inet" "group gps inet";
if [[ -z "$(grep -o 'group radio system' $qcomdevice)" && -z "$(grep -o 'service qmuxd /system/bin/qmuxd\n class main\n user root' $qcomdevice)" ]]; then
replace_section $qcomdevice "service netmgrd /system/bin/netmgrd" "group radio" "service netmgrd /system/bin/netmgrd\n class main\n user root\n group radio system";
replace_section $qcomdevice "service qmuxd /system/bin/qmuxd" "user radio" "service qmuxd /system/bin/qmuxd\n class main\n user root";
fi;
fi;

## 3.10 ramdisk fixes

Also I will update builds are online with this included.

https://mega.nz/#F!rZtQHJDI!dzi7ekhC1uiu_Wx3j2obKQ

(as usual compiled in stock gcc 4.8 and in few versions of uber (uses binder from torvalds linux repo))

EDIT: Or not. I just realized that it won't work on second time.

EDIT2: After a lot of edits of this reply, this should work without adding anything to LATEST (only with latest, because it contains updated replace_section) osm0sis anykernel script. At least you still need to check if it is updated, but it is still faster to check osm0sis repo than find replace_string_multiline.
[ONE Original Android Development] Mecca EL:
[MENTION=4804871]DerRomtester[/MENTION] [MENTION=4511190]idprophecy[/MENTION]

You guys are awesome. Testing the latest 3.10-bacon-uber-4.9-aa37266-20160705-141713-optimized-test.zip

Will report my findings.
[ONE Original Android Development] DerRomtester:
Really appreciate your help my friend. Btw where can i find your github ? Can you link it please with your profile? :)
[ONE Original Android Development] idprophecy:
Glad to help you. Here is my github. Nothing in there, just anykernel I uploaded few minutes ago.
[ONE Original Android Development] Blackscorpion3:
Random reboot.
[ONE Original Android Development] nikhil18:
Bro you need to upload sys/fs/pstore/ramoops file because dmesg is useless in this case
[ONE Original Android Development] DerRomtester:
I just thought you share your source with us :) I am interested in the binder changes you have made.

Edit:

compiled a new version for some of you guys:

differences to erorcuns kernel:

* compiled with DespairFactors Linaro GCC 5.4.1 toolchain

* upstreamed binder with linux stable kernel to support different toolchains

* added BFQ I/O scheduler

* fixed some compilation warnings caused by gcc 5

* fixed my mistake i have did with anykernel ramdisk all credits go to [MENTION=4511190]idprophecy[/MENTION] --> reboots should be gone

What is the binder ipc driver?

Binder is used in Android for both communication between processes, and remote method invocation. This means one Android process can call a method/routine in another Android process, using Binder to identify, invoke and pass arguments between said processes.

necessary for new binder so upstreamed it:

*upstream sched/prio: sched: Move the priority specific bits into a new header file

*sched: Expose some macros related to priority

*sched: Implement task_nice() as static inline function

*sched/prio: Use DEFAULT_PRIO to define NICE_TO_PRIO() and PRIO_TO_NICE()

*sched/prio: Add 3 macros of MAX_NICE, MIN_NICE and NICE_WIDTH in prio.h

*sched: Consolidate open coded implementations of nice level frobbinginto nice_to_rlimit() and rlimit_to_nice()

*and update binder for rlmit_to_nice

*sched: Implement task_nice as static inline function
[ONE Original Android Development] TorchaOne:
Got reboot during vellamo multi core run.

http://pastebin.com/LJryCECW
[ONE Original Android Development] DerRomtester:
Thx for reporting. Seems like i ****ed up binder.

Wait is it a beta feature of the app?
[ONE Original Android Development] Blackscorpion3:
I havent had any issues with your new compile.
[ONE Original Android Development] Mecca EL:
Had my device freeze while screen on. And the recharging issue is slightly back.
[ONE Original Android Development] DerRomtester:
Please post console-ramoops. There is nothing useful in the dmesg.
[ONE Original Android Development] Hingbong:
View attachment 3805888
[ONE Original Android Development] DerRomtester:
removed my build. I need to check the logs at first. Thanks guys. But sometimes i appreciate more info.

e.g. what were you currently doing ?

have you tweaked any settings ?

have you flashed it over a previous kernel ?

which rome are you running ? (please use cm nightlys)

are you running xposed ?
[ONE Original Android Development] Mecca EL:
There wasn't any log showing up in the ps folder. I'll make another attempt
[ONE Original Android Development] Blackscorpion3:
Random reboot
[ONE Original Android Development] idprophecy:
Updated anykernel builds in my mega folder (use them just for testing purposes).

Compiled using UBERIZED-LINARO (gcc, binutils from linaro's repository). Also I've added bfq and tried to apply binder changes again.
[ONE Original Android Development] Blackscorpion3:
Will give these a try, as I'm still getting errors on building, I'll hit you up tomorrow about them.
[ONE Original Android Development] pankspoo:
Using u r built from 3 days, no problem at all no reboots else.

I doesn't tweaked kernel any more! As it is. Working good.
[ONE Original Android Development] Pablo.x:
Same here, anyway to solve this?

Thanks in advance..

Enviado desde mi OnePlus One.
[ONE Original Android Development] Mecca EL:
Had three random reboots today, on your latest build. Other than that, it's running well.
[ONE Original Android Development] Leicxan:
No, even on erorcun's latest kernel build. Waiting for his update.
[ONE Original Android Development] hawktalon:
Used your build which you taken down. 6.0 version for a few days. Randomly freezes then reboots. Reboots never occurred when sleep. No ramoops generated tho. What can I get you?

1. It's random, anything from taking picture to Spotify. Nothing in particular seems to trigger it.

2. No tweaks

3. Previous kernel was errorcun's 3rd July build

4. Latest CM nightly on the day you released the builds.

5. No idea what that is so, no.
[ONE Original Android Development] DerRomtester:
I think something was wrong with my binder upstream changes so i removed my build.

Also i think there is memory leak in the camera driver. Because my reboots do happen when something is open that needs the camera. Pokemon go, Snapchat, Normal Camera. But i dont know i need to investigate that first. Currently school is my main priority so i dont have much time on these days.
[ONE Original Android Development] Mecca EL:
[MENTION=4511190]idprophecy[/MENTION] [MENTION=4898631]erorcun[/MENTION] [MENTION=4804871]DerRomtester[/MENTION]

Just my observation, but I think I've figured out why this kernel freezes and random reboots.

.If you have 20+ apps open, the memory gets taxed and throws a few Fatalities, which I've noticed in the event logs. But if I can recover fast enough, from a slow down or impending crash, and close some background apps, my phone works find.

I'm using [MENTION=4511190]idprophecy[/MENTION] last build, the 6xx version. OPO. CM13 nightly, xposed not running, busybox, etc.
[ONE Original Android Development] idprophecy:
I haven't regarded any reboot yet. I don't have many apps opened. So you might be right, going to try to stress memory somehow.

EDIT: It is random. It didn't crashed when I was "filling ram".
[ONE Original Android Development] natheux:
[MENTION=4511190]idprophecy[/MENTION] have you compiled your latest version (1407) with the omnirom camera fix ? Because I read somewhere that you need a different command or something like that when you build this kernel for omni. But I didn't understand clearly

Thank you in advance
[ONE Original Android Development] idprophecy:
No, there aren't even CAF drivers enabled. It doesn't work properly.
[ONE Original Android Development] DarKAngel1234:
Erorcun what is going on with this kernel, any word as of late.?
[ONE Original Android Development] DarKAngel1234:
This project seems to be dead.
[ONE Original Android Development] solar666:
Sometimes people are busy with other things and can't even tell it to us here.

Maybe even due to the late ongoings in Turkey he cannot respond ... Who knows.

But keep calm and wait ....
[ONE Original Android Development] DarKAngel1234:
Any more updated builds idprophecy?
[ONE Original Android Development] idprophecy:
Kernel hasn't been updated for month so it is not necessary.
[ONE Original Android Development] DarKAngel1234:
OK makes sense.
[ONE Original Android Development] mucinch:
Let's hope Erorcun comes back and resumes his awesome work soon :)
[ONE Original Android Development] DarKAngel1234:
Yes because, I have seen what this awesome kernel is capable of, and it is awesome, needs still quite a bit of tweaking, from a battery drain perspective but it should get there. Let's hope.
[ONE Original Android Development] Mecca EL:
[MENTION=4511190]idprophecy[/MENTION]

Surprisingly, the last kernel you compiled has been running really well on the past weeks nightly. On a reboot, after a nightly update, your kernel keeps my phone as cool as if the screen was off, during the apps update process - and I have 190 apps.

I don't know your skill level, but would it be possible to add elements of the latest kernel updates to the 3.10 kernel? I'm using ZaneZam's boeffla variant u541, and my phone just doesn't feel as good as your last build.

3.10 has it's moments, but it's still ultra-responsive and functional.

Thanks!
[ONE Original Android Development] idprophecy:
Thank you. I don't know if I understood you properly, but you might find your answer here. I am just able to add few features like i/o schedulers or governors, optimize it and sync it with erorcun's source. When there will be an update, I'll try to make a build immediately or just make some with updated toolchain (Also I will use stock binder with reverts to support ubertc, not with one from mainline kernel). :)
[ONE Original Android Development] Mecca EL:
Whatever magic you work can at least keep this thread alive. Features would be awesome, since at it's current state, what you've compiled is working very well. Thanks for responding!
[ONE Original Android Development] Mecca EL:
For those interested, idprophecy updated his version of the 3.10 kernel build. I've been running it for about 4 hours now, over CM13's 8-20 nightly. Everything is smooth and fast. :good:
[ONE Original Android Development] kalapapa:
Changelog?

Did he add more CPU governors and such
[ONE Original Android Development] Mecca EL:
No, I don't think the kernel development is at that point yet. Just updated tool chains
[ONE Original Android Development] evronetwork:
I'm impressed with this, so can you flash this with cm(e.g. cm13) roms? Any known bugs?

CMOS13.1.1(official rom) should be incompatible right?
[ONE Original Android Development] erorcun:
Yes.

Guys, I'm back. I will prepare the environment as soon as possible in this PC and will continue to develop it.

I've began making my custom kernel also but I don't when I will finish it.
[ONE Original Android Development] f41lbl0g:
Great to have you back!
[ONE Original Android Development] DarKAngel1234:
That is awesome news, to here you are back.
[ONE Original Android Development] Blackscorpion3:
Great to see you back. Can't wait to see what goodness you have up your sleeve for us.

---------- Post added at 06:04 AM ---------- Previous post was at 06:03 AM ----------

Yes this is done with anykernel so it should work with cos13
[ONE Original Android Development] evronetwork:
I guess I can try it and see how it goes :p

To be honest I didn't believe that someone would deliver this kernel, glad I was wrong

-------------------------

EDIT:

COS 13.1.1-ZNH2KAS2X1-bacon gets you into bootloop with this kernel :( ..oh well, maybe in the future it will work

EDIT2: Lightning Kernel v5 seems to work for some reason, currenty using it(same kernel but it works) :P
[ONE Original Android Development] erorcun:
Hey, there is a new version :P This time in anykernel, so it works with COS.

Battery driver updated with latest OP3 one, synced with CM commits, there is a fix in binder and improvements in gpu driver.

Also I can confirm it works in enforced selinux, atleast with anykernel. But I will give anykernel link this time anyhow.

http://www.mediafire.com/download/6j5xw1j1lel1tra/260816kernel310.zip

I'm testing it only for a hour, so there can be reboots, I don't know.
[ONE Original Android Development] idprophecy:
Glad to see new changes. Gonna give that a try if it works in another toolchains! :P

EDIT:

Doesn't work. It is still necessary to solve it by reverting of those 3 commits.

Also I will make some builds. It's going to be Builds are up in my mega folder and compiled in uberized-linaro with small optimizations as usually.

EDIT2:

So it was just one commit to revert. Also I have rebased my repo and I am compiling final builds of today. First builds that I pushed today are pretty bad. So if somebody wants to use mine, take final builds. Enjoy! :)
[ONE Original Android Development] KenjiHannya:
Booted on Darkobas ROM 2016.08.16 build

WiFi and Data work

Câmera dont work
[ONE Original Android Development] Renosh:
Darkobas uses color OS blobs so the camera won't work. You can try jgcaap color kernel, Boeffla cafcam (Zanezam) or lightning color. Nothing else will work
[ONE Original Android Development] iRhyiku:
Seems to work great on BrokenOS!

Will keep it running tonight in work to see if it's fine. thanks :)
[ONE Original Android Development] KenjiHannya:
Vanir ROM

WiFi and Data Work

Câmera work
[ONE Original Android Development] KenjiHannya:
Tipsy ROM

WiFi and Data work

Câmera dint work
[ONE Original Android Development] KenjiHannya:
Tnx for feedback

I testing with some ROMs

Lets ser

Vanir work good
[ONE Original Android Development] Renosh:
Cool

It's actually pretty simple though

Any ROM with CM camera blobs will work

ROMs with Sultan CAF or color OS blobs won't have a functional camera or may not boot at all.

Happy Flashing ?
[ONE Original Android Development] KenjiHannya:
Nice

Look your CPU 4. Here dont sleep.

Its normal?
[ONE Original Android Development] erorcun:
2 cpus are always online if screen is on, it's normal behaviour.
[ONE Original Android Development] erorcun:
Today's kernel with CAF camera driver: http://www.mediafire.com/download/b9qp8d1axq9g2nn/260816kernel310caf.zip

As some of you guys can remember, focusing with CAF camera driver on my kernel was broken.

I tried to fix it, hope it's ok now :/
[ONE Original Android Development] f41lbl0g:
I flashed this and my touchscreen stopped working for some reason. Will try reflashing.

EDIT: Touchscreen working now but camera not working on CandySix rom (with CAF camera). Is it working for anyone else? (Perhaps a fault on my end)
[ONE Original Android Development] erorcun:
I may have broken camera completely =D thanks for testing.
[ONE Original Android Development] 69gm:
Gonna try again? I'll test on Sultan once you think you got it working...
[ONE Original Android Development] erorcun:
Sure I'll try to fix it in a week but not today.
[ONE Original Android Development] KenjiHannya:
Tnx ;)
[ONE Original Android Development] 69gm:
Of course! Haha. Didn't expect anything soon. Just wondering if you wanted to have another go at it. Hope you got it figured out. :good:
[ONE Original Android Development] LLStarks:
Is there anything in particular preventing this kernel from being upstreamed?

There's precedence.

The 3.4 d2lte kernel was upstreamed when the official firmware was still only 3.0. It was only months later with the Kitkat firmware did the device officially receive 3.4, which was surprising by in and of itself.
[ONE Original Android Development] guidoido004:
Stability?

Enviado de meu A0001 usando Tapatalk
[ONE Original Android Development] erorcun:
There are some weak points on my English,

What did you mean by upstreaming?
[ONE Original Android Development] TorchaOne:
Hip, running ok. Got only one reboot: watching youtube and turning to landscape mode and at the same time the 15% battery saving was about to happen -> reboot :) Multicore as performance vise is way worse than stock kernel. So little tuning would be nice :) governors and stuff.
[ONE Original Android Development] erorcun:
Wish you have had some log.

I won't add any governor etc. since I'm trying to keep it close to stock, thanks.
[ONE Original Android Development] TorchaOne:
Its ok not to add.

old log, where are the logs? kmesg was empty, so was old_kmesg.
[ONE Original Android Development] erorcun:
sys/fs/pstore/console_ramoops
[ONE Original Android Development] TorchaOne:
I already checked it, it started

[ 0.000000] Booting Linux on physical CPU 0

[ 0.000000] Initializing cgroup subsys cpu

[ 0.000000] Linux version 3.4.112-cyanogenmod (tugapower@tugapower-G751JY) (gcc version 4.9.x-google 20140827 (prerelease) (GCC) ) #1 SMP PREEMPT Sun Jun 5 21:16:32 CEST 2016

So I think this time it has not been written at all. But if you want to look:

https://drive.google.com/open?id=0Bx5Ipn9gRusdR016N01LRmZpTnM
[ONE Original Android Development] erorcun:
Yeah it's not related :/ thanks anyway.

At least I found some other reboot reason just happened to me and I will go over it.
[ONE Original Android Development] Matthew_333:
When you grab logs make sure you don't boot to recovery in between. Recovery makes it's own logs. You have tugapower's twrp, right? That's log from recovery booting. Recovery has separated kernel from system's one. Since you are grabing "last kernel message" if you boot in recovery in between is not from previous boot but from recovery boot :)
[ONE Original Android Development] TorchaOne:
Yes. True. It would be nice that there is previous log too... my mistake. I just updated new radio, just to test. ::crying:

And crash:

https://drive.google.com/file/d/0Bx5Ipn9gRusdRHU3dmc2RlNVSHM/view?usp=drivesdk
[ONE Original Android Development] kalapapa:
You can always use kernel adiutor to give you the last kmesg

Just go into kernel adiutor's settings and click save last last kmesg
[ONE Original Android Development] Mecca EL:
[MENTION=4511190]idprophecy[/MENTION]

I have two logs from your current compile. Had two random reboots. Not sure if it's kernel or last nights nightly CM13

UPDATE!!! I looked through the logs and noticed a module I'm testing, causing system errors. I'm disabling the module at retesting. I don't think the kernel is the source of the reboot.
[ONE Original Android Development] xaro99:
big THX
[ONE Original Android Development] LLStarks:
Merge it into our kernel github for CM
[ONE Original Android Development] erorcun:
Qualcomm officially delivers 3.4 kernel to Cyanogen, and once I've seen a comment from either Ethan Chen or Steve Kondik he has said that he hates 3.10 Sony kernel while there is already 3.4 one for same devices.

I don't think he will accept this, but I will write that on G+ or gerrit, let's see what's gonna happen.
[ONE Original Android Development] Mecca EL:
From all you've done so far, it's running really well.

If any of the other devs assisting can add more governors, while you focus on stabilization and adding missing USB and OTG drivers, you'll have done more than expected. Thanks for the progress you've made, nonetheless
[ONE Original Android Development] erorcun:
Thanks =) It's always better when there are more devs, wish there was someone who helps me finding reasons of those reboots. But I don't want to add any governor due to I want to keep this kernel stock, I was planning to make my custom kernel but I don't know will I have time for that :silly: Sure anyone can release a custom kernel based on this without asking me.

Btw, 27/08 build is ready. Min. 2 reboots are fixed(cpufreq and kgsl) let's see what will be next :/

http://www.mediafire.com/download/09fzdvt4r6mq8ea/270816kernel310.zip (anykernel)
[ONE Original Android Development] Mecca EL:
I wish I knew a fraction of what you know about kernel development, I'd definitely help you out. Thanks for getting us this far!
[ONE Original Android Development] fards:
Only error i can see in that is related to sepolicy.
[ONE Original Android Development] TorchaOne:
Maybe it was cm then... ;)
[ONE Original Android Development] erorcun:
28/08 build(anykernel): http://www.mediafire.com/download/f5sj222vq41nvtn/280816kernel310.zip

It's probably N compatible, I will be happy if someone can try.

There are critical changes, so it's highly recommended. (For those who doesn't know, all I try on last times is fixing reboots)