I posted this in another thread about flashing S6 Edge roms on an S6. My post was prior to getting my S6. I had gotten my S6 information from a SM-G920I forum. I made the wrong assumption that all S6s would have the same partition layout, they don't. Once I got my S6 I found that the Sprint S6 and Edge did have the same partition layout. So flashing Sprint S6 Edge roms on an Sprint S6 does work. The OP of that post said, "I think that we have exhausted this topic." I am honoring the OP request, so started this thread.
With little happening, development wise, on the Sprint S6, we should be having this discussion. I came from the S4 and many of the roms that I ran were international roms. Their development far exceeds development on the Sprint variant. @AntaresOne's optimized CM 12.1 is definitely one of the best roms for the S4. @chenxiaolong's work on dualboot made possible running multiple roms on an S4 (this now works on the S6 Edge and so S6). @AntaresOne also added multirom support (@tassadars Nexus 7 work) for the S4. These are just some of the international S4 work that worked on the Sprint S4. I am sure in the future much of the good international work will work on the Sprint S6. We know from my incorrect post that SM-G920I (India) roms would have problems on our Sprint S6 without modifications to the updater script.
Continue the dialog here. We need to make International development work on our Sprint variant.
International ROMs are created for GSM phones, not CDMA phones. So unified development requires as you mentioned a proper update.script, an aroma like installer and either detection of carrier or have you choose so that the proper kernel can be installed, as the kernels will be a little different...so there would need to be correct kernels included to correspond with the chosen carrier.
KennyG123 said:
International ROMs are created for GSM phones, not CDMA phones. So unified development requires as you mentioned a proper update.script, an aroma like installer and either detection of carrier or have you choose so that the proper kernel can be installed, as the kernels will be a little different...so there would need to be correct kernels included to correspond with the chosen carrier.
Click to expand...
Click to collapse
Most of the innards is above my pay scale. However, I think what you are saying is probably all true for TW Albe95, Echoe, etc.) , but for AOSP so so. Once CM was unified, this opened the door for many of the AOSP roms (CM, pacman, GPE, etc). I do not know how they managed unified, but it was done with the same kernel, did not require aroma, and no changes to the updater script. I know dualboot patches the updater script in addition to other things and does flashes by name as opposed to partition number (/dev/block). I surely hope this technology gets carried over to the S6.
todivefor said:
Most of the innards is above my pay scale. However, I think what you are saying is probably all true for TW Albe95, Echoe, etc.) , but for AOSP so so. Once CM was unified, this opened the door for many of the AOSP roms (CM, pacman, GPE, etc). I do not know how they managed unified, but it was done with the same kernel, did not require aroma, and no changes to the updater script. I know dualboot patches the updater script in addition to other things and does flashes by name as opposed to partition number (/dev/block). I surely hope this technology gets carried over to the S6.
Click to expand...
Click to collapse
What is used is auto-detection and then auto-selection of proper kernels during the flashing which would be unseen to the user. This was mostly beneficial to the developers and maintainers because then they only had to monitor one thread.
KennyG123 said:
What is used is auto-detection and then auto-selection of proper kernels during the flashing which would be unseen to the user. This was mostly beneficial to the developers and maintainers because then they only had to monitor one thread.
Click to expand...
Click to collapse
What you refer to as auto-detection and auto-selection is all built into the rom or kernel, not the updater script. Most of my experience is with CM12.1 optimized which is unified by @AntaresOne and uses the @Alucard kernel. Neither rom nor kernel zips have any auto-selection in their updater scripts. Each has only one boot.img. I have flashed @Alucard's and @ktoonsez's kernels on both CM12.1 optimized and jfltespr CM12.1 nightlies along with other AOSP roms. As I can flash a unified kernel @Alucard and @ktoonsez) onto a device specific rom (CM jfltespr) quite a bit of the unification code must be in the kernel.
todivefor said:
What you refer to as auto-detection and auto-selection is all built into the rom or kernel, not the updater script. Most of my experience is with CM12.1 optimized which is unified by @AntaresOne and uses the @Alucard kernel. Neither rom nor kernel zips have any auto-selection in their updater scripts. Each has only one boot.img. I have flashed @Alucard's and @ktoonsez's kernels on both CM12.1 optimized and jfltespr CM12.1 nightlies along with other AOSP roms. As I can flash a unified kernel @alucrad and @ktoonsez) onto a device specific rom (CM jfltespr) quite a bit of the unification code must be in the kernel.
Click to expand...
Click to collapse
Thanks for that info...so the detection and selection of correct drivers occurs on kernel level.
KennyG123 said:
Thanks for that info...so the detection and selection of correct drivers occurs on kernel level.
Click to expand...
Click to collapse
That's what I have seen.
Don't know this for fact, but in another thread read that Sprint variant is the only one that has different partition layout. Confirmed TMO and Canadian have same layout, but different from Sprint.
Related
Other than the Kernel, what is it that separates the Sprint S3 from the Verizon S3 from the US Cellular S3, etc.....
The frequencies to which the radios are tuned -- mostly the LTE radio and probably the EVDO radio. Plus, the Verizon S3 has a SIM slot (not sure about the US Cellular version) because of their deal for the AWS spectrum. Oh, and the Verizon S3 has a wireless charger available that's incompatible with the Sprint S3 because the Verizon one has extra connectors under the battery.
Putting the ILLA in KILLA since 1985
Yeah, also the vendor files are different (/system/vendor)
Ahh, yeah, the vendor files make sense and yeah., USCC has a SIM card in it, too
Sprint has a sim card in also, but it's non removable
Transmitted with a portable device using Xparent Blue Tapatalk 2
edfunkycold said:
Sprint has a sim card in also, but it's non removable
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
So, my next question, if you are going to build a ROM, and you take out the radios, and the carrier's specific vendor files, (OK, this is a stretch but you'd have to have an available kernel for each carrier to add to the ROM prior to flashing and if the S3 is anything like the moment, it's a simple as replacing the zImage in the zip file with the kernel you want) would the ROM flash and would it work?? Could you creat an update zip for the carrier specific vendor files. Do the radios NEED to be part of the ROM zip?? Can you create a ROM without the radios, etc??
You see where I'm going with this?
HipKat said:
So, my next question, if you are going to build a ROM, and you take out the radios, and the carrier's specific vendor files, (OK, this is a stretch but you'd have to have an available kernel for each carrier to add to the ROM prior to flashing and if the S3 is anything like the moment, it's a simple as replacing the zImage in the zip file with the kernel you want) would the ROM flash and would it work?? Could you creat an update zip for the carrier specific vendor files. Do the radios NEED to be part of the ROM zip?? Can you create a ROM without the radios, etc??
You see where I'm going with this?
Click to expand...
Click to collapse
No the radios dont necessarily have to be part of a rom. But at boot, the kernel initializes all of those services so it may or may not give errors and may or may not prevent it from booting up completely
But are you trying to create a multicarrier rom? I'd suggest looking at the ones that already exist. The general method to do it is exactly where you're going with this, the devs use aroma installer and install the carrier-specific files (vendor files, etc) based on the selection the user makes for their carrier
Sprint defaults to some different build props and other options like mandatory camera sound, MMS deactivated options like group send to a lot of recipients, etc. All of those are modifiable if rooted of course.
My Galaxy SIII setup and tweaks:
[spoil]
Sprint Galaxy S3 SPH-L710 // MOAR 2.4 + MC3 + buildprops // KT747 ktoonservative-DEADLINE 384-1728Mhz + TK Mod + scaling tweaks // Crossbreeder entropy + DNS + blocking // Lagfix fsTRIM // TWRP // Nova Prime // sent from xda premium // ATMIRL on Miniclip 8 Ball Pool ** Come at me bro! [/spoil]
CNexus said:
No the radios dont necessarily have to be part of a rom. But at boot, the kernel initializes all of those services so it may or may not give errors and may or may not prevent it from booting up completely
But are you trying to create a multicarrier rom? I'd suggest looking at the ones that already exist. The general method to do it is exactly where you're going with this, the devs use aroma installer and install the carrier-specific files (vendor files, etc) based on the selection the user makes for their carrier
Click to expand...
Click to collapse
Ahh, very cool .I haven't seen Aroma since Mazda and Jaime were using it on their ROMS last year. Yeah, that's the ticket right there. Pick the carrier, get the right kernel and carrier specific files plus any other options you'd want!
HipKat said:
Ahh, very cool .I haven't seen Aroma since Mazda and Jaime were using it on their ROMS last year. Yeah, that's the ticket right there. Pick the carrier, get the right kernel and carrier specific files plus any other options you'd want!
Click to expand...
Click to collapse
Several of the most popular roms here on the S3 use aroma installer. TPR and MOAR for examples.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Yeah Aroma is boss, and Aroma file manager is even cooler :thumbup:
As the title suggests, is there a kernel for the P605 which will allow SElinux permissive, and therefore allow full linux chroot installs to be completed with relative ease.
I am aware of a permissive kernel for P600, http://forum.xda-developers.com/showthread.php?t=2590311
but assume this will not function for the P605.
If not can the same steps used to make the P600 kernel permissive be applied to a P605 kernel?
Looking for the same kernel
I'm looking for the same SELinux-permissive kernel for P605.
You definitely can't use the P600 kernel as it is for the Exynos variant (P600/01) while ours (P605) is the Quallcom CPU.
Unfortunately the P600/01 was released around the world first with most devs getting the Exynos version. Little developement has been done for the P605 but there has been a little. Just not for an SE-Linux permissable kernel, at least not here on XDA...
Will try to build it myself
I've been thinking of modifying and building the kernel myself. The problem is that there are several kernel source codes on Samsung's website for SM-P605. (I can't post the link here) My device model is SM-P605 without any suffixes so I think it's the first kernel that I should choose.
I think modifying the kernel into SELinux permissive should be as easy as changing a default value in one of the source files and then I can build the kernel using the instructions that come with it. Fingures crossed!
One more thing: in the source code that Samsung provides there are two directories, one kernel and the other platform do I need to build the platform too?
Rhesus007 said:
I've been thinking of modifying and building the kernel myself. The problem is that there are several kernel source codes on Samsung's website for SM-P605. (I can't post the link here) My device model is SM-P605 without any suffixes so I think it's the first kernel that I should choose.
I think modifying the kernel into SELinux permissive should be as easy as changing a default value in one of the source files and then I can build the kernel using the instructions that come with it. Fingures crossed!
One more thing: in the source code that Samsung provides there are two directories, one kernel and the other platform do I need to build the platform too?
Click to expand...
Click to collapse
Hey Rhesus007, just wondering if you have made any progress?
Im really in need of a permissive kernel, however i have no knowledge of how to make it etc.
Thanks.
Just dropping back in the thread, still hoping this will happen, as linux on this tab would be really useful imo.
Someone with some dev experience might be able to use the methods used on the note3, which has the same snapdragon 800 soc to achieve this. The basic steps needed to modify the kernel are described in this thread
http://forum.xda-developers.com/showthread.php?t=2471416
if nobody with experience can do this, I might give it a try, but that might be a recipe for disaster....
patchseven said:
Just dropping back in the thread, still hoping this will happen, as linux on this tab would be really useful imo.
Someone with some dev experience might be able to use the methods used on the note3, which has the same snapdragon 800 soc to achieve this. The basic steps needed to modify the kernel are described in this thread
http://forum.xda-developers.com/showthread.php?t=2471416
if nobody with experience can do this, I might give it a try, but that might be a recipe for disaster....
Click to expand...
Click to collapse
I've got no experience with this, if you could attempt it, I'm sure a lot of people would be grateful!
For those still looking.
Maybe this might work, don't know if it will work on custom ROM's
http://forum.xda-developers.com/showthread.php?t=2765353&page=3
EP005 said:
Maybe this might work, don't know if it will work on custom ROM's
http://forum.xda-developers.com/showthread.php?t=2765353&page=3
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...rnel-stock-selinux-permissive-kernel-t3232814
For the 5.1.1 update!
Hi,
Please can someone explain why Exynos has a bad rep for custom ROMs? Samsung release the kernel and I assume it contains either open source drivers or binary blobs. Either way we have a functional boot.img with a working ~3.4 kernel, that kernel should presumably boot any sensible 4.4+ system.img right?
I'm asking because I'm considering building a clean ASOP ROM for the Tab S just to get rid of the crazy amount of bloat. This is obviously trivial with the Nexus device line, but I'm just trying to understand why it's complex in this case? Can we not just use the stock kernel/drivers with any arbitrary userspace e.g ASOP git or CM? Does the SoC really matter to us for non-kernel projects? Or are all the problems purely in the custom kernel world?
Also, is there anything actually important in Samsung's userspace that i'm missing? It's really just the UI and little extra features for the camera and things right? I can't help but feel the speed gain from an ASOP built would be incredible, all the hardware should work just fine given a working stock kernel?
Thanks!
@eousphoros is working on porting CM right now. Why don't you PM him and see if you can put your heads together on it?
jasonfxp said:
Hi,
Please can someone explain why Exynos has a bad rep for custom ROMs? Samsung release the kernel and I assume it contains either open source drivers or binary blobs. Either way we have a functional boot.img with a working ~3.4 kernel, that kernel should presumably boot any sensible 4.4+ system.img right?
I'm asking because I'm considering building a clean ASOP ROM for the Tab S just to get rid of the crazy amount of bloat. This is obviously trivial with the Nexus device line, but I'm just trying to understand why it's complex in this case? Can we not just use the stock kernel/drivers with any arbitrary userspace e.g ASOP git or CM? Does the SoC really matter to us for non-kernel projects? Or are all the problems purely in the custom kernel world?
Also, is there anything actually important in Samsung's userspace that i'm missing? It's really just the UI and little extra features for the camera and things right? I can't help but feel the speed gain from an ASOP built would be incredible, all the hardware should work just fine given a working stock kernel?
Thanks!
Click to expand...
Click to collapse
The big problem I ran into is with gralloc/hwcomposer. The hwcomposer that ships with the device is 1.3 whereas the opensource is currently only 1.1. While the initial thought of just copying gralloc.exynos5.so hwcomposer.exynos5.so as propertietary blobs seems like it a good one, they are unfortunately linked to a ton of libraries in /system/lib that makes bringing them over troublesome at best. Though that being said that is the hack I used to get my one and only bootable rom up and running.
Going further the issue with the exynoshwc 1.1 that I have been fighting with is after opening up /dev/graphics/fb0 it trys to send it an ioctl that I assume is the S3C_WIN_CONFIG pointer and gets an ENOTTY back from the device. If you are interested in helping out please checkout the cyanogenmod porting thread in general where I have linked my local_manifests.xml with my git repo's and a blog of my progress.
Cheers.
EDIT: Has anyone ever requested source from samsung? What seems to be the most succesfull method?
What would it take to see a base AOSP ROM put together for the LG G4? I know there's some folks working hard at bringing CM to the G4, but what about an AOSP unmodified ROM with drivers, of course? I've always wondered if that is a better option than say a ROM like CM which has loads of known bugs and issues.
Maybe an AOSP super-stock setup which we could modify after via Xposed / Mods to add in what we want would be a better option?
CJ-Wylde said:
What would it take to see a base AOSP ROM put together for the LG G4? I know there's some folks working hard at bringing CM to the G4, but what about an AOSP unmodified ROM with drivers, of course? I've always wondered if that is a better option than say a ROM like CM which has loads of known bugs and issues.
Maybe an AOSP super-stock setup which we could modify after via Xposed / Mods to add in what we want would be a better option?
Click to expand...
Click to collapse
After we finish the device tree and everything is working, it can be then used to build whatever Rom you desire
You rock, thank you for the quick response! I'm not even sure what kind of rom I desire. I just know it would be neat to go full on basic AOSP and add from there without some of the clutter and bugs introduced with CM's stuff, although CM has always been an enjoyable experience. Whoot for guys like you!
I know this is old thread... but what source tree are we talking about here? Obviously not AOSP itself, i think... right?
CM source?
Maybe i'm missing something about branches of AOSP... and other trees..
many thanks
mythos234 said:
After we finish the device tree and everything is working, it can be then used to build whatever Rom you desire
Click to expand...
Click to collapse
thenextdon13 said:
I know this is old thread... but what source tree are we talking about here? Obviously not AOSP itself, i think... right?
CM source?
Maybe i'm missing something about branches of AOSP... and other trees..
many thanks
Click to expand...
Click to collapse
They talked about device tree here. An example for a pure AOSP one for the device LG H815 is here:
https://github.com/cile381/android_device_h815
See this for an explanation :
http://wp.me/p6ZeCY-3p
AOSP source contains the sources to build a ROM which are the same for all devices and a device tree is a device specific description on how to build or as the above link states:
“A device tree is a tree data structure with nodes that describe the physical devices in a system”
.
Sent from my LG-H815 using XDA Labs
Thank you, steadfasterX.
That provides some clarity, although I think there is still a bit missing for me--
Ugh, i can't post links because of spam rules.. :-/ makes describing things harder.
How did you find the github cile381/android_device_h815 as being the AOSP tree for that phone? My understanding was that the AOSP main repo is here:
android.googlesource.com
And so related to my question previously.. i guess i'm confused specifically who the 'we' is that mythos234 references, and where that source would be located...
many thanks!
krexus_7.1.1-170309-flounder.zip - https://www.androidfilehost.com/?w=files&flid=144667 March security updates & Rootless Substratum
THINGS TO READ BEFORE ASKING:
Use N4F26T Vendor Image for 03/09.2017 build.
Stock kernel does not force encryption.
Not prerooted.
Built for the Nexus 9 Wifi (but it works on Nexus 9 LTE too. Flash latest volantisg vendor IMG and manually set APN)
Originally Posted by @KreAch3R
Krexus was born out of a simple necessity. The latest releases of stock Android (namely lollipop and marshmallow) were pretty close to my idea of a perfect android ROM, yet missing some elements, which are meant to be included in stock Android, at least for me. Starting from a clean AOSP environment, only specific features and fixes are included, which are personally tested ON HAMMERHEAD, with one goal in mind. To create a stock like android ROM, "as it should be".
This means, and I mean it, a ROM like how stock nexus image should be, for me.
This isn't going to get bloated. Most UI "features" are already there.
This isn't going to start picking commits relentlessly, I will test them personally and only add things that 1) work like they should 2) would fit in a stock ROM.
This isn't going to be updated very quickly. Only security and bug fixes will be pushed out ASAP.
This is going to follow Google's & AOSP guidelines as closely as I can.
And lastly, this is first and foremost a ROM about Nexus 5 (hammerhead). This is my personal device, this is where I test the ROM. angler, bullhead, flo, mako, shamu builds are provided AS-IS, and bugs/missing stuff/features especially for them will be put on the lowest priority and will depend on my free time. I will only guarantee the nexus 5 ROM and its abilities.
That said, welcome aboard!
Click to expand...
Click to collapse
Google+ Community
PushBullet Channel
DOWNLOAD LINKS:
KREXUS on AndroidFileHost
Previous Builds
CHANGELOG
Source Code: https://github.com/krexus
When @KreAch3R started building this ROM for shamu in 2015, I jumped on board right away. I've got Krexus running on every Nexus in my family: mako, hammerhead, shamu, grouper, and NOW flounder.
It runs beautifully on flounder and I hope you enjoy it too.
I am extremely grateful to @KreAch3R for all of his help and support.
IMPORTANT POINTS:
You have to flash GApps (Open or BaNks recommended)
ROM is not rooted, flash stable SuperSu for root
Busybox is included
Included kernel is stock no-force-encrypt
Flash newest factory vendor.img (I had Layers issues with stock selinux enforcing kernel on an older vendor version. Newest vendor.img works perfectly with stock kernel enforcing and layers)
F.A.Q.
a.k.a questions you shouldn't repost
Check the always updated F.A.Q.:
https://plus.google.com/+GeorgeGian/posts/f9m7zmi42Gy
OR
https://docs.google.com/document/d/1hMX-lQ2iUiNsrhszMIlp0Wwj1tSHWvsaEQ_yT4pD_eE/edit?usp=sharing?
BELIEVE ME, THE QUESTION YOU HAVE IS PROBABLY ANSWERED THERE.
Thank you for supporting the building for flounder, @buffal0b1ll!
For the next build, I will try to make Layers work with the default google kernel, and fix the processor info.
I want to specifically thank @BeansTown106, which device trees and blobs I used for this bringup.
Enjoy Krexus!
Another more conspicuous link for the Krexus G+ community.
https://plus.google.com/communities/117603046007221302455/
You will want to join this community if you like Krexus. It's very beneficial to hear user and developer advice/feedback and experiences across all supported devices.
Firsties!
Sent from my Motorola Nexus 6 using XDA Labs
Finally, we are starting to get some more quality ROM builds for this device. This is just awesome.
KreAch3R said:
For the next build, I will try to make Layers work with the default google kernel
Click to expand...
Click to collapse
Layers actually works fine with the default kernel and SELinux enforcing. An up to date vendor.img flash was all I needed to fix that.
Is charging extremely slow for anyone else? Latest Fire&Ice kernel.
dictionary said:
Is charging extremely slow for anyone else? Latest Fire&Ice kernel.
Click to expand...
Click to collapse
Try the purenexus version of fire & ice
Sent from my Nexus 9 using XDA-Developers mobile app
dictionary said:
Is charging extremely slow for anyone else? Latest Fire&Ice kernel.
Click to expand...
Click to collapse
I'm still using fire-ice 10.2.2 and haven't noticed slow charging. In 18 minutes I went from 27 to 35% just now. Ampere has me charging at 1460 mAh
Thanks for a great rom! Will it work with LTE version?
maelfilk said:
Thanks for a great rom! Will it work with LTE version?
Click to expand...
Click to collapse
I'm glad you like it! I don't know, as I don't have either device. Are the ROMs interchangeable on these two variants? For reference, the device tree is highly based on PureNexus' excellent tree (both based on AOSP with very few commits). The kernel is the default google kernel for flounder.
KreAch3R said:
I'm glad you like it! I don't know, as I don't have either device. Are the ROMs interchangeable on these two variants? For reference, the device tree is highly based on PureNexus' excellent tree (both based on AOSP with very few commits). The kernel is the default google kernel for flounder.
Click to expand...
Click to collapse
Will try it out on the weekend and report
Works great with LTE version!:good:
maelfilk said:
Works great with LTE version!:good:
Click to expand...
Click to collapse
That's awesome! Any hoops you had to jump thru?
buffal0b1ll said:
That's awesome! Any hoops you had to jump thru?
Click to expand...
Click to collapse
Nope, just flashed the rom and mobile data works right away. Corresponding section in settings and mobile data tile are also there.
maelfilk said:
Nope, just flashed the rom and mobile data works right away. Corresponding section in settings and mobile data tile are also there.
Click to expand...
Click to collapse
Sweet. Not even a vendor fingerprint mismatch?
buffal0b1ll said:
Sweet. Not even a vendor fingerprint mismatch?
Click to expand...
Click to collapse
I always flash vendorfix in twrp to 100% avoid this error so can't tell
maelfilk said:
I always flash vendorfix in twrp to 100% avoid this error so can't tell
Click to expand...
Click to collapse
Got it. FYI I'd been manually vendor fixing the fingerprint since December on the Wi-Fi flounder and had layers issues on the stock enforcing kernel. Fire ice made it work with the old hacked vendor partition. To make layers work with stock kernel i updated to may factory vendor.img