yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] RobbieL811:
I mean, it's not hurting anything to be added to the kernel, it is just unnecessary. Know what I mean? There is not currently an app in the Google play store that this phone can't handle easily.

Edit - I'm sure it will be back at some point in time just Mr opinion that there shouldn't be a rush put on it. If it's add easy as just cherry picking 1 commit, then throw it back in there, but if it's an hour of work, I say take care of other stuff first.
[ONE Original Android Development] Setting.Out:
... Only 80 times?.. I thought that it wasn't accurate until the 120 mark.. I usually clock around 1.9ghz and it still feels like butter.. ;)
[ONE Original Android Development] Ferranza:
You did it on b12…!!! You're the... Master... Thank you

Inviato dal mio One A0001 utilizzando Tapatalk
[ONE Original Android Development] shawn0223:
TESH!!!! whats up buddy.

Also, I just flashed CM nightly and this kernel and keep getting bootloop on the 1+ screen. i tried both .040 and 041

am i doing somehting wrong? was coming straight from CM11s. wiped EVERYTHING. flashed CM nightly, Gapps, then kernel.

Even tried just CM nightly. booted up. went back and flashed the kernel. Bootloop
[ONE Original Android Development] oriveradel:
Dalvik and cache wiped?
[ONE Original Android Development] magnamentis:
check this

if it's not that sorry but just trying to help to find the reason so check if you downloaded the right kernel version, there is one for cm11s and one for cm11 and they stick quite close together on a mobile device's display :) good luck

---------- Post added at 11:02 PM ---------- Previous post was at 11:01 PM ----------

he said he did a clean install that means all was wiped. at least that's what i understood
[ONE Original Android Development] shawn0223:
yes i wiped before and after installing everything. Also i did make sure i got just the CM11 and not the CM11s
[ONE Original Android Development] oriveradel:
Aosp CM11 kernel? Try francos r20 kernel
[ONE Original Android Development] magnamentis:
next try

so the only thing which remains then if you did clean install, have the right kernel and it works with stock cm kernel, would be the recovery.

which one are you using ? i remember that there was one twrp version 2.8.0 or something like that which caused such kind of issues, but

it was quickly solved and updated.

we are a bit fishing in murky waters here because that's extremely weird every one here is flashing this very same combo almost daily and it never happend except upon that twrp issue for a day or two.

report back your findings, i'm sure we can learn something here.
[ONE Original Android Development] shawn0223:
these are the ones i tried

http://ak.hiddenbytes.org/downloads/ak.041_b06.opo.cm11.zip

http://ak.hiddenbytes.org/downloads/ak.040.opo.cm11.zip

both causing bootloop on this CM nightly build.

http://download.cyanogenmod.org/get/jenkins/84550/cm-11-20140923-NIGHTLY-bacon.zip

trying Franco now.

---------- Post added at 04:18 PM ---------- Previous post was at 04:11 PM ----------

Franco kernel booted

AK still wont for some reason
[ONE Original Android Development] :
Interestingly I can mega undervolt on interactive pro, but not on lates beta version with whichever I try. Lots of reboots.
[ONE Original Android Development] magnamentis:
as you like

of course you can do that but i hope that considering the fact that this combo definitely does not cause bootloops in general, frankly said, only on your device, that you are aware that there is something on your end and if you want to find out what it is, it makes perhaps sense to get to the bottom with it. but as i said, that's your free choice, albeit i would be very interested to learn what the culprit was. good luck however but be aware that franco does not build for cm11 just for cm11s for this device. so from time to time people report issues, while often it works for some time.

Download:

For CM11S only

boot image:

http://kernels.franco-lnx.net/OnePlusOne/4.4/

zip:

http://kernels.franco-lnx.net/OnePlusOne/4.4/zips

For AOSP roms ( my note here: cm11 is not a clean aosp rom there is a lot of caf stuff )

http://kernels.franco-lnx.net/OnePlusOne/4.4/aosp/
[ONE Original Android Development] shawn0223:
oh i dont wanna keep franco kernel. i was just trying it because someone said to try it to see if it boot.

ive been rooting and flashing roms and kernels for years and never had the issue. what else could it be on my end?:eek:
[ONE Original Android Development] juanjo7812:
No nightly for cm11s this time?

Enviado desde mi Oppo N1 usando Tapatalk
[ONE Original Android Development] jgcaap:
From what I learned dirty background ratio should be on low values. Such as dirty ratio 5% and background ratio 15%. If you insert such high numbers there will be moments where your phone will lag.

According to my study, basically works like this.

System inserts information on ram, and from that information some of it is "dirty" which means, useless info that will have to be written down to cache. If the numbers gets to high, you'll have alot information to be written and will lag.

Beside the theory I made tests, on the I/O level, where I shared here in the forum.

Conclusion, the default value inserted by [MENTION=3685904]ak[/MENTION] are already perfect. You can change swapiness to 15% which improves a bit multitasking, or keep the 10% to get more, the so called Immediate performance. To ally swapiness you can give a max of 124mb of zram, which is faster and on memory level. Also you have the benefit to not "tear down" so quickly the sdd memory card.

In case of any question feel free to ask. =) cheers

---------- Post added at 10:59 PM ---------- Previous post was at 10:55 PM ----------

You cannot mega undervolt. Remember. Some governors hide the voltage you need on each frequency. In order to correctly test, you must do it on on-demand governor so that it'll hit on all frequencies. Else, you'll notice that some frequencies are never used, but after a while, when it is used... It'll freeze or reboot. :) hope it helped.

---------- Post added at 11:01 PM ---------- Previous post was at 10:59 PM ----------

There are many theories. According to what I've learned from this matter, wipe cache and Dalvik is important after every rom or kernel update as it basically will optimize the app "speed as also compabilities" on related to the Rom and kernel settings.

---------- Post added at 11:03 PM ---------- Previous post was at 11:01 PM ----------

What's your cpu? What's the voltage you have between 2ghz and 2.5? Please insert here by order so that I can suggest some tests.
[ONE Original Android Development] venky716:
These are the values I set for vm.

I found these to be common in a lot of threads about battery saving.

My main intention was to improve battery life, I haven't noticed any change in battery life, if you know anything about these could you please let me know.

Thank you.
[ONE Original Android Development] jgcaap:
Well the secret in batter saving is the speed response the cpu has over each app you open. On the cpu configuration section in synapse you'll have there saying that cpu response is 8 ms, raise that number a bit and you'll get better battery.

Changing dirty ratio values won't give you better battery, will only delay the battery usage, because there will be a moment where your phone will have to writte down all data. Which means higher consume of cpu during longer period of time.

So basically... Those threads are a bit misleading on this. :/

Now of corse I can also speak with you about getting xposed, with Grenville, display configuration to save energy and many other things. But what you are trying to achieve is basically this what I told you. But if lags... Is normal... You'll get performance or battery but at least with the best values for your phone to work.
[ONE Original Android Development] shawn0223:
How would I even get that without booting? Ak kernel won't boot for me on cm nightly.
[ONE Original Android Development] gordon.shameway:
This really sounds like recovery is causing the problem. Check your version of twrp. If its 2.8.0.0, update to 2.8.0.1
[ONE Original Android Development] jgcaap:
You have that on synapse app at info.

Which kernel did you download? There are two versions. One is for cm11s which won't let you boot on nightly the other is for cm11.. Download that one.. Install ukm and app :)
[ONE Original Android Development] :
Normally I would agree, as logic seems sound. But I tested it with an app capable to stresstest each frequency, It didnt skipp any and no errors were made nor did phone reboot as fast as on new kernel. I also tested with lower voltages and they did make my phone freeze/reboot suggesting the voltages were correctly used.

Odd
[ONE Original Android Development] jgcaap:
Just to finish. On a phone you want less swap as possible. Because it saves battery. So change it to the default 10% and vfs_cache_pressure to 100.

As I said before, I questioned [MENTION=3685904]ak[/MENTION] default values... But they are the best on the market.

---------- Post added at 11:41 PM ---------- Previous post was at 11:19 PM ----------

Bachera what I tried to mean is. Each frequency has its voltage for any type of governor you'll use. Imagine you have a porshe and that in other to save gas, you cut a bit on the air to the car. Basically will accelerate less but when it goes to its maximum rpm will be lower than before, this of course in high speed.

On electronics is more and less the same, but here what matters it's the percentage value on each cpu. I trust you stress tested. But the real test is on the use of the phone, not of the apps. Because when you change frequency if you don't give enough juice it'll freeze. On stress test, will give un unrealistic idea. That's what I found during what I investigated but as always... Each phone has its fabrication, that's why we have all diferent cpu versions and soc. But the real test make it on on-demand while using.

My bet will 2 of the cpu steps are causing issues. Caused to me and I raised voltage and never had an issue again. I even suggested to remove those cpu steps as they are doing almost nothing here.

But to clear every thing up. I suggest you to try. 2.3ghz and 2.4ghz cpu step have to be raised the voltage on some cpu. Specially if you are pvs 7.
[ONE Original Android Development] shawn0223:
you were right bro. updated TWRP and we got it booting. Thanks man

I know man. I had the right one from the beginning stupid TWRP version was bad. All's good now. thank you both for your help:highfive:
[ONE Original Android Development] magnamentis:
you are funny man

i told you that 2 or 3 pages before, so reading the post would help a lot then considering how many posts came thereafter

dont' believe me, check this link: http://xdaforums.com/showpost.php?p=55631712&postcount=3457
[ONE Original Android Development] magnamentis:
quote error

hi, thanks for the thanks my friend [MENTION=5593968]gordon.shameway[/MENTION]

your post above mixed the quoted text with my name, i did not post that, sorry.

i'm on clockworkmod recovery, the thing with twrp recovery 2.8.0.0/2.8.0.1 just crossed my mind because his issue could not be rom or kernel related and i remembered that there was something while following each post in the thread from day one.

so unfortunately i cannot answer your question about unofficial because i never used it on this device
[ONE Original Android Development] jgcaap:
[MENTION=3685904]ak[/MENTION] perhaps would be wise to update the main threat with some alerts about the TWRP recovery and links to people read about each mode on the kernel.
[ONE Original Android Development] shawn0223:
honestly, i dont know how i looked over your post. complete and honest mistake bro. I been here a while and know to read lol.. just happened to overlook yours lol. my apologies. Thanks for being so prompt with the responses though.
[ONE Original Android Development] gordon.shameway:
Whats your SOT ?
[ONE Original Android Development] magnamentis:
yeah can happen

no prob really was a bit confused the first moment because in the background i was really pondering like hell what the hell could be the issue since it looked then like it was neither rom version nor twrp. now that this is settled let's be glad that your device is up and running now. after all that's the whole purpose of all this. enjoy
[ONE Original Android Development] MrMarkEdward:
Looking forward to v.041_b08 the simple on-demand governor is fixed correct?
[ONE Original Android Development] RobbieL811:
It's fixed.
[ONE Original Android Development] ak:
new kernel online

[ KERNEL v.041_b08 - NIGHTLY ]

ak.041_b08.opo.cm11

[ SMALL CHANGELOG ]

Linux 3.4.103

Update to last CM

Fix Simple Ondemand crash

Interactive PRO governor

Please press thanks button and rate thread.
[ONE Original Android Development] ak:
https://plus.google.com/100278518551580225387/posts/4j7nfNWbnq6

ak~vanir@a0001
[ONE Original Android Development] Glatzi:
At the moment there are no new updates for CM11S because there are no updates from CM ;)
[ONE Original Android Development] vignesh_jariwala:
Boot loop

I am getting boot loop after installing ak41 b6 and now with also b8, If I restore it with franco it is working fine, I tried cleaning dalvik and cache but not seem to be working what should I do?
[ONE Original Android Development] maxver0:
It's after cleanflash... Why I'm having this drain in standby?

Wyslano z Oneplus One
[ONE Original Android Development] venky716:
Turn off anything that uses the proximity sensor.

I had this before then I turned off pocket mode in lockscreen notification, active display, acdisplay's active mode, proximity wake from display etc.

You've to search deep to find and disable them.

It is caused by a race issue of proximity sensor. CM knows and is working on a fix.
[ONE Original Android Development] ak:
reflash your rom.
[ONE Original Android Development] ak:
I dont know why everytime users have drain the problem is related to kernel.:silly:
[ONE Original Android Development] maxver0:
I don't any proximity fancy things. I'm on slimkat with stable ak.

Wyslano z Oneplus One

---------- Post added at 08:53 AM ---------- Previous post was at 08:51 AM ----------

Well, I didn't said it's because of kernel. There are many battery gurus, so I'm asking here :)

Wyslano z Oneplus One
[ONE Original Android Development] ak:
No problem, you have to apologize was not related to your post, just that a few times then it creates entropy and many users report then without having a real analysis.
[ONE Original Android Development] albyXR:
I was with stock ROM and AK v.39: best experience ever with battery.

Now with v.40 its ridicoulos! After che last reboot during check mail now i am with franco kernel..

I was faithfull to this kernel but with the update they change the unique thing that work well...dont understand..this is my experience ..please i dont want teacher or people that judge me..it only an aswer..
[ONE Original Android Development] Addicteddddd:
Good to know, thanks.

And imo, you should not be flamed for stating an opinion, it is a forum after all :).

Will look into the franco kernel now.
[ONE Original Android Development] nosidefcp:
[MENTION=3685904]ak[/MENTION] i cant manage to use the search functionm at this time. have you eliminated the higher frequencies?maybe you can create a version for oc and other without those frequencies...thanks in advance
[ONE Original Android Development] ak:
for now yes. :fingers-crossed:
[ONE Original Android Development] RobbieL811:
Are you using stock Slim build? If so, that's probably why you are having the proximity battery drain problems. There are some commits on Gerrit that fix it. I am trying to finish updating the kernel & get it all pushed to Gerrit, & that problem will be no more.
[ONE Original Android Development] DespairFactor:
I am working on bringing over clock to sensei which is based on AK
[ONE Original Android Development] maxver0:
Yes I'm. Well dunno if it's really proximity sensor issue. Someone just said so. Is there any way to check it to be sure?

Let me know.

Wyslano z Oneplus One
[ONE Original Android Development] jgcaap:
Can you make cm11s to? Thanks
[ONE Original Android Development] ak:
:angel::angel::angel:
[ONE Original Android Development] Lither:
Thanks for the explanation, if you have alter any other settings in the kernel for better battery consumption, please let me know :)
[ONE Original Android Development] famonaco:
Hi anarchia which is the best intelliplug profiles?(battery and performance)

Thx

PS: i use ondemand_eps (i can change it if u suggest me other)on aicp rom
[ONE Original Android Development] happybabe:
How to flash back stock Kernel if i don't like it?
[ONE Original Android Development] NickosD:
Dirty flash rom again.

Sent from my Bacon!!
[ONE Original Android Development] jgcaap:
You have a thread with default kernel, you have to use fastboot

---------- Post added at 02:25 PM ---------- Previous post was at 02:22 PM ----------

here : http://xdaforums.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 only need to flash boot.img
[ONE Original Android Development] happybabe:
fastboot.exe flash boot boot.img

you mean just do like this?
[ONE Original Android Development] jgcaap:
You don't need the. exe

But yes :)
[ONE Original Android Development] jgcaap:
Noticed something interesting. If I have mpdecision off on cm11s he will respect the low cpu frequency values that I insert. Anyone having this issue?

---------- Post added at 05:37 PM ---------- Previous post was at 05:29 PM ----------

Anyone know where I can find the main difference between intelliplug and autosmp? Can't find the info..
[ONE Original Android Development] dinglehoser:
[MENTION=3685904]ak[/MENTION] what's the new "high performance sound" mode do? Just noticed it showing up in Synapse for the last couple of kernel releases. Does it improve quality, decrease resource utilization, or ...? Trying to get the cleanest output from the headphone jack possible.
[ONE Original Android Development] jgcaap:
[MENTION=3685904]ak[/MENTION] do you think we can test this new tcp https://en.wikipedia.org/wiki/TCP_Westwood_plus ?
[ONE Original Android Development] DJMartini:
+1
[ONE Original Android Development] jgcaap:
Had an idea [MENTION=3685904]ak[/MENTION] , how is the charge management beeing on this phone?

We could create a way of extending the quality of the battery life beyond the normal kernels possible by editing how it should be charged. I've been up searching and come up with: http://xdaforums.com/nexus-s/development/mod-battery-life-extender-blx-t1257497

We should also have possibility to edit Charging for USB 2 and 3, or has to be 1 configuration for all ?

What do you think?
[ONE Original Android Development] funCrash93:
interesting idea, and a chance to tune that maximum value in Synapse would be great. :)

Send from my bacon.
[ONE Original Android Development] DJMartini:
I'd agree with that. This would be nice to have!
[ONE Original Android Development] :
Bunch of reboots with my settings on b8 I dont get on version 40.

Added logs maybe they help.

Flashed stoc kernel before and uninstalled and clean installed to make sure it wasnt leftovers messing with it.
[ONE Original Android Development] shawn0223:
look a couple pages back, i had the same issue yesterday bro. if you're on TWRP 2.8.0.0 it wont work. you need 2.8.0.1
[ONE Original Android Development] ak:
Very strange, you have last kmsg that report V40 my friend:

[ 0.000000] Booting Linux on physical CPU 0 [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Linux version 3.4.0~ak.040.opo.cm11 (ak@kernel) (gcc version 4.8.4 20140831 (prerelease) (SaberMod-4.8.4_arm-graphite) ) #1 SMP PREEMPT Fri Sep 19 08:28:20 CEST 2014 [ 0.000000] CPU: ARMv7 Processor [512f06f1] revision 1 (ARMv7), cr=10c5387d [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache [ 0.000000] Machine: Qualcomm MSM 8974 (Flattened Device Tree), model: Qualcomm MSM 8974Pro-AC One+ A0001 [ 0.000000] Hardboot page reserved at 0x2F600000 [ 0.000000] Initialized persistent memory from 60000000-600fffff

The problem cant be related to kernel.
[ONE Original Android Development] jgcaap:
[ 7.189744] [<c086c368>] (cpuidle_idle_call+0x0/0x250) from [<c010ed00>] (cpu_idle+0x84/0x108)
[ 7.189824] [<c010ec7c>] (cpu_idle+0x0/0x108) from [<c0db8cd0>] (secondary_start_kernel+0xf8/0x100)
[ 7.189909] r9:512f06f1 r8:0000406a r7:c14f1d9c r6:10c0387d r5:ee162000
[ 7.190170] r4:00000003
[ 7.190307] [<c0db8bd8>] (secondary_start_kernel+0x0/0x100) from [<00db83d4>] (0xdb83d4)
[ 7.190354] r5:00000015 r4:51000400
[ 8.190908] wcnss crash shutdown 0
[ 8.190949] Rebooting in 5 seconds..
[ 13.192547] Going down for restart now
[ 13.193265] Calling SCM to disable SPMI PMIC arbiter

There was a crash of the wcnss? isnt this related to wifi? Perhaps a bug on the rom side no?
[ONE Original Android Development] BoboBrazil:
Does this kernel have the latest touch screen fixes in it? On version 40 for 11s I started getting the multi touch bug where it spazzes out during pinch to zoom. I didn't get this when running Franco kernel, but I'd lime to stay on this kernel as I like the over clocking option and I actually get better battery on ak.
[ONE Original Android Development] jgcaap:
yes for cm11s user v0.40 stable
[ONE Original Android Development] :
I guess I didnt get the other reboots in the logs. Did get one reboot on 40, that was indeed user error.
[ONE Original Android Development] ak:
This is related to userspace/softreboot from rom side, not kernel.
[ONE Original Android Development] ak:
cm11s kernel dont have the same patches of cm11 for nightly rom. so the touch fixes arent inside.

it will be implemented when official source coming out on shipping branch.
[ONE Original Android Development] vng10:
sorry for asking this but what are the default GPU and I/O? trying to go back to default and i cannot remember those :)
[ONE Original Android Development] Roymik:
Msm-adreno-tz for GPU and Deadline for I/O afaik..
[ONE Original Android Development] vng10:
is FSYNC enabled or disabled by default
[ONE Original Android Development] Roymik:
Enabled by default...btw,in synapse if you uncheck "apply settings on boot" and then do a reboot,you will have stock values..
[ONE Original Android Development] jlevy73:
Enabled.
[ONE Original Android Development] jgcaap:
Question, Franco implemented those fixes for cm11s if I am not wrong. Didn't he?
[ONE Original Android Development] BoboBrazil:
Ok I thought so. Back to Franco until official is out I guess:highfive:

Yes he implemented them in Franco kernel.
[ONE Original Android Development] jgcaap:
After testing alot... I find v 0.40 unstable for cm11s, but v0.40 b12 is stable. The kernel which is stated as stable 0.40 gives reboots, sod when mpdecision is off, when it is on gives reboots and simply doesn't respect minimum cpu value.

Don't know what happen between those versions.. But all logs I shared in past are all related to v 0.40. The beta 12 from 0.40 works great... Why?
[ONE Original Android Development] jgcaap:
[MENTION=3685904]ak[/MENTION] sorry if you find annoying or something.. I like your kernel... And I would like to be able to use as others.. Just trying to help... Sorry if in any way I am being repetitive or something... Thanks... Take care.
[ONE Original Android Development] ludester:
Just wanted to post this here (http://xdaforums.com/showpost.php?p=55656639&postcount=3960) Anyone that can advise what has changed in the newer kernels (must be a CM change).
[ONE Original Android Development] fards:
I've not seen any rild changes ( they are user space anyway). There's just some protected nv code, but that just messed up us unlocking the other radio frequencies.

Unless I've missed something..
[ONE Original Android Development] ak:
Only Developers can be found where is the problem, but i think CM sooner or later will fix, i'm only an RC here. ;)
[ONE Original Android Development] RobbieL811:
Lol. Don't feel bad. They said I was too stupid for RD too. Lol.
[ONE Original Android Development] ak:
I'm feeling good my friend don't worry.