yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] magnamentis:
yes you can

a) yes you can

b) you even should

c) the first 5 and the last 5 pages are a must and would have done in this case

d) the first 10 an the last 10pages usually do and would have done in this case

if someone asks you to go 5 steps don't argue that you cannot cross the continent on foot

and even that would not be true, you could but you don't want and make others pay the price in energy

and no matter whether we like rules and/or find them always good rules but nevertherless, reading before posting is a rule.
[ONE Original Android Development] simo.scorpion:
the next time i'll do it, is a promise, so the answer is yes when cm team release new ota

simpatiaportamivia
[ONE Original Android Development] shaker2k:
Try and imagine how AK feels. He busts his butt making this kernel for us. Coding, fixing, merging. Hours of work.

You and other users are posting the same question at least 20 times. Maybe more. So yeah I'm guessing a simple search would not be too much to ask.
[ONE Original Android Development] simo.scorpion:
all I'm uproar when it was enough to say "yes"
[ONE Original Android Development] DxTcmix:
I have had zero issues with the latest version on PA 4.5 beta 1. My battery life has been out of this world
[ONE Original Android Development] d13guit0:
[MENTION=3685904]ak[/MENTION] I'm trying last beta over slimdarkness and performance and battery seems great. What about the GPU error prompted in synapse? Could be a wrong path? Mako's script is shown instead of A001
[ONE Original Android Development] DerRomtester:
Will this kernel work with latest cm11s ota update ?

Maybe they have updated their kernel branch.
[ONE Original Android Development] Nicuz95:
Nope, [MENTION=3685904]ak[/MENTION] will not support CM11S as said in the OP and in previous pages
[ONE Original Android Development] DerRomtester:
Yeah i read that. But AK kernel supports cm11 right. And maybe they have updated latest ota their kernel branch to the latest cm11 branch and so the kernel should work . it is only a theory.
[ONE Original Android Development] ak:
New release of UKM will be with all fixes, also for slim device tree recognition.

Stay tuned, also voltage control is fixed now.
[ONE Original Android Development] chikimonke:
Released now.
[ONE Original Android Development] ak:
Thanks a lot for report.

Nb:

new UKM v3.1 release fixes all problems, please flashing it for full control on AK kernel.
[ONE Original Android Development] Shambola:
Nice to see you [MENTION=3951473]AK![/MENTION]

:)
[ONE Original Android Development] ak:
The same for me.

If you have any question PM me.

last night I had to fight to restore the factory but I won, it was tough and so if you need help im here.
[ONE Original Android Development] Shambola:
I knew I'd bet on the winning horse :laugh:

tnx man
[ONE Original Android Development] d13guit0:
[MENTION=3685904]ak[/MENTION] New UKM update works better so faaar! GPU label working at last good with many many governors :)

Good work friend!
[ONE Original Android Development] ak:
Thanks man.
[ONE Original Android Development] d13guit0:
Do U have a donation link mate? I would do a little contribution to ur work [emoji8]
[ONE Original Android Development] dudas89:
Same issue here, with stock CM11S.
[ONE Original Android Development] gordon.shameway:
Try to make a fresh install just of the rom, then let it boot. After that try to flash kernel. Make sure that the download is not corrupted and it is the right version
[ONE Original Android Development] NickosD:
If you are coming from another custom kernel, flash the stock one first.
[ONE Original Android Development] Poesini:
Ohhhh, I see... Let me get to my house and I will try :)

Thanks man
[ONE Original Android Development] :
I'not noob :). I've checked the files and is all ok.

---------- Post added at 01:02 AM ---------- Previous post was at 12:59 AM ----------

@ak your new cm11s kernel support latest miui for OPO? I really appreciate your work
[ONE Original Android Development] RobbieL811:
No problem. First thing you will see when you open the script are the paths that I am talking about. Just change to the location that the files are at on your pc. Also, clone that ramdisk, as it is needed to compile. Also, you will probably need to clone the toolchain.
[ONE Original Android Development] tsouza:
The gfx glitch is still here using cm11 kernel + 38r :/
[ONE Original Android Development] jgcaap:
Still didn't have this but soon enough well discover what is.
[ONE Original Android Development] :
anyone of you have tried 61 with the M11?
[ONE Original Android Development] dudas89:
I flashed this one first: http://xdaforums.com/oneplus-one/general/kernel-stock-cm11s-xnph25r-t2822949, as instructions said. It is the most recent kernel I found and I'm using the most recent version available on the website: 33R. Then I flashed AK 061 and... Bootloop.
[ONE Original Android Development] RobbieL811:
Using the stock cm kernel?
[ONE Original Android Development] jgcaap:
With stock cm didn't have but tested for 6 hours. Now testing with ak and nothing also..
[ONE Original Android Development] tsouza:
AK 61 is for 38R
[ONE Original Android Development] vibranze:
What is the recommended settings in Synapse, e.g. governor, scheduler, etc for balanced performance/power saving? Thanks.
[ONE Original Android Development] tsouza:
There is no general rule since it depends on usage patterns. You should try different combinations and see which one is better for your needs.
[ONE Original Android Development] nicholaschum:
I had a post about this for Mahdi and v50 gold. Are these graphical glitches black in color and flickers around randomly on different segments of the screen?

||||||||||||||||||||||||||||||||||||||

Looks something like that ^?
[ONE Original Android Development] akarol:
It's a black horizontal line or so across the screen. Disabling He overlay temporarily fixes it.
[ONE Original Android Development] Poesini:
Ok I cloned everything but now it says this:

#
# configuration written to .config
#
scripts/kconfig/conf --silentoldconfig Kconfig
CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[1]: `include/generated/mach-types.h' is up to date.
make[1]: Nothing to be done for `arch/arm/boot/dtbs'.
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
CC init/do_mounts.o
In file included from include/linux/icmpv6.h:175:0,
from include/linux/ipv6.h:224,
from include/net/ipv6.h:16,
from include/linux/sunrpc/clnt.h:26,
from include/linux/nfs_fs.h:57,
from init/do_mounts.c:20:
include/linux/netdevice.h: In function 'skb_gro_offset':
include/linux/netdevice.h:1638:18: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
error, forbidden warning: netdevice.h:1638
make[1]: *** [init/do_mounts.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make: *** [init] Error 2
make: *** Waiting for unfinished jobs....
make: *** wait: No child processes. Stop.
‘/home/mauricio/android/AK-OnePone/arch/arm/boot/zImage’ -> ‘/home/mauricio/android/AK-OnePone-AnyKernel/zImage’
DTB combiner:
Input directory: 'arch/arm/boot/'
Output file: '/home/mauricio/android/AK-OnePone-AnyKernel/patch/boot.img-dtb'
Found file: msm8974pro-ac-pm8941-a0001.dtb ... chipset: 194, rev: 65536, platform: 8, subtype: 0
additional chipset: 210, rev: 65536, platform: 8, subtype: 0
additional chipset: 213, rev: 65536, platform: 8, subtype: 0
additional chipset: 216, rev: 65536, platform: 8, subtype: 0
=> Found 4 unique DTB(s)

Generating master DTB... completed
adding: anykernel.sh (deflated 66%)
adding: META-INF/ (stored 0%)
adding: META-INF/com/ (stored 0%)
adding: META-INF/com/google/ (stored 0%)
adding: META-INF/com/google/android/ (stored 0%)
adding: META-INF/com/google/android/update-binary (deflated 34%)
adding: META-INF/com/google/android/updater-script (deflated 72%)
adding: patch/ (stored 0%)
adding: patch/boot.img-dtb (deflated 80%)
adding: patch/init.d/ (stored 0%)
adding: patch/init.d/00ak (deflated 57%)
adding: patch/init.d/99zram.sh (deflated 43%)
adding: patch/modules/ (stored 0%)
adding: ramdisk/ (stored 0%)
adding: ramdisk/sbin/ (stored 0%)
adding: ramdisk/sbin/bb/ (stored 0%)
adding: ramdisk/sbin/bb/busybox (deflated 43%)
adding: tools/ (stored 0%)
adding: tools/dtbToolCM (deflated 66%)
adding: tools/mkbootimg (deflated 35%)
adding: tools/unpackbootimg (deflated 34%)
adding: zImage (deflated 0%)

-------------------
Build Completed in:
-------------------

Time: 0 minute(s) and 7 seconds.

I am pretty sure the files under modules are there cuz I see them, but after I run the script they get deleted somehow :/
[ONE Original Android Development] tsouza:
Yep, something like that!
[ONE Original Android Development] nicholaschum:
Good. I'm not alone. Haha! I was actually getting worried as I didn't see many people with it here....was planning to grab another invite lol.
[ONE Original Android Development] ak:
If you have installed cm11 kernel, and the rom isnt updated to the last source is normal.
[ONE Original Android Development] akarol:
Any way to change DPI via Synapse? It seems so robust. Also, any way to change pre-approved DPI? Synapse overlaps with the status bar and navigation bar when using 380 DPI which is what I find the most appropriate for this device.

Thanks in advance.
[ONE Original Android Development] ak:
This is good:

https://github.com/CyanogenMod/andr...mmit/ad268d45e9117e67612bcbb3594c0b1d49d331c5
[ONE Original Android Development] ak:
I think you have to post this on UKM thread.
[ONE Original Android Development] akarol:
Will give that a try. Thanks!

Anyways, any clue as to why we're getting the black horizontal line glitches still? Been present since 0.50 for me.
[ONE Original Android Development] ak:
No kernel related, you have to wrote to rom developer.
[ONE Original Android Development] tsouza:
So this is a compatibility problem between the kernel and cm11s 38R but the problem is in the rom?
[ONE Original Android Development] nicholaschum:
When was the latest commit for the display that caused graphic distortion released? I'm on latest Mahdi, but from this I'm guessing we'll need a newer Mahdi...
[ONE Original Android Development] akarol:
But people o different ROMs are experiencing the same issue. And when using Mahdi stock kernel, I don't have this problem. =/

---------- Post added at 12:31 AM ---------- Previous post was at 12:29 AM ----------

But I thought I saw this problem with 0.50 and the latest Mahdi as well. I could be wrong though.
[ONE Original Android Development] RobbieL811:
It's not showing an AK kernel zip? Idk what the module errors are. Never seen that. Did you set everything up like I told you? What branch are you compiling?

What's so great about that?
[ONE Original Android Development] prstorero:
Seems like the audio will process faster.
[ONE Original Android Development] Poesini:
Compiling ak-11.0 branch on anykernel repo and ak-11.0-gold on the other, otherwise is master
[ONE Original Android Development] RobbieL811:
You have the ramdisk, & kernel source in the same directory right?

Separate folders but both folders in the same directory.

Edit - I just cloned everything & tried a build. Worked just fine. You have something in your setup wrong. This is what it should look like:

Also, you need to edit the build script to reflect your paths like I said. Here is a screenshot of mine:
[ONE Original Android Development] wicked245:
Sorry for stupid q but i cant find any answers. What is difference between Cm11s and CM11? I see someone flash cm11 on stock 38R? Why we have CM11S kernel than?
[ONE Original Android Development] RobbieL811:
Don't flash 11 on 38R. Let everyone else do it. Don't be a follower! You are bound to have some kind of problems. That kernel is not designed to run on 38R. Flash 11s kernel on 38R, & 11 kernel on nightlies. That's the way they are intended. Those same people flashing 11 kernel on 38R will be back in here complaining about how something doesn't work or AK can you fix this...
[ONE Original Android Development] nadavar:
Hey AK,

I'm experiencing slower app cold start time on 61 and art.

Reverted back to 60 to check if I was imagining and some apps were much quicker to load there. Overall fluidity of both is extremely good besides that.

What setting might affect that? The crc?
[ONE Original Android Development] NOSTALGIA:
just flash the kernel directly on vanir? no special consideration ??
[ONE Original Android Development] poondog:
Use only a stylus to perform the install. Using a body part in the install will not work due to the different current output by your finger into the screen. It will lead to a short circuit, because of the ramdisk modifications in Vanir

Why they have this I do not know

This is not good in the middle of a flash

nah kidding but this has been asked before

Best to do a search

http://xdaforums.com/oneplus-one/orig-development/kernel-ak-t2832168/page383
[ONE Original Android Development] NOSTALGIA:
i knew it u were kidding.. made me nervous. hahahaha

thnx buddy.. too many pages.. cant really construct the exact words to type on the search field..
[ONE Original Android Development] poondog:
"Vanir"

lol :D
[ONE Original Android Development] toyota86:
Can I flash the zip with stock CM11S recovery?
[ONE Original Android Development] ak:
No
[ONE Original Android Development] ak:
I know, but i can't do anything, the problem is rom side.
[ONE Original Android Development] ak:
I dont know.
[ONE Original Android Development] drbest:
Use Rashr from the Google play store (root required). Its the best tool to flash a kernel or recovery direct on the device.

---------- Post added at 10:24 AM ---------- Previous post was at 10:04 AM ----------

@ak: your Kernel is exciting! Thank you very much for this excellent work.
[ONE Original Android Development] jgcaap:
Guys. Everyone having graphical glitches I need your help.

http://xdaforums.com/showthread.php?p=55718252

Follow this and send to me as quick as possible so that I can debug it together. Also give me the exact settings which you are using. Thanks.

---------- Post added at 12:05 PM ---------- Previous post was at 11:58 AM ----------

When you send this to me the glitches has to be passing around
[ONE Original Android Development] AcmE85:
You probably already know this, the glitches also appear with the stock cm11 nightly kernel.

For me, mostly when I am watching a video with MX Player or YouTube and switching back to homescreen via homebutton.

After the screen changes back from landscape to portrait orientation the glitches appear until I reboot or disable HW overlays.

I will try to send a log if it occurs again.
[ONE Original Android Development] jejemc:
hello ak your kernel running it on the 38R version of thank you to you.
[ONE Original Android Development] jgcaap:
Yes and let's discover a fix =p
[ONE Original Android Development] TheDynamiteGuy:
i cannot compile the kernel using SaberMod 4.9, it always come with error. with SaberMod 4.8 is compile just fine. is this the problem of SaberMod 4.9 itself? :confused:
[ONE Original Android Development] ak:
Its kernel related, you have to fix all errors.
[ONE Original Android Development] funCrash93:
indeed, guys, does AK have support for that.?

via what app it is possible to do that.? Trickster.? :confused:

edit : my guess is to flash UKM and install Synapse along side with the kernel, and under Gamma (if not mistaken) you have such option.

no.?

can someone correct me is wrong :)

Send from my bacon.
[ONE Original Android Development] ak:
yes right.
[ONE Original Android Development] mrsim:
or you can use this little APK here developed just for that problem

http://xdaforums.com/oneplus-one/development/dev-yellow-bacon-t2857616
[ONE Original Android Development] ak:
thanks its a pleasure.
[ONE Original Android Development] vassy.uk:
I'm on Latest Mahdi ROM n AK kernel. Can I use the rotate lockscreen feature as mentioned in this?

http://xdaforums.com/showthread.php?t=2855096
[ONE Original Android Development] jejemc:
I misspoke your kernel market it on the latest version 38R? thank you ;)
[ONE Original Android Development] ak:
yes with no problems. but i think is implented yet into rom.
[ONE Original Android Development] RukusX7:
I'm on liquid smooth currently. 2014-10-03.

Every ak kernel I've tried has been issue free for myself. Great work!

Sent from my Oneplus One ...mmmm... bacon.
[ONE Original Android Development] THUNDERASS:
Why is the ak kernel antutu score %10 lower than stock 38r?(i got 46500 on stock i got 41300 with ak)

it looks slower than stock..
[ONE Original Android Development] prstorero:
Who cares about benchmarks lol. As long as real world performance isn't taking a hit, it's not an issue. :)
[ONE Original Android Development] ak:
For me the kernel is superspeedy ... you cant compare because the configuration is different. :good:
[ONE Original Android Development] jgcaap:
It's because the entropy was tuned. Since then seems with lower benchmarks. Don't know yet to explain the reason. But soon I can give a good answer about it.

Edit:my guess would be more cpu use. But doesn't affect ui as it eliminates lags.. Which means is faster
[ONE Original Android Development] RukusX7:
Someone mind checking out synapse to see if the deadline scheduler has any values set, or they are at 0 for you as well.

Sent from my Oneplus One ...mmmm... bacon.
[ONE Original Android Development] XblackdemonX:
I'm not sure if this is what you are looking for?

read_expire: 250

write_expire:2000

fifo_batch:8

front_merges:1

writes_starved:1
[ONE Original Android Development] jgcaap:
That's a bad read on synapse app. The best would be to report this to the dev which created the app and ukm.
[ONE Original Android Development] RukusX7:
Mine was broken. No idea. Thanks for info

Sent from my Oneplus One ...mmmm... bacon.
[ONE Original Android Development] ak:
You have to fix some errors the kernel isn't compiled.

Sent from my A0001
[ONE Original Android Development] LarsPT:
Hey guys,

I think I need a little help here. I unlocked the phone, flashed recovery (TWRP), and flashed AK CM11S latest. Was this the wrong kernel? I thought the S was for the stock ROM. The phone won't boot.

I still got fastboot mode and recovery. What should I do? I'm gonna try and push another kernel with ADB. But if you have other suggestions I'm all ears.

Thank you!
[ONE Original Android Development] vassy.uk:
What ROM are u in? If stock cm11s else cm11.
[ONE Original Android Development] LarsPT:
I described exactly everything I did. So yes, I am in stock. So I guessed correctly that I should use the CM11S, but unfortunately the phone won't boot...
[ONE Original Android Development] chikimonke:
He's on Stock, but what version of stock are you on?
[ONE Original Android Development] LarsPT:
Or, in other words, it will stay forever in the 1+ Logo screen.

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

I don't know chikimonke, I got the phone yesterday...
[ONE Original Android Development] chikimonke:
Then you are probably on an older version of the Stock ROM, which the latest kernel will not work with. You're probably on 25R. Go here for legacy kernels, I believe the r38 CM11S kernel should work for you, but I'm not certain, keep going back to the next older kernel until you find one that works. Then once you can boot again, go to settings>about phone and look at your Build version. Also check for an OTA. If you want to make sure not to lose your custom recovery when doing the OTA, go into Developer Settings and uncheck the update recovery box. (tap on the build number in About Phone until you get a toast saying you are now a developer if you haven't done so already, to enable this menu) Once you have unchecked that box, go through with the OTA, then come back and get the latest kernel, though I think there is still some confusion as to which version you should flash on 38R (latest CM11S), [MENTION=3685904]ak[/MENTION] will need to clear that up :)

AK, maybe for your legacy kernels you can add what the latest version of CM11S they will work with to the file name, or really all the CM11S kernels? Just to help avoid confusion?
[ONE Original Android Development] LarsPT:
Thanks man.

I'm trying to push the kernel into the sdcard, but even if the device shows up when I do fastboot devices, I get a "device not found" error when I try to push into /sdcard/.

Any ideas?

Thanks so much.

---------- Post added at 05:50 PM ---------- Previous post was at 05:42 PM ----------

It looks like ADB doesn't work, but fastboot does, if this makes any sense... is it possible to flash the kernel via fastboot?

Thanks.
[ONE Original Android Development] chikimonke:
I'm not sure if fastboot recognizes /sdcard/ as that's not an actual location, it's really /storage/emulated/legacy/ (on my phone anyway) see if that helps. Or if you have an OTG USB cable you can use a flash drive and copy it over while in recovery (in TWRP anyway, I use this a lot, I find it easier, just have to mount OTG once in TWRP)

Edit, in answer to your edit, pull the boot.img out of the kernel zip and then you can

fastboot flash boot boot.img

Hmm, it seems OPO kernels are different, [MENTION=3685904]ak[/MENTION] or anyone else, can we fastboot an AK kernel?
[ONE Original Android Development] LarsPT:
Also can't find /storage/emulated/legacy/ (I get the same error:device not found)

I can't find boot.img in the kernel zip, only boot.img-dtb :(

(thanks again for your patience)

---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------

PS: No, unfortunately I do not have an OTG USB cable :/

But if you could point me to an .img of the whole stock image or something, that would be helpful, all I need is something I can flash with fastboot... :/ (I've been rooting and flashing ROMs for a while now... I guess I got too comfortable and didn't care to do a backup... nice lesson...)
[ONE Original Android Development] drp1:
Maybe the files posted by Vomer will help you? See this post.
[ONE Original Android Development] chikimonke:
Here's a whole post on fastboot flashing back to stock. That should give you everything that you need. Seeing that you just got the phone yesterday, I don't imagine there's much on there that you are worried about losing?

Factory images can be found at the bottom of this page, though they only have 33R not the latest 38R, so you'll still have to do the OTA afterwards.

---------- Post added at 11:08 AM ---------- Previous post was at 11:06 AM ----------

This option seems better, go with that and you'll be fully up to date.
[ONE Original Android Development] LarsPT:
Thanks so much everyone.

No [MENTION=2495716]chikimonke[/MENTION], your option was the good one. I flashed every file one by one and it worked. Thanks so much bro, if you ever come around Würzburg let me know, I'll buy you a cold one :)

---------- Post added at 06:22 PM ---------- Previous post was at 06:21 PM ----------

PS: Maybe it would be a good idea to clearly warn newbies (apparently, like me) that they should carefully check what version they are on before flashing? Or was I that careless? :(

Thanks again!
[ONE Original Android Development] osmosizzz:
Had a random reboot while watching a YouTube video. Log attached

Edit : log is too large for xda
[ONE Original Android Development] drdrewdown:
pastebin..
[ONE Original Android Development] Poesini:
Ok, I fixed the errors and I have compiled the kernel and I flashed it (9.4MB instead of 8.0MB, because of some flags that I have added), but I tried SM 4.9... I remember I don't know if it was here or in another thread that someone said that 4.9 was worse than 4.8... Is this true or not?
[ONE Original Android Development] kd8bny:
I have experienced many more compilation errors with 4.9 (Non-ak kernel)
[ONE Original Android Development] chipstien:
Can someone give a rundown of the differences in the Power Suspend Modes? Google came up empty handed and I really would like to know the specifics of LCD Hook, Highest Level Hook, and Kernel Mode. Thanks.