Develop Bugs

How can you tell which kernel you are currently running?

A forum search turned up nothing, so I'm asking here:
On most Android phones, you usually go to Settings->About Phone and look under the "Kernel Version" section to see the name and version of the kernel you are running.
With my Galaxy Nexus, I don't see kernel names. Instead, I see something like:
Code:
3.0.31-g6fb96c9
[email protected])
#1 SMP PREEMPTY Thu Jun 28 11:02:39 PDT
2012
No matter which kernel I flash, it always seems like the same type of info but no names or version numbers.
I was okay with that as long as I remembered what I flashed last. However, I recently reverted to stock but the kernel looks like it stayed the same. Is there anyway to check if I'm back on stock kernel or still running the last kernel flashed (franco, in my case)?

I'm running leankernel 4.3.0 it says the version
Sent from my Galaxy Nexus

drdoombot said:
A forum search turned up nothing, so I'm asking here:
On most Android phones, you usually go to Settings->About Phone and look under the "Kernel Version" section to see the name and version of the kernel you are running.
With my Galaxy Nexus, I don't see kernel names. Instead, I see something like:
Code:
3.0.31-g6fb96c9
[email protected])
#1 SMP PREEMPTY Thu Jun 28 11:02:39 PDT
2012
No matter which kernel I flash, it always seems like the same type of info but no names or version numbers.
I was okay with that as long as I remembered what I flashed last. However, I recently reverted to stock but the kernel looks like it stayed the same. Is there anyway to check if I'm back on stock kernel or still running the last kernel flashed (franco, in my case)?
Click to expand...
Click to collapse
Most (if not all) kernels have a name similar to stock. But there is usually something amongst the numbers and letters which point to what kernel your running.
For instance my phone running trinity.
I know its trinity because it says dirtymorfic, morfic being the xda name of the trinity kernel developer. I only use stock kernel and trinity so can't comment on the others, but it will always look similar but also always have something pointing to the kernel your using. Hope this helps
Sent from my Galaxy Nexus using Tapatalk 2

Also typing code below in terminal will give you some more bits of info.
Code:
cat /proc/version
good day.

question
sir i want to ask 2 questions :
my phone specifications after flashing jelly blast v2 are:
android version:4.1.1
baseband version :S5360DDLC2
KERNEL VERSION : 2.6.35.7 [email protected]#1
BUILD NUMBER :NXT2ICSv2:jelly blast
1.i want to install jelly blast v3 what i have to do?
2. installing a custom rom change a kernel version or not ?

sunil332011 said:
sir i want to ask 2 questions :
my phone specifications after flashing jelly blast v2 are:
android version:4.1.1
baseband version :S5360DDLC2
KERNEL VERSION : 2.6.35.7 [email protected]#1
BUILD NUMBER :NXT2ICSv2:jelly blast
1.i want to install jelly blast v3 what i have to do?
2. installing a custom rom change a kernel version or not ?
Click to expand...
Click to collapse
Why did you bump a thread that's months old, and you don't even have our device?
Sent from my Nexus

a small doubt about sony xperia z ultra
there is a date under the kernel.
but that is not the same as the date of purchase
date of purchase is june 12 2015 at 12pm
date in the kernel is june 12 2014 at 2pm
am i being cheated with an old or used phone?
also the video clarity is very bad for a FHD screen
help me please

mnanoop said:
there is a date under the kernel.
but that is not the same as the date of purchase
date of purchase is june 12 2015 at 12pm
date in the kernel is june 12 2014 at 2pm
am i being cheated with an old or used phone?
also the video clarity is very bad for a FHD screen
help me please
Click to expand...
Click to collapse
1. Kernel and rom are developed much earlier, you weren't cheated.
2. Video clarity? Do you mean the video recording quality or the screen quality?

im running cm12 (android 5.1.) on my lg d855 right now, and it shows my kernel version in the "about phone" category.

Defy Custom Kernel Thread[2nd boot source released][Test Kernel released]

OOk guys so I found this thread which shows MS2 got a custom kernel. The proceduce is bit difficult but can be modified for working for Defy too.
Hope has struck back again.
http://forum.xda-developers.com/showthread.php?t=1908687
Update: 2ndboot module sources are here:
https://github.com/czechop/2ndboot
Quarx puts his kernel here:
quarx2k.ru
Sdcard symlink Fix:
http://forum.xda-developers.com/showpost.php?p=32428611&postcount=392
Thanks to walter.
-------------------------------------------------------------------------------------------------------------------------------
BIGNOTE: Green lens users who flashed redlens builds please dont try using flash, you will end up burning it like me and many others.
STEPS TO FOLLOW WHEN YOU HAVE BOOTLOOPS OR BLACK SCREEN WITH RED LED ON:
-1st of all set default boot to 2nd-boot
-Go to recovery and flash the 24.9 build
-Then flash the kernel 6.10
-After that flash the latest build
-Wait and you will have your phone working proper.
For Bl7 users:
kozaks said:
If your current kernel is 2.6.32.9-ge281b6e [email protected]#1 then the custom kernel won't boot. To get it boot, you need to flash the kernel shared by our friend. Post flashing your kernel should be 2.6.32.9-ge281b6e
[email protected]#1. Once this is confirmed go ahead and flash tbw custom kernel as defined in the first page. Should be good to go.
Link to 51#1 kernel.
http://forum.xda-developers.com/showthread.php?p=32538963
Click to expand...
Click to collapse
-------------------------------------------------------------------------------------------------------------------------------
A suggestion made by a member:
rodrigojfuentes said:
Hey, I just read in this post that flashing gapps before the kernel may prevent the kernel from successfully booting. I tried it and it worked fine. I think you should advice that in the OP
Click to expand...
Click to collapse
-------------------------------------------------------------------------------------------------------------------------------
FOR SIMUNLOCK:
Redhotero said:
Dont know if it's OT or what, but helped me a lot.
This is for the people who wants "sim unlock" in quarx 10/10
1- Download this rar http://forum.motofan.ru/index.php?act=Attach&type=post&id=243798
2- Paste bp_ptc in /system/bin
3- Paste init.mapphone_umts.rc in /system/bootmenu/2nd-boot
and then:
Credits to crakeron, labsin, Dabb and all the people who helped. Im just the messenger,
PD: sorry for my english and sorry if it was posted before
Click to expand...
Click to collapse
-------------------------------------------------------------------------------------------------------------------------------
Feature request for next kernel:
-OTG cable support
- FM transmitter capability Link(requested by amirali_b)
-Sim unlock support(requested by Redhotero)
-Wifi-direct(requested by mdsaif92)
(pm me to add other features)

Waiting for someone to compile a kernel so we can test
Sent from my MB525 using xda app-developrs app

hsrars-d said:
Waiting for someone to compile a kernel so we can test
Sent from my MB525 using xda app-developrs app
Click to expand...
Click to collapse
u can try currently available kernels just to try!
To see if the scripts and modules work xD
M sure they wont work right away

+Really great news
I tried boot my kernel with it (not booted, but log is good).
Waiting for source code and changes in kernel for 2ndboot
http://pastebin.com/jKjQ2ykn
In future i think we can make one kernel for defy and defy+

so just to clear things up for noobs like me: does this mean we could have a jellybean kernel, or is this still gb? and functions like wifi direct which need to be built in the kernel are possible now?
sent from my cm7 defy...

zakoo2 said:
so just to clear things up for noobs like me: does this mean we could have a jellybean kernel, or is this still gb? and functions like wifi direct which need to be built in the kernel are possible now?
sent from my cm7 defy...
Click to expand...
Click to collapse
It means we could use custom kernels.
I think that a developer could even port 3.0.x kernel on defy, if everything 'll go fine.

We may get swap support!(many more things)
Swap is really imp for us since 512MB ram is not enough for jb
Hope Quarx gets it working
Also does kernel version really matter?
I mean if an older kernel is working perfectly and has all ROM features working,why not use that only(2.6.35)
Also I dont think Defy's hardware supports WifiDirect
Sent from my MB526 using xda premium

It seems our sweetoldlittle Defy just won't get outdated soon! Great news, great devs
Sent from my MB525 using xda app-developers app

It works for defy, but unstable for now
http://forum.xda-developers.com/showpost.php?p=32120862&postcount=21

take your time quarx.we are patient it's an amazing news

Custom kernel from sources works too
Linux (none) 2.6.32.9 #1 PREEMPT Fri Sep 28 14:11:14 MSK 2012 armv7l GNU/Linux

Quarx said:
Custom kernel from sources works too
Linux (none) 2.6.32.9 #1 PREEMPT Fri Sep 28 14:11:14 MSK 2012 armv7l GNU/Linux
Click to expand...
Click to collapse
so finally , can we think of DSSCOMP , ION and hwcomposer ?
i know it too early to ask this question
but m very eager to know the answer from quarx

So it means we will have in near future new kernels and possibilty to brick Defy completly ? Or still Defy will be unbrickable and with new kernel

wifibdirect is a sofrware thing, not hardware. the defy would be perfectly capable, but we couldnt load custom kernels (until now).
sent from my cm7 defy...

sebx_g1 said:
So it means we will have in near future new kernels and possibilty to brick Defy completly ? Or still Defy will be unbrickable and with new kernel
Click to expand...
Click to collapse
As far as I understand from this is, the bootloader is still the same, so you still always be able to resurrect your defy with the stock sbfs :cyclops:

Quarx, I can't believe you are just one person... I mean, the progress you've done on the Defy in such a short time is really amazing!!! If the custom kernel gets developed half fast the speed of your mods, our little phone will be a blast pretty soon!!!

Can't Boot
Quarx said:
Custom kernel from sources works too
Linux (none) 2.6.32.9 #1 PREEMPT Fri Sep 28 14:11:14 MSK 2012 armv7l GNU/Linux
Click to expand...
Click to collapse
Can't boot, when i try 2nd boot, defy stuck on black screen 10 to 20 seconds, and reboot :crying:
I don't know why....

I suppose you followed the milestone 2 method directly.
Quarx has not released anything (afaik), and its not intended to users at this staqe.

dumb
hsrars-d said:
I suppose you followed the milestone 2 method directly.
Quarx has not released anything (afaik), and its not intended to users at this staqe.
Click to expand...
Click to collapse
I think quarx boot the mm2 method on defy directly... im dumb

Boss442 said:
I think quarx boot the mm2 method on defy directly... im dumb
Click to expand...
Click to collapse
Yes he did that first, then he modded it and got it to boot. :victory:

We need one real update...

Hallo i watch all this roms... They are all 4.2.2. In the sort time adroid L its out... And i have the big question when we have one real update ??? I have this phone 9 months until now i live in eu

gkm8123 said:
Hallo i watch all this roms... They are all 4.2.2. In the sort time adroid L its out... And i have the big question when we have one real update ??? I have this phone 9 months until now i live in eu
Click to expand...
Click to collapse
100% agree but unfortunately duo to mate 2 is out they have no plan to update mate1 to 4.3 or 4.4:crying:
i really think ham is good phablet and deserve better support from manufacturer.

mazi_v said:
100% agree but unfortunately duo to mate 2 is out they have no plan to update mate1 to 4.3 or 4.4:crying:
i really think ham is good phablet and deserve better support from manufacturer.
Click to expand...
Click to collapse
This kind of support let me turn away from Huawei. A pitty. But i want decent support. A phone schould get 2 year regular updates. Thats wat a customer deserves

Well you'll have to dive deeply into it to do the job of building a custom Android ROM. I just downloaded the kernel sources from the official JB (4.1) release, but I'm not sure how far I can get with that. Some experienced devs here posted that they would need Huawei's sources for KitKat to build a KitKat ROM, but I also have an Ascend P1 and I'm running a custom KitKat CyanogenMod build from the forums here although Huawei only released ICS (4.0) Kernel sources. I will have a try with a custom cross compiling toolchain of mine that I use for my Radxa Rock, but it's quite generic. I'll let you know how far I could get if at all.
Cheers!

The kernel build was successful, but I've simply used Google's latest toolchain (arm-linux-androideabi-4.6-android-4.4.4_r1). I'm now syncing the most recent Android repo, that will take some time. I will try to set everything up to start compiling tomorrow morning or something...
Just in case you want to build the kernel yourself as well: There is an indentation issue in one of Huawei's Makefiles for the touchscreen, you'll see an error message about it if you run the first make according to the README_kernel.txt. You can just add tabs and your file should look like this:
[drivers/huawei/device/touchscreen_Mate/Makefile]
Code:
[COLOR="DarkOrange"]#
# Makefile for the touchscreen drivers.
#
# Each configuration option enables a list of files.
obj-y += synaptics_i2c_rmi.o
obj-y += rmi_dev_6.o
obj-y += rmi_f54_6.o
obj-y += rmi_fw_update_6.o
all:
make -C /lib/modules/$(shell uname -r)/build M=$(PWD) modules
clean:
make -C /lib/modules/$(shell uname -r)/build M=$(PWD) clean[/COLOR]

CyReVolt said:
The kernel build was successful, but I've simply used Google's latest toolchain (arm-linux-androideabi-4.6-android-4.4.4_r1). I'm now syncing the most recent Android repo, that will take some time. I will try to set everything up to start compiling tomorrow morning or something...
Just in case you want to build the kernel yourself as well: There is an indentation issue in one of Huawei's Makefiles for the touchscreen, you'll see an error message about it if you run the first make according to the README_kernel.txt. You can just add tabs and your file should look like this:
[drivers/huawei/device/touchscreen_Mate/Makefile]
Code:
[COLOR="DarkOrange"]#
# Makefile for the touchscreen drivers.
#
# Each configuration option enables a list of files.
obj-y += synaptics_i2c_rmi.o
obj-y += rmi_dev_6.o
obj-y += rmi_f54_6.o
obj-y += rmi_fw_update_6.o
all:
make -C /lib/modules/$(shell uname -r)/build M=$(PWD) modules
clean:
make -C /lib/modules/$(shell uname -r)/build M=$(PWD) clean[/COLOR]
Click to expand...
Click to collapse
A kitkat kernel that would make you in my opinion almost immortal for Mate users

henk_j said:
A kitkat kernel that would make you in my opinion almost immortal for Mate users
Click to expand...
Click to collapse
We'll see, I'm still learning about the stuff, but the chances look quite fair. I've set up the rest of the environment and the build is running now. But I guess it will take some more hours. I usually need about 3.5 hours to build chrome, firefox or libreoffice. AOSP should be similar. I'll see how far it got today evening/night. But for now it looks good, I'm running with -j4 as recommended. ^^

CyReVolt said:
We'll see, I'm still learning about the stuff, but the chances look quite fair. I've set up the rest of the environment and the build is running now. But I guess it will take some more hours. I usually need about 3.5 hours to build chrome, firefox or libreoffice. AOSP should be similar. I'll see how far it got today evening/night. But for now it looks good, I'm running with -j4 as recommended. ^^
Click to expand...
Click to collapse
if you have more cores processor why dont increase the thread value so that build process will complete more quickly

svvv said:
if you have more cores processor why dont increase the thread value so that build process will complete more quickly
Click to expand...
Click to collapse
I have 2 cores, so 4 is quite fine. The next option would have been 16.

Take your time! we need more developers

Any news ?

Really appreciate the works here.
so many had forgotten Mate 1 and P6 since 2 & 7 came out...
For me the first editions are always the best although the the 2nd might have little differences or improvements (but always have flaws or bugs more than the 1st editions)..
so very much grateful and thanks for devs that spent their time looking at mate 1 and p6...
Will donate if theres any need for it..count on me for that..
[email protected]

gkm8123 said:
Any news ?
Click to expand...
Click to collapse
Come on, I'm writing every couple of hours...
Well, the news is: v8 failed in some point. I've just resynced the AOSP repo to start over. ^^ I'll let you know how it went today evening. I also have a job, you know.

CyReVolt said:
Come on, I'm writing every couple of hours...
Well, the news is: v8 failed in some point. I've just resynced the AOSP repo to start over. ^^ I'll let you know how it went today evening. I also have a job, you know.
Click to expand...
Click to collapse
Ok no problem, thank so much for your help

Well, the newer patches didn't resolve the issue so I decided to try the normal user build (I tried a full debug build first). For now it looks very promising. I'm not sure if I can figure out how to to fix the issue I had, so if this one fails at the same point (although as far as I understood it was one of the debug parts so it shouldn't), it might get a little harder. We'll see ^^

thank you mate.. i mean CyReVolt.
i hope ur doing ok with ur job also,, and really hope u give us a good news..

cumanisengdoang said:
thank you mate.. i mean CyReVolt.
i hope ur doing ok with ur job also,, and really hope u give us a good news..
Click to expand...
Click to collapse
Sure, np... actually, it failed again due to the same problem, and I quickly figured out the cause (I already had suspected that): I'm on a strongly hardened Linux system, and the
Code:
mksnapshot
tool was killed due to NX protection (see http://wiki.gentoo.org/wiki/Hardened/PaX_Quickstart#Understanding_PaX). So if you're running a PaX protected kernel or similar you might run into the same issue. Duh... -.-
It's up and running again, so let's wait for a result!
While waiting you can try the Android kernel I have attached. Don't ask me how to do that. I have no clue. This is just for fun. And for you!
Considering work: It was actually quite funny today because I had to work on a Mac and OSX feels just horrible to me. My boss asked me to take a glance at Xcode and especially the new beta and Swift. I'm so glad to be back at my Linux machine now.

CyReVolt said:
Well you'll have to dive deeply into it to do the job of building a custom Android ROM. I just downloaded the kernel sources from the official JB (4.1) release, but I'm not sure how far I can get with that. Some experienced devs here posted that they would need Huawei's sources for KitKat to build a KitKat ROM, but I also have an Ascend P1 and I'm running a custom KitKat CyanogenMod build from the forums here although Huawei only released ICS (4.0) Kernel sources. I will have a try with a custom cross compiling toolchain of mine that I use for my Radxa Rock, but it's quite generic. I'll let you know how far I could get if at all.
Cheers!
Click to expand...
Click to collapse
The main problem is not the kernel. We can build a kitkat rom with the 3.0.8 kernel , but we have no source for display part , audio part. We have to use the prebuilt hwcomposer , grallloc etc. . These prebuilt libs are compatible only with the android version of the stock rom they are coming from and with the kernel they are patched for.
With sources of display driver we can patch the kernel and the driver to work on KK . Like I did JB on ZTE V11,V71,V55 tablet with 2.6.35 kernel , but that device was QC based device with available display driver sources. (http://forum.xda-developers.com/showthread.php?t=1629630)
I have compiled a 4.3 rom for mate , but I am stuck at display. There are changed routines in framework which are not working with 4.2's display drivers . One solution can be to get these sources , or to change the framework to work with the 4.2' display driver.
The Mate is my first non QC chipset based device , but also the last too. This is my fourth device from Huawei and until now I was satisfied , they simply do not care Mate customers. The release of the KK for Mate is just a few hours job , but they wont do it.

joe.stone said:
The main problem is not the kernel. We can build a kitkat rom with the 3.0.8 kernel , but we have no source for display part , audio part. We have to use the prebuilt hwcomposer , grallloc etc. . These prebuilt libs are compatible only with the android version of the stock rom they are coming from and with the kernel they are patched for.
With sources of display driver we can patch the kernel and the driver to work on KK . Like I did JB on ZTE V11,V71,V55 tablet with 2.6.35 kernel , but that device was QC based device with available display driver sources. (http://forum.xda-developers.com/showthread.php?t=1629630)
I have compiled a 4.3 rom for mate , but I am stuck at display. There are changed routines in framework which are not working with 4.2's display drivers . One solution can be to get these sources , or to change the framework to work with the 4.2' display driver.
The Mate is my first non QC chipset based device , but also the last too. This is my fourth device from Huawei and until now I was satisfied , they simply do not care Mate customers. The release of the KK for Mate is just a few hours job , but they wont do it.
Click to expand...
Click to collapse
Thats why we have to get some sense into their heads thats trough they're Wallet. The only way tot make them do this strangely by hurting them where it counts.

Alright, I'm getting the point now... so I did some research.
The GPU is a Vivante GC4000, so might this help https://github.com/laanwj/etna_viv ?
I wouldn't mind the sound at first. I would love to work on this somehow.
Can you point out which files I should look at? I know a bit about the ARM/Thumb ISA, so I'd try to reverse engineer a little to either adjust the pre-built drivers or the framework using them. =) I don't give up very quickly, you know! Finally, I'd just contact Huawei and talk straight to them. Thanks in advance for all your efforts.
Cheers
CyReVolt

[TW][5.0.1][AndromedaKernel][SM-N910F][Abandoned]

Andromeda Kernel
Supported: SM-N910F & SM-N910V
Do not try to flash this on ANY other variant than the N910F (Snapdragon, European)! It might work, but it can fail and end in a bootloop! Testers for SM-N910G wanted!
Disclaimer
Your warranty is now void.
We are not responsible if your phone will be damaged, broken, bootlooping or detonating in a thermonuclear reaction.
YOU are choosing to make these modifications and accept the fact that something might go wrong.
Click to expand...
Click to collapse
About me and Andromeda / Philosophy
Andromeda Kernel was created by a madman who tries to combine raw power, stability and batterylife in his high-tech laboratory home. IÄm not doing compromises and will always listen to every feedback and feature request!
Click to expand...
Click to collapse
Index
OP Post: About the kernel, basic changelog, Download, Credits
Post 2 : Changelog Preview + Development Status, FAQ
Post 3 : Known Issues, Fixes and Updates about pending fixes
Post 4 : Reserved for future use (Better safe than sorry, right? )
Features:
# Based on Samsung OpenSource Kernel XXU1BOB4
# SeLinux Permissive
# Linux version 3.10.40
# Overclocking and Underclocking (268mhz - 3,07Ghz)
# Governors: Intelliactive, Bluactive (more to come...)
# Compiled with GCC Linaro 4.9.3 Cortex A15 (03.2015) [/CENTER]
Click to expand...
Click to collapse
Changelog
Andromeda Stable 2.1
- Overclock and Underclock (268mhz - 3,07Ghz)
- Kernel NEON mode implemented
- Added KCAL Color Control (v2)(Controllable from KControl or this app: http://downloads.codefi.re/savoca/kcal)
- IntelliPlug is disabled for now (Great change, I know lol)
- Brandnew IntelliThermal from faux *yay*
Andromeda Stable 1.0
- FauxSound 3.6 fully integrated
- IntelliPlug 4.0
- Enhancements and battery optimizations
- Renamed the Kernel in the settings, the last one was a disaster http://forum.xda-developers.com/for...xda-developers.com/images/smilies/biggrin.gif
- 57% Support with KControl currently (Playstore App)
Andromeda Milestone 1.0.0 (Public Release)
- Based on BOB4 Stock kernel
- Added Bluactive and Intelliactive governors
- SeLinux Permissive (Try viper4Android, it's great!)
- Compiled with Linaro 4.9.3 Cortex A15
Click to expand...
Click to collapse
Please check Post Nr.2 for the list of features to be included!
Downloads:
Important: Do NOT make mirrors please! If you want one, please request it. Unofficial mirrors found will be reported, please respect this.
http://d-h.st/tNu1 (Stable 2.1)
Click to expand...
Click to collapse
How to Install
You have to have a custom recovery like TWRP, Philz or CWM installed.
- Download the kernel
- Reboot to recovery
- A backup is always recommended
- Flash the zip file
- You're done! Reboot and enjoy.
Credits:
Pafcholini - If it weren't for you, we'd be stuck at compiling or somewhere else. Massive Thanks for helping, guiding and having incredible patience with my incompetence
Psycho_666 - For boldly flashing what no one had flashed before and for continued support. Try SimpleRom it's an awesome ROM. And there's a new version to be launched soon, with a specially built SimpleKernel, derived from Andromeda
*To be updated in the future*
Rsroms- For being the most fearless Tester there is on the world, thanks for the massive help!
XDA:DevDB Information
AndromedaKernel, Kernel for the Samsung Galaxy Note 4
Contributors
mythos234
Source Code:https://gitlab.com/mythos234/AndromedaN910F-LL/
Kernel Special Features:
Version Information
Status: Abandoned
Current Stable Version: Stable 2.1
Stable Release Date: 2015-03-30
Beta Release Date: 2015-03-17
Created 2015-03-17
Last Updated 2015-05-08

Changelog Preview / FAQ
Changelog Preview
To be included in next build (Andromeda_Stable_V1)
# Synapse Support (Use Trickstermod Pro or Kcontrol for now)
# IntelliPlug 4.0 (make it work finally.. Sorry for the screwup)
# Voltage Control
# Support for the N910T (T-Mobile Variant)
#
# Enhancements and battery optimizations
Click to expand...
Click to collapse
Feature requests are always welcome and highly encouraged! Just as reviews and feedback
Benchmarks:
Just how fast is this kernel? Well, this should answer it:
Frequently asked Questions (FAQ)
Or Questions and answers, since this thread is new.
Q: Can this be flashed on the Exynos Note 4?
A: No, by no means. The Exynos model is completely incompatible, sorry.
Q: And what about other Snapdragon versions?
A: I can't advise to do that, it's untested and might not work. If you know how to handle bootloops and can remove my kernel if it doesn't boot, then you can always try it and tell me how it went. More variants would be awesome.
Q: Yikes, this kernel is too close to stock! What about more features?
A: More features will be included, please check the changelog preview. You can also request features and track the progress. I will make a section on this thread to display the feature request and write if I look at them, make them or - and that might happen - reject them.
- To be updated..

Known Issues / Fixes
Bootloop if you have Viper4Android installed and flashed Andromeda over it
Fix: Uninstall Viper, install Andromeda and then reinstall.
If this issue persists in my future builds, then I'll add an automated script to remove Viper4Android upon installation of the kernel.

Welcome Aboard Mate Good luck Stefan.

G is on kk how to test it. Kernel mentioned as 5.0.1
Sent from my SM-N910F using XDA Free mobile app

bhasg1007 said:
G is on kk how to test it. Kernel mentioned as 5.0.1
Sent from my SM-N910F using XDA Free mobile app
Click to expand...
Click to collapse
Still on kk? Samsung is slower than I thought lol... Thanks for letting me know, edited the thread. Probably better to try it when G receives official 5.0

Seems like a great Kernel, good luck buddy

Going to test on my n910t after work. Ktoonsez is the only booting kernel so far for TW5.0 but we have a data issue

Welcome thanks for the work: Bueno:

Hey stefan, great work, can i use it with simplrom, although i am happy with nadia

Rsroms said:
Hey stefan, great work, can i use it with simplrom, although i am happy with nadia
Click to expand...
Click to collapse
Hi, yes of course you can! We are actually working on deeper and more exclusive support for SimpleRom too. Stay tuned for version 2.1, it will be awesome
My kernel is much closer to the stock base, so you might get some more performance squeezed out - especially if you select Intelliactive as your governor - but at the cost of battery. I'm still not so big on features, the last couple of days my compiler decided to give me a hard time :crying:
Only 910F for now though!

this kernel is the best one for note 4 it is soo fast
nadia kernel not good lag soo much

rowihel2012 said:
this kernel is the best one for note 4 it is soo fast
nadia kernel not good lag soo much
Click to expand...
Click to collapse
same devs in this kernel like nadia , hahahahaha nadia kernel lag , boy, you need to read more before posting

ManDone.vRs said:
same devs in this kernel like nadia , hahahahaha nadia kernel lag , boy, you need to read more before posting
Click to expand...
Click to collapse
I'm not part of their Team, but Pafcholini is teaching me Don't worry, this kernel is not a clone of Nadia. My newest and upcoming build is as fluent as the last one and the batterylife is holding up a ton better too. No compromises on either side, thats my motto!

mythos234 said:
I'm not part of their Team, but Pafcholini is teaching me Don't worry, this kernel is not a clone of Nadia. My newest and upcoming build is as fluent as the last one and the batterylife is holding up a ton better too. No compromises on either side, thats my motto!
Click to expand...
Click to collapse
yeah stefan i know , but when i see a reply from unknow users and said : x kernel got lag , y kernel so bad , hey ! wake up ! need to read more than 1 week to know about a custom kernel Cheers compi .

ManDone.vRs said:
yeah stefan i know , but when i see a reply from unknow users and said : x kernel got lag , y kernel so bad , hey ! wake up ! need to read more than 1 week to know about a custom kernel Cheers compi .
Click to expand...
Click to collapse
Haha, I know what you mean I love the compliment, but I know as well as you do, that Nadia doesn't lag, unless the Synapse settings are set wrong. Too bad that my attempts at Synapse aren't going so great atm..

Hi, this kernel is compatible with BOC3 version, of Lollipop netherland??? Thank u

xxxfirenzexxx said:
Hi, this kernel is compatible with BOC3 version, of Lollipop netherland??? Thank u
Click to expand...
Click to collapse
This kernel is compatible with F version

xxxfirenzexxx said:
Hi, this kernel is compatible with BOC3 version, of Lollipop netherland??? Thank u
Click to expand...
Click to collapse
Yes, it is. I don't know what changes Sammy made to the BOC3 kernel yet, so mine might be a bit slower than the BOC3 stock one. But it works with the version just fine

Andromeda Stable 1.0 released!
Good evening everyone,
it took me a while, but I present you the first Stable build of Andromeda!
Changelog
- FauxSound 3.6 fully integrated
- IntelliPlug 4.0
- Enhancements and battery optimizations (mainly centered around powersuspend and adaptations to the default interactive governor)
- Renamed the Kernel in the settings, the last one was a disaster
- 57% Support with KControl currently (Playstore App)
Click to expand...
Click to collapse
About the Overclocking and Synapse...
I originally intended to include both in this build, but it will still need much more time and work and I didn't want to keep you away from the great upgrades I made in this version, so those two goodies will come later. I can highly recommend trying TricksterMod and KControl, both from the PlayStore.
And a very special announcement...
Perhaps the biggest change is that I recently joined "Team Simple - Simply Awesome" cool and will contribute an adapted version of the Andromeda kernel to SimpleRom, starting with the very close release of it's 2.1 Build. We planned something special - FauxSound is only the cherry on the Audiophile package inbuilt, so be very excited for whats coming up and be sure to try SimpleRom, especially the upcoming 2.1 version!
Oh, btw. I will also open a thread for the SimpleKernel once the Rom is released, to provide an optimized yet very close to stock experience! And there are also plans for an Exynos Build (the N910C), but I need some help with the Exy, so if anyone could lend me a hand, it would be highly appreciated! Now I understand why most devs settle for the Snapdragon..
Link to SimplRom: http://forum.xda-developers.com/note-4/snapdragon-dev/rom-simplrom-v1-t3004628
Download for Andromeda Stable 1.0:
http://d-h.st/TBO4
Click to expand...
Click to collapse

Xiaomi has released the Mi Pad's kernel source code!!!

Finally!!!
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/mocha-kk-oss

Finally, now xda can see some updates/threads for mipad

Kage Yume said:
Finally!!!
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/mocha-kk-oss
Click to expand...
Click to collapse
What a good news!. I Hope someone will already working in a newer ROM for Mi Pad ...

Hello,
This is a good news!!!
Hope some developers start playing with it.
Kind regards.

nah, this monster did not survive. let it be. no one care mi pad already. release sources 2 and a half years is rubbish. forget about it.

ChooiWC said:
nah, this monster did not survive. let it be. no one care mi pad already. release sources 2 and a half years is rubbish. forget about it.
Click to expand...
Click to collapse
I agree you.**** Off Xiaomi.
Sent using XDA One

The important question is.. how broken is it?

Had to make these changes to build it. Yet not boot-able.
Makefile
-Werror-implicit-function-declaration
Drivers/tspdrv/tspdrv.c
43 #include "tspdrv.h"
52 "ImmVibeSPI.c"
93 "tspdrvOutputDataHandler.c"
95 "VibeOSkernelLinuxHRTime.c"
Drivers/staging/ozwpan/ozeventtrace.h
219 #include" trace/define_trace.h"
216 . - > /home/android/mocha/k/drivers/staging/ozwpan
Drivers/tspdrv/makefile
33 EXTRA_CFLAGS += - I$(M) -> -I$(shell pwd)
Used 4.7 Google toolchain.

Sudeep Duhoon said:
Had to make these changes to build it. Yet not boot-able.
Makefile
-Werror-implicit-function-declaration
Drivers/tspdrv/tspdrv.c
43 #include "tspdrv.h"
52 "ImmVibeSPI.c"
93 "tspdrvOutputDataHandler.c"
95 "VibeOSkernelLinuxHRTime.c"
Drivers/staging/ozwpan/ozeventtrace.h
219 #include" trace/define_trace.h"
216 . - > /home/android/mocha/k/drivers/staging/ozwpan
Drivers/tspdrv/makefile
33 EXTRA_CFLAGS += - I$(M) -> -I$(shell pwd)
Used 4.7 Google toolchain.
Click to expand...
Click to collapse
What are you trying to boot it with? MIUI?
Xiaomi have a bad habit of not using kernel base compatible with newer proprietary firmware blobs.

Harrynowl said:
What are you trying to boot it with? MIUI?
Xiaomi have a bad habit of not using kernel base compatible with newer proprietary firmware blobs.
Click to expand...
Click to collapse
Miui cn dev 6.10.13 (version can vary from 6.9.x-6.11.3, I don't remember, will update tomorrow)
Will update the build here so anyone can test it.

Based on which Android version? I'm hoping in a MIUI 8 based on Android Marshmallow for now, and future upgrade to Nougat. It will remain a dream?

Sudeep Duhoon said:
Miui cn dev 6.10.13 (version can vary from 6.9.x-6.11.3, I don't remember, will update tomorrow)
Will update the build here so anyone can test it.
Click to expand...
Click to collapse
Hello,
Is possible to build CM with this kernel?
Regards.

jlazkano said:
Hello,
Is possible to build CM with this kernel?
Regards.
Click to expand...
Click to collapse
Don't know. Never built rom.
In best of my knowledge, to build cm with this kernel, it would be difficult as we don't have device tree.
Android version upgrade is more difficult.

It boots with firmware blobs used in miui7. Works as well (nice change)

Harrynowl said:
It boots with firmware blobs used in miui7. Works as well (nice change)
Click to expand...
Click to collapse
Is this screenshoot a CM version of Mi Pad1?
Kind regards.

jlazkano said:
Is this screenshoot a CM version of Mi Pad1?
Kind regards.
Click to expand...
Click to collapse
Boots on CM11 also, if this is what you're asking

Harrynowl said:
Boots on CM11 also, if this is what you're asking
Click to expand...
Click to collapse
That is great!
If you upload the image, I could help testing it.
Best regards.

jlazkano said:
That is great!
If you upload the image, I could help testing it.
Best regards.
Click to expand...
Click to collapse
You can find my source here:
https://github.com/harrynowl/MiPad
This is only fixup so it compiles using 4.9 GCC

Sudeep Duhoon said:
Had to make these changes to build it. Yet not boot-able.
Makefile
-Werror-implicit-function-declaration
Drivers/tspdrv/tspdrv.c
43 #include "tspdrv.h"
52 "ImmVibeSPI.c"
93 "tspdrvOutputDataHandler.c"
95 "VibeOSkernelLinuxHRTime.c"
Drivers/staging/ozwpan/ozeventtrace.h
219 #include" trace/define_trace.h"
216 . - > /home/android/mocha/k/drivers/staging/ozwpan
Drivers/tspdrv/makefile
33 EXTRA_CFLAGS += - I$(M) -> -I$(shell pwd)
Used 4.7 Google toolchain.
Click to expand...
Click to collapse
Yep. I too tried the same. I built CM13 from this kernel but not booting.
https://github.com/Nihhaar/android_kernel_xiaomi_mocha/
I know xiaomi source is broken.

Hi !
Harrynowl said:
You can find my source here:
https://github.com/harrynowl/MiPad
This is only fixup so it compiles using 4.9 GCC
Click to expand...
Click to collapse
1. Could you explain whether this would allow use of the kernel with later versions of Android like Marshmallow or Nougat ?
2. If not, what would be required for it to work ?
3. As someone who is adept at compiling and editing kernels, could you recommend a few links related to compiling and editing kernels ? It would be of great help to new learners like myself.
Thanks !
Thank you !