Since Nextbit has stubbornly decided that the Robin will not officially support Robin, I must turn to custom roms to properly make use of the hardware in this phone. To that end, I have been having difficulty locating a rom with the necessary GPU libs to support Vulkan, and I am not ready to experiment with patch zips. Can anyone provide a list of roms they know include it?
https://insider.razerzone.com/index.php?threads/vulkan-support.23169/
Related
Just wondering. In the early stages of a ROM, it always seems like camera, and camcorder don't work. Why? Thanks in advance.
These depends on the hadware, it require proper kernel drivers with matching APIs inside it for external apps to access the device.
in case of ICS,there are lots of changes in APIs which provide access to these devices.
But the Manufacturer (OEMs) has not yet provided/released any ICS compatible kernel drivers or source code for that either.
So unless u dont have source code or drivers, such things will happen.
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?
Ive been enjoying Resurrection Remix [Unofficial] rom and was wondering if they or any other rom for the Xperia Z5 P will support Oreo?
There is no kernel so unfortunately no
tset351 said:
There is no kernel so unfortunately no
Click to expand...
Click to collapse
???
zacharias.maladroit said:
???
Click to expand...
Click to collapse
Well there are no kernel sources nor binaries, blobs etc. so I guess there will no custom rom be available anytime soon but please correct me if I'm wrong. I would be glad to have Oreo on my Z5P.
tset351 said:
Well there are no kernel sources nor binaries, blobs etc. so I guess there will no custom rom be available anytime soon but please correct me if I'm wrong. I would be glad to have Oreo on my Z5P.
Click to expand...
Click to collapse
The developer seems to be busy so allow me to answer (though I'm not that experienced). I'm pretty sure that Sony always releases it's phone's kernel sources. Phone hardware doesn't change from an update so when the sources are released they can be used to create a kernel for any android version (basically developers need access to unique hardware). Blobs are like closed-source kernel modules. They're provided with the kernel source but the manufacturer doesn't want them to be copyrighted or tampered with. So I'm sure that Oreo will be available on your device, just give the developers some time. And please don't answer questions if you don't know what you're talking about (at least write that you're inexperienced).
Nik0laTesla said:
The developer seems to be busy so allow me to answer (though I'm not that experienced). I'm pretty sure that Sony always releases it's phone's kernel sources. Phone hardware doesn't change from an update so when the sources are released they can be used to create a kernel for any android version (basically developers need access to unique hardware). Blobs are like closed-source kernel modules. They're provided with the kernel source but the manufacturer doesn't want them to be copyrighted or tampered with. So I'm sure that Oreo will be available on your device, just give the developers some time. And please don't answer questions if you don't know what you're talking about (at least write that you're inexperienced).
Click to expand...
Click to collapse
I am a very inexperienced person.
For MSM8994 platform there is only 3.10 kernel sources available, at least on sony's developer page. On open devices resource list, there are binaries for Z5 premium for 5.1, 6.0, 6.0.1, 7.0 and 7.1 but unfortunately no 8.0 or 8.1. And well, developers can take their time - as long as they want because I don't use that cell phone anymore and I won't expect any custom Rom changes anytime soon especially for a 2015 Device which had very less development going on since its launch.
But once again, I am very inexperienced.
Nik0laTesla said:
The developer seems to be busy so allow me to answer (though I'm not that experienced). I'm pretty sure that Sony always releases it's phone's kernel sources. Phone hardware doesn't change from an update so when the sources are released they can be used to create a kernel for any android version (basically developers need access to unique hardware). Blobs are like closed-source kernel modules. They're provided with the kernel source but the manufacturer doesn't want them to be copyrighted or tampered with. So I'm sure that Oreo will be available on your device, just give the developers some time.
Click to expand...
Click to collapse
Ok, sorry I got a bit mixed up in the devices :laugh:. Either way Snapdragon provides up to date documentation on their SOC's (which is the most important hardware component on the device) so developers should still be able to provide Oreo. And you are right the Z5 premium is an old device and support usually drops as soon as the developer gets rid of that device. But it's weird how much attention different devices get. For example I have a Oneplus X (SD801, I know it's ancient) (didn't even get Nougat) and there are multiple Oreo 8.1 ROMs available.
Hi, i'm asking to devs if it's possible to port say Galaxy S9's rom to Treble enabled devices or even other manufacterer roms such as LG's or HTC? I thought S9 was released with Oreo, therefore it should have Treble support and could its stock rom can be used a GSI rom or am i wrong? Thanks in advance.
+1. Want to see Samsung Experience on my device too
I Wont Samsung Experience on my Device Too :crying:
Most capable man atm
@fxsheep
Jamie_oppo said:
Most capable man atm
@fxsheep
Click to expand...
Click to collapse
Wait for SE 10.0 Android P,
I can be possible. Yes!
But there are many Knox dependecies on TW kernel. Even if you did, stuff like storage wont work at all.
I'm doing a lot of research about GSIs and Project Treble recently; and that was the FIRST thing that came in my mind.
"What if my Xiaomi could run Samsung Experience?"
I absolutely love Stock Android; and Android Pie looks pretty close to Samsung Experience 9.0 based on Oreo.
But still; it'd be nice to have Galaxy Note's exclusive features on a bloody Xiaomi!
I think its going to be a headache for developers; but a bug-free, smooth running Samsung Experience GSI would be a bombshell for sure!
HighonBolo said:
Hi, i'm asking to devs if it's possible to port say Galaxy S9's rom to Treble enabled devices or even other manufacterer roms such as LG's or HTC? I thought S9 was released with Oreo, therefore it should have Treble support and could its stock rom can be used a GSI rom or am i wrong? Thanks in advance.
Click to expand...
Click to collapse
I'm not a Dev but I can tell you, No it'll never happen!
Here's some reasons why....
Project treble is just a way to separate proprietory vendor files and driver's from the base of ROM and giving them a standard to interface with new roms. It means the device is compliant with treble roms, not that their stock ROM is.
Treble roms are built from source code and that code is written to allow 1 GSI to be installed on multiple devices and work their hardware. Samsung has no source code for their roms.
Allot of Samsung's features are all tied in with their framework and also hardware dependent.
So the only way to remotely get a manufacturer ROM on another device is by porting. Which is a difficult process.
aaron74 said:
I'm not a Dev but I can tell you, No it'll never happen!
Here's some reasons why....
Project treble is just a way to separate proprietory vendor files and driver's from the base of ROM and giving them a standard to interface with new roms. It means the device is compliant with treble roms, not that their stock ROM is.
Treble roms are built from source code and that code is written to allow 1 GSI to be installed on multiple devices and work their hardware. Samsung has no source code for their roms.
Allot of Samsung's features are all tied in with their framework and also hardware dependent.
So the only way to remotely get a manufacturer ROM on another device is by porting. Which is a difficult process.
Click to expand...
Click to collapse
Thanks, but I wanna ask what will happen if I done these:
1. ADB pull everything from /system on a rooted Samsung phone
2. Repack it into system.img
3. Use erfangsi tool to convert it into a GSI
Not challenging you, just completely out of my curiosity.
As the thread question states I am a junior Java/Kotlin developer and would like to contribute to custom rom projects.
I have been mainly using Lineage OS on my old devices for a past few years and I am genuinely thankful for this community and would like to give back.
I have no idea where to get started and the only threads I found were really old from 2013 and hence I am posting it here. I have only gone as far as compiling AOSP from source and managing to flash it to my device. ( Any guidance is welcome ).
I have 2 additional queries :-
1) Why most custom rom releases are based on AOSP or Lineage as source rather than working backwards from the manufacture's provided rom? In that way the device can retain most of this functionality.
2) I have observed QUALCOMM powered devices are much more appreciated in this community compared to MediaTek, Why is that so? Recent MediaTek Chips have been quite powerful yet support from the community isn't there yet ..... what are MediaTek chipsets lacking ?
Mediatek doesn't release their source code so it's very difficult to develop custom ROMs.
Correct me if I'm wrong
How does your self-built AOSP perform? Everything working correctly?
I think the first question is, because the manufacturer's ROMs are proprietary and closed source, so it's not impossible, but difficult I think. Dunno how Xiaomi.eu does it.
Second question is, because Qualcomm releases source code to CAF - Code Aurora Forum. Custom ROM/Kernel Makers pull a few bits & pieces from CAF into their AOSP ROM, for that added spice.
I think MediaTek does too, but only for few devices?