can semaphore jvz kernel be used for jw1 roms?
Sent from my GT-I9000 using XDA App
Yes, I just tried it and it works fine.
apparantly jw1 and jvz are almost identical (only diff is in lang files or something), so jvz kernel is fine.
i think that progress in changelog number is too great for the only changes to be were the language typos fixes
using custom kernel is bad
using custom kernel from previous version to some more recent is bad
but if you want various tweaks and overclocking there's no other possibility then using a custom kernel that supports it or am wrong?
greetz
well yes but take a second and think about it
kernel sources those guys use are half year old and are for 2.3.3 kernel version
currently used kernel by samsung in jw1 is 2.3.6 that sources are unreleased
$omator said:
well yes but take a second and think about it
kernel sources those guys use are half year old and are for 2.3.3 kernel version
currently used kernel by samsung in jw1 is 2.3.6 that sources are unreleased
Click to expand...
Click to collapse
Now i see. That's why i used to be so satisfied with my stock jvq rom and latest semaphore kernel. Now im on jvz and cant see any improvement. \/
i can tell that jw1 and jvx/jvz stock versions
are faster then jvt and eariler ones (2.3.5) - more responisive
tings like zergrush exploit gets patched
but it is still your fair choice to pick custom kernel
and overclock/ondervolt or do whatever you like with it
i am pissed a bit that those guys are not informing in op post
"builded from latest smsung source" is not saying that this source have half year
but i will not start another rant to get banned by some moderator for trollingas usuaal ;]
$omator said:
i think that progress in changelog number is too great for the only changes to be were the language typos fixes
using custom kernel is bad
using custom kernel from previous version to some more recent is bad
Click to expand...
Click to collapse
Not true. Were there any bugs that were not present in the stock kernel that is present in a custom kernel? None so far.
Samsung is obligated to release the latest source code for its kernel. If a compiled kernel doesn't boot or the kernel can't work with the binaries that are released, Samsung is liable to being sued for not being GPL compliant. So far they've been pretty quick in releasing sources (from the past year) with the delta being less than a 2 weeks after a release.
Also, if you spot any differences of stock with a custom kernel, you should report it to Samsung so that they release the latest source code. So far I have not detected any bugs stemming from using a compiled kernel from the source that's been released more than 3 months ago.
{
"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"
}
GB_Update2 you see is not even a full source - released in August
$omator said:
GB_Update2 you see is not even a full source - released in August
Click to expand...
Click to collapse
This is because Samsung expects you to use the pre-compiled modules for Wifi and a few others (from what I read from the source code).
still where is the latest source for jw1 or jvt ? any updated source i missed ?
$omator said:
still where is the latest source for jw1 or jvt ? any updated source i missed ?
Click to expand...
Click to collapse
No changes for them. Even their initramfs didn't change except for the magic number for the pre-compiled modules.
no changes since august in sources ? are you serious mate ))))
$omator said:
no changes since august in sources ? are you serious mate ))))
Click to expand...
Click to collapse
Yup
Decompile the initramfs and see for yourself
As for the kernel binaries themselves, it's harder to detect. However, no loss of functionality has been reported from custom kernel usage. I'm about 95% sure that no source change occurred.
Platform though, is another matter. The platform changed quite a bit, though all of it are closed sources ones (like Touchwiz).
;] 10 lulz!!
$omator said:
;] 10 lulz!!
Click to expand...
Click to collapse
If there is I didn't notice it. And gingerbread gpu drivers sucks.
Sent from my GT-I9000 using Tapatalk
About gpl and Samsungs obligation to release sources for kernel:
JW1 is not released for public use, is it?
This is a LEAK and should be treated likewise - WYSIWYG
Tapatalked - There's a Thanks button somewhere
shush! they mixup 10 zImage's and it is working
$omator said:
i think that progress in changelog number is too great for the only changes to be were the language typos fixes
using custom kernel is bad
using custom kernel from previous version to some more recent is bad
Click to expand...
Click to collapse
I respect that you hate custom kernels but telling people that 'using custom kernel is bad'...is bad.
Can you please post your arguments?
With your logic XDA should not exist. With your logic nobody should tweak or change the standard products that Samsung delivers. Nobody should experiment. Nobody should try experimental features/tweaks/mods.
Or maybe, nobody except you?
Related
Some people said the new kernel 2.6.35.10 is laggy. I have done a test using Quadrant Advanced.
To be fair, each kernel were tested 5 TIMES. Then select the HIGHEST score.
2.6.32.40
{
"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"
}
2.6.35.13 (I think it is based on 2.6.35.10 in the leaked sense rom)
We can see that the score of memory is a bit low. This may be the reason why sense rom with 2.6.35.10 is laggy.
Thanks for your concern, Sorry for my bad English!!
How much yu overclock the phone?
Sent from my T-Mobile G2 using XDA Premium App
androidfeen809 said:
How much yu overclock the phone?
Sent from my T-Mobile G2 using XDA Premium App
Click to expand...
Click to collapse
Sorry, both are 1516MHz.
nok07635 said:
Sorry, both are 1516MHz.
Click to expand...
Click to collapse
Wow that's impressive, 3000+ @ 1.5 ghz, I get 2200+ @ 1.4 ghz shouldn't I be getting close to 3000 since its not much you have overclocked from 1.42 ghz?
Sent from my T-Mobile G2 using XDA Premium App
With linux in general why has the kernel not gone past 2.6 for as long as I can remember?
Sent from my HTC Vision using XDA Premium App
Here's my score, benched 5 times.
Runnin' UD 3.3.0 w/ Pyros's kernel @ 1.5ghz - smartass governor
Quadrant scores are useless imo. Smartbench 2011 is way more accurate and reliable. But yeah benchmarks dont mean anything, its about how your device runs in real world usage.
xsteven77x said:
With linux in general why has the kernel not gone past 2.6 for as long as I can remember?
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Check this out, but pay special attention to the 4th paragraph. I think it should answer your question:
Version numbering
The Linux kernel has had three different numbering schemes.
The first version of the kernel was 0.01. This was followed by 0.02, 0.03, 0.10, 0.11, 0.12 (the first GPL version), 0.95, 0.96, 0.97, 0.98, 0.99 and then 1.0.[96] From 0.95 on there were many patch releases between versions.
After the 1.0 release and prior to version 2.6, the version was composed as "A.B.C", where the number A denoted the kernel version, the number B denoted the major revision of the kernel, and the number C indicated the minor revision of the kernel. The version was changed only when major changes in the code and the concept of the kernel occurred, twice in the history of the kernel: In 1994 (version 1.0) and in 1996 (version 2.0). The major revision was used according to the traditional even-odd system version numbering system. The minor revision had been changed whenever security patches, bug fixes, new features or drivers were implemented in the kernel.
Since 2004, after version 2.6.0 was released, the kernel developers held several discussions regarding the release and version scheme[97][98] and ultimately Linus Torvalds and others decided that a much shorter release cycle would be beneficial. Since then, the version has been composed of three or four numbers. The first two numbers became largely irrelevant, and the third number is the actual version of the kernel. The fourth number accounts for bug and security fixes (only) to the kernel version.
The first use of the fourth number occurred when a grave error, which required immediate fixing, was encountered in 2.6.8's NFS code. However, there were not enough other changes to legitimize the release of a new minor revision (which would have been 2.6.9). So, 2.6.8.1 was released, with the only change being the fix of that error. With 2.6.11, this was adopted as the new official versioning policy. Later it became customary to continuously back-port major bug-fixes and security patches to released kernels and indicate that by updating the fourth number.
Regular development pre-releases are titled release candidates, which is indicated by appending the suffix 'rc' to the kernel version, followed by an ordinal number.
Also, sometimes the version will have a suffix such as 'tip', indicating another development branch, usually (but not always) the initials of a person who made it. For example, 'ck' stands for Con Kolivas, 'ac' stands for Alan Cox, etc. Sometimes, the letters are related to the primary development area of the branch the kernel is built from, for example, 'wl' indicates a wireless networking test build. Also, distributors may have their own suffixes with different numbering systems and for back-ports to their "Enterprise" (i.e. stable but older) distribution versions. -From Wikipedia
Click to expand...
Click to collapse
Oops! I tested these two kernel again.
The result surprised me.
Tested 5 times for each kernel
2.6.32.40
2.6.35.10 / 2.6.35.13
The performance of 2.6.35.10 is not so bad or even better!
Hey,
I've read various topics on the forum, but they seem to confuse me as they say different things:
when ICS was released, some people said we needed a newer kernel for our nook in order to run ICS. but now, we have a pre-alpha build which runs on the old kernel. There are various other devices which have ICS builds on a 2.6.32.x kernel, so why did some people say that we needed a newer kernel?
Are Dal and fattire building ics ontop of a gingerbread kernel?
And which kernel is the "default" for ics? a 3.0 kernel?
i'd appreciate some answers to enlighten me
Take a look here, from the dev thread, kernel is 2.6.32.9.
{
"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"
}
Homer
Homer_S_xda said:
Take a look here, from the dev thread, kernel is 2.6.32.9.
Homer
Click to expand...
Click to collapse
Yeah, i know we are on that kernel, but my question is: how is this possible? Are they porting ICS to a froyo kernel?
The HD2 uses a froyo kernel too, for it's ICS builds.
But why were people saying when the ics source code was just released that we need a newer kernel before ICS could be ported to our nook?
I think you might be confused between NT and NC.
AFAIK, NT does need newer kernel (as set of drivers since it has new hardware) while NC doesn't require to. I might be wrong though.
It's my understanding that the NC (not sure about the NT) doesn't actually need the new kernel to run, but it would make things a hell of a lot easier. Mainly, the problem seems to be getting outdated hardware drivers working with the newer parts of ICS--thus the lack of sound and video, among others--and that 2.6.35 has code and/or links to drivers that would help. But until B&N updates to that kernel (unlikely for now)m anyone working on CM9 has to deal with the old code and thus has an uphill battle.
IIRC, at first the CM9 team said it might never come to the NC, so I feel like we're kinda lucky. And if you read the first post of the DEV thread, you'll see that they're still iffy (and that's being generous) on a final, working, daily-driver version ever being released.
A lot of misleading info here , I'll try to make it simple and understandable
First , NT has a locked bootloader - it doesn't have anything to do with ICS or kernel ver.
ICS doesn't NEED 3.0 kernel to run ( proven on many devices ) , BUT there are some compatibility issues that needs fixing/back-porting/revere-engineering
and there are some things that can't be exactly ported ( or it's pretty hard and not worthy to reverse engineer ) , such as closed-source drivers
The main issues most devices encounter are GPU & Camera
Since we don't have a cam , the GPU drivers are the main thing to worry about
As dalingrin explained some time ago , there are closed-source libs that we need updated from the manufacturer to support ICS - It seems some can be found compatible with newer kernel versions ( 2.6.35 ) , but again it doesn't promise full support till an official ICS version for a similar spec device comes out
As I see it , a 2.6.35/37/38 or even better 3.0 ( as some devices starting to concentrate on now to get full gpu support & camera working instead of back-porting closed source drivers ) eventually will be necessary , because all we do now is relying on legacy support / hacks
I'm hoping for a community port of 3.0 kernel once ICS port will reach its full potential using 2.6.32 kernel ( now that fat-tire has caused many people to learn how to build , maybe we will see more progress soon )
6/03 : Official topic has been opened
http://forum.xda-developers.com/showthread.php?p=23319217
Get your latest CNA fix there.
This topic is now officially (get it?) dead.
Since no official topic for CNA 1.4.0 has opened, I want to share their latest build.
It has the fixed RIL issues many are looking for.
I do not claim any involvement in the development of the ROM, I'm just a guy who setup a build environment, downloaded the source code and compiled.
As such : treat it as a NIGHTLY, this is NOT an official release so expect no support from me or the devs.
It's just a basic compile so be sure to know EXACTLY what you're doing before flashing.
Code:
ro.build.date=Tue Feb 21 18:26:48 CET 2012
ro.modversion=Codename-Android-(MOD)-1.4.0-GalaxyS
I can recommend flashing another kernel as the original had a tendency to bootloop in the past. But you don't need to listen to me of course.
21/2: http://www.mediafire.com/?rbbh36drchehigt
Edit: Apparently it also has the external SD card fix
26/2: I noticed several changes in their code: mostly kernel, bin, xbin. I compiled again. I'm running the default kernel for now.
http://www.mediafire.com/?81ciaepocyo6wp6
27/2: I've flashed another kernel as the included one caused a dialer wakelock, draining the battery, as well as two reboots.
2/03 : Uploaded another compile
http://www.mediafire.com/?lp54q6x6lkhzf3u
This could be the last one if I read the grapevine correctly.
Click to expand...
Click to collapse
you mean this is the "official" CNA from codenameandroid himself? :-D
You're a legend man. This rom is now perfect!
***Trusty old SGS1 running CNA ICS and Devil kernel 1.1BFS***
Is it DaxIΠFIΠITY ROM or someone else?
This has nothing to do with the Asnet release right? It was stopped because it contained a pay-app.
I want to try this one, but only if I harm nobody's income.
Benjamin
Same procedure as usual?
Which kernel is included here?
1) wipe cache & data/factory reset
2) flash zip
3) reboot phone and wipe again?
Im coming from GB 2.3.3.. cheers
BenjaminX2 said:
This has nothing to do with the Asnet release right? It was stopped because it contained a pay-app.
I want to try this one, but only if I harm nobody's income.
Benjamin
Click to expand...
Click to collapse
You don't have to worry, this is another release.
Mull1s said:
Same procedure as usual?
Which kernel is included here?
Click to expand...
Click to collapse
Yes, don't forget gapps.
Nandroid first !
As far as I know, the kernel is the standard CM9 one.
But you may want to try another ICS rom from in the development section first...
Data/factory reset is necessary in any case?
Wossner said:
Data/factory reset is necessary in any case?
Click to expand...
Click to collapse
It's necessary if you don't come from an other CNA release...
BYTHAWAY Bubble, shouldn't you post this in development section? Or am I wrong?
boris0711 said:
BYTHAWAY Bubble, shouldn't you post this in development section? Or am I wrong?
Click to expand...
Click to collapse
I just compiled someone else's code, so it does not belong there.
How about External storage? Does it fix too?
Pekedel said:
How about External storage? Does it fix too?
Click to expand...
Click to collapse
What do you need to be fixed ?
It is now visible in storage and the music player, is that what you mean ?
{
"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"
}
I upgraded from Dax' release to this one without wipe and everything works fine.
RIL and external SD card issues have been solved.
The only thing that didn't work (didn't show up in the app list) was the Galaxy S Settings (AriesParts.apk), so I copied the one from Dax to /system/app and then it worked.
Is this rom have gb graphic leftovers?
Like orange stuffs,green buttons?
malcho said:
Is this rom have gb graphic leftovers?
Like orange stuffs,green buttons?
Click to expand...
Click to collapse
Like any AOSP ICS, it has. But that can easily be remedied by this.
Bubble-be said:
Like any AOSP ICS, it has. But that can easily be remedied by this.
Click to expand...
Click to collapse
Thanks i will try it.
MrMagic said:
I upgraded from Dax' release to this one without wipe and everything works fine.
RIL and external SD card issues have been solved.
That's answer my question. Thanks. Now I can start flash your rom Bubble-be.
Click to expand...
Click to collapse
Bubble-B
Thanks again for compiling this for us. Everything seems to work including Wi-Fi tethering solo!
Was wondering if you could use this commit to compile a deep idle top-OFF modded framework-Res.
https://github.com/peteralfonso/platform_vendor_pete/commit/a19d2a56ccf07b9ab53a44b7ba5605a1aaffd9e6
Unlike the other ICS ports this one seems to work glitch free. I was using this one on the previous 1.4 build with amazing success but it isn't compatible with this rom... Not 100% sure that commit is in this modded framework sorry.
http://db.tt/PMXOVx4K
***Trusty old SGS1 running CNA ICS and Devil kernel 1.1BFS***
rlorange said:
Bubble-be
Was wondering if you could use this commit to compile a deep idle top-OFF modded framework-Res.
Click to expand...
Click to collapse
I decided to indulge you as it's a friday night, so I edited that xml and ran the compile. Give it a shot, but you know it's mostly placebo right ?
{
"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"
}
Overview
Pure AOSP for Cancro
Features
- No T-mobile theme engine or Layers, It is just stock AOSP.
- No .dat features
Download
Developer-Preview-1
Working
- Everything (unless I missed something, pretty sure I didn't)
Sources
My codebase is uploading.
GPL stuff:
Kernel used can be found here
Extended Information
I created this for firmware developers, It is for forking stock firmware such as MIUI.
If people choose to use this to port MIUI I obviously cannot stop them, but blah blah, beta software, blah.
This firmware uses the structure everyone loved in KitKat; I will not force anyone to deal with the .dat nonsense that we've all come to know and hate.
The codebase aligns very closely to what Xiaomi uses, and this code-base also aligns with many other vendor firmware.
Thx to: Datagutt, Heheda; co-maintainers :<
Thx to: Firmware developers, the source builders for this device
What is this exactly?
Works on mi4 ?
tendulkaradi said:
What is this exactly?
Click to expand...
Click to collapse
It's pure AOSP, and yes it's good to work on any device that idents as Cancro
It is designed specifically for use with porting firmware, recovery has been modded in source to allow for this more easily as well.
It is easy to build either CAF or deCAF firmware in this build engine, I designed it to be very easy like CyanogenMod and it does accept CM configs.
HOWEVER IT IS AOSP AND NOT SLIMROM OR CYANOGEN I can't stress this enough, It is AOSP
Will work for mi4.?
droidead said:
Will work for mi4.?
Click to expand...
Click to collapse
He already answered this question
@MonoIiths can you try building the Android M 6.0 (AOSP) with the same tree and blobs?
Link not working
contactwajeeh said:
@MonoIiths can you try building the Android M 6.0 (AOSP) with the same tree and blobs?
Click to expand...
Click to collapse
Ivan is already building android M. He will give a base rom which can be used for custom roms.
vishal24387 said:
Ivan is already building android M. He will give a base rom which can be used for custom roms.
Click to expand...
Click to collapse
My work is better
Edit: At least with source-build; his AOSP is not useful for porting ROM where mine actually is.
Android M will be the same in that case; when I decide to build it
Ir blaster an FM work in this rom?
camera quality, HDR?
hdr bug is still present, hdr mode click complete dark pictures, normal mode quality is fine. Can u manage to focus on camera quality .otherwise rom is good ,still haven't tested full
Source is still uploading?
Sent from my MI 3W using Tapatalk
Bitti09 said:
Source is still uploading?
Sent from my MI 3W using Tapatalk
Click to expand...
Click to collapse
Yes, my build engine is really huge and has multiple GCC forks depending on the firmware used :<
Neat clean stock ROM. Though meant to for porting and etc stuff. But as a user I like it, it's smoooth.
Everything is great except some minor stuff eg: long Wi-Fi turning on time, WCDMA Only mode reset after reboot, CPU frequency control not working proper with stock kernel.
These are minor stuff and I'm not complaining neither asking you to do anything about it.
PS if anybody has a solution for 3G Only reset would be glad.
Hope I can see a 6.0 ROM by you soon
Also, there's a lag between screen and capacitive keys becoming inactive.. say if I turn off screen and the very next second I touch capacitive keys the screen wakes up.
MonoIiths said:
My work is better
Edit: At least with source-build; his AOSP is not useful for porting ROM where mine actually is.
Android M will be the same in that case; when I decide to build it
Click to expand...
Click to collapse
We already Have @Bitti09 for this...we already have lots of lollipop ROMs...and u are late by a year ?
Sent from my MI 3W using Tapatalk
tendulkaradi said:
We already Have @Bitti09 for this...we already have lots of lollipop ROMs...and u are late by a year
Sent from my MI 3W using Tapatalk
Click to expand...
Click to collapse
But you still don't have 5.1.1 MIUI v7
MonoIiths said:
But you still don't have 5.1.1 MIUI v7
Click to expand...
Click to collapse
But we have bunch of official lollipop custom roms.
Hello Everyone!
I've been working on my thuglife™ kernel for bullhead for a while, have included it in some ROMs, have released it yet
I'm planning to release it soon, and hence want to know how it is, and if you'll have some requests for it, etc
https://sourceforge.net/projects/thuglife/files/bullhead
There are a lotta zips there, been uploading quite a few of my builds
Latest one I'm currently running has been updated of Linux kernel version 3.10.99, and compiled with Ubertc 5.3
https://sourceforge.net/projects/thuglife/files/bullhead/thuglife-bullhead-20160305.zip
Kernel source --> https://github.com/akhilnarang/ThugLife_bullhead
I'm not really a kernel developer, just like having my own though, with all the features I like and want, all credit goes to various developers who actually wrote everything that's in the kernel
Enjoy
Sent from my Nexus 5X using Tapatalk
{
"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"
}
PS. - Huge thanks to @TJSteveMX for testing some builds and helping me debug stuff by providing logs
yeah, been running this kernel for a month now i guess.... good work tho
sharing the love is a great step for developing. good good...
Great! Hope to see your work on sprout.
akhilnarang said:
Hello Everyone!
I've been working on my thuglife™ kernel for bullhead for a while, have included it in some ROMs, have released it yet
I'm planning to release it soon, and hence want to know how it is, and if you'll have some requests for it, etc
https://sourceforge.net/projects/thuglife/files/bullhead
There are a lotta zips there, been uploading quite a few of my builds
Latest one I'm currently running has been updated of Linux kernel version 3.10.99, and compiled with Ubertc 5.3
https://sourceforge.net/projects/thuglife/files/bullhead/thuglife-bullhead-20160305.zip
Kernel source --> https://github.com/akhilnarang/ThugLife_bullhead
I'm not really a kernel developer, just like having my own though, with all the features I like and want, all credit goes to various developers who actually wrote everything that's in the kernel
Enjoy
Sent from my Nexus 5X using Tapatalk
PS. - Huge thanks to @TJSteveMX for testing some builds and helping me debug stuff by providing logs
Click to expand...
Click to collapse
Great new stuff for the 5X users,
off topic question but where did you get your navigation bar icons from?
Great kernel. Thank you
First of all, thank you for sharing your work! I flashed this just a few minutes ago, no immediate problems so far. I liked the fact that it's optimized with Uber and is based off the latest Linux version. I did run into one problem, however. I cannot select Zen as my I/O scheduler. I appears on the list in ElementalX Kernel Manager, but selecting it does nothing. I switched to SIO Plus for now, but this issue did not occur in Phasma Kernel which also has the Zen scheduler.
Alcolawl said:
First of all, thank you for sharing your work! I flashed this just a few minutes ago, no immediate problems so far. I liked the fact that it's optimized with Uber and is based off the latest Linux version. I did run into one problem, however. I cannot select Zen as my I/O scheduler. I appears on the list in ElementalX Kernel Manager, but selecting it does nothing. I switched to SIO Plus for now, but this issue did not occur in Phasma Kernel which also has the Zen scheduler.
Click to expand...
Click to collapse
Will check it out, thanks for the feedback
@JustPlayingHard : please don't quote full OP
The navbar is from iLayers theme
http://blazingphoenix.in/akhilnarang/ThugLife/bullhead/thuglife-bullhead-20160320.zip
Here's a new build, kernel is updated to 3.10.101, and March kernel updates included
Please test and let me know how it is
akhilnarang said:
http://blazingphoenix.in/akhilnarang/ThugLife/bullhead/thuglife-bullhead-20160320.zip
Here's a new build, kernel is updated to 3.10.101, and March kernel updates included
Please test and let me know how it is
Click to expand...
Click to collapse
Any info for the new build dated for August 13th?
https://github.com/akhilnarang/ThugLife-Misc has a changelog for builds
Sent from my Nexus 5X using Tapatalk
akhilnarang said:
https://github.com/ThugLife-Misc has a changelog for builds
Click to expand...
Click to collapse
Link ends in 404
TW1ST3D1NS4N3 said:
Link ends in 404
Click to expand...
Click to collapse
Fixed link
Sent from my Nexus 5X using Tapatalk
akhilnarang said:
Fixed link
Click to expand...
Click to collapse
Could there be a problem on my end somehow? Still getting same issue.
https://github.com/akhilnarang/ThugLife-Misc?files=1
Any future plans?