yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] jgcaap:
was checking the source code of the commit you've added and i found this:

qcom,speed3-pvs7-bin-v1 =
< 0 0 0 >,
< 268800000 770000 68 >,
< 300000000 775000 76 >,
< 345600000 775000 87 >,
< 422400000 775000 106 >,
< 499200000 775000 126 >,
< 576000000 775000 147 >,
< 652800000 775000 168 >,
< 729600000 780000 189 >,
< 806400000 785000 211 >,
< 883200000 795000 233 >,
< 960000000 805000 256 >,
< 1036800000 815000 278 >,
< 1113600000 825000 301 >,
< 1190400000 835000 324 >,
< 1267200000 845000 348 >,
< 1344000000 855000 372 >,
< 1420800000 865000 396 >,
< 1497600000 875000 421 >,
< 1574400000 885000 446 >,
< 1651200000 895000 473 >,
< 1728000000 910000 501 >,
< 1804800000 925000 529 >,
< 1881600000 940000 558 >,
< 1958400000 955000 588 >,
< 2035200000 970000 617 >,
< 2112000000 985000 649 >,
< 2150400000 1000000 682 >,
< 2188800000 1000000 682 >,
< 2265600000 1015000 716 >,
< 2342400000 1030000 751 >,
< 2419200000 1045000 786 >,
< 2457600000 1050000 802 >,
< 2572800000 1105000 827 >,
< 2726400000 1135000 900 >,
< 2880000000 1165000 937 >;

For PVS7 Bin 3

Isnt this creating a conflict?

https://github.com/anarkia1976/AK-O...c5f4ad3a59e/arch/arm/boot/dts/msm8974pro.dtsi

Shouldn't be something as:

qcom,speed3-pvs7-bin-v1 =
< 0 0 0 >,
< 268800000 770000 68 >,
< 300000000 775000 76 >,
< 422400000 775000 106 >,
< 652800000 775000 168 >,
< 729600000 780000 189 >,
< 883200000 795000 233 >,
< 960000000 805000 256 >,
< 1036800000 815000 278 >,
< 1190400000 835000 324 >,
< 1267200000 845000 348 >,
< 1497600000 875000 421 >,
< 1574400000 885000 446 >,
< 1728000000 910000 501 >,
< 1958400000 955000 588 >,
< 2265600000 1015000 716 >,
< 2342400000 1030000 751 >,
< 2419200000 1045000 786 >,
< 2457600000 1050000 802 >,
< 2572800000 1105000 827 >,
< 2726400000 1135000 900 >,
< 2880000000 1165000 937 >;

EDIT: nvm has nothing to do with this still searching why is assuming something else :p
[ONE Original Android Development] ak:
What is the specific commit?

Can you explain what is the problem?

ak@bacon@pancetta
[ONE Original Android Development] jgcaap:
i was on boeffla, and went to your kernel, this was mostly a clean flash. And i noticed that the CPU voltages werent correct on synapse.

and i cant find the source of problem. So i dont know if is related to some line on the source, or if is my fault :[
[ONE Original Android Development] ak:
This isnt a k problem

ak@bacon@pancetta
[ONE Original Android Development] jgcaap:
now i got a reboot ... well i wanted to try use your kernel again... :\ seems isnt working for me... I guess i have to quit trying.. Perhaps when i have more knowledge i can find the reason why this happens. if i find i'll let you know ... thanks ak. :)
[ONE Original Android Development] bud77:
Don't forget to reflash your rom kernel before flashing AK kernel :good:
[ONE Original Android Development] martinoff:
I want to write the same but he sad was a clean install so I got confused[emoji45]

sent from my super duphah dumb phone
[ONE Original Android Development] xanthrax:
He said "I was on boefla, this was mostly a clean flash..." I really can't understand

If he was using another kernel then a rom kernel flash has been required

Btw, the voltage table it OK

Sent from my Darkside of 1+1
[ONE Original Android Development] jgcaap:
Ok I have to complete remove boeffla app. And reflash kernel. Now it assumed the kernel default values. Let's see how it runs. :)
[ONE Original Android Development] Lukaslukasm:
Flashed the new kernel and already started the day bad with dropping my oneplus one and causing a little dent and cracking my tempered glass screen protector :( other than that kernel seems to be running smoothly! Thanks ak!
[ONE Original Android Development] tr1gg3r.man:
@ak

Hey brother... Thanks for the new kernel... Getting ready to flash it now, so excited.

Truly appreciate all your hard work and the time you've committed into this amazing kernel.

Was wondering if you might have plausibly reverted the following commits or had any plans to in the future?

401904a29760a7a8e93d79aeb25d51b86ee38d5e
ed1a73d224f2fbf7eb0f4e3d31282f72b3873b3d
3094e977c7840159bccf1102824dc23c832137c1
5ece66503e61768811db8148913d38a469a65daf
8c04f2e6ed27eb07544a2d6caa9a88f68bc2538b
9ad69f5d5c61ce2b77525cea96e7a1e1a148f1f3

Hope you're having a great week thus far!

Sent from my bacon!
[ONE Original Android Development] xanthrax:
Don't drink and flash

Sent from my Darkside of 1+1
[ONE Original Android Development] shure2:
Does this have the new display drivers? Me and another guy used the new Franco kernel with them and suffered from a less responsive screen (slightly delayed swiping etc) but it seems better with AK. Also scrolling is a lot smoother in fb and other apps
[ONE Original Android Development] xanthrax:
Huh you were using boefla app, great and you expect stability, the app dictated those values including that sudden reboot

Always delete its data before flashing another kernel

Sent from my Darkside of 1+1
[ONE Original Android Development] martinoff:
I think that screen is less responsive too, but I am not sure.maybe it's placebo

And maybe more battery hungry with screen on, but for that I will be sure tomorrow

Other than that it's flying as always [emoji1]

sent from my super duphah dumb phone
[ONE Original Android Development] xanthrax:
Actually he was saying that the screen is less responsive on touch with Franco and better with ak or, am I drunk already?

Sent from my Darkside of 1+1
[ONE Original Android Development] martinoff:
Well, maybe I am drunk and have placebo too [emoji38]

sent from my super duphah dumb phone
[ONE Original Android Development] xanthrax:
I guess the only solution for now is to swap the roms in multirom and flash ak on primary

Sent from my Darkside of 1+1
[ONE Original Android Development] shure2:
I probably have OCD because I slide the notification bar down and up all the time. Also I can spot it a mile away if the letter popups are delayed from touch. For me AK kernel is quicker to register touches but it wouldn't make sense if they both use the same new drivers unless AK still uses old drivers (Franco's r28 kernel has a quicker response time)
[ONE Original Android Development] Homerh3t:
Try to flash ak kernel with stock kernel before but wont but up! Tried with .68 and .72 with the cm11s version because im stock rom ! Had to flash stock boot img any help?
[ONE Original Android Development] ak:
What are the commits? why revert is necessary?
[ONE Original Android Development] Ferranza:
I'm terrible sorry for my fast post. Everything is gonna go very well with 72 release. More smooth and responsive than 71. And my battery life is come back. I'm always follow instructions and sometimes I'd love to contribute to this thread
[ONE Original Android Development] martinoff:
Something wrong in your side

sent from my super duphah dumb phone
[ONE Original Android Development] xanthrax:
nope , isn`t right for you but all good here

is UCM flashed already ?

-=-=-

hmm ... deleted
[ONE Original Android Development] ak:
[ INSTALL STEP-BY-STEP - ANYKERNEL FORMAT ]

go to recovery

flash your kernel ROM ---> What is the problem to follow this step? its so simple

flash AK kernel

reboot

finish

I do not understand what is the difficulty of following the procedure. is it difficult?

My kernel use the ANYKERNEL format This means that builds the ramdisk based on the previous one. So if you do not match the stock kernel and use a kernel that distorts the configuration for reasons obscure to me is absolutely necessary to flash stock.

So constantly I see people post nothing but trouble and never a report with some consistency to how it goes.

so why don't give you the stock kernel?

because there are thousands of different ROMs and kernels

around into this dante's inferno.

I expect that at least for this operation there is a commitment on your part.

thanks a lot

ak
[ONE Original Android Development] martinoff:
If he hadn't ukm synapse won't be running

sent from my super duphah dumb phone
[ONE Original Android Development] xanthrax:
eagle eye ! :cool:
[ONE Original Android Development] ak:
You have a problem on your side because for me boot without problems.

Post here last_kmsg if you want.

I dont have understand, but my kernel is always updated and merged with CM11 nightly source.
[ONE Original Android Development] Homerh3t:
Is it problem if i flash with twrp?
[ONE Original Android Development] xanthrax:
not at all !
[ONE Original Android Development] Homerh3t:
So why i cant pass the bootloader when i flash these kernel? I just flash the zip and reboot right?
[ONE Original Android Development] martinoff:
Try to wipe dalvik-cache and cache

sent from my super duphah dumb phone
[ONE Original Android Development] ak:
i want to suggest twrp v2.7.1.1, you can have problems with 2.8.x.x.
[ONE Original Android Development] chikimonke:
What ROM and what version of the Kernel?

[MENTION=3685904]ak[/MENTION] I've never had an issue with TWRP for what it's worth.
[ONE Original Android Development] Homerh3t:
Im on stock cm11s 38R and tried to flash .72 and .68 but no luck!
[ONE Original Android Development] chikimonke:
Did you flash the CM11 or CM11S version of the Kernel?
[ONE Original Android Development] Alin CG:
Did you tried AK.072.GOLD.OPO.CM11. Or. AK.072.GOLD.OPO.CM11S.? :D
[ONE Original Android Development] Homerh3t:
The one for cm11s
[ONE Original Android Development] jojo_whit3:
@ak

He's asking to revert these commits for a mod that I've been working on. The mod is essentially a port of the Voice Wakeup app that was supposed to be included with the OPO...but was removed before being released. The app uses the listening service (LSM) kernel module to register a soundmodel with the Hexagon DSP to provide the always-on voice recognition. Back on October 12th, CM merged these 6 commits from the Code Aurora guys into their source. All 6 commits modify the LSM kernel module in some way and based on the comments, they are meant to provide "MultiKeyword detection for each Listen session" (my guess is they're for the 2nd gen MotoX). Anyway....based on testing and user feedback of the mod, these commits broke the Voice Wakeup app's ability to register a soundmodel in the hardware and causes the phone to reboot.
[ONE Original Android Development] ak:
Do you have last kmsg after reboot?

ps:

i can made a kernel compatible for testing purposes.
[ONE Original Android Development] jojo_whit3:
I'll have to generate one when I get home from work.

I did verify those changes though. I downloaded the CM11 kernel source yesterday, reverted the 6 commits, and compiled it myself. I tested the CM11 10/27 nightly with the stock kernel and the device reboots. I flashed my modified kernel and everything worked as expected
[ONE Original Android Development] thespeed:
Great work.

The kernel (071) is really fast but still not much battery drain.

5 minuts ago i installed 072.. but i think it will be great :)

Only i have a frustrating Wifi problem.

But i think it's a bug in Cyanogenmod so it's not the AK kernel.

See the following bug tracker:

https://jira.cyanogenmod.org/browse/BACON-912

On Wifi 5g i will get an amazing speed of 5 Mbps. :(

When i disable and enable the wifi it goes to 50 - 70 Mbps.

After a while it will go back to 5 Mbps.

Are there more people with this problem?

Because maybe they have changed the wifi drivers in the kernel.

Maybe the old drivers are more stable?

I am now using the Mahdi final rom with the AK kernel.

And a Netgear R7000 Nighthawk.

(checked with DD-WRT and stock Netgear firmware with disabling a lot of stuff and changing channels)

I can't program but maybe swapping a wifi driver is an easy solution. (I don't know how to do it ;) )

Thanks for the great kernel and the time and effort you put in.
[ONE Original Android Development] beany>:
Or use RobbieL811 saber nodded cm11
[ONE Original Android Development] funCrash93:
[MENTION=3685904]ak[/MENTION] do you have any ideas why the "Connection Speed" doesn't go maximum on Wi-Fi?

look

it's "N" Router, so it should give 150Mbps,

like "B" type gives 54Mbps maximum.

The computer (witch doesn't have AC with 300Mbps max type even) connects at 150, why the One can not achieve max. :confused:

(I haven't tried AC, can someone? :) )

Send from my bacon.
[ONE Original Android Development] xlollomanx:
Anybody experieced a slow boot animation? Let me explain: the phone takes the same time to boot but ( I'm using cm11s) the logo rotates more slowly. Is it normal? There are any workaround? Thanks

Edit: Now I'm on 0.72, but I tried 0.68 too, but with the same results. Flashed over stock kernel
[ONE Original Android Development] azsl1326:
I think this is a kernel issue. Running 72 for cm11 on Mahdi. I have an issue with the wake functionality. Drawing a "V" while the screen is off, puts the phone in vibrate mode, as opposed to turning on the flashlight. Unchecking the flashlight option in Synapse/Wake stops this behaviour.

Thanks
[ONE Original Android Development] jgcaap:
[MENTION=3685904]ak[/MENTION] for a long time kernel for me is rock and stable. Thank you for your work
[ONE Original Android Development] tofuboi01:
My router is set to 5ghz N mode and its connected at 144Mbps before but im only getting 65Mbps despite being in the same room as the router..wifi driver problem?

Edit: reconnected and its at 150mbps again, just dodgy signal I guess lol.
[ONE Original Android Development] Alin CG:
Really [emoji19] does that bother you .?...the kernel is rock stable fast and smooth and you are complaining about the speed of the logo ..... No disrespect :D
[ONE Original Android Development] Cris7ianO:
Does newest version have faux/neobuddys intelliplug 5.0 included? Works pretty well on Tyr kernel would really like to see it in this one :D

Sent from my Bacon
[ONE Original Android Development] jojo_whit3:
@ak

Here you go. I did it both for your kernel and the stock CM11 kernel too for comparison.
[ONE Original Android Development] xanthrax:
Enable the torch option in synapse and in ROM settings as well, arrow up or down for torch, it is working well on Mahdi this way

Sent from my Darkside of 1+1
[ONE Original Android Development] :
Perhaps make your own distro. That way we stay clear of the reasons they didnt include this.
[ONE Original Android Development] martinoff:
Change your boot animation

sent from my super duphah dumb phone
[ONE Original Android Development] nicola1989:
[MENTION=3685904]ak[/MENTION] ???
[ONE Original Android Development] RobbieL811:
Neobuddy? Intelliplug is written by Faux.
[ONE Original Android Development] tr1gg3r.man:
If you install BIOS boot animation by BrianAllred you can set the FPS, not sure about other boot animations.
[ONE Original Android Development] reggiexp:
I flashed it over my franco kernel.

And euh now my wifi wont turn on.

I will try again installin it. Im running stock. So i dont have any rom to flash. Or i will end up factory reseting...
[ONE Original Android Development] tr1gg3r.man:
If you look around the threads I'm sure you can find a default kernel to flash for 38R or 33R... I bet there is even a kernel thread.

Sent from my bacon!
[ONE Original Android Development] martinoff:
Just dirty flash the stock rom

sent from my super duphah dumb phone
[ONE Original Android Development] reggiexp:
Yeah but for that i first will need to download a stock rom.

Lool

So reflashing thr ak kernel doesnt give me my wifi back
[ONE Original Android Development] martinoff:
So we have to find it for you, ok.....

Wasn't that hard

http://xdaforums.com/oneplus-one/development/rom-stock-rooted-4-4-4-xnph38r-t2898098

sent from my super duphah dumb phone
[ONE Original Android Development] Homerh3t:
Thanks men the problem was the recovery being 2.8.0.0
[ONE Original Android Development] reggiexp:
Thanks will download that tomorow.

Just flashed franco again and wifi is back. But u find franco kernel a bit boring. So if i want to flash AK i need to flash a new rom? I mean reflash a rom first to get ak kernel to work?
[ONE Original Android Development] fiz:ik:
you just have to reflash the kernel .zip / the boot.img of your rom and then flash ak over it

to fix the wifi issues you have to dirty flash your rom (or I think it is sufficient to reflash the stock wifi drivers posted some pages ago)
[ONE Original Android Development] chachin:
I hope [MENTION=3685904]ak[/MENTION] gets a Nexus6 so we can keep enjoying his awesome kernel even on that phone too :D :cyclops:
[ONE Original Android Development] akarol:
Oh the trouble you'd have avoided by actually reading the directions in the OP... Sigh...
[ONE Original Android Development] sien1996:
With latest slimsaber, videos don't play. I guess that's video drivers not being up to date :angel: Correct me if I'm wrong though :p
[ONE Original Android Development] ak:
Interesting:

https://github.com/CyanogenMod/andr...mmit/49016f917a8196c2b983ddbca762601e3f5a7c94
[ONE Original Android Development] osmosizzz:
Just bouncing around between kernels. It was time to come back. Not having any WiFi issues as others are claiming. Not the 120mbps I'm paying for but this is good enough.

Sent from my OnePlusOne
[ONE Original Android Development] osmosizzz:
So does that mean the GPU will act similarly to touch boost?

Sent from my OnePlusOne
[ONE Original Android Development] ak:
Multirom and anykernel:

http://xdaforums.com/showpost.php?p=56369588&postcount=62
[ONE Original Android Development] legendxx89:
with the last version wifi not work for me
[ONE Original Android Development] ak:
What k before?

ak@bacon@pancetta
[ONE Original Android Development] legendxx89:
franco kernel r29
[ONE Original Android Development] martinoff:
[MENTION=3685904]ak[/MENTION] right now
[ONE Original Android Development] ak:
your friend is the SEARCH button.
[ONE Original Android Development] dasti555:
I have same "issue". I dont find solution for fix :(
[ONE Original Android Development] xanthrax:
So, nothing to do for now until Tasssadar will fix the mr, right?

Sent from my Darkside of 1+1

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

How slow? 5 seconds more? Does it make too much difference?

Sent from my Darkside of 1+1
[ONE Original Android Development] gulp79:
Replace in AK.072.GOLD.OPO.CM11.zip the updater-script in META-INF\com\google\android\

with updater-script from AK.061.GOLD.OPO.CM11.zip and you can flash new versions under MR.
[ONE Original Android Development] vassy.uk:
Hi. I'm on Mahdi ROM. Is the AK 72 version the latest to install?
[ONE Original Android Development] NickosD:
The latest is on the site.
[ONE Original Android Development] dasti555:
You probably dont understand us ..

boot time is same as before but image is slow its not smooth but little bit laggy.
[ONE Original Android Development] lerkin:
Who cares about a little bit slower boot animation? Is it affecting your quality of life or what? Do you have your phone more in restating state or booted?
[ONE Original Android Development] martinoff:
If you search this thread you will see that this is something with cm boot logo, change it and problem solved

sent from my super duphah dumb phone
[ONE Original Android Development] LookedPath:
I noticed that someone mentioned that the touch panel now is less reactive and I'm experiencing the same problem since the new touch driver got merged.

Now I can't write something fast with SwiftKey because half of the touches are lost.

Is it possible to revert it?
[ONE Original Android Development] ak:
I have patched anykernel .. I have to test it .. I think it working.

ak@bacon@pancetta
[ONE Original Android Development] Cris7ianO:
Hey [MENTION=3685904]ak[/MENTION] saw that there is still intelliplug 3.8. any chance for intelliplug 5.0 to be included (like tyr kernel)? :)

Sent from my Bacon
[ONE Original Android Development] ak:
My intelliplug is original one from faux and this is the last ... Tyr have the modded one from neobuddy kernel.

ak@bacon@pancetta
[ONE Original Android Development] ak:
Yeah

ak@bacon@pancetta
[ONE Original Android Development] beany>:
Danged 8 thanks a day. Too many good posts today; off to tapatalk ;)

That sounds good, thanks. OK the workaround is easy but not having to workaround is better still :)
[ONE Original Android Development] Cris7ianO:
Ah OK this clears my confusion ^^ so there is no chance for the nodded one to be included in your kernel? :)

Sent from my Bacon
[ONE Original Android Development] ak:
From my point of view its not necessary ... v3.x is stable.
[ONE Original Android Development] Jole7:
I don't agree the new kernel with the new touch firmware is super reactive no problem here :good:
[ONE Original Android Development] LookedPath:
I've never experienced any problem with the touch panel and from this update i only experience them for a limited amount of time.

This is strange.
[ONE Original Android Development] akarol:
Flawless on my end. Zero reboots so far and the touchscreen is perfect!
[ONE Original Android Development] xlollomanx:
Anybody knows how work slim governor? I searched everywhere but I don't find anything that explain this governor
[ONE Original Android Development] ak:
Its similar to :

ElementalX Governor
The ElementalX CPU governor has been specifically designed and tuned to get the best balance between battery life and performance. By default, it is more conservative than Ondemand. During routine usage, the CPU frequency does not ramp up very often. If gboost is enabled, during gaming or any other graphics intensive situation, the CPU frequencies boost much easier in order to maintain maximum performance. There is also a built in input boost. There are several tunables specific to the governor:

input_event_min_freq: takes four values separated by comma. These are the input boost frequencies for cores 0, 1, 2, and 3 (default 1728000, 1267200, 1267200, 1267200)

input_event_timeout: this is the length of time in milliseconds that the input boost will be active (default 500). Setting this to 0 disables input boosting.

ui_sampling_rate: when you touch the screen, the sampling rate changes temporarily to whatever you set here (default 15000)

two_phase_frequency: this sets the max frequency for moderate loads. Accepts four frequency values separated by comma, for cores 0, 1, 2, and 3. (default 1728000, 1728000, 1728000, 1728000)

How does it work? It's basically a multiphase ondemand governor.

The basic governor is very conservative for most phone activities, spending most of its time at 1267MHz. If there is graphics load, we switch to a two phase ondemand. The first phase runs with a max freq of 1728MHz (default). If the load increases, it goes to max frequency (default is 2265MHz) and the minimum frequency changes to 1267200 (I will probably make this tunable)

The input boost does a couple things. First, it lowers the sampling rate for the timeout duration to make the governor more responsive. Second, it boosts the frequency of any online cores. You can disable this by setting input_event_timeout to 0.

If you want to experiment, delete /system/lib/hw/power.msm8974.so and set the input_event_timeout to about 1000. But I recommend leaving it alone for optimal smoothness.
[ONE Original Android Development] shure2:
You're not on your own my friend, I think we have slightly different experiences to other people for some reason. I find AK better than the latest Franco, but it probably doesn't make sense.
[ONE Original Android Development] Prey521:
AK72 is running like butter so far! Underclocked by 60mv, interactive_pro Gov and OC'd to 2.8 and the phone is running like a champ!! Like it better than Franco. Feels more responsive plus I live the ability to control a lot of the tunables with Synapse. Awesome work!!
[ONE Original Android Development] reggiexp:
okay i will try that thanks. learned that acualy just flashing .img kernel isnt enough, need hole system. will try both and see. the AK kernel looks more completed with extras (franco is okay but i miss things, like governers there is only interactive and performence. rom is okay but i miss just the extras)

just trying to understand. how this phone works with flashing.