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.
1. Why is the Sprint Galaxy S 2 referred to as the Epic 4g touch? this is confusing.
2. what are all the numbers FG20! FF18, FF02! FE21, FE16, FE10, FE07, FD24, EL29, EL26, EG30, EK02?
3.my devices number is FI27, I also see some people post FL27 are these the same devices?
4. are all of above numbers referring to one phone?
5.I just got my phone where are the guides for FI27? I have looked most of the guides should be taken down or archived and new more relevant guides put up.
I don't mean that comment to be disrespectfully mean or anything. Most guides say one needs to read through full guide just to find out it's old out of date and has little or nothing to due with FI27.
6. what is the latest version FI27?
7. as far as the leaks for JB which is the latest versions? the numbering system is ridiculous.
8. I have read several posts referring to safe recovery, why release an unsafe recovery?
9. Is there a section just for FI27, I am not interested in older out of date version all these threads should be archived as well or move to the back.
10.The front threads one sees should be about FI27 and later, new user like myself have no desire to read through old outdated threads.
Thank you for you time.
I have only had my phone a few days, what I have done so far?
I rooted my phone with a kernel root method I made up, didn't flash a full rom just to get root.
I have built my own kernel and am now using it, I am going to setup up a dual boot on this device.
I can do all of above and more, yet can't figure out most of the guides here, LOL.
1. Why is the Sprint Galaxy S 2 referred to as the Epic 4g touch? this is confusing.
Because Sprint wanted the phone to feel like it was special.
2. what are all the numbers FG20! FF18, FF02! FE21, FE16, FE10, FE07, FD24, EL29, EL26, EG30, EK02?
They are software release names. Usually the higher the letter the newer the release, and same with the numbers. So FF18 is newer than FF02. And FG20 is newer than FE21
3.my devices number is FI27, I also see some people post FL27 are these the same devices?
Good question, whoever made capital i look like a lower case L is an idiot.
4. are all of above numbers referring to one phone?
Yes, they are just software versions.
5.I just got my phone where are the guides for FI27? I have looked most of the guides should be taken down or archived and new more relevant guides put up.
Depends what you want to do, the stickies on the top of the android development page are super useful.
I don't mean that comment to be disrespectfully mean or anything. Most guides say one needs to read through full guide just to find out it's old out of date and has little or nothing to due with FI27.
6. what is the latest version FI27?
Read above
7. as far as the leaks for JB which is the latest versions? the numbering system is ridiculous.
Read above
8. I have read several posts referring to safe recovery, why release and unsafe recovery?
Because before the kernel was fixed, there were no other options in recovery. If you use a newer ROM then the recovery should already be fixed.
9. Is there a section just for FI27, I am not interested in older out of date version all these threads should be archived as well or move to the back.
Not everyone uses the same software. Some people still like gingerbread. Also, what do you mean a section? Most of the time it doesn't matter what YOUR version is, only the version you want to be on when you flash a ROM.
10.The front threads one sees should be about FI27 and later, new user like myself have not desire to read through old outdated threads.
You are starting to sound like a troll, but hopefully you will understand a little more when you read my explanations.
Thank you for you time.
You are welcome
I have only had my phone a few days, what i have done so far?
I rooted my phone with a kernel root method I made up, didn't flash a full rom just to get root.
Good for you. But there are methods on here that do the same thing.
I have built my own kernel and am now using it, I am going to setup up a dual boot on the device.
Feel free to share it in the original development section, just be sure to post source and all that good stuff
Also, what will you be dual booting? I will be very interested to see the development on this because I don't think it has been done successfully yet.
I can do all of above and more, yet can't figure out most of the guides here, LOL.
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 10:16 AM ---------- Previous post was at 10:15 AM ----------
I answered your questions under each question. Let me know if you have any more.
Sent from my Nexus 7 using xda app-developers app
tomtom1265 said:
1. Why is the Sprint Galaxy S 2 referred to as the Epic 4g touch? this is confusing.
2. what are all the numbers FG20! FF18, FF02! FE21, FE16, FE10, FE07, FD24, EL29, EL26, EG30, EK02?
3.my devices number is FI27, I also see some people post FL27 are these the same devices?
4. are all of above numbers referring to one phone?
5.I just got my phone where are the guides for FI27? I have looked most of the guides should be taken down or archived and new more relevant guides put up.
I don't mean that comment to be disrespectfully mean or anything. Most guides say one needs to read through full guide just to find out it's old out of date and has little or nothing to due with FI27.
6. what is the latest version FI27?
7. as far as the leaks for JB which is the latest versions? the numbering system is ridiculous.
8. I have read several posts referring to safe recovery, why release an unsafe recovery?
9. Is there a section just for FI27, I am not interested in older out of date version all these threads should be archived as well or move to the back.
10.The front threads one sees should be about FI27 and later, new user like myself have no desire to read through old outdated threads.
Thank you for you time.
I have only had my phone a few days, what I have done so far?
I rooted my phone with a kernel root method I made up, didn't flash a full rom just to get root.
I have built my own kernel and am now using it, I am going to setup up a dual boot on this device.
I can do all of above and more, yet can't figure out most of the guides here, LOL.
Click to expand...
Click to collapse
1. Sprint did it to show theirs was different. They've since stopped the mention of "Epic 4G Touch" since selling under Boost and Virgin.
2. Software Builds.
First Letter - Year (A was 2007, F was 2012, G - 2013)
Second Letter - Month (A-L)
Third & Fourth - Build Day.
3. FI27 is the official build. FL27 is a known build for JB but currently unavailable to the public.
4. Yes - and to make it even more fun they have 2 variants: SPH-D710BST for Boost, SPH-D710VMUB for Virgin Mobile.
5. The FI27 One Click thread is the simplest resource. Other than that there are some old ICS threads but most of that is dead since JB turned out to breathe new life into this phone.
6. Officially Yes. Unofficially FL16 (JB)
7. See #6
8. Generally you don't need to worry about this anymore with kernels that folks built. Older recoveries had offending code that triggered a bug in the eMMC firmware that would potentially brick your phone at worst or lose 2GB of data at best. Agat's kernels for TW are rendered safe.
9/10: Again, on XDA FI27 is considered old news and most around here are either on AOSP builds running Jelly Bean or TW builds running JB. That's why, nothing against your intentions. (They were stickied when they were big, they've moved on though.)
Congrats if you've built your own kernel! Make sure that you too remove the offending code to avoid triggering the eMMC bug if you decide to go that way. I know Agat is working on a multi-boot kernel (TW/AOSP) and they're having issues with it in the display depatment, so if you're that far you may want to reach out to him as he may welcome the help.
Thank you both for your answers, they help a lot to clear things up.
Ok I just searched the offending code to avoid triggering the eMMC bug, I am using Agat kernel source code, cause everyone says his kernels don't have the MMC_CAP_ERASE.
However his kernel source does have MMC_CAP_ERASE in the source code the eMMC bug still exists, I would have thought Agat would remove MMC_CAP_ERASE from his source code.
Anyway I can remove it using this guide, http://forum.xda-developers.com/showthread.php?t=1847859
thanks for pointing that out, even if one gets source code from a dev's github the eMMC bug still exist in the source code and one needs to remove it themselves..
A quick way to find all the MMC_CAP_ERASE is to use grep
Code:
grep -Hr 'MMC_CAP_ERASE' '/home/tom/Desktop/epic/kernel/AGAT_FI27_kernel'
/home/tom/Desktop/epic/kernel/AGAT_FI27_kernel/arch/arm/mach-exynos/mach-nuri.c: MMC_CAP_DISABLE | MMC_CAP_ERASE),
/home/tom/Desktop/epic/kernel/AGAT_FI27_kernel/drivers/mmc/core/core.c: if (!(card->host->caps & MMC_CAP_ERASE) ||
/home/tom/Desktop/epic/kernel/AGAT_FI27_kernel/drivers/mmc/core/core.c: if ((card->host->caps & MMC_CAP_ERASE) &&
/home/tom/Desktop/epic/kernel/AGAT_FI27_kernel/drivers/mmc/host/omap_hsmmc.c: MMC_CAP_WAIT_WHILE_BUSY | MMC_CAP_ERASE;
/home/tom/Desktop/epic/kernel/AGAT_FI27_kernel/drivers/mmc/host/sdhci.c: mmc->caps |= MMC_CAP_SDIO_IRQ | MMC_CAP_ERASE;
/home/tom/Desktop/epic/kernel/AGAT_FI27_kernel/include/linux/mmc/host.h:#define MMC_CAP_ERASE (1 << 10) /* Allow erase/trim commands */
tomtom1265 said:
A quick way to find all the MMC_CAP_ERASE is to use grep
Code:
grep -Hr 'MMC_CAP_ERASE' '/home/tom/Desktop/epic/kernel/AGAT_FI27_kernel'
/home/tom/Desktop/epic/kernel/AGAT_FI27_kernel/arch/arm/mach-exynos/mach-nuri.c: MMC_CAP_DISABLE | MMC_CAP_ERASE),
/home/tom/Desktop/epic/kernel/AGAT_FI27_kernel/drivers/mmc/core/core.c: if (!(card->host->caps & MMC_CAP_ERASE) ||
/home/tom/Desktop/epic/kernel/AGAT_FI27_kernel/drivers/mmc/core/core.c: if ((card->host->caps & MMC_CAP_ERASE) &&
/home/tom/Desktop/epic/kernel/AGAT_FI27_kernel/drivers/mmc/host/omap_hsmmc.c: MMC_CAP_WAIT_WHILE_BUSY | MMC_CAP_ERASE;
/home/tom/Desktop/epic/kernel/AGAT_FI27_kernel/drivers/mmc/host/sdhci.c: mmc->caps |= MMC_CAP_SDIO_IRQ | MMC_CAP_ERASE;
/home/tom/Desktop/epic/kernel/AGAT_FI27_kernel/include/linux/mmc/host.h:#define MMC_CAP_ERASE (1 << 10) /* Allow erase/trim commands */
Click to expand...
Click to collapse
The key is whether it is in mshci.c, which it has been removed.
We discussed this before as I wasn't sure as well:
http://forum.xda-developers.com/showthread.php?t=1644364&page=28
You're good.
garwynn said:
The key is whether it is in mshci.c, which it has been removed.
We discussed this before as I wasn't sure as well:
http://forum.xda-developers.com/showthread.php?t=1644364&page=28
You're good.
Click to expand...
Click to collapse
Thanks again, I going to go ahead and remove the rest, won't hurt anything. Then work on dual boot.
Hi,
I am trying to apply the preempt_rt patches[2] in order to test the realtime performance of native code on an android device in a study project. The device I have for testing is the Galaxy Nexus.
People here seem to have managed to do that with a Xoom[1].
My starting point was the kernel of the current official (4.2.2) Android release (android-omap-tuna-3.0-jb-mr1.1). According to the version string it is based on linux 3.0.31, so I tried to patch it with the corresponding rt-patchset. Except for a few rejects that went fine. Most of them I could get fixed manually.
My problem atm is that there seem to be quite some backports from newer (3.3/3.4?) kernels, especially for the file "include/linux/plist.h" and "kernel/rtmutex.c" which change some function-declarations. Today I managed to compile the kernel with the "CONFIG_PREEMPT_BASIC" option set, but when I try to boot the phone it gets stuck during the Google-bootscreen. It does not show up as an adb device, so I can't get any output from the device.
For me the question is, how much of the Kernel is actually still 3.0.31, maybe it would be more suitable to use the rt_patches for more recent Linux-kernels?
I was also thinking about trying to patch the kernel the GNex was released with, because this one may be closer to the original Linux kernel (I checked, plist.h and rtmutex.c are not the original ones as well)?
Maybe someone else has a better idea what to test, because I am not overly familiar with all the different subbranches and development trees of Android yet. Any help or suggestions would be greatly appreciated.
Best regards,
Jan
PS: I would have posted this in the development section, but wasn't permitted to. Maybe a mod could move it?
PPS: It seems, I am also not allowed to include working links :-/
[1] Search for: "mauerer real time linux tag" to get the paper
[2] rt.wiki.kernel.org/index.php/CONFIG_PREEMPT_RT_Patch
not true
As he stated numerous times, codeworkx isn't likely to ever work on this device again. I don't know how to check whether the kernel is for H60 (other than looking at that encouraging filename), but the version of these sources is 3.10.74, the same that is running on my phone's EMUI with Android 5.1.1.
I kind of feel as if this should be a very basic topic and that I should not be having to post a new thread on it... but, out of curiosity, does anyone know whether or not the Android kernel-- which as we all know is a flavour of the Linux kernel-- can be updated through "patching" as the regular Linux kernel can? The reason I am asking is that I greatly prefer to run my device with a custom kernel that has extra features over the stock kernel, however, it seems like every custom kernel that is released is released as a one-shot deal, and that the only way to have a kernel that continues to be updated with fresh source is to run the kernels that are provided with the nightly ROM builds.
Of course, I could go the route of learning how to build my own kernels and add features to them.. but I guess my basic question is, does there exist any form of "general patch" that is periodically released by Google, or the Linux Kernel foundation, etc., that will bring your current kernel up-to-date with the latest system-wide changes (secuturity & stability fixes, etc), while leaving the bulk of the kernel and the kernel configuration in place? Or is that a totally unrealistic and impractical concept? I do build my own kernels from source for my laptop, but I know very little about compiling a kernel for android.. anyway, if there are any kernel devs still on this device's forum, what do you guys think?
Any feedback from knowledgeable individuals much appreciated.. thank you!
No. You would have to build the kernel and flash it yourself. You can usually find HTC's kernel source on their website for each device. You take that kernel and manually patch the updates yourself.