Search results

Szaki (Developer of the tool from post 5) has removed option for MIUI Cloud, so probably a good idea to keep that one for now. I think this is to prevent lock-out. I had a problem unable to use adb. Might as well post what fixed it for me in case it helps others: Disconnect USB between PC and...

Probably worth editing the OP play store link to make it identical to the above. Thanks for the guide.

Samt434 interesting, can you go into more detail about how you built the data partition image?

Which one, V7: https://goo.gl/n66DdG ?

Here's the stats: I've said before that I've had to run benchmarks many times over to get a reliable average. This time I was very concerned that the stock kernel was still out-performing my own build in stdlib copy operations. I tested stock vs Moxie 30 times. There were I think four or five...

I just leave all the tunables at their default settings, but the interfaces are available if you want to fiddle with them.

I'll have to take a look through their commits and see if there's anything I could make use of. Thanks for the heads up. BLX just limits the charge to a lower level so the battery won't last a long on any given day, but will stay healthier in the long run.

Yes mate, just like stock. So far I haven't seen the need to meddle with the CPU governors or hot-plugging.

I've managed to get a lot of performance back, but I'm really struggling to find the source of the huge drop in stdlib memmove and memcpy operations. Scores are about half that of Marshmallow. At this point I feel like I've tried everything, so perhaps the issue is more to do with the way the...

Download: here Version N7 Changed since v6: -Removed more debug stuff -a few more minor tweaks, see my git repo -fixed gestures The gesture fix actually required a section of code to be commented out. This is why it took me so long to fix. I was actually confused because the last time OnePlus...

I need some help with this one. Has anyone tried a custom kernel on 7.1.1 where touchscreen gestures work properly?

Thanks, I'll investigate

Here we go... Download: here Version N6 [Nougat] -Linaro 6.3.1 -Mainline to .48 final -optimised config (removed a lot of debug stuff) -a few other minor tweaks, see my git repo Cheers! EDIT: Okay, I forgot to mention that BLX is of course included, and Sultan's great tweaks that disable...

I've just installed 7.1.1 and got a basic kernel working. Big thanks again to NevaX1 for a problem free experience! I'll be publishing something in the next day or two.

New v12 Marshmallow kernel: https://goo.gl/2Sifs9 - Patched up to linux 3.18.48 - Brought in a large number of commits from ARM (check my github for the complete list) - Built with latest linaro 6.3.1 toolchain I've really been fighting the kernel since version 9, trying to work out what could...

I thought I'd sorted out the instability problem, then suffered a series of random reboots. Anyone else running my kernel with any F2FS partitions has probably suffered the same. (If so, let me know please?) v10 above was supposed to fix this instability, but obviously I was on the wrong track...

Good stuff, but looks like the kernel has not seen much love, still on .31

I'm using NevaX1's Freedom OS v1.7 (still on his server). Absolutely brilliant installation experience and no problems at all.

It's for stock ROMs only I'm afraid, if you already flashed this just dirty flash Sultan's ROM to restore the original boot image.

New v10 Marshmallow kernel: v10 removed If you want v11, please go here: https://forum.xda-developers.com/showpost.php?p=71306804&postcount=519 - Used some of the config options I developed for my uninspiring N release and managed to shrink it down to it's smallest ever size! - Figured out...

I'm still working on a refreshed M kernel. The first attempt a few posts up crashed on me, so I had to try to figure out what config option caused the problem. I believe CONFIG_DEBUG_INFO=y is a necessary setting, but I'm not sure why this would cause a random reboot. Any ideas anyone? EDIT...

I might throw my two cents in some other time, but for now, anyone who's back on (or never left) marshmallow might appreciate this: Edit: had a reboot so link removed, sorry! It's the same marshmallow kernel with some further debug stuff disabled, F2FS enabled, and rebuilt with the latest...

I'll stick with M until they release that. I need a consistent platform or I can't judge what impact my changes are having

Haha I was only joking. I was already back on Marshmallow when I posted that :p

I'm going back to marshmallow :D

I can't, but admittedly I'm not very good at interpreting the OS logs. At any rate, I've set the kernel build to be as high performing as possible, so nearly of the kernel debug logging is disabled, so even if this is a kernel error, it'd be nearly impossible to identify why. Try another kernel...

Did the phone hard reboot, i.e. reboot to the bootloader menu?

Ah, I wish I could find the time. I'm happy with the OEM android experience, but who knows... in the future I may switch over.

Thanks very much! I saw a lot of downloads from Russia!

Thanks again to Mostafa Wael for that interesting summary. I'm not a ROM guy, so this was all news to me! Anyway, I just thought I'd pop in to drop a minor update: https://goo.gl/MgxgDB It may interest some people as it's been built with the newly released linaro 6.3.1 (read the release notes...

I got a bit of time to myself today to do some benchmarks that I've been meaning to get around to for a while, Moxie (linaro toolchain) vs Moxie (google toolchain) vs Stock. Back near the beginning of January I'd already established that there were some tests I could run in Geekbench2 with a...

Yep it is, so we'll stop seeing official patches for security and maintenance, but kernel devs here will continue to support the device. I'll happily backport any critical security patches as they are released upstream.

N5 just above is now mostly synced with it, but 4.0.3 was only a minor code drop anyway.

Version N5 is here I've merged in the 4.0.3 source drop from OnePlus but I'm not happy with some of the code, so I've rolled back part of the update. Here's the commit: https://github.com/bedalus/oneplus3kernel/commit/e1983709a29db05ff8e38fb7ad534eff5785f475 There's no reason for them to be...

I think there is no chance that we'll see a 4.x kernel that will boot to a fully working OS. It's just too much work to forward-port all the drivers.

Version N4 is here I've merged in 3.18.48 but also had a good look at google's marlin branches and brought in commits from there too, since they're on msm hardware and at the 3.18.y kernel level, there's a lot of compatible updates. This isn't the complete list of commits as I've tried to...

Version N3 is here - Brought config in line with latest arm specification from android common - Committed more patches from android common, mainly updates for ext4, sdcardfs and ARM64 specific fixes Testing_N is the branch you want to look at for the full list of changes. Since this release...

Ah, I think finally understand what happened in N. It's all here: https://source.android.com/devices/tech/dalvik/jit-compiler.html We're possible dealing with a few things here (and I'm just doing some benchmarks as I write this to shed some light). We've got Oneplus with code that boosts...

How'd you get on with the wakelocks?

Mostafa Wael ah yes, I do remember reading that the first time. I'm using geekbench 2.

I just tested and got near identical scores to my M kernel. How much higher was stock?

test kernel I've built one with franco's commits for the wakelocks. Do you want to give it a try? There's also a bunch of other stuff in there (all the upstream stuff from android common that was in the v9 marshmallow version). I think I know what's causing the volatile benchmark results. I...

Ah thanks. I'm very impressed, but I don't think anyone should hold their breath. There's probably a lot of drivers that still need porting to get a functioning android system.

Guys, I noticed that my benchmark app was being affected badly by the Kernel Adiutor app. I'm no expert on the OS side of things. Did something change from M to N in app behaviour?

I just quickly tried to find some mention of that in his thread, all I'm finding are references to things being backported from later kernels. Can you provide a link to where he's said this? If not, don't worry, I'll PM him.

I think there's something up with it, the benchmark scores are low and volatile too. I'm not sure what the cause is yet, but appreciate the testing!

I think they're all necessary wakelocks, aren't they? Headphone jack makes sense, wlan is the wifi hardware, and ipa is part of networking. Someone correct me if I'm wrong?

I'm about 5 miles north of Chester, it's quite rural around here!

Yes, sorry, it's supposed to be 3.18. Incidentally there are usually benefits to upgrading to a newer kernel version, so long as your hardware is still supported. The problem we have with 3.18 is that it won't be supported for much longer as it is near the end of its LTS life. I think it's...

Left my phone off the charger last night to test: Seems like it's back to normal on vN2. That flat line is when I went to bed!