a new Linux file system from Samsung that is faster than existing ones when running on flash storage devices, submitted in a clean, easy-to-apply manner. This will be great for Android-based systems.
#source: G+
ithunter said:
a new Linux file system from Samsung that is faster than existing ones when running on flash storage devices, submitted in a clean, easy-to-apply manner. This will be great for Android-based systems.
#source: G+
Click to expand...
Click to collapse
Look at this.. XDA users are on the case already!
I like the idea behind this filesystem!
As the OP of the thread said, it is possible but we would need a new recovery and edit the kernel to add F2FS (that's the name, right?) formatting and detecting support. What I'm confused about is whether or not we are gonna need USB drivers if we use this. Please explain.
Is this lwn.net/Articles/518718/ what you're talking about?
Sent from my rooted tomato using xda app
I dont have a single ideea what f2fs means but i smell nAa-15 kernel.
Sent from my X8 using xda app-developers app
Hmm, interesting... wonder what advantages it has compared to YAFFS2.
i guess efficient flash storage, that is if Sammy doesn't screw it up like they did with RFS.
i hope it's good. i also hope it can be made to work with the X8.
fingers crossed.
We can get this working on the x8.. It's just a matter of compiling it into the kernel, editing the ramdisk and recovery.
Kernel & ramdisk bits are really simple..
I haven't found yet what needs to be edited in the recovery. Anyone any leads on this?
This will give us much higher sd read & write with less overhead so the sdcards will last much longer and will fragment less.
They don't have a fsck for it yet but it has full logging and journaling..
Can even choose to only convert system and data and leave bootimage/recovery as is.
Sent from my GT-I9300 using xda premium
yes but when you format a system based on the new FS, you need to have a recovery that supports it.
@CtrlAltDelIrl
then compile a kernel that supports it as soon as Samsung releases it's source (it is open source, right?)
sgt. meow said:
yes but when you format a system based on the new FS, you need to have a recovery that supports it.
@CtrlAltDelIrl
then compile a kernel that supports it as soon as Samsung releases it's source (it is open source, right?)
Click to expand...
Click to collapse
The source is already available.. I might just do that!
sgt. meow said:
yes but when you format a system based on the new FS, you need to have a recovery that supports it.
@CtrlAltDelIrl
then compile a kernel that supports it as soon as Samsung releases it's source (it is open source, right?)
Click to expand...
Click to collapse
So the kernel in recovery needs to support it, problem solved.
Sent from my GT-I9300 using xda premium
yes but the recovery binary that we have in the kernel is compiled from a regular CM tree and settings have to be changed there (not sure which) before compiling the binary. maybe nAa, alfsamsung, CtrlAltDelIrl, other devs or a team of devs can come up with one such recovery and kernel.
It is not that hard, when you have that kernel compiled and in device sources (or build it during the progress like we do on LG P500) you can build a recovery which supports it.
Sent from my GT-I9300 using xda premium
_Arjen_ said:
It is not that hard, when you have that kernel compiled and in device sources (or build it during the progress like we do on LG P500) you can build a recovery which supports it.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
exactly what i meant.
Related
please see thread in dev section
Onecosmic our kernel guy made it
Pawtip for recent help on ril.
I thank nikademus for creating the kernel for us in first place.
And a general thanks to the rest of the people in this thread that helped in this.
AFAIK the boot.img for SGS is different from boot.img of other phones. To decompile boot.img dsixda kitchen is used. It gives an error for our phones when we try to extract the contents of boot.img "Android header not found"...the file doesn't get extracted. Thats the problem.
May be a decent developer can guide us at this point??
muzicfreako said:
AFAIK the boot.img for SGS is different from boot.img of other phones. To decompile boot.img dsixda kitchen is used. It gives an error for our phones when we try to extract the contents of boot.img "Android header not found"...the file doesn't get extracted. Thats the problem.
May be a decent developer can guide us at this point??
Click to expand...
Click to collapse
Yes i tried that also!
Sent from my GT-I9000 using Tapatalk
Actually we need the ramdisk file from boot.img. And forr galaxy S the kernel in not inside boot.img as we can see in every rom we have.
Unless theres a way to edit this boot.img...we're stuck.
Nobody?
Sent from my GT-I9000
Well im in conversation w some kernel devs to cook some kernel with that init.rc modified...
Sent from my GT-I9000
*subscribing*
the phone is quite similar to the GT-i9000 or at least the Nexus S right ?
so it should be achievable
we need a central github repo [preferrably in an organization] for kernel sources, etc.
Well this sounds exciting
Sent from my GT-I9000 using XDA App
progress...
well, i have spoken with nikademus, he made a specific kernel for this, gonna test now, later i post a link with boot.img for another dev to test the rom...
http://www.multiupload.com/HS59X8PISQ
zacharias.maladroit said:
*subscribing*
the phone is quite similar to the GT-i9000 or at least the Nexus S right ?
so it should be achievable
we need a central github repo [preferrably in an organization] for kernel sources, etc.
Click to expand...
Click to collapse
right the nexus s and galaxy s are quite similar, remembre that cyanogen rom was first ported from nexus s to sgs.
well i'm not a experienced Guy in this, i want to get it to work but if we join forces maybe the goal is achieved early.
How can i help?
malcho said:
How can i help?
Click to expand...
Click to collapse
the goal is to port nexus s 4g ics sdk rom to i9000
http://forums.androidcentral.com/sp...oms-hacks/127806-rom-ics-sdk-port-wip-22.html
Did the specialized kernel work.
yes yes yes was waiting for someone to initiate this best of luck with development.. and do keep the first post updated of the happenings!
It is working with the boot.img file that Netmatrix shared? Tks.
most of the services died, getting bootloops...
Continue testing...
Sent from my GT-I9000
good luck and keep it posted!
Later on, i put logcat here...
Sent from my GT-I9000
but just boot.img has to be changed to make SGS to boot with ICS?
Its not, build.prop had to be changed....
Sent from my GT-I9000
I found this tread that makes an install of Linux on every mobilephone, could this be usefull?? I am not a developer but I think this thing belongs to Development, if not I am sorry and ask mods to move this.
So what you want to do is install webtop as a linux OS on the atrix?
I think its not posible...but maybe Im wrong
from the (m)ATRIX...
Quote from that thread:
This projects aim is to bring a range of linux distros to your android device through a method known as 'chroot',
Click to expand...
Click to collapse
As far as I know, this is already available for the Atrix's webtop since forever ago, through debian chroot (and possibly webtop2sd).
ravilov said:
Quote from that thread:
As far as I know, this is already available for the Atrix's webtop since forever ago, through debian chroot (and possibly webtop2sd).
Click to expand...
Click to collapse
Since this is a project working on also other devices w/o webtop functionality, maybe it could help in having webtop in cyanogenmod and other custom ROM builted from sources!
gianluca.tomat said:
Since this is a project working on also other devices w/o webtop functionality, maybe it could help in having webtop in cyanogenmod and other custom ROM builted from sources!
Click to expand...
Click to collapse
Its been done, over a year now. here Just root and install this.
Djazin said:
Its been done, over a year now. here Just root and install this.
Click to expand...
Click to collapse
I know, but I posted the link here so that maybe some devs could possibly integrate it into a ROM so that when you connect the phone to tv/dock it boots automatically into linux distro!
It doesn't work like that. You have to actually start the hardware side of things on the tegra2 chip, it has nothing to do with the chroot linux distro, which is very old news (and all the devs know about it). What you essentially have to do is code the x session to send itself over the seperate hdmi output frame buffer, which also has to be triggered and deactivated properly.
No developer has been interested in really trying it. Jokersax was working on it at one point in CM9, but scrapped it due to upstream changes that broke his code.
This doesn't really belong in this section, and I've given you the actual reason why there's more to this than you think. Also, as I said, everyone knows about running linux on android in this fashion, as it's a very old project at this point.
Yup, chroot methods won't help a bit
I believe that webtop on cm is something that Samcripp is still trying to make work...
http://forum.xda-developers.com/showthread.php?p=29376000
When the official ICS comes out, we just might have webtop on cyanogenmod
;29914961 said:
Yup, chroot methods won't help a bit
I believe that webtop on cm is something that Samcripp is still trying to make work...
http://forum.xda-developers.com/showthread.php?p=29376000
When the official ICS comes out, we just might have webtop on cyanogenmod
Click to expand...
Click to collapse
Maybe yes maybe no, because CM7 which is based on gingerbread (we do have official gingerbread) still dont have webtop integration...
Sent from my MB860 using xda premium
Ok sorry guys!
bimasakti85 said:
Maybe yes maybe no, because CM7 which is based on gingerbread (we do have official gingerbread) still dont have webtop integration...
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
The gingerbread webtop is a hack by Motorola. Even tho is a linux distribution its tightly woven into android libraries. This libraries without source can't be added into cm7.
Cm9 is different. Ics is capable of switching to tablet mode. Offering a better option than just plain locked down linux. We shall see.
Sent from my MB860 using xda premium
there is gentop2
search it
Sent from my MB860 using xda premium
Searching a dev who understand about source ... i wona build mozilla boot to Gecko for X8 :fingers-crossed: or help in this theard ..
1.Resize - http://forum.xda-developers.com/showthread.php?t=1593121
2. or build from source - https://github.com/mozilla-b2g/B2G
And tut from here - https://developer.mozilla.org/en-US/docs/Mozilla/Boot_to_Gecko/Building_and_installing_Boot_to_Gecko
Yes .. the system its too big for our device... so i search and a dev for kernel or help (to do sd-ext in kernel)
And why..B2G is alpha stage..wait for stable ROM
Sent from my E15i using xda premium
I know.. but you wona say its not better to do it ........
Honestly, why? Why on earth would you need B2G on an X8? You're far better off trying to develop for JB or ICS. But I support you and would also like to help, but I cannot download the sources as my Internet connection sucks big time. And also you need to figure out a way to run the kernel from sd-ext if I'm not mistaken. So if the sdcard goes bust somehow, the user's screwed (for some time), right? Keeping these things in mind, I personally feel that developing for JB or ICS would be far better. Still with you, if you need any help.
souljaboy11792 said:
Honestly, why? Why on earth would you need B2G on an X8
Click to expand...
Click to collapse
Sometime the world is not enough for you. There gonna be something better from the basic.
People want an innovative and not honestly "Argh argh" who sue for thier innovative
souljaboy11792 said:
Honestly, why? Why on earth would you need B2G on an X8? You're far better off trying to develop for JB or ICS. But I support you and would also like to help, but I cannot download the sources as my Internet connection sucks big time. And also you need to figure out a way to run the kernel from sd-ext if I'm not mistaken. So if the sdcard goes bust somehow, the user's screwed (for some time), right? Keeping these things in mind, I personally feel that developing for JB or ICS would be far better. Still with you, if you need any help.
Click to expand...
Click to collapse
Honestly, im sick and tired of hearing JellyBean =.= it'd be nice to hear something else for a change
Please, stop this "Why on earth would you need B2G " .. If any wona help me, write PM
You can take a look at the github.com/adfad666 .
He started on porting to LG P500. As we share the same chipset it can be used as base for x8 too.
It compiles for us, but we have some booting issues. But if someone over here manages to solve it...
Sent from my GT-I9300 using xda app-developers app
Mozilla Boot to Gecko Coming up tomorrow - Builded from source and MDPI Resized !!
Now i up GitHub Source !!!!
So you got it booting? Super!
Sent from my GT-I9300 using xda app-developers app
_Arjen_ said:
So you got it booting? Super!
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Not think ... ..... I need Kernel dev for booting .. For more info follow my twitter !
Edit : Just wait tomorrow
Heard from Adfad666 that a lot of code is armv7-based, so there is still some work...
You should use nAa cm9 kernel for it.
Sent from my GT-I9300 using xda app-developers app
_Arjen_ said:
Heard from Adfad666 that a lot of code is armv7-based, so there is still some work...
You should use nAa cm9 kernel for it.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Yes.. it will nAa-ics only
i changed my mind. move over jellybean hello B2G. so how'd you get it booting and how'd you fix the kernel from sd-ext thingy?
souljaboy11792 said:
Honestly, why? Why on earth would you need B2G on an X8? You're far better off trying to develop for JB or ICS. But I support you and would also like to help, but I cannot download the sources as my Internet connection sucks big time. And also you need to figure out a way to run the kernel from sd-ext if I'm not mistaken. So if the sdcard goes bust somehow, the user's screwed (for some time), right? Keeping these things in mind, I personally feel that developing for JB or ICS would be far better. Still with you, if you need any help.
Click to expand...
Click to collapse
Honestly why on earth would you need (check out my tuts).but its nice to have them
good point fotak-x which is exactly why i changed my mind? it'd be nice to see B2G running on our phones, even if it's just a proof of concept.
have you stopped working on it ? Because as I can see on your twitter you are into sense nowadays
Good luck Danibosdev
Envoyé depuis mon X8 avec Tapatalk
OK, so I am not a dev.
And iam completely newbie
I saw some people saying that if you have aosp on your device it's much easier to port omnirom for your device
So can I use CyanogenMod 10.2 that is available for the i9100
To build omni
And is there any detailed instruction on how to build it !!
Sent from my GT-I9100 using Tapatalk 4
I9100 needs some work because of its unified kernel, building it right now is pretty much useless if you don't know where to put your hands to solve some issues; I want to try it too but this project is in a early stage so I'll wait
Sent from my GT-I9100 using xda app-developers app
filllob said:
I9100 needs some work because of its unified kernel, building it right now is pretty much useless if you don't know where to put your hands to solve some issues; I want to try it too but this project is in a early stage so I'll wait
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Yup. There are two MAJOR blockers right now:
1) We haven't merged and tested the implementation of BOARD_SUPPRESS_EMMC_WIPE yet. So if someone were to build for a Superbrick-vulnerable device, they would have a a build that risks triggering Superbrick. While I normally don't like having moderators take down builds for something, if I see builds for Superbrick-vulnerable devices show up, I'm going to work with the mods to have them taken down until EMMC wipe suppression can be verified.
2) The build system needs some changes to permit TWRP to be built on userdebug builds. Right now, the only way you'll have a chance of working recovery is with an eng build.
Entropy512 said:
Yup. There are two MAJOR blockers right now:
1) We haven't merged and tested the implementation of BOARD_SUPPRESS_EMMC_WIPE yet. So if someone were to build for a Superbrick-vulnerable device, they would have a a build that risks triggering Superbrick. While I normally don't like having moderators take down builds for something, if I see builds for Superbrick-vulnerable devices show up, I'm going to work with the mods to have them taken down until EMMC wipe suppression can be verified.
2) The build system needs some changes to permit TWRP to be built on userdebug builds. Right now, the only way you'll have a chance of working recovery is with an eng build.
Click to expand...
Click to collapse
Can we not use cm10.2 smdk4412 kernel, @Entropy512? EMMC_WIPE is disabled there?
Also, would there be any problems if one were to remove Omni bootable project and replace it with cm10.2's?
chasmodo said:
Can we not use cm10.2 smdk4412 kernel, @Entropy512? EMMC_WIPE is disabled there?
Also, would there be any problems if one were to remove Omni bootable project and replace it with cm10.2's?
Click to expand...
Click to collapse
No, because it could still cause damage if flashing from an old "unsafe" kernel (see the first few CM10 builds as an example...). These are far rarer now than they used to be, but there are, believe it or not, occasionally people who are flashing stuff starting from TW ICS.
And CWM has tentacles throughout the CM source tree to get it to build. It requires too many hacks in too many places. TWRP is more standalone, the limitation being that on devices with standalone recovery, Dees_Troy always built using the "eng" variant instead of "userdebug".
There's a patch that allows for TWRP to build properly on userdebug using "make recoveryimage" but it fails to allow building of TWRP into unified-recovery devices like Sony pollux_windy/yuga. (Samsung requires even more hacks...)
Even the Sonys which are "sort of" working aren't ready for builds yet - for them to work they're dependent on the FOTAKernel trick Dees_Troy developed to allow for alternate recoveries to be put on a device.
Does the above apply also to the i9100g? It has an OMAP4 processor instead of Exynos so it should be easier to build for.
aidfarh said:
Does the above apply also to the i9100g? It has an OMAP4 processor instead of Exynos so it should be easier to build for.
Click to expand...
Click to collapse
I'm fairly certain the G has unified kernel/recovery just like most of the rest of the galaxys2 family (exception being the Qualcomm-based ones).
So it might build, but recovery will not function at all until the build system is fixed to properly support TWRP on devices with unified kernel/recovery.
It has nothing to do with Qualcomm vs. OMAP vs. Exynos, except that for whatever reason, Samsung actually allowed the recovery partition to serve its normal purpose on the Skyrocket and Hercules. Actually, the Straight Talk variant of the SGH-I777 might work, as that oddball device actually DID use its recovery partition.
Entropy512 said:
I'm fairly certain the G has unified kernel/recovery just like most of the rest of the galaxys2 family (exception being the Qualcomm-based ones).
So it might build, but recovery will not function at all until the build system is fixed to properly support TWRP on devices with unified kernel/recovery.
It has nothing to do with Qualcomm vs. OMAP vs. Exynos, except that for whatever reason, Samsung actually allowed the recovery partition to serve its normal purpose on the Skyrocket and Hercules. Actually, the Straight Talk variant of the SGH-I777 might work, as that oddball device actually DID use its recovery partition.
Click to expand...
Click to collapse
Is there anything I can do to help? Maybe if I can make it work on my device?
So the I9000 got a build of OmniRom, I thought it has also a unified kernel !!!
I was searching on Google today
and I suddenly found this
http://forum.xda-developers.com/showthread.php?t=2494127
that's an alpha build for I9100
it's using the CM10 kernel and it uses CWM not TWRP
Iam testing it right now
Jiangyi had some success getting i9100g working last night
I'm attempting to build for n7000 to see if it works at all... Who knows. Although I still need to merge in BOARD_SUPPRESS_EMMC_WIPE...
Entropy512 said:
Jiangyi had some success getting i9100g working last night
I'm attempting to build for n7000 to see if it works at all... Who knows. Although I still need to merge in BOARD_SUPPRESS_EMMC_WIPE...
Click to expand...
Click to collapse
I built it for Note already
http://forum.xda-developers.com/showthread.php?t=2495930
Sent from my GT-N7000 using Tapatalk
Yes @herna,you built it without a working recovery and without further testing. Nonetheless, it is running flawlessly, quicksand fluid with Raw kernel r3 and it's Cwm recovery.
Would you mind having a look at this commit.
http://review.cyanogenmod.org/#/c/50800/
Fixed the mobile data drop while calling. Thanks
GALAXY NOTE N7000 // OMNI ROM // JLS36I
AA1973 said:
Yes @herna,you built it without a working recovery and without further testing. Nonetheless, it is running flawlessly, quicksand fluid with Raw kernel r3 and it's Cwm recovery.
Would you mind having a look at this commit.
http://review.cyanogenmod.org/#/c/50800/
Fixed the mobile data drop while calling. Thanks
GALAXY NOTE N7000 // OMNI ROM // JLS36I
Click to expand...
Click to collapse
Yeah I know. Entropy and me are looking for the error, but is not beeing easy to fix. Okey, will add in a few hours and release new one. And I correct you, except the latest version, I tried all versions I released and some others I didn't release. I always do but that day I needed phone for important family things and couldn't test
Also I went to release with a prebuilt TWRP 3.0.101 kernel but XplodWilD say me that this will get Semi-Official maybe, and only compiled non-touched ROMs will be released.
Sent from my GT-N7000 using Tapatalk
@Entropy512 just wondering if your commit "i777 bringup" can be applied (obviously with some changes) to i9100
Sent from my GT-I9100 using xda app-developers app
filllob said:
@Entropy512 just wondering if your commit "i777 bringup" can be applied (obviously with some changes) to i9100
Click to expand...
Click to collapse
n7000 bringup would be easier, methinks.
filllob said:
@Entropy512 just wondering if your commit "i777 bringup" can be applied (obviously with some changes) to i9100
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Ask some DEV to try and see if works
Enviado desde mi GT-N7000 mediante Tapatalk
---------- Post added at 01:45 PM ---------- Previous post was at 01:44 PM ----------
chasmodo said:
n7000 bringup would be easier, methinks.
Click to expand...
Click to collapse
N7000 is gonna be up as soon as XplodWild get free and merge it and change something I said him. Idk why my Gerrit is not working. I am gonna install Ubunt 13.10 for clean and will set up all again for try if I can get Gerrit working again
Enviado desde mi GT-N7000 mediante Tapatalk
I'd like to try it myself, just want to know if it's legit or not
Sent from my GT-I9100 using xda app-developers app
filllob said:
I'd like to try it myself, just want to know if it's legit or not
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
If is legit what? I cannot understand you, sorry. You want to try, to compile...?
i am a noob to compiling etc, only followed cm instructions.
I want to know if the changes in the commit I mentioned can be applied to i9100 too, obviously with some adjustments, and if there is something more to do to compile omni for i9100
I hope I explained myself right( English is not my language)
Sent from my GT-I9100 using xda app-developers app
http://www.sammobile.com/2013/11/05/samsung-releases-android-4-3-kernel-source-for-galaxy-s3/
Wow man latest news isn t it?? Using Internet Explorer??
And? Could you explain a bit in how it help us?
Thanks.
Enviado desde mi GT-I9300 usando Tapatalk
It means we can finally have custom kernels woooooo
Sent from my GT-I9300 using XDA Premium 4 mobile app
Well, I downloaded the source kernel and I need a clear way how to compile it smoothly. I wonder whether I can flash the kernel via Odin or CWM to a rooted stock I9300XXUGMJ9 firmware or not. Will it work? Any walkthroughs?
ahmedmelm said:
Well, I downloaded the source kernel and I need a clear way how to compile it smoothly. I wonder whether I can flash the kernel via Odin or CWM to a rooted stock I9300XXUGMJ9 firmware or not. Will it work? Any walkthroughs?
Click to expand...
Click to collapse
http://source.android.com/source/building.html
Read everything on left hand side
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
rootSU said:
http://source.android.com/source/building.html
Read everything on left hand side
Click to expand...
Click to collapse
That's way cool. But any matter to accelerate the process? Would really compiling this kernel and pushing it to existing ROM work?
What do you think source code is exactly? What is it you think you want?
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
I know this is not a Q&A thread but could I ask? Does this release of source kernel code mean, that Samsung finally released the source code for the dreaded mali GPU driver and the FM radio blobs that we so need to make CM roms fully functional and smooth?
granets said:
I know this is not a Q&A thread but could I ask? Does this release of source kernel code mean, that Samsung finally released the source code for the dreaded mali GPU driver and the FM radio blobs that we so need to make CM roms fully functional and smooth?
Click to expand...
Click to collapse
No. Read following for explanation.
dhiru1602 said:
Blobs are userspace components which correspond to the HAL (Hardware Abstraction Layer). It is this layer which is responsible for communication between the kernel and the operating system. GPU kernel driver is opensource, but the GPU HAL is closed source. This is the case with all the devices, but on our device, much more components of the HAL are closed source like FIMC, FIMG, HWJPEG, TVOUT. Samsung doesn't release the source code for this components because it doesn't necessarily have to. Without the source code, we are forced to use the compiled binary which may or may not work properly. Since we are left without options, we often mess around with the Android framework, making dirty hacks to get them to work. We will not be able to futureproof our device with newer versions of Android unless we have the source code since making edits on compiled binaries is not possible and hence we have to wait for official releases so that we could get newer binaries (blobs). Here is the list of all the blobs that we use on our device. Having proprietary code is not uncommon, but Samsung doesn't release the source code for essential parts of the OS like Graphics subsystem, OMX and DSP, which makes things more complex provided there is no documentation for the SOC, nor they are wiling to help developers.
Click to expand...
Click to collapse
dhirend_6d said:
No. Read following for explanation.
Click to expand...
Click to collapse
Thanks for the explanation. So basicaly those kernel sources don't mean much. And I was so excited
granets said:
Thanks for the explanation. So basicaly those kernel sources don't mean much. And I was so excited
Click to expand...
Click to collapse
They mean as much as every other kernel source release. We still dont have everything we need to make AOSP work properly, but we can now get custom kernels for 4.3 touchwiz roms.
rootSU said:
They mean as much as every other kernel source release. We still dont have everything we need to make AOSP work properly, but we can now get custom kernels for 4.3 touchwiz roms.
Click to expand...
Click to collapse
These include the latest mali r3p2. So we have now userspace binaries + kernel source drivers. It makes this possible, which is awesome. It's coming for all exynos4 devices.