yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] magnamentis:
not sure bot one thing to add at least

i'm not sure but i seriously doubt that it's a kernel issue. however as to my previous workaround it was missing something unfortunately. you certainly know what happens to files when you delete or clear them. they remain where they are until the space on disc or drive is needed or until you format that storage. up to that moment the file or folder is still in place, what we did was just removing the visible link ( directory ) to that file or folder. i don't know about the level of experience but from my experience, depending on how the process is handled, upon re-installing or re-building a file or folder with the same name two things can happen; a) the old one is overwritten ( good in this case ) b) the link to the file or folder is re-installed and points to the very same old file or folder we thought we deleted. so i do NOT know which is the case here but the strange revival of former settings in synapse could well point to variant b). i'm just sharing thoughts here because there certainly must be a reason why once of a sudden a previous tweak would just insist to pop-in over and over again.

a consequence would be that you at least flash your rom again, because chances are good that these files are located in system which would be formated upon flashing many roms. one of the reasons why for example custom bootanimations in system/media are gone after that, while the very same bootanimation will stick when placed in data/local.

i'm glad for any feedback so i can learn and discard false assumptions and search for solutions elsewhere.
[ONE Original Android Development] funCrash93:
[MENTION=3685904]ak[/MENTION] can you take a look at this : https://cloud.mail.ru/public/9923efd0ceb6/log

1 reboot and 1 freeze so I had to reboot for today... 20.09

ak40.stable on MAHDI 17/09.

Send from my bacon.
[ONE Original Android Development] stab244:
For me it's weird. I have locked frequencies when I use it on CM nightlies but on fusionjacks SlimSaber, I don't.

Sent from my bacon
[ONE Original Android Development] ak:
If you install busybox from market you can fix it.

ak@a0001
[ONE Original Android Development] ak:
You can disable it, set freq and re-enable.

ak@a0001
[ONE Original Android Development] ak:
you have to excuse me I'll be a little absent in these days, my wife's sister is about to have a daughter.

Already has two twins and my wife and I are doing babysitting ... fantastic addition to our 4 year old son.

I hope you can understand, thank you very much for your support.
[ONE Original Android Development] jgcaap:
Congratulations! Give us the news soon.
[ONE Original Android Development] magnamentis:
have fun

no problem, same here, you uncle, i grandpa but same procedure i'm sure :) just be careful with heavy metal sound levels, children's ears are way more sensitive hehe.. just kidding of course. enjoy
[ONE Original Android Development] ak:
Yeah metal up your ass forever ... Hail and Kill .... :D

for the uninitiated

http://metallica.wikia.com/wiki/Metal_Up_Your_Ass_(demo)
[ONE Original Android Development] fards:
looks like some new kernel code in the latest cm nightlies might be causing issues for some of us playing with unlocking the modem bands.

Did you pull that code into yours @ak?

https://github.com/CyanogenMod/andr...mmit/c2ab22468bd7bce11e40e884723452e3b0132657
[ONE Original Android Development] clock51:
congratulations ... I understand, I'm a grandfather of two beautiful grandchildren
[ONE Original Android Development] jgcaap:
According to what I have seen It depends or we would have ports from all types of roms. There are always optimizations that can be done on a rom + kernel level where files changes. For instance AK kernel doesn't support all roms.
[ONE Original Android Development] ak:
AK CM11 nightly have this commit.
[ONE Original Android Development] fards:
I presumed so, didn't get a chance to look through your github yet, but tried V40 to check and had same issue.

Looking more likely that is causing issues with us writing the changed values with qxdm to enable all the bands in the modem, some people are reporting success with unlocking and using band 20 LTE (800mhz) on the chinese opo.

Something oneplus said was impossible, however it won't work with the last couple of cm11 nightlies, so it's looking like that code is responsible.
[ONE Original Android Development] LookedPath:
Nightly? What nightly? Did I miss something? ?

However you don't have to apologize for an absence of a couple of days since we owe you the speed of our phone. ?
[ONE Original Android Development] ak:
Have you try v039?
[ONE Original Android Development] fards:
slowly working backwards through options at the mo, been trying to get diagnostics working on qloader mode, or in recovery, to bypass kernel all together, neither will play. .

will test v39 next, im intrigued to see how the values are reset in the kernel, and if I can get them to stick, how they are changed by flashing a new one.

EDIT V39 breaks things in all manner of interesting ways, no network, value reading errors in qxdm and options to disable Cdma roaming in network settings (I'm on euro gsm).. back to v40 or the 20/09 nightly kernel fixes that one..
[ONE Original Android Development] chipstien:
Hey AK. Any chance you can add the Optimax governor? After switching to this governor I've noticed my SoT has increased quite a bit.
[ONE Original Android Development] poondog:
Give them my congratulations and wish them luck from me :)
[ONE Original Android Development] DespairFactor:
[MENTION=3685904]ak[/MENTION] any idea when you are merging those new touch work queue fixes and so on?;)
[ONE Original Android Development] Glatzi:
Enjoy the really important things in life[emoji6] congrats!!!!!
[ONE Original Android Development] ak:
I have rebased all ... I'm testing the new version ....

ak@a0001
[ONE Original Android Development] RobbieL811:
Awesome! This is good news! Thanks!

---------- Post added at 05:23 AM ---------- Previous post was at 05:20 AM ----------

Also, I updated toolchain. Make sure to pull the changes.
[ONE Original Android Development] bud77:
Sorry for the offtopic, could you link to the thread ?

I'm really interested in 800mhz LTE ... :D

Edit : Nvm, found it :)
[ONE Original Android Development] shure2:
Could you share it please?
[ONE Original Android Development] danny_and_2:
Search for it.

It have been in top of the general section for multiple days now.. Oo

http://xdaforums.com/oneplus-one/general/guide-unlock-aditional-bands-qualcomm-t2877031
[ONE Original Android Development] jgcaap:
Nice.. What's the base?
[ONE Original Android Development] störte:
Ehndroix is working also well with the cm11 kernel.
[ONE Original Android Development] jakemog:
Intellithermal is very buggy, and does not react to custom throttle temp. If i set throttle to 75c it downclocks at 60..
[ONE Original Android Development] RobbieL811:
It is being worked on. Give it a little time.
[ONE Original Android Development] jakemog:
Awesome thanks :good:
[ONE Original Android Development] ak:
If you think is buggy, you can explain what is the problem exactly .... I have fully tested and the only problem is the freq lock when throttling.
[ONE Original Android Development] innomi:
Quick question.

In first post it's stated the cm11s kernel if for 30o. But what if I am on 33r?

Can I use it then?

And in difference of Franco kernel.

What is the biggest plus for me to install this AK kernel?

Verstuurd vanaf mijn OnePlus One 64GB
[ONE Original Android Development] ¿GotJazz?:
Hi - I'm currently running Franco on my OPO, and I'm thinking about giving AK a shot (based on all the great reviews).

One of the main features I'm looking for is low idle current. On Franco, I'm generally seeing 7-8 mA on idle.

What is the normal idle current seen for AK? I don't want to lose the nice battery benefits I'm seeing with Franco.

Cheers,

¿GJ?
[ONE Original Android Development] venky716:
5-9 depending on what you have in the background etc.

Franco gives me same as well.

This was with sync, Wifi, data off.. Only cell standby.
[ONE Original Android Development] jakemog:
As i said when i set throttle temp to 75c it ignores it and throttles at 60c instead :confused:
[ONE Original Android Development] Sick1:
I use Cooltool to monitor "thermalzone0" which i believe is SoC temp. and its been throttling fine since Faux kernel on hammerhead till now on this one.
[ONE Original Android Development] magnamentis:
all on !

see attached thumbnail

as to comparing kernels, i think i remember that it's not welcome on xda to compare, i propose that you read the feature list and the thread and you'll get an idea.

for me the dev and his attitude can sometimes count more than often minor technical details, insiders certainly know what i mean and else nothing is said.

EDIT: i get 1% in 8-10h idle and this over many months on several devices, including the OPO which i owe for about 80 days
[ONE Original Android Development] jakemog:
Just installed a fresh version of mahdi, ill test in a moment.

Nope same, im rolling back to nightly untill this gets less buggy :/
[ONE Original Android Development] famonaco:
AK if i have already installed ukm can i flash only your kernel,right?
[ONE Original Android Development] BoOsT:
Yes, and synapse from playstore[emoji106]
[ONE Original Android Development] magnamentis:
no

- you can flash ukm before or after the kernel, does not matter

- you can install another kernel if you find one for your device

- if you don't use synapse ukm is not necessary to run this or any kernel

- if you are going to use synapse it will show exactly the tunables which your kernel allows but you need UKM

- i recommend to reflash ukm after updating your rom, it happenes that otherwise it's gone

---------- Post added at 08:04 PM ---------- Previous post was at 08:01 PM ----------

not sure who understood him wrong, he asked only this kernel which is not the case, ukm and synapse works with other kernels too.

but perhaps he meant if he can flash kernel after ukm as well as before that would be no problem, so let's see, i'm curious ;) :)
[ONE Original Android Development] jakemog:
Can you run the top freq until the temp reaches 70c?
[ONE Original Android Development] ak:
You do not have thermal like N4 or N5 (3 phases), When throttle cpu temperatures, drivers go only one step down is act for the frequencies, and you can not set it but it's automatically calculate. So when you finish set temperature is 60c and you Reached what is the behavior for you?
[ONE Original Android Development] ¿GotJazz?:
Thanks, for the info, magnamentis! That's what I was looking for. Definitely going to give AK a shot now.

Regarding the "comparison", I think what I was asking for is fair ... I was asking about a quantitative (measurable, scientific) difference instead of a qualitative ("what do you think is better", emotional) difference.

And, that's exactly what you provided.

Thank you!

¿GJ?
[ONE Original Android Development] jakemog:
when the cpu reaches 60-65c (setting throttle temp to 100c does not effect this) under 100% load from a constant 2880mhz 4x each core randomly reduces to lowest of 2265mhz and fluctuates in between, my previous phone was galaxy s 4 where if i has set throttle temp to 85c it would stay at 2 ghz until it reaches 85c
[ONE Original Android Development] SenK9:
Is there any plan for per app profiles in the future? Or is that up to Synapse dev?
[ONE Original Android Development] ak:
Re: [KERNEL] [3.4][SM4.8][AOSP/CM11/CM11S] [19/09] [stable v.040 - nightly v.0xx] AK

Deleted
[ONE Original Android Development] ak:
No .. But you can use fauxclock

ak@a0001
[ONE Original Android Development] Glatzi:
[MENTION=3685904]ak[/MENTION] were there Bluetooth related commits during the last days? Really have strange issues with last cm11 build from RobbieL811
[ONE Original Android Development] ak:
No bluetooth commits inside the last kernel.
[ONE Original Android Development] RobbieL811:
Most Bluetooth commits are handled on other repos than the kernel repo.
[ONE Original Android Development] Glatzi:
I've installed the v40 from ak now. It is compiled with less optimizations or am I wrong? Will try Bluetooth again tomorrow
[ONE Original Android Development] RobbieL811:
Should be the same as mine. You can still try it if you want.
[ONE Original Android Development] Glatzi:
Ok than the experience should not differ
[ONE Original Android Development] fards:
bluetooth or audio? one of two of the audio changes in cm11 might break audio over bt.
[ONE Original Android Development] RobbieL811:
Hmmm. Thanks for that. Do you know exactly what commit it was?
[ONE Original Android Development] fards:
I'm not convinced by some of the changes in the 19/09 the adsp/acdb stuff, although speakers work fine.

this is an odd choice as well.

http://review.cyanogenmod.org/#/c/73387/
[ONE Original Android Development] Vortex1969:
Just a little update on the Beanstalk build I am doing. I finally got it to build but there are some bugs to fix.

All I have to say is the dev's that brought there ROMs over to the one had a lot of things to add.

It much easier to just repo a ROM that has been built for the one already.

PS ak kernel is still running great Thanks..
[ONE Original Android Development] RobbieL811:
Glad that you finally got it to build! AWESOME!!!
[ONE Original Android Development] Vortex1969:
Yeah I was sweating it for a while. It made me have a lot of respect for the Dev's that bought there ROMs to the one. Much more than just vendor file- breakfast bacon. I had to branch and pick a lot of code. Much easier to just repo a ROM that was already built for the One. I will post it to test when I get the couple of thing fixed and Thanks.. [emoji6][emoji12][emoji29]
[ONE Original Android Development] RobbieL811:
Lol. You didn't tell me that's what you were trying to do in all of those PMs! Lol. I thought that you were just trying to sync & build.
[ONE Original Android Development] ¿GotJazz?:
Hi, [MENTION=5372360]magnamentis[/MENTION] (or, anyone else) - Could you please provide additional details on your AK settings? I installed AK v.040 over CM11S 33R, and I am seeing a huge difference in my idle settings. I haven't made any adjustments yet to AK - but the lowest idle currents I am seeing are around 50 mA, and mostly around 120mA to 320 mA, This is a lot higher than what I saw with Franco - I am sure I need to make some settings to AK to get my battery drain lower.

Thanks,

¿GJ?
[ONE Original Android Development] dgjenkins:
Here's a whole thread that talks of nothing but exactly this. Enjoy! http://xdaforums.com/oneplus-one/general/ak-kernel-profile-synapse-t2858674
[ONE Original Android Development] maxver0:
Ummm, not so convinced. Just changed gov to conservative.

Wyslano z Oneplus One
[ONE Original Android Development] magnamentis:
not kernel related

2 Hidden Quotes:

sorry guys, this kind of battery drain is not kernel related. the repeating argument is that it started after installing this (or another) kernel and it still has more to do with flashing anything than with what has been installed. these are userspace battery consumers which cause it and it can happen upon many opportunities, flashing new rom, updating old rom, updating apps, updating kernel or flashing new kernel.

many many times a restart will help, if not the procedures are more or less standard to find the culprits:

a) reboot under power and check again because each boot-up causes media scanner and other processes to consume higher than average power

b) install WLD or BBS and look for the culprits

c) found culprits, clear cache and app data in settings>apps>"guilty app"

d) install greenify and greenify the rogue apps on screen of with tasker

e) if all that does not help do a clean install with formatting system, data etc. partition and install everything from scratch.

....further use the opportunity to install user apps i increments to find out in which group of apps is the culprit. if you make

....a nandroid before adding a new group of user apps you can just go back to prevous state withing a minute or two and retry

....with fewer apps until you found your cause.

BTW albeit i have currently 7 devices to manage i had to clean install with formatting partitions (not the same like wiping) for such reason is not higher than 3-4 times so chances are good that you get away without that but there is always a chance that from time to time installing from scratch is the way. good luck

ok you asked for my settings, almost nothing changed, just noop scheduler, 2048 read-ahead, performance gpu gov, cubic tcp, i tweaked heavier before but since the touch sensitivity got improved firmware wise i could reduce power and go a bit more battery friendly. before that i got 2% in 8-10 hours idle and now it's 1% while SOT varies a lot between 7-8 hours average
[ONE Original Android Development] ak:
[ KERNEL NIGHTLY ]

A kernel based on CAF CM11 Bacon branch.

cm11/aosp: ak.041_b06.opo.cm11

- rebased over CM11 branch - ultra last

- removed interactive_pro, slim governors

- remove intellithermal

- removed zram

- removed and cleaned some stuffs

changelog:

https://github.com/anarkia1976/AK-OnePone/commits/ak-11.0-nightly-rebased

please press thanks button.
[ONE Original Android Development] _PrEzi_:
Agreed. CM11s + AK's kernel +UKM (and some tuning in Synapse) and this thingy is sleeping like a baby !!

Last time I have reached over 5 days with data/WLAN always on and 2,5-3h Screen on time.

Remember that the kernel only helps to achieve great battery life, but IT IS NOT ENOUGH!

Things like freezing apps, greenifying them, removing Ad-framework (through patching, not through ad-away/other host methods), removing other kind of ADs (via min min guard) etc. will DEFINITELY be the 90% of work to achieve good uptimes !

maxver0 - I serio serio --- polecam ten kernel, ale -- tak jak powiedzialem - sam kernel wiosny nie czyni...
[ONE Original Android Development] maxver0:
Nie używam greenify i nie będę bo uważam ze to szkodzi środowiskowi androida, mam na tyle ramu ze nie musze sie o niego martwić. Wszystkie aplikacje jakie mam to sa te z których chce otrzymamywac powiadomienia, więc nie ma mowy o greenifikowaniu.

Używam tylko adaway, to nie powinno mieć wplywu przy idle. Miałem wszystko wyłączone wtedy, zasięg - 80dbm na 2g a brało 1,3%/h.

How it can't be kernel related? There was no wifi/internet connection, I have set type connection to 2g and it was 99% in deep sleep and during that time i had like 1,3%/h drain. That's right I have flashed ak over franco kernel. I might try clean flashing tomorrow, now I need working phone.
[ONE Original Android Development] jgcaap:
Will you continue development to cm11s?thanks
[ONE Original Android Development] ak:
yes why not ;)
[ONE Original Android Development] EasyGoingXD:
ak, whats your favourite rom?
[ONE Original Android Development] jgcaap:
Thanks. I prefer for now cm11s is more stable and faster compared to others. :) will wait a cm11s version.
[ONE Original Android Development] faddys123:
How do you remove the ad framework? Is it with lucky patcher?
[ONE Original Android Development] ak:
no updates from CM for cm11s for now.
[ONE Original Android Development] _PrEzi_:
You should read the OP -- it clearly says you need to flash the stock kernel before flashing AK.

Dirty-flashing from other kernel wasn't and never will be supported.

P.S. With Greenify you can preserve the notifications and push-messages, just make some research before writing.
[ONE Original Android Development] maxver0:
I know that about greenify. But I prefer android eco system to handle it on its own.
[ONE Original Android Development] kdrkdr:
[MENTION=3475639]ak.[/MENTION] Now Sensei dropped BLX support are you willing to introduce it? This is why I want it.
[ONE Original Android Development] ak:
No ... For now.

ak@a0001
[ONE Original Android Development] magnamentis:
how ?

i thought i explained that, because it's 999/1000 times userspace related and if it would be kernel related how can i and others have great battery life and nobody else complains about it, at least never for long until the real culprit is found.

if you have set an app to sync only on wifi, that's a possibility if that app keeps trying, you have wifi always on in settings>wifi>adavanced>scanning alway on, that's another possibiltiy, if you have set location services to battery saving and/or high accuracy that would be another and the list could be endless these are just a few "POSSIBILITIES" which does not mean it's one of those but it's certainly user space. further as i wrote, if you read through various kernel threads you will find many similar posts like yours, all ending with i solved it, was this or that but never was the kernel, i simply don't remember any issue like that which was kernel related and at the same time most if not all others get extremely good battery life.

this was my last attempt to convince you. if you insist that it's kernel related then change the kernel and let us enjoy the perfect efficieny of this one.
[ONE Original Android Development] famonaco:
Anarchia love your kernels, is good the last nightly?:)

Forza Italia:)
[ONE Original Android Development] ak:
yes ... no problem so far. You have to use with roms updated to last cm11 commits.
[ONE Original Android Development] famonaco:
Hope that crdroid rom have these update:)

THX My friend
[ONE Original Android Development] jgcaap:
[MENTION=3685904]ak[/MENTION] what is the new base? Thanks
[ONE Original Android Development] ak:
cm11 branch.

the same as always, but CM have merged ton of stuffs ...
[ONE Original Android Development] _PrEzi_:
Dear all, I know this is more ROM-related than kernel... but since I use CM11s (for now at least -- thinking about a switch to RobbieL811's Sabermodded CM11) I thought I might give a shot here... Searched through XDA and googled... but haven't found an answer.

The issue is -- I have a flip-cover with window and a "cut-out" part where the answer/reject ring is placed. The issue is -- either it is cut out too high or the ring on the Colour OS is higher than in CM11s/CM11. Now my question -- is there a way to modify the vertical placement of the call answer/reject ring ??

Same with the alarm-clock -- the disable/sleep ring is about 1,5 cm too low for me.

Sorry for OT...
[ONE Original Android Development] jgcaap:
Ah Oki. Did you saw the logs I sent you about the cpu changing values constantly?
[ONE Original Android Development] bigmase521:
Thanks for the update! Was the conservative GPU governor also removed? It's not showing up in Trickster, and msm-adreno-tz is now the default.
[ONE Original Android Development] ak:
Because yes all drivers for DVFS have changed.
[ONE Original Android Development] ak:
im looking kmsg live with this command and i cant see problems with last CM11 nightly:

while true;do dmesg -c;sleep 1;done
[ONE Original Android Development] jgcaap:
All logs from me are from CM11S Stock.

I tried to use robbie rom, but is not as fast as stock, so i decided to flash back.
[ONE Original Android Development] ak:
can you post logs?
[ONE Original Android Development] RobbieL811:
Mr [MENTION=3475639]ak.[/MENTION] Do you think it's possible that you could've left out the commit that keeps simple_ondemand GPU governor from rebooting when applied? I can't remember the commit message, but I remember seeing the commit. I'm getting a reboot on new build as soon as I apply simple_ondemand.
[ONE Original Android Development] jgcaap:
all here:

https://www.dropbox.com/sh/mnobhvtxmxesu50/AAD44O4vlEvqBtVEmZxAiLQwa?dl=0

the last 2 ones (on date, logcat) are the ones which have that issue of the CPU, of lowering minimum voltage always to 268Mhz.

PS: Don't forget to update CPU voltage, because it reboots. (you have 3 kmsg with the information with default settings, later changing voltage becomes stable for PSV 7 chip, dont know how others are dealing with this.)
[ONE Original Android Development] ak:
Yes ... no problem i can investigate.
[ONE Original Android Development] RobbieL811:
Also, should I still just continue building from nightly branch or should I switch to nightly-rebase?