yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] jgcaap:
None taken.. It is true I have to improve my level of communication. Perhaps making positive statements, as you are suggesting is more likely to work for a healthier "relation" to work things out.

My mistake on forgetting we are all humans... So I em deeply sorry. I didn't want to create any stress... Just tried to call the attention of ak on a matter which I thought was related. I'll format my phone after this week and try again.

[MENTION=3685904]ak[/MENTION] I'm sorry about sometimes thinking and saying things so straightforward. Even if you closed the thread, I would speak the mods to reopen for you and after that create a script to spam your email until you started to participate again. =p

I hope the years end I am able to get myself with some contribution on code to your kernel as I said in the begining, I would like to work with you and help improve kernel.

Later I'll do the tests you've requested. But I start to think is may be some compability relation between cm11 and cm11s.

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

Perhaps the bug is on UKM. I'll try see the files later... Will do a dirty flash as you did and see if kernel works well after. Thanks...

edit: i used UKM with CM kernel also and dont have this issue, but i'll test AK without UKM by dirty flashing.
[ONE Original Android Development] chikimonke:
Hi [MENTION=3685904]ak[/MENTION] I just had my first random reboot in a long while. I'm on [MENTION=4911350]RobbieL811[/MENTION] 's later SM Slim and have the following settings:

ondemand_eps, Fiops, Intelliplug - Balanced, Intellithermal - Stock, arch power

every thing else is stock.
[ONE Original Android Development] ak:
the problem is related to this:

[39812.483227] cpufreq: invalid target_freq: 43205032

[39812.524364] cpufreq: invalid target_freq: 43205032

in the log i cant see what is the driver with problem, but i can search into the code tonight.
[ONE Original Android Development] jgcaap:
Well I done two tests after dirty flashing.. One gave good speed.. The other gave bad speed. :(

I'm going for clean flash to see if improves after new update arrives...
[ONE Original Android Development] prstorero:
If you're testing multiple times in a row, make sure to first let the device cool down. The hotter it is when you run it, the lower results will be due to throttling.
[ONE Original Android Development] jgcaap:
The thing is never reaches the throlling temp... I'll test again later to see if solves...
[ONE Original Android Development] ak:
How do you have checked for verify throttling?
[ONE Original Android Development] ak:
Mmm .... the error is related to cpufreq:

ak@ak-desktop ~/android/AK-OnePone $ grep -r "msm_cpufreq_target" .

./arch/arm/mach-msm/cpufreq.c:static int msm_cpufreq_target(struct cpufreq_policy *policy,

do you have the full last kmsg?
[ONE Original Android Development] Franc38:
I've tested it this way:

first with AK.

then flash stock kernel.

The unit is noticeably hot after having run the benchmark a first time but still, run the benchmark less than a minute after the reboot.

Result... 30k with AK, 46k with stock. and clearly a much smoother visual in the 3d part at the end of the test.

Tried a go with Boeffla latest and it seems to be a sort of middle ground... slower/choppier than stock but less so than AK and a score at 40K. (Plus Boeffla gives me some wifi slowness that I don't have with either AK or stock).

Seems I'm stuck with stock kernel... Will see how it goes battery wise.
[ONE Original Android Development] ak:
At this point i think cm11s will be stock as possible.
[ONE Original Android Development] irony17:
[MENTION=3685904]ak[/MENTION]

what does the values in the panel calibration tool refer to ?

With " c8 01 06 ff 02 0e fe ec 0a f8 f9 fe b7 ee 04 fb fc fe af ec " my colors are awful but I don't know what they refer to in order to change them
[ONE Original Android Development] jgcaap:
I monitor temperature with this during test:

https://play.google.com/store/apps/details?id=com.yanyan.cputemp

I didn't compare the code yet with cm kernel. But have you thought about the sensors being with diferent variables?

Thanks...
[ONE Original Android Development] tofuboi01:
Not sure what is a good score on antutu benchmark for OPO but i did a few tests and got scores ranging from 32-39k.

On my current setup i consistently scored 39k on two runs.

Cm11S 38R F2FS

Interactive: 268-2457

Intelliplug balance4 + cpu boost driver

thermal d control 80/90 degree C

Voltage: -50mV on lower freq and -25mV on higher freq

2048 SIO

GPU: 200-578 msm-areno-tz

hope this helps?
[ONE Original Android Development] Brightlenny:
I am loving this kernel I don't need to run unreliable benchmarks scores to tell me how well my kernel is running. I want my kernel to be more battery friendly then a performance monster. But a simple change of the governer is all I need to do for a switch from battery to performance. I usually get close to 7 hours screen on time and 2 days of use. oh by the way ran a benchmark just changed governer to performance here my result. This will be first and only benchmark I will run.

AK loving this kernel keep up the good work mate
[ONE Original Android Development] jgcaap:
Normal is between 42k and 48k.

You also have cm11s?
[ONE Original Android Development] tofuboi01:
What rom and settings are you using? Just curious.

Yeah I am, I am running CM11S on F2FS format. Speed bin of 7 and using v.75 kernel.

I am happy with the performance i am getting and battery has been great, although i have yet to test gaming performance as i dont really play any games on it that is intensive.
[ONE Original Android Development] jgcaap:
Ok... Third person with cm11s... I think we are getting somewhere here.. As soon as I get home I'll review and compare the code with stock to better understand this.
[ONE Original Android Development] acuicultor:
I dont care of benchmarks cuz i really feel when im happy with a rom or kernel but here are my results using ak kernel with RobbieL's cm11 rom. Not bad!! And yes im having this resusts more or less every time i run antutu

Sent from my Crispy Bacon
[ONE Original Android Development] DJMartini:
I'm just going to mention this from other kernel threads I've had with experience.

For those of you running benchmarks and caring about how high of a score you're getting or how your phone runs at max, feel free to put in it a freezer and overclock all setting than run your test. That's great! But on day to day usage benchmarks don't mean crap. It's always based off max performance for short duration of time which any phone should never be running at in the first place. If you're looking for a max performance kernel I doubt any dev actually wants to design their kernel around. The purpose of all these kernels is to provide users the ability to tweak settings here and there to perform better for day to day use. If you're maxing your phone out for benchmarking on a day day use I'm not sure what the practical purpose you're using your phone for. Voice/SMS/Data and even Gaming don't need to max out the performance of your phone for day to day use.
[ONE Original Android Development] venky716:
I've tried all kernels available for bacon including those that are not on xda like dark kernel. I'm very picky about even the minor lags and stutters.

Keep coming back to ak just for its smoothness.

Slim+mpdecision is just a beast.

Even underclock to 1.7 with no lag.

Not much of a gamer though I play once in a while and all my games run top notch with no frame drops. [MENTION=2040569]jgcaap[/MENTION] I get what your saying but I stopped using antutu after it gave great results for very laggy kernels on my previous devices. Interactive is a bit less smooth on ak than stock kernel don't know why but I don't use it anyways since I find it a very conservative governor.

Once again kudos to you [MENTION=3685904]ak[/MENTION] for building the best kernel on One.
[ONE Original Android Development] ak:
Thanks guys for support, my only problem is related to the fact i dont have 2 phone so i can test only one kernel at a time.

What makes me angry is the fact that left 20 version of the kernel version for CM11S and only now people say they have problems.

I think to rabase only the S version with only official cm11s commits.
[ONE Original Android Development] CounterC:
I see a lot of users giving feedback about cm11 and cm11s. can anyone share experiences with AK in combination with aosp Mahdi? what version should I take and any other tips?

thanks
[ONE Original Android Development] vikrant82:
CM11S, AK75, CPU on Perf, GPU on Perf - (Relatively cold device) Antutu - 44395. I know for fact that if I put it in refrigerator it would be around 45.5 - 46. I remember running it on interactive and score was probably around 30K. I keep going to stock kernel now and then and I have observed average score there would be +1-2K in general. But it's all in same range. Most low scores is because of hot device.

EDIT: I have thermal range as 85, 95.

Sorry to possibly spoil the mood of thread - But any kind of lag simply puts me off! A small lag and I am back to drawing board with Synapse. Only way to get rid of lag completely is to go to SmartMAX or OnDemand which defeats the entire purpose of tweaking.

But its fun. Yet to get the perfect battery / performance thing. I wonder if there's even such a thing.
[ONE Original Android Development] martinoff:
Well this is fair enough if it will be your last decision and we all have to respect it and say to you a big thanks for all your works

For myself I don't care since I'm not using cm and won't do it in near future

But here until now I see only one user who is care for bench and staff. What about all other users who are not members on xda or they not write, will they lose the smoothing and battery life of this kernel because of one bench app
[ONE Original Android Development] tofuboi01:
Im not complaining anything at all, you re added sio and brang back the .63 kernel colours which i appreciate and cant thank you enough for.

Every kernel i had no issues, i did have some reboots on idle but that is due to underclocking too much. Fixed it and have had no issues since. :D
[ONE Original Android Development] Franc38:
Yeah, it's been said time and again how benchmarks are not very useful, how depending on temperature, other apps running and so on, your perfs will vary. But, this is like... totally not related to what we discuss.

The thing is not the absolute best performance to be obtained, had you cared to read... It's that in the specific case mentioned, the "3D video game" part of the benchmark becomes choppy and the performances take a big hit... compared to perfs on the very same device, in the same conditions, just minutes apart, with a different kernel. The purpose of this is to exemplify and measure the fact that something limits AK kernel on CM11s when running a demanding app. Could be observed in other ways, but hey... that's what benchmarks are made for.
[ONE Original Android Development] ak:
decision

for now I will not give more support to the CM11S until it comes out the L version of Android for OPO.

There are so many good kernels here that can be used.

Sorry for my outburst in these pages.

The adventure continues with CM11 nightly.
[ONE Original Android Development] kenzolo:
@ak

How can I enable logcat by default without using synapse?
[ONE Original Android Development] Beaster:
Sad news.

Hope you reconsider.. Been using your kernel on CM11S for 2 weeks and i love it.

Of course your decision is respected!

Thx for your hard work!
[ONE Original Android Development] jgcaap:
I'll try help you with cm11s as soon as I can. But I understand.

On-demand fixes this?
[ONE Original Android Development] Prey521:
Thanks for the update on the WIFI drivers. The latest Saber Mahdi (11/01) doesn't work with .75, so I'll use .74 until [MENTION=2699658]xanaxdroid[/MENTION] get a chance to update the ROM, since it appears that .75 works with the latest official Mahdi release.
[ONE Original Android Development] vikrant82:
Yes, ondemand_eps and smartmax are very buttery but too noisy on CPU and cores.
[ONE Original Android Development] jgcaap:
Ondemand fixes it!

This must be issues with interactive governor?

edit: dont use this gov, is still bugged... :\
[ONE Original Android Development] fiz:ik:
It's your decision, v75 running stable for me, so basically no need for more. I cherish you, I really do. You're one of the nicest and best devs out there. :good:
[ONE Original Android Development] zaphodbeeb:
Top man in my book. Thank you for producing and maintaining Ak kernels.
[ONE Original Android Development] tofuboi01:
Sad times..i hope you will reconsider this decision. But all respect to you! Used your kernel since i got my phone two months ago and has been great! Satisfied all tweaking needs!
[ONE Original Android Development] jgcaap:
With smartmax is fine to. I remember you tuned interactive. Did you update both branches? Sorry come up with this but u just thinking about it.. Since other governors work well..
[ONE Original Android Development] RobbieL811:
This what I would've done all along! Who cares about 11s!?
[ONE Original Android Development] fiz:ik:
May I ask why? :confused:
[ONE Original Android Development] bud77:
[MENTION=2040569]jgcaap[/MENTION] : Please STOP talking about issue or "inconsistency"

Don't you find it odd, that you are the only one reporting "issues", which is actually not an issue, since there is no log or whatsoever

And no, antutu or any benchmark in general is not a reference, it does NOT reflect daily use, as 99.99% of people are using it

If you want to report something, provide proper log, or better, a proper fix

Just open your favorite github repository, fork it, and make changes, makes tries, and come with a solution, or something at least helpful other than an antutu bench

Several person did it already (poke [MENTION=5169465]RIPng[/MENTION]) and made it great

I'm just pissed to see you freely trashtalking over "nothing"

AK is doing much more than a hardwork, and you MUST be thankful to that

[MENTION=3685904]ak[/MENTION] Is your website down ? Can't access it form my 2 networks
[ONE Original Android Development] DespairFactor:
What are you trying to get from AK? I will pull it for you.

If anyone has any problems with AK, I will clear it up for them. If you want to bash any "dev" bash me. AK puts a lot of work into this and he doesn't expect anything back from you guys. The fact that you can go around saying bad things about someone who generously offer charity to you in the form of development is ridiculous and insinuates that you have a poor moral compass. If you think he isn't doing a good job, go use something else or make your own.

EDIT: nevermind, I can't hit his site either.
[ONE Original Android Development] bud77:
Just the 0.75 for CM11

Thanks mate :good:
[ONE Original Android Development] RobbieL811:
B/c it's a pain in the ass & its outdated as soon as is built! It's a stupid concept to me. What's the point in running a month or two month old ROM?
[ONE Original Android Development] DespairFactor:
I couldn't get to his site either
[ONE Original Android Development] fiz:ik:
If you're comparing OP with Samsung or HTC you'll be thankfull for a two month old ROM. But yes, you are right. I'm confused due to knowing CM as a "fast" maintainer. If there were CM11S nighlies, that would be great. But no, there is nothing but some OTAs. It feels weird to have CM installed and get such a poor support. I mean, we're talking about the CyanogenMod Phone :confused:

I think I'll switch ROM when the WiFi issue is fixed :cowboy:
[ONE Original Android Development] RobbieL811:
I don't have WiFi problems in any of my ROMs. There are no WiFi problems. Just as I said, ROM is outdated already.
[ONE Original Android Development] naeem76:
There are WiFi problems for some of us, I created a thread, and no one even batted an eye.

Anyways the AK site is down, if someone could mirror the CM11s v75 zip, it will be helpful
[ONE Original Android Development] jgcaap:
For real guys? Do you really think I have problems with him? If it got me money.. Perhaps I would think about it. :p

These are issues which some users have, from cm11s. Read carefully.
[ONE Original Android Development] CounterC:
I'm running the same setup. thanks for the info. I can flash 74 with working WiFi then...
[ONE Original Android Development] xanthrax:
No, these are issues with "some benchmark results" which is a big difference compared to kernel issue, as I said earlier but apparently you missed it, the Daily usage is the real benchmark which should be taken in consideration when talking about "stability", " consistency " and so on

Sent from my Darkside of 1+1
[ONE Original Android Development] jgcaap:
You have the right for your opinion and I am glad your experience was good. As I have right to point thing I think is hurting performance. In your sense, that is a personal attack? Please man!

I use his kernel since 0.35. If reporting possible bugs, issues is an insult. I even tried to help process that info in the past, so that we going debug in an organized way. I've been trying to find reasons for bugs and studying stuff. Is also frustrating to not find answers and have problems.

I even wrote a apology about the way I write... And about what I said.

So I really cannot understand where you assume I have a problem with ak. I love the guy, he is usualy very humble. And he proved I'm wrong and that's something else.

I also can imagine is hard for him since he cannot debug properly.
[ONE Original Android Development] chikimonke:
The problem is that [MENTION=3685904]ak[/MENTION] has repeatedly said that he holds no confidence in benchmark results. You've written some very long posts, but very few, if any, have been accompanied by a log. Yet, you keep insisting on telling AK that he's doing something wrong, and that he needs to fix it, basically just so you can have top notch benchmark scores. I've used this kernel since it became available for my 1+1 and I used his kernels on my GNex. He's been nothing short of an awesome kernel dev, always offering great support, if you supply the proper information. If he can't reproduce the error, and you can't provide a log, how is he supposed to fix it? I realize you do mean well with all your posts, but it's falling on deaf ears at this point. When I see a wall of text from you, I just skip by it, and I imagine there are many others in here that do the same, including AK at this point. If you want to actually constructively contribute, get logs and real world data. If you want to be taken seriously, don't use benchmark tools as your main source (or really any source) of information.
[ONE Original Android Development] Franc38:
Nope. The problems are with any demanding app... Makes the phone "choppy". Antutu is but a mean to measure that and to allow comparison between different settings.

If you play a game and sometimes you have 60fps, and at other times, same place in the game, you have 20fps, yeah, the right word is "problem of consistency". Which usually hides something nasty.

Anyway... stop bashing [MENTION=2040569]jgcaap[/MENTION] for being the messenger of bad news. I too have the same problems. I'm sure others do, too (if using CM11S and ak75) but given how they get treated, they probably don't even dare saying it.

Which is bad as it prevents ak from identifying the culprit and improving his otherwise very fine kernel.
[ONE Original Android Development] ashok:
I have tried all you have mentioned. None of the method works. Tried flashing stock kernel, does not work. tried flashing AK v74 does not work. Tried dirty flashing the rom, does not work. Luckily I had made TWRP backup which i had restore,
[ONE Original Android Development] bud77:
Rule number one when you create a bug report : provide a log

So far, I've seen NONE

You can also provide a way to reproduce error ... Oh wait, no one was able to reproduce ...

I'm using this kernel since day 1, and I've never seen a "real" bug not being taken care of (And yes, I've read all the 639 pages)
[ONE Original Android Development] Franc38:
Who says it's a bug?

You've read since page 1 but.... maybe too fast.

Nobody is attacking ak, here, and if it were the case, I don't think he'd need you to defend himself.
[ONE Original Android Development] danyvw:
Thanks dude. I will try it.

Edit: Got it. Looks identical to the one I had. Thanks.

Sent from my Oneplus One
[ONE Original Android Development] lowrider82:
Latest stable.. Random reboots with cm11 nightly.. Back to v20 stable

Sent from my OnePlus One
[ONE Original Android Development] DespairFactor:
It's cm code causing reboots, you can request him to pull the commits that fix the issue either from me or cm
[ONE Original Android Development] lowrider82:
Can't adapt the kernel to the rom? I doubt they will pull commits just for this kernel... V20 works without problems

Sent from my OnePlus One
[ONE Original Android Development] DespairFactor:
What? I build off of ak/cm source and have committed fixes for the reboots. The reboots were from code CM committed to fix the touch screen and wcnss
[ONE Original Android Development] lowrider82:
Sorry..... I don't understand... Same Cm works fine with older ak kernel... How is it cms issue then?

Sent from my OnePlus One
[ONE Original Android Development] DespairFactor:
The older AK kernel doesn't have the buggy code in it.

If you need a further explanation, feel free to inbox me or reach out to me on hangouts
[ONE Original Android Development] Setting.Out:
CM's kernel commits, not ROM commits.. ;)
[ONE Original Android Development] clock51:
v 030 installed on my OPO, it works very well, just a little problem, if I load the phone off, you do not see the battery icon, it is normal, there is a rimedio.grazie
[ONE Original Android Development] chikimonke:
I believe that's ROM related. I know [MENTION=4790322]kufikugel[/MENTION] from the Slim team had been trying (or very possibly been successful in) squashing that bug.
[ONE Original Android Development] lowrider82:
Thanks understood.

Damn... Can't cm fix touch etc without causing reboots? Is there any plan for fix? Do the reboots happen with the latest cm kernel as well?

Sent from my OnePlus One
[ONE Original Android Development] DespairFactor:
I told you CM has a fix, ak hasn't merged it yet
[ONE Original Android Development] lowrider82:
Ah great.. Come on AK! Make it happen! [emoji3]

Sent from my OnePlus One
[ONE Original Android Development] sambaeallegria:
Had a lot of random reboot today with latest PA, with and without UV. Here is the last kmsg.
[ONE Original Android Development] mimpoca:
What are your Synapse settings? I can't manage to get past 39,000... :(
[ONE Original Android Development] danyvw:
Just Max CPU frequency with Performance governor, Max GPU frequency, stock voltage, MP-Decision and FSYNC disabled.

Sent from my Oneplus One
[ONE Original Android Development] ak:
I'm on holidays, so sorry guys, but i can't update kernel for now.

I have a slow connection.

:)

Crash related to modem:

[ 97.591225] SMSM: Modem SMSM state changed to SMSM_RESET. [ 97.591517] Fatal error on the modem.
[ONE Original Android Development] sambaeallegria:
Have fun! :)

Inviato dal mio One utilizzando Tapatalk
[ONE Original Android Development] Pipodi93:
Don't know if is kernel-related, but it's something strange! 5 minutes ago I was at 98% battery, and now I'm fully charged, even without plugging it in the charger!

Strange, isn't it?
[ONE Original Android Development] Glatzi:
Self charging kernel. Already experienced this with [MENTION=2376110]dorimanx[/MENTION] kernel on my G2 ?
[ONE Original Android Development] pinoymutt:
Really sad to hear that as well, as I've been running your kernels on CM11S since I got the phone, and I've never had any major issues. Respect your decision, but still sad that other folks' complaining drives you to that point... :(