KERNELS - compatibility - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

Hey everyone -
Got my S3 on the way which should be delivered monday. I'm pretty much planning to root/recovery/kernel/rom it as soon as it gets out of the box, and I was looking at the already available kernels over in the dev section. Seems the options are surprisingly limited. I've never had a galaxy phone, but I do have a galaxy player 5.0 which I've been developing a kernel for so I'm not entirely new to this game.
Normally I would know the answer to this question, which would be no. Are we US users not able to use kernels such as Siyah? His changelogs and descriptions say NOTHING other than "for SG3" and "one kernel for all" or something to that effect. If we can't use it, what's everyone using for a jellybean/non-samsung kernel these days?
And yes, I did look at the sticky at the top of the page and I've been searching all this stuff for days.. just wondering what's good is all. I'm after all the cpu/gpu overclocking, added schedulers and governors, init.rc, all the techy stuff.
Thanks!

Pulled this from the new user guide stickied in the general forum...as far i know this is the complete list of kernels for the devices covered by this sub forum unless there are any released since the last update to the sticky.
d2tmo/att-ICS[Linux 3.0.37]kernel for Stock Based ROMs
Thanks to: faux123
I747UCALEM - Rooted, Unsecure, bootanimation & init.d support...splash img
Thanks to: NunHugger
[Sammy] KT747
Thanks to: ktoonsez
[REF] Kernel source code repository for AT&T Galaxy S III (I747M)
Thanks to:Tortel1210
AOSP/AOKP Kernels
d2tmo/att-ICS[Linux 3.0.37]kernel for AOSP/AOKP/CM9 ROMs
Thanks to: faux123
AOSP ktoonez version
Thanks to: ktoonsez

Please read forum rules before posting
Questions go in Q&A
Thread moved
FNM
And all kernels are good. Look at the OP of each kernel and all the features will be listed there.

Sorry about that! I'm so used to the Q&A section over in SGP5-land not being used. Thanks for moving it.
I've already looked at all those kernels, apparently leankernel should also be on that list.. it's available over at rootzwiki for the 747. So siyah is a no-go then?

I was thinking about Siyah also lol, I'm glad I checked here
SHALOM TO YOU!

exodus454 said:
Hey everyone -
Got my S3 on the way which should be delivered monday. I'm pretty much planning to root/recovery/kernel/rom it as soon as it gets out of the box, and I was looking at the already available kernels over in the dev section. Seems the options are surprisingly limited. I've never had a galaxy phone, but I do have a galaxy player 5.0 which I've been developing a kernel for so I'm not entirely new to this game.
Normally I would know the answer to this question, which would be no. Are we US users not able to use kernels such as Siyah? His changelogs and descriptions say NOTHING other than "for SG3" and "one kernel for all" or something to that effect. If we can't use it, what's everyone using for a jellybean/non-samsung kernel these days?
And yes, I did look at the sticky at the top of the page and I've been searching all this stuff for days.. just wondering what's good is all. I'm after all the cpu/gpu overclocking, added schedulers and governors, init.rc, all the techy stuff.
Thanks!
Click to expand...
Click to collapse
you might not see a ton of kernels here, but what we do have are great and have great dev support. additionally, some of the ROMs come packaged with such good kernels that there's no need to look anywhere else for one unless you just want to play around.
you'll hear the name "ktoonsez" a lot around here and will quickly forget about siyah...

Related

[INFO][KERNEL] GLaDOS by Ezekeel | GSM / Verizon / Sprint

V1.xx for ICS - the last V1.34​V2.xx for JB​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ezekeel is the dev of GLaDOS kernels for Android Devices​
His Social Network
http://twitter.com/ezekeel666
http://plus.google.com/101637761999487954252
[email protected]​
◇ The Official Thread ◇​
☞click GSM
☞click LTE
Ezekeel said:
Before you ask... Yes this kernel will work with your Sprint Galaxy Nexus.
Click to expand...
Click to collapse
I'm a general user, just link for the XDA members' information
To download does not require registering, it's Rootzwiki forum
Ezekeel said:
"Permission is granted to distribute these zips and links on non-English speaking sites and forums. However permission is not granted to distribute these zips and links on sites and forums with English as their main language; instead please link to this thread."
Click to expand...
Click to collapse
Source code:​
https://github.com/Ezekeel/GLaDOS-nexus-prime​
Features:​
Features:
- Based on stock Android kernel Jelly Bean 4.1.1 JRO03C
- Live OC version 2
- Custom Voltage version 3
- Battery Life eXtender (BLX) version 1
- SLQB memory allocator
- Color Control version 4 (based on supercurio's idea)
- CPUfreq governor 'Wheatley'
- Additional 1.4GHz, 1.6GHz, 1.8GHz and 2.0GHz MPU frequency slots
- Sound Control version 1
- Temp Control version 1
- Vibrator Control version 1
- FSync Control version 1
- USB Fast Charge
- Gamma control
- WiFi low latency power mode
- CIFS (as module)
- TUN (as module)
- NFS client + server (as module)
- NTFS read/write support (as module)
- Cleaned out all unnecessary kernel features and drivers
- Various other tweaks​
Changelog:​
http://rootzwiki.com/topic/14685-09-apr-glados-v127/#entry367718​
Tweaks:​
http://rootzwiki.com/topic/14685-09-apr-glados-v127/#entry367719​
CPUfreq governor 'Wheatley'​
http://rootzwiki.com/topic/14685-09-apr-glados-v127/page__st__90__p__405813#entry405813​
◆ Good color control settings for the glados control app​
http://rootzwiki.com/topic/14685-28-may-glados-v134/page__st__1250#entry712352
http://forum.xda-developers.com/showthread.php?p=23716259#post23716259
http://forum.xda-developers.com/showthread.php?t=1521195​
◆ Reset GLaDOS Control​
If the device can't boot due to inappropriate settings, install Reset_GLaDOS.Control.app.zip in CWM recovery.
(deleting /data/data/aperture.ezekeel.gladoscontrol/shared_prefs/)
Reset_GLaDOS.Control.app.zip​
◆ Switching Kernels​
Switching from one kernel to the other dev's kernel, flash Preparation.for.Installing.Kernels.zip in Recovery before flashing the kernel
(the residues from previously installed kernels are cleaned)
Preparation.for.Installing.Kernels.zip​
◆ Adding init.d to the existing ramdisk​
In GN forum, most of ROMs have init.d function (busybox run-parts)
But Stock and Peter Alfonso do not have that
Flashable zip in recovery, Adding init.d to the existing ramdisk and busybox installer
GN_Add_init.d.zip
Busybox_v1.20.1_CM9.zip
or
http://play.google.com/store/apps/details?id=stericson.busybox​
◆ ICS Stock Kernel - 4.0.3 / 4.0.4 compatible​
boot.img format
4.0.3_boot.img.zip
4.0.4_IMM76I_boot.img.zip​
Any Kernel format
4.0.3_Any.Kernel.zip
4.0.4_IMM76I_Any.Kernel.zip​
◆ Jelly Bean Stock Kernel - 4.1 / 4.1.1 compatible​4.1 JRN84D
boot.img format
4.1_JRN84D_boot.img.zip
Any Kernel format
4.1_JRN84D_AnyKernel.zip​4.1.1 JRO03C
boot.img format
4.1.1_JRO03C_boot.img.zip
Any Kernel format
4.1.1_JRO03C_Any.Kernel.zip​
This sounds promising, nice work!
Sent from my Galaxy Nexus using Tapatalk
phone_user said:
He's here at last!
Click to expand...
Click to collapse
jameslfc5 said:
This sounds promising, nice work!
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Only sounds for now.. doesn't boot on my GN and clean installed AOKP b15 (both versions).
vel1m1r said:
Only sounds for now.. doesn't boot on my GN and clean installed AOKP b15 (both versions).
Click to expand...
Click to collapse
I downloaded from Rootz last night and got the same thing on CM9
. Tried twice just to make sure
The developer wanted to keep the kernel as a RootzWiki exclusive. Kind of a silly thing to do in my opinion as it hurts the users to split the community.
Glad to see this kernel make its way to the Galaxy Nexus though. Was a great kernel for the Nexus S. Now we just need morfic
Sent from my Galaxy Nexus using xda premium
zephiK said:
The developer wanted to keep the kernel as a RootzWiki exclusive. Kind of a silly thing to do in my opinion as it hurts the users to split the community.
Glad to see this kernel make its way to the Galaxy Nexus though. Was a great kernel for the Nexus S. Now we just need morfic
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Well he got a phone from them.. but yeah he said please link to that thread, but I don't see it living for long here..
morfic.. hopefully soon
vel1m1r said:
Well he got a phone from them.. but yeah he said please link to that thread, but I don't see it living for long here..
morfic.. hopefully soon
Click to expand...
Click to collapse
Yeah I appreciate what rootzwiki does for the developers. It definitely favors them, it just hurts the users because they are unaware of these great and talented developer's work that's being exclusive to rootzwiki. Because, lets be honest, rootzwiki is nice to developers, but its not as popular as XDA causing a lack of awareness of releases.
I already feel this because the rom I use gets updated the fastest on rootzwiki. The xda thread of the rom is 1-2 builds behind.
That's just my take on rootzwiki. It definitely makes people go to their site. But I just don't think its right to split the community between the two websites.
Sent from my Galaxy Nexus using xda premium
zephiK said:
Yeah I appreciate what rootzwiki does for the developers. It definitely favors them, it just hurts the users because they are unaware of these great and talented developer's work that's being exclusive to rootzwiki. Because, lets be honest, rootzwiki is nice to developers, but its not as popular as XDA causing a lack of awareness of releases.
I already feel this because the rom I use gets updated the fastest on rootzwiki. The xda thread of the rom is 1-2 builds behind.
That's just my take on rootzwiki. It definitely makes people go to their site. But I just don't think its right to split the community between the two websites.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
ah I see now I misread your post :/.. anyways, 2 forums to check now for me also (ROM).
This would be better in General, no?
Sent from my Galaxy Nexus using XDA App
vel1m1r said:
Only sounds for now.. doesn't boot on my GN and clean installed AOKP b15 (both versions).
Click to expand...
Click to collapse
There's a second version of the kernel in that thread that ezekeel posted that has less of a ram/gpu/bus OC. He posted for people that can't boot the one in the OP, try that. I'm lucky, I must have a good soc I can run the one in the OP with AOKP 15 no problem.
Sent from my Galaxy Nexus
zephiK said:
Yeah I appreciate what rootzwiki does for the developers. It definitely favors them, it just hurts the users because they are unaware of these great and talented developer's work that's being exclusive to rootzwiki. Because, lets be honest, rootzwiki is nice to developers, but its not as popular as XDA causing a lack of awareness of releases.
I already feel this because the rom I use gets updated the fastest on rootzwiki. The xda thread of the rom is 1-2 builds behind.
That's just my take on rootzwiki. It definitely makes people go to their site. But I just don't think its right to split the community between the two websites.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
You can be member of XDA and RW at the same time. So I do not see how this is splitting up the community. You can link XDA threads on RW and vice versa. No matter what forum you are currently on, the other always is only one click away. All barriers you might see that split up the community, are in reality only in your mind.
I agree that it can cause a little more effort for the users since they might have to check two forums for updates. But let me be frank here, compared to all the effort I invested in writing this kernel this tiny bit of extra work for the users is hardly anything to complain about. If you have the time to play around with custom kernels and ROMs on your device, you got the time to check a second forum once in a while for updates.
Wow! Here a last. I will give it a go...
Ezekeel said:
You can be member of XDA and RW at the same time. So I do not see how this is splitting up the community. You can link XDA threads on RW and vice versa. No matter what forum you are currently on, the other always is only one click away. All barriers you might see that split up the community, are in reality only in your mind.
I agree that it can cause a little more effort for the users since they might have to check two forums for updates. But let me be frank here, compared to all the effort I invested in writing this kernel this tiny bit of extra work for the users is hardly anything to complain about. If you have the time to play around with custom kernels and ROMs on your device, you got the time to check a second forum once in a while for updates.
Click to expand...
Click to collapse
I know you can be a member of both. It splits the community in terms of discussions. Because one forum thread on XDA can be discussing about a bug within the kernel; where on RW, the discussion is about something else. You can fill in the rest of the points.
Pretty much what I said about developers updating their threads having the latest exclusive to Rootzwiki. Some developers don't update their threads and have it a few versions behind and not even link Rootzwiki.
I certainly have the time to visit both forums, no doubt in my mind about that. I visit both, but I mainly "lurk" on Rootzwiki and don't really put any effort into contributing to the forum discussion.
Unfortunately, for some users they don't have the time to go through two forums and view all the forum pages that they weren't able to read then to find out that there's a bug with the current release (or having a outdated thread where it's fixed in the newer version). Pretty much the point I'm making is that the OP thread is not equal to the Rootzwiki thread (or vice versa) in some ROMs or kernels. But pretty much since you made a rule about not having download links on any other forum, it pretty much voids my point but not generally speaking as not all devs follow this.
As much credit as Rootzwiki give to the developers. XDA can deserve the same amount of credit for providing a source for developers to distribute their custom made ROMs / kernels for mass consumption due to it's popular user base.
zephiK said:
I know you can be a member of both. It splits the community in terms of discussions. Because one forum thread on XDA can be discussing about a bug within the kernel; where on RW, the discussion is about something else. You can fill in the rest of the points.
Pretty much what I said about developers updating their threads having the latest exclusive to Rootzwiki. Some developers don't update their threads and have it a few versions behind and not even link Rootzwiki.
I certainly have the time to visit both forums, no doubt in my mind about that. I visit both, but I mainly "lurk" on Rootzwiki and don't really put any effort into contributing to the forum discussion.
Unfortunately, for some users they don't have the time to go through two forums and view all the forum pages that they weren't able to read then to find out that there's a bug with the current release (or having a outdated thread where it's fixed in the newer version). Pretty much the point I'm making is that the OP thread is not equal to the Rootzwiki thread (or vice versa) in some ROMs or kernels. But pretty much since you made a rule about not having download links on any other forum, it pretty much voids my point but not generally speaking as not all devs follow this.
As much credit as Rootzwiki give to the developers. XDA can deserve the same amount of credit for providing a source for developers to distribute their custom made ROMs / kernels for mass consumption due to it's popular user base.
Click to expand...
Click to collapse
If you don't have the time to do some extra reading, you probably don't have the time to root, and if you can't afford to do some extra reading in order to quash any bugs that may occur whilst you are using a ROM, then once again, maybe you should stay on stock.
Think about it this way, having certain distributions on RootzWiki will eventually increase their community, which will give users a choice in regards to where they wish to settle to collect their distributions from. There's no point constricting everything into one place, especially considering certain communities really do have a poor reputation in regards to quality of users, posts, content, and hosting. RootWiki I'm pretty sure are also responsible for actually supplying a few developers with devices, which is rather generous in a sense, don't see many communities doing this (most likely wrong).
Not my place to argue this, but I don't think you have a leg to stand on with your argument.
zeekiz said:
If you don't have the time to do some extra reading, you probably don't have the time to root, and if you can't afford to do some extra reading in order to quash any bugs that may occur whilst you are using a ROM, then once again, maybe you should stay on stock.
Think about it this way, having certain distributions on RootzWiki will eventually increase their community, which will give users a choice in regards to where they wish to settle to collect their distributions from. There's no point constricting everything into one place, especially considering certain communities really do have a poor reputation in regards to quality of users, posts, content, and hosting. RootWiki I'm pretty sure are also responsible for actually supplying a few developers with devices, which is rather generous in a sense, don't see many communities doing this (most likely wrong).
Not my place to argue this, but I don't think you have a leg to stand on with your argument.
Click to expand...
Click to collapse
I have the time to do the extra reading. I'm not saying it on my part, I'm saying for everybody else. And not everybody has to read to be using custom ROMs and kernels. That's why there are "nightlies" and "stable" releases. Stable releases are releases that are meant for people who don't have the time to sit here and flash every other release. I myself flash the newest and latest all the time. You can validate this by looking at my posts as I'm a very active poster and help many individuals out with their phones when they're having problems.
Not everybody are addicted to flashing because they don't have the time and they're not always available to be near a computer. This causes a misconception when it comes to ROM/kernel releases (as I mentioned earlier so you can stop directly calling me out).
As I mentioned previously, I respect RootzWiki for what they're doing and I have mentioned this numerous times. I'm not disliking RootzWiki or the developer's choices whatsoever. As much as RootzWiki has for its developers, the same goes with XDA for mass consumption. And that's that, developers and users both go the same way.
Developers want mass consumption for people to find bugs with their kernels / ROMs to have it fixed. The more people, the more chance of stability.
Users want more developers for more production of ROMs / Kernels. Kinda like how XDA & Rootzwiki correlate with each other.
I personally like Ezekeel's work with the lazy governor and what he's done for the Nexus S and I'm really happy to see him developing for the Galaxy Nexus. Just stating my two cents for the casual flashers (yes they do exist) although I'm not one of them. If you'd like to have this debate, feel free to inbox me. This is way too irrelevant out of this thread.
But anywho getting back on topic. Can't wait for this kernel to mature and see what it has to bring to the table. It'll definitely be a good thing overall when the kernel is stabilized then source is revealed for other creative kernel developers to implement the 'lazy' governor and additional features to improve overall kernel performance.
Never mind 10 charr
Its not that big a deal to write a damn book on it. Who cares where the kernel is posted, them more devs the better.
Trust me, the issues have nothing to do with making sure the users see all the discussions and updates. It boils down to the fact XDA is not really happy when someone uses their reputation and brand and web presence to drive traffic to a competing site. Good or bad? I'm just saying, that is why the rules about this subject exist. It's naive to think otherwise.
The other rule is that the Development forum is a place for developers to share their own work. It is not a place for users to post links to someone else's work on some other site. That is why I think this thread belongs in General. But whatever.
But with all that said, I know that Ezekeel is one of the most talented and creative kernel developers working on Android today (I know his work from Nexus S) and I'm very happy his work is available for the Galaxy Nexus now. Cheers!
Sent from my Galaxy Nexus using XDA App
enjoying the kernel so far.

Looking to study Kernel Development could use some pointing in the right direction.

Looks like im getting involved earlier than I planned. But other than compiling a stock kernel from source. The guides for our phone never really got finished. Looks like the international guides as well as android kernel guides in general will lend some guidance.
So if anyone can point me in the right direction. Maybe even help when i get stuck.
Guides I found for our phone:
http://forum.xda-developers.com/showthread.php?t=1291122
http://forum.xda-developers.com/showthread.php?t=1442870
http://forum.xda-developers.com/showthread.php?t=1494804
I realize the problem with leak kernels on our phone other than not having source is with recovery being part of the initramfs. After reading up on the initramfs scheme one would think we can extract modify the files and repack it into the kernel like steady has been doing.
A quick google turns up a guide for the international gs2 which i hope will help me. http://forum.xda-developers.com/showthread.php?t=1294436
Then there is things like adding init.d support which i might be able to bug sfhub about. Most importantly building cwm to be packed into the initramfs. Also learned root was a part of the kernel but had i known zimage was the kernel partition I probably would have figured. But i have yet to look at either of these since I only decided yesterday to do this.
Im going to have this phone another 1.5 years so if were losing people I mind as well shuffle my projects and do this one now. I am not looking to create and maintain a custom cwm or anything.
Ive been a pascal programmer for 14 years. I can read and translate C syntax languages. I studied C++ but never having practiced it I can not write fluently without a reference in hand. I am a bit of a linux noob i mean i have compiled kernels and drivers even a from scratch gentoo install but that was all from instructions. Its one thing to do something its different to understand it.
I wrote this from my cell phone so sorry for worse than usual spelling grammar and lack of punctuation.
Also figured in my searching looking at threads started by formerly active devs might turns up some stuff.
Chris41g had a thread in the OG Epic section perfectly titled "To the people wanting learn to code kernels and roms for the Epic" http://forum.xda-developers.com/showthread.php?t=1177076
Edit - Having some time to read before i pass out that third guide that sweetwater did for our phone is rather complete up to date and he is still hanging around.
good luck man, i hope you get up and running with this. thanks for taking the challenge. the community is lacking in the kernel area and any support is greatly appreciated, by me anyway. thanks again.
Rain can you pm me?
RainMotorsports said:
Also figured in my searching looking at threads started by formerly active devs might turns up some stuff.
Chris41g had a thread in the OG Epic section perfectly titled "To the people wanting learn to code kernels and roms for the Epic" http://forum.xda-developers.com/showthread.php?t=1177076
Edit - Having some time to read before i pass out that third guide that sweetwater did for our phone is rather complete up to date and he is still hanging around.
Click to expand...
Click to collapse
Both of the E4GT guides will work no problem and are actually pretty simple, anyone here can do it. I promise that. There are some issues though. Our EL29 source is a little funky so building with the first E4GT guide will get you a booting CWM kernel but wifi will break. After A LOT of testing we found the problem in the init.d file and the fix is in Sweetwaterburn's github source. There were several of us who built kernels(even EL29 with CWM, which is weird that everyone still uses EL26 to flash AOSP but anyways...) and a few like interloper and agat who were able to incorporate various governors. That was around the time all of the leaks started so then the kernels just kind of fell of the map because why waste the time?
Now onto the ICS stock repacks.....There is a ton of risk in testing those. Look how many bricks steady and the team rogue had not to mention team troll and random users. Why not just wait a little till source drops? Once source drops building kernels will be a ton easier. Also Calkulin and the new guy(can't think of his tag) have built unsecure stock kernels so that should satisfy all of the needs for leaks.
Here is one Agat built: http://forum.xda-developers.com/showpost.php?p=22463351&postcount=265
here is another EL29 I built: http://forum.xda-developers.com/showpost.php?p=22461146&postcount=264
Thanks DTM. I read on Steady's G+ he is definitively moving away from the E4GT as he has given it to his wife.
The amount of activity and the people involved in SweetWaterBurns thread surprised me and now that I know that I don't think people should be too worried. I mean we already know part of this is a bit of impatience.
I will still be learning for the long run. Hope to see some good things with the community thread when the ICS kernel source is out.
RainMotorsports said:
Thanks DTM. I read on Steady's G+ he is definitively moving away from the E4GT as he has given it to his wife.
The amount of activity and the people involved in SweetWaterBurns thread surprised me and now that I know that I don't think people should be too worried. I mean we already know part of this is a bit of impatience.
I will still be learning for the long run. Hope to see some good things with the community thread when the ICS kernel source is out.
Click to expand...
Click to collapse
I encourage everyone to attempt a kernel. I have no formal computer training and I just dual booted my laptop, next thing you know I was churning out kernels. We definitely need some variety in our kernel selection, I just don't advise it for the leaks unless you can afford some bricks. Because we have beast "big brother" in the international SGSII community it is pretty easy porting over some of their modifications to our source code via winmerge or copy and paste. It is also a lot less risky than messing with leaks.

[Q] Simple Question about Franco Kernel

Please do not flame me as I am really creating this thread to earn the right to post in developers threads.
I am running AOKP MR1 Build 1 on my Toro Galaxy Nexus which is as smooth as to be expected on an initial build. The simple question I have is does the Franco Kernel in this thread: http://forum.xda-developers.com/showthread.php?t=1367341 Support the VZN Toro? Franco while I really like his work seems to be unable to simply state in the OP if this is a multi phone Kernel or if its specific. Trolling through the multitude of posts I see the majority of posters seem to be on GSM version which deterred me from downloading and risking a boot loop. Yes I have a backup but it would be better to know that I wont have to use it...
Thanks in advance - Joe
you are looking in the wrong development forum. you need to look in the verizon dev forum
http://forum.xda-developers.com/forumdisplay.php?f=1455
Another Question
Zepius said:
you are looking in the wrong development forum. you need to look in the verizon dev forum
http://forum.xda-developers.com/forumdisplay.php?f=1455
Click to expand...
Click to collapse
So looking over the Verizon Developers thread as I had a few days ago I was unable to find a Franco specific thread...However, almost giving up and looking over Tinys Kernel OP the very first of the disclaimers states that:
The kernel will only work on JB and is carrier independent as all Galaxy Nexus kernels are from 4.0.3 onwards.
If this is a true statement then that means that all GNex Kernels work on all GNex variants...???
Thanks again
jrgilbert79 said:
So looking over the Verizon Developers thread as I had a few days ago I was unable to find a Franco specific thread...However, almost giving up and looking over Tinys Kernel OP the very first of the disclaimers states that:
The kernel will only work on JB and is carrier independent as all Galaxy Nexus kernels are from 4.0.3 onwards.
If this is a true statement then that means that all GNex Kernels work on all GNex variants...???
Thanks again
Click to expand...
Click to collapse
no.
kernels are device specific
as far as not being able to find it... uh its on the 2nd page. guess you dont read.
http://forum.xda-developers.com/showthread.php?t=1422956
Sure...
Zepius said:
no.
kernels are device specific
as far as not being able to find it... uh its on the 2nd page. guess you dont read.
http://forum.xda-developers.com/showthread.php?t=1422956
Click to expand...
Click to collapse
Well I am looking for a 4.2.X FRANCO Kernel as stated in the OP and not his Milestone 6 that works on 4.0.X/4.1.X...I appreciate your help really I do however, apparently there are two of us here who have literacy issues...

Newcomer to the S4 family in need of assistance!

Hello all, Good to finally be here! Just came from an S3.
I'm obviously going to do much digging in the dev forums but off the top of your heads whats the best ROM for my preferences below:
I enjoy Blue themed ROM's
I have a S-view enabled case (Spigen Slim Armor View) so I need S-view (Does that mean ASOP ROMs are out of the question or did they build S-view into them for the S4?)
Overclocking available
Note: The ROM doesn't have to come blue themed, just be able to flash a blue theme over top of the ROM.
Thanks all!
EDIT: Also whats the best root method for this device? If theres more than one.
SemiGamer said:
Hello all, Good to finally be here! Just came from an S3.
I'm obviously going to do much digging in the dev forums but off the top of your heads whats the best ROM for my preferences below:
I enjoy Blue themed ROM's
I have a S-view enabled case (Spigen Slim Armor View) so I need S-view (Does that mean ASOP ROMs are out of the question or did they build S-view into them for the S4?)
Overclocking available
Note: The ROM doesn't have to come blue themed, just be able to flash a blue theme over top of the ROM.
Thanks all!
EDIT: Also whats the best root method for this device? If theres more than one.
Click to expand...
Click to collapse
Research. Your questions have all been asked, even the one that's not allowed; which ROM is best for *. Most every ROM thread has screenshots in the very first post that will say if it's blue or not as well as tell you whether it's TouchWiz or AOSP along with listing the features it has. It will take a little more digging to see if AOSP supports S-View; though not much more. The kernel OPs will mention whether they are overclockable (what good is a custom kernel if you can't overclock it anyway?) There is no "best" root method. Any of the rooting methods found here will certainly work.
This for rooting
http://forum.xda-developers.com/showthread.php?p=41797153
Rom is a matter of preferences, there's no "best" ROM just what's best for you. I'm guessing for S-view you'll need to stick with a TW bass ROM.
baseballfanz said:
This for rooting
http://forum.xda-developers.com/showthread.php?p=41797153
Rom is a matter of preferences, there's no "best" ROM just what's best for you. I'm guessing for S-view you'll need to stick with a TW bass ROM.
Click to expand...
Click to collapse
Thank you for the friendlier answer and the link mate!
Not sure how "I'm going to do some research as well but" was missed in my OP but eh. Was asking for recommendations for me to check out first since I'm sure some ROMs are more stable than others just like every other phone that I usually spend a week flashing ROM's to find the stable ones, thought maybe someone could help me narrow that first week of flashing down and meet people on this forum as people do on my previous phone' forums but that doesn't seem the way to go over here I guess. Oh well getting used to the community comes with a new device.
Thanks for the help anyhow, Mods may close this thread.
Flash Wicked Rom. Has the option of either blue, red, pr stock theme.
Sent from Flip's Galaxy S4
Please read forum rules before posting
Questions and help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
There is no such thing as a BEST ROM! Threads are closed asking such questions
This is a development site, not a support site. Members are expected to do their own research before drastically altering their $700 device.
SemiGamer said:
Hello all, Good to finally be here! Just came from an S3.
I'm obviously going to do much digging in the dev forums but off the top of your heads whats the best ROM for my preferences below:
I enjoy Blue themed ROM's
I have a S-view enabled case (Spigen Slim Armor View) so I need S-view (Does that mean ASOP ROMs are out of the question or did they build S-view into them for the S4?)
Overclocking available
Note: The ROM doesn't have to come blue themed, just be able to flash a blue theme over top of the ROM.
Thanks all!
EDIT: Also whats the best root method for this device? If theres more than one.
Click to expand...
Click to collapse
And after you get root and recovery taken care of, here is a slew of roms that will work with your device...
[GUIDE][ROMS]RUN OTHER CARRIER ROMs on AT&T/TMO/Canadian S4 devices. Here's how!
http://forum.xda-developers.com/showthread.php?t=2295557
have fun, welcome, and by all means, READ! because it is a little different from the G3...or whatever device you have came from...
Thanks

[Q] Custom Kernel vs Stock Kernel

Hey guys, I have a couple questions for those of you who have good kernel knowledge (especially for HTC One M8).
I'd appreciate if you made your replies as noob proof as possible, since I'm not too familiar with how Kernels work, thank you!
1. What are the best known / most common kernels are available for the HTC One M8? (give names)
2. For each kernel mentioned above, what are the pros and cons, and what do they do that's unique? And how do they compare to stock kernel? (remember to make this noob proof)
Thank you guys for your help.
Depending on how much information and the quality of such information, I will compile all replies given here into its own thread as a kernel guide for the M8, and list the usernames of all who helped in the credits.
Sent from my Nexus 9 through XDA app
1 : check the Android development and original Android development section and count the threads starting with [KERNEL]
2 : The pros and cons.....just read each independent thread, the opening posts contain all needed info with the mods they carry.
It's all written out already. Just take the time to read. And there are already "kernel talk" threads in the general section. Just explore more in the different sections here.
Mr Hofs said:
1 : check the Android development and original Android development section and count the threads starting with [KERNEL]
2 : The pros and cons.....just read each independent thread, the opening posts contain all needed info with the mods they carry.
It's all written out already. Just take the time to read. And there are already "kernel talk" threads in the general section. Just explore more in the different sections here.
Click to expand...
Click to collapse
Hehe thanks, you actually pointed out a flaw in one of my questions, which I'll have to correct the OP to better reflect my needs.
Question 1 should probably be, what are the most common or best known kernels for the M8.
And on another note, I'd just like to repeat and emphasise (something which I'll edit the OP as well to make clearer), this honestly needs to be N00b proof, I'm not joking haha I'm good at understanding ROMs and OSs (I'm an IT student btw), but I'm a complete newbie at Kernels.
Your second answer is something I already have done, and what they described there, was pure jargon to me. A list of what the kernel does, but there is no explanations for what each element on the list is.
And about reading the kernel talk threads, I did some research on Kernels and how to choose the best one for me, but none of them explained fully, more like just looked at the major points (over/underclock, touch to wake support etc...) which honestly i can just as easily get from a ROM.
But there's so much more I do not understand yet, which I would appreciate if you, or someone else explained in a simple not too technical way.
I'm pretty sure I'm not the only one with such a question.
Sent from my Nexus 9 through XDA app
Kyuubi10 said:
And about reading the kernel talk threads, I did some research on Kernels and how to choose the best one for me, but none of them explained fully, more like just looked at the major points (over/underclock, touch to wake support etc...) which honestly i can just as easily get from a ROM.
Click to expand...
Click to collapse
If you got those feature from a ROM, its only because the ROM included a custom kernel. You can't have those things without changing the kernel.
To me, custom kernels are a very personal thing. What you get (or don't get) out of them depends a lot on how you use your phone. Therefore, I think that is the reason why most kernel threads won't have much description on the exact benefits. I know lots of folks swear by custom kernels and the features they offer. But personally, I've never been much a kernel flasher or tweaker. Reason being, the times I have messed with kernels, they don't seem to give me much benefit in terms of performance (battery and/or responsiveness) and sometimes even hurt those aspects. But again, YMMV and I think it depends a lot on your setup and how you as an individual use your phone.
On that same note, I think it makes a thread like this difficult to construct; or any opinion given possibly not relevant to all. Like ROMs, its not that hard to look at the threads and discern which are most popular (if that is your goal, popular doesn't always mean best). Then pick a few that look good (seem to meet your needs or wants), try them out, and see what works best for you.
I know that sounds like a cop out; but its what I honestly believe.
@redpoint73
I see what you mean, but I am already limiting things only to the M8. So there shouldn't be that many Kernels go talk about.
Having a look through the forums it's no so well organised as to give a clear view of how each kernel compare to each other.
(note: Not to decide which one is best, but to clearly display differences, which could make it easier to see which one is better for the person)
If I was to make a guide on M8 Kernels I'd try to find what is common among them, what you can 100% expect from all Kernels.
Then I'd start naming the Kernels and displaying the different features (and how they are meant to benefit or how they work, because so far I have only found names/initials, which make it hard for a noob to understand what those features are from just a name).
So yeah, that is what I had in mind.
But its hard from purely reading the individual kernel threads, mostly coz I'm a noob at kernels (which is why I created this thread, to understand better kernels)
I had no idea about i/o schedulers... I just did some research, but the worst part is that there are some kernels which just make the names a joke, making it hard to find out what that scheduler really does. And the OP doesn't explain either.
Same is true for CPU governors. But now I'm just ranting.
It seems as there are not many people who know kernels as well as they think they do.
Sent from my Nexus 9 through XDA app
Why not make it a bit easier on yourself and participate in this thread ?
http://forum.xda-developers.com/showthread.php?t=3103465
Lots of kernel talk,regardless the rom.
I went in as you advised, but it still doesn't cover what I wanted to know, I had to search each specific feature on its own, as I tweaked it.
There are a lot of guides to individual features, no comprehensive guide (with links) for kernels.
I hv decided, I'm gonna play around a bit on my new kernel (ended up going for ElementalX), and then I'll do a kernel guide. Nothing like using a kernel to understand it better right?
Sent from my Nexus 9 through XDA app
Kyuubi10 said:
I went in as you advised, but it still doesn't cover what I wanted to know, I had to search each specific feature on its own, as I tweaked it.
There are a lot of guides to individual features, no comprehensive guide (with links) for kernels.
I hv decided, I'm gonna play around a bit on my new kernel (ended up going for ElementalX), and then I'll do a kernel guide. Nothing like using a kernel to understand it better right?
Sent from my Nexus 9 through XDA app
Click to expand...
Click to collapse
Definitely true there mate, i am on stock as it behaves very good for me. I have no need for a custom one at this moment
Stock is good... I like stock, but I'm trying to learn a bit more, expand my horizons a bit.
Got kinda boring tweaking only the ROM
Sent from my Nexus 9 through XDA app
Hey guys, as promised, after playing around with Kernels I decided to make a Comprehensive guide on Kernels.
If you wanna have a nosey and give some feedback here's the link:
http://forum.xda-developers.com/showthread.php?p=61026926
Sent from my Nexus 9 using XDA Free mobile app

Categories

Resources